Documentation Guidelines - Requirements Engineering and Management for Software Development Projects - page 226

Table A.1 Revision History Block

Version
Number

Details of Changes Prepared

by

Approved
by

Date of
Approval

3. The name of our organization and the month and year of preparation of the
document shall be placed just above the revision history block. These will be
two lines in font size 14
4. There will be a revision history block at the bottom of the page. The revision
history block shall be as depicted in Table A.1 .

A.2.3 Table of Contents

All documents with 5 sections or more shall have a table of contents page. It will
be on a separate page. It shall be prepared using the table of contents feature and
shall be set to ''formal'' type. It shall be the next page after the title page.

A.2.4 Content Pages

Content pages shall start on a fresh page after the table of contents page and will
continue till the end of the document.

A.2.5 Terminology

All the technical terminology will conform to IEEE standard 610 ''IEEE Standard
Glossary of Software Engineering Terminology''. If a customer enforces a
different standard, a waiver needs to be obtained for using a different set other that
IEEE standard 610.

A.2.6 Abbreviations

All abbreviations need to be aligned with internationally understood abbreviations.
When there is room for doubt or if the abbreviation is not found in any
international standards, the full form is to be given within brackets the first time
the abbreviation is used in the document. The following guidelines shall be
followed when using abbreviations: