《ISO-15289-2006.pdf》由会员分享，可在线阅读，更多相关《ISO-15289-2006.pdf（60页珍藏版）》请在三一文库上搜索。
1、 Reference number ISO/IEC 15289:2006(E) ISO/IEC 2006 INTERNATIONAL STANDARD ISO/IEC 15289 First edition 2006-04-15 Systems and software engineering Content of systems and software life cycle process information products (Documentation) Ingnierie des systmes et du logiciel Contenu des systmes et prod
2、uits dinformation du processus de cycle de vie du logiciel (documentation) Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/05/2007 05:22:34 MDTNo reproduction or networking permitt
3、ed without license from IHS -,-,- ISO/IEC 15289:2006(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 installed on the com
4、puter 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 products used to cre
5、ate 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, please inform th
6、e Central Secretariat at the address given below. ISO/IEC 2006 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 microfilm, without permission in writing from ei
7、ther 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/IEC 2006 All rights reserved Copyright Intern
8、ational Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/05/2007 05:22:34 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 15289:2006(E) ISO/IEC 2006 All rights reserved ii
9、i Contents Page Foreword. vii Introduction. viii 1 Scope . 1 2 Applicability. 3 3 Conformance. 3 3.1 Definition of Conformance. 3 3.2 Conformance Situations 4 3.3 Type of Conformance. 4 4 Normative references. 5 5 Terms and definitions. 5 6 Life cycle data and information items 6 6.1 Life cycle data
10、 characteristics. 6 6.2 Records compared to other information items (documents). 6 6.3 Management of life cycle data (records) 7 6.4 Management of information items (documents) . 7 6.4.1 Developing the documentation plan. 7 6.4.2 Managing and controlling information items. 7 7 Generic information ty
11、pes and information items 8 7.1 Overview 8 7.2 Record generic content guidelines 8 7.3 Description generic content guidelines 9 7.4 Plan generic content guidelines. 10 7.5 Procedure generic content guidelines 11 7.6 Report generic content guidelines. 12 7.7 Request generic content guidelines 13 7.8
12、Specification generic content guideline 14 8 Mapping of information items to the life cycle 14 8.1 Mapping of information items to the system life cycle. 15 8.2 Mapping of information items to the software life cycle 20 9 Records 27 9.1 General. 27 9.2 Specific record contents 27 10 Specific informa
13、tion item (document) contents 28 10.1 Acceptance plan . 28 10.2 Acceptance procedure. 29 10.3 Acceptance review and testing report 29 10.4 Acquisition plan 29 10.5 Acquisition report. 29 10.6 Asset management plan 29 10.7 Audit acknowledgement report. 30 10.8 Audit report . 30 10.9 Change request. 3
14、0 10.10 Configuration management plan. 30 10.11 Configuration management procedures 31 10.12 Configuration status report . 31 10.13 Contract . 31 10.14 Database design description. 31 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employe
15、es/1111111001, User=Wing, Bernie Not for Resale, 04/05/2007 05:22:34 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 15289:2006(E) iv ISO/IEC 2006 All rights reserved 10.15 Database detailed design description 32 10.16 Database test procedure32 10.17 Database test r
16、eport .32 10.18 Development plan .32 10.19 Documentation plan33 10.20 Domain engineering plan.33 10.21 Evaluation report.33 10.22 High-level software design description33 10.23 Infrastructure plan 34 10.24 Installation plan.34 10.25 Installation report34 10.26 Integration and test report .34 10.27 I
17、nterface Description 35 10.28 Joint review minutes.35 10.29 Low-level software design description.35 10.30 Maintenance plan35 10.31 Maintenance problem/ modification report36 10.32 Maintenance procedures36 10.33 Migration plan36 10.34 Modification notification report.36 10.35 Modification requiremen
18、t report37 10.36 Modification test report 37 10.37 Monitoring and control report37 10.38 Operational test procedures37 10.39 Operations plan.37 10.40 Organizational procedures.38 10.41 Problem report.38 10.42 Problem resolution procedure.38 10.43 Process assessment procedure39 10.44 Process improvem
19、ent analysis report39 10.45 Product need assessment39 10.46 Production plan.39 10.47 Progress report .40 10.48 Project management plan 40 10.49 Proposal.40 10.50 Qualification test procedure 41 10.51 Qualification test report41 10.52 Quality assurance plan.41 10.53 Quality management procedures41 10
20、.54 Release record 42 10.55 Request for proposal (RFP) .42 10.56 Retirement notification report42 10.57 Retirement plan.42 10.58 Reuse plan.43 10.59 Risk management plan.43 10.60 Risk management procedures.43 10.61 Software integration test plan43 10.62 Software requirements specification44 10.63 So
21、ftware unit description.44 10.64 Software unit test plan44 10.65 Software unit test procedure .44 10.66 Software unit test report.44 10.67 Software user documentation45 10.68 Strategic plan.45 10.69 Supplier selection procedure.45 10.70 System architecture description .45 10.71 System description.46
22、 10.72 System element description 46 10.73 System life cycle description.46 10.74 System integration test procedure46 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/05/2007 05:22:
23、34 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 15289:2006(E) ISO/IEC 2006 All rights reserved v 10.75 System requirements specification 47 10.76 Training documentation. 47 10.77 Training plan . 47 10.78 User Documentation. 47 10.79 Validation plan 48 10.80 Valid
24、ation test specification 48 10.81 Validation report . 48 10.82 Verification plan 48 10.83 Verification report. 48 Annex A (informative) Procedure for identifying information items and their contents 50 Annex B (Informative) Bibliography. 51 Copyright International Organization for Standardization Pr
25、ovided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/05/2007 05:22:34 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 15289:2006(E) vi ISO/IEC 2006 All rights reserved List of Tables Table 1 Mapping of ISO/IEC
26、15288:2002, Clauses to Information Items for Each System Life Cycle Process.16 Table 2 Mapping of ISO/IEC 12207 Clauses to Information Items for Each Software Life Cycle Process21 Table 3 Record References and Contents27 Copyright International Organization for Standardization Provided by IHS under
27、license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/05/2007 05:22:34 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 15289:2006(E) ISO/IEC 2006 All rights reserved vii Foreword ISO (the International Organization for Standardizat
28、ion) 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 through technical committees established by the respective organization to
29、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 take part in the work. In the field of information technology, ISO and
30、 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 prepare International Standards. Draft International Standards adopted by t
31、he 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. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
32、rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 15289 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering. This International Standard is based on ISO/IEC 12207:1
33、995, with Amendments 1 and 2, ISO/IEC 15288:2002, and IEEE/EIA 12207.1-1996, Industry implementation of ISO/IEC 12207:1995. The IEEE Computer Society participated as a liaison organization in the development of this International Standard. Copyright International Organization for Standardization Pro
34、vided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/05/2007 05:22:34 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 15289:2006(E) viii ISO/IEC 2006 All rights reserved Introduction This International Standard
35、was developed to assist users of ISO/IEC 15288:2002 or ISO/IEC 12207:1995/AMD 1:2002/AMD 2, to manage information items as products of the system or software life cycle processes. In many cases, ISO/IEC 12207:1995 may state that the result of a process must be documented or may imply the need for a
36、document (or information item). ISO/IEC 12207:1995 clauses often do not specify the contents of documents. The indicated information items in ISO/IEC 12207:1995 aid in planning, producing, and evaluating the results of the life-cycle processes. Information items are essential to preserving what tran
37、spired when using system life cycle processes, and may be identified as deliverable documents. This International Standard may be used as a conformance or a guidance document for projects and organizations claiming conformance to ISO/IEC 15288:2002 and/or ISO/IEC 12207:1995 and amendments. This Inte
38、rnational Standards nomenclature for information items, document titles and contents is informative. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/05/2007 05:22:34 MDTNo reproduc
39、tion or networking permitted without license from IHS -,-,- INTERNATIONAL STANDARD ISO/IEC 15289:2006(E) ISO/IEC 2006 All rights reserved 1 Systems and software engineering Content of systems and software life cycle process information products (Documentation) 1 Scope This International Standard ass
40、umes an organization is implementing life cycle processes in conformance with ISO/IEC 15288:2002 or ISO/IEC 12207:1995, with Amendments 1 and 2. ISO/IEC 15288:2002 defines a set of processes for managing and performing the stages of a systems life cycle. It defines an Information Management process,
41、 but “does not detail documentation in terms of name, format, explicit content, and recording media” (1.3). ISO/IEC 12207:1995 with AMD 1 and 2, establishes a common framework for software life cycle processes, and in passing identifies or requires a number of documentation items. The purpose of thi
42、s International Standard is to guide users of ISO/IEC 12207:1995 (with Amendments 1 and 2) and ISO/IEC 15288:2002 in identifying and planning the specific information items to be produced during systems and software life cycles. As stated in G.5 of IEEE/EIA 12207.0:1996, This International Standard
43、identifies the purpose and content of all identified Systems and Software Life Cycle information items. The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). The generic document types (which may
44、 be referred to as information item types to conform to 3) are to be used to identify the information necessary to support the ISO/IEC 15288:2002 agreement, enterprise, project, and technical processes; and the ISO/IEC 12207:1995, primary, supporting, and organizational life cycle processes. This In
45、ternational Standard identifies records and information items based on analysis of references in ISO/IEC 15288:2002 and ISO/IEC 12207:1995, which in some cases provide partial or complete outlines for the content of specific documents. However, the requirements for the life-cycle processes do not un
46、iquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item. Moreover, the information from the life-cycle processes may overlap or may be created and revised at different times. In short, the analyzed references do no
47、t result in a logically complete list of information items. For example, for each life-cycle process, it would be possible to prepare a plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of a The use of the Documentation process
48、 should achieve the following objectives: a) Identify all documents to be produced by the process or project; b) Specify the content and purpose of all documents and plan and schedule their production; c) Identify the standards to be applied for development of documents; d) Develop and publish all documents in accordance with identified standards and in accordance with nominated plans; e) Maintain all documents in accordance with specified criteria. Copyright Internat