《BS-ISO-IEC-TR-15846-1998.pdf》由会员分享，可在线阅读，更多相关《BS-ISO-IEC-TR-15846-1998.pdf（28页珍藏版）》请在三一文库上搜索。
1、BRITISH STANDARD BS ISO/IEC TR 15846:1998 Information technology Software life cycle processes Configuration Management ICS 35.080 Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 15846:1998 This British Standard, having been pr
2、epared under the direction of the DISC Board, was published under the authority of the Standards Committee and comes into effect on 15 October 1999 BSI 04-2000 ISBN 0 580 35329 X National foreword This British Standard reproduces verbatim ISO/IEC TR 15846:1998 and implements it as the UK national st
3、andard. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software Engineering, which has the responsibility to: aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for
4、change, and keep the UK interests informed; monitor related international and European developments and promulgate them in the UK. A list of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British Standards which implement international o
5、r European publications referred to in this document may be found in the BSI Standards Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to include all th
6、e necessary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii,
7、 the ISO/IEC TR title page, pages ii to iv, pages 1 to 18 and a back cover. This standard has been updated (see copyright date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover. Amendments issued since publication Amd. No.DateComments
8、Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 15846:1998 BSI 04-2000i Contents Page National forewordInside front cover Forewordiv Text of ISO/IEC TR 158461 Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+
9、00:00 2006, Uncontrolled Copy, (c) BSI ii blank Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 15846:1998 ii BSI 04-200
10、0 Contents Page Forewordiv Introduction1 1Scope4 1.1Tailoring this Technical Report4 1.2Process roles4 2Conformance5 3Normative references5 4Definitions5 5Symbols (and abbreviated terms)6 5.1Abbreviations and acronyms6 6SCM Process Implementation6 6.1Initiating and defining the scope6 6.1.1 Defining
11、 the inputs to the SCM Process6 6.1.2 Defining the resources and constraints to the SCM Process6 6.1.3 Allocating responsibility and authority7 6.1.4 Criteria for selection of SCIs7 6.1.5 Defining the outcomes from the SCM Process7 6.2Planning7 6.3Controlling execution8 6.4Review and evaluation of t
12、he SCM Process8 6.5Closing8 7Software configuration identification8 7.1Identifying SCIs8 7.2Identifying software configuration baselines8 7.3Identifying software libraries9 7.4Advancement status9 8Software configuration control9 8.1Proposing changes9 8.2Evaluating the impact of proposed changes9 8.3
13、Implementing the changes10 8.4Communicating the disposition10 8.5Closing the changes10 9Software configuration status accounting10 9.1Recording the identification10 9.2Tracing changes10 9.3Reporting status accounting records10 10Software configuration evaluation11 11Software release management and d
14、elivery11 11.1 Handling11 11.2 Storing11 11.3 Replicating12 11.4 Packaging12 11.5 Delivering12 12Interface control12 Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 15846:1998 BSI 04-2000iii Page Annex A (normative) Mapping of
15、clauses between ISO/IEC TR 15846, ISO/IEC 12207 and ISO 1000713 Bibliography18 Figure 1 Role relationship between Supplier of SCM Process and other parties4 Table A.1 Mapping ISO/IEC TR 15846 to ISO/IEC 12207 and to ISO 1000714 Table A.2 Correspondence of clauses in ISO/IEC 12207 with ISO/IEC TR 158
16、4616 Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 15846:1998 iv BSI 04-2000 Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized syste
17、m for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of Technical Reports through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collabora
18、te in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The main task of technical
19、committees is to prepare Technical Reports, but in exceptional circumstances a technical 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 a Technical Report, despite repeated efforts
20、; type 2, when the subject is still under technical development or where for any other reason there is the future but not immediate possibility of an agreement on a Technical Report; type 3, when a technical committee has collected data of a different kind from that which is normally published as a
21、Technical Report (“state of the art”, for example). 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 data they p
22、rovide are considered to be no longer valid or useful. ISO/IEC TR 15846, which is a Technical Report of type 1, was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software engineering. Annex A forms an integral part of this Technical Report. Licensed
23、Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 15846:1998 BSI 04-20001 Introduction Relationship with other Technical Reports This Technical Report presents the requirements for the Software Configuration Management (SCM) Process. SCM
24、is a supporting CM Process to the life cycle of a software product, as described in ISO/IEC 12207, “Information technology Software life cycle processes”. SCM provides continuity across the Operation, Maintenance and Development Processes. Annex A (informative) of this Technical Report shows the rel
25、ationship with the clauses of ISO/IEC 12207. Where text has been quoted from ISO/IEC 12207:1995, that text is enclosed in a box, for ease of identification. This Technical Report keeps consistency with ISO 10007 “1995, Quality management Guidelines for configuration management”. The relationship of
26、the clauses in ISO 10007 to the clauses in this Technical Report is shown in Annex A. Types of software SCM administers any information that can be stored in a computer, including the software products. For example: specifications, database schema, test cases, user operating instructions, reusable c
27、oded objects, source and executable code, or data. SCM may also administer lists and records about software items of significance stored in other locations. For example: products installed at an operational site, or off-the-shelf products loaded on a network. Software products used as tools in the s
28、oftware environment to create, maintain, archive or restore the deliverable software product, are also types of software capable of being administered by SCM, as are the instructions and any customization or parameters to operate the tool. The software environment (for example development) may be de
29、liverable or may be proprietary. SCM can apply to few or to all items of software from a life-cycle activity. Implementation of the SCM Process SCM may be performed by a combination of software tools, methods and techniques. This Technical Report does not specify how to implement or perform the acti
30、vities and tasks in the SCM Process. The SCM requirements remain the same irrespective of the tools by which SCM is implemented. A number of emerging requirements for SCM (e.g. for product delivery to multiple sites with different product configurations, or for concurrent modification of Configurati
31、on Items CIs) may apply the SCM Process in this Technical Report to assist in controlling these emerging areas. Parties wishing to operate such tasks are advised to define the additional requirements in contract agreements or SCM policy and procedures. NOTEA procedure may a document, a template, etc
32、. Benefits This Technical Report can improve the visibility and accountability within the Operation, Maintenance and Development Processes by: w providing an appropriate documented and repeatable scheme for identifying and controlling electronic documents, code, interfaces, databases, etc., to suppo
33、rt the software life-cycle processes; w supporting a chosen development, maintenance or operations methodology fitting the requirements, standards, policies and directives, organization and management philosophy; w producing management and product information concerning the status of baselines, chan
34、ges, releases, versions, archives, etc.; w recursively defining a Software CI (SCI) to the level of individual items of significance to be controlled; w controlling the libraries used to store SCIs together with their status and related information; w invoking the ISO/IEC 12207 Processes to assure t
35、he integrity of the configurations; Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 15846:1998 2 BSI 04-2000 w controlling the software environment to enable a software product to be configured and reconfigured over its useful
36、life, including the software tools used to develop and verify the software product; to assure the integrity of the configuration (e.g. requirements tracker, SCM library guardian, release builder); and to run those tools (e.g. operating system); w storing and retrieving information on anomalies for i
37、ndividual SCIs and for software product configurations; w reporting the ownership for intellectual property considerations, such as licences or copyright. SCM in contractual relationships The SCM requirements are derived from at least three supply chain relationships: w acquirer placing work on the
38、software product supplier; w supplier responsible for delivering the software product; w subcontractor or software technicians to carry out the work. A fourth relationship may exist where the acquirer and supplier agree to use a third party archive (for escrow). In this relationship, in addition to
39、the bi-directional supply chain between acquirer and supplier, there is a triangular unidirectional flow from the supplier via the third-party archive to the acquirer (see Table 1 and Figure 1). Benefits to the prime acquirer For the acquirer some benefits of SCM are: w assurance of the completeness
40、 of the development, operations or maintenance requirements; w flexibility to enable changes to the requirements to be made under controlled conditions; w basis to establish evaluation criteria for SCM activities and tasks; w provision of complete and incomplete (e.g. engineering release) items. Use
41、 of this Technical Report is intended to help ensure: w project objectives meet customer and organizational constraints; w criteria and means for determining successful completion of project objectives are defined; w SCM software life-cycle products and their inter-relationships are defined; w inter
42、-relationships between processes are defined, where an SCM activity interacts with other software life-cycle process(es), e.g. Software Quality Assurance; w software baselines are controlled; w a plan for SCM activities, or related planning document, is created, used, monitored and adjusted; w SCM i
43、nterfacing between two or more parties or processes is defined. Where multiple teams and/or subcontractor relationships require more emphasis on interface management, the configuration control is normally tailored to cater to changes across interfaces rippling through levels of subcontracts or organ
44、izations. Benefits to the software product supplier Some benefits of SCM to the software product supplier are: w looking after items fulfilling the requirements and by controlling change; w support for the Joint Reviews Process by providing the status of SCIs (in this instance, the major software pr
45、oduct from a life-cycle process) attached to management milestones; w support for the Audit Process by concentrating on results which are measurable for compliance checking; w support for the Quality Assurance, Verification and Validation Processes to the extent they are present in the software life
46、 cycle. Licensed Copy: sheffieldun sheffieldun, na, Thu Nov 23 03:44:52 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 15846:1998 BSI 04-20003 Benefits to a subcontractor or software technician Some benefits of SCM to subcontractors or software technicians are: w stable baselines with assu
47、rance these baselines can be rebuilt; w consistent communication of status; w status and interdependence of outstanding requirements; w notification, analysis and reversal of change; w delegated change authority; w consistent method for handling, storing, replicating, packaging and releasing SCIs. B
48、enefits of any third party archive (escrow) The status of SCIs may be shared between a supplier, an acquirer and a third-party agent charged with holding items until some contract condition is met, for example, final payment or liquidation of the supplier. A benefit to the acquirer and supplier of a
49、 third-party agent applying SCM is the integrity of the deposited SCIs. This Technical Report provides requirements for guarding and retrieving these SCIs. RoleAs AcquirerAs Supplier Acquirer/operator/userTo software product supplier:To final client: request productmay supply software product receive SCM managed productmay use software product to deliver information technology service Software product supplier To SCM Process supplier:To acquirer/operator/user: requests SCM Processsupplies software product receives result of SCM activities and tasks r