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 TRAINING.......... AND 13.....0 RECORDS COLLECTION.................... 56 ......................................................... 55 COLLECTION......... 56 .................................................................................................................................................................................. MAINTENANCE....................................................0 SUPPLIER CONTROL .......................................... AND RETENTION .......... 12....... .......CONTROL ........................................iv - .............. 14...............................0 RISK MANAGEMENT .... ......................................................................... 56 14..................0 TRAINING ............. 15...................................................................

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• Test responsibilities.29 - . 4. • Detailed test results.11 Software Integration Audit Report (SIAR) The purpose of the software integration audit report is to describe the results of an independent audit of software qualification testing activities and work products. • Test schedule. • 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. SQA shall conduct an audit of the SOIP to verify the following properties: • Generic plan information. • Test log.3.• Impact of test environment. • Scope. SQA shall conduct an audit of the SIAR to verify the following properties: • Date of issue and status. • Problems encountered. • Test summary. • Test requirements. • Test data.3. • Rationale for decisions. • Issuing organization. • Test procedures.

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

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

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

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

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

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 -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful