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 -

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

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

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

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

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

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

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

for a CSCI of a system or segment of a system. for a CSCI of a system or segment of a system. (d)—detailed. including its operational and support environments. -7- . for later use by software requirements analysis. • Software Architectural Design Phase: Software architectural design is the process of transforming software requirements into a top-level software design consisting of computer software components (CSC). for later use by software architectural design. (u)—updated • System Architectural Design Phase: System architectural design is the process of transforming the system-level requirements into an architectural design. • Software Requirements Analysis Phase: Software requirements analysis is the process of developing software requirements. for later use by software detailed design. for a system or segment of a system.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 system qualification testing. for CSCIs of a system or segment of a system. for later use by software qualification testing. and software records of the software life cycle phases for conformance to software process and software product standards. and work instructions. • 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. using test cases and test procedures based on system-level requirements. • Software Qualification Testing Phase: Software qualification testing is the process of dynamically evaluating computer software using test cases and test procedures based on CSCI-level software requirements. software products. technical reviews. that have undergone individual software and hardware qualification testing. using installation policies. There are SQA activities for each of the twelve software life cycle phases. using acceptance test plans. software architectural design. including system requirements analysis. • System Integration Phase: System integration is the process of combining and evaluating CSCIs and HWCIs of a system or segment of a system. • Software Coding and Testing Phase: Software coding and testing is the process of transforming the software detailed design—CSUs—into computer software.2.• 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). software requirements analysis. and test procedures. test cases. • Software Acceptance Support Phase: Software acceptance support is the process of assisting customers and end-users dynamically evaluate a system or segment of a system. for a CSCI of a system or segment of a system.2 SQA Activities The SQA activities principally consist of auditing the software activities. • System Qualification Testing Phase: System qualification testing is the process of dynamically evaluating integrated CSCIs and HWCIs of a system or segment of a system. for a CSCI of a system or segment of a system. for later use by system integration. in order to determine to whether or not to accept the system from the developer. for later use by software integration. plans. 3. for later use by software installation. for later use by software acceptance support. software -8- . software detailed design. system architectural design. for a CSCI of a system or segment of a system. for later use by software coding and unit testing. • Software Integration Phase: Software integration is the process of combining and evaluating the CSUs that have been implemented and unit tested. procedures.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.