"Ten Steps to software Requirements" read Note five

This reading note writes the sixth chapter of the book "Management".

The sixth chapter is divided into four chapters, which are the thinking of demand management, the requirement version control, the management change request and the requirement tracking ability.

First, the first chapter, "The thinking of demand management."

The goal of the requirements management activities is to ensure that the requirements business activities are able to produce high-quality software requirements specifications that are comprised of business requirements, user requirements, and system requirements, in line with progress requirements, quality requirements, and cost requirements. The requirement management work is to integrate and standardize the requirement business activities with the help of the requirement contract which is composed of baseline, version, State, change and tracking. The purpose of a requirements management activity is to create a document-based requirement baseline between the customer and the software developer. The specific work of the requirements management Organization is composed of the content of the requirements management activities.

Then the second chapter, "Demand version control".

The software requirements baseline is the integration of the work results document for each stage of the requirements business activity and the version number of the content within the document. The implementation of the software requirements baseline is achieved through the work results documentation and the content version numbers within the documentation. The version number is a means of quantifying the difference between the same name and content. In order to reduce conflict and inconsistency, only designated person can be allowed to update, change the requirements Specification document, and personnel for storage and release.

Then the third chapter, "Management Change Request".

Management changes are called anomalies compared to other areas of work, are considered emergencies, need to have a corresponding contingency solution to be controlled and handled in a timely manner, so do not treat requirements change as a normal. All requirements changes must follow the process, and if a change requirement is not adopted, then the process will not be considered.

Finally, the fourth chapter, "Demand tracking ability".

The goal of the requirements tracking activity is to integrate the requirements business activities and software development activities through the demand capability matrix, and establish an association relationship table that can be traced from the source to the terminal or from the terminal back to the source.

Talk about individual understanding of demand management.

As this semester of a system is required to meet the needs of multiple changes to complete, for the revision of the requirements of the management is very important, first of all to distinguish which version of this is to do which version, or do it is also white to do, because the user's needs have changed. Therefore, the management of demand is also very important.

"Ten Steps to software Requirements" read Note five