ICW Naming Conventions
versions of the same files during the ICW
development process. Tracking these files can
pose a significant management problem unless
developers and reviewers follow a standardized
file naming convention.
The following format is recommended as a
file/project naming convention. Although you
can adopt your own naming convention using
this one should make it easier to access and use
files from other Coast Guard development
teams. The following example is for a HH60
Use a descriptive names that range from
general - specific. Use underscores
between words and to separate sections
This number denotes major release and the
next release would be 2.0, etc.
The development number is used to
designate where the file is at in the review
Vacant - unit preference.
Customer - user review. This file has been
reviewed by the customers/users once.
SME review. This file has been reviewed
by the development teams SME's six times.
Development team revision or version.
NOT the finished program version. This is
the eighth version of this file produced by
the development team
Based on program type. This is for an