Work problem set related to software requirements (2)

1. Why does demand management involve?

Requirement management is the scope management of IT projects, and requirement management is the source of the entire IT project. It project estimation, planning, and subsequent tracking control, verification and validation are all closely related to requirements. Therefore, in order to ensure the smooth implementation of the project progress, quality, and cost objectives, ensure the seriousness and enforceability of the project plan, and ensure that the final product developed by the software system is exactly what the customer expects, demand management must be done well.

Demand management should be a full-Lifecycle Requirement management. From the proposal of users' original requirements to the final formation of software products, the user verifies the demand implementation to form a closed-loop process. Therefore, we need to track and understand the evolution of the demand status. The software life cycle model of a large project is complex. The implementation of a requirement is subject to user requirements, software requirements, overall design, detailed design, development and unit testing, and integration testing, system testing and acceptance testing are performed in multiple phases. In this process, a requirement tracking is required to confirm the consistency of work products generated in the requirement and intermediate stages. In addition, change management is another focus of demand management, and requirements need to be baseline and controlled after review and confirmation, when there is a demand change, the corresponding demand impact analysis must be performed to confirm the handling method of the demand change. When the workload of the change is greatly affected, adjustments should be made and the baseline project plan should be reactivated.

The entire requirement investigation, analysis, and requirement development process also needs to be managed during review and confirmation. One of the key points in this process is to get the user's requirement output documents, and the joint confirmation and commitment from the project team design and developers.

2. What is the significance of demand change management? Specific content

The user constantly submits request modifications, and the project progress is not guaranteed to be extended. A change to the requirement leads to various unexpected errors and exceptions in the originally stable system; these are the symptoms of defects in requirement management. The importance of demand management is embodied in the seriousness and enforceability of the project plan to ensure the realization of the project objectives. After the requirement change management is introduced, the software requirement document becomes a document that everyone undertakes and serves as a reference. This document needs to be designed, developed, test and other roles are fully transferred and shared. In addition, through demand management, everyone is aware of the impact of changes on the project and the cost of changes, in turn to promote the improvement of demand development quality.

The demand change management includes the proposal of change requests. The CBB Committee conducts an impact analysis on the requirements to determine whether a change is required. The design and Development Director confirms the modules and codes that the change will affect and the specific modification methods, the developer modifies and tests the changes, and finally the change requestor verifies the requirements for the changes. The impact analysis of changes generally needs to be carried out by the project team's Development Director. Large projects can be analyzed based on the requirement tracking established in demand management, however, tracking based on actual needs does not play a significant role in impact analysis.

3. Does the requirement need to be documented? What does it mean?

SRS requirement document is the most important document in the entire software development process. Regardless of the project size, personal opinions are related to Requirement documents. This document is the basis for multi-party communication between users, project managers, requirements, design and development personnel, so that everyone can have a consistent understanding of the requirements and carry out the work in accordance with this document. For agile software development, we also need to describe the use case scenario and document CRC cards to facilitate communication.

Once again, we emphasize that communication, especially face-to-face communication, is the most efficient way of information transmission. However, when a piece of information needs to be in different stages of the entire lifecycle of software development, when different roles are used for multiple times, they must be documented. The requirement document exactly belongs to this type.

4. Where do small and medium software development teams focus on demand development and management?

Small and Medium-Sized Project Teams must use lightweight methodologies and processes to achieve the target service. The purpose of the process is to solve the current problems and possible problems. In a process that is not in this scope, rules or work will not produce value and meaning.

For small and medium teams, first of all, they should be aware of the importance of the demand work, formulate the requirement documents and demo interface specifications, and document and structure the requirements. Second, the requirements for development must be reviewed and approved by users, implementers, and testers. Finally, after the requirement is documented, the artifacts need to be managed through various configuration management tools. After the requirement is completed, the artifacts should be archived and controlled in a timely manner. Changes to the requirement must be managed rather than randomly.

5. How to evaluate the priority of a requirement?

The purpose of demand priority is to enhance project management and user satisfaction. After a system is launched, it often occurs that the commonly used functions are concentrated on 20% of the functions, and many functions are rarely used. The demand priority allows us to better grasp the key points and allocate resources, and truly refine the 20% most important requirements and frequently used demands, only in this way can we truly improve user satisfaction and achieve the project goal.

The demand priority usually gives users the most say, but when a system involves multiple business departments and organizational structures, it is inevitable that all users will view the priority and urgency of requirements from their own standpoint. However, the contribution and effect of a demand on efficiency improvement, cost reduction, and cycle reduction are not measured. Therefore, the concept of value engineering should be considered for the evaluation of the demand priority. The priority of a demand should be reflected in the value generated and the cost saved after the demand is realized.