DOC

Configuration Management Plan

By Larry Phillips,2014-05-19 10:00
9 views 0
2.3.6 Responsibilities of the NESDIS OSD Project Manager 7 CLASS Project Management Team The managing authority for the CLASS project.

    NOAA

    National Environmental Satellite, Data, and Information Service

    (NESDIS)

Comprehensive Large Array-data

    Stewardship System

    Configuration Management Plan

    CLASS-1001-CLS-PLN-CM

    February 1, 2005

    CLASS Project Configuration Management Plan Version Description of Version Date Completed 0.1 Initial draft 7/05/02 1.0 Updated with QMO Review Comments ready for CPMT review 7/16/02 1.0 Incorporated comments from CPMT approved by CPMT 10/01/02 1.0 Cleanup non-printing characters 10/07/02 1.1 Updated to remove material documented in procedures 7/17/03 1.2 Incorporated QA review comments 8/28/03 1.3 Incorporated PM review comments PM approved 8/29/03 1.4 Corrected section references PM approved 09/02/03 1.5 Incorporated comments from SCE and new organization 09/30/03 1.6 Incorporated SEPG review comments 09/30/04 1.7 01/17/05 Added activities for ORR and data management, clarified

    requirements flow, corrected CM processes and procedures.

    2.0 Approved by CPMT 02/01/05

    CLASS-1001-CLS-PLN-CM Page i

    CLASS Project Configuration Management Plan Project Plan Review History

    Reviewer Approval Date Version

    Reviewed

    1.7 01/23/05 SEPG

    1.7 02/01/05 CPMT

    CLASS-1001-CLS-PLN-CM Page ii

    CLASS Project Configuration Management Plan 1 INTRODUCTION .............................................................................................................1 1.1 Purpose............................................................................................................................1 1.2 Scope...............................................................................................................................1 1.3 Applicable Documents.....................................................................................................2

    1.4 Acronyms ........................................................................................................................2 1.5 Definitions .......................................................................................................................3 2 ORGANIZATION .............................................................................................................5 2.1 Configuration Management Office...................................................................................5

    2.2 Configuration Control Board ...........................................................................................5

    2.3 Roles and Responsibilities ...............................................................................................6 2.3.1 Responsibilities of the CCB .....................................................................................6

    2.3.2 Responsibilities of the CCB Chair ............................................................................6

    2.3.3 Responsibilities of the Configuration Management Office (CMO) ...........................7

    2.3.4 Responsibilities of the CLASS System Engineer ......................................................7

    2.3.5 Responsibilities of the CLASS Lead Integrator ........................................................7

    2.3.6 Responsibilities of the NESDIS OSD Project Manager ............................................7

    2.3.7 Responsibilities of the CPMT ..................................................................................7

    2.4 Tools ...............................................................................................................................7 3 CONFIGURATION CONTROL ......................................................................................9 3.1 Configuration Identification .............................................................................................9 3.2 Identification of Proposed Changes..................................................................................9

    3.3 Documentation of Proposed Changes............................................................................. 10

    3.4 Evaluation of Proposed Changes .................................................................................... 10

    3.4.1 Processing Urgent Changes .................................................................................... 11

    3.5 Integration of Approved Changes .................................................................................. 11

    3.5.1 Requirement Baseline Changes .............................................................................. 11

    3.5.2 Production Baseline Changes ................................................................................. 11

    3.5.3 Process Baseline Changes ...................................................................................... 12

    4 DOCUMENT AND DATA MANAGEMENT ................................................................ 13 4.1 Identification ................................................................................................................. 13 4.2 Document Management ................................................................................................. 13

    4.3 Change Management ..................................................................................................... 13

    4.4 Data Management .......................................................................................................... 13 4.4.1 Responsibilities ...................................................................................................... 13 4.4.2 Data Acquistion ..................................................................................................... 14

    5 CONFIGURATION STATUS ACCOUNTING ............................................................. 16 5.1 Status Account Data ...................................................................................................... 16 5.2 CLASS Configuration Management Database ............................................................... 16

    CLASS-1001-CLS-PLN-CM Page iii

    CLASS Project Configuration Management Plan 6 CONFIGURATION AUDITS ......................................................................................... 17 6.1 CM Process Audits ........................................................................................................ 17 6.2 CM Baseline Audit ........................................................................................................ 17 6.3 Operational Readiness Reviews (ORR) .......................................................................... 17

    CLASS-1001-CLS-PLN-CM Page iv

CLASS Project Configuration Management Plan

    1.1 Purpose

    The purpose of this Configuration Management (CM) Plan is to provide an overview of the

    organization, activities, overall tasks, and objectives of Configuration Management for the

    Comprehensive Large Array-data Stewardship System (CLASS). It addresses configuration item

    (CI) identification, change control and configuration audits at a high level; additional details

    regarding CM activities, techniques, and tools are provided in the CM-related procedures (see

    CLASS Document Repository for the most current procedures). These procedures are listed in

    Section 1.3, and referenced where applicable in this document.

    1.2 Scope

    The CLASS project has established several levels of baseline, with appropriate levels of control

    for each, as summarized in the following table:

    Baseline Contents Control Level Requirements System Requirements (CLASS requirements OSD

    repository)

    Allocated Requirements (CLASS requirements CCB/CPMT

    repository)

    Detailed Requirements (approved Level III CCRs) CCB Production Operational software, hardware (including COTS) CCB Process Documented processes, plans, and procedures CPMT Test Integration environment System Integration &

    System Test environment Test

    Deployment Test environment CMO Development Local development environment Local development team

    management

This document describes the CM approach for management of the Requirements, Production,

    and Process Baselines, which are controlled at the CLASS project level. The management and

    control of the Test baseline is described in the System Integration and Test Plan. The

    development environments are managed and controlled at the local level. The Configuration

    Management Office (CMO) maintains software baselines (development, integration, system test,

    and deployment test) for each release in the CLASS CM repository.

Changes to the Requirements and Production baselines are controlled by the CLASS

    Configuration Control Board (described in Section 2) via Configuration Change Requests

    (CCRs), Problem Reports (PRs), and Work Requests (WRs). Section 3 describes the CIs defined

    in these baselines and the process for managing changes to the CIs.

The Process baseline is controlled by the CPMT. Changes to CIs in this baseline are

    implemented via WRs, as described in the CLASS Process Baseline Management Procedure.

    Section 4 of this document describes CLASS document and data management.

    CLASS-1001-CLS-PLN-CM Page 1

CLASS Project Configuration Management Plan

    The Integration and System Test baselines are controlled by System Integration and Test

    management, while the Deployment Test environment is controlled by CLASS CMO. Local

    development environments are controlled by site administrators.

    1.3 Applicable Documents

    The following related documents are stored in the CLASS Document Repository:

    Document Number Title Requirements Baseline

    CLASS-1005-CLS-REQ-SRDOC System Requirements CLASS-1017-CLS-REQ-AADS Archive, Access, and Distribution System Allocated

    Requirements

    CLASS Process Baseline Plans

    CLASS-1028-CLS-PLN-MPMP Master Project Management Plan CLASS-1001-CLS-PLN-CM Configuration Management Plan CLASS-1002-CLS-PRO-Guide Software Development Guide CLASS-1006-CLS-PLN-QM Quality Management Plan CLASS CM Procedures

    CLASS-1000-CLS-PRO-DOCMT Document Management Procedure CLASS-1024-CLS-PRO-CM Configuration Item Identification CLASS-1025-CLS-PRO-CM Configuration Audits CLASS-1026-CLS-PRO-CM Configuration Change Request CLASS-1027-CLS-PRO-CM Database Configuration Management CLASS-1029-CLS-PRO-CM Requirements Baseline Management CLASS-1030-CLS-PRO-CM Process Baseline Document Management CLASS-1031-CLS-PRO-CM Source Code Control CLASS-1032-CLS-PRO-CM Software Change Promotion CLASS-1034-CLS-PRO-CM Issues and Action Tracking CLASS-1048-CLS-PRO-CM System Administration Change CLASS-1056-CLS-PRO-CM Work Requests

    CLASS-1064-CLS-PRO-CM Problem Reports

     CM-Related Procedures

    CLASS-1018-CLS-PRO-QM Peer Reviews

    CLASS-1049-CLS-PRO-SIT Operational Readiness Review

The CLASS Document Control Numbers are maintained in the CLASS requirements repository,

    and a full list identifying the version and location of the current baseline documents is posted in

    CLASS Document Repository.

    1.4 Acronyms

    CCR Configuration Change Request

    CCB Configuration Control Board

    CI Configuration Item

    CLASS Comprehensive Large Array-data Stewardship System

    CLASS-1001-CLS-PLN-CM Page 2

