The objective of the Software Quality Program Plan
is to ensure that developing software is evaluated to determine
that the desired quality has been achieved. This is performed
by creating a process to provide independent assessment of whether
the desired quality has been achieved.
The plan shall be applicable for all software products and processes
declared for use on a specific software development project.
The title page shall be laid out in accordance with
the requirement in the documentation standard and contain the
following information:
The scope shall identify the specific program or project, state the purpose and provide an introduction to the document.
For example Section 1 see SQPP section 1
This section shall identify all the applicable and
referenced documents which are required for the specific program
or project.
Also, the order of precedence and availability (source) of the
documents shall be stated.
Identify any contractual and non-contractual provisions.
For example Section 2 see SQPP section 2
Section 3 defines the organization and resources necessary for a specific software development project. It shall describe the organization(s) responsible for fulfilment of, and for ensuring compliance with, Software Quality Program requirements. The authority and responsibility of each organization and its relationship to other organizational entities (for example, configuration management and control, systems engineering management, etc.,). A diagram shall be used to illustrate the structure of the organization(s) performing Software Quality Program Activities and their position within the project management system. If more than one organization is involved, the precise structure and personnel of each organization and their interrelationships shall be specified.
Additionally a description of all resources necessary for successful performance of the development will be defined in particular:
A schedule for the SQP activities will be provided. For each activity, the schedule shall indicate activity initiation, dependencies on other events (such as availability of draft documents), and activity completion times. The schedule shall also show all key development milestones, such as formal reviews, audits, and key meetings. For an example Section 3 see SQPP section 3
Section 4 defines the necessary SQP procedures, tools,
and records.
Procedures used by SQP are as follows:
Tools to be used in the
SQP are:
Software Quality Records describe the plans for preparing, maintaining, and making available for acquirer review, records of each SQP activity performed. For an example Section 4 see SQPP section 4
The section 'NOTES' shall contain information of
a general or explanatory nature that may be helpful, but is not
mandatory, for example, Acronyms, abbreviations, definitions,
etc. used throughout the document.
For an example Section 5 see SQPP section 5
Appendixes may be used to provide information separately for convenience in document maintenance (charts, classified data, etc.).
For an more information and example appendix see APPENDIX model text
Example SQPP SQPP model text
The organization(s) need not be structural groups but may be specialist persons with the necessary experience. Training should be provided for staff in a wide range of disciplines to allow a cross discipline skill to be developed.
Back to Home page MANAGING STANDARDS Home page
Please send any beneficial comments or identification of errors
using the following form to: kenr@wysywig.airtime.co.uk