| Evaluation Criteria | |||||||
|---|---|---|---|---|---|---|---|
| Product | Contains all applic. info in: | Meets SOW, if applic. | Meets CDRL, if applic. | Understandable | Intern. consistent | Follows SW dev plan | Additional Criteria |
| 1. Software development plan (5.1.1) | a. SDP DID | b. | c. | d. | e. | f. (Updates) | g. Covers all activities/deliverables in SOW and CDRL h. Consistent with other project plans i. Presents a sound approach to the development |
| 2. Software Software test plan (5.1.2, 5.1.3) | a. STP DID | b. | c. | d. | e. | f. | g. Covers all software-related qualification activities in the SOW h. Covers all requirements for the items under test i. Consistent with other project plans j. Presents a sound approach to the testing |
| 3. Software installation plan (5.1.4) | a. SIP DID | b. | c. | d. | e. | f. | g. Covers all user site installation activities in the SOW h. Consistent with other project plans i. Presents a sound approach to the installation |
| 4. Software transition plan (5.1.5) | a. STrP DID | b. | c. | d. | e. | f. | g. Covers all transition-related activities in the SOW h. Consistent with other project plans i. Presents a sound approach to the transition |
| 5. Operational concept (5.3.2) | a. OCD DID | b. | c. | d. | e. | f. | g. Feasible |
| 6. System requirements (5.3.3) | a. SSS, IRS DIDs | b. | c. | d. | e. | f. | g. Covers the operational concept h. Feasible i. Testable |
| 7. System-wide design decisions (5.4.1) | a. SSDD, IDD, DBDD DIDs | b. | c. | d. | e. | f. | g. Consistent with system requirements h. Feasible |
| 8. System architectural design (5.4.2) | a. SSDD, IDD DIDs | b. | c. | d. | e. | f. | g. Covers the system requirements h. Consistent with the system-wide design decisions i. Feasible |
| 9. CSCI requirements (5.5) | a. SRS, IRS DIDs | b. | c. | d. | e. | f. | g. Covers system requirements allocated to the CSCI h. Feasible i. Testable |
| 10. CSCI-wide design decisions (5.6.1) | a. SDD, IDD, DBDD DIDs | b. | c. | d. | e. | f. | g. Meets delivery requirements h. All software necessary for execution is present i. Version exactly matches version that passed testing j. Deliverable media accurately labelled |
| 11. CSCI architectural design (5.6.2) | a. SDD, IDD DIDs | b. | c. | d. | e. | f. | g. Consistent with CSCI requirements h. Feasible |
| 12. CSCI detailed design (5.6.3) | a. SDD, IDD, DBDD DIDs | b. | c. | d. | e. | f. | g. Covers CSCI requirements h. Consistent with CSCI-wide design decisions i. Feasible |
| 13. Implemented software (5.7.1) | N/A | b. | c. | d. | e. | f. | g. Covers CSCI requirements allocated to each unit h. Consistent with CSCI-wide design decisions |
| 14. CSCI qualification test descriptions (5.9.3) | a. STD DID | b. | c. | d. | e. | f. | g. Covers the CSCI detailed design |
| 15. CSCI qualification test results (5.9.7) | a. STR DID | b. | c. | d. | e. | f. | g. Covers all CSCI requirements |
| 16. System qualification test descriptions (5.11.3) | a. STD DID | b. | c. | d. | e. | f. | g. Covers all planned CSCI qualification test cases h. Shows evidence that the CSCI meets its requirements |
| 17. System qualification test results (5.11.7) | a. STR DID | b. | c. | d. | e. | f. | g. Covers all system requirements |
| 18. Executable software (5.12.1, 5.13.1) | N/A | b. | c. | d. | e. | f. | g. Covers all planned system qualification test cases h. Shows evidence the system meets its requirements |
| 19. Software version descriptions (5.12.2, 5.13.3) | a. SVD DID | b. | c. | d. | e. | f. | g. Accurately identifies the version of each software component (file,
unit, CSCI, etc.) delivered h. Accurately identifies the changes incorporated |
| 20. Software user manuals (5.12.3.1) | a. SUM DID | b. | c. | d. | e. | f. | g. Accurately describes software installation and use to the intended audience of this manual |
| 21. Software input/ output manuals (5.12.3.2) | a. SIOM DID | b. | c. | d. | e. | f. | g. Accurately describes software input/output to the intended audience of this manual |
| 22. Software center operator manuals (5.12.3.3) | a. SCOM DID | b. | c. | d. | e. | f. | g. Accurately describes software installation and operation to the intended audience of this manual |
| 23. Computer operation manuals (5.12.3.4) | a. COM DID | b. | c. | d. | e. | f. | g. Accurately describes the operational characteristics of the computer |
| 24. Source files (5.13.2) | a. SPS DID | b. | c. | d. | e. | f. | g. Meets delivery requirements h. All required software is present i. Version exactly matches version that passed testing j. Deliverable media accurately labelled |
| 25. "As built" CSCI design and related information (5.13.4) | a. SPS DID | b. | c. | d. | e. | f. | g. Accurately describes the "as built" design of the CSCI h. Accurately describes compilation/build procedures i. Accurately describes modification procedures j. Source files cover all units in the CSCI design k. Measured resource utilization meets CSC |
| 26. "As built" system design (5.13.5) | a. SSDD DID | b. | c. | d. | e. | f. | g. Accurately describes the "as built" system design |
| 27. Computer programming manuals (5.13.6.1) | a. CPM DID | b. | c. | d. | e. | f. | g. Accurately describes the programming features of the computer |
| 28. Firmware support manuals (5.13.6.2) | a. FSM DID | b. | c. | d. | e. | f. | g. Accurately describes firmware programming features |
| 29. Sampling of software development files (5.7.2, 5.7.3, 5.8.1, 5.8.4, 5.9.4, 5.10.1, 5.10.4, 5.11.4) | N/A | b. | N/A | d. | e. | f. | g. Contents are current with the ongoing effort h. Adequate unit test cases/procedures/data/results i. Adequate unit integration test cases/procedures/ data/results j. Adequate CSCI qualification dry run results k. Adequate CSCI/HWCI integration test case |
Translator: Simon Wright simon@pogner.demon.co.uk
Last updated: 22.iii.99