Requirements engineering is a very broad concept, and all activities directly related to requirements are collectively called requirements engineering. The activities involved in requirements engineering involve two categories : requirements development and requirements management , as shown in the figure below.
Each of these items in the above picture can be talked for several hours, and it is simple to deal with, and summarized in one sentence, as follows:
Requirements elicitation is the process of determining and understanding the needs and limitations of different user classes, and is the first step in building a bridge between the problem and its final solution.
Requirements analysis refers to all the work done when determining the purpose, scope, definition and function of the target work. Research in recent years believes that demand analysis is the most critical part of the entire demand process.
The requirements specification is the solution provided by the solution system to meet the needs of users, and specifies the behavioral characteristics of the system.
Requirements verification is mainly to determine: 1. The requirements specification correctly describes the expected system behavior and characteristics; 2. The requirements are complete and high-quality; 3. All views on the requirements are consistent; 4. Current Demand work provides a sufficient foundation for continuing product design, construction and testing. Requirement verification is mainly manifested as inspection (inspection) . The main tasks of change
management (requirement management of change, RMOC) include: 1. Analyze the necessity and rationality of the change, determine whether to implement the change; 2. Record the change information, and implement the change approval control ; 3. Modify the corresponding software configuration items (baseline) and establish a new version; 4. Release the new version after review.
Revision control is a software engineering technique to ensure that the same files edited by different people are updated during the development process. The point of version control is to formulate version control rules and strictly enforce them.
Demand trackingRequirements traceability refers to the entire process of tracing a requirement's lifespan. Requirements tracing provides us with the ability to clearly refer to the entire process range from requirements to product realization. There are two ways of demand tracking: 1. Forward tracking. Check whether each requirement in the "Product Requirements Specification" can be found in the subsequent work results. 2. Reverse tracking. Check whether the work results such as design documents, codes, test cases, etc. can be found in the "Product Requirements Specification". Forward tracking and reverse tracking are collectively referred to as "two-way tracking". Regardless of the tracking method adopted, a demand tracking matrix must be established and maintained. The demand tracking matrix saves the correspondence between demands and subsequent work results.
Requirements status (requirements status) in software engineering is a perspective of requirements tracking, which shows the status of requirements completion in a macroscopic view. The requirements here can be user requirements or system requirements. Change according to specific circumstances.
Reprinted from https://baijiahao.baidu.com/s?id=1626220059267621308&wfr=spider&for=pc