|
|
Keywords:
Deliverable,
Milestone,
Thereafter,
Configuration,
Revision
A baseline is a complete description of the configuration of a system at a particular point in its development.
A documented version of a hardware component, software program, configuration, standard, procedure, or project management plan. Baseline versions are placed under formal change controls and should not be modified unless the changes are approved and documented.
a formally identified cohesive set of one or more configuration items that is to be established by a certain milestone. Note that a baseline can only be changed by means of the formal configuration control task. vb. to place a work product under configuration control and identify it as part of a baseline.
a baselevel that is suitable for a formal internal or external release
a Configuration Identification formally designated and applicable at a specific point in an items life cycle
a set of documented configurations of a product or system that is established at a specific point in time
a snapshot of the state of a configuration item (or a plan) and its component configuration items at a point in time
a special kind of version resource that captures the state of the version-controlled members of a configuration
a version resource that captures the state of each version-controlled member of a configuration
An item or collection of items of a particular shape and form used as a reference. A baseline configuration is a reference point for evaluating modifications and enhancements and a starting point for making those changes. This baseline is normally considered the “official” version of an installed and operational Configuration Item.
A formally approved version of a configuration item, regardless of media, formally designated and fixed at a specific time during the configuration item's life cycle.
a specification or product that has been formally reviewed and agreed on, which thereafter serves as a basis for further development and can be changed only through formal change control procedures. (Copyright 1993 IEEE. All rights reserved.)
A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures.
(1) An agreed-to description of the attributes of a product, at a point in time, which serves as a basis for defining change. (2) An approved and released document, or a set of documents, each of a specific revision; the purpose of which is to provide a defined basis for managing change. (3) The currently approved and released configuration documentation. (4) A released set of files consisting of a software version and associated configuration documentation.
A tested and certified version of a deliverable, representing the basis for further development, that can be modified only through formal change control procedures. A particular version becomes a baseline when a responsible group decides to designate it as such.
See Configuration Baseline.
A collection of approved design information about a configuration. The current configuration is acknowledged to be the approved baseline plus approved changes.
A work product (such as software or documentation) that has been formally reviewed, approved, and delivered and can only be changed through formal change control procedures. See Allocated Baseline, Functional Baseline, Operational Baseline, Product Baseline.
1. A starting point or condition against which future changes are measured. 2. A named set of object versions which fixes a configuration at a particular point in time. A baseline normally represents a milestone or key deliverable of a project.
The point at which some deliverable produced during the software engineering process is put under formal change control.
See Reference-Configuration . An interim result, chosen and released at a specific point in time during the software development process which is assembled to a software configuration, so that it is possible to refer to it in later phases of the developmental process.
(1) A description of a system and its components (configuration items) at a particular period of time, and any approved updates to the baseline. (2) A work product that has been placed under formal configuration management. A baseline should be changed only through formal configuration management procedures. Some baselines may be project deliverables while others provide the basis for further work. See also work product.
an authorized software work product that can only be changed through formal change control procedures
Configuration management is the process of managing change in hardware, software, firmware, documentation, measurements, etc. As change requires an initial state and next state, the marking of significant states within a series of several changes becomes important. The identification of significant states within the revision history of a configuration item is the central purpose of baseline identification.CMMI Product Team, "Chpt 7, Maturity Level 2: Managed, Configuration Management, SP 1.3," in Capability Maturity Model Integration, Version 1.1 (CMMI-SE/SW/IPPD/SS, V1.1): Staged Representation, Carnegie Mellon Software Engineering Institute.
|
