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 -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.