"Requirements Engineering-software modeling and analysis" reading notes three

Recently read the "Demand Engineering-software modeling and Analysis" This book, this time I read the fifth part of the "demand management and engineering management", divided into three chapters, demand management, demand engineering process management, demand engineering project management.

Requirement management includes maintenance requirement baseline, requirement tracking, control change, and requirement management in practice. The important task of demand management: to communicate the needs of stakeholders, to apply and implement the requirements to the solution, to drive the design and implementation of the work, to control the change, to send the demand distribution to the subsystem, to test and validate the final product, to control the changes in the iterative development, and to assist the project management. After the requirements development activities, the requirements baseline should be the basis and binder for subsequent software system development: First, the project manager monitors and manages the project plan according to the requirements. Second, developers develop corresponding product features and features based on requirements. Thirdly, testers perform system tests and acceptance tests as required. The customer and the guest will accept the final product according to the demand. Five, the maintenance personnel reference requirements to carry out product evolution. In other words, after the production, the impact of demand throughout the follow-up of the product life cycle, rather than simply exist in the demand development phase. Software Requirements Specification documentation plays an important role in all phases of the product life cycle. Many of the subsequent development efforts should be based on the content of the software Requirements Specification document as standards and objectives. Therefore, after the end of demand development, there is also a need to have a force to ensure that the follow-up system development activities in accordance with the requirements of the baseline, so as to ensure the quality of the system. Demand management is such a management activity, it is in the product cycle after the demand development to ensure the effective play of demand function.

In the process management of demand engineering, there is the environmental dependence of the requirement engineering process, the establishment of the requirement engineering process and the improvement of the requirement engineering process. One of the difficulties in building a successful demand project is that the details of the requirements engineering activities cannot be described by a systematic knowledge system, but there are a lot of practical ways to explain it. Therefore, the establishment of an effective demand engineering process will require the process of the customizer familiar with and master a large number of time methods, and choose, implement and maintain a set of effective practical methods.

Project management in demand engineering includes resource support, life cycle planning of demand engineering, team management and demand risk management.

As a result of demand development, the final requirement should be defined and fixed and communicated to other project staff. A requirement baseline is an explicit and fixed set of requirements that a project team needs to implement in a particular product release. Once a requirement baseline has been established, the stakeholders of the project can have a consistent understanding of the functionality and characteristics of the product and work on it as a basis for common goals. A requirement baseline is a summary of the results of the demand development process, which needs to continue to play a role in the subsequent product life cycle. As a result, the requirement baselines exist in a way that is consistent, balanced, and easy for project stakeholder access, typically by writing requirements baselines into formal documents and incorporating configuration management. After the establishment of a demand baseline, it was not immutable. In product development and after product use, users and other product stakeholders will still ask for changes in demand, these changes should be timely and consistent reflected in the requirements baseline. Of course, this change should be controlled. In the actual software system development, facing the changing environment of business and technology, the risk of software system being inconsistent and deviated from the demand baseline in the process of development or evolution is increasing. In order to avoid this phenomenon, control the quality, cost and time of software development, people put forward the method of demand tracking. Demand tracking is an effective control method, it can coordinate the evolution of the system in the change of the stakeholder's demand, and maintain the consistency of the development work to the demand. Demand tracking means that each requirement is described and understood from the beginning of its initial occurrence, and that the process of understanding should permeate the requirements development process, the subsequent system development process, and the continuous refinement and iterative process. Demand tracking is the unified management and use of knowledge in the project. Ignoring the traceability of demand, or capturing the tracking relationship is inadequate, reducing the quality of the system, causing rework, and increasing the cost and time of the project. In the absence of effective management of the requirements of the project, there are often erroneous decisions, misunderstandings and erroneous information exchange. If someone leaves the project, the lack of effective management of knowledge in demand will also lead to the loss of knowledge.

"Requirements Engineering-software modeling and analysis" reading notes three