Managing change requirements
With Change Management for DOORS, you can manage requirement changes, such as:
- Submitting RCRs.
- Selecting a default RCR on which to work.
- Proposing changes to requirements.
- Having the requirements automatically associated with the default RCR.
- Reviewing RCRs.
- Applying RCRs.
Requirements change management using Change Management for DOORS is centered around an RCR. The request contains a description of the change and other associated information such as priority, product name, reviewer comments, and the user name of the person assigned to make the requirement changes. This CR is assigned to a single requirement engineer, who then uses DOORS to propose changes to one or more requirements.
Proposed changes are automatically associated with the RCR that the engineer is currently working on. After the requirement engineer completes the CR, it is reviewed by one or more people. If the CR is approved, the proposed changes can be applied to the DOORS document.
You can also choose to use the system CR lifecycle that is included with Change Management for DOORS to manage your requirements changes. The system CR lifecycle is designed for users to submit requests for changes they want made to a system. The system CR is then broken down into one or more RCRs, and potentially into one or more implementation requests (IRs).
- Adding one or more objects in any structure.
- Modifying objects.
- Adding or removing outgoing links to an object.
- Deleting objects or object hierarchies.
- Relocating objects within a module.
To enforce that all changes made to a module are associated with an RCR, Change Management for DOORS requires that the user select a default RCR whenever a module is opened for editing.
The following sections contain information about using Change Management for DOORS operations: