Software Improvement/Trouble Report Checklist / PAGE / 2 / Of / 3
ITEM / REQUIREMENT / AD / NI / UN / REMARKS
1
2
3
4 / GENERATE/DESCRIBE SOFTWARE IMPROVEMENT/SOFTWARE TROUBLE REPORT (SI/STR):
Request from Customer, Request for Engineering Services (RES), PTR,
Trouble is found, Improvement is required, etc. is adressed ?
Request for Improvement/Trouble is allocated to Software ?
SI/STR was filled-in in the Database ?
1. Project Number
2. Title
3. Eng. Summary
4. Event
5. Change Type
6. Usage
7. Responsible System
Change/Trouble Description was filled-in in the Database ?
1. Reference to system specification requirement.
2. System condition during trouble, including test set-up.
3. Description of procedure that led to the trouble
4. a. Description of normal/optimum performance (trouble),
b. Description of modified/new performance (improvement).
5
6
7 / LOCATE IMPROVEMENT/TROUBLE IN PRODUCT SOFTWARE
Impacts were identified as per SI/STR Impact Analysis Check-List ?
SI/STR was filled-in in the Database ?
1. CSCI
2. Version
3. Reference Document, if any
4. Project Leader
5. Cause
Change/Trouble Description was updated as required ?
1. Reference to CSCI software specification.
2. a) Description of faulty performance.
b) Description of modified/new performance.
7
8
9
10
11
12
13
14 / OPEN SI/STR AT SCCB
SI/STR are ready for reviewed ?
SI/STR wase analyzed by the SCCB ?
The course of action (no action, action STR, delay decision on STR, etc.) was decided by the SCCB ?
The class of the SI/STR was determined by SCCB ?
STR was approved by the SCCB ?
Impact Analysis Check-List, the Effort Log and the SI/STR form was filed in the SI/STR folder ?
SI/STR is distributed by CM to the software representative ?
SI/STR form was filled-in in the Database by CM ?
1. Category
2. Priority (Criticality as per SI-STR User’s Guide)
3. Target event.
4. Incorporation (i.e. version to be included).
5. CM is signed the Approval of the SI/STR.
6. CM filled the Class field.
[DELAY DECISION ON str, ETC.)reviewed ?
Trouble/Improvement investigation is performed ?
Software specifications are redlined ?
SI/STR database are filled-in ?
1. Responsible software (software engineer for the requirements).
Proposed Disposition is filled-in (all as a software requirement) ?
- Plain text - Diagrams
- Flow Charts - Equations
- Reference to other documents

LEGEND: AD = ADEQUATE NI = NEEDS IMPROVEMENT UN = UNSATISFACTORY