Naming Applications
Applications provide functions which are required by a business service. Applications are typically software and are usually referred to as "application software." But in some cases applications, may require specific hardware components or other assets in order to function. An application may be part of more than one business service and may require other services to support it.
Application software Configuration Item names should follow the form of:
{common_name} [({nickname})] [{version}] [ - (owner)]Where:
{common_name} | The name of the software as it referred to by the majority those who will reference the CI. Whether a commercial product or something developed in-house, this should be the full, formal name of the product (e.g., "Office Suite 2016" or "Graduate Applicant Tracking System") rather than a nickname, abbreviation, or acronym ("Office 16" or "GATS"). While nicknames and abbreviations may be meaningful to frequent users of the CI, they are not so apparent to others who are not as familiar with the application. |
|---|---|
{nickname} | Nickname, abbreviation, or acronym for the CI. The nickname is optional and should always be enclosed in parentheses to separate it from the full name. |
{version} | A version is used to identify a specific baseline of a CI. This information should only be included if the CI is being defined to track a specific version or release of the applicaiton. |
{owner} | The name of the primary end user of the CI. This is optional and should only be used to eliminate any confusion about the owner of the CI or to eliminate duplication of CI names. For example, if several departments are using the same same application software but there are separate instances of the software for each department, include the department name as the owner. For example: Office Suite 2016 - (DUE), Office Suite 2016 - (Graduate Division), etc. The owner should always be enclosed in parentheses and separated from the rest of the CI name by a hyphen. |
Application Software CI Name Examples
The following are examples of CI names that have been standardized using the conventions described above.
Common | Standard |
|---|---|
GATS | Graduate Applicant Tracking System (GATS) |
GD ZotPortal Portlets | ZotPortal Portlets - (Grad Division) |
| Jack/port location (JPL) database | Jack/Port Database (JPL) |