Configuration and Management

This standard describes Configuration Management functions and principles and defines a neutral Configuration Management Terminology for use with any product line.. Development began [r]

Working closely with Facilities Planning, Capacity and Performance Management, Inventory Management and many other SMC disciplines, Configuration Management will assist in the definition, ordering, implementation planning, installation, and acceptance testing of equipment and software components needed to support business and user requirements. In response to a business requirement, Configuration Management will assist in the selection and installation planning of equipment / software that is compatible with the existing configuration, taking note of any exception that will have to be

Communicates an adaptable framework for configuration management that allows OI&T offices to incorporate the principles of configuration management into their business functions and work products as a routine procedure. Allows OI&T to reinforce a commitment to minimizing or preventing adverse effects on VA information systems, as a result of a lack of proper planning, documentation, and/or coordination through an approved standard process

9.2.2 Configuration Management Process Understanding of what CM is supposed to accomplish is one thing. Putting it into practice is another. As with most project activities CM begins with planning. With a plan, configuration baselines can be established. Following this initial configuration identification, the cyclical configuration control process is put into motion. These three major CM implementation activities are shown in Figure 9-3.

The first step in a configuration management process is to understand what assets you need to configure and maintain. If systems administrators had to manually visit every office to catalog every device and collect information about installed applications (down to minor version levels), they would be hard pressed to get other work done, at least not without augmenting the number of systems administrators on staff. Manually tracking assets is especially problematic in cases where there are frequent changes that warrant more frequent updates to the asset inventory. For most businesses that have grown beyond a small number of employees, the prospect of desk‐side visits to collect information on assets is impractical. The tedious and inefficient manual process of tracking assets can be replaced by applications that can query OSs to collect information about a devices configuration or

“function” and Configuration Management is a Systems Engineering “function” with a sub-set of CM being change control of configuration items (and their associated configuration documen[r]

5998 Dartshire Blvd., Dublin, OH 43016, USA A BSTRACT This paper is an investigation of the benefits of Applying Change Management Techniques in relation to Configuration Management in Product Lifecycle Management. This paper formulates in depth principles of Change Management to demonstrate the end result of a better quality engineering product in Industries like Aerospace and Automotive. This paper further illustrates the use of Change Management Techniques to bring about Cost reduction and elimination of Engineering design errors when applied in the Initial stages of a Project.

The Configuration Management Plan must be prepared according to the general format requirements defined in SOP SOP_0102 “Documentation Standards.” A Configuration Management Plan is developed for each unique computer system that would define for each application the specific process for controlling the application elements.

Software Configuration Management Section A: Multiple Choices 1) Which of the following should be considered as Configuration Items for any project: Project plan, Requirement specification, Class diagrams Design specification, Design tools, Activity diagrams Source Code, Test plan, test Script, Test tools, Test results All of the above

I What about shared files?.. Software configuration management areas.. source revision control).. I Store history:[r]

5.1.5 Formal baseline identification Configuration identification includes establishing and maintaining baselines that define the system or subsystem configuration items at any point in time. Based on the ESS programme life cycle phases, which relies on an incremental development and delivery scheme, different technical baselines, are progressively established and populated by configuration items [SEMP]. Configuration Identification uses configuration baselines as an integral configuration management concept. A technical baseline is defined as means to reveal the products maturity between two product development phases; it therefore serves as both the completion stage of one product phase and the initiation point of the following phase. Each baseline is initiated from the top i.e. the facility level and gradually enriched by the lower levels as their development maturity progresses.

AFRL has also developed requirements to ensure that hardware produced by universities can be integrated into a system that in turn meets the NASA and DoD requirements. The primary AFRL requirements document is UN5-0001, Nanosat-5 User’s Guide. Other requirements include AFRL Document UN-SPEC- 12311, Rev. A, Stress Analysis Case Study, this Configuration/Document Management and Quality Assurance Plan, and all ancillary requirements documents listed as applicable to the UNP by UN5-0001, UN- SPEC-12311, and this document.

4. Controls should be commensurate with the relevant risk of any amendments to any CI affecting the security or compliance of the licence holder’s systems. 5. The configuration item risk management plan shall be reviewed with each change request and change. The configuration item risk management plan shall be included with Release Notes, and provided to the Director of Gaming.

