Metrics Glossary

Software Metrics Glossary - C : Part 1

CAB Change Advisory Board (Reference ITIL® Sept 2002)
CAB/EC Change Advisory Board/Emergency Committee (Reference ITIL® Sept 2002)
Calendar Unit The smallest unit of time used in scheduling the project. Calendar units are generally in hours, days, or weeks, but can also be in shifts or even in minutes. Used primarily in relation to project management software. ( Reference : PMI:PMBOK)
calibration set of operations that establish, under specified conditions, the relationship between values indicated by a measuring instrument or measuring system, or values represented by a material measure or a reference standard, and the corresponding values realized by standards [ISO 10012] ( Reference : TC176:ISO 9000:2000)
Candidate FSM Method a documented software size measurement method submitted for compliance assessment for compliance to ISO/IEC 14143-1:1998 ( Reference : ISO/IEC JTC1/SC7:14143-2)
candidate solution A solution that is developed for consideration when seeking an optimal solution. [Bate - SEI] ( Reference : SEI:SE-CMM)
capability ability of an object (4.1.6) to realize a product (4.3.5) that will fulfil the requirement (4.1.7) for that product (4.3.5) ( Reference : TC176:ISO 9000:2000)
capability A measure of the system's ability to achieve the mission objectives, given that the system is dependable and suitable. Examples of capability measures are accuracy, range, payload, lethality, information rates, number of engagements, and destructiveness. Capability measures can be used as performance requirements, design constraints. and/or technical exit criteria. Capability is a systems engineering metric. [MIL-STD 499B] ( Reference : SEI:SE-CMM)
capability dimension the set of process attributes comprising the capability aspects of the reference model of processes and process capability ( Reference : ISO/IEC JTC1/SC7:15504-9)
capability evaluation An appraisal made by a trained team of professionals, using an established method (e.g., the SEI software capability evaluation method) to: (1) identify contractors qualified to perform specific task(s), or (2) monitor the state of the process used on an all information pertinent to the systems engineering process. This repository is used to preserve a historical view into the tradeoffs and decisions that evolved the system architecture and design into a given state. [IEEE P1220] ( Reference : SEI:SE-CMM)
capability level A set of common features (sets of generic practices) that work together to provide a major enhancement in the capability to perform a process area. [SPICE BPG 0.06] (adapted) ( Reference : SEI:SE-CMM)
capability maturity model A descriptive model of the stages through which organizations progress as they define, implement, evolve, and improve their processes. This model serves a guide for selecting process improvement strategies by facilitating the determination of the current process capabilities and the identification of issues most critical to quality and process improvement within a particular domain, such as software engineering or systems engineering. [CMM for Software] (adapted) ( Reference : SEI:SE-CMM)
capability maturity model A description of the stages through which software organizations evolve as they define, implement, measure, control, and improve their software processes. This model provides a guide for selecting process improvement strategies by facilitating the determination of current process capabilities and the identification of the issues most critical to software quality and process improvement. ( Reference : SEI:SW-CMM)
capability set a collection of characteristics that describes the functionality of a resource or an enterprise activity ( Reference : TC184/SC5:15704)
Capital expenditure A form of spending in which an enterprise trades money (capital) for acquisition of tangible objects such as furniture, computers, and the like. ( Reference : IFPUG CPM 4.1)
Cardinality Describes the constraint on the number of entity instances that are related to the subject entity through a relationship. Cardinality is represented for each entity participating in a relationship by indicating the minimum and maximum number of its instances that may be associated with one particular instance of the related entity. ( Reference : ISO/IEC JTC1/SC7; CDIF:15474-1)
CASE Computer-Aided Systems Engineering (Reference ITIL® Sept 2002)
CASE needs The organizational requirements which are met by CASE tool characteristics. These characteristics are detailed in Clause 9 of ISO/IEC 14102 : 1995, Information technology - Guideline for the evaluation and selection of CASE tools. They include : management process, development process, maintenance, documentation, configuration management, quality assurance, verification, validation, environment needs, CASE tool integrability, quality characteristics, acquisition needs, implementation needs, support indicators, and certification requirements. ( Reference : ISO/IEC JTC1/SC7:14471)
CASE tool a program that is used as an aid to systems development ( Reference : ISO/IEC JTC1/SC7; CDIF:15474-3)
categorization scheme An orderly combination of views and categories related to software. ( Reference : ISO/IEC JTC1/SC7:12182)
category A specifically defined division or grouping of software based upon one or more attributes or characteristics. ( Reference : ISO/IEC JTC1/SC7:12182)
category Classification of a group of Configuration Items, Change documents or Problems. (Reference ITIL® Sept 2002)
causal analysis The analysis of defects to determine their underlying root cause. ( Reference : SEI:SW-CMM)
causal analysis meeting A meeting, conducted after completing a specific task, to analyze defects uncovered during the performance of that task. ( Reference : SEI:SW-CMM)
CCTA Central Computer and Telecommunications Agency (Reference ITIL® Sept 2002)
certification The development of a statement that an asset has been assessed according specified criteria. ( derived from IEEE Std 1420.1a) ( Reference : IEEE SESC:729)
certification Acknowledgement, based on a formal demonstration, that a system or component complies with its specified requirements and is acceptable for operational use. [IEEE STD 610.12-1990] (adapted) ( Reference : SEI:SE-CMM)
Cfsu: COSMIC functional size unit Reference :COSMIC-FFP MM Version 2.1
change The addition, modification or removal of approved, supported or baselined hardware, network, software, application, environment, system, desktop build or associated documentation. (Reference ITIL® Sept 2002)
Change Advisory Board A group of people who can give expert advice to Change Management on the implementation of Changes. This Board is likely to be made up of representatives from all areas within IT and representatives from business units. (Reference ITIL® Sept 2002)
change authority As "configuration board" in ISO 10007. ( Reference : SC7/WG8:15846)
change authority A group that is given the authority to approve Change, e.g. by a project board. Sometimes referred to as the Configuration Board (Reference ITIL® Sept 2002)
change control An element of configuration management, consisting of the evaluation, coordination, approval or disapproval, and implementation of changes to work products. [SE-CMM] ( Reference : SEI:SE-CMM)
change control The procedure to ensure that all Changes are controlled, including the submission, analysis, decision making, approval, implementation and post implementation of the Change. (Reference ITIL® Sept 2002)
change control board A group of people responsible for evaluating and approving or disapproving proposed changes to work products, and for ensuring implementation of approved changes. Configuration control board. ( Reference : SEI:SE-CMM)
Change document Request for Change, Change control form, Change order, Change record. (Reference ITIL® Sept 2002)
Change history Auditable information that records, for example, what was done, when it was done, by whom and why (Reference ITIL® Sept 2002)
Change in Scope See scope change. ( Reference : PMI:PMBOK)
Change log A log of Requests for Change raised during a project, showing information on each Change, its evaluation, what decisions have been made and its current status, e.g. raised, reviewed, approved, implemented, or closed. (Reference ITIL® Sept 2002)
Change Management Process of controlling Changes to the infrastructure or any aspect of services, in a controlled manner, enabling approved Changes with minimum disruption. (Reference ITIL® Sept 2002)
Change record A record containing details of which CIs are affected by an authorised Change (planned or implemented), and how. (Reference ITIL® Sept 2002)
change request A formal request to change some aspect of an established baseline. [Jones - IBM] ( Reference : SEI:SE-CMM)
change-over system A temporary information processing system used to facilitate the transition from an operational system to its successor. ( Reference : ISO/IEC JTC1/SC1:2382-20)
Character Set A character set is a collection of characters used in an Encoding to represent terminal symbols. The character set used is significant in the encoding of text and string meta-attributes for a CDIF Transfer. ( Reference : ISO/IEC JTC1/SC7; CDIF:15474-1)
Characteristic Entity A meta-entity that provides additional attribution for another meta-object. Other common names for Characteristic Entity are: Attributive Entity and Dependent Entity. Each instance of a characteristic meta-entity is logically only related to one instance of one other meta-object, therefore an importer could incorporate the meta-attributes of a characteristic meta-entity with those of the 'owning' meta-object, where the owning meta-object is the one to which the characteristic meta-entity is related with a cardinality of 1:1. ( Reference : ISO/IEC JTC1/SC7; CDIF:15474-1)
Chart of Accounts Any numbering system used to monitor project costs by category (e.g., labor, supplies, materials). The project chart of accounts is usually based upon the corporate chart of accounts of the primary performing organization. See also code of accounts. ( Reference : PMI:PMBOK)
Charter See project charter. ( Reference : PMI:PMBOK)
CI Configuration Item (Reference ITIL® Sept 2002)
classification A choice within a category. (IEEE Std 1044-1993) ( Reference : IEEE SESC:729)
classification Process of formally grouping Configuration Items by type, e.g. software, hardware, documentation, environment, application. (Reference ITIL® Sept 2002)
classification Process of formally identifying Changes by type e.g. project scope Change request, validation Change request, infrastructure Change request. (Reference ITIL® Sept 2002)
classification Process of formally identifying Incidents, Problems and Known Errors by origin, symptoms and cause. (Reference ITIL® Sept 2002)
Clear Text A form of encoding where the resulting physical file is human-readable. ( Reference : ISO/IEC JTC1/SC7; CDIF:15474-1)
Closure When the Customer is satisfied that an incident has been resolved. (Reference ITIL® Sept 2002)
CMDB Configuration Management Database (Reference ITIL® Sept 2002)
COP Code of Practice (Reference ITIL® Sept 2002)
Code of Accounts Any numbering system used to uniquely identify each element of the work breakdown structure. See also chart of accounts. ( Reference : PMI:PMBOK)
commitment A pact that is freely assumed, visible, and expected to be kept by all parties. [CMM for Software] ( Reference : SEI:SE-CMM)
common cause (of a defect) A cause of a defect that is inherently part of a process or system. Common causes affect every outcome of the process and everyone working in the process. (See special cause for contrast.) ( Reference : SEI:SW-CMM)
common features The subdivision categories of the SA-CMM key process areas. The common features are attributes that indicate whether the implementation and institutionalization of a key process area can be effective, repeatable, and lasting. The SA-CMM's common features are the following: Commitment to perform, Ability to perform, Activities performed, Measurement and analysis, and Verifying implementation. ( Reference : SEI:SA-CMM)
Communications Planning Determining the information and communications needs of the project stakeholders. ( Reference : PMI:PMBOK)
compatibility (1) The ability of two or more systems or components to perform their required functions while sharing the same environment. (2) The ability of two or more systems or components to exchange information. [IEEE STD 610.12-1990] (adapted) ( Reference : SEI:SE-CMM)
compatible assessment model an operational model, used for performing assessments, which meets the defined requirements (for model purpose, scope, elements and indicators, mapping to the reference model, and translation of results) for conformance to the reference model ( Reference : ISO/IEC JTC1/SC7:15504-9)
competent assessor a person who has demonstrated the necessary skills, competencies and experience for performing process assessments ( Reference : ISO/IEC JTC1/SC7:15504-9)
Complex processing GSC One of the 14 general system characteristics describing the degree to which processing logic influences the development of the application. ( Reference : IFPUG CPM 4.1)
complexity (1) The degree to which a system or component has a design or implementation that is difficult to understand and verify. (2) Pertaining to any of a set of structure-based metrics that measure the attribute in (1). [IEEE STD 610.12-1990] ( Reference : SEI:SE-CMM)
component An entity with discrete structure, such as an assembly or software module, within a system considered at a particular level of analysis. ( Reference : ISO/IEC JTC1/SC7; IEC TC56:15026)
Component A discrete, essentially homogeneous part of a system that mutually interacts with other components of the system, thereby contributing to the system properties and characteristics. NOTES -- 1) A component is the lowest level of interest in any branch of the architecture of a system, i.e. a component is expected to meet its specifications with an acceptable level of certainty 2) From the system viewpoint, a component typically has a technology or discipline-specific nature. ( Reference : SC7/WG7:15288)
component One of the parts that make up a system. A component may be hardware or software and may be subdivided into other components. [IEEE STD 610.12-1990] ( Reference : SEI:SE-CMM)
Computer Aided Systems Engineering A software tool for programmers. It provides help in the planning, analysis, design and documentation of computer software. (Reference ITIL® Sept 2002)
concept of operations A user-oriented description of a systemís operational characteristics from the end userís viewpoint. (derived from IEEE Std1362) ( Reference : IEEE SESC:729)
conceptual system design A system design activity concerned with specifying the logical aspects of the system organization, its processes, and the flow of information through the system. ( Reference : ISO/IEC JTC1/SC1:2382-20)
concession authorization to use or release a product (4.3.5) which does not conform to specified requirements (4.1.8) NOTE 1 - A concession is limited to the delivery of a product (4.3.5) that has specific nonconforming characteristics (4.4.1) within specific limits for an agreed time or quantity. NOTE 2 - A concession is typically issued as a document (4.7.1) to meet the needs of audit (4.6.7). ( Reference : TC176:ISO 9000:2000)
concession; waiver written authorization to use or release a quantity of material, components or stores already produced but which do not conform to the specified requirements ( Reference : TC176:8402)
Concurrent Engineering An approach to project staffing that, in its most general form, calls for implementors to be involved in the design phase. Sometimes confused with fast tracking. ( Reference : PMI:PMBOK)
conditional Information supplied with every package to which it is relevant. ( Reference : ISO/IEC JTC1/SC7:6592)
configuration arrangement of the elements of a system (4.1.1) NOTE - Further definitions and guidance on principles and practice related to configuration may be obtained in ISO 10007. ( Reference : TC176:ISO 9000:2000)
configuration The arrangement of a computer system or component as defined by the number, nature, and interconnections of its constituent parts. (Adapted from IEEE Std 610.12-1990) ( Reference : IEEE SESC:729)
configuration In configuration management, the functional and physical characteristics of hardware or software as set forth in technical documentation or achieved in a product. [IEEE STD 610.12-1990] ( Reference : SEI:SE-CMM)
configuration baseline Configuration of a product or system established at a specific point in time, which captures both the structure and details of that product or system, and enables that product or system to be rebuilt at a later date. (Reference ITIL® Sept 2002)
configuration baseline A snapshot or a position which is recorded. Although the position may be updated later, the baseline remains unchanged and available as a reference of the original state and as a comparison against the current position (PRINCE2). (Reference ITIL® Sept 2002)
configuration control An element of configuration management, consisting of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items after formal establishment of their configuration identification. [IEEE-STD-610] ( Reference : SEI:SW-CMM)
configuration control Activities comprising the control of Changes to Configuration Items after formally establishing its configuration documents. It includes the evaluation, coordination, approval or rejection of Changes. The implementation of Changes includes changes, deviations and waivers that impact on the configuration (Reference ITIL® Sept 2002)
configuration control board Qualified personnel who evaluate, for approval or disapproval, all Proposed changes to the current developmental baseline. ( Reference : ISO/IEC JTC1/SC1:2382-20)
configuration data Data that reflect the current configuration or state of the system or its components. [Jones - IBM] ( Reference : SEI:SE-CMM)
configuration documentation Documents that define requirements, system design, build, production, and verification for a Configuration Item. (Reference ITIL® Sept 2002)
configuration identification An element of configuration management, consisting of selecting the configuration items for a system and recording their functional and physical characteristics in technical documentation. [IEEE-STD-610] ( Reference : SEI:SW-CMM)
configuration identification Activities that determine the product structure, the selection of Configuration Items, and the documentation of the Configuration Item's physical and functional characteristics, including interfaces and subsequent Changes. It includes the allocation of identification characters or numbers to the Configuration Items and their documents. It also includes the unique numbering of configuration control forms associated with Changes and Problems. (Reference ITIL® Sept 2002)
configuration item An aggregation of hardware, software, or both, that is designated for configuration management and treated as a single entity in the configuration management process. [IEEE-STD-610] ( Reference : SEI:SW-CMM)
configuration item (CI) Component of an infrastructure - or an item, such as a Request for Change, associated with an infrastructure - that is (or is to be) under the control of Configuration Management. CIs may vary widely in complexity, size and type, from an entire system (including all hardware, software and documentation) to a single module or a minor hardware component. (Reference ITIL® Sept 2002)
configuration management 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]. ( Reference : SEI:SA-CMM)
configuration management 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] ( Reference : SEI:SE-CMM)
Configuration Management 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. (Reference ITIL® Sept 2002)
Configuration Management tool A software product providing automatic support for Change, Configuration or version control. (Reference ITIL® Sept 2002)
Configuration Management
Database (CMDB)
A database that contains all relevant details of each CI and details of the important relationships between CIs. (Reference ITIL® Sept 2002)
configuration management library system 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] ( Reference : SEI:SE-CMM)
configuration management library system The tools and procedures to access the contents of the software baseline library. ( Reference : SEI:SW-CMM)
Configuration Management plan Document setting out the organisation and procedures for the Configuration Management of a specific product, project, system, support group or service. (Reference ITIL® Sept 2002)
Configuration structure A hierarchy of all the CIs that comprise a configuration. (Reference ITIL® Sept 2002)
configuration unit The lowest level entity of a configuration item or component that can be placed into, and retrieved from, a configuration management library system. [CMM for Software] ( Reference : SEI:SE-CMM)
conformity fulfilment of a requirement (4.1.7) NOTE Ė This definition is consistent with ISO/IEC Guide 2 but differs from it in phrasing to fit into the ISO 9000 concept system. ( Reference : TC176:ISO 9000:2000)
Connectivity Two graphic objects are connected if they share common pixels at the boundaries of their respective shapes. A synonym for "Connects" is touch. Within the context of the CDIF presentation subject areas, connectivity is more restrictive. Two objects are connected if the movement of one will result in a change in the representation of the other. ( Reference : ISO/IEC JTC1/SC7; CDIF:15474-1)
consistency The degree of uniformity, standardization, and freedom from contradiction among the documents or parts of system or component. [IEEE-STD-610] ( Reference : SEI:SW-CMM)
Constraint A constraint is generally a restriction on the value of an attribute or the existence of any object based on the value or existence of one or more others. In CDIF a constraint may be classed as computable (i.e., code may be built to implement the constraint) or non-computable (e.g., a constraint expressed in natural language). An example of a non-computable constraint -- "No two instances of DFMProcess may have the same value for the meta-attribute Name." An example of a computable textual constraint "ForAny (DFMProcess,c) Unique (c.Name)." ( Reference : ISO/IEC JTC1/SC7; CDIF:15474-1)
CTI Computer Telephony Integration (Reference ITIL® Sept 2002)