"Ten Steps to software Requirements" read Note one

Since the learning software, each program teacher will tell us to carry out needs analysis, and sometimes they will simply need analysis, and sometimes do not control, and then every time the program will be censored to their own do not know what the program to do what, the program is used to do what, the more you feel the problem with the implementation of the results are separated a lot , without the original idea of his own. Now to learn the needs analysis, it is too easy to feel your own ideas. Through the reflection on the process of previous program writing, the importance of demand analysis is deeply realized. "It is beneficial to Choufso the demand analysis work beforehand, and Choufso is fearless afterwards."

Always think that the program is the key to good or bad software, always ignoring the need for software analysis. Many data show that software requirements analysis is the key to improve software quality, but also the key to determine a software project.

By reading the first two articles of this book, we have a preliminary understanding of the principles and basic knowledge of the requirements engineering. In addition, the recent period of study on demand engineering to see the importance of demand engineering to software development.

The first chapter of this book compares software requirements to Achilles ' heel ———— a deadly weakness. This is perhaps the key to China's software has been bad. We need to take the "heavy business, heavy system" as an important concept of the new generation of software requirements engineering. and re-positioning software requirements and the use of logic method is the software needs to be complete, accurate, clear, change controllable and so on. Software requirements are divided into business and information planning, user requirements analysis and system requirements analysis. Software requirements have both content features and formal features, and different features are the objectives of different software requirements.

Compared with the traditional software requirement engineering, the new software requirement engineering increases the demand planning. Requirements planning has developed a problem analysis, target analysis, business analysis, system analysis constitute the business and information planning instructions, used to guide the needs of development work and software engineering aspects of the work. The new software requirements engineering consists of 10 business activity structures, such as business Research, application modeling, system planning, demand acquisition, and demand analysis. 10 links, the last part of the output is the next step in the input. The quality of demand analysis determines the success or failure of the project, and the neglect of business analysis and demand analysis is a common drawback in the current software development work. To make good software, business analysis, demand analysis and system and coding must be placed in the same high position.

The different roles in demand analysis have different requirements for software, which creates a contradiction. This requires the system architect to have the customer's thinking, think of the customer. The system architect should be a link between the customer and the software developer. The requirement engineering is not invariable, it will adapt with the new theory, the summary of the practice process, the improvement of software development technology and so on. In the software development process, the requirement risk can not be neglected and omitted, any error (whether understanding or programming) may bring the risk that cannot be underestimated.

"Demand engineering is the center of the circle, software engineering is a dot" is a real portrayal of the relationship between demand engineering and software engineering. I think the requirement engineering is the foundation of software engineering, the requirement engineering provides a basis and a direction for the software engineering, and the software engineering is an implementation of the requirement engineering.

Under the three theories of demand engineering, the knowledge system of each sub-system is different, and each has its own principles and methods. Requirements engineering is based on a universal trial, whether for software engineering or other engineering fields. The knowledge of requirements engineering involves proprietary software knowledge such as software development, architecture, and information resources. The specific knowledge of demand planning includes demand planning, demand development, and demand management. From the previous business requirements to the technology to the current business and technology to start interrelated, mutual constraints to the future of business as the core, technology and business both ends, the change in demand analysis is increasing, which also reflects the importance of software development for demand engineering, which can also be seen as a form of development change, The liberation of a development idea!

The key to the new requirement planning is the problem, the business, the system three kinds of elements. Ask questions, find the root cause, find the crux of the problem we often say in the direction, positioning, fixed point. In my opinion, the seven principles of demand planning provide us with a demand analysis of seven areas to be aware of. Although the understanding of demand engineering is not in place, but the basic concept of understanding is still possible. Although the requirements engineering mentioned a lot of principles, models and so on, but all put forward to business-oriented, technology as a supplement, visible demand engineering importance. These are for the future development, concrete learning laid the foundation.

"Ten Steps to software Requirements" read Note one