RiVidium Configuration Management Configuration Management
Software Development & CM

Without a proper Software Development Configuration Management (CM) process, any well-intended systems/software life cycle management process is doomed to failure. CM is the process that ensures changes are captured, documented, and traced back to the initial Requirements Documents.

RiVidium’s CM ensures Software Problem Reports (SPRs), software and hardware change proposals, and proposed improvements and enhancements are analyzed, solutions designed, implemented, tested, and documented. RiVidium acts as the agent to perform the sustainment and enhancement of the software of assigned fielded systems. Nothing will reduce risk more for the client's systems engineering process than having a strong CM program. Our CM process encompasses all systems engineering and development efforts. We implement four configuration management functions. These are:

  • Configuration Identification.
  • Configuration Control.
  • Configuration Status Accounting.
  • Configuration Verification and Audit.

Configuration Identification

Configuration Identification: determines which documents best describe Configuration Items (CIs). This includes the system, the end component(s) comprising the system, and lower level items including logistics support elements. Configuration identification is a prerequisite for the other configuration management activities.

Configuration identification exists to identify and document the decisions made by the development team regarding functional / performance requirements, as well as the physical characteristics of the system and its constituent elements. Preparing and maintaining configuration baselines accomplishes this. These baselines are composed of specifications, drawings, and code listings. Our configuration identification process entails:

  • Selecting configuration components
  • Determining the types of configuration documentation required for each configuration component
  • Developing the Software Version Description/Version Description Document (VDD)
  • Issuing cataloging numbers and other identifiers which are affixed to the configuration components, as well as to the technical documentation
  • Releasing configuration components and their associated configuration documentation
  • Establishing configuration baselines for end components

The configuration identification incrementally establishes and maintains the definitive current basis for control and status accounting of a system and its configuration items throughout their life cycle (which include development, production, deployment and operational support, all of which are functional until the demilitarization and disposal phase).

Configuration Control

Configuration Control: RiVidium uses Configuration Control as perhaps the most visible element of configuration management. Configuration Control is the process used by RiVidium to manage preparation, justification, evaluation, coordination, disposition, and implementation of proposed engineering changes and deviations to effected configuration items (CIs) and baseline configuration documentation.

Our objective for configuration control is to establish and maintain a systematic change management process that regulates life-cycle costs, and allows optimum design and development latitude with the appropriate degree, and depth of configuration change control procedures during the life-cycle of a system. RiVidium’s Configuration Control includes:

  1. Efficiently process and implement configuration changes that maintain or enhance operational readiness, supportability, interchangeability and interoperability.
  2. Ensure complete, accurate and timely changes to configuration documentation maintained under appropriate configuration control authority
  3. Eliminate unnecessary change proliferation

Configuration Status Accounting

Configuration Status Accounting: Our Configuration Status Accounting: Our configuration status accounting approach is based on a transaction database fed by the transactions that take place under other configuration management processes. It provides visibility into status and configuration information concerning the client's products and their documentation. In essence, it provides a track of configuration documentation changes, i.e., the configuration history, and documents the configuration of configured components.

Configuration Verification and Audit

Configuration Audit Plan: Our Configuration Audit Plan (CAP) uses each of the following data types at specific and appropriate points in the systems engineering cycle:

  1. Schedule information from status accounting
  2. Configuration documentation for configuration identification
  3. The results of product testing
  4. The physical hardware or software product or its representation
  5. Manufacturing instructions
  6. The software engineering environment

Our CAP uses these data to verify that the product's performance requirements have been achieved by the product design, and that the product design has been accurately documented in the configuration documentation. The CAP also includes verification that approved engineering changes have been incorporated.

Back to the Top