"Requirements Engineering-software modeling and analysis" read Note one

I read through the first part of the book, which focuses on some of the basics of requirements engineering. After reading it, I also learned something.

Below, I have a brief description of my understanding of the fundamentals of demand engineering.

The first step of the demand process needs to be acquired. Demand acquisition is the process of acquiring requirements from people, documents, or the environment. In demand acquisition, a requirement engineer typically needs to perform the following steps:

1, collect background information.

2, define the project foreground and scope.

3. Select the source of the information.

4, select Get method, execute get.

5, record to obtain the result.

Secondly, the second step is demand analysis, its main work is to integrate various information through modeling, so that people better understand the problem. At the same time, demand analysis also defines a collection of requirements for the problem, which can define an effective solution for the problem. Demand analysis also needs to check the requirements of the errors, omissions, inconsistencies and other defects, and to be corrected. Its main tasks are:

1, background analysis.

2, determine the system boundaries.

3, demand modeling.

4, demand refinement.

5, determine the priority level.

6, the demand consultation.

Third, the next step is the requirements specification. Acquisition requirements need to be documented, and the main purpose of writing documents is to communicate requirements information among system stakeholders, so the documentation should be of a certain quality.

Then there is the requirement verification. In order to minimize unnecessary impact on subsequent development activities such as design, implementation, and testing, the requirements defined in the requirements Specification document must accurately and correctly reflect the user's intentions. Therefore, the requirements Specification document must meet at least the following criteria:

Each requirement in the ① document reflects the user's intentions in a more correct and accurate manner.

The requirements set for ② documentation is complete and consistent throughout.

③ the way documents are organized and how they need to be written is readable and modifiable.

In addition, the main tasks in the requirements validation phase include: Performing validation and issue remediation.

Iv. demand management. After the requirements development, design, testing, implementation and other follow-up software system development activities need to work around the needs. The impact of demand runs through the product lifecycle of the software, rather than the mere requirement development phase. Therefore, after the end of demand development, there is also a need for a force to ensure the continuous, stable and effective use of demand, demand management is such a management activity.

Its main tasks include:

1. Establish and maintain a baseline set of requirements.

2, establish the demand tracking information.

3, the change control.

The process of demand development involves the process of learning and cognition, and the process of learning and cognition is progressive, that is, learning a little, adding some cognition, and then continuing to learn on the basis of new cognition. Therefore, demand acquisition and demand and analysis are intertwined, demand engineers need to obtain some information, then analysis and collation, understanding, awareness to a certain extent, and then determine the content to be further acquired.

"Requirements Engineering-software modeling and analysis" read Note one