<Company Name>
<Project Name>
Programming Guidelines
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in
square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author
and should be deleted before publishing the document. A paragraph entered following this style will
automatically be set to normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select
File>Properties and replace the Title, Subject and Company fields with the appropriate information for
this document. After closing the dialog, automatic fields may be updated throughout the document by
selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must
be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the
field contents. See Word help for more information on working with fields.]
<Project Name> Version: <1.0>
Programming Guidelines Date: <dd/mmm/yy>
<document identifier>
Revision History
Date Version Description Author
<dd/mmm/yy> <x.x> <details> <name>
Confidential <Company Name>, 2026 Page 2 of 4
<Project Name> Version: <1.0>
Programming Guidelines Date: <dd/mmm/yy>
<document identifier>
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. Code Organization and Style
3. Comments
4. Naming
5. Declaration
6. Expressions and Statements
7. Memory Management
8. Error Handling and Exceptions
9. Portability
10. Reuse
11. Compilation Issues
12. Annex: Summary of Guidelines
Programming Guidelines
1. Introduction
[The introduction of the Programming Guidelines should provide an overview of the entire document. It
should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of the
Programming Guidelines.]
1.1 Purpose
[Specify the purpose of the Programming Guidelines.]
1.2 Scope
[A brief description of the scope of the Programming Guidelines; what Project(s) it is associated with and
anything else that is affected or influenced by this document.]
1.3 Definitions, Acronyms, and Abbreviations
[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly
interpret the Programming Guidelines. This information may be provided by reference to the project’s
Confidential <Company Name>, 2026 Page 3 of 4
<Project Name> Version: <1.0>
Programming Guidelines Date: <dd/mmm/yy>
<document identifier>
Glossary.]
1.4 References
[This subsection provides a complete list of all documents referenced elsewhere in the Programming
Guidelines. Identify each document by title, report number if applicable, date, and publishing
organization. Specify the sources from which the references can be obtained. This information may be
provided by reference to an appendix or to another document.]
1.5 Overview
[This subsection describes what the rest of the Programming Guidelines contains and explains how the
document is organized.]
2. Code Organization and Style
[A description of the size of a module, layout of a module, space, nesting, legibility, and so on.]
3. Comments
[A description of the use of comments.]
4. Naming
[A description of how each kind of entity, such as types, variables, and subprograms, will be named.]
5. Declaration
[A description of how declarations will be written.]
6. Expressions and Statements
[A description of how expressions and statements will be written.]
7. Memory Management
[A description of how memory will be managed.]
8. Error Handling and Exceptions
[This section gives rules and guidelines on how error handling and exceptions will be handled.]
9. Portability
[This section describes special rules to ensure portability across different platforms and compilers.]
10. Reuse
[This section gives rules and guidelines to foster easier reuse.]
11. Compilation Issues
[This section describes dependencies between modules, compiler directives, and so on.]
12. Annex: Summary of Guidelines
[This section summarizes all guidelines; one line for each.]
Confidential <Company Name>, 2026 Page 4 of 4