...
CI names should be concise, follow a consistent format, and contain enough information that a unique name can be assigned to each individual item and the nature of the item is immediately apparent to any user.
Contents
| Table of Contents |
|---|
General Principles in Naming CIs
...
- A format should be chosen that eliminates the need to ever have to rename the CI throughout its life cycle. Do not include version numbers or release dates in CI names unless you are tracking that specific version of the CI through its entire life cycle.
The name should describe the CI in a way that it is recognizable by the majority of users (including clients) who will see it.
The name should have the more significant information at the beginning, which will make it easier for systems with autocomplete to find the name when a user searches for it.
For hardware, consider including the asset tag ID or chassis serial number in the name. This will uniquely identify the CI and typically will not change during the CI's life cycle.
For software, use the common industry name of the product (for commercial products) or the name by which the software is usually referenced (for software developed internally) as the basis of the name.
For servers, printers, workstations and other network devices, consider that host names often change and care should be taken when considering them as CI names.
- Make every attempt to avoid abbreviations, jargon, and slang in CI names. Keep in mind that everyone from end users on the business side to the technical staff called on to provide support will need to understand the name.
- Under no circumstances should a person’s name be included in a CI name. If, for some reason, a person's name must be included then use the person's home department rather than the person’s name.
Naming Application Software
...
CIs
Application software CI names should follow the form of:
...
{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., 'Windows 7"Office Suite 2016" or "Graduate Applicant Tracking System") rather than a nickname, abbreviation, or acronym ("Win7Office 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. |
|---|---|
{nounnickname} | The item or system being worked on as a result of the project. For example, System, Server, Web Site, SQL Server, Telephone System, Network Switch, etc. Note that the noune can be a single word or a noun phrase. |
{modifier} | Further defines the relationship between the verb and the noun. Modifiers should be prefixed with a preposition such as “from,” “on,” “to,” “with,” etc. For example “to Version 2.1” or “with Oracle.” In rare instances, it may be necessary to use multiple modifiers (e.g., “to Version 2.17 from Version 2.12”), but this should be done by exception. |
{sponsor} | Optional Nickname, abbreviation, or acronym for the CI. The nickname 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 purpose of similar projectsthe owner of the CI or to eliminate duplication of CI names. For example, if several projects are under way to upgrade servers from one OS to another but separate projects are being run for individual clients, the sponsor name should be included in each of the project names in order to tell them apart. The sponsor’s name should always be prefixed with the word “for.” |
Other Considerations
- Avoid using multiple verbs. Most projects involve more than one kind of activity and it is not necessary to mention them all in the project name. For example, a software development project might involve designing, developing, testing, and deploying business application software. All this activity can be summarized simply as “implementing” since the final outcome of the project will be newly implemented software.
- In all cases, avoid abbreviations, jargon, and slang in project names. Keep in mind that everyone from the executive sponsor on the business side to the technical staff called on to implement the detailed tasks associated with the project will need to understand the name.
- Under no circumstances should a person’s name be included in a project name. If the project sponsor needs to be included, use the department name rather than the individual person’s name.
- Avoid using the words “old” and “new” since, by definition, most projects are implementing something “new” and most result in the elimination of something “old.”
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 project CI names that have been normalized standardized using the conventions described above.
| OriginalCommon | NormalizedStandard | |
|---|---|---|
QuickTemp Rewrite | Rewrite QuickTemp | |
Greentree Web and Database Servers Upgrade | Upgrade Greentree Web and Database Servers | |
WSG - Migrate File Storage from NetApp to Windows File Server | Migrate File Storage to Windows File Server | |
Constituent Engagement Management System | Implement Constituent Engagement Management System | |
Kuali Coeus and Cayuse 424 System to System Integration | Implement Integration of Kuali Coeus with Cayuse 424 System | |
Kuali Coeus Conflict of Interest for Research | Implement Kuali Coeus Conflict of Interest for Research | |
Kuali Coeus Negotiations Module Implementation | Implement Kuali Coeus Negotiations Module | |
LAOHP Administration System | Implement LAOHP Administration System | |
Planning and Budget Scanning Project | Implement Scanning System for Planning and Budget | |
Office365 Email Migration - University Advancement | Migrate Email to Office 365 for University Advancement | |
New User Account Automation | Automate New User Account Creation | |
Border IDS / IPS Replacement | Replace Border Intrusion Detection and Prevention System | |
Enhance OR and GD VB6 apps to support MS Office 2013 | Enhance VB6 Applications to Support MS Office 2013 | |
Netreo Automation | Automate Netreo | |
Enterprise Data Center Firewall Consolidation Project | Consolidate Firewalls for Enterprise Data CenterGATS | Graduate Applicant Tracking System (GATS) |
GD ZotPortal Portlets | ZotPortal Portlets - (Grad Division) | |
| Jack/port location (JPL) database | Jack/Port Database (JPL) |