Example: Labeling Configuration Items
An example for labeling configuration items
Main Description

The following is a suggested product-level work product labeling convention that can be used for labeling paths and work products.

<SYSTEM>[<A>]_[<SUBSYSTEM>]_[<A>]_[R|A|B]<X>[.<Y>.<Z>][.BL<#>]

<SYSTEM> Identifies the system

<A> Stands for the three letter acronym (TLA!). This is used for the various kinds of work products used in the creation of the system. For example,

PLN  Project Plans 
REQ  Requirements Files 
USC  Use Cases 
MOD  Model Files 
SRC  Source Code Files 
INT  Public Interfaces 
TST  Test Scripts and Results 
DOC  Documentation (User, Release Notes) 
BIN  Executables 

<SUBSYSTEM> Identifies each subsystem

<A> Stands for the three letter acronym for the various kinds of work products used in the creation of the subsystem. In accordance with the table above.

R|A|B  Stand for release, alpha, or beta 
<X>  Integer, stands for a major release (e.g. 1) 
<Y>  Integer (optional), stands for a minor release 
<Z>  Integer (optional), stands for an alternative release (patches, ports, etc.) 
BL  Stands for base level (an internal release) 
Integer, for internal releases 

Here are some examples:

T2K_R1.0  Release 1 of the Thorn 2000 system 
T2K_GUI_R2.0.BL5  Internal release of the GUI system intended for delivery in release 2 
T2K_B1.1  Beta release 1.1 of the Thorn 2000 system 
T2K_R2.0.BL16  Internal system baseline #16 of thorn 2000 intended for creating release 2 
T2K_R1.0.5  Maintenance release of Thorn 2000