EIA-649 Configuration Management Standard Rev C - Terminology Flashcards
AQUIRER (1)
An individual or enterprise that (1) commissions the engineering or design of a product
AQUIRER (2)
An individual or enterprise that (2) is a prospective purchaser of the end products of a system or a portion thereof; (3) is a procurer of a product; (4) is a user or consumer of the product; or (5) an obtainer of output.
AQUIRER (3)
An individual or enterprise that (3) is a procurer of a product; (4) is a user or consumer of the product; or (5) an obtainer of output.
AQUIRER (3)
An individual or enterprise that (4) is a user or consumer of the product; or (5) an obtainer of output.
APPROVAL AUTHORITY (1)
The organization or person authorized to approve: (1) A configuration change to a product
APPROVAL AUTHORITY (2)
The organization or person authorized to approve: (2) Changes to product definition information and other related documents
APPROVAL AUTHORITY (3)
The organization or person authorized to approve: (3) Release (or cancellation) of documents for use anywhere or in a specific program
APPROVAL AUTHORITY (4)
The organization or person authorized to approve: (4) Commitment of resources.
APPROVED CONFIGURATION
The baseline plus any approved changes
ARTIFACT (1)
(1) A contained piece of information that is used or produced by a software or hardware development process, or by deployment and operation of a system. Examples of artifacts include: representational views, model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, a word-processing document, or a mail message.
ARTIFACT (2)
(2) Physical entities and their elements such as patterns, parts, components, and assemblies. New artifacts can be created by grouping existing artifacts.
BASELINE
Configuration of a product, at a specific point in time, which serves as a basis for defining change, for conducting verifications, and for other management activities. For a software product, the build baseline includes the actual product.
CHANGE BOARD
A group comprised of technical and administrative representatives who review and recommend approval or disapproval to the approval authority, of changes and variances to a configuration managed product and its supporting documentation.
CONFIGURATION (1)
(1) The product attributes of an existing or planned product, or a combination of products, i.e., product requirements, the product, and associated product configuration information
CONFIGURATION (2)
(2) one of a series of sequentially created variations of a product.
CONFIGURABILITY
The capability to temporarily adapt or rearrange the configuration of a system or system of systems to accommodate the needs of a particular application or deployment.
CONFIGURATION AUDIT
Review of processes, product definition information, documented verification of compliance with requirements, and an inspection of products, to confirm that products have achieved their required attributes and conform to released product configuration definition information.
CONFIGURATION BASELINE
Configuration of a product, at a specific point in time, which serves as a basis for defining change, for conducting verifications, and for other management activities. For a software product, the build baseline includes the actual product.
CONFIGURATION CHANGE
A change to the product configuration information and the product.
CONFIGURATION CHANGE MANAGEMENT
The CM function that ensures changes to and variances from a configuration baseline are properly identified, recorded, evaluated, dispositioned, and incorporated and verified as appropriate.
CONFIGURATION CONTROL
The systematic proposal, justification, evaluation, coordination, disposition of proposed changes or requested variances and the implementation of all approved changes or variances in the configuration after the establishment of a configuration baseline.
CONFIGURATION IDENTIFICATION (1)
The CM function which (1) assigns unique identifiers to each product and product configuration information;
CONFIGURATION IDENTIFICATION (3)
The CM function which (3) selects, defines, documents, and baselines product attributes.
CONFIGURATION IDENTIFICATION (2)
The CM function which (2) establishes a structure for products and product configuration information;
CONFIGURATION ITEM (CI)
A product, allocated components of a product, or both, that satisfies an end use function, has distinct requirements, functionality and/or product relationships, and is designated for distinct control.
CONFIGURATION MANAGEMENT (CM)
A technical and management process applying appropriate processes, resources, and controls, to establish and maintain consistency between product configuration information, and the product.
CONFIGURATION STATUS ACCOUNTING (CSA)
The CM function that formalizes the recording and reporting of the established product configuration information, the status of requested changes, and the implementation of approved changes including changes occurring to product units during operation and maintenance.
CONFIGURATION VERIFICATION
Verification of requirements and incorporation of approved configuration changes (see verification).
CUSTOMIZATION
The action to permanently establish a configuration of a system or system of systems with a unique set of items to satisfy a particular application or deployment with no intention of changing or rearranging the custom configuration over the life of the product.
DESIGN ACTIVITY
An organization that has, or has had, responsibility for the design of an item. (Adapted from ASME Y14.100)
DESIGN RELEASE CONFIGURATION
The set of design information, incrementally released to date, by the development activity for a product during a product’s definition (development) phase.
DISPOSITION (NOUN)
DISPOSITION (VERB)
To make a decision on a change to either approve, disapprove, defer or cancel.
