Task: Set Up Configuration Management (CM) Environment
Create an environment where the product can be developed and built
Disciplines: Configuration and Change Management
Purpose
The purpose of this task is to establish an environment where the product can be developed and built. This is done in two parts, firstly by setting up the hardware environment, and then by establishing the development environment.
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
      Outputs
        Main Description

        Steps
        Set up the CM Hardware Environment

        The Configuration Manager works with the System Administrator to allocate machine resources, and install the necessary software tools.

        The key considerations (in order of priority) for the machine dedicated to running the server that mediates access to actual data in  the project repository are the following:

        • Memory Requirements
        • Disk Input / Output Requirements
        • Network Bandwidth
        • Project Repository Disk Space

        Information on each of these items is provided under the Project Repository

        Map the Architecture to the Repository
        The product directory structure serves a logically nested placeholder for all product-related work products. The shape of the directory (which serves as the project repository) depends on the number of subsystems in the overall system, and the number of elements in each subsystem.
        Create Initial Set of Versioned Elements
        Even on projects with no configuration management there is a notion of a directory structure and an existing body of material that is used by the project on an on-going basis. The idea is to export/import the existing material into the structure created for product development.
        Create Integration Workspace
        Create private workspace, where individuals can develop and change code in a contained area. The integration workspace is where subsystem and system integrators convince themselves that separately developed and tested components can indeed work together as a product.
        Key Considerations

        This may not be necessary 

        1. For big organization because they may have separate tool department or a tool administrator to setup configuration management environment.
        2. For smaller project which are not mature enough