Explore chapters and articles related to this topic
Software Quality Domain
Published in Marvin Gechman, Project Management of Large Software-Intensive Systems, 2019
The basic Software Configuration Management responsibilities are to: Establish formal baselines of identified products and maintain the integrity of baselines. Identify software configuration items (CI), components, and related products that will be placed under Configuration Management and when that takes place.Create and release baselines for internal use and for delivery to the customer.Track and control Change Requests for the configuration items and control the changes. Establish and maintain a Configuration Management and change management system for controlling software product changes.Establish and maintain records describing configuration items and perform configuration audits to maintain the integrity of the configuration baselines.
Reliability Engineering and Control
Published in Armand A. Lakner, Ronald T. Anderson, Reliability Engineering for Nuclear and Other High Technology Systems, 2017
Configuration management is achieved by imposing a procedural framework around the configuration items and applying systematic administrative techniques in order to identify and document the characteristics of the item, control changes to these characteristics and record/report on the implementation of approved changes throughout the system life cycle. The configuration of the software is identified and established at discrete points (baselines) during the life cycle so that subsequent changes to the configuration can be evaluated and systematically controlled. Thus, effective configuration management maintains the integrity and traceability of the software throughout the life cycle.
Aerospace systems engineering and technology management
Published in Wesley Spreen, The Aerospace Business, 2019
Configuration identification is the initial basis of the configuration management process. It involves defining and documenting the design baseline of the item or system to be controlled. The detailed baseline documentation includes all lower-level component parts, software, performance parameters, interfaces, purchased parts, and so on. Once an item is identified and defined it is referred to as a configuration item (CI).
Data and model-based triple V product development framework and methodology
Published in Enterprise Information Systems, 2022
Qing Li, Hailong Wei, Chao Yu, Shuangshuang Wang
The baselined-integrated system architecture is a key connector between design process and implementation process. It could be executable use case models for configuration item development task or specific hardware/software executable models for hardware/software development.