ICW Naming Conventions
Multimedia developers typically produce many
Rationale
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
Sample Format
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
hydraulics system.
Sample Name
HH60_Hydraulics_LFI_1.0_01608.a3w
HH60_Hydraulics_LFI_1.0_01608.a3w
Use a descriptive names that range from
Project
general - specific. Use underscores
Name
between words and to separate sections
This number denotes major release and the
HH60_Hydraulics_LFI_1.0_01608.a3w
Version/
next release would be 2.0, etc.
Release
HH60_Hydraulics_LFI_1.0_01608. a3w
The development number is used to
5 Digit
designate where the file is at in the review
Dev.
cycle.
Number
Vacant - unit preference.
HH60_Hydraulics_LFI_1.0_01608.a3w
1st digit
Customer - user review. This file has been
HH60_Hydraulics_LFI_1.0_01608.a3w
2nd digit
reviewed by the customers/users once.
SME review. This file has been reviewed
HH60_Hydraulics_LFI_1.0_01608.a3w
3rd digit
by the development teams SME's six times.
HH60_Hydraulics_LFI_1.0_01608.a3w
Development team revision or version.
4th/5th
NOT the finished program version. This is
digit
the eighth version of this file produced by
the development team
HH60_Hydraulics_LFI_1.0_01608. a3w
Based on program type. This is for an
file ext.
Authorware program.
7
Previous Page
