Configuration management is not asset management. Configuration management focuses on building and maintaining Configuration Items CI that need to be managed in order to deliver an IT service.
Configuration item CI is an asset, service component or item that is, or will be under the control of Configuration Management. CI may be a single module such as a monitor or a tape drive, or a more complex item , such as a complete system. It needs to be managed in order to deliver IT service. A configuration item CI is a physical, logical, or conceptual entity that is part of your IT environment and has configurable attributes.
Some CI types are virtual, while others are physical and include hardware and software. A configuration item is anything that can be configured and that is absolutely necessary for the success of your project. For example, source codes , property files, binaries, servers, and tools can all be configuration items for a software firm. Configuration Data means the Facility-specific data that is used in conjunction with the Software, including without limitation, tuning and set point constants, graphical, pictorial and text files, that instantiate the Software for the specific Facility environment.
What is a computer software configuration item? Category: technology and computing operating systems. What do you mean by software configuration? Which items are configuration items? Why do we need configuration management? Why do we need software configuration management? How do you manage system configuration? What is meant by configuration management?
What do you understand by software configuration? Who is responsible for configuration management? What college classes are required for computer science?
Selected items of system hardware or software or combinations of hardware and software , in which the Government or acquiring activity has configuration management concern, are designated as Configuration Items CIs. CIs are the basic units of configuration management. They may vary widely in complexity, size and type, from an aircraft, ship, tank, electronic system or software program to a test meter or a round of ammunition. Regardless of form, size or complexity, the configuration of a CI is documented and controlled.
CI selection separates system components into identifiable subsets for the purpose of managing further development. For each CI:. To define and control the performance of a system or CI, does not mean that all of its hardware and software components must be designated as CIs, nor does it mean that the performance requirements for the non-CI components must be under Government control.
The requirements to be met by a lower-level component which is not designated as a CI are established and controlled via the Contractor's design and engineering release process. Government control occurs only when changes to the lower level components impact the Government-baselined performance specification for the CI.
Initial CI selection should reflect an optimum management level during early acquisition. As shown in Figure , the view of what is designated a CI may depend on where in the contracting tree the view originates. Note that, where the Government acquires a system using detail, rather than performance specifications, the Government view may eventually include all of the CIs shown in this figure.
Computer software items, because they typically control the functionality of a system, are almost always designated as CIs. Typically the top tier of CIs directly relate to the line items of a contract and the work breakdown structure. The determination of the need to designate them as CIs is normally simple and straight forward. However, there are many cases in which other lower-level items should also be selected based on the management needs of the program.
Some of the primary reasons for designating separate CIs are:. Although the initial CI selection generally occurs early in the acquisition process, its consequences are lasting and affect many aspects of program management, systems engineering, acquisition logistics, and configuration management. CI selection establishes the level of Government configuration control throughout the system life cycle.
Selecting CIs separates a system into individually identified components for the purpose of managing their development and support. Government CI designation should reflect the optimum level for both acquisition and support. During acquisition, this is the level at which a contracting activity specifies, contracts for, and accepts individual components of a system, and at which the logistics activities organize, assign responsibility and report modification and maintenance actions during support.
During the concept exploration and the program definition and risk reduction phases, the system architecture is established, the program work breakdown structure is developed, and major CIs are selected. These activities provide the basis for the Supportability Plan for the program, which, in turn, dictates the selection of lower-level CIs.
Development, acquisition, retrofit, and hardware and software interfaces are all affected by the breakout of the key system elements into CIs during the early stages of the development effort. Configuration Item Selection Criteria]. Many engineering requirements or considerations can influence the selection of CIs. Throughout development and support, the allocation of engineering effort and organization are rooted in the selection of CIs.
Developing contractors should participate in the selection process and provide recommendations based upon engineering or other technical considerations. Either the Government or the contractor may make initial recommendations of top-level CI candidates as a result of their system engineering analyses; however the contractor is normally tasked to provide the comprehensive recommendations.
CI selection criteria are applied to contractor recommendations to decide on the items to be managed as CIs by the Government. Decisions to designate specific candidates as CIs and decisions on the time when they will come under Government control normally involve an integrated team of acquisition program management, systems engineering, and acquisition logistics working with configuration management.
In addition, the contractor determines those items in the system that are not Government CIs, but which will be subject to lower tier lower tier configuration management by the contractor. For each CI: There will be associated configuration documentation which may range from a performance specification to a detailed drawing to a commercial item description [See 5.
Some of the primary reasons for designating separate CIs are: Critical, new or modified design Independent end use functions Sub-assembly factors such as the need for separate configuration control or a separate address for the effectivity of changes [Details: Section 6] Components common to several systems Interface with other systems, equipment or software Level at which interchangeability must be maintained Separate delivery or installation requirement Separate definition of performance and test requirements.
High risk and critical components Although the initial CI selection generally occurs early in the acquisition process, its consequences are lasting and affect many aspects of program management, systems engineering, acquisition logistics, and configuration management.
By clicking sign up, you agree to receive emails from Techopedia and agree to our Terms of Use and Privacy Policy. In information technology, a configuration item is a component of a system that can be identified as a self-contained unit for purposes of change control and identification. In other words, version numbers and configuration item registration codes help in uniquely identifying configuration items.
Configuration items play an important role in configuration management systems. The versions and changes of configuration items form a major part of any configuration audits. A configuration item can not only be at the most atomic level, but also can consist of a more complex assembly of other configuration items. In other words, a configuration item can be a primitive component or an aggregate of other configuration items.
In fact, the level at which a configuration item is considered as primitive or aggregate is often decided by the system in which it is created, maintained and managed. With the help of processes and tools, configuration management looks after the configuration items, especially with regards to change management, status accounting, identification and any audits.
Common configuration types include software, hardware, communications, location and documentation. Configuration items have specific attributes as well as relationships that are often unique for configuration items underneath them in the particular system. Configuration items help in identifying the components of a system.
0コメント