After studying the course of "Software Requirements" for about a month, the software requirements I understand are what the users want to have in the software, and the requirements analysts analyze and sort out which requirements of the users can be realized and which cannot be realized. of. Recently, I read the book "Ten Steps to Software Requirements", which gives the definition of software requirements. The IEEE Software Standard Vocabulary (1997) defines traditional software requirements as: (1) Users need to solve problems or achieve goals. (2) a condition or capability required for a system or system component to satisfy a contract, standard, specification or other formally specified document; (3) a condition or capability that reflects the conditions described in (1) or (2) above or documentation for the capability. In addition, the book also gives the definitions of software requirements given by several other senior workers, so I will not list them one by one here. However, although their expressions are not the same, they all point out that software requirements should include descriptions of user needs, system functions, performance, and constraints.
In the development of a system or software, I used to think that the realization of functions accounted for the majority, and technical personnel should be a more important role in a team. Therefore, in the previous study, I paid more attention to my coding ability. However, through learning After reading "Software Requirements" and reading related books, I realized that software requirements are the important part, and the success of a system or software depends on the accuracy of the requirements. And what needs to be distinguished is that software engineering and requirements engineering are two relatively independent and interrelated projects. Software engineering is based on requirements engineering, the product of requirements engineering is software requirements, and software requirements are the link between requirements engineering and software engineering. . It is also important to distinguish between software engineering and requirements engineering and to understand the connection between them.
The book gives the definition of a new generation of software requirements as: (1) From the top-level and global perspective, analyze and describe the business in a comprehensive and detailed manner starting from the problem and goal; (2) On the basis of business analysis, the information is analyzed and described. The macro design of the system is also incorporated into the analysis and describes the relationship between the business and the information system; (3) the conditions or capabilities required by users to solve problems or achieve goals; (4) the system or system components must meet contracts, standards, specifications or Others formally specify the conditions or capabilities that the document needs to have; (5) a document specification that reflects the conditions or capabilities described in Section 4 above. The new generation of software requirements more comprehensively takes care of all stakeholders in the software development process than before.
In my opinion, a successful project largely depends on a good software requirements team, and a good requirements analyst basically needs to ensure that the software requirements can meet the following characteristics:
(1) Integrity: Each software requirement must clearly describe the functions that need to be implemented, because even if 99.9% of the requirements are correct, only 0.1% of the errors may cause major mistakes and lead to the failure of the project.
(2) Correctness: Each software requirement must accurately describe its development function.
(3) Primary: The work of business analysis is the first important work of software requirements.
(4) Precedence: the information system will be included in the software requirements
(5) Feasibility:
(6) Necessity:
(7) Hierarchical:
(8) Unambiguous:
(9) Verifiability: