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 -

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

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

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

the audits and reviews of the evolving software product. • ANSI/IEEE STD 730. programming -3- . including requirements for source code presentation. the tracking and reporting of such changes. and software joint reviews. UML is a graphically and visually oriented diagramming standard for representing analytical models of software requirements and software designs.1-1989 (IEEE Standard for Software Quality Assurance Plans): The purpose of this standard is to provide uniform. software technical reviews. the IEEE Standard for Reviews and Audits. which serve as controlling documents for managing software projects. such as instructions for a particular position or task. • SPC-94093-CMC Version 01. It may also cover a particular aspect of software operation. the IEEE Standard for Software Quality Assurance Plans. • 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. approval. readability. • 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.The reference documents which the SQAP is principally based upon consist of three documents.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. software products. the review. software records. • OMG Version 1. • ANSI/IEEE STD 1058. minimum acceptable requirements for software activities.0-1996 (IEEE Standard for Software Life Cycle Processes): The purpose of this standard is to provide uniform.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. and the IEEE Standard for Software Life Cycle Processes. • IEEE/EIA 12207. and the control of interface documenation and project supplier SCM.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. define minimum V&V tasks. minimum acceptable requirements for preparation and content of Software Quality Assurance Plans (SQAPs). program structure. or a software system or subsystem. and control of changes. • 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.00. and suggest optional V&V tasks. • 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. a group of related CSCIs.

lint. control and user interface standards. Elliot. 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. declarations. H.. Kirchhoff. Schan. K. Inc. portability. constants. including requirements for files.H.. comments.practices. Milner. character formatting. Prentice Hall. Files include file naming conventions. keyword reference. simple statements. 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. header file content. including requirements for markup tags.M..0. Keppel. variables. statements. identifier naming conventions. and source file content.O. Inc. Wildfire Communications. to include broad classes of software measures. indentation. including requirements for declaration standards. T. N. functions. preprocessor. conditional compilation. macros.P. guidelines for application.. white space. • MIL-STD-1521B-4 June 1985 (Military Standard for Technical Reviews and Audits for Systems. • Patrick. and programming practices. • Cannon. and interaction with C. and improving performance. D.. and Brader. including requirements for file names. R. file organization. T..W. file organization. 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. R.W.W. ANSI C. types. • DoD and US Army Version 4. • BL. Revision 6.. L.. and -4- . and project-dependent standards. reusability object-oriented features. Wittington. naming conventions.. M. miscellaneous. concurrency.. linking. debugging. make. comments. J. and fill-out forms. compound statements. Mitze. inline images. special considerations. naming conventions. 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 Computer Software): The purpose of this standard is to prescribe the requirements for the conduct of technical reviews and audits on systems. portability. E. statements. declarations. J.A. and practical examples. function declarations. using white space. Equipments. including requirements for file organization. operators. and database standards. 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.. whitespace. tables. • Gabryelski. • Sun Microsystems. Miller..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. Spencer. W3C. equipments. L.

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

software coding and testing. software installation. and (c) the relationships between these tasks and the planned major check-points. 3.1 Software Life Cycle The software life cycle phases to which the SQAP applies include system requirements analysis. objectivity.2. schedule. record and report change processing and implementation status. the software project lead. software requirements analysis. • 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. SCM. and software acceptance support. or the software engineering functional manager. and authority from software engineering in order to maintain independence. system integration.3 Organizational Independence The organizational independence of SQA consists of a mutually exclusive chain of authority.1. The sequence of the tasks shall be indicated. for computer software configuration items (CSCI) of a system or segment of a system. (b) the tasks to be performed with special emphasis on software quality assurance activities. Primarily. software detailed design. software qualification testing. software integration.2 Tasks This paragraph shall describe (a) that portion of the software life cycle covered by the SQAP. and thus maintains independent power. functional organization. • System Requirements Analysis Phase: System requirements analysis is the process of developing system-level requirements. software testing. 3. quality. and delivery pressures of software projects. 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. SQA is not functionally subordinate to software engineering. Furthermore. and especially SQA. software architectural design. and verify compliance with specified requirements. software engineering reports to a software project lead and the software engineering functional manager. responsibility. and reporting channels between software engineering. 3. (2) A set of activities designed to evaluate the process by which software work products are developed and/or maintained. and integrity of SQA activities. system architectural design.• 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. for later use by system architectural design. control changes to those characteristics. -6- . status. system qualification testing.

for a CSCI of a system or segment of a system. for a system or segment of a system. (d)—detailed. • Software Requirements Analysis Phase: Software requirements analysis is the process of developing software requirements. including its operational and support environments. for later use by software architectural design. • 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).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. (u)—updated • System Architectural Design Phase: System architectural design is the process of transforming the system-level requirements into an architectural design. for a CSCI of a system or segment of a system. -7- . for later use by software requirements analysis. for later use by software detailed design.

for a CSCI of a system or segment of a system. software detailed design.2 SQA Activities The SQA activities principally consist of auditing the software activities. in order to determine to whether or not to accept the system from the developer. test cases. for later use by software coding and unit testing. and work instructions. for later use by software qualification testing. using acceptance test plans. • 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. • Software Coding and Testing Phase: Software coding and testing is the process of transforming the software detailed design—CSUs—into computer software. for a CSCI of a system or segment of a system. software architectural design. using installation policies. • 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. that have undergone individual software and hardware qualification testing. for later use by software installation. for later use by system integration. for later use by system qualification testing. for a CSCI of a system or segment of a system. 3. for later use by software acceptance support. and test procedures. system architectural design. software requirements analysis. using test cases and test procedures based on system-level requirements. technical reviews. plans. and software records of the software life cycle phases for conformance to software process and software product standards. for later use by software integration. • System Integration Phase: System integration is the process of combining and evaluating CSCIs and HWCIs of a system or segment of a system. software -8- . • 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. • Software Integration Phase: Software integration is the process of combining and evaluating the CSUs that have been implemented and unit tested.• 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. There are SQA activities for each of the twelve software life cycle phases. software products. for CSCIs of a system or segment of a system.2. • 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. including system requirements analysis.

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

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

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

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

SIAR. and UDD (u) resulting from the software architectural design activity. SQA shall audit the SRD and UDD resulting from the software requirements analysis activity. SQA shall audit inspections of the SRD and UDD resulting from the software requirements analysis activity. SQA shall audit the DDD (u). and UDD (u) resulting from the software detailed design activity. TVPL (u). SQA shall audit the TVRR of the software acceptance support activity. SIAR. SQA shall audit walkthroughs of the UDD (u). And. TVPL. TVPR (u). SQA shall audit the TVRR of the system qualification testing activity. SQA shall audit the DDD (p). SDD. and TVRR resulting from the software qualification testing activity. SQA shall audit walkthroughs of the SRS resulting from the system requirements analysis activity.3. TVPL. SDD. SQA shall audit walkthroughs of the SARAD resulting from the system architectural design activity. SQA shall audit the DDD (d). and TVRR resulting from the software integration activity. SQA shall audit walkthroughs of the DDD (d). SQA shall audit walkthroughs of the TVPR (u) and TVRR of the system integration activity. TVPL (u). TVPL (u). UDD (u). UDD (u). SQA shall audit the TVPR (u) and TVRR of the system integration activity. and TVRR resulting from the software qualification testing activity. and TVRR resulting . and TVRR resulting from the software coding and testing activity. SQA shall audit the SIP of the software installation activity. SQA shall audit walkthroughs of the SRD and UDD resulting from the software requirements analysis activity. SAD.13 - . and UDD (u) resulting from the software architectural design activity. 3. and UDD (u) resulting from the software detailed design activity. SQA shall audit the UDD (u). SQA shall audit walkthroughs of the DDD (u). SQA shall audit inspections of the DDD (p). and UDD (u) resulting from the software architectural design activity. SAD. TVPL (u). and TVRR resulting from the software coding and testing activity. UDD (u). SAD. SQA shall audit the TVRR of the software acceptance support activity. SQA shall audit inspections of the SRS resulting from the system requirements analysis activity.SARAD resulting from the system architectural design activity. TVPR. SQA shall audit walkthroughs of the SIP of the software installation activity. And. TVPL (u). and UDD (u) resulting from the software detailed design activity. SIDD (d). SQA shall audit inspections of the DDD (d). TVPR. SQA shall audit inspections of the DDD (u). UDD (u). SIDD (d). UDD (u). SIDD (p).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. SIDD (p). TVPR. SQA shall audit walkthroughs of the DDD (p). 3. SIDD (p). SIDD (d). SQA shall audit the SOIP. SQA shall audit walkthroughs of the TVRR of the system qualification testing activity. SQA shall audit inspections of the SARAD resulting from the system architectural design activity. TVPL. TVPL (u).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. TVPR (u). SDD. SQA shall audit walkthroughs of the SOIP. and TVRR resulting from the software integration activity.

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

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

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

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

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

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

) 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. • Installation and setup. • Access control. • Referenced documents. SQA shall conduct an audit of the UDD to verify the following properties: • Scope. A method of describing user-identified errors or problems to the developer or the owner of the software shall be described. • Document overview. • Access to the software. • Software organization and overview of operation. • Equipment familiarization. • Software environment. • First-time user of the software. • Identification. . (Embedded software that has no direct user interaction has no need for user documentation and is therefore exempted from this requirement.20 - . • System overview. • Software inventory. • Software summary. • Software application. • Contingencies and alternate states and modes of operation. • Security and privacy. • Assistance and problem reporting. • Initiating a session.corrective actions described.

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

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

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

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

logical. physical). including descriptions of applicable design levels (e. . internal. 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.. and manual operations. software items. • Rationale for allocation of hardware items. The database design description may also describe the software units used to access or manipulate the data. SQA shall conduct an audit of the DDD to verify the following properties: • Generic description information.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. • Concept of execution. • Manual operations identification. • Design of the database. • Software item identification. • Rationale. 4. • Precedence and criticality of requirements. conceptual.3. that is.3. 4. • Database overview and identification. • Reference to design description of software used for database access or manipulation. • Hardware item identification.• Packaging requirements.g. The database design description is used as the basis for implementing the database and related software units.4 Database Design Description (DDD) The purpose of the database design description is to describe the design of a database.25 - . • System overview and identification. SQA shall conduct an audit of the SARAD to verify the following properties: • Generic description information.

. hardware item. diagrams).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. • Software component identification. diagrams).. subsystem.g. • Data recording. SQA shall conduct an audit of the SIDD to verify the following properties: • Generic description information. The test or validation plan describes the software test environment to be used for the testing. diagrams). The software interface design description may describe any number of interfaces. source language. SQA shall conduct an audit of the TVPL to verify the following properties: • Generic plan information. reduction. • Test progression..• Rationale for database design. . manual operation. software item.g. and analysis. • Software unit identification. • External interface identification.3. • General test conditions. • External-software item interface definition (e. identify the tests to be performed. source language. • Test levels. 4. • Software component-software component interface definition (e. • Test classes.26 - .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. and provide schedules for test activities.3. 4. source language. • Software item-software item interface definition (e.g. or other system component.

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

• Prerequisite conditions. • Rationale for decisions. • Criteria for evaluating results. • Expected test results. • Overall assessment of the software tested. • Generic procedure information. 4.3. • Requirements addressed. • Overview of test results. SQA shall conduct an audit of the TVRR to verify the following properties: • Generic report information. requirements. • Test identifier. software. • Requirements traceability. a software system or subsystem. other) for each test.28 - . . • Test objectives. and rationale. or other software-related item. • Instructions for conducting procedure.SQA shall conduct an audit of the TVPR to verify the following properties: • Test or Validation Procedures.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. • Identification of test configuration. • Test descriptions. • Test input. • Identification of test author. The test or validation results report enables the acquirer to assess the testing and its results. • Test preparations (hardware. • System identification and overview.

• Test responsibilities. • Test data.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. • Scope. • Rationale for decisions. • Issuing organization. • Test procedures.3. . SQA shall conduct an audit of the SOIP to verify the following properties: • Generic plan information.29 - . • Detailed test results. • Test requirements. • Problems encountered. • Test log. SQA shall conduct an audit of the SIAR to verify the following properties: • Date of issue and status.3. 4. • Test schedule.• Impact of test environment. • Test summary. • Deviations from test cases/procedures.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. • Test identifier. 4.

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

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

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

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

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

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 -

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

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

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

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

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

External review techniques include a software preliminary design review (SPDR). which immediately follows software architectural design. 6. this review focuses on the evaluation of the progress. and UDD form a satisfactory basis for proceeding into software architectural design. SRD. subsystem.2.43 - . Finally this review establishes the existence and compatibility of the physical and functional interfaces among the configuration items and other items of equipment. and schedule basis) of the selected design approach. cost. and technical adequacy of the selected top-level design and test approach. 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. and risk resolution (on a technical. A successful SRR is predicated upon the contracting agency's determination that the COD. compatibility between software requirements and preliminary design. 6. This review is conducted for each configuration item or aggregate of configuration items to evaluate the progress. The SRR is conducted when CSCI requirements have been sufficiently defined to evaluate the contractor's responsiveness to and interpretation of the system. facilities. which immediately follows software requirements analysis. technical adequacy. and personnel.6.2. or prime item level requirements. and on the preliminary version of the operation and support documents. and evaluates the degree of definition and assesses the technical risk associated with the selected manufacturing methods/processes.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.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. computer software. External review techniques include a software critical design review (SCDR). External review techniques include a software requirements review (SRR). This review is conducted for each configuration . For configuration items. consistency.2. this review determines their compatibility with performance and engineering specialty requirements of the HWCI development specification. For CSCIs. which immediately follows software detailed design.

Verifying the SVVR meets the needs of the software project consists of conducting managerial reviews. computer software and personnel. assesses configuration item risk areas (on a technical. 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.44 - . and test characteristics of the design solution. and schedule basis). and software quality and reliability levels of the software work products themselves.2. monitoring. Determining the effectiveness of software V&V consists of analyzing completion of SVVP tasks. and non-conformances arising from managerial reviews. measure compliance with the SVVP. 6. the SVVP meets the needs of the software project. 6. Measuring compliance with the SVVP consists of conducting audits of software V&V activities to determine their compliance with policies and procedures. Finally. and tracking the issues. and on the adequacy of the operation and support documents.item when detail design is essentially complete. This review also establishes the detailed design compatibility among the configuration items and other items of equipment. walkthroughs. walkthroughs.2. and ensuring their rapid resolution and closure.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. facilities. and assesses the results of the producibility analyses conducted on system hardware. For CSCIs. performance. The objective of the Software Verification and Validation Plan Review (SVVR) shall be to verify the SVVP conforms to software V&V standards. compliance levels of software V&V activities. inspections. Resolving software V&V non-conformances consists of identifying. this review focuses on the determination of the acceptability of the detailed design. and resolve software V&V non-conformances. and audits. determine the effectiveness of software V&V. cost. 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. the purpose of this review is to review the preliminary hardware product specifications.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. Test data shall be reviewed to verify that the hardware or computer software performs as required by its functional/ allocated . and inspections of the SVVP to ensure that it meets the requirements as stated in software project plans and software requirements documents. actions. 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.

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. Software audits are independent evaluations of software activities and software work products by software quality assurance. a technical understanding shall be reached on the validity and the degree of completeness of the Software Test Reports. Walkthroughs are informal design review meetings held principally by software project managers to elicit comments and feedback on their design solutions.2. and manuals for CSCIs. specifications. the Computer System Diagnostic Manual (CSDM). walkthroughs. technical data and tests utilized in production of HWCIs and a detailed audit of design documentation.7 In-Process Audit In-process audits of a sample of the design are held to verify consistency of the design. namely software . and inspections. 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. For software.45 - . For configuration items developed at Government expense. Inspections are expertly facilitated evaluations of software products by domain experts. and as appropriate. software audits. all subsequent changes are processed by engineering change action. After successful completion of the audit. an FCA shall be a prerequisite to acceptance of the configuration item. listings.2. Software User's Manual (SUM).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. 6. 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. Computer System Operator's Manual (CSOM). The PCA includes a detailed audit of engineering drawings. For software.configuration identification. 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. 6. 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.

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

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

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

This review is conducted to evaluate the optimization. and completeness of the SOTRER shall be maintained with the functional configuration audit and duplication of effort avoided. 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.3. prior to the physical configuration audit. At SOTRR.49 - . and to identify the test report(s)/data which document results of qualification tests of the configuration items. If sufficient test results are not available at the functional configuration audit to insure the configuration items will perform in their system environment. 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. which immediately follows software qualification testing. For noncombined functional configuration audit/SOTRERs. software requirements and interface requirements specifications. traceability. Software test procedures are evaluated for compliance with software test plans and descriptions. When feasible. the contracting agency also reviews the results of informal software testing and any updates to the operation and support documents. and contractor progress in successfully verifying the requirements of the configuration items. the SOTRER shall be combined with the functional configuration audit at the end of configuration item/subsystem testing. 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.3 Software Test Readiness Review (SOTRR) External review techniques include a software test readiness review (SOTRR). and for adequacy in accomplishing test requirements. SOTRERs are held to resolve open issues regarding the results of software qualification testing. 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. 6. which is necessary to successfully conclude the system architectural design. The point of government certification will be determined by the contracting agency and will depend upon the nature of the program. completeness. correlation. 6. .3. which produced the allocated technical requirements and of the engineering planning for the next phase of effort.4 Software Test Results Review (SOTRER) External review techniques include a software test results review (SOTRER).External review techniques include a system/subsystem design review (SSDR). and risks associated with the allocated technical requirements. 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. Basic manufacturing considerations are reviewed and planning for production engineering in subsequent phases is addressed. correlation. Also included is a summary review of the system engineering process. risk aspects of the particular hardware and software.

the contracting agency also reviews the results of informal system testing and any updates to the operation and support documents.3. and for adequacy in accomplishing test requirements.50 - .6 System Test Results Review (SYTRER) External review techniques include a system test results review (SYTRER). and then using these problems to make recommendations for fixing the problems and improving the usability of . prior to the physical configuration audit. At SYTRR. which immediately follows system qualification testing. SURs optionally involve conducting usability inspections. system requirements and interface requirements specifications. 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. For noncombined functional configuration audit/SYTRERs.3. correlation. SURs are held to resolve open issues regarding the readiness of the software for installation at user sites. 6. and contractor progress in successfully verifying the requirements of the configuration items. status of training. When feasible. 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.3. The point of government certification will be determined by the contracting agency and will depend upon the nature of the program. SYTRERs are held to resolve open issues regarding the results of system qualification testing. 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.5 System Test Readiness Review (SYTRR) External review techniques include a system test readiness review (SYTRR). which are aimed at finding usability problems in an existing user interface design. and completeness of the SYTRER shall be maintained with the functional configuration audit and duplication of effort avoided. risk aspects of the particular hardware and software. 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. and to identify the test report(s)/data which document results of qualification tests of the configuration items. which immediately follows software installation. traceability. which immediately follows system integration.” if applicable. including “training software products.6. 6.7 Software Usability Review (SUR) External review techniques include a software usability review (SUR). System test procedures are evaluated for compliance with system test plans and descriptions. the software version descriptions. the user and operator manuals. If sufficient test results are not available at the functional configuration audit to insure the configuration items will perform in their system environment. the SYTRER shall be combined with the functional configuration audit at the end of configuration item/subsystem testing. and the status of installation preparations and activities.

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

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

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

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

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

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

and control areas of risk arising during the portion of the software life cycle covered by the SQAP.57 - . assess. and tasks necessary to satisfy the requirements of a software project. activities. as defined in the project agreement. that shall be enforced by the SQAP. The methods and procedures employed to identify. A software project plan defines the technical and managerial project functions. . monitor. 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. and control areas of risk arising during the portion of the software life cycle.

Sign up to vote on this title
UsefulNot useful