7428795 IEEE Software Quality Assurance Plan Template | Software Testing | Source Code

SOFTWARE QUALITY ASSURANCE PLAN TEMPLATE

(BASED ON ANSI/IEEE STD 730.1-1989)

1.0 1.1 1.2 1.3 1.4 2.0 3.0

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

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

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

- ii -

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

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

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

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

- iii -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- 35 -

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

- 36 -

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

- 37 -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful