"Ten Steps to software Requirements" read Note three

Since the requirement is a project, there is a complete process. Requirements Engineering research field can be divided into three parts of demand planning, demand development, demand management, the new generation of demand engineering process is composed of 10 business activities, namely business Research, application modeling, system planning, analysis and calculation, Report preparation, planning review, demand acquisition, demand analysis, demand preparation, demand verification.

There are three kinds of roles in traditional demand analysis, such as customer role, analysis role and team role, three kinds of roles, different thinking modes, and there are many contradictory problems. The problem arises from the fact that each field is running on its own track, and that it does not combine to create many differences. So in order to solve this problem, we have introduced a new field called demand Planning area, the role of this domain is called the requirement architect. In fact, as the name implies, the architect is to determine a direction problem, not focus on the development details, and do not care about the scale of management, is to all work to determine a premise, and this premise is crucial.

Of course, the process of demand engineering is not static, with the new theory, new practice summary, the new experience will be a modest transformation. So, why should we improve it? The goal of the improvement must be to solve the problem, to solve the problems of the previous project and the current project, and to prevent the problem, and to improve the quality of the software requirement continuously.

Always say that demand is the core of software projects, so in the development process, there will be a lot of business activities and software requirements associated.

In other words, demand engineering process improvement at all times need to pay attention to the various business activities of software development, we are in fact every improvement is to let customers, users, developers and other satisfaction.

The improvement also needs certain principle, does not pursue a perfect, the repeated grinding gradual adjustment, determines the improvement goal, has the goal to have the direction only then the impetus, the improvement activity as the project to operate, the timely review improvement effect, in fact is in order to "faster, higher, stronger".

"Ten Steps to software Requirements" read Note three