How we control changes to the deliverable elements of a project (including programs, prototypes, models, requirements, test cases etc), maintaining their integrity and traceability throughout the project lifecycle.
Configuration management brings aggregated intelligence from Sun's installed base. It is the ability to set up policies for software configurations and manage the servers to those policies. It improves system availability while reducing the cost of administration.
Refers to the capabilities which allow the user to configure operational parameters of physical and logical devices used within the system. There are two categories, Subscriber Management performed through the User Configuration System and Infrastructure Management performed through the OmniLink Zone Manager.
Configuration Management is the management of security features and assurances through control of changes made to hardware, software, documentation, and the testing aspects of information systems, throughout the development and operational life of a system. It is also the control of changes to hardware, software, and documentation throughout the system lifecycle. (Also see Visual SourceSafe)
The process of identifying, managing, and revising components of a business capability and their relationships to one another in a controlled manner.
We eschew the sysadmin-world definition of `configuration management' (keeping track of hosts, cables, networky things, ...); instead we throw our lot with the world of software configuration management, one definition of which is: Configuration Management is the process of identifying and defining the items in the system, controlling the change of these items throughout their lifecycle, recording and reporting the status of items and change requests, and verifying the completeness and correctness of items. -- IEEE-Std-729-1983 There are many other definitions you can choose from
One of five categories of network management defined by ISO for management of OSI networks. Configuration management subsystems are responsible for detecting and determining the state of a network. See also accounting management, fault management, performance management, and security management.
A discipline applying technical and administrative direction and surveillance to: (a) identify and document the functional and physical characteristics of a configuration item, (b) control changes to those characteristics and, (c) record and report changes to processing and implementation status.
The process of keeping track of changes to the system, if needed, approving them.
Configuration Management (CM) is the detailed recording and updating of information that describes an enterprise's computer systems and networks, including all hardware and software components.
Configuration management is the system you use to track multiple development builds of the software so that confusion is avoided. Revision control, Change Control, and Release Control are important aspects of Configuration Management.
Establish a known baseline condition and manage it.
A discipline, normally supported by software tools, which give management precise control over its assets (e.g. the products of a project), covering planning, identification, control, status accounting and verification of the products.
Configuration management refers to the act of controlling and managing the physical and functional make-up of the configuration items that comprise the system.
technical and administrative activities concerned with the creation, maintenance and controlled change of configuration throughout the life of the product. Note: See BS EN ISO 10007 for guidance on configuration management, including specialist terminology.
The component of the system that allows you to manage the current configuration of voice channels, host sessions, and database connections, assign scripts to run on specific voice channels or host sessions, assign functionality to circuit cards, and perform various maintenance functions.
The manual or automated management of system behavior and conditions.
The process of identifying and defining the configuration items in a system, controlling the release and change of these items throughout the system life cycle, recording and reporting the status of configuration items and change requests, and verifying the completeness and correctness of configuration items.
A management process for establishing and maintaining consistency of a product's performance, functional, and physical attributers with its requirements, design, and operational information throughout its life.
The process of retrieving data from network devices and using the information to manage the setup of the devices. For example, SNMP has the ability to automatically or manually retrieve data from SNMP-enabled network devices. Based on this data, a network manager can decide whether configuration changes are necessary to maintain network performance.
The process of managing the system architecture and infrastructure to ensure optimum performance.
Technical and organisational activities comprising configuration identification, configuration control, configuration status accounting and configuration audit. This includes the processes of identifying and defining the Configuration Items, recording and reporting the status of Configuration Items and requests for change, and verifying the completeness and correctness of Configuration Items.
Configuration management refers to the Director's ability to remotely manage the configuration of Sensors and IDSMs. This ability allows network security personnel to centrally manage all the Sensors/IDSMs across an enterprise-wide collection.
A MOF service management function in the changing quadrant. It employs the process of identifying and defining configuration items in a system, recording and reporting the status of configuration items and requests for change, and verifying the completeness and correctness of configuration items.
Configuration Management (CM) is the process of defining and controlling a product, its structure, associated documentation and other data. CM includes maintaining revision control and history information about all changes to a document, parts, assemblies and all other related data.
The discipline of identifying the configuration of a hardware/software system at each life cycle phase for the purpose of controlling changes to the configuration and maintaining the integrity and traceability of the configuration through the entire life cycle.
The management of security features and assurances through control of changes made to a system's hardware, software, firmware, documentation, test, test fixtures and test documentation throughout the development and operational life of the system. Compare "configuration control."
The tracking and controlling of how and why source files are created, organized, accessed, and changed, and from which versions of source a program is built. This is commonly referred to as CM.
The process of identifying, defining, recording and verifying CIs within a system and reporting their status and requests for change of Cis
A discipline applying technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. [IEEE Std 610.12-1990
Subset of project management that includes the processes for formally identifying and controlling project configuration items. Includes version control of project deliverables and other text documents, as well as code and build procedures. Technology project artifacts and deliverables must be versioned if they are to be kept up-to-date, including business and system requirements, designs and data models. An agency-wide configuration management practice can support the ongoing maintenance of standards and requirements and code bases within an agency.
The practice of identifying, tracking, reviewing, and controlling changes to artifacts in a project. Defines how products are built and released by an organization.
the collective duties associated with managing the hardware and software configuration. Key disciplines include configuration identification, control, relationship management, status accounting and audit.
All those activities focused on the registration, management and availability of the IT components and the relation between them, belonging to the computer platform on which the digital archive runs.
Defines and controls changes to project deliverables. Any documented procedure used to apply technical and administrative direction and surveillance to: define and document characteristics of a system: control changes: record and report changes: ensure conformance to requirements. (PMI)
The management of changes made to a MIS hardware, software, firmware, documentation, tests, test fixtures, test documentation, communications interfaces, operating procedures, installation structures, and all changes thereto throughout the development and operational life-cycle of the MIS.
Configuration Management (CM) is an Information Technology Infrastructure Library (ITIL®) IT Service Management (ITSM) process that tracks all of the individual Configuration Items (CI) in an IT system which may be as simple as a single server, or as complex as the entire IT department. In large organizations a configuration manager may be appointed to oversee and manage the CM process.
