Difficulties for enterprise-level application software development

Abstract: For the dilemma of Enterprise Technical Architecture Software Development, see Preface
Eliminate Wolf
Top 10 proposition programming rules of software

I have been very busy recently and have no time to write a blog. When I write an article today, I feel that the following content can be shared with you.

Without the support of the enterprise's technical architecture, application software development is just as miserable as early software programming without the support of the operating system. It cannot get rid of the following three dilemmas:

1) hands-on workshop-based development, strong reliance on technical personnel;

2) The software development team is firmly tied to secondary work (tedious implementation details), not to the root problem;

What are the fundamental and secondary issues in software development? In his famous article "no silver bullet", Mr. Brooks elaborated in detail that demand and design are fundamental issues in the software system, while specific technical implementation is secondary issues; at present, most of the projects are entangled in technical details, how to listen to control events, how to parse packets, what stack, what list, what hasmap, what observation mode, What decoration mode ......, The technicians are fascinated by these wonderful terms, and the project team is like a fierce beast struggling in the tar pit. The fundamental problems of requirements and design are ignored as a pass-through and formal document. More energy is consumed in the tar pit, and the project has essentially evolved into a coding and testing process that satisfies the functions, (What's more terrible is that due to the lack of a serious demand analysis process, these functions are only individual requirements, not the essential needs of the business field, and they are fragile and easy to change ), the core principle of software system design-the open and closed principle, has become the Project Group's prehistoric distant memories, and the vague ones have no trace. Everyone is busy with secondary issues.

3) an expensive application system is like a land house built on a technical sandpile. It has no foundation and cannot withstand storms. Any changes in technical details, messages, or data formats will cause an earthquake in the application system;

How to face the impact of the flood of technological development, the system design guided by the principle of no open or closed, and the functional-oriented software development process, how can we meet the vigorous development requirements of our business!