Requirements Management Process.

Overview

The purpose of Requirements Management process is to establish a common understanding between the acquirer and the system projects of the acquirer’s requirements that will be addressed by the program and projects.

Requirements Management involves establishing and maintaining an agreement with the acquirer on the requirements for the specific project.  This agreement is referred to as the “system requirements allocated to the software or hardware”.  The agreement shall cover both the technical and non-technical (e.g., delivery dates) requirements.

Projects shall:

1.      Control system requirements allocated to establish a baseline for engineering and management use;

2.      Keep software plans, products, and activities consistent with the system requirements allocated;

3.      Establish responsibility for analysing the system requirements and allocating them to hardware, software, and other system components;

4.      Document the allocated requirements;

5.      Provide adequate resources and funding for managing the allocated requirements;

6.      Train members of the engineering group and other related groups to perform their requirements management activities;

7.      Conduct reviews by the engineering group of the allocated requirements before they are incorporated into the development project;

8.      Use the allocated requirements as the basis for software/hardware development plans, work products, and activities;

9.      Review changes to the allocated requirements and incorporate into the software/hardware project;

10. Make and use measurements to determine the status of the activities for managing the allocated requirements;

11. Review the activities for managing the allocated requirements with senior management on a periodic basis;

12. Review the activities for managing the allocated requirements with the project manager on both a periodic and event-driven basis;

13. Conduct reviews or audits by the quality assurance group on the activities and work products for managing the allocated requirements and reports the results.

 

Programme/Project Managers shall be responsible for implementing this policy.

 

SEMG shall be responsible for the Management policy and will be responsible for the preparation of all the required management processes required to harmonize the development of systems and comprising hardware and software components across the program.

The purpose of the Requirements Management Process” is to satisfy the SW Management Policy as defined in the “Organizational Program Management Plan/Process” for the software projects.  This process will comply with ISO/IEC 15288, ISO/IEC 12207/ MIL-STD-498, and the SEI/CMM “Best Practices”.

 




Back to Home page MANAGING STANDARDS Home page

Please send any beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk

Copyright © Ken Rigby 1996, 1997, 1998, 1999, 2000, 2001, 2002