Abstract. The deployment of services — sets of running programs that provide some useful facility on a system or network — is typically implemented through a manual, time-consuming and error-prone process. For instance, system admin- istrators must deploy the necessary software components, edit configuration files, start or stop processes, and so on. This is often done in an ad hoc style with no reproducibility, violating proper configuration management practices. In this paper we show that build management, software deployment and service deploy- ment can be integrated into a single formalism. We do this in the context of the Nix software deployment system, and show that its advantages — co-existence of versions and variants, atomic upgrades and rollbacks, and component closure

Abstract. The deployment of services — sets of running programs that provide some useful facility on a system or network — is typically implemented through a manual, time-consuming and error-prone process. For instance, system admin- istrators must deploy the necessary software components, edit configuration files, start or stop processes, and so on. This is often done in an ad hoc style with no reproducibility, violating proper configuration management practices. In this paper we show that build management, software deployment and service deploy- ment can be integrated into a single formalism. We do this in the context of the Nix software deployment system, and show that its advantages — co-existence of versions and variants, atomic upgrades and rollbacks, and component closure

Improvements made based on these performance measures will be used as a baseline for configuration management during future project phases. 2.5 Configuration Status Accounting (CSA) The IPS change management database will facilitate the CSA. The Change Control Coordinator will generate reports from the database to summarize the changes made during each project phase. The Coordinator will determine the percentage of CI’s that required changes during each phase and will provide a comparison of those percentages in a management report. This formal tracking will provide trace-ability to project phases. The IPS project team can also use the baseline CI report to map design characteristics to the functional baseline to assure that all requirements are met during design. The IPS development team will map its work to the functional baseline to confirm that the new system will meet the needs of the users.

1 A-4500 HOV Project Configuration Management Plan 1.0 Introduction The purpose of this Configuration Management Plan (CMP) is to set forth the methodology to be used for the control of configuration items associated with the A-4500 HOV Project. The CMP is the formal means for approval of design documentation and deliverables, including drawings, and subsequent changes. It is WHOI's responsibility to ensure that the configuration is managed and controlled in a fashion that is relative to the project stages, is well documented, and is communicated to affected functional areas in a timely manner.

The STMCSLS project will use the Rational ClearCase LT tool in the configuration management process and ClearQuest for Engineering Change Request (ECR) and Software Problem Report (SPR) tracking. (While ClearCase and ClearCase LT are separate products, for the purposes of this document, the terms will be used interchangeably.) ClearCase is designed for storage and version control of artifacts for the project. All baselined code and document deliverables will be stored in ClearCase. ClearCase will be used to create project baselines, and may be used to capture snapshots of what all project artifacts look like at a certain point in time, if required.

business-aligned CMS by focusing on business value rather than infrastructure components. The rationale behind the CMS is that the CMDB, when used as a part of an overall system, goes beyond storing Configuration Items and actually supports business strategy. So the business value is not in a database of Configuration Items on its own, but rather in a system where the database of Configuration Items is considered with processes that leverage that data in support of the business. The CMS is more than the CMDB and reflects the infusion of good IT Service Management (ITSM) practices. Relationships are at the heart of the CMS. The CMDB was often viewed as a repository of attributes. The CMS is a force to break this cycle by mandating the relationships necessary to make the raw data meaningful.

Copyright © 2005 Softhouse Consulting. All rights reserved. 4 Introduction Configuration management has evolved from the beginnings of software engineering in the 1960’s as a key discipline, required to assert control over changes and handle coordination between concurrent work by individuals and teams. As configuration management has evolved from a need of control, this contradicts the values of the Agile Methodologies [13] and Lean manufacturing [4] that emphasize responding to change rather than controlling change. In this paper we discuss experiences gained from CM activities in two industrial organizations over a period of more than a decade, that lead us to the conclusion that by allowing the CM activities to support agile principles we can achieve several interesting effects, both as a direct result of the CM activities and the effects of the agile practices supported. Specifically, by making CM practices support agile methods and lean principles we assert that it is possible to reduce the overhead involved in CM activities, increase the possibility of rapid feedback through more frequent iteration deliveries and to be able to control more rapid change than traditional CM activities can support. The results of these effects should ultimately lead to increased ROI for the software project.