5.2 Examples

Tables 5-1 and 5-2 are examples of the activities in configuration management systems with low and high degrees of formalism, respectively. The principles are valid for all types of configuration items, such as a document, source code file, or delivery. It is presumed that the tool(s) used will register transactions in the controlled library, creating an automatic log of everything going on. Such logs are often quite limited and are typically suited to a low degree of formalism. A high degree of formalism, which requires logs filled out by people, may seem to promote paper-based configuration management, but this is not necessarily true, as these logs can be kept electronically .

Table 5-1. Activities with a Low Degree of Formalism

Activity	Description
Creation	The producer Identifies a new item Registers the metadata most needed in the required format and on the required media Inserts the new item in the controlled library
Usage	The users Extract copies of the configuration item when they have a need They perform the extraction themselves , directly from the controlled library.
Events	The users Send e- mails about events to the person responsible for configuration management and to members of the configuration control board
Event evaluation	The person responsible for configuration management makes sure that Every event registration is evaluated by the original producer (or other experts) The result of this evaluation is sent by e-mail to the configuration control board
Change decision	The configuration control board Sends its decision regarding changes to the producer by e-mail
New items	The producer Identifies the needed new item Gets an earlier configuration item as the basis for the production of the new item as appropriate Registers the most needed metadata in the required format and on the required media Inserts the new item in the controlled library
And so on . . .	Life goes on like this.

Table 5-2. Activities with a High Degree of Formalism

Activity	Description
Creation	The person responsible for configuration management Identifies a new item Fills in all metadata in the required format and on the required media for the new item, including full detailed tracing to related items
Approval	The person responsible for quality Fills in and signs written approval of an item ready to be placed under configuration management
Submission	The producer Submits a registration of metadata, the item itself, and the item approval to the librarian
Placement in storage	The librarian Places the item in the controlled library Takes care of the registration and storage of associated metadata and forms
Release request	The users Submit written release requests to the librarian, including information on who is going to use the item and for what purpose
Release for usage	The librarian Releases copies of the configuration item to those who are going to use them, according to the release request Takes care of registration and storage of related data and forms
Events	Users Submit written event registration to the person responsible for configuration management
Event evaluation	The person responsible for configuration management Arranges a written evaluation of each event registration from the original producer of the item and/or other experts
The CCB works	The configuration control board Meets Evaluates each event registration Documents their evaluation on the respective event registrations
Change requests	The configuration control board Produces the necessary written change requests in accordance with the results of their evaluations
New items	The person responsible for configuration management Identifies a new item Releases a configuration item as the basis for the production of a new item, as appropriate
Approval of change	The person responsible for quality Fills in and signs a written approval of the new item ready to be placed under configuration management
Acceptance of change	The configuration control board Meets Evaluates each approval Documents their evaluation on the respective change requests and event registrations
Submission of change	The producer Submits metadata registration, the item itself, and an approved change request to the librarian for each new item
Storage	The librarian Inserts the item in the controlled library Takes care of the registration and storage of related data and forms
Communication of change	The librarian Informs all those who have received previous versions of the configuration item that a new, changed version is available This esnables stakeholders to decide if they want the new version released for usage.
And so on . . .	Life goes on like this.