"Software Requirements Engineering" read NOTE I

The book simply defines the requirement as a requirement that defines what the system needs to do rather than how it is done.

Requirements also have some principles, 1) define the problem rather than the solution, 2) define the system instead of the project, 3) distinguish between formal and informal parts, 4) avoid duplication. In the process of several requirements, we understand that each requirement process has its own advantages and disadvantages, the traditional requirements process is more orderly, so that the project needs analysis of the organization, the agile requirements process can be more clearly to obtain the demand, the limit requirements process using user stories can be arranged in the order of specific implementation, The incremental demand process is between the traditional requirements process and the limit requirements process, keeping everyone in the same understanding and avoiding duplication.

The book also introduced the requirements specification, see Requirements Specification content, feeling demand analysis is really not like that simple, but also see the importance of the requirements specification, ① easy for users, developers to understand and communicate. ② reflects the structure of user problem, which can be used as the basis and basis of software development work. ③ as the basis for confirming testing and acceptance.

In demand analysis, the demand pattern is crucial, the benefits of Demand mode: 1. Demand mode provides guidance, 2. Demand mode saves time, 3, demand mode promotes consistency of the same type of demand.

Demand patterns need to describe when to use patterns and how to write requirements based on patterns. The requirements model includes these elements: basic details, applicability, discussion, content, templates, examples, additional requirements, development considerations, test considerations.

The basic details are used to describe some of the short things in the pattern.

The applicability section describes how the demand pattern is used. It should be clear and accurate.

The discussion describes how to write this requirement, which explains everything, as long as it can help define this type of requirement.

The content details the information about which entries must be communicated by this type of requirement.

The purpose of the requirements template is to replicate it as a starting point for the requirements description.

Example: Each requirement pattern contains at least one instance that demonstrates how to use patterns in practice.

Additional requirements explain what additional requirements to consider and under what circumstances to consider.

Development considerations are designed to help design and implement software developers to meet this type of requirement.

Test considerations can explain how to test this type of requirement.

There is a link between the demand patterns and not the independent existence. We should learn to use the appropriate demand model, and understand the relationship between the establishment of patterns, so as to make the needs analysis more clear and accurate.

"Software Requirements Engineering" read NOTE I