| Task: Update and Maintain Software Requirements |
|
 |
| This task establishes traceability from the Use-Case block properties to the relevant requirements. |
|
Purpose
| To establish the traceability to support coverage, completeness and impact analysis. |
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
| Outputs |
|
Main Description
| This task maintains the software requirements. Some of these may be directly allocated from a system requirement. Others
may require derivation and elaboration from system requirements and update based on other forms of requirements analysis
including use case analysis. In addition, this task establishes traceability among the system requirements, software
requirements, and software user cases. This traceability information is used for review, impact, coverage, and completeness
analysis. |
Steps
|
Identify requirements that are applicable to the subject use case
| Review the requirements specification and the traceability record to identify the functional and non-functional
requirements that apply to the subject use case. This information should be available in the Traceability Record as a
result of previous work done detailing the requirements. |
Establish traceability from the relevant use-case block properties to the system requirements
| Based upon the requirements that are relevant to the subject use case, create <<satisfies>> links from each of
the subject use-case block operations and attributes to the associated functional and non-functional
requirements, respectively. |
Copy system requirements allocated to software
| Some system requirements map directly to singular software requirements. These may be copied or referenced from the system
requirements specification directly. |
Derive and elaborate system requirements to software
| Some system requirements map to multiple software requirements or to combinations of software and hardware. These must be
decomposed into derived and elaborated requirements at the software level. |
Add requirements identified due to furthre requirements analysis
| Missing, incorrect, inaccurate, or inconsistent requirements are often identified after systems engineering. This step
identifies and addresses those requirements. This may result in change requests levied against the system requirements. |
|
More Information
© Copyright IBM Corp. 1987, 2010. All Rights Reserved.
|
|
