Студопедия
Случайная страница | ТОМ-1 | ТОМ-2 | ТОМ-3
АвтомобилиАстрономияБиологияГеографияДом и садДругие языкиДругоеИнформатика
ИсторияКультураЛитератураЛогикаМатематикаМедицинаМеталлургияМеханика
ОбразованиеОхрана трудаПедагогикаПолитикаПравоПсихологияРелигияРиторика
СоциологияСпортСтроительствоТехнологияТуризмФизикаФилософияФинансы
ХимияЧерчениеЭкологияЭкономикаЭлектроника

Status accounting and reporting

Читайте также:
  1. According to IAS 16, for accounting of PPE items an entity may choose between
  2. Accounting and Finance
  3. Accounting and Finance
  4. Accounting personal statement
  5. Article 3 Legal Status
  6. Die Zeit's editor aims to regain the paper's status as a forum for lively intellectual debate
  7. Functions regarding to reporting

Each asset or CI will have one or more discrete states through which it can progress. The significance of each state should be defined in terms of what use can be made of the asset or CI in that state. There will typically be a range of states relevant to the individual asset or CIs.

A simple example of a lifecycle is:

The way CIs move from one state to another should be defined, e.g. an application release may be registered, accepted, installed or withdrawn. An example of a lifecycle for a package application release is shown in Figure 4.14. This will include defining the type of review and approval required and the authority level necessary to give that approval. In Figure 4.12 the role that can promote the CI from Accepted to Installed is ‘ release management ’. At each lifecycle status change the CMS should be updated with the reason, date-time stamp and person that did the status change. The planning activities should also establish any attribute s that should be updated at each state.

Figure 4.14 Example of asset and configuration item lifecycle

Configuration status accounting and reporting is concerned with ensuring that all configuration data and documentation is recorded as each asset or CI progresses through its lifecycle. It provides the status of the configuration of a service and its environment as the configuration evolves through the service lifecycle.

Status reporting provides the current and historical data concerned with each CI that in turn enables tracking of changes to CIs and their record s, i.e. tracking the status as a CI changes from one state to another, e.g. ‘ development ’, ‘ test ’, ‘ live ’ or ‘withdrawn’.

The organization should perform configuration status accounting and reporting activities throughout the lifecycle of the service in order to support and enable an efficient Configuration Management process. Typical activities include:

Records

During the configuration identification and control activities, configuration status records will be created. These records allow for visibility and traceability and for the efficient management of the evolving configuration. They typically include details of:

The evolving service configuration information should be recorded in a manner that identifies the cross-references and inter relationship s necessary to provide the required reports.


Дата добавления: 2015-10-29; просмотров: 185 | Нарушение авторских прав


Читайте в этой же книге: Good practice in the public domain | Service Strategy | Functions and processes across the lifecycle | Specialization and coordination across the lifecycle | Service utilities and warranties | Service change | Types of change request | Process activities, methods and techniques | Create and record Requests for change | Configuration structures and the selection of configuration items |
<== предыдущая страница | следующая страница ==>
Identification of configuration baselines| Release design options and considerations

mybiblioteka.su - 2015-2024 год. (0.006 сек.)