IV.22.1 Identify requirements modifications required due to a change request.
Intent: The intent of this task is to establish specific requirements modifications for changes requested by either internal or external customers.
Mechanics: If the project has implemented formal SCM procedures, the tasks defined for the Software Configuration Management umbrella activity are implemented. Maintenance requirements are identified with a Software Change Request and are managed using a change control procedure.
The software engineering team should attempt to identify how changes will impact the data design, the architectural design, the human interface design, and the component-level design.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Is the change request bounded? Stated unambiguously?
2. Has the potential impact of the change been considered? Internal to the application? to interoperable applications?
3. Have all SCM controls (Chapter 5, Tasks U.4) been applied?
Do's & Don'ts
Do: Meet with the change requester to ensure that the specific requirements are unambiguous, consistent and complete.
Do: Be sure that the change requirements are recorded in a Software Change Request (see Chapter 5, Software Configuration Management).
Do: Be certain to determine the impact of the change.
Don't Assume that an maintenance can be implemented without side effects.
Deliverables: Software Change Request describing the change
IV.22.2 Perform SCM functions.
Intent: The intent of this task is to evaluate the impact of the maintenance and approve or reject it.
Mechanics: See the Software Configuration Management umbrella activity
Application of Formal Methods: SCM procedures
Application of CASE Tools: SCM tools
Deliverables: Engineering change order
IV.22.3 Generate engineering change order.
Intent: The intent of this task is to define the final set of requirements that describe the change to be made.
Mechanics: When necessary, maintenance requirements are modeled using software engineering analysis methods (see also, Task III.18). In many cases however, maintenance requirements are defined by listing changes required in the data, functional, and behavioral domain for the software.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Have requirements been reviewed for completeness, consistency, and lack of ambiguity? Has the customer reviewed the final requirements?
2. Have impacts been explicitly noted?
Do's & Don'ts
Do: Be sure that everyone is on the same page; that is, that all changes have been stated in an unambiguous fashion.
Do: Note any constraints that will affect the way that the maintenance is implemented.
Don't: Focus solely on the functions to be modified. Consider also the data and the behavior of the system.
Deliverables: Engineering change order
Use Browser "back" arrow or return to APM Process Design Language Description
