Websites provide information or access to functions which are required by a business service. Websites are browser-based and are similar to application software but typically they do not execute any business logic or update databases. A website may be part of more than one business service and may require other services to support it.
Website Configuration Item names should follow the form of:
{common_name} ({url}) [{version}] [ - (owner)]
Where:
{common_name}
The name of the website as it referred to by the majority those who will reference the CI. Whether provided by a third party or developed in-house, this should be the full, formal title of the website (e.g., "UCI Student Affairs" or "UCI Alumni") rather than a URL, nickname, abbreviation, or acronym. 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.
{URL}
URL used to access the website. The URL should include only the fully qualified site name (e.g., "studentaffairs.uci.edu") without the URL scheme label ("http" or "https"). It should always be enclosed in parentheses to separate it from the common 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 website.
{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 name for a website but there are separate instances of the website for each department, include the department name as the owner. For example: Home Page - (DUE), Home Page - (Graduate Division), etc. The owner should always be enclosed in parentheses and separated from the rest of the CI name by a hyphen.
Website CI Name Examples
The following are examples of CI names that have been standardized using the conventions described above.
Original
Standard
Better
studentaffairs.uci.edu
Main Website (studentaffairs.uci.edu)
Student Affairs Main Website (studentaffairs.uci.edu)
GD Home
Home Page (www.grad.uci.edu) - (Grad Division)
Grad Division Home Page (www.grad.uci.edu)
Admissions Home
Home Page (www.admissions.uci.edu) - (Admissions)
Enrollment Services Home Page (www.admissions.uci.edu)
Typical Life Cycle for Websites
Unable to render {include} The included page could not be found.
CI Maintenance
Owner
Create CI
Change CI
Decommission CI
Maintain Relationships
Comments
OIT group responsible for supporting the application.
Application Owner
Configuration Review Team
Application Owner
Configuration Review Team
Application Owner
Application Owner
Configuration Review Team
Typical Relationships
The following relationships should be used when defining dependencies for applications: