Consider the requirement management plan from the perspective of CMM

Throughout the CMM activities of the requirements, the overwhelming majority of KPA need to start from the plan (planning), the general step requirements from the preparation-planning---the implementation of activities---maintenance process---improvement process, such as the major categories, such as configuration management, quality assurance, project planning, sub-contract management and so on. The requirements management of CMM does not require a definite plan, but before the operation of the project team in order to ensure the smooth implementation of the requirements of the project, to ensure that the needs of the activities in an orderly manner, will be a rough or detailed plan for a demand, the plan customization, will directly affect the overall development of the effectiveness of the project, affect the accuracy of the custom requirements baseline. We will consider how the program is customized from this perspective after we understand the activities required by the CMM requirements management kpa.

First of all, the document of the activity plan, we know, a plan the most effective way to operate is to document, in black and white left our planned activities, participants, operational content, achieve goals, etc., so that the future operation of the organic, there is "a written organization management strategy", This is the first part of the CMM requirements management process to implement the agreement. In this writing, it contains the common characteristics of all the five KPA activities that need to be executed in our requirements management process, execution capability, execution activity, analysis process, and validation implementation results. In accordance with KPA requirements of the cmm-requirements management process, we develop the following requirements management Plan template, the role of the template is based on the requirements of the common, create a common, can guide people to think in this way, can be applied to most of the basic requirements of similar operations documents.

Requirements Management Plan Template

1. Confirm

1 The scope of the application of this template, to achieve the goal

2 responsibilities of the project manager in this activity, and the responsibilities of the project team members

3 Define the responsibilities of the client to participate in the demand research activities (decision making, required activities, resources required, etc.)

4 Confirmation of user-given requirements of documents (such as agreements, conditions and contract terms, such as products to be delivered, date and milestone requirements, etc.), functional requirements, technical requirements, etc. (see CMM Requirements Management Execution Capacity 2)

2. Overview of Demand activities

2.1 Methods of Demand survey

Decide what way to conduct demand research, that is, to determine the methods of information collection and analysis (such as the way to communicate with customers, the forms used for communication, the project group Business Process Analysis form, etc.).

2.2 Demand activity requirements

1 collect the relevant technical requirements, request to collect the required function points, constraints and processing processes, etc.

2) Collect the user's special needs

3 analysis of the user's original business or workflow

4 analysis of the required system business processes to establish system scope and objectives

5 require the use of "CMM Requirements Specification template" as a requirement statement document

2.3 Demand Cycle planning

To develop a time schedule for this demand activity and the content to be completed in each phase.

3. Demand Review Plan

1) Determine the requirements of the Panel members and members

2) to determine the requirements of the evaluation method

3) Determine the requirements review content

4, the Demand acceptance method

1) Determine the acceptance method

2) Determine the acceptance record form

5. Requirements Change Management

6. Project organization and Resources

The plan template synthesizes several features of CMM requirements management requirements, and the operation of the specific project teams is based on the needs of their actual projects.

Second, the implementation process of demand activities, according to the proposed requirements management plan to carry out the actual needs of the project research activities, in the activities recorded with the customer Exchange content, record the various stages of change, change reasons, in accordance with the written strategy of the two sides of the activities of the constraints.

The overall activity chart is as follows:

In this process, the demand collection, analysis, documentation is the main activity, should distinguish the customer needs can be divided into business needs, functional requirements, interface requirements, performance requirements and special needs, etc., in the collection of the requirements of the type of classification. Analysis, that is, to distinguish between the category of requirements, but also to pay attention to the relationship between, because these will affect the entire system design and implementation.

After the required activities are completed as planned, we require that the analytical documentation generated in the process, the collected resources, be consolidated into a "Software requirements Specification" that can be confirmed by the customer, and that the requirements of the CMM are required, and that this specification will also serve as a basis for our determination of requirements baselines, and the CMM's original system requirements specification Some items are too complicated, we do not require all, just according to the actual situation and requirements of the project, the template-type requirements description.

Re-demand review plan and acceptance plan when developing the requirements management plan, review is required before acceptance of the operation, the purpose is to superior management department can properly and timely grasp the software process activities, and before the customer acceptance of the dispute to resolve the issue, to ensure that the final acceptance of the customer needs are complete and appropriate. The review program requires reviewers to undergo a certain amount of training, including the methods, standards and procedures used in the project, application domain knowledge (cmm-requirements management Process Execution capacity 4), and requirements review (see cmm-Requirements Management Process Execution Activity 2).

Acceptance plan is a prior agreement with the customer to carry out the acceptance of the way, the acceptance of the required delivery of the workpiece, and so on, the design of demand acceptance (confirmation) table.

Final requirements change operations cmm-requirements Management Process Execution Activity 3 describes some activities for the requirements change process, including necessary changes to related activities that are caused by the change. Instead, we use the action that can be applied to change activities throughout the project:

"Propose change → change assessment → change item audit → change approval → implement change", in the project operation, according to the size and impact of changes, to carry out the actual implementation process. But the requirement is to change the final centralization of the personnel must be the project manager, only the project manager in a coordinated change control, in order to make changes in the project is controlled, is unified, of course, this is based on the requirements of different enterprise projects to actually operate.