III.15.1 Identify requirements modifications that will be visible to the end users of the product/system.
Intent: The intent of this task is to establish specific requirements for changes requested by either internal or external customers.
Mechanics: If the project has implemented formal SCM procedures, the tasks defined the umbrella task, Software Configuration Management, are implemented. Product enhancement 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 program architectural design and the procedural design associated with each program component. Changes in the interface design must also be considered.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Is the enhancement request bounded? Stated unambiguously?
2. Has the potential impact of the enhancement been considered? Internal to the application? to interoperable applications?
3. Have all SCM controls 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
Do: Be certain to determine the impact of the change (see Task III.17).
Don't Assume that an enhancement can be implemented without side effects.
Deliverables: Software Change Request describing the enhancement
III.15.2 Isolate differences in enhancement requirements if request comes from multiple customers or if enhancement is intended for different product lines.
Intent: The intent of this task is to identify individual customer requirements that may cause some modification to the product as delivered to specific customer sites or for different product lines. The primary focus is on the customer use of the product, specialized needs, and differences in target environment.
Mechanics: Meeting are conducted with individual customers to determine local requirements. Once requirements are known, they are evaluated for impact on the product and negotiated, if impact is high.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
Do's & Don'ts
Deliverables: list of requirements for each customer or product line
III.15.3 Perform SCM functions.
Intent: The intent of this task is to evaluate the impact of the enhancement and approve or reject it.
Mechanics: See Tasks U.4, defined in Chapter 5.
Application of Formal Methods: SCM procedures
Application of CASE Tools: SCM tools
Deliverables: Engineering change order
III.15.4 Define final enhancement requirements.
Intent: The intent of this task is to define the final set of requirements that will comprise the product/system enhancement.
Mechanics: When necessary, enhancement requirements are modeled using software engineering analysis methods (see also, Task III.18). In many cases however, enhancement 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 enhancement is implemented.
Don't: Focus solely on the functions to be modified. Consider also the data and the behavior of the system.
Deliverables: Product enhancement specification and/or Engineering change order
Use Browser "back" arrow or return to APM Process Design Language Description