CLASS Project Configuration Management Plan

    CM Configuration Management

    CMDB Configuration Management Database

    CMO Configuration Management Office

    COT CLASS Operations Team

    CPMT CLASS Project Management Team

    CSDPC Central Satellite Data Processing Center

    CVS Concurrent Versions System

    NCDC National Climatic Data Center

    NESDIS National Environmental Satellite, Data, and Information Service

    NGDC National Geophysical Data Center

    NOAA National Oceanic and Atmospheric Administration

    ORR Operational Readiness Review

    OSD NOAA NESDIS Office of System Development

    PR Problem Report

    QMO Quality Management Office

    SAA Satellite Active Archive

    SAT System Administration Team

    SEPG Software Engineering Process Group (CLASS)

    SET System Engineering Team (CLASS)

    TAL Technical Area Lead

    TBD To Be Determined

    TBW To Be Written

    WR Work Request

    1.5 Definitions

    Baseline A formal, approved document or product serving as

    a departure point for future releases. The CLASS

    baselines are described in Section 1.2 above.

CLASS Configuration Control Board The board defining the disposition of Configuration

    Change Requests. The board is composed of CPMT

    members, SET members, and the CMO.

CLASS Oversight Group A board consisting of representatives from each of

    NOAA’s data centers, who provide vision and

    overall direction for CLASS.

CLASS Project Management Team The managing authority for the CLASS project.

    This team is defined in Section 2.

CLASS Systems Engineering Team The technical advisory committee for CLASS. This

    team is defined in Section 2.

Configuration Change Request A request for change to a baseline document or

    system.

CLASS-1001-CLS-PLN-CM Page 3

CLASS Project Configuration Management Plan

    Configuration Item An aggregation of hardware, software, or both,

    designated for configuration management and

    treated as a single entity in the configuration

    management process.

Level-I CCR A request for a change to the baselined CLASS

    System Requirements. A Level I CCR is directed

    from OSD.

Level-II CCR A request for change to the allocated requirements

    or interfaces. A Level II CCR is directed from the

    CPMT.

Level-III CCR A request for change to the Production baseline not

    requiring updates to the CLASS System or

    Allocated Requirements. This level of CCR

    constitutes a release-based change (discrepancy or

    enhancement) , as approved by the CLASS CCB.

Originator The person who submits a Configuration Change

    Request.

Problem Report A request for a change submitted to the CLASS

    configuration management tool, documenting a

    problem identified during system integration and

    test.

Work Request A request for a changed submitted to the CLASS

    configuration management tool, documenting an

    activity that may be approved by the CLASS

    Technical Area Lead (TAL).

CLASS-1001-CLS-PLN-CM Page 4

CLASS Project Configuration Management Plan

    The CLASS project is being conducted in support of the mission of the National Environmental Satellite, Data, and Information Service (NESDIS) to acquire, archive, and disseminate environmental data. The development of CLASS is expected to be a long-term, evolutionary process, as current and new campaigns are incorporated into the CLASS architecture.

    A distributed team including NOAA personnel at OSD, NCDC, and NGDC; and contractors in Suitland, MD, Fairmont, WV, and Boulder, CO, are developing the system. Development systems are located at the CSDPC site in Maryland, NGDC in Colorado, and the NCDC contractor site in Fairmont, WV. The integration system is located in Maryland. The system operates at both facilities in Suitland, MD, and the NCDC facility in Asheville, NC.

    In such a distributed development environment, it is particularly important that changes to the baseline system be strictly controlled. This control is provided by the Configuration Management Office, described in Section 2.1, under the direction of the Configuration Control Board, described in Section 2.2.

    2.1 Configuration Management Office

    The Configuration Management Office (CMO) includes the personnel responsible for management of all components of the CLASS baselines: software, hardware, and documentation. The CMO manages changes to the CLASS Requirements and Production baselines with the review and approval of the CLASS Configuration Control Board (CCB).

The CMO includes the following roles:

    ? Requirements Manager responsible for maintenance and update of the CLASS

    requirements repository

    ? Document Manager responsible for tracking project documentation

    ? Software Configuration Manager responsible for tracking software components, and

    building and promoting software releases

    ? System Administrator responsible for tracking and maintenance of hardware

    components

    2.2 Configuration Control Board

    The CLASS Project Management Team (CPMT) is responsible for overall direction and coordination for CLASS. The Technical Area Lead (TAL) from each participating organization serves on the CPMT with NESDIS Office of Systems Development (OSD) project management leading the team. The NOAA CLASS Technical Lead has authority for technical decisions related to CLASS, while the NESDIS OSD Project Manager maintains Requirements Baseline direction, administrative and budget authority.

    Similarly, each development team is represented on the CLASS System Engineering Team (SET). The SET oversees the technical direction of the development to ensure consistency and compatibility among the various components. The CLASS System Engineer and the CLASS Lead Integrator are members of the SET.

    CLASS-1001-CLS-PLN-CM Page 5

Report this document

For any questions or suggestions please email
cust-service@docsford.com