Software quality assurance plan template

Software quality assurance plan template

Software quality assurance plan template
Software quality assurance plan template

Free Software quality assurance plan template in word

General Tailoring Guidelines

This document is a template for a Software Quality Assurance Plan intended for use by Code 303, Assurance Management Office (AMO) personnel as the basis for a mission-specific Software Quality Assurance Plan.

There are three general types of text format:  Text in Black, Text in Blue with < >, Text in Blue with [ ] and Text underlined in blue.

Text in Black: Text in this style, black, is used for text that is equally applicable to all Software Quality Assurance Plans and will be included in the Software Quality Assurance Plan without modification. All document section headings are in the same category.

Text in Blue with < >: Text in this style, <blue>, is used to indicate that the text needs to be updated with project specific information such as the project name, persons name, persons title, date, revision #, Document Control Number, etc..

Text in Blue with [ ]: Text in this style, [blue], is used to indicate that there is additional instruction for tailoring text in any specific section.  Delete this style, [blue], text before the document is finalized.

Text underlined in Blue: Text in this style, blue, is used to indicate active links.  These links are usually to project or software assurance websites.  The text color may very depending on each persons personal computer settings/configuration.

All components of the table of contents will be addressed, but the level of detail is left up to the software quality personnel. The length and level of detail of the Software Quality Assurance Plan should be commensurate with the scope and complexity of the project.

Section headings may be added where necessary, but existing headings should not be modified or deleted. If a particular section is not applicable to the specific Software Quality Assurance Plan under production, that fact should be noted under the section heading, together with a brief explanation.

The purpose of this Software Quality Assurance (SQA) Plan is to establish the goals, processes, and responsibilities required to implement effective quality assurance functions for the <Project Name> project.

The <Project Name> Software Quality Assurance Plan provides the framework necessary to ensure a consistent approach to software quality assurance throughout the project life cycle. It defines the approach that will be used by the SAM and Software Quality (SQ) personnel to monitor and assess software development processes and products to provide objective insight into the maturity and quality of the software.  

The systematic monitoring of <Project Name> products, processes, and services will be evaluated to ensure they meet requirements and comply with National Aeronautics and Space Administration (NASA), Goddard Space Flight Center (GSFC), and <Project Name> policies, standards, and procedures, as well as applicable Institute of Electrical and Electronic Engineers (IEEE) standards.

This plan covers SQA activities throughout the <identify phases, formulation and implementation> phases of the <Project Name> mission.  Indicate whether or not SQA activities will continue through operations and maintenance of the system.

Enter a brief description of the project, the suppliers of the software, the software items covered by the plan, and their intended use.

This section describes the management organizational structure, its roles and responsibilities, and the software quality tasks to be performed.

3.1-Management Organization
<Project Name> efforts are supported by numerous entities, organizations and personnel (see <Project Name> internal website for a detailed organizational chart).  Relevant entities/roles that are of interest and applicable to this SQA Plan and the software assurance effort are described at a high level below.

[Enter a copy of the project’s management organizational chart or the project’s website where this information can be found.  This chart should reflect the project’s interface with Code 303.]

3.1.1-<Project Name> Project Office
The <Project Name> Project Office at NASA GSFC is responsible for management of project objectives within the guidelines and controls prescribed by NASA Headquarters, GSFC Management, and the <Project Name> Project Plan. The Project Manager (PM) from GSFC Code <enter Code> is specifically responsible for the success of the <Project Name> Project, including but not limited to cost, schedule, and quality.

3.1.2-Assurance Management Office
The Assurance Management Office (AMO), Code 303, provides mission assurance support to NASA GSFC programs and projects (Reference 303-PG-1060.1.2).  The AMO is comprised of civil service Systems Assurance Managers (SAMs), Quality Assurance Specialists (QASs), and Product Assurance Engineers (PAEs).  The SAM assigned to a project is an AMO civil service representative responsible for supporting the Project Manager in the coordination of the definition and implementation of a Project Mission Assurance Program.

The SAM provides Project Management with visibility into the processes being used by the software development teams and the quality of the products being built.  The SAM is matrixed to the <Project> project and maintains a level of independence from the project and the software developers.  Risk escalation begins at the project level, and extends to the AMO and the Office of Systems Safety and Mission Assurance (OSSMA), Code 300.

In support of software quality assurance activities, the SAM has assigned and secured Software Quality personnel from the Mission Assurance Services Contract (MASC) to coordinate and conduct the SQ activities for the project and identify and document noncompliance issues.  In the future and on an as needed basis, SQ personnel support from the Supplier Assurance Contract (SAC) and/or Defense Contract Management Agency (DCMA) may be utilized to support the SQ activities at remote (non-GSFC) locations.

Additional support personnel may also include OSSMA Safety and Reliability and NASA Independent Verification and Validation (IV&V) personnel from the NASA IV&V Facility in Fairmont, WV.   For additional details on IV&V activities, reference the IV&V Memorandum of Agreement (MOA) and/or the IV&V Project Plan (IVVP).  [Identify which IV&V agreements/plans are applicable to your project.]

This section summarizes the tasks (product and process assessments) to be performed during the development, operations, and maintenance of software. These tasks are selected based on the developer’s Project Schedule, Software Management Plan (SMP) (and/or Software Maintenance Plan) and planned deliverables, contractual deliverables, and identified reviews.  

Reference 303-PG-7120.2.1, Procedure for Developing and Implementing Software Quality Programs, for additional information on the various process and product assessments.  Reference 303-WI-7120.2.2, Software Quality Assessment Process, for specific instructions on conducting process and product assessments.

3.2.1-Product Assessments
The following are typical product assessments that may be conducted by SQ personnel.  See the SQ Activity Schedule for the planned assessments:
  • Peer Review packages 
  • Document Reviews (see Section 4, Documentation)
  • Software Development Folders
  • Software Configuration Management (configuration baselines, configuration change requests, and change control records)
  • Test results (e.g., requirements traceability matrix, test reports)
3.2.2-Process Assessments
The following are typical process assessments that may be conducted by SQ personnel.  See the SQ Activity Schedule for the planned assessments:
  • Project Planning 
  • Project Monitoring and Control 
  • Measurement and Analysis 
  • System/Subsystem Reviews 
  • Peer Reviews 
  • Requirements Management 
  • Software Configuration Management and Configuration Audits (FCA/PCA) 
  • Test Management (Verification & Validation) 
  • Software Problem Reporting and Corrective Action
  • Risk Management
  • Supplier Agreement Management

3.3-Roles and Responsibility
This section describes the roles and responsibilities for each assurance person assigned to the <Project Name> Project.

Responsibilities include, but are not limited to:
  • Secure and manage SQ personnel resource levels 
  • Ensure that SQ personnel have office space and the appropriate tools to conduct SQ activities 
  • Provide general guidance and direction to the SQ personnel responsible for conducting software quality activities and assessments 
  • Issue Letters of Delegation, MASC Service Orders, and SAC task orders to initiate software support services (as required)
  • Provide AMO with weekly and quarterly software status (per 303-PG-1060.1.1, Systems Assurance Manager Reporting) 
  • Assist SQ personnel in the resolution of any noncompliance, issues and/or risks identified as a result of software quality activities
  • Escalate any noncompliance to project management
3.3.2-Software Quality Personnel
Responsibilities include, but are not limited to:
  • Develop and maintain the project software quality assurance plan 
  • Generate and maintain a schedule of software quality assurance activities 
  • Conduct process and product assessments, as described within this plan, using objective criteria 
  • Interface with Safety, Reliability, and IV&V personnel on software assurance activities 
  • Identify and document noncompliance, observations, and risks from all software assurance related activities to the SAM
  • Communicate results from assessments with relevant stakeholders
  • Ensure resolution of noncompliance and escalate any issues that cannot be resolved within the project
  • Identify lessons learned that could improve processes for future products 
  • Develop and maintain metrics
3.3.3-Other OSSMA Personnel
The Systems Safety and Reliability Office, Code 302, provides NASA GSFC projects with Safety and Reliability support.  The following are the primary responsibilities for Safety and Reliability personnel in support of software assurance.

3.4-Software Assurance Estimated Resources
Staffing to support software assurance (i.e., quality, safety, and reliability) activities must be balanced against various project characteristics and constraints, including cost, schedule, maturity level of the providers, criticality of the software being developed, return on investment, perceived risk, etc.

The staffing resource levels provided in the table below represent what has currently been agreed upon between Project Management and the SAM.  For applicable IV &V resources, see the <Project Name> IV&V MOA or IVVP. As the project’s efforts progress, these staffing resource levels may be revisited and updated as necessary to complete the activities/tasks described within this plan.  [NOTE:  Table 3-2 can be omitted from the SQAP so long as a reference to the information is provided and the resource information is maintained.]

Download also:

Post a Comment

Previous Post Next Post