Explorer

Content

Software Quality Management

Introduction

Fundamentally software is a product and as such the mandated requirements for quality apply. How they are applied; and specific quality assurance activities, tools and techniques need to be modified to address the differing needs of software lifecycle.

What is the purpose of the guidance ?

The Software Quality Management (SQM) guidance [86KB PDF] is intended to provide supplementary quality management guidance and information to help users to address the differing needs or risks related to software acquisition and support.

The guidance assumes that the reader is already familiar with general content of this ‘Managing Quality’ website, and in particular the sections titled Achieving Quality and Project Quality Strategy.

Who is the guidance for ?

The guidance is aimed at MOD personnel, Suppliers to the MOD and consultants (including 3rd Party Certification bodies) involved in activities that relate to MOD acquisitions with a software element.

What is the expected Outcome ?

The expected outcome of the application of the SQM guidance is:

Supplier selection criteria will include appropriate certification and process maturity assessment as appropriate to the software acquisition.
Appropriate Quality Assurance standards will be invoked in contracts with a software element.
Government Quality Assurance Surveillance (GQAS) will be applied according to risk, to assure contractual requirements relating to software quality are and will be met.

Change History

February 2009: Software Quality Assurance topic replaced with completely revised guidance contained within the Software Quality Management topic and download.