Documentation Standard
Section 3.3 - Model Text

3.3 Changes and revisions to associated documentation.

This paragraph is applicable to documents that do not establish a baseline or will eventually be used as a baseline as defined by the applicable development plan.

3.3.1 General.

The associated documentation shall be traceable, handled, stored, responsive to change of requirements and consistent with the relevant program plan. The documentation will be reviewed and approved for adequacy by authorized personnel prior to issue.
This control shall ensure that:

• the pertinent issues of appropriate documents are available at all locations where operations essential to effective function are performed;
• obsolete documents are promptly removed from points of issue or use.

Changes may be proposed using document Change Requests as identified in the specific program plan. These will enable a change record for treaceability purposes to be produced if necessary.
A master list or the equivalent document control procedure shall be established by the relevant Configuration Control centre to identify the current revision of the documents in order to preclude the use of non-applicable documents.

3.3.2 Changes.

Changes to these documents shall be prepared, processed, reviewed and approved by the same function/organization that performed the original review and approval unless specifically designated otherwise. Where practicable, the nature of the change shall be identified in the document or appropriate attachments.
An example of the recommended change method should be described in the specific program plan document change procedures, e.g., Software development plan, etc.

3.3.3 Revisions.

Associated documents shall be re-issued after a practical number of changes have been made. Revised documentation shall be prepared, processed, issued, and identified in the same manner as the document it supersedes. The identification issue number will be incremented in accordance with the technical numbering standard, when applicable. Change bars or similar methods shall be used to identify where the changes have been made with respect to the superseded issue. A brief summary detailing the change(s) or correction(s) incorporated into the document shall be provided in the section identified as NOTES and paragraph identified as "Changes from previous issue" or "Identification of changes""; (normally section 6).
During development, software units will conform to the PIN scheme defined in the relevant project technical numbering standard.

LE FastCounter

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
Originated 7th June 1995.