[Project Management] requirement management of project management

I. Definition of requirement Management

Requirement management is a systematic method for finding, recording, organizing, and tracking system demand changes.

Requirements can be defined as conditions or functions that must be met by the system.

Requirement management can be defined as: requirement management is a systematic method that can be used to obtain, organize, and record system requirements, and ensure that customers and project teams reach and maintain consensus on system change requirements.

The key to effective requirement management lies in the explicit elaboration of maintenance requirements, the attributes applicable to each requirement type, and traceability between other requirements and other project artifacts.

 

II. Scope of demand management

Requirements can generally be divided into the following requirements:

No.	Requirement type	Example
1	Time requirements	Requirement for project progress and completion period
2	Quality requirements	Requirement on defect rate.
3	Functional requirements	Requirements on product functions
4	Performance Requirements	Requirements on product performance, such as computing speed.
5	Management requirements	Management requirements for the production process, such as requirements for the processes used.
6	Other requirements	Omitted

 

Iii. Classification of requirements 1. Based on the stages proposed by the customer:

Initial requirements: includes original requirements raised by the customer and requirements developed based on the customer's original needs, such as style books.

Demand change: increase, change, and decrease of demand.

For maintenance projects (the project work corresponds to the various requirements of the customer), it can be considered that the requirements are changed without initial requirements.

2. According to the proposed form:

SRS: Software request Specification

Product Model Book: Specific Requirements

Requirements raised by other methods such as mail, telephone, and teleconference

 

Iv. Demand management activities

Demand management activities include requirement Management Plan, requirement record, requirement analysis, requirement confirmation, requirement commitment, requirement implementation, requirement traceability, measurement and analysis.

 

1. Demand Management Plan

When a project plan is formulated after the project is established, the project requirement Management Plan (included in the Project Plan) is formulated. The main content of the plan is as follows:

1) personnel and responsibilities

The project owner's requirements on acceptance, record, analysis, confirmation, and implementation of required personnel.

You can leave the Specific Name of the person without specifying the relevant personnel's requirements.

2) requirement management methods and templates

Requirement tracing method: naming rules/Development Manual

Requirement management method: What template/method is used to manage requirements

Requirement validation retention method: how to retain the Validation Record.

3) requirements commitment rules

A project can define requirements commitment rules to define how the Group promises.

2. Requirement record

Record management requirements. Record the requirement to the requirement management template.

3. Demand Analysis

Analyze the requirements in the following aspects:

1) technical impact degree: whether the requirement can be implemented, and whether the requirement has any impact on other requirements after implementation.

2) Workload estimation: whether the resources are sufficient and whether the plan needs to be adjusted to meet the requirement.

3) understanding and consistency of the requirement content: Is the requirement content fully understandable? Is there any ambiguity that needs to be confirmed with the customer?

 

When accepting a requirement, you can check whether the requirement is accepted from the following points.

1) whether the requirement description is clear and complete.

2) whether the requirements are consistent and there is no conflict.

3) whether the requirement is verifiable (testable.

4) whether the requirements are appropriate and can be fulfilled.

5) whether the demand can be fulfilled (taking into account factors such as technology, resources, time, and quality)

 

Generally, a specific requirement must be analyzed in detail in the following situations.

1) The need to use new technologies that have not been used before

2) there is a large scope of demand changes, involving modifications to multiple modules and different functions.

3) requirement implementation is a change to a certain underlying module.

4) requirement implementation will change the interface

5) the corresponding project in the market. If the requirement for a common function is changed

 

The analysis can be performed in the following aspects:

1) describe the functions and modules that may be affected

2) Describe the side effect that may be generated after the requirement is implemented

3) Describe countermeasures, such as re-testing a function after the requirement is implemented.

4) whether or not the corresponding market project needs to be expanded in other types

4. Confirm requirements

Key steps for confirmation.

Submit the requirement analysis results to the project owner for review. If the review fails, the results are analyzed and confirmed or directly canceled.

After the review is passed, confirm the analysis results with the customer to eliminate obvious errors and differences.

Retained validation records and results.

5. Requirement commitment

Submit the requirement validation results to the project owner for recognition.

Adjust the project plan according to the confirmation result as needed.

Project participants make a commitment to the implementation of requirements.

6. Demand implementation

Demand implementation refers to exporting and analyzing customer, product, or product component requirements.

7. Requirement Traceability

The purpose of requirement tracing.

1) establish and maintain traceability between products from demand-design-implementation-test patterns, traceability of requirements to plans, that is, Vertical traceability.

2) Establish and maintain Horizontal traceability. Such as the relationship and impact between different modules, functions, and interfaces.

 

Requirement traceability classification.

1) Vertical traceability:

A. Define <demand traceability document> to clearly describe the traceability relationship of requirements in the project. The requirement traceability must be at the functional point.

B. the traceability relationship between requirements and plans must be clear, that is, the relationship between requirements and planned task arrangements.

2) Horizontal traceability:

For example, how to reflect the relationship between two templates in requirements, design documents, code, and test patterns.

You can trace the horizontal relationship between requirements in any of the following ways, or you can trace the horizontal relationship between requirements in any of the following ways, but you must be able to find and have evidence.

A. The relationship between modules can be presented in UML diagrams through design patterns.

B. description in the Development Manual

C. Using naming rules

 

Method of requirement tracing.

1) requirement traceability Matrix

Using the form of tables, you can clearly describe how a requirement corresponds to the corresponding design, code, and test style.

2) Naming rules

Project naming rules can be defined to implement requirements-design-code-test style traceability.

3) development manual

The project can be made into a development manual describing how to modify the implementation of each function to be modified, the design and test cases in the project development. This method is generally suitable for some long-term maintenance projects.

 

8. Measurement and Analysis

The following measurement and analysis data must be collected during project summary:

Total number of demand changes: by category: Demand addition, demand change, and demand deletion.

 

---------------------------------------------------------------------------

GL (arui319)

Http://blog.csdn.net/arui319

Android Application Development solution has been published. Please refer to the following link for more information:

This article can be reproduced, but please keep the above author information. Thank you.

---------------------------------------------------------------------------