1、 Reference number ISO/IEC TR 18018:2010(E) ISO/IEC 2010TECHNICAL REPORT ISO/IEC TR 18018 First edition 2010-02-15Information technology Systems and software engineering Guide for configuration management tool capabilities Technologies de linformation Ingnierie des systmes et du logiciel Guide pour l
2、es capacits doutil de gestion de configuration ISO/IEC TR 18018:2010(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and inst
3、alled on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software prod
4、ucts used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found,
5、please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2010 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and mic
6、rofilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/
7、IEC 2010 All rights reservedISO/IEC TR 18018:2010(E) ISO/IEC 2010 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Normative references1 3 Terms and definitions .1 4 Application of this Technical Report.3 4.1 Overview.3 4.2 CM personnel.3 4.3 Tool suppliers 3 4.4 Acquirers3
8、 5 Capabilities of configuration management tools.4 5.1 Overview of configuration management tool capabilities 4 5.2 Configuration management tool capabilities .4 5.3 Configuration identification6 5.4 Configuration baselining 7 5.5 Configuration control8 5.6 Configuration status accounting .12 5.7 C
9、onfiguration auditing13 5.8 Release management and delivery15 5.9 Other configuration management tool capabilities .16 Annex A (informative) Focus areas of each reference17 Annex B (informative) Configuration management services .20 Bibliography27 ISO/IEC TR 18018:2010(E) iv ISO/IEC 2010 All rights
10、reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards throug
11、h technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also t
12、ake part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepar
13、e International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. In exceptional circumstances, the joint t
14、echnical committee may propose the publication of a Technical Report of one of the following types: type 1, when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts; type 2, when the subject is still under technical development or where
15、for any other reason there is the future but not immediate possibility of an agreement on an International Standard; type 3, when the joint technical committee has collected data of a different kind from that which is normally published as an International Standard (“state of the art”, for example).
16、 Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or
17、useful. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC TR 18018, which is a Technical Report of type 2, was prepared by Joint Techni
18、cal Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering. ISO/IEC TR 18018:2010(E) ISO/IEC 2010 All rights reserved vIntroduction Configuration management (CM) is a process central to the software engineering life cycle. CM has been established as an I
19、SO/IEC standard life cycle process in ISO/IEC 12207:2008, Systems and software engineering Software life cycle processes and ISO/IEC 15288:2008, Systems and software engineering System life cycle processes. ISO/IEC 12207 and ISO/IEC 15288 describe a comprehensive set of processes, activities and tas
20、ks to be performed when acquiring or developing software. However, these documents do not address the capabilities that a CM tool user can expect from a tool in order to support the CM process and other software engineering life cycle activities. There is a gap between CM process descriptions and co
21、rresponding CM process automation which affects both tool users and tool suppliers. This Technical Report provides guidance in the evaluation and selection for CM tools during acquisition. CM tool evaluation by prospective users can be complex, time consuming, and expensive. This Technical Report he
22、lps to characterize what a CM tool can and cannot do in the CM process. This Technical Report provides guidance for tool manufacturers in implementing a minimum set of capabilities. The capabilities defined in this Technical Report are linked to ISO/IEC 12207 and ISO/IEC 15288, and will provide tool
23、 manufacturers with guidance on the characteristics their tools should support to meet these International Standards. TECHNICAL REPORT ISO/IEC TR 18018:2010(E) ISO/IEC 2010 All rights reserved 1Information technology Systems and software engineering Guide for configuration management tool capabiliti
24、es 1 Scope This Technical Report provides guidance for configuration management tool capabilities from which systems and software development life cycle activities can be supported. ISO/IEC 14102:2008, Information technology Guideline for the evaluation and selection of CASE tools, details a set of
25、evaluation criteria for CASE tools without referencing a specific activity or task which the tool supports. This lack of consideration on a specific activity or task causes users confusion and difficulty in evaluating and selecting the right tools. This Technical Report supplements ISO/IEC 14102:200
26、8 by providing a set of minimum tool capabilities for configuration management. It can be used as the set of criteria by a potential user during an acquisition process, or by a configuration management tool supplier to help identify desirable tool capabilities. 2 Normative references The following r
27、eferenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 12207:2008, Systems and software engineering Software li
28、fe cycle processes ISO/IEC 15288:2008, Systems and software engineering System life cycle processes 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 attribute property associated with a set of real or abstract things that is some characteristi
29、c of interest 3.2 baseline version of a configuration, 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 ISO/IEC 12207:2008 and ISO/IEC 15288:20
30、08 3.3 branch deviation from the main development line for a configuration item, which allows different persons to work on the same item at the same time ISO/IEC TR 18018:2010(E) 2 ISO/IEC 2010 All rights reserved3.4 build process of generating (archiving) an executable and testable system from sour
31、ce versions or baselines NOTE The build needs to compile and link the various versions in the correct order. The build tools can be integrated into a configuration management tool. 3.5 change request CR formal procedure for submitting a request for an adjustment of a configuration item 3.6 configura
32、tion item entity within a configuration that satisfies an end use function and that can be uniquely identified at a given reference point ISO/IEC 12207:2008 and ISO/IEC 15288:2008 3.7 configuration management CM coordinated activities to direct and control configuration 3.8 CM services abstract desc
33、ription of work done by CM tools NOTE A service is self contained, coherent, discrete, and can be composed of other services. 3.9 CM tool software product that can assist software engineers by providing automated support for configuration management activities 3.10 configuration status accounting CS
34、A element of configuration management that consists of the recording and reporting of information needed to manage a configuration effectively ISO/IEC 24765 3.11 delta difference between two versions 3.12 software/system element element that defines and prescribes what a software or system is compos
35、ed of (for example, requirements, design, code, test cases, and version number) NOTE An element can contain sub elements or other software/system elements that are dependent on the top level element. 3.13 release particular version of a configuration item that is made available for a specific purpos
36、e (for example, test release) ISO/IEC TR 18018:2010(E) ISO/IEC 2010 All rights reserved 33.14 traceability degree to which each element in a software development product establishes its reason for existing 3.15 version identified instance of a configuration item NOTE Modification to a version of a s
37、oftware product, resulting in a new version, requires configuration management action. 3.16 version identifier supplementary information used to distinguish a version of a configuration item from other versions NOTE Version numbers are used to compare the version of the software product against anot
38、her version. 4 Application of this Technical Report 4.1 Overview This clause presents the benefits to groups of people that acquire, supply, develop, operate, and maintain a CM tool. The objective is to provide a road map for the users of this Technical Report so that they can orient themselves in i
39、t and apply it judiciously. 4.2 CM personnel Personnel involved in the performance of one or more CM activities will benefit from this Technical Report as follows: obtain a better understanding of the relationship between the activities in which they are involved and CM tool capabilities identify pr
40、ocesses or activities that can be improved through better support by a CM tool have an objective basis for a better comparison, evaluation, and assessment of CM tools 4.3 Tool suppliers Suppliers of software engineering tools will benefit from this Technical Report as follows: develop CM tools consi
41、stent with the International Standards ISO/IEC 12207:2008, ISO/IEC 15288:2008, and ISO/IEC 14102:2008 provide CM tools that can be shown to support an internationally accepted set of capabilities 4.4 Acquirers People involved in the purchase of CM tools will benefit from this Technical Report as fol
42、lows: review CM services that can contribute to CM process improvement identify criteria for selecting CM tools compare competing CM tools based upon this Technical Report ISO/IEC TR 18018:2010(E) 4 ISO/IEC 2010 All rights reserved5 Capabilities of configuration management tools 5.1 Overview of conf
43、iguration management tool capabilities Throughout the systems and software life cycle, different artifacts (e.g., hardware, software, documents) exist in different versions at different times and changes arise constantly. Configuration Management (CM) verifies and assures that a product performs as
44、intended by providing visibility and control of products functional and physical characteristics. A CM tool can provide automated assistance for CM activities: configuration identification, change management, reports, status accounting, and auditing. This Technical Report provides the tool capabilit
45、ies for the automation of CM activities to support software and systems lifecycle processes. NOTE The following documents have been reviewed for identifying the CM tool capabilities: ISO/IEC 12207:2008, ISO/IEC 15288:2008, ISO/IEC TR 15846, ISO/IEC TR 19759 SWEBOK, ISO/IEC 14102:2008, ISO 10007:2003
46、, ISO/IEC 15940:2006, IEEE 828:1990, ANSI/EIA 649:1998, and commercial tool information. The life cycle processes and activities from these references have been used as the basis for the CM tool capability categorization found in this document. 5.2 Configuration management tool capabilities 5.2.1 Ov
47、erview The CM activities described in ISO/IEC 12207:2008 and ISO/IEC 15288:2008 includes configuration identification, configuration baselining, configuration control, configuration status accounting, configuration auditing, and release management and delivery. Besides of these CM activities, integr
48、ating CM tools into the software development environment is also a key for automated CM support. The CM tool should provide not only the capabilities supporting the CM activities but also the tool integration capability into other tools and platforms. 5.2.2 Configuration identification Configuration
49、 identification should capture the attributes of the software to be controlled: the software contents, the different versions of contents, the operation data, and any other essential elements that constitute the configuration item. The tools should provide the following capabilities for the configuration items: identifying configuration items specifying configuration item relationship defining states and specifying status of configuration items NOTE Refer to ISO/IEC 12207:2008 and ISO/IEC 152
