The five major processes of project requirements management
1. Requirements acquisition,
writing project view
, scope document
, user group classification,
selecting user representatives,
establishing a core team,
determining use cases,
holding a joint meeting,
analyzing user workflow,
determining quality attributes,
checking problem reports ,
and reusing requirements .
2. Requirements analysis
1. Draw an association diagram, which is used to define a simple model of the boundary and interface between the system and the external entities of the system;
2. Create a development prototype. When developers or users cannot clarify certain requirements, develop a system prototype, which makes many concepts
and possibilities What happened is more intuitive and clear;
3. Analyze the feasibility, analyze the feasibility of implementing each requirement under the allowable cost and performance requirements, and clarify the risks
associated , including conflicts with other requirements, Involves the balance of interests of various users, dependence on external factors and technical obstacles;
4. Determine the priority of requirements: analyze methods to determine the priority of implementation of use cases, system characteristics or individual requirements, and determine the product version based on the priority. Which features or types of requirements are included;
5. Establishing models for requirements, and establishing graphical analysis models for requirements is an excellent supplementary description of software requirements specifications, which can model system requirements from multiple angles; 6. Write
data dictionaries, create Data dictionary The data dictionary is the definition of all data items and structures used by the system to ensure that developers use a unified data definition; 7.
Application quality function allocation, linking system features and attributes with the importance to customers, providing An analysis method was developed to determine which features are of most concern to customers.
3. Write requirements specification
1. Adopt a template. In your organization, define a standard template for writing software requirements specifications and other documents. This template provides a unified structure for recording system requirements and various other important information related to requirements; 2.
Specify Demand source, demand traceability matrix
3. Mark each demand with a label for the traceability and modifiability of demand quality standards 4.
Record business specifications, which refers to the operating principles of the system and independent business specification documents
Theoretical Basis of Needs:
Business Requirements (Business Value: Business Objectives and Business Processes: High Level Requirements)
- project view
- scope document
User needs (what users expect and what value and functionality to provide)
-
Instance Documents: Arranging and Considering the Method of Instanced Requirements
-
Scenario script
Functional requirements (a list of functions and features required by the software or system)
Technical requirements
Software project view (comparison of competing products) and scope (some performance not included) - requirements analysis
https://blog.csdn.net/xiaoniba1024/article/details/7186324
https://www.docin.com/p -2480120945.html
Software Architecture View—4+1 View Mode
https://www.cnblogs.com/PatrickLiu/p/6214857.html