SOFTWARE QUALITY ASSURANCE PLAN TEMPLATE

(BASED ON ANSI/IEEE STD 730.1-1989)

1.0 1.1 1.2 1.3 1.4 2.0 3.0

..................................................................................................... ................................................................ INTRODUCTION ..................................................................................................... 1 PURPOSE ............................................................................................................... 1 SCOPE ................................................................................................................... 1 SOFTWARE ITEMS.................................................................................................... 1 SOFTWARE LIFE CYCLE ............................................................................................ 2 DOCUMENTS ................................................................ ..................................................... REFERENCE DOCUMENTS ..................................................................................... 2 ....................................................................................................... ................................................................ MANAGEMENT ....................................................................................................... 5

3.1 ORGANIZATION ....................................................................................................... 5 3.1.1 Organizational Structure ................................................................................. 5 3.1.2 Organizational Description .............................................................................. 5 3.1.3 Organizational Independence.......................................................................... 6 3.2 TASKS ................................................................................................................... 6 3.2.1 Software Life Cycle ......................................................................................... 6 3.2.2 SQA Activities.................................................................................................. 8 3.2.3 Milestones...................................................................................................... 10 3.3 RESPONSIBILITIES ................................................................................................. 12 3.3.1 Software Activities ........................................................................................ 12 3.3.2 Software Work Products................................................................................ 12 3.3.3 Walkthroughs Software Work Products ........................................................ 13 3.3.4 Inspections of Software Work Products........................................................ 13 4.0 ................................................................ ............................................................... DOCUMENTATION ............................................................................................... 14

4.1 PURPOSE ............................................................................................................. 14 4.2 MINIMUM DOCUMENTATION REQUIREMENTS ............................................................. 14 4.2.1 Software Requirements Document (SRD) ..................................................... 14 4.2.2 Software Architecture Description (SAD) ..................................................... 16 4.2.3 Software Verification and Validation Plan (SVVP)........................................ 16 4.2.4 Software Verification and Validation Report (SVVR).................................... 18 4.2.5 User Documentation Description (UDD)........................................................ 19 4.2.6 Software Configuration Management Plan (SCMP)....................................... 21 4.3 OTHER ................................................................................................................ 22 4.3.1 Software Project Plan (SPP) .......................................................................... 22 4.3.2 System Requirements Specification (SRS) ................................................... 24 4.3.3 System Architecture and Requirements Allocation Description (SARAD) ... 25 4.3.4 Database Design Description (DDD) .............................................................. 25 4.3.5 Software Interface Design Description (SIDD).............................................. 26 4.3.6 Test or Validation Plan (TVPL) ...................................................................... 26 4.3.7 Software Design Description (SDD)............................................................... 27 4.3.8 Test or Validation Procedures (TVPR) .......................................................... 27 4.3.9 Test or Validation Results Report (TVRR)..................................................... 28 4.3.10 Software Integration Plan (SOIP) ............................................................... 29 4.3.11 Software Integration Audit Report (SIAR).................................................. 29

- ii -

4.3.12 Software Installation Plan (SIP) ................................................................. 30 5.0 PRACTICES, STANDARDS, PRACTICES, CONVENTIONS, AND METRICS ................................ 31 AND

5.1 PURPOSE ............................................................................................................. 31 5.2 CONTENT ............................................................................................................. 31 5.2.1 Documentation Standards ............................................................................. 32 5.2.2 Logic Structure Standards ............................................................................ 32 5.2.3 Coding and Commentary Standards .............................................................. 35 5.2.4 Testing Standards and Practices .................................................................. 37 5.2.5 Software Process and Product Metrics......................................................... 39 6.0 REVIEWS AND AUDITS ........................................................................................ 40 AUDITS ........................................................................................ ................................

6.1 PURPOSE ............................................................................................................. 40 6.1.1 Technical and Managerial Reviews and Audits ............................................ 40 6.1.2 Accomplishing Reviews and Audits .............................................................. 41 6.1.3 Implementing and Verifying Reviews and Audits ......................................... 42 6.2 MINIMUM REQUIREMENTS ...................................................................................... 42 6.2.1 Software Requirements Review (SRR) .......................................................... 43 6.2.2 Software Preliminary Design Review (SPDR)................................................ 43 6.2.3 Software Critical Design Review (SCDR) ...................................................... 43 6.2.4 Software Verification and Validation Plan Review (SVVPR) ........................ 44 6.2.5 Functional Configuration Audit (FCA) ........................................................... 44 6.2.6 Physical Configuration Audit (PCA) ............................................................... 45 6.2.7 In-Process Audit ............................................................................................ 45 6.2.8 Managerial Review ........................................................................................ 46 6.2.9 Software Configuration Management Plan Review (SCMPR) ....................... 47 6.2.10 Post Mortem Review................................................................................... 47 6.3 OTHER ................................................................................................................ 48 6.3.1 System/Subsystem Requirements Review (SSRR)........................................ 48 6.3.2 System/Subsystem Design Review (SSDR) ................................................... 48 6.3.3 Software Test Readiness Review (SOTRR)................................................... 49 6.3.4 Software Test Results Review (SOTRER) ..................................................... 49 6.3.5 System Test Readiness Review (SYTRR)...................................................... 50 6.3.6 System Test Results Review (SYTRER) ........................................................ 50 6.3.7 Software Usability Review (SUR) .................................................................. 50 6.3.8 Software Maintenance Review (SMR) ........................................................... 51 7.0 8.0 9.0 TEST..................................................................................................................... TEST..................................................................................................................... 51 ................................................................................................ REPORTING ACTION............................................ ION................................ PROBLEM REPORTING AND CORRECTIVE ACTION............................................ 52 TECHNIQUES, METHODOLOGIES................................ ................................................... TOOLS, TECHNIQUES, AND METHODOLOGIES................................................... 52

................................................................................................... 10.0 CODE CONTROL................................................................................................... 54 CONTROL ................................................................................................ ................................................................................................. ................................................................ 11.0 MEDIA CONTROL ................................................................................................. 54

- iii -

.............................iv - ......0 TRAINING.......0 RECORDS COLLECTION............... AND 13...... ........................................................... 15...................................... 12........................................ ............................................................................................ AND RETENTION ... 14.............................................................................................................................. 56 ......................................CONTROL .... .............................................. 55 COLLECTION...... MAINTENANCE.............0 TRAINING ...............................0 SUPPLIER CONTROL ...................................................0 RISK MANAGEMENT .......................................................................................................... 56 14.................... 56 ................................................

and data processing CSCI of the command and control system. 1. and postprocessing of real-time telemetry data from specialized data measurement equipment. -1- . and records collection. The command and control system enables the high-speed collection. and metrics for software developers and how SQA verifies them. the data acquisition CSCI.0 INTRODUCTION This section shall delineate the specific purpose and scope of the particular SQAP. storage. status messaging and logging. conventions. Finally. techniques. the scope of the SQAP includes identification of SQA training requirements and the risk management methods and procedures to be used by the software project manager. tasks. identification of standards. It shall list the name(s) of the software items covered by the SQAP and the intended use of the software. The scope of the SQAP also includes identification of software tests not included in the SVVP. 1. data management CSCI.3 Software Items The software items covered by the SQAP include the operating system CSCI. the SQAP defines a set of activities designed to evaluate the software processes by which software work products are developed and/or maintained. and responsibilities.1. data management CSCI.1 Purpose The purpose of the SQAP is to define a planned and systematic pattern of all actions necessary to provide adequate confidence that a software work product conforms to established technical requirements. • Operating System CSCI: The operating system CSCI provides the integrating framework for the other three CSCIs. caution and warning. and methodologies for SQA. data acquisition CSCI. the scope of the SQAP includes identification of the code control. It shall state the portion of the software life cycle covered by the SQAP for each software item specified. and identification of tools. identification of minimum documentation requirements for software developers and how SQA verifies them. The operating system CSCI provides key integrating functions such as the human-computer user interface. identification of practices and procedures for problem reporting and corrective action. and identification of reviews and audits.2 Scope The scope of the SQAP includes definition of the SQA organization. In addition. Specifically. supplier control. and data processing CSCI. maintenance. media control. 1. and retention policies and procedures from software configuration management. practices.

and software acceptance support. The SQAP in its entirety applies to the command and control system and its four CSCIs. test. initialization. software installation. techniques. and methodologies. The software life cycle phases to which the SQAP applies include system requirements analysis.4 Software Life Cycle The software life cycle to which the SQAP applies for all CSCIs is defined by IEEE 12207. initialization. automatic data-rate detection. the software life cycle is a collection of interrelated activities or software processes for managing and developing software-based products and services. standards. high-speed data storage. More specifically. reviews and audits. software requirements analysis. system integration. datarate configuration. system architectural design. software coding and testing. archiving. -2- . practices. 2. software detailed design. conventions. and automated interfaces to the data management CSCI and operating system CSCI. The management. shutdown. data-rate detection. 1. supplier control. software integration. automatic data-size detection. system startup and shutdown. tools. initialization. data-size configuration. maintenance. built-in-test. system qualification testing. code control. training. and automated interfaces to the data processing CSCI and operating system CSCI. manual control.0 REFERENCE DOCUMENTS This section shall provide a complete list of documents referenced elsewhere in the text of the SQAP. • Data Acquisition CSCI: The data acquisition CSCI provides key functions such as a real-time interface to the specialized data measurement equipment. high-speed data reduction and analysis. and retrieval. • Data Processing CSCI: The data processing CSCI provides key functions such as real-time and non-real-time data processing. The software life cycle is the period of time that begins when a software product is conceived and ends when the software is no longer available for use. system initialization. high-speed data collection. shutdown. software qualification testing. media control. and risk management requirements of the SQAP apply to the command and control system software. software architectural design. • Data Management CSCI: The data management CSCI provides key functions such as a realtime interface to the data acquisition CSCI. and an automated command interface to the data management CSCI and operating system CSCI. and metrics. built-in-test. and retention. records collection. automatic data-size detection. special test scenario execution. built-in-test. and system debugging. shutdown. documentation.automatic command and control system execution. problem reporting and corrective action.

and control of changes. or a software system or subsystem. a group of related CSCIs.1-1989 (IEEE Standard for Software Quality Assurance Plans): The purpose of this standard is to provide uniform.0-1996 (IEEE Standard for Software Life Cycle Processes): The purpose of this standard is to provide uniform. • ANSI/IEEE STD 1058. It may also cover a particular aspect of software operation. define minimum V&V tasks. approval. • ANSI/IEEE STD 730. the tracking and reporting of such changes. readability. the IEEE Standard for Reviews and Audits. and software joint reviews. • DI-IPSC-81433-941205 (MIL-STD-498 Software User Manual Data Item Description): The purpose of this DID is to tell a hands-on software user how to install and use a CSCI.00. • ANSI/IEEE STD 1028-1988 (IEEE Standard for Software Reviews and Audits): The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. UML is a graphically and visually oriented diagramming standard for representing analytical models of software requirements and software designs. software records. minimum acceptable requirements for software activities.1-1987 (IEEE Standard for Software Project Management Plans): The purpose of this standard is to prescribe the format and content of software project management plans. which serve as controlling documents for managing software projects. the audits and reviews of the evolving software product. the IEEE Standard for Software Quality Assurance Plans. program structure. • ANSI/IEEE STD 828-1990 (IEEE Standard for Software Configuration Management Plans): The purpose of this standard is to establish the minimum required contents of SCM plans and activities which include the identification and establishment of baselines. software technical reviews. and the control of interface documenation and project supplier SCM. minimum acceptable requirements for preparation and content of Software Quality Assurance Plans (SQAPs). including requirements for source code presentation. • IEEE/EIA 12207. • OMG Version 1. • SPC-94093-CMC Version 01. the review. software products.The reference documents which the SQAP is principally based upon consist of three documents. programming -3- . and suggest optional V&V tasks. • ANSI/IEEE STD 1012-1986 (IEEE Standard for Software Verification and Validation Plans): This purpose of this standard is to provide uniform and minimum requirements for the format and content of SVVPs. such as instructions for a particular position or task. and the IEEE Standard for Software Life Cycle Processes.3-June 1999 (OMG Unified Modeling Language Specification): The purpose of this standard is to serve as a precise and self-consistent definition of UML semantics and notation.10-October 1995 (Ada 95 Quality and Style: Guidelines for Professional Programmers): The purpose of this document is to provide software source code style and coding guidelines for the Ada 95 computer programming language.

Inc...P.W. • BL. Miller. comments. W3C. make. types. 25-June-1990 (Indian Hill C Style and Coding Standards): The purpose of this document is to provide software source code style and coding guidelines for the C computer programming language. R. to include broad classes of software measures. linking.. Keppel. Milner.. whitespace. file organization. white space. Files include file naming conventions. and project-dependent standards. including requirements for file organization. Spencer. keyword reference. and source file content. Prentice Hall. functions. simple statements. Mitze. Kirchhoff. • Sun Microsystems. 1998 (W3C Style Guide for Online Hypertext): The purpose of this document is to provide software source code style and coding guidelines for the HTML computer programming language. and database standards... R. conditional compilation.0b-October 2000 (PSM Practical Software and Systems Measurement: A Foundation for Objective Project Management): The purpose of this document is to introduce software process and product measurement guidelines for managing system and software projects.practices.H. declarations. statements. function declarations. Elliot. T.W. including requirements for markup tags.. L. Revision 6. H. 1997 (Wildfire C++ Programming Style: With Rationale): The purpose of this document is to provide software source code style and coding guidelines for the C++ computer programming language.. reusability object-oriented features. portability. indentation. tables. declarations. lint...W. operators. portability. and practical examples. miscellaneous.. Inc. equipments. J. M. naming conventions. compound statements. • Gabryelski. K. constants. concurrency. header file content. E.O. and fill-out forms. comments. character formatting.. macros. • Patrick. T. including requirements for files. control and user interface standards.M. • MIL-STD-1521B-4 June 1985 (Military Standard for Technical Reviews and Audits for Systems. using white space. N. special considerations. debugging. Schan.0. 20-APR-99 (Sun Code Conventions for the Java Programming Language): The purpose of this document is to provide software source code style and coding guidelines for the Java computer programming language. D. inline images. Equipments. and Brader. and -4- .A. • DoD and US Army Version 4. Wildfire Communications. ANSI C. naming conventions. 2000 (Visual Basic Style Guide): The purpose of this document is to provide software source code style and coding guidelines for the Visual Basic computer programming language. and programming practices. and interaction with C. and Computer Software): The purpose of this standard is to prescribe the requirements for the conduct of technical reviews and audits on systems. guidelines for application. including requirements for file names. preprocessor. statements. Wittington. L. • Cannon. J. including requirements for declaration standards. variables. and improving performance. file organization. identifier naming conventions.

