AWS-3 EEP v2.3 DSO Form 19 - Software System Certification.pdf

SOFTWARE SYSTEM CERTIFICATION

Software Name & Version:

Version Description: New Development Major Modification Minor Modification

Software System Components:

V & V FINAL RESULTS

V&V Activities:

Results:

Anomalies and Resolutions

Issues and Action Items

Assessment of Software Quality

Recommendation

DSO Justification:

(If Certification is not approved)

Distribution:

DSO Form 19, Effective JAN 2010 (Replaces JSC Form 18, SEP 2002, which is obsolete), Part 1 of 2

APPROVAL Typed Name Approving Signature Date (mm/dd/yyyy)

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

Carey.Beall Line

SOFTWARE SYSTEM CERTIFICATION

The purpose of this software system certification is to summarize the results of the V&V activities performed on the project, to document Contractor certification of the software system, and to ultimately record the JSC acceptance of the software system. The V&V Software System Certification is issued at the conclusion of the V&V effort.

Software System Certification Content

Task Order No., Name and Task

Enter the identifying Task Order (TO) number and name as it appears on the TO. If the TO is composed of multiple tasks, identify the specific task or tasks in the TO in which V&V is conducted.

Software System Name & Version

Enter the name and baseline version number of the software system that was the subject of the V&V effort during its development or maintenance.

Version Description

Indicate the degree of development involved in creating the new version of the software system, which was the subject of the V&V effort.

Software System Components

Identify the components of the software system and associated documentation that were the subject of the V&V effort.

V&V Activities

Identify all V&V activities that were conducted during the development or maintenance of the identified system. Choose from the following: Concept V&V, Requirements V&V, Design V&V, Implementation V&V, Test V&V, Installation V&V, Maintenance V&V. For each activity identified, indicate the level of V&V performed (i.e., Level 1, 2, 3, or 4).

V&V Results For each V&V activity identified above, summarize the findings that resulted from the activity.

Anomalies and Resolutions

For each V&V activity identified above, summarize the anomalies, detected as a result of the V&V tasks performed, and their associated resolutions. Identify those defects or anomalies that remain in the software system, and present an assessment of their impact on the reliability and usability of system.

Issues and Action Items

For each V&V activity identified above, summarize the issues, identified as a result of the V&V tasks performed, and the status of their associated action items.

Assessment of Software Quality

Based on the V&V task results and the status of identified anomalies and action items, present an assessment of the overall quality of the software system and of the software process used to develop or maintain it.

V&V Recommendations

Provide V&V recommendations related to the software system and the software process based on the software quality assessment. Provide comments relevant to the certification of the software system based on the final results of the V&V effort performed on the system. A representative of the V&V organization recommends certification of the software system by signing and dating this V&V Final Report.

DSO Form 19, Effective JAN 2010 (Replaces JSC Form 18, SEP 2002, which is obsolete), Part 2 of 2

Approval Signatures

Required approval signatures may vary, with the following exceptions: (1) the JSC Task Monitor must sign, (2) if the change is a major software change the JSC Commander must sign, (3) there must be signatures for both CRM Validation and for Production Validation.

Software System Certification Content