It took a day to sort out the required engineering methods. The implementation difficulty and effect of these methods are classified.
For your reference and discussion
High Impact and high difficulty
- Define the requirement development process
- Plan based on requirements
- Rediscuss project commitment
High difficulty is affecting
- Training user groups and managers on demand
- Build models for requirements
- Manage demand risks
- Use requirement management tools
- Create a requirement tracking capability matrix
- Hold a demand acquisition Seminar
High difficulty, low impact
- Reuse requirements
- Application quality function allocation
- Measure requirement Stability
High Impact in difficulty
- Confirm use case
- Specify quality attributes
- Determine demand priority
- Use SRS Template
- Define change control process
- Establish CCB
- Review Requirement documents
- Allocate requests to subsystems
- Record business rules
The difficulty is being affected.
- Training Demand Analyst
- Select User Spokesperson
- Build core teams
- Create a prototype
- Define conformity criteria
- Conduct Change Impact Analysis
- Select a proper development cycle
Low impact in difficulty
- Maintain requirement change history
- Tracking workload in input demand Projects
Low difficulty, high impact
- Develop developers in the application field
- Define project prospects and scope
- User Group category
- Draw Association Diagram
- Determine demand Source
- Create requirement baseline and control version
Low difficulty is affecting
- Analysis feasibility
- Create a glossary
- Compile a data dictionary
- Observe the process of user execution
- Determine System Events and responses
- Add a unique label for each requirement
- Test requirements
- Tracking requirement status
- Review past experiences and lessons learned
Low difficulty, low impact
References: Version 2 of software requirements -- Karl E. wiegers translated by Liu weiqin Liu Hongtao