.2 Organizational Description The organizational description to which the SQAP applies consists of software engineering which is responsible for software development. • Software Testing: Software testing is a process of dynamically operating. software testing. software testing which is responsible for evaluating the software. SCM which is responsible for controlling software baselines. 3. more specifically. the software configuration management group.e. and the software engineering process group. SCM. exercising. by the application of software test plans. are not included in the software engineering group. and has been designed to take advantage of current technological advancement and management procedures in conducting reviews and audits. and test reports. 3.1 Organization This paragraph shall depict the organizational structure that influences and controls the quality of the software. code. and SQA which is responsible for evaluating the software engineering. and.computer software. Groups performing software-related work. software test procedures. and evaluating CSCIs to ensure that they meets their software requirements. and test) for a project. software test designs. This shall include a description of each major element of the organization together with the delegated responsibilities. 3. software testing. -5- . requirements analysis. SQA itself. and responsibilities. 3. such as the software quality assurance group. Organizational dependence or independence of the elements responsible for SQA from those responsible for software development and use shall be clearly described or depicted.1 Organizational Structure The organizational structure to which the SQAP applies consists of software engineering. tasks. software test cases. and SCM processes.0 MANAGEMENT This section shall describe organization. • Software Engineering: Software engineering is the collection of individuals (both managers and technical staff) who have responsibility for software development and maintenance activities (i. design. executing.1.1.

SQA is not functionally subordinate to software engineering. software architectural design. software integration. system qualification testing. and authority from software engineering in order to maintain independence. and software acceptance support. schedule. quality. SCM. or the software engineering functional manager. 3. -6- . responsibility. for later use by system architectural design.1 Software Life Cycle The software life cycle phases to which the SQAP applies include system requirements analysis. and especially SQA. for computer software configuration items (CSCI) of a system or segment of a system. software testing. • System Requirements Analysis Phase: System requirements analysis is the process of developing system-level requirements. software engineering reports to a software project lead and the software engineering functional manager. 3. system architectural design.2 Tasks This paragraph shall describe (a) that portion of the software life cycle covered by the SQAP.2. and integrity of SQA activities. objectivity. and delivery pressures of software projects. the software project lead. software installation. software coding and testing. SQA does not report to the system project or program manager in order to further propagate the integrity of SQA independence and protect SQA software process evaluation activities and results from the cost.1. Primarily. The sequence of the tasks shall be indicated. system integration. and verify compliance with specified requirements. (2) A set of activities designed to evaluate the process by which software work products are developed and/or maintained. software detailed design. and reporting channels between software engineering. Furthermore. software requirements analysis. software qualification testing.• SCM: SCM is a discipline applying technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a configuration item. and (c) the relationships between these tasks and the planned major check-points. functional organization. and thus maintains independent power. control changes to those characteristics. record and report change processing and implementation status.3 Organizational Independence The organizational independence of SQA consists of a mutually exclusive chain of authority. (b) the tasks to be performed with special emphasis on software quality assurance activities. status. • SQA: SQA is defined as a (1) A planned and systematic pattern of all actions necessary to provide adequate confidence that a software work product conforms to established technical requirements. 3.

for a CSCI of a system or segment of a system.Software Activity System System Software Software Requirements Architectural Requirements Architectural Analysis Design Analysis Design Software Detailed Design Software Coding and Testing Software Integration Software Qualification Testing System Integration System Qualification Testing Software Installation Software Acceptance Support Software Product • SRS • SARAD SRD • UDD • DDD (p) SAD • SIDD (p) • TVPL • UDD (u) • • DDD (d) SDD • SIDD (d) • TVPL (u) • UDD (u) • • DDD (u) TVPL (u) • TVPR • UDD (u) • TVRR • • SOIP TVPR (u) • UDD (u) • TVRR • • UDD (u) SIAR • TVRR • • • • TVPR (u) TVRR • TVRR • SIP • TVRR Technical Review • Walkthru • Inspection • Walkthru • Inspection • Walkthru • Inspection • Walkthru • Inspection • Walkthru • Inspection • Walkthru • Inspection • Walkthru • Inspection • Walkthru • Inspection • Walkthru • Inspection • Walkthru • Inspection Software Record • SYRER • SYAER • SORER • SOAER • DDER EOCR SCTRER • SCR • • • SIER • • DER SCR • SQTER SCR SER • SQTARR • • • SIRR • SCR Joint Review System/ Subsystem Requirements Review System/ Subsystem Design Review Software Requirements Review Software Preliminary Design Review Software Critical Design Review Software Test Readiness Review Software Test Results Review System Test Readiness Review System Test Results Review Software Usability Review Software Maintenance Review PLAN (3) SIP SOIP TVPL Software Installation Plan Software Integration Plan Test or Validation Plan SPECIFICATION (1) SRS System Requirements Specification DESCRIPTION (7) DDD SAD SARAD SDD SIDD SRD UDD Database Design Description Software Architecture Description System Architecture and Requirements Allocation Description Software Design Description Software Interface Design Description Software Requirements Description User Documentation Description PROCEDURE (1) TVPR Test or Validation Procedures SIAR TVRR REPORT (2) Software Integration Audit Report Test or Validation Results Report RECORD (14) DDER DER EOCR SCR SCTRER SER SIER SIRR SOAER SORER SQTARR SQTER SYAER SYRER Detailed Design Evaluation Record Documentation Evaluation Record Executable Object Code Record Source Code Record Software Code and Test Results Evaluation Record System Evaluation Record Software Integration Evaluation Record Software Installation Results Record Software Architecture Evaluation Record Software Requirements Evaluation Record System Qualification Test Audit Results Record System Qualification Test Evaluation Record System Architecture Evaluation Record System Requirements Evaluation Record (p)—preliminary. • Software Requirements Analysis Phase: Software requirements analysis is the process of developing software requirements. for later use by software detailed design. for a system or segment of a system. (u)—updated • System Architectural Design Phase: System architectural design is the process of transforming the system-level requirements into an architectural design. including its operational and support environments. -7- . • Software Architectural Design Phase: Software architectural design is the process of transforming software requirements into a top-level software design consisting of computer software components (CSC). for later use by software architectural design. (d)—detailed. for a CSCI of a system or segment of a system. for later use by software requirements analysis.

using test cases and test procedures based on system-level requirements. technical reviews. using acceptance test plans. • Software Integration Phase: Software integration is the process of combining and evaluating the CSUs that have been implemented and unit tested. for a CSCI of a system or segment of a system. software architectural design. for later use by software coding and unit testing. for later use by software installation. system architectural design.2. for CSCIs of a system or segment of a system. for later use by system qualification testing. for later use by software qualification testing. including system requirements analysis. that have undergone individual software and hardware qualification testing. software -8- . for later use by software integration. • Software Coding and Testing Phase: Software coding and testing is the process of transforming the software detailed design—CSUs—into computer software. • Software Installation Phase: Software installation is the process of transporting and installing software associated with a system or a segment of a system from the development environment to the target environment. and test procedures. • System Qualification Testing Phase: System qualification testing is the process of dynamically evaluating integrated CSCIs and HWCIs of a system or segment of a system. software detailed design. software products. software requirements analysis. • System Integration Phase: System integration is the process of combining and evaluating CSCIs and HWCIs of a system or segment of a system. using installation policies. plans. test cases. for later use by system integration.2 SQA Activities The SQA activities principally consist of auditing the software activities. 3. in order to determine to whether or not to accept the system from the developer. and software records of the software life cycle phases for conformance to software process and software product standards. There are SQA activities for each of the twelve software life cycle phases. • Software Qualification Testing Phase: Software qualification testing is the process of dynamically evaluating computer software using test cases and test procedures based on CSCI-level software requirements. • Software Acceptance Support Phase: Software acceptance support is the process of assisting customers and end-users dynamically evaluate a system or segment of a system. for a CSCI of a system or segment of a system. for a CSCI of a system or segment of a system. for later use by software acceptance support.• Software Detailed Design Phase: Software detailed design is the process of decomposing the software architectural design into an increasingly detailed hierarchy of computer software units (CSU). procedures. and work instructions.

and UDD (u) for conformance to the software detailed design activity standard. TVPR (u). walkthrough standard. and UDD (u). SRS document standard. DDD (u). and UDD (u) for conformance to the software architectural design activity standard. • System Architectural Design Phase: The SQA activities for the system architectural design phase include auditing the system architectural design activities. UDD. and UDD (u). and UDD (u) document standards. UDD (u). SID (p). TVPR (u). SAD.coding and testing. walkthroughs of the SOIP. UDD (u). SAD. SDD. TVPR. and TVRR. SIDD (d). walkthroughs of the DDD (u). walkthroughs of the DDD (p). TVPL (u). and TVRR document standards. walkthroughs of the SARAD. and inspections of the SRD and UDD for conformance to the software requirements analysis activity standard. TVPR. and inspections of the SRS for conformance to the system requirements analysis activity standard. SDD. walkthroughs of the SRD and UDD. DDD (d). and TVRR. TVPL (u). system qualification testing. UDD (u). and inspections of the DDD (d). -9- . SID (p). walkthrough standard. UDD (u). TVPL. software qualification testing. SAD. software installation. SDD. and inspection standard. and inspections of the DDD (u). SIDD (d). SDD. DDD (d). TVPL (u). SID (p). SAD. TVPL (u). walkthrough standard. SARAD. walkthrough standard. system integration. DDD (p). SIDD (d). TVPR. TVPL. SRD and UDD document standards. TVPL (u). and TVRR. TVPL. TVPR. SARAD document standard. • Software Integration Phase: The SQA activities for the software integration phase include auditing the software integration activities. and TVRR. and UDD (u) document standards. and inspection standard. • Software Requirements Analysis Phase: The SQA activities for the software requirements analysis phase include auditing the software requirements analysis activities. and inspections of the DDD (p). SRS. software integration. DDD (p). and inspection standard. and UDD (u). TVPL (u). and inspection standard. and inspections of the SARAD for conformance to the system architectural design activity standard. UDD (u). TVPL (u). walkthrough standard. and inspections of the SOIP. and inspection standard. • Software Coding and Testing Phase: The SQA activities for the software coding and testing phase include auditing the software coding and testing activities. TVPL. DDD (u). and software acceptance support. SID (p). SIDD (d). UDD (u). and TVRR for conformance to the software coding and testing activity standard. walkthroughs of the SRS. and inspection standard. SRD. • System Requirements Analysis Phase: The SQA activities for the system requirements analysis phase include auditing the system requirements analysis activities. • Software Architectural Design Phase: The SQA activities for the software architectural design phase include auditing the software architectural design activities. SOIP. walkthrough standard. walkthroughs of the DDD (d). and UDD (u). • Software Detailed Design Phase: The SQA activities for the software detailed design phase include auditing the software detailed design activities. TVPL (u).

TVPR (u) and TVRR document standards. UDD (u). . and SRS inspections shall occur before SSRR commences. UDD (u). UDD (u). and TVRR. system/subsystem design review. TVPR (u) and TVRR. walkthrough standard. TVRR document standard. SIAR.2. and inspection standard. TVRR document standard. and TVRR for conformance to the software integration activity standard. SIAR. walkthrough standard. UDD (u). SQA audits of system requirements analysis activities. system test readiness review. and inspection standard. and the software maintenance review. and inspection standard. walkthroughs of the SIP.3 Milestones The milestones which follow the SQA activities include the system/subsystem requirements review. • System Qualification Testing Phase: The SQA activities for the system qualification testing phase include auditing the system qualification testing activities. system test results review. SOIP. • System Integration Phase: The SQA activities for the system integration phase include auditing the system integration activities. • Software Installation Phase: The SQA activities for the software installation phase include auditing the software installation activities. walkthrough standard. and inspections of the TVRR for conformance to the system integration activity standard. • Software Qualification Testing Phase: The SQA activities for the software qualification testing phase include auditing the software qualification testing activities. and inspections of the TVRR for conformance to the system integration activity standard. the SRS. and inspections of the UDD (u). software critical design review. and inspection standard. and TVRR document standards. walkthrough standard. SIAR. and inspections of the TVPR (u) and TVRR for conformance to the system integration activity standard. which immediately follows the system requirements analysis phase. software usability review. walkthroughs of the TVRR. and inspections of the SIP for conformance to the system integration activity standard. walkthrough standard. and TVRR for conformance to the software qualification testing activity standard. software test results review. and TVRR document standards. TVRR. • System/Subsystem Requirements Review (SSRR): External review techniques include a system/subsystem requirements review (SSRR). walkthroughs of the TVPR (u) and TVRR. SRS walkthroughs. and inspection standard. 3. and inspection standard.10 - . walkthroughs of the TVRR. software requirements review. software test readiness review. SIP document standard. TVPR (u). walkthroughs of the UDD (u). and TVRR. • Software Acceptance Support Phase: The SQA activities for the software acceptance support phase include auditing the software acceptance support activities. TVRR. SIAR. software preliminary design review.TVPR (u). walkthrough standard. SIP.

TVPL. SQA audits of software architectural design activities. SIAR. SIAR. TVPL. which immediately follows the software architectural design phase. which immediately follows the software detailed design phase. SRD and UDD walkthroughs. SID (p). SAD. TVRR. SQA audits of software detailed design activities. UDD (u). TVPR (u) and TVRR walkthroughs. and UDD (u) inspections shall occur before SCDR commences. TVRR. SOIP. • System Test Readiness Review (SYTRR): External review techniques include a SYTRR. and TVPR (u) inspections shall occur before SOTRR commences. and TVPR (u) walkthroughs. TVRR. which immediately follows the system integration phase. SID (p). and UDD (u) walkthroughs. SQA audits of software requirements analysis activities. the UDD (u). SID (p). SIDD (d). SAD. SQA audits of system integration activities. SQA audits of system architectural design activities. DDD (d). and UDD (u). the SRD and UDD. SDD. which immediately follows the software qualification testing phase. which is necessary to successfully conclude the system architectural design phase. and DDD (p).• System/Subsystem Design Review (SSDR): External review techniques include a system/subsystem design review (SSDR). TVPL (u). SOIP. DDD (p). • Software Requirements Review (SRR): External review techniques include a software requirements review (SRR). SIDD (d). • Software Test Results Review (SOTRER): External review techniques include a software test results review (SOTRER). the DDD (d). and UDD (u) walkthroughs. SOIP. and TVPR (u) and TVRR inspections shall occur before SYTRR. SIAR. UDD (u). SDD. and UDD (u) inspections shall occur before SPDR commences. and UDD (u). . TVPL (u). SAD. the SARAD. TVPL (u). and TVRR inspections shall occur before SOTRER. TVPR. which immediately follows the software requirements analysis phase. SIDD (d). the TVPR (u) and TVRR. and UDD (u). and DDD (d). and DDD (u). • Software Critical Design Review (SCDR): External review techniques include a software critical design review (SCDR). TVPL (u). TVPR. TVPL (u). SDD. SQA audits of software qualification testing activities. TVPR. and SARAD inspections shall occur before SSDR commences. the DDD (u). • Software Test Readiness Review (SOTRR): External review techniques include a software test readiness review (SOTRR). TVPL (u). SARAD walkthroughs. and TVRR walkthroughs. • Software Preliminary Design Review (SPDR): External review techniques include a software preliminary design review (SPDR). which immediately follows the software integration phase. SQA audits of software coding and testing activities and software integration activities. the DDD (p). DDD (u). and TVRR. and TVPR (u). UDD (u).11 - . UDD (u). and SRD and UDD inspections shall occur before SRR commences. TVPL.

and TVRR inspections shall occur before SMR. walkthroughs of the software work products.12 - . SQA shall audit the software products. SQA shall audit the SRS resulting from the system requirements analysis activity. which immediately follows the software installation phase. • Software Maintenance Review (SMR): External review techniques include a software usability review (SUR). SQA audits of the software acceptance support activities. and SIP inspections shall occur before SUR.2 Software Work Products The responsibilities of SQA shall include auditing the software work products for each of the twelve software life cycle phases for conformance to software work product standards.1 Software Activities The responsibilities of SQA shall include auditing the software activities for each of the twelve software life cycle phases for conformance to software activity standards. and software acceptance support activities. which immediately follows the system qualification testing phase. SQA audits of the software installation activities. software installation. the TVRR. which include each of the 31 software work products resulting from each of the twelve software activities for conformance to software work product standards. SQA shall audit the . which include the software activities themselves. SQA shall audit the system requirements analysis. 3. 3. 3. and TVRR inspections shall occur before SYTRR. SIP walkthroughs. software qualification testing. software requirements analysis. system qualification testing. the TVRR. walkthrough standards. • Software Usability Review (SUR): External review techniques include a software usability review (SUR). the SIP.3. software integration.3 Responsibilities This paragraph shall identify the specific organizational elements responsible for each task. TVRR walkthroughs.• System Test Results Review (SYTRER): External review techniques include a system test results review (SYTRER). software coding and testing. system integration. and inspections of the software work products for conformance to software activity standards. software architectural design. The responsibilities of SQA shall include auditing the software processes and software products of the software life cycle for conformance to software process and software product standards. and inspection standards. system architectural design. which immediately follows the software installation phase. TVRR walkthroughs. SQA shall audit the software processes. SQA audits of the system qualification testing activities.3. software detailed design.

SQA shall audit walkthroughs of the UDD (u). TVPL (u). And.13 - . SIDD (d). and TVRR resulting from the software qualification testing activity. SQA shall audit the SOIP. UDD (u). UDD (u). SIAR.3 Walkthroughs Software Work Products The responsibilities of SQA shall include auditing walkthroughs of software work products for each of the twelve software life cycle phases for conformance to walkthrough standards. SQA shall audit the UDD (u). SIAR.3. SQA shall audit walkthroughs of the DDD (d). SQA shall audit the TVRR of the system qualification testing activity. UDD (u). and UDD (u) resulting from the software architectural design activity. SQA shall audit inspections of the SRS resulting from the system requirements analysis activity. and TVRR resulting from the software qualification testing activity. TVPL (u). UDD (u). SQA shall audit walkthroughs of the DDD (p). and UDD (u) resulting from the software detailed design activity.SARAD resulting from the system architectural design activity. and TVRR resulting . TVPL. TVPL. SAD.3. SQA shall audit the TVPR (u) and TVRR of the system integration activity. and UDD (u) resulting from the software detailed design activity. SIDD (d). SQA shall audit inspections of the DDD (p). SAD. SQA shall audit the DDD (p). TVPL (u). and UDD (u) resulting from the software architectural design activity. SDD. SAD. SQA shall audit walkthroughs of the DDD (u). SQA shall audit the DDD (d). and UDD (u) resulting from the software detailed design activity. SQA shall audit the SRD and UDD resulting from the software requirements analysis activity. SQA shall audit walkthroughs of the SRS resulting from the system requirements analysis activity. SQA shall audit the TVRR of the software acceptance support activity. TVPL (u). SDD. And. SQA shall audit walkthroughs of the SOIP. SQA shall audit the DDD (u). TVPL (u). SIDD (p). TVPR (u). SIDD (p). SQA shall audit walkthroughs of the SRD and UDD resulting from the software requirements analysis activity. SIDD (d). SQA shall audit walkthroughs of the TVPR (u) and TVRR of the system integration activity. and TVRR resulting from the software coding and testing activity. TVPR. TVPR.4 Inspections of Software Work Products The responsibilities of SQA shall include auditing inspections of software work products for each of the twelve software life cycle phases for conformance to inspection standards. 3. SQA shall audit walkthroughs of the SIP of the software installation activity. SQA shall audit inspections of the DDD (d). SIDD (p). TVPR (u). SQA shall audit walkthroughs of the SARAD resulting from the system architectural design activity. UDD (u). TVPL (u). and TVRR resulting from the software coding and testing activity. SQA shall audit inspections of the SRD and UDD resulting from the software requirements analysis activity. and TVRR resulting from the software integration activity. TVPR. 3. SQA shall audit the SIP of the software installation activity. SQA shall audit inspections of the DDD (u). TVPL. SDD. SQA shall audit inspections of the SARAD resulting from the system architectural design activity. and TVRR resulting from the software integration activity. SQA shall audit walkthroughs of the TVRR of the system qualification testing activity. SQA shall audit the TVRR of the software acceptance support activity. and UDD (u) resulting from the software architectural design activity.

(2) State how the documents are to be checked for adequacy. demonstration. the following documentation is required as a minimum: 4. SQA shall conduct an audit of the SRD to verify the following properties: .1 DOCUMENTATION Purpose This section shall perform the following functions: (1) Identify the documentation governing the development. for example. TVPR (u). SQA shall audit the TVRR of the software acceptance support activity. UDD (u). The purpose of the software requirements description is to specify the requirements for a software item and the methods to be used to ensure that each requirement has been met. 4.from the software coding and testing activity. And. design constraints. use. This shall include the criteria and the identification of the review or audit by which the adequacy of each document shall be confirmed. inspection. performances. The software requirements description is used as the basis for design and qualification testing of a software item. and TVRR resulting from the software integration activity. SQA shall audit inspections of the TVRR of the system qualification testing activity. verification and validation. 4. Each requirement shall be defined such that its achievement is capable of being objectively verified and validated by a prescribed method.14 - . analysis. SQA shall audit inspections of the UDD (u). or test. SIAR.0 4. SQA shall audit inspections of the SOIP. SQA shall audit inspections of the SIP of the software installation activity. SQA shall audit inspections of the TVPR (u) and TVRR of the system integration activity. and maintenance of the software. and TVRR resulting from the software qualification testing activity. and attributes) of the software and the external interfaces.2.2 Minimum Documentation Requirements To ensure that the implementation of the software satisfies requirements. with reference to Section 6 of the SQAP.1 Software Requirements Document (SRD) The SRD shall clearly and precisely describe each of the essential requirements (functions.

• Design and implementation constraints. • Environmental conditions. • Performance requirements. • Qualification requirements.• Generic description information.15 - . • Security and privacy specifications. • User maintenance requirements. environmental influences. • Safety specifications. including those related to compromise of sensitive information. • Human-factors engineering (ergonomics) requirements. • User documentation requirements. and personnel injury. • Requirements for interfaces external to software item. • User operation and execution requirements. • Areas that need concentrated human attention and are sensitive to human errors and training. • Human-equipment interactions. • Software quality characteristics. • Data definition and database requirements. including installation-dependent data for adaptation needs. • Functionality of the software item. • Installation and acceptance requirements of the delivered software product at the maintenance site(s). • Constraints on personnel. • Physical characteristics. • Installation and acceptance requirements of the delivered software product at the operation site(s). • Manual operations. including those related to methods of operation and maintenance. . • System identification and overview.

• Packaging requirements. • Requirements traceability. The SAD shall describe the components and subcomponents of the software design. The purpose of the software architecture description is to describe the software item-wide design decisions and the software item architectural design.3 Software Verification and Validation Plan (SVVP) The SVVP shall identify and describe the methods (for example.• Computer resource requirements. • System overview and identification. 4.2. • Identification of software requirements allocated to each software component. • Precedence and criticality of requirements. . inspection. • Software component definition. • Software item architectural design. 4. • Software component concept of execution. • Rationale for software architecture and component definition decisions. • Rationale. • Resource limitations and the strategy for managing each resource and its limitation. • Software architecture general description.2. including data bases and internal interfaces.16 - .2 Software Architecture Description (SAD) The SAD shall depict how the software will be structured to satisfy the requirements in the SRD. The SAD shall be prepared first as the Preliminary SAD (also referred to as the Top-Level SAD) and shall be subsequently expanded to produce the Detailed SDD. SQA shall conduct an audit of the SAD to verify the following properties: • Generic description information. analysis. including database and user interface design.

• Referenced documents. complies with the requirements expressed in the SRS. • Tools. for critical software. • Concept phase V&V. • Management of V&V. • Resources summary. define. The purpose of the software verification and validation plan is to provide.17 - .demonstration. specific minimum V&V tasks and their required inputs and outputs that shall be included in SVVPs. • Implementation phase V&V. and (c) the design expressed in the SDD is implemented in the code. . for both critical and non-critical software. when executed. • Master schedule. (2) To validate that the code. • Design phase V&V. • Life-cycle verification and validation. • Requirements phase V&V. and methodologies. • Test phase V&V. • Definitions. • Responsibilities. uniform and minimum requirements for the format and content of SVVPs. SQA shall conduct an audit of the SVVP to verify the following properties: • Purpose. and suggest optional V&V tasks to be used to tailor SVVPs as appropriate for the particular V&V effort. (b) the requirements in the SRS are implemented in the design expressed in the SDD. techniques. • Verification and validation overview. • Organization. or test) to be used: (1) To verify that (a) the requirements in the SRS have been approved by an appropriate authority.

practices. • Control procedures. software qualification testing. • Interim results and status.18 - .4 Software Verification and Validation Report (SVVR) The SVVR shall describe the results of the execution of the SVVP. • Summary of anomalies and resolution. • Optional reports. 4. • Summary of task results. • Operation and maintenance phase V&V. system qualification testing.• Installation and checkout phase V&V. . • Task iteration policy. • Standards. software detailed design. software architectural design. • Description of V&V tasks performed. • Anomaly reporting and resolution. and software acceptance support. software requirements analysis. system architectural design. and conventions. • V&V phase summary report. system requirements analysis. SQA shall conduct an audit of the SVVR to verify the following properties: • Task reporting. • Required reports. software installation. • Deviation policy. system integration. • Software verification and validation reporting. • Verification and validation administrative procedures. software integration.2. The purpose of the software verification and validation report is to summarize the results of V&V tasks performed in each of the software life cycle phases. software coding and testing.

• Recommendations. • Software quality assurance results.. • Impact. guide. • Special studies report. options. • Summary of anomalies and resolutions. program limitations. • Criticality. manual. • Cause. input sequences. • V&V final report.• Assessment of software quality.19 - .2. All error messages shall be identified and . • Summary.g. • Approach. • Recomendations. • Recommendations. 4. • Software configuration management results. • Other reports. • Purpose and objectives. and other activities or items necessary for successful execution of the software. • Software testing results.5 User Documentation Description (UDD) User documentation (e.) shall specify and describe the required data and control inputs. • Description and location. • Anomaly report. • Assessment of overall software quality. • Summary of task results. • Summary of all life-cycle V&V tasks. etc.

• Software summary. • First-time user of the software. • Access control. • Software inventory. • Equipment familiarization. • Document overview.corrective actions described. • Installation and setup. • Access to the software. • Software organization and overview of operation. • Contingencies and alternate states and modes of operation. A method of describing user-identified errors or problems to the developer or the owner of the software shall be described. • Assistance and problem reporting. • Initiating a session. (Embedded software that has no direct user interaction has no need for user documentation and is therefore exempted from this requirement.20 - . . • System overview. SQA shall conduct an audit of the UDD to verify the following properties: • Scope. • Security and privacy.) The purpose of the user documentation description is to record the planning and engineering information created during the development process that is of use to the users of the software product or service. • Software environment. • Referenced documents. • Software application. • Identification.

• Notes. .• Stopping and suspending work. • Messages. • SCM management. • Appendices. 4. • Conventions. • Quick-reference guide. The purpose of the software configuration management plan is to provide a structure for identifying and controlling software documentation. software interfaces. organization and management philosophy. malfunctions. support the software development and maintenance methodology that fits the software requirements. • Identifying configuration items. and recording and reporting change implementation status. SQA shall conduct an audit of the SCMP to verify the following properties: • Introduction. and databases to support all software life cycle phases.6 Software Configuration Management Plan (SCMP) The SCMP shall document methods to be used for identifying software items. and support production of management and product information concerning the status of software baselines.2. • (Aspect of software use). • Related processing. • Data backup. tests. standards. • Capabilities. policies. and audits. releases.21 - . software source code. • Configuration identification. change control. • Processing reference guide. controlling and implementing changes. and emergencies. • Recovery from errors. • Processing procedures.

• SCM schedules.22 - . • Configuration control. and tasks necessary to satisfy the requirements of a software project. • Configuration audits and reviews. • Requesting changes. • Interface control. • Subcontractor/vendor control. • Evaluating changes. A software project plan defines the technical and managerial project functions. SQA shall conduct an audit of the SPP to verify the following properties: .1 Software Project Plan (SPP) The purpose of the software project plan is to serve as a controlling document for managing a software project. • Configuration status accounting. • Acquiring configuration items.• Naming configuration items.3. 4. • Approving or disapproving changes. activities. as defined in the project agreement.3 Other Other documentation may include the following: (1) Software Development Plan (2) Standards and Procedures Manual (3) Software Project Management Plan (4) Software Maintenance Manual. • SCM plan maintenance. • SCM resources. • Implementing changes. 4.

. software size. • Means for scheduling. . • Software life cycle model. operation or maintenance. as applicable). warranty and licensing rights.. implementation. • Approval required by such means as regulations. • Management of the quality characteristics of the software products or services (separate plans for quality may be developed). equipment. and other critical requirements of the software products or services (separate plans for safety and security may be developed).e. proprietary. required certifications. if any. • Project organizational structure showing authority and responsibility of each organizational unit. and reporting. staffing. approval. audits. security. requirements setting exercises. privacy. ownership. • Training of personnel. including the approach for interfacing with the verification and validation agent. tracking.e. joint reviews. acceptance. access to facilities). modification and change. • Configuration management (separate plans for configuration management may be developed). standards. • User involvement (i. software services and non-deliverable items to be performed. • Engineering environment (for development. including external organizations. procedures.23 - .. • Risk management (i.. reporting. informal meetings. • Subcontractor management. including the software products. • Management of safety. including subcontractor selection and involvement between the subcontractor and the acquirer. prototype demonstrations and evaluations). physical resources. including test environment.• Generic plan information for managing the project.e. and schedules associated with the tasks. cost. if specified. usage. • Verification and validation. facilities. budgets.e. the management of the areas of the project that involve technical. and tools. • Security policy (i. and schedule risks). • Work breakdown structure of the life cycle processes and activities. library. • Quality assurance. the rules for need-to-know and access-to-information at each project organizational level). • Acquirer involvement (i.

including utilization requirements.3. • System quality characteristics. and logistics requirements. • Required states and modes. • Personnel. and privacy protection requirements. The system requirements specification is used as the basis for design and qualification testing of a system or subsystem. and user requirements. • System external interface requirements. • Design constraints and qualification requirements. • Physical requirements. • System environmental requirements. .24 - .2 System Requirements Specification (SRS) The purpose of the system requirements specification is to specify the requirements for a system or subsystem and the methods to be used to ensure that each requirement has been met. • Business. • Internal data requirements. • Computer hardware resource requirements. training. • Human-factors engineering (ergonomics) requirements. • Computer hardware requirements. • Computer communications requirements. • Requirements for the functions and performance of the system. • System identification and overview. • Computer software requirements. • Safety. • Operations and maintenance requirements. • Computer resource requirements. security. organizational.4. • Installation-dependent data requirements. SQA shall conduct an audit of the SRS to verify the following properties: • Generic specification information.

• System overview and identification. SQA shall conduct an audit of the DDD to verify the following properties: • Generic description information. The database design description is used as the basis for implementing the database and related software units.3.g. • Hardware item identification. software items. .. 4. • Database overview and identification. internal.4 Database Design Description (DDD) The purpose of the database design description is to describe the design of a database.3 System Architecture and Requirements Allocation Description (SARAD) The purpose of the system architecture and requirements allocation description is to describe the architectural design of a system or subsystem. including descriptions of applicable design levels (e. • Rationale. a collection of related data stored in one or more computerized files in a manner that can be accessed by users or computer programs via a database management system. conceptual. that is. • Precedence and criticality of requirements. SQA shall conduct an audit of the SARAD to verify the following properties: • Generic description information. 4. • Concept of execution. • Manual operations identification. and manual operations. • Design of the database. • Rationale for allocation of hardware items.3. The database design description may also describe the software units used to access or manipulate the data.25 - .• Packaging requirements. physical). • Software item identification. logical. • Reference to design description of software used for database access or manipulation.

reduction. source language.6 Test or Validation Plan (TVPL) The purpose of the test or validation plan is to describe plans for qualification testing of software items and software systems. SQA shall conduct an audit of the SIDD to verify the following properties: • Generic description information.g. .3. hardware item. • Test progression. and analysis. • External interface identification. • Data recording.5 Software Interface Design Description (SIDD) The purpose of the software interface design description is to describe the interface characteristics of one or more system. software item.. source language. manual operation. • External-software item interface definition (e.. and provide schedules for test activities.g. 4. • General test conditions.3. identify the tests to be performed. • Software component-software component interface definition (e. • Software item-software item interface definition (e. source language. • Software component identification. • Test levels. diagrams).. or other system component.26 - . • Test classes. subsystem.g. The software interface design description may describe any number of interfaces. diagrams). The test or validation plan describes the software test environment to be used for the testing. 4. SQA shall conduct an audit of the TVPL to verify the following properties: • Generic plan information. • Software unit identification.• Rationale for database design. diagrams).

• Rationale for software item design. SQA shall conduct an audit of the SDD to verify the following properties: • Generic description information. • Reuse element identification. and test procedures to be used to perform qualification testing of a software item or a software system or subsystem. including algorithms and data structures.3.27 - .3. • Software item input/output description.8 Test or Validation Procedures (TVPR) The purpose of the test or validation procedures is to describe the test preparations. . and participating organizations. • Requirements traceability. • Planned tests. site. 4. The software design description may be supplemented by software item interface design and database design. • Qualification testing environment.• Test coverage (breadth and depth) or other methods for assuring sufficiency of testing. • Requirements traceability. including data flow and control flow. • Description of how the software item satisfies the software requirements. • Test schedules. • Static relationships of software units. The test or validation procedures enable the acquirer to assess the adequacy of the qualification testing to be performed. The software design description and the software architecture provide the detailed design needed to implement the software. • Software component-level requirements traceability. 4. including items and their identifiers. personnel. • Concept of execution. test cases. • Software unit-level requirements traceability.7 Software Design Description (SDD) The purpose of the software design description is to describe the design of a software item.

SQA shall conduct an audit of the TVPR to verify the following properties: • Test or Validation Procedures.28 - . • Overall assessment of the software tested. a software system or subsystem. • Criteria for evaluating results. The test or validation results report enables the acquirer to assess the testing and its results. SQA shall conduct an audit of the TVRR to verify the following properties: • Generic report information. and rationale. . • Identification of test configuration. or other software-related item. software. • Requirements addressed. • Expected test results. • Requirements traceability. • Instructions for conducting procedure. • Overview of test results. requirements. • System identification and overview. • Test objectives. • Identification of test author. • Rationale for decisions. other) for each test. 4. • Test preparations (hardware. • Test identifier. • Test input. • Prerequisite conditions. • Generic procedure information.9 Test or Validation Results Report (TVRR) The purpose of the test or validation results report is to provide a record of the qualification testing performed on a software item.3. • Test descriptions.

SQA shall conduct an audit of the SOIP to verify the following properties: • Generic plan information. • Test data. • Test responsibilities.10 Software Integration Plan (SOIP) The purpose of the software integration plan is to define the activities necessary to integrate the software units and software components into the software item.• Impact of test environment. • Test summary. 4.3. • Rationale for decisions. • Deviations from test cases/procedures. • Test log. • Problems encountered. • Test schedule. • Detailed test results. • Test identifier. • Scope.3.29 - . • Issuing organization. SQA shall conduct an audit of the SIAR to verify the following properties: • Date of issue and status.11 Software Integration Audit Report (SIAR) The purpose of the software integration audit report is to describe the results of an independent audit of software qualification testing activities and work products. • Test procedures. • Test requirements. 4. .

• Conclusions and recommendations. • Document overview. • Change history. • Bibliography. set initial parameters. • Relationship to other plans. • Referenced documents. • Support materials.12 Software Installation Plan (SIP) The purpose of the software installation plan is to describe the information necessary to install a system or component. • System overview. • Contributors. • Contact point. • Description. and prepare the system or component for operational use. • Summary. 4. . • Introduction. • Message.30 - .3. • Identification. • Context.• References. • Installation overview. SQA shall conduct an audit of the SIP to verify the following properties: • Scope. • Body. • Glossary.

• Facilities. • (Site name). • Data update procedures.2 Content The subjects covered shall include the basic technical.• Training. conventions and metrics to be applied. • Tasks.31 - . • Installation team. • Security and privacy protection.0 5. design. • (Site name). 5. • Site-specific information for software users. PRACTICES. 5. and programming activities .1 STANDARDS. • Software inventory. (2) State how compliance with these items is to be monitored and assured. CONVENTIONS. • Installation procedures. • Data update procedures. • Installation procedures. AND METRICS Purpose This section shall: (1) Identify the standards. • Site-specific information for software center operations staff. • Schedule. • Schedule. • Personnel. practices.

and even instances.1 Documentation Standards The documentation standards that shall be enforced by the SQAP are the IEEE Standard for Software Life Cycle Processes. 5. interfaces. use case diagram. The following nine UML logic structure diagrams shall be enforced by the SQAP. As a minimum.2 Logic Structure Standards The logic structure standard that shall be enforced by the SQAP is the OMG Unified Modeling Language. SAD. the SRS. TVPR. A class diagram is a graphic view of the static structural model. collaboration diagram. such as documentation.32 - . TVPL. packages.2. The individual class diagrams do not represent divisions in the underlying model.2. UDD. and deployment diagram. MIL-STD-498 Software User Manual Data Item Description. the following information shall be provided: (1) Documentation standards (2) Logic structure standards (3) Coding standards (4) Commentary standards (5) Testing standards and practices (6) Selected software quality assurance product and process metrics such as: (a) Branch metric (b) Decision point metric (c) Domain metric (d) Error message metric (e) Requirements demonstration metric 5. SDD. relationships. statechart diagram. TVRR. IEEE Standard for Software Configuration Management Plans. connected as a graph to each other and to their contents. object diagram. Only the following documentation standards from the IEEE Standard for Software Life Cycle Processes shall be enforced by the SQAP.involved. and SIP. Perhaps a better name would be “static structural diagram” but “class diagram” is shorter and well established. variable and module naming. such as objects and links. class diagram. and testing. SARAD. such as classes. SIDD. Class diagrams may be organized into packages . A class diagram is a collection of (static) declarative model elements. Note that a “class” diagram may also contain interfaces. and the IEEE Standard for Software Project Management Plans. IEEE Standard for Software Verification and Validation Plans. SRD. SIAR. • Class Diagram: A class diagram is a graph of classifier elements connected by their various static relationships. programming. and their relationships. activity diagram. SOIP. sequence diagram. inspection. component diagram. DDD.

) • Collaboration Diagram: A collaboration diagram presents a collaboration. Class diagrams can contain objects. Objects can be grouped into “swimlanes” on a diagram. or a class as manifested by sequences of messages exchanged among the system and one or more outside interactors (called actors) together with actions performed by the system. as manifested to external interactors with the system or the classifier. A use case diagram is a graph of actors. an the relationships between these elements. A class represents a concept within the system being modeled. A use case is show as an ellipse containing the name of the use case. The use cases represent functionality of a system or a classifier. (See subsequent sections for details of the contents of a sequence diagram. As a classifier. Classes have data structure and behavior and relationships to other elements. An optional stereotype keyword may be placed above the name and a list of properties included below the name. which defines a set of messages .33 - .) Usually only time sequences are important. a subsystem. to characterize a particular usage achievable in various ways. which is a set of messages between classifier roles within a collaboration to effect a desired operation or result. extends. Use case diagrams show actors and use cases together with their relationships. a set of use cases. The relationships are associations between the actors and the use cases. • Use Case Diagram: A use case diagram shows the relationship among actors and use cases within a system. A sequence diagram has two dimensions: 1) the vertical dimension represents time and 2) the horizontal dimension represents different objects. • Object Diagram: An object diagram is a graph of instances. A use case is a kind of classifier representing a coherent unit of functionality provide by a system. if desired. so a class diagram with objects and no classes is an “object diagram.” The phrase is useful. and generalizations. There is no significance to the horizontal ordering of the objects. a use case may also have compartments displaying attributes and operations. The name of a class has scope within the package in which it is declared and the name must be unique (among class names) within its package. as well as their required relationships given in a particular context. generalizations between the actors. A static object diagram is an instance of a class diagram. like a subsystems or a class. including objects and data values. A class is drawn as a solid-outline rectangle with three compartments separated by horizontal lines. (The dimensions may be reversed. but in real-time applications the time axis could be an actual metric. it shows a snapshot of the detailed state of a system at a point in time. Mainly to show examples of data structures.either with their underlying models or as separate packages that build upon the underlying model packages. however. and includes among the use cases. The diagram may also present an interaction. The top name compartment holds a list of attributes. which contains a set or roles to played by objects. the bottom list compartment holds a list of operations. • Sequence Diagram: A sequence diagram presents an interaction. possibly some interfaces. Tools need not support a separate format for object diagrams. The use of object diagrams is fairly limited. Normally time proceeds down the page. The use cases may optionally be enclosed by a rectangle that represents the boundary of the containing system or classifier.

States may also contain sub-diagrams by physical containment or tiling. and executable components. but statecharts may also describe the behavior of other model entities such as use cases. and stimuli. actors. “software” components are taken in the broad sense to include business procedures and documents. A statechart diagram is a graph that represents a state machine. while a collaboration describing an operation includes the arguments and local variables of the operation. signals. association roles. operations invocations). while transitions are generally rendered by directed arcs that interconnect them.specifying the interaction between the objects playing the roles within a collaboration to achieve the desired result. The graphical rendering of this top state is optional. some exist at link time. some exist at run . or classifier roles and association roles. • Statechart Diagram: A statechart diagram can be used to describe the behavior of a model element such as an objet or an interaction. it may either show instances. A collaboration which describes a classifier. A software module may be represented as a component stereotype. and messages. For a business.g. like a use case. The entire activity diagram is attached (through the model) to a class. operations. Use activity diagrams in situations where all or most of the events represent fhe completion of internally-generated actions (that is. or show classifier roles. procedural flow of control). or methods. • Activity Diagram: An activity graph is a variation of a sate machine in which the states represent the performance of actions or subactivities and the transitions are triggered by the completion of the actions or subactivities. binary code components. Note that every state machine has a top state which contains all the other elements of the entire state machine. Specifically. • Component Diagram: A component diagram shows the dependencies among software components.34 - . Use ordinary state diagrams in situations where asynchronous events occur. Some components exist at compile time. including source code components. An activity diagram is a special case of a state diagram in which all (or at least most) of the states are action or subactivity states and in which all (or at least most) of the transitions are triggered by completion of the actions or subactivities in the source states. Statechart diagrams represent the behavior of entities capable of dynamic behavior by specifying its response to the receipt of event instances. The purpose of this diagram is to focus on flows driven by internal processing (as opposed to external events). States and various other types of vertices (pseudostates) in the state machine graph are rendered by appropriate state and pseudostate symbols. A collaboration diagram shows a graph of either objects linked to each other. subsystems. Typically. A collaboration is used for describing the realization of an operation or a classifier. such as a use case. it may also include the communication stated by an interaction.. references classifiers and associations in general. or to the implementation of an operation. it describes possible sequences of states and actions through which the element can proceed during its lifetime as a result of reacting to discrete events (e. or to a package. A collaboration diagram can be given in two different forms: at instance level or at specification level. it is used for describing the behavior of classes. It represents a state machine of a procedure itself. links. as well as ordinary associations attached to the classifier owning the operation.

time, and some exist at more than one time. A compile-only component is one that is only meaningful at compile time. The run-time component in this case would be an executable program. A component diagram has only a type form, not an instance form. To show component instances, use a deployment diagram (possibly a degenerate one without nodes). A component diagram is a graph of components connected by dependency relationships. Components may also be connected to components by physical containment representing composition relationships. A diagram containing component types and node types may be used to show static dependencies, such as compiler dependencies between programs, which are show as dashed arrows (dependencies) from a client component to a supplier component that it depends on in some way. The kinds of dependencies are implementation-specific and may be shown as stereotypes of the dependencies. As a classifier, a component may have operations and may realize interfaces. The diagram may show these interfaces and calling dependencies among components, using dashed arrows from components to interfaces on other components. • Deployment Diagram: Deployment diagrams show the configuration of run-time processing elements and the software components, processes, and objects that live on them. Software component instances represent run-time manifestations of code units. Components that do not exist as run-time entities (because they have been compiled away) do not appear on these diagrams, they should be show on component diagrams. For business modeling, the run-time processing elements include workers and organizational units, and the software components include procedures and documents used by the workers and organizational units. A deployment diagram is a graph of nodes connected by communication associations. Nodes may contain component instances. This indicates that the component lives or runs on the node. Components may contain objects, this indicates that the object resides on the component. Components are connected to other components by dashed-arrow dependencies (possible through interfaces). This indicates that one component uses the services of another component. A stereotype may be used to indicate the precise dependency, if needed. The deployment type diagram may also be used to show which components may reside on which nodes, by using dashed arrows with the stereotype support from the component symbol to the node symbol or by graphically nesting the component symbol within the node symbol. 5.2.3 Coding and Commentary Standards

The coding standards that shall be enforced by the SQAP include the SPC Ada 95 Quality and Style, Indian Hill C Style and Coding Standards, Wildfire C++ Programming Style, Visual Basic Style Guide, W3C Style Guide for Online Hypertext, and the Sun Code Conventions for the Java Programming Language. • SPC Ada 95 Quality and Style: The SPC Ada 95 Quality and Style includes requirements for source code presentation, readability, program structure, programming practices, concurrency, portability, reusability object-oriented features, and improving performance. Source code presentation includes code formatting. Readability includes spelling, naming conventions,

- 35 -

comments, and using types. Program structure includes high-level structure, visibility, and exceptions. Programming practices include optional parts of the syntax, parameter lists, types, data structures, expressions, statements, visibility, using exceptions, and erroneous execution and bounded errors. Concurrency includes concurrency options, communication, and termination. Portability includes fundamentals, numeric types and expressions, storage control, tasking, exceptions, representation clauses and implementation-dependent features, and input/output. Reusability includes understanding and clarity, robustness, adaptability, and independence. Object-oriented features include object-oriented design, tagged type hierarchies, tagged type operations, managing visibility, and multiple inheritance. Improving performance includes performance issues, performance measurement, program structure, data structures, algorithms, types, and pragmas. • Indian Hill C Style and Coding Standards: The Indian Hill C Style and Coding Standards include requirements for file organization, comments, declarations, function declarations, whitespace, simple statements, compound statements, operators, naming conventions, constants, macros, conditional compilation, debugging, portability, ANSI C, special considerations, lint, make, and project-dependent standards. • Wildfire C++ Programming Style: The Wildfire C++ Programming Style includes requirements for files, preprocessor, identifier naming conventions, using white space, types, variables, functions, statements, miscellaneous, and interaction with C. Files include file naming conventions, file organization, header file content, and source file content. Preprocessor includes macros and conditional compilation. Identifier naming conventions include general rules, identifier style, namespace clashes, and reserved namespaces. Using white space includes indentation, long lines, comments, block comments, single-line comments, and trailing comments. Types include constants, use of const, struct and union declarations, enum declarations, classes, class declarations, class constructors and destructors, automatically-provided member functions, function overloading, operator overloading, protected items, friends, friend classes, friend methods, and templates. Variables include placement of declarations, extern declaration, indentation of variables, number of variables per line, definitions hiding other definitions, and initialized variables. Functions include function declarations and function definitions. Statements include compound statements, if/else statements, for statements, do statements, while statements, infinite loops, empty loops, switch statements, goto statements, return statements, and try/catch statements. Miscellaneous includes general comments and rules, limits on numeric precision, comparing against zero, boolean, character, integral, floating point, pointer, use and misuse of inline, references versus pointers, and portability. Interaction with C includes ANSI-C/C++ include files, including C++ header files in C programs, including C header files in C++, and C code calling C++ libraries. • Visual Basic Style Guide: The Visual Basic Style Guide includes requirements for declaration standards, keyword reference, control and user interface standards, and database standards. Declaration standards include nomenclature standards, nomenclature for variables, nomenclature for constants, nomenclature for user-defined types, nomenclature for

- 36 -

enumerated data types, nomenclature for line labels, nomenclature for procedures, nomenclature for declares, nomenclature for user interface elements, nomenclature exceptions, instantiation standards, instantiation of variables, instantiation of constants, instantiation of user-defined types, instantiation of enumerated data types, instantiation of line lables, instantiation of procedures, instantiation of declares, declaration modifiers, global options, compiler directives, Visual Basic limitation on declaration, and data typing of literals. Keyword reference includes compiler directives, conversion functions, date and time features, declaration features, error handling and debugging features, file system features, financial features, flow control features, math features, miscellaneous features, operators, and string features. Control and user interface standards includes general considerations, communication, control interaction, documentation, and specific control information. Database standards include database design, nomenclature, normalization, database documentation, database usage, spreadsheet presentation, bound filed presentation, and form object presentation. • W3C Style Guide for Online Hypertext: The W3C Style Guide for Online Hypertext includes requirements for markup tags, character formatting, linking, inline images, tables, and fill-out forms. Markup tags include html, head, title, body, headings, paragraphs, lists, preformatted text, extended quotations, addresses, forced line breaks/postal addresses, and horizontal rules. Character formatting includes logical versus physical styles and escape sequences. Linking includes relative pathnames versus absolute pathnames, URLs, links to specific sections, and mailto. Inline images include image size attributes, aligning images, alternate text for images, background graphics, background color, and external images, sounds, and animations. Tables include table tags, general table format, and tables for nontabular information. • Sun Code Conventions for the Java Programming Language: The Sun Code Conventions for the Java Programming Language includes requirements for file names, file organization, indentation, comments, declarations, statements, white space, naming conventions, and programming practices. File names include file suffixes and common file names. File organization includes Java source files, beginning comments, package and import statements, and class and interface declarations. Indentation includes line length and wrapping lines. Comments include implementation comment formats, block comments, single-line comments, trailing comments, end-of-line comments, and documentation comments. Declarations include number per line, initialization, placement, and class and interface declarations. Statements include simple statements, compound statements, return statements, if, if-else, if else-if else statements, for statements, while statements, do-while statements, switch statements, and trycatch statements. White space includes blank lines and blank spaces. Programming practices include providing access to instance and class variables, referring to class variables and methods, constants, variable assignments, miscellaneous practices, parentheses, returning values, expressions before ‘?’ in the conditional operator, and special comments. 5.2.4 Testing Standards and Practices

- 37 -

The test or . and test procedures to be used to perform qualification testing of a software item or a software system or subsystem. software qualification testing. The test or validation plan describes the software test environment to be used for the testing. the TVPL. using test cases and test procedures based on system-level requirements. and software acceptance support. software coding and testing. and the TVRR. for later use by software integration. for later use by software installation. for a CSCI of a system or segment of a system. • Test or Validation Procedures (TVPR): The purpose of the test or validation procedures is to describe the test preparations. identify the tests to be performed. test cases. and provide schedules for test activities. test cases. that have undergone individual software and hardware qualification testing. system qualification testing. • Software Coding and Testing Phase: Software coding and testing is the process of transforming the software detailed design—CSUs—into computer software. • Software Qualification Testing Phase: Software qualification testing is the process of dynamically evaluating computer software using test cases and test procedures based on CSCI-level software requirements.38 - . • Software Acceptance Support Phase: Software acceptance support is the process of assisting customers and end-users dynamically evaluate a system or segment of a system. for later use by system qualification testing. software integration. for a CSCI of a system or segment of a system. for later use by system integration. TVPR. system integration. • Test or Validation Plan (TVPL): The purpose of the test or validation plan is to describe plans for qualification testing of software items and software systems. in order to determine to whether or not to accept the system from the developer. • Software Integration Phase: Software integration is the process of combining and evaluating the CSUs that have been implemented and unit tested. for CSCIs of a system or segment of a system.The testing standards and practices that shall be enforced by the SQAP are from the IEEE Standard for Software Life Cycle Processes. using acceptance test plans. and test procedures. The following software activity standards from the IEEE Standard for Software Life Cycle Processes shall be enforced by the SQAP. The following documentation standards from the IEEE Standard for Software Life Cycle Processes shall be enforced by the SQAP. for later use by software qualification testing. • System Qualification Testing Phase: System qualification testing is the process of dynamically evaluating integrated CSCIs and HWCIs of a system or segment of a system. • System Integration Phase: System integration is the process of combining and evaluating CSCIs and HWCIs of a system or segment of a system.

easily understood measure. Size is a critical factor for estimating development schedules and costs. software effort (process). The lines of code measure counts the total amount of source code and the amount that has been added. software cycle time (process). The test or validation results report enables the acquirer to assess the testing and its results.5 Software Process and Product Metrics The software process and product metrics that shall be enforced by the SQAP are defined by the PSM Practical Software and Systems Measurement guide. and system test. The effort measure counts the number of labor hours or number of personnel applied to all tasks. and process performance. and productivity. Productivity is also useful early in the project for estimate and baseline comparisons before actual productivity data is available. This is a straightforward. modified. • Software Cost (process): The cost measure counts budgeted and expended costs. compared to budgets. and software quality (product).39 - . and possible additional work. Changes in the number of lines of code indicate development risk due to product size volatility. or other software-related item. unit test. code. but can also address other common issue areas including schedule and progress. which is especially critical late in product development. required effort. 5. measured in person-months.validation procedures enable the acquirer to assess the adequacy of the qualification testing to be performed. • Test or Validation Results Report (TVRR): The purpose of the test or validation results report is to provide a record of the qualification testing performed on a software item. This measure is a basic input to project planning and can evaluate whether performance levels are sufficient to meet cost and schedule estimates. The productivity measure compares the amount of product completed to the amount of effort expended. or deleted. Lines of code is a well-understood software measure that helps in estimating project cost. a software system or subsystem. The measure provides information about the amount of money spent on a project or a product. • Software Cycle Time (process): Cycle time or duration is defined as the elapsed time in hours or months during which development effort proceeds without interruption. • Software Effort (process): Effort refers to develop effort—the effort required to design.2. It can be categorized by activity as well as by product. schedule. software productivity (process). These measures also provide information on the amount and frequency of change to products. software cost (process). • Software Productivity (process): Productivity is the number of lines of source code produced per programmer-month (person-month) of effort. Cycle time . and shall include software size (process). • Software Size (process): Physical size and stability measures quantify the physical size of a system or product. This measure usually correlates directly with cost. Only six software process and product metrics have been selected from the PSM Practical Software and Systems Measurement Guide.

1 Technical and Managerial Reviews and Audits The first ten technical and managerial reviews and audits are from the IEEE Standard for Software Quality Assurance Plans and the IEEE Standard for Software Reviews and Audits. Closure rates are an indication of progress. or whether rework is being deferred. 6. status. functional configuration audit. a key objective in process improvement is to reduce overall cycle time. Defect density can identify components with the highest concentration of defects. They include the software requirements review. The purpose of this section is to identify and define the technical and managerial reviews and audits that shall be enforced by the SQAP. 6. Military Standard for Technical Reviews and Audits for Systems.1.40 - . The number of defects indicates the amount of rework. Usually. Eighteen technical and managerial reviews and audits shall be enforced by the SQAP as defined by the IEEE Standard for Software Quality Assurance Plans. and has a direct impact on quality. and post mortem review.measures the length of time that it takes a process to complete all associate activities.0 6. software verification and validation plan review. in-process audits. The defects measure quantifies the number. software. IEEE 12207. physical configuration audit. • Software Quality (product): Quality or defect density is the number of software defects committ4ed per thousand lines of software source code. Tracking the length of time that defects have remained open can be use to determine whether progress is being made in fixing defects. and the IEEE Standard for Software Reviews and Audits. The accumulation of all processes determines the total schedule to complete a project. and priority of defects reported. The next eight reviews are from the IEEE Standard for Software Life Cycle Processes and Military Standard for Technical Reviews and . Equipments.1 REVIEWS AND AUDITS Purpose This section shall: (1) Define the technical and managerial reviews and audits to be conducted. and Computer Software. software critical design review. and can be used to predict test completion. (3) State what further actions are required and how they are to be implemented and verified. Arrival rates can indicate product maturity (a decrease should occur as testing is completed). It provides useful information on the ability of a supplier to find and fix defects in hardware. A defect density measure—an expression of the number of defects in a quantity of product—can be derived from this measure. (2) State how the reviews and audits are to be accomplished. or documentation. managerial reviews. software preliminary design review. software configuration management plan review.

walkthroughs and inspections. software verification and validation personnel. and software quality assurance personnel. • Managerial Review: Software project managers and software project personnel are responsible for executing the policies and procedures of managerial reviews. software configuration management personnel. Software project personnel.1. software project personnel. system test results review. are responsible for executing the policies and procedures of walkthroughs and inspections. • Software Requirements Review (SRR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SRR. software test readiness review. the audit process itself. are responsible for executing the policies and procedures for two of the three types of in-process audits. system/subsystem design review. 6. system test readiness review.41 - . Software quality assurance is directly responsible for executing the policies and procedures of only one of the three types of in-process audits. • In-Process Audit: Software quality assurance personnel are responsible for executing the policies and the procedures of the audit process. and software configuration management are responsible for executing the policies and procedures of the SVVPR. software project personnel. software usability review. and Computer Software. .Audits for Systems. They include the system/subsystem requirements review. Equipments. software quality assurance. Software configuration management is responsible for executing the policies and procedures associated with functional configuration audits and physical configuration audits. • Functional Configuration Audit (FCA): Software configuration management personnel are responsible for executing the policies and procedures of the FCA. namely software engineers. and software maintenance review. • Software Verification and Validation Plan Review (SVVPR): Software project managers. • Software Preliminary Design Review (SPDR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SPDR. Software project managers are responsible for executing the policies and procedures associated with joint reviews. • Physical Configuration Audit (PCA): Software configuration management personnel are responsible for executing the policies and procedures of the PCA. • Software Critical Design Review (SCDR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SCDR. software test results review. Software project personnel. namely software engineers.2 Accomplishing Reviews and Audits The reviews and audits will be accomplished by the application of individual policies and procedures for each of the reviews and audits by software project managers.

6. • Software Test Readiness Review (SOTRR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SOTRR.42 - . • System Test Readiness Review (SYTRR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SYTRR. as well as audit process effectiveness.1. and software configuration management are responsible for executing the policies and procedures of post mortem reviews. software quality assurance. Verification of the audit process. software quality assurance. and software configuration management are responsible for executing the policies and procedures of the SCMPR. • System/Subsystem Requirements Review (SSRR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SCDR.• Software Configuration Management Plan Review (SCMPR): Software project managers. • Software Maintenance Review (SMR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SMR. • System/Subsystem Design Review (SSDR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SSDR.2 Minimum Requirements As a minimum.3 Implementing and Verifying Reviews and Audits Implementation and verification of the eighteen major types of reviews and audits shall be accomplished by audits performed by software quality assurance personnel. software project personnel. software project personnel. • Post Mortem Review: Software project managers. SQA shall audit each of the eighteen types of reviews and audits using the audit process itself (with the exception of the audit process). 6. • System Test Results Review (SYTRER): Software project managers and software project personnel are responsible for executing the policies and procedures of the SYTRER. • Software Test Results Review (SOTRER): Software project managers and software project personnel are responsible for executing the policies and procedures of the SOTRER. shall be independently evaluated (other than by software quality assurance personnel). • Software Usability Review (SUR): Software project managers and software project personnel are responsible for executing the policies and procedures of the SUR. software verification and validation personnel. the following reviews and audits shall be conducted: .

this review determines their compatibility with performance and engineering specialty requirements of the HWCI development specification. and personnel. this review focuses on the evaluation of the progress. This review is conducted for each configuration . The SRR is conducted when CSCI requirements have been sufficiently defined to evaluate the contractor's responsiveness to and interpretation of the system. External review techniques include a software preliminary design review (SPDR). and schedule basis) of the selected design approach. subsystem. facilities. External review techniques include a software requirements review (SRR). A successful SRR is predicated upon the contracting agency's determination that the COD. and risk resolution (on a technical. cost. and on the preliminary version of the operation and support documents.2. which immediately follows software requirements analysis. 6.2.43 - . SRD. which immediately follows software architectural design. This review is conducted for each configuration item or aggregate of configuration items to evaluate the progress. Finally this review establishes the existence and compatibility of the physical and functional interfaces among the configuration items and other items of equipment. or prime item level requirements. computer software. technical adequacy. For configuration items. and technical adequacy of the selected top-level design and test approach. 6. The SRR is a review of the finalized CSCI requirements and operational concept.1 Software Requirements Review (SRR) The SRR is held to ensure the adequacy of the requirements stated in the SRS. For CSCIs.2 Software Preliminary Design Review (SPDR) The SPDR (also known as top-level design review) is held to evaluate the technical adequacy of the preliminary design (also known as top-level design) of the software as depicted in the preliminary software design description. which immediately follows software detailed design. compatibility between software requirements and preliminary design. and evaluates the degree of definition and assesses the technical risk associated with the selected manufacturing methods/processes.2. consistency. and UDD form a satisfactory basis for proceeding into software architectural design.6. External review techniques include a software critical design review (SCDR).3 Software Critical Design Review (SCDR) The SCDR (also known as detailed design review) is held to determine the acceptability of the detailed software designs as depicted in the detailed software design description in satisfying the requirements of the SRD.

6. Resolving software V&V non-conformances consists of identifying. computer software and personnel. performance. monitoring. The objective of the Functional Configuration Audit (FCA) shall be to verify that the configuration item's actual performance complies with its hardware Development or Software Requirements and Interface Requirements Specifications. cost.2. 6. walkthroughs.2. and schedule basis). compliance levels of software V&V activities. and inspections of the SVVP to ensure that it meets the requirements as stated in software project plans and software requirements documents. and test characteristics of the design solution. determine the effectiveness of software V&V. and on the adequacy of the operation and support documents. This review also establishes the detailed design compatibility among the configuration items and other items of equipment. measure compliance with the SVVP. The objective of the Software Verification and Validation Plan Review (SVVR) shall be to verify the SVVP conforms to software V&V standards. and resolve software V&V non-conformances. Measuring compliance with the SVVP consists of conducting audits of software V&V activities to determine their compliance with policies and procedures. inspections. this review focuses on the determination of the acceptability of the detailed design. and software quality and reliability levels of the software work products themselves. Determining the effectiveness of software V&V consists of analyzing completion of SVVP tasks. actions. walkthroughs. Finally.44 - . Verifying the SVVP conforms to software V&V standards consists of conducting audits of the SVVP to ensure that it meets the requirements of the SVVP standard. and audits. and tracking the issues. assesses configuration item risk areas (on a technical.4 Software Verification and Validation Plan Review (SVVPR) The SVVPR is held to evaluate the adequacy and completeness of the verification and validation methods defined in the SVVP. Verifying the SVVR meets the needs of the software project consists of conducting managerial reviews. the SVVP meets the needs of the software project. the purpose of this review is to review the preliminary hardware product specifications. and assesses the results of the producibility analyses conducted on system hardware. facilities. Test data shall be reviewed to verify that the hardware or computer software performs as required by its functional/ allocated . For CSCIs. The purpose of this review is to determine that the detailed design of the configuration item under review satisfies the performance and engineering specialty requirements of the HWCI development specifications.item when detail design is essentially complete.5 Functional Configuration Audit (FCA) This audit is held prior to the software delivery to verify that all requirements specified in the SRS have been met. and non-conformances arising from managerial reviews. and ensuring their rapid resolution and closure.

specifications. including: (1) Code versus design documentation (2) Interface specifications (hardware and software) (3) Design implementations versus functional requirements (4) Functional requirements versus test descriptions There are three types of in-process audits. walkthroughs. The review shall include an audit of the released engineering documentation and quality control records to make sure the as-build or as-coded configuration is reflected by this documentation. For software. 6. For configuration items developed at Government expense. Inspections are expertly facilitated evaluations of software products by domain experts. Software User's Manual (SUM). and manuals for CSCIs.7 In-Process Audit In-process audits of a sample of the design are held to verify consistency of the design. the Software Product Specification and Software Version Description shall be a part of the PCA review. in or order to verify conformance to software process and product standards. and as appropriate. the Computer System Diagnostic Manual (CSDM). Software audits are independent evaluations of software activities and software work products by software quality assurance. 6. namely software .configuration identification.6 Physical Configuration Audit (PCA) This audit is held to verify that the software and its documentation are internally consistent and are ready for delivery. listings. The PCA includes a detailed audit of engineering drawings. For software.2. Computer System Operator's Manual (CSOM).45 - . and inspections. a technical understanding shall be reached on the validity and the degree of completeness of the Software Test Reports.2. Walkthroughs are informal design review meetings held principally by software project managers to elicit comments and feedback on their design solutions. The PCA also determines that the acceptance testing requirements prescribed by the documentation is adequate for acceptance of production units of a configuration item by quality assurance activities. After successful completion of the audit. all subsequent changes are processed by engineering change action. software audits. The Physical Configuration Audit (PCA) shall be the formal examination of the as-built version of a configuration item against its design documentation in order to establish the product baseline. technical data and tests utilized in production of HWCIs and a detailed audit of design documentation. an FCA shall be a prerequisite to acceptance of the configuration item.

or technical lead that’s directly responsible for creating or designing a product. nonconformances to standards. and/or safety hazards. verbalizes the intended operational flow. without any defense from the author or creator of the product. In performing the audit. specifications. and procedures.8 Managerial Review . SQA audits verify conformance to software process and product standards.2. guidelines. walkthroughs are intended for managers to solicit design alternatives (without any mandatory action on behalf of the manager or product author). or procedures. recommendations are reported in addition to the audit results. or technical leads.engineers. requirements. and software engineering inspections are expert forums for directly improving software quality. and standards. In short. and without any consideration of design alternatives. non-conformances to numerical tolerances. in order to identify defects. functional flow. When stipulated by the audit plan. The results of the audit are documented and are submitted to the management of the audited organization. In short. plans. operational and functional failures. Audits are performed in accordance with documented plans and procedures. • Walkthrough: A walkthrough is an informal design review meeting in which the manager. without the presence of managers. and to any external organizations identified in the audit plan. or a specific solution to satisfy the product’s requirements or specifications. a technical architecture. solicit a critique of the approach. non-conformances to requirements and specifications.46 - . not suggest design alternatives or subjective improvements to the product). supervisor. to the entity initiating the audit. a detailed design. • Software Audit: The objective of software auditing is to provide an objective compliance confirmation of products and processes to certify adherence to standards. or any subjective improvements to the product’s design by the examiners (in order identify defects for later mandatory correction and enable early validation of the product using internal technical experts before it is delivered). The report includes a list of the items in noncompliance or other issues for subsequent review and action. Software project manager walkthroughs are open forums for evaluating software designs. audit personnel evaluate software elements and the processes for producing them against objective audit criteria. engineers. while very complementary. The three types of in-process audits are each unique. such as contracts. and technical specialists (in order to defend the design concept. • Inspection: An inspection is a highly structured and facilitated meeting in which independent technical experts analyze and examine each of the individual product characteristics one-byone. supervisors. specifications. guidelines. to evaluate their conformance to requirements and identify software defects for mandatory correction. The audit plan establishes a procedure to conduct the audit and for follow-up action on the audit findings. inspections are for technical experts to identify defects that must be corrected (but. or solicit design alternatives). design critiques. 6. and/or rationale and justification for selecting technologies. with other managers.

These reviews shall be held by an organizational element independent of the unit being reviewed. The objective of the management review is to provide recommendations for the following: (1) Making activities progress according to plan. This review may require additional changes in the SQAP itself. and inspections of the SCMP to ensure that it meets the requirements as stated in software project plans and software requirements documents. standards.47 - . The objective of the Software Configuration Management Plan Review (SCMPR) shall be to verify the SCMP conforms to SCM standards. and SCM integrity levels of the software work products themselves. determine the effectiveness of SCM. monitoring. Measuring compliance with the SCMP consists of conducting audits of SCM activities to determine their compliance with policies and procedures. and resolve SCM non-conformances. 6. Determining the effectiveness of SCM consists of analyzing completion of SCMP tasks. Verifying the SCMP conforms to SCM standards consists of conducting audits of the SCMP to ensure that it meets the requirements of the SCMP standard. then an additional meeting shall be scheduled to complete the management review process. and audits. Each problem areas identified by the review team is recorded. compliance levels of SCM activities. (3) Maintaining global control of the project through adequate allocation of resources. the SCMP meets the needs of the software project. When critical data and information cannot be supplied. The management review process can be applied to new development or to maintenance activities. and ensuring their rapid resolution and closure. measure compliance with the SCMP.9 Software Configuration Management Plan Review (SCMPR) The SCMPR is held to evaluate the adequacy and completeness of the configuration management methods defined in the SCMP. During the review meeting the entire review team examines plans or progress against applicable plans.Managerial reviews are held periodically to assess the execution of all of the actions and the items identified in the SQAP. based on an evaluation of product develop status. and non-conformances arising from managerial reviews. or by a qualified third party. walkthroughs. (2) Changing project direction nor to identify the need for alternative planning. Verifying the SCMP meets the needs of the software project consists of conducting managerial reviews. inspections. Resolving SCM non-conformances consists of identifying. walkthroughs. actions.2. or both. and guidelines. A management review is a formal evaluation of a project level plan or project status relative to that plan by a designated review team.2.10 Post Mortem Review The review is held at the conclusion of the project to assess the development activities . and tracking the issues. 6.

objectively. completeness. purchasing. and the allocation of personnel and facility resources (e. if required. This review is held to evaluate the adequacy (e. and facilities management). information systems. corporate infrastructure support (e. and measurable fashion (in order to ensure that future projects proactively improve their performance). in a highly structured.implemented on that project and to provide recommendations for appropriate actions. and groups.g. It is conducted when a significant portion of the system functional requirements has been established. SSRRs are to determine initial direction and progress of the systems engineering management effort and the convergence upon an optimum and complete configuration. and process quality. human resources. 6. teams. and usability) of user documentation. cooperation. This review will not be conducted by S&IS if a system specification is not required or. cost. and product quality. correctness.3. 6. how well software project objectives were met. and teamwork.1 System/Subsystem Requirements Review (SSRR) External review techniques include a system/subsystem requirements review (SSRR). and most importantly the ability of the organization effectively organize and execute similar projects in the future (if at all). repeatable. is provided by the government. SSRRs are inprocess reviews normally conducted during the system conceptual or validation phase. which immediately follows system requirements analysis.2 System/Subsystem Design Review (SSDR) . computers and software engineering tools). clarity.g. the initial accuracy of quantitative estimates (e. The objective of the SSRR is to ascertain the adequacy of the contractor’s efforts in defining system requirements. Evaluating the effectiveness of the software project also includes evaluating the effectiveness of any necessary replanning and corrective actions. deliverables.. intergroup coordination.3 Other Other reviews and audits may include the user documentation review (UDR). size.g. appropriateness of processes.48 - . communication.. 6. schedule accuracy.. the technical and interpersonal strengths and weaknesses of individuals.g. activities. Such reviews may be conducted at any time but normally will be conducted after accomplishment of functional analysis and preliminary requirements allocation. the appropriate identification and mitigation of software risks. Evaluating the effectiveness of the software project includes evaluating the effectiveness of the software project plan. and critical computer resources). and consistently evaluate the effectiveness of the software project upon its completion. The objective of the project postmortem review is to formally.. appropriateness of work products. software project management and coordination. effort.3.

This review is conducted to evaluate the optimization. and risks associated with the allocated technical requirements. SOTRERs are held to resolve open issues regarding the results of software qualification testing. risk aspects of the particular hardware and software. 6. The point of government certification will be determined by the contracting agency and will depend upon the nature of the program. and completeness of the SOTRER shall be maintained with the functional configuration audit and duplication of effort avoided. For noncombined functional configuration audit/SOTRERs. software requirements and interface requirements specifications. 6.3. If sufficient test results are not available at the functional configuration audit to insure the configuration items will perform in their system environment.4 Software Test Results Review (SOTRER) External review techniques include a software test results review (SOTRER). the contracting agency also reviews the results of informal software testing and any updates to the operation and support documents. correlation. traceability. A successful SOTRR is predicated on the contracting agency's determination that the software test procedures and informal test results form a satisfactory basis for proceeding into software qualification testing.3. When feasible. At SOTRR. which is necessary to successfully conclude the system architectural design. prior to the physical configuration audit. the SOTRER shall be conducted (post physical configuration audit) during system testing whenever the necessary tests have been successfully completed to enable certification of configuration items. which immediately follows software qualification testing. completeness. This review is conducted for each CSCI to determine whether the software test procedures are complete and to assure that the contractor is prepared for formal CSCI testing. Also included is a summary review of the system engineering process. The objective of the SOTRER shall be to verify that the actual performance of the configuration items of the system as determined through test comply with the hardware development specification. and to identify the test report(s)/data which document results of qualification tests of the configuration items.3 Software Test Readiness Review (SOTRR) External review techniques include a software test readiness review (SOTRR). Software test procedures are evaluated for compliance with software test plans and descriptions. Basic manufacturing considerations are reviewed and planning for production engineering in subsequent phases is addressed. the SOTRER shall be combined with the functional configuration audit at the end of configuration item/subsystem testing.External review techniques include a system/subsystem design review (SSDR). correlation. This review is conducted when the system definition effort has proceeded to the point where system characteristics are defined and the configuration items are identified. which immediately follows software integration. and for adequacy in accomplishing test requirements. which produced the allocated technical requirements and of the engineering planning for the next phase of effort. .49 - . and contractor progress in successfully verifying the requirements of the configuration items.

including “training software products. traceability. and completeness of the SYTRER shall be maintained with the functional configuration audit and duplication of effort avoided. and for adequacy in accomplishing test requirements. and to identify the test report(s)/data which document results of qualification tests of the configuration items. the contracting agency also reviews the results of informal system testing and any updates to the operation and support documents.3. system requirements and interface requirements specifications. which immediately follows software installation. At SYTRR. correlation. which immediately follows system integration. SURs are held to resolve open issues regarding the readiness of the software for installation at user sites. which are aimed at finding usability problems in an existing user interface design.50 - . When feasible. 6. and the status of installation preparations and activities.6.6 System Test Results Review (SYTRER) External review techniques include a system test results review (SYTRER). which immediately follows system qualification testing. The objective of the SYTRER shall be to verify that the actual performance of the configuration items of the system as determined through test comply with the hardware development specification. the SYTRER shall be combined with the functional configuration audit at the end of configuration item/subsystem testing. SURs optionally involve conducting usability inspections. prior to the physical configuration audit. This review is conducted for each system to determine whether the system test procedures are complete and to assure that the contractor is prepared for formal system testing. System test procedures are evaluated for compliance with system test plans and descriptions. the software version descriptions. and then using these problems to make recommendations for fixing the problems and improving the usability of . the user and operator manuals. the SYTRER shall be conducted (post physical configuration audit) during system testing whenever the necessary tests have been successfully completed to enable certification of configuration items. For noncombined functional configuration audit/SYTRERs. The point of government certification will be determined by the contracting agency and will depend upon the nature of the program.” if applicable. risk aspects of the particular hardware and software. status of training.3. A successful SYTRR is predicated on the contracting agency's determination that the system test procedures and informal test results form a satisfactory basis for proceeding into system qualification testing. and contractor progress in successfully verifying the requirements of the configuration items.5 System Test Readiness Review (SYTRR) External review techniques include a system test readiness review (SYTRR). SYTRERs are held to resolve open issues regarding the results of system qualification testing.7 Software Usability Review (SUR) External review techniques include a software usability review (SUR). If sufficient test results are not available at the functional configuration audit to insure the configuration items will perform in their system environment.3. 6.

and human factors people step through a scenario. 7. both industry-wide and for the particular application. and develop the software maintenance plan. if applicable. wish-lists of new functions and features. expected internal changes to support new requirements. developers.0 TEST This section shall identify all the tests not included in the SVVP for the software covered by the SQAP and shall state the methods to be used. the software maintenance manuals.the design. pluralistic walkthroughs (meetings where users. guideline reviews (checking the user interface for conformance with a comprehensive list of usability guidelines). types and number of requests received for changes.8 Software Maintenance Review (SMR) External review techniques include a software maintenance review (SMR). their job descriptions. Finally. the experience level of the maintenance staff. and connectivity. the software product specifications. . quantify the software maintenance effort. any existing performance statistics. consistent. including transition of the software engineering environment. actual methods used by programming staff. and new technologies that need to be incorporated. standards inspections (increasing the degree to which a given user interface is similar to the user interfaces of competing products in the marketplace). and the status of transition preparations and activities. current written maintenance methods at the systems and program level. including expected external or regulatory changes to the system. usefulness of the system. 6. number of maintainers. consistency inspections (evaluating user interface consistency across a family of products by designers from multiple projects). number and type of changes during life. and tools used to support the maintenance process and how they are used. adaptability. discussing usability issues associated with dialogue elements involved in the scenario steps). including age since being placed in production. correct. SMRs are also used to determine the necessary software maintenance process. the rate of turnover and possible reasons for leaving. formal usability inspections (a software inspection process used to identify defects in user interfaces). SMRs are used to determine necessary software maintenance effort. SMRs are held to resolve open issues regarding the readiness of the software for transition to the maintenance organization. expected upgrades for performance. Usability inspections consist of heuristic evaluation (having usability specialists judge whether each dialogue element conforms to established usability principles). and repeatable user operations).51 - . the software version descriptions. which immediately follows software acceptance support. new lines of business that need to be supported.3. cognitive walkthroughs (checking to see if the user interface enables intuitive. SMRs are used to determine the software maintenance requirements. and their actual jobs. and feature inspections (used to verify that individual user interface functions conform to system requirements). quality and timeliness of documentation.

plans. and resolving problems identified in both software items and the software development and maintenance process. and documentation support. AND METHODOLOGIES .0 PROBLEM REPORTING AND CORRECTIVE ACTION This section shall: (1) Describe the practices and procedures to be followed for reporting. shall be identified and defined by the test or validation plan and the test or validation procedures. and procedures by software projects.0 TOOLS. identification and definition of software testing methods shall be defined in the test or validation plan. per se. So. and test procedures to be used to perform qualification testing of a software item or a software system or subsystem.Software test methods that shall be enforced by the SQAP. This procedure shall begin with project system managers ensuring that software quality assurance is present on all software projects and end with independent experts reviewing the methods and frequency that software quality assurance will use to provide feedback to software engineering.52 - . which are not covered by the SVVP. and resolving problems identified in both software items and the software development and maintenance process. The SVVP. The practices and procedures to be followed for reporting. 9. The test or validation plan describes the software test environment to be used for the testing. (2) State the specific organizational responsibilities concerned with their implementation. TECHNIQUES. is not the principal test plan. software quality assurance participates in creation of software development plans. test cases. and provide schedules for test activities. The test or validation procedures enable the acquirer to assess the adequacy of the qualification testing to be performed. 8. tracking. • Test or Validation Procedures (TVPR): The purpose of the test or validation procedures is to describe the test preparations. • Software Quality Assurance Policy and Procedure: This procedure establishes the guidelines by which software quality assurance prepares software quality assurance plans for software projects. software quality assurance reviews and audits activities and work products of software projects. software configuration management. • Test or Validation Plan (TVPL): The purpose of the test or validation plan is to describe plans for qualification testing of software items and software systems. identify the tests to be performed. and software quality assurance handles deviations and non-compliances to software standards. shall be identified and defined by the software quality assurance policy and procedure. that shall be enforced by the SQAP. as well as the test or validation procedures. tracking.

non-conformances to numerical tolerances. • Software Audit: The objective of software auditing is to provide an objective compliance confirmation of products and processes to certify adherence to standards. operational and functional failures. or any subjective improvements to the product’s design by the examiners (in order identify defects for later mandatory correction and enable early validation of the product using internal technical experts before it is delivered). engineers. functional flow. without the presence of managers. or technical lead that’s directly responsible for creating or designing a product. In performing the audit. and technical specialists (in order to defend the design concept. guidelines. without any defense from the author or creator of the product. that shall be enforced by the SQAP. not suggest design alternatives or subjective improvements to the product). and software quality modeling. specifications. In short. plans. inspections. state their purposes. solicit a critique of the approach. guidelines.This section shall identify the special software tools. non-conformances to requirements and specifications. supervisors. inspections are for technical experts to identify defects that must be corrected (but. The audit plan establishes a procedure to conduct the audit and for follow-up action on the audit findings. recommendations are reported in addition to the audit results. requirements. and procedures. a detailed design. Audits are performed in accordance with documented plans and procedures. The results of the audit are documented and are submitted to the management of the audited organization. supervisor. In short. defect typing and classification. and describe their use. . or solicit design alternatives). shall include audits. with other managers. specifications. When stipulated by the audit plan. walkthroughs. and/or rationale and justification for selecting technologies. The report includes a list of the items in noncompliance or other issues for subsequent review and action. walkthroughs are intended for managers to solicit design alternatives (without any mandatory action on behalf of the manager or product author). and standards. audit personnel evaluate software elements and the processes for producing them against objective audit criteria.53 - . • Inspection: An inspection is a highly structured and facilitated meeting in which independent technical experts analyze and examine each of the individual product characteristics one-byone. • Walkthrough: A walkthrough is an informal design review meeting in which the manager. design critiques. a technical architecture. and without any consideration of design alternatives. and to any external organizations identified in the audit plan. in order to identify defects. and/or safety hazards. nonconformances to standards. and methodologies that support SQA. or a specific solution to satisfy the product’s requirements or specifications. or technical leads. The special software tools. techniques. or procedures. and methodologies that support SQA. verbalizes the intended operational flow. to the entity initiating the audit. such as contracts. techniques.

secure and document controlled versions of the identified software during all phases of the software life cycle. shall be identified and defined by the software configuration management plan. software interfaces. It describes the processing of anomalies discovered during any software life cycle phase. If so. The minimum set of classifications deemed necessary for a complete data-set are indicated as mandatory.0 CODE CONTROL This section shall define the methods and facilities used to maintain. 10. The number of defects indicates the amount of rework. and priority of defects reported. • Software Quality Modeling: Software quality or defect density is the number of software defects committ4ed per thousand lines of software source code. secure and document controlled versions of the identified software during all phases of the software life cycle.0 MEDIA CONTROL . support the software development and maintenance methodology that fits the software requirements. software. store. A defect density measure—an expression of the number of defects in a quantity of product—can be derived from this measure. • Software Configuration Management Plan (SCMP): The purpose of the software configuration management plan is to provide a structure for identifying and controlling software documentation. that shall be enforced by the SQAP. or documentation. and databases to support all software life cycle phases. and can be used to predict test completion. Arrival rates can indicate product maturity (a decrease should occur as testing is completed). and audits. and it provides comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies. or whether rework is being deferred. tests. store. software source code.• Software Defect Typing and Classification: Software defect typing and classification provides a uniform approach to the classification of anomalies found in software and its documentation. The defects measure quantifies the number. status. Closure rates are an indication of progress. Tracking the length of time that defects have remained open can be use to determine whether progress is being made in fixing defects. 11. This may be implemented in conjunction with a computer program library. and has a direct impact on quality. The methods and facilities used to maintain. It provides useful information on the ability of a supplier to find and fix defects in hardware. policies. and support production of management and product information concerning the status of software baselines. change control. This may be provided as part of the SCMP. More detailed classifications are provided for those projects that require more rigor. releases. organization and management philosophy. standards. Defect density can identify components with the highest concentration of defects. an appropriate reference shall be made thereto.54 - .

and support production of management and product information concerning the status of software baselines. change control. policies. and databases to support all software life cycle phases. This procedures shall begin with project system managers ensuring that documented standards and procedures are used for selecting software subcontractors and . The provisions for assuring that software provided by suppliers meets established requirements. this section shall state the methods that will be used to assure that the software supplier receives adequate and complete requirements. and (b) protect computer program physical media from unauthorized access or inadvertent damage or degradation during all phases of the software life cycle. this section shall state the methods to be used to assure the suitability of the product for use with the software items covered by the SQAP. that shall be enforced by the SQAP. For software that is to be developed. • Software Subcontract Management Policy and Procedure: This procedure establishes the guidelines by which subcontract software managers define software work to be subcontracted. releases. and subcontract software managers make changes to software subcontract agreements. tests.This section shall state the methods and facilities to be used to (a) identify the media for each computer product and the documentation required to store the media. an appropriate reference shall be made thereto. 12. support the software development and maintenance methodology that fits the software requirements. software interfaces. This may be provided as a part of the SCMP. In addition. organization and management philosophy. This section shall also state the methods to be employed to assure that the developers comply with the requirements of this standard. shall be identified and defined by the software configuration management plan. • Software Configuration Management Plan (SCMP): The purpose of the software configuration management plan is to provide a structure for identifying and controlling software documentation. that shall be enforced by the SQAP. For previouslydeveloped software. the supplier shall be required to prepare and implement a SQAP in accordance with this standard. The methods and facilities to be used to identify the media for each computer product and the documentation required to store the media. subcontract software managers select software subcontractors. standards.0 SUPPLIER CONTROL This section shall state the provisions for assuring that software provided by suppliers meets established requirements. and protect computer program physical media from unauthorized access or inadvertent damage or degradation during all phases of the software life cycle. subcontract software managers track software subcontractors. including the copy and restore process. and audits. software source code. If so. subcontract software managers create software subcontract agreements.55 - . including the copy and restore process. shall be identified and defined by the software subcontract management policy and procedure.

policies.0 RECORDS COLLECTION. tests. The training activities necessary to meet the needs of the SQAP. that shall be enforced by the SQAP.0 TRAINING This section shall identify the training activities necessary to meet the needs of the SQAP. shall state the methods and facilities to be used to assemble. software interfaces. and training groups maintain records of training for the organization and software projects. shall be identified and defined by the software configuration management plan. The methods and facilities to be used to assemble. training groups perform training for the organization and software projects. monitor. and maintain the SQA documentation to be retained. and support production of management and product information concerning the status of software baselines. change control.0 RISK MANAGEMENT This section shall specify the methods and procedures employed to identify. releases. 15. AND RETENTION This section shall identify the SQA documentation to be retained. support the software development and maintenance methodology that fits the software requirements.managing software subcontracts and end with software quality assurance reviewing and/or auditing acceptance processes for products of software subcontractors. standards. safeguard. shall be identified and defined by the training program policy and procedure. organization and management philosophy. • Software Configuration Management Plan (SCMP): The purpose of the software configuration management plan is to provide a structure for identifying and controlling software documentation. safeguard. training groups develop and maintain training courses. This procedure shall begin with senior management ensuring that skills and knowledge for software management and technical roles are identified and end with independent experts verifying that training groups follow the organization training plan. and databases to support all software life cycle phases. software source code. • Training Management Policy and Procedure: This procedure establishes the guidelines by which project software managers develop and maintain a training plan for each software project. and maintain this documentation and shall designate the retention period. training groups develop and revise the organization training plan. 14. assess. and audits. 13. MAINTENANCE.56 - . that shall be enforced by the SQAP. .

assess. as defined in the project agreement.57 - . monitor. A software project plan defines the technical and managerial project functions. . activities. that shall be enforced by the SQAP. The methods and procedures employed to identify. and tasks necessary to satisfy the requirements of a software project. and control areas of risk arising during the portion of the software life cycle.and control areas of risk arising during the portion of the software life cycle covered by the SQAP. shall be identified and defined by the software project plan. • Software Project Plan (SPP): The purpose of the software project plan is to serve as a controlling document for managing a software project.

Sign up to vote on this title
UsefulNot useful