Website Development – Create Baseline Records

Website Development – Create Baseline Records

Create Baseline Records

When a baseline gets created, the Baseline Form (CMP-F001) has to be opened for the new Baseline. An event that creates a new Baseline record could be one of the following:

· Start of the project (Initial baseline)

· End of project (Release baseline)

· A major scope re-definition has occurred leading to changes to more than 50% of the CIs for the project (intermediate baseline).

However, the events are not necessarily restricted to the above. Other events, as appropriate to the project, could be defined. A separate form has to be opened for each Baseline defined in the CMP. Refer Appendix - B1:Baseline Register. The Baseline information is needed for tracability across documents.

Identify Dynamic and Controlled Libraries

Dynamic libraries are used for creating and modifying the CIs. Controlled libraries are used for moving released CIs. Once the CIs are moved to the Controlled Libraries, they automatically come under Change Control. All changes to documents or programs that have been moved to the Controlled Libraries have to be done as laid out in the Change Control procedure.

Each project should define the directories that are to be used as Dynamic and Controlled directories. Typically the dynamic directory is named ‘work’ directory. The controlled directory is named ‘release’ directory.

Bring CIs Under Configuration / Change Control

The event that creates a Configuration Item (CI) is defined in the CMP. On occurrence of such an event, the Configuration item has to be brought under Change Control. The most common event that brings a CI under Change Control is the 'Release' of CI. Any other event that causes a CI to come under Change Control should be defined in the CMP.

To bring a CI under Change Control, the following activities have to be completed:

The release details of the CI have to be noted down in the Configuration Item Index (CMP-F002). Refer Appendix - B2 – Configuration Item Index.

Once the CI has been brought under Change Control, it is mandatory to track all changes to the Configuration Item. Refer to procedure Change Control for details on how to identify, track and control changes.

Maintain the Configuration Item Index

The Configuration Item Index (CII) maintains details on all releases of a CI. It gives an overview of the number of releases made for a CI, the date of the releases and the latest version of a CI. Refer Appendix - B2 – Configuration Item Index

Deliverables from the process

· Configuration Management Plan

· Configuration Item Index

· Baseline Registers

Exit Criteria

· All CIs for the project have been identified in the CMP

· All Baselines for the project have been identified in the CMP

· The Dynamic and Control Libraries have been identified in the CMP

· A Baseline Register has been opened.

· A CI has been entered into the CII

· A Change Request has been entered into the CCR

Check-out and Check-In Mechanisms

Back to the LinksMultiple eBay Auction | eBay Shopping home page