Requirements Management Processes
From Requirements Management School
In order to ensure that you have a robust requirements management process in place you need to have the following well considered processes/procedures in place:
Contents |
Requirements Management Process
Definition:
The Requirements Management process is a function within requirements engineering. The role of the requirements management process is to oversee the development process through to delivery and operation of the product to ensure that the baseline is what is delivered to the customer in a timely and cost effective manner.
Key attributes for a robust process:
- Robust change control process.
- Organized documentation and version control.
- Requirements status tracking.
- Requirements tracing.
Change Control Procedure
Definition:
The process that regulates any changes required to the requirements once the baseline is agreed.
Key attributes for a robust process:
- Recording and monitoring of the requests.
- Assessment of the requests.
- Transparent authorization mechanism.
- Scheduling of any changes agreed.
- Clear communication of requests status at all stages of the process.
Requirements Status Tracking Procedure
Definition:
The requirements status tracking process enables the monitoring of requirements from various angles; those completed; those outstanding; those being worked on; those currently not being worked on; which requirements are assigned to whom for completion; and a whole variety of other information that is vital to the monitoring of the project.
Key attributes for a robust process:
- Attributes clearly defined.
- Attributes created and communicated.
- Attributes updated regularly by all stakeholders, as needed.
- Attributes monitored, action taken due to the monitoring.
Change Control Board Charter
Definition:
The change control board charter is a document that lays out the process that with govern the change control process. It is defined and agreed prior to the baseline being set.
Key attributes for a robust process:
- Clearly defined purpose.
- Clearly defined scope of authority.
- Transparent set of procedures for the change control process.
- Transparent set of procedures for the decision making process.
- Formal communication plan.
Requirements Change Impact Analysis Procedure
Definition:
The requirements change impact analysis procedure clearly defines the review and analysis process that has to take place when any change request is being considered for approval. This is defined by way of checklists and/or templates to ensure that there is consistency of approach.
Key attributes for a robust process:
- Process to define the extent of the change.
- Process to identify all tasks that will need to be undertaken to implement the change.
- Process to that identifies the resources needed to implement the change.
- Comprehensive documentation that captures the outcome of each process.
Requirements Traceability Procedure
Definition:
The requirements traceability procedure ensures that all requirements can be traced back to their source as well as forward to the functionality that is delivered. This ensures that all agreed requirements are delivered and that no unnecessary development is carried out.
Key attributes for a robust process:
- Efficient system for capturing the data required for bidirectional traceability. Data from the following source documentation should be considered:
- Use cases
- The architectural/design document
- The SRS
- Software modules
- Test cases
- Verification document
- Cross functional cooperation to regularly update the data by all stakeholders.
