The Institute of Electrical and Electronics Engineers, New York. IEEE Guide to Software Configuration Management Plans, 1990. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Unified Versioning through Feature Logic - Zeller, Snelting (1997) (23 citations) (Correct)
....Management, Theory, Standardization Additional Key Words and Phrases: Feature logic, Version sets 1 Introduction Software Configuration Management, or SCM for short, is the discipline for controlling the evolution of software systems. SCM encompasses general configuration management procedures [21, 22] like identification of components and structures, control of changes and releases, status accounting, or audit and review, as well as software specific tasks [12] like manufacture, process management, and team work. SCM is one of the basic prerequisites for process improvement, stipulated by the ....
....sets, that is, sets of software components identified by their attributes. The basic SCM operations of selecting a version and composing a consistent configurations are modeled by means of set operations, as provided by feature logic. 3. 1 Versions and Components According with the SCM standards [21, 22], we consider that the object of interest in SCM is a family of software products. Each of these software products breaks down in several components, each of which may exist in several component versions. A component version is an unbreakable, unambiguous configuration item. In the SCM domain, ....
The Institute of Electrical and Electronics Engineers, Inc. IEEE Guide to Software Configuration Management Plans. New York,
Unified Versioning through Feature Logic - Zeller, Snelting (1997) (23 citations) (Correct)
....Management, Theory, Standardization Additional Key Words and Phrases: Feature logic, Version sets 1 Introduction Software Configuration Management, or SCM for short, is the discipline for controlling the evolution of software systems. SCM encompasses general configuration management procedures [21, 22] like identification of components and structures, control of changes and releases, status accounting, or audit and review, as well as software specific tasks [12] like manufacture, process management, and team work. SCM is one of the basic prerequisites for process improvement, stipulated by the ....
....sets, that is, sets of software components identified by their attributes. The basic SCM operations of selecting a version and composing a consistent configurations are modeled by means of set operations, as provided by feature logic. 3. 1 Versions and Components According with the SCM standards [21, 22], we consider that the object of interest in SCM is a family of software products. Each of these software products breaks down in several components, each of which may exist in several component versions. A component version is an unbreakable, unambiguous configuration item. In the SCM domain, ....
The Institute of Electrical and Electronics Engineers, Inc. IEEE Guide to Software Configuration Management. New York,
Designing Configuration Management Tools for Dynamically Composed .. - Schmerl (1998) (Correct)
.... configuration management becomes more important [Heimbigner96] In order to understand the role that configuration management plays in the development of software, Dart [Dart90] summarises the four operational aspects of a configuration management, based on the relevant IEEE standards [IEEE88, IEEE90], as: Identification: Each configuration item within a system needs to be identified. The attributes needed to identify a configuration item are: the kind of configuration item, its name, its version, and an indication of the configuration(s) to which it belongs. It is also necessary to identify ....
The Institute of Electrical and Electronics Engineers, Incorporated. IEEE Guide to Software Configuration Management, ANSI/IEEE Standard 828-1990, New York, 1990.
Unified Versioning through Feature Logic - Zeller, Snelting (1997) (23 citations) (Correct)
....Management, Theory, Standardization Additional Key Words and Phrases: Feature logic, Version sets 1 Introduction Software Configuration Management, or SCM for short, is the discipline for controlling the evolution of software systems. SCM encompasses general configuration management procedures [21, 22] like identification of components and structures, control of changes and releases, status accounting, or audit and review, as well as software specific tasks [12] like manufacture, process management, and team work. SCM is one of the basic prerequisites for process improvement, stipulated by ....
....sets, that is, sets of software components identified by their attributes. The basic SCM operations of selecting a version and composing a consistent configurations are modeled by means of set operations, as provided by feature logic. 3. 1 Versions and Components According with the SCM standards [21, 22], we consider that the object of interest in SCM is a family of software products. Each of these software products breaks down in several components, each of which may exist in several component versions. A component version is an unbreakable, unambiguous configuration item. In the SCM domain, ....
The Institute of Electrical and Electronics Engineers, Inc. IEEE Guide to Software Configuration Management Plans. New York, 1990. ANSI/IEEE Standard 828-1990.
Configuration Management Concept for Lyee Software - GRUHN, IJIOUI, PETERS, SCHÄFER (2002) (Correct)
No context found.
The Institute of Electrical and Electronics Engineers, New York. IEEE Guide to Software Configuration Management Plans, 1990.
Configuration Management Concept for Lyee Software - GRUHN, IJIOUI, PETERS, SCHÄFER (2002) (Correct)
No context found.
The Institute of Electrical and Electronics Engineers, New York. IEEE Guide to Software Configuration Management, 1988.
Configuration Management for Lyee Software - Gruhn, Ijioui, Peters, Schäfer (2003) (Correct)
No context found.
The Institute of Electrical and Electronics Engineers, New York, IEEE Guide to Software Configuration Management Plans, ANSI/IEEE Standard 828--1990 (1990).
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC