1、raising standards worldwide NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BSI Standards Publication BS ISO/IEC 26512:2011 Systems and software engineering Requirements for acquirers and suppliers of user documentationBS ISO/IEC 26512:2011 BRITISH STANDARD National foreword T
2、his British Standard is the UK implementation of ISO/IEC 26512:2011. It supersedes BS ISO/IEC 15910:1999, which is withdrawn. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee c
3、an be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. BSI 2011 ISBN 978 0 580 68059 5 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obli
4、gations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 July 2011. Amendments issued since publication Date Text affectedBS ISO/IEC 26512:2011 Reference number ISO/IEC/IEEE 26512:2011(E) ISO/IEC 2011 IEEE 2011 INTERNATIONAL STANDARD ISO/I
5、EC/ IEEE 26512 First edition 2011-06-01 Systems and software engineering Requirements for acquirers and suppliers of user documentation Ingnierie du logiciel et des systmes Exigences pour acqureurs et fournisseurs de documentation utilisateur BS ISO/IEC 26512:2011 ISO/IEC/IEEE 26512:2011(E) PDF disc
6、laimer 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 computer performing the editing. In downloading this file, parties
7、accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat, the IEC Central Office and IEEE do not accept any liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be
8、 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 and IEEE members. In the unlikely event that a problem relating to it is found, please inform the ISO C
9、entral Secretariat or IEEE at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2011 IEEE 2011 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 micr
10、ofilm, without permission in writing from ISO, IEC or IEEE at the respective address below. ISO copyright office IEC Central Office Institute of Electrical and Electronics Engineers, Inc. Case postale 56 3, rue de Varemb 3 Park Avenue, New York CH-1211 Geneva 20 CH-1211 Geneva 20 NY 10016-5997, USA
11、Tel. + 41 22 749 01 11 Switzerland E-mail stds.iprieee.org Fax + 41 22 749 09 47 E-mail inmailiec.ch Web www.ieee.org E-mail copyrightiso.org Web www.iec.ch Web www.iso.org Published in Switzerland ii ISO/IEC 2011 All rights reserved IEEE 2011 All rights reservedBS ISO/IEC 26512:2011 ISO/IEC/IEEE 26
12、512:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved iiiContents Page Foreword .v Introductionvi 1 Scope1 2 Conformance .2 2.1 Definition of conformance2 2.2 Conformance situations .3 3 Normative references3 4 Terms and definitions .3 5 User documentation within a system/softwa
13、re life cycle8 5.1 Software documentation management process 8 5.2 Information management process.9 6 User documentation agreement processes within a system/software life cycle .10 6.1 User documentation acquisition process.10 6.1.1 Purpose of the acquisition process 10 6.1.2 Outcomes of the acquisi
14、tion process .11 6.2 User documentation acquisition activities and tasks .11 6.2.1 Acquisition preparation 11 6.2.2 Supplier selection13 6.2.3 Contract agreement.13 6.2.4 Contract management and monitoring .13 6.2.5 Acquirer acceptance .14 6.2.6 Acquisition closure .14 6.3 User documentation supply
15、process 14 6.3.1 Purpose of the supply process14 6.3.2 Outcomes of the supply process.14 6.4 User documentation supply activities and tasks.14 6.4.1 Opportunity identification and evaluation 15 6.4.2 Proposal preparation 15 6.4.3 Contract agreement.15 6.4.4 Contract execution 15 6.4.5 Product/servic
16、e delivery and support.17 6.4.6 Closure .17 7 Defining user documentation requirements and constraints.18 7.1 Aspects of requirements and constraints 18 7.2 Schedule constraints 18 7.3 Usability requirements19 7.4 Product modification requirements.19 7.5 Localization and translation requirements.20
17、7.6 Legal requirements .20 7.7 Security requirements.21 7.8 Standards and conventions .21 7.9 Quality management requirements .21 8 User Documentation Specification21 9 User documentation Statement of Work.22 10 Request for Proposal 23 10.1 Request for Proposal topics 23 10.2 Project objectives23 BS
18、 ISO/IEC 26512:2011 ISO/IEC/IEEE 26512:2011(E) iv ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved10.3 Requirements for supporting processes 24 10.4 Supplier capabilities and experience.24 10.5 Instructions for bidders 24 10.6 List of deliverable user documentation products or services
19、 24 10.7 Terms and conditions .25 10.8 Proposal evaluation criteria25 11 Documentation proposal 25 11.1 Documentation proposal contents 25 11.2 Understanding of requirements .26 11.3 Scope of the project 26 11.4 Processes .27 11.5 Experience, capabilities, and available resources.27 11.6 Schedule .2
20、8 11.7 Deliverables28 11.8 Price proposal28 Annex A (informative) Requirements clauses and checklist for acquirers.29 Annex B (informative) Requirements clauses and checklist for suppliers.34 Bibliography 37 BS ISO/IEC 26512:2011 ISO/IEC/IEEE 26512:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011
21、All rights reserved vForeword 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 Sta
22、ndards through 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 a
23、nd 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. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA)
24、Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the I
25、nstitute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its standards. International S
26、tandards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an Inte
27、rnational Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is called to the possibility that implementation of this standard may require the use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect
28、to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or scope of patents or patent claims or determining whether
29、any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the
30、validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards Association. ISO/IEC/IEEE 26512:2011 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, S
31、ubcommittee SC 7, Software and systems engineering, in cooperation with the Software and Systems Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE. This first edition of ISO/IEC/IEEE 26512 can
32、cels and replaces ISO/IEC 15910:1999, which has been technically revised. BS ISO/IEC 26512:2011 ISO/IEC/IEEE 26512:2011(E) vi ISO/IEC 2011 All rights reserved IEEE 2011 All rights reservedIntroduction This International Standard was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-200
33、8) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation and documentation services as part of the software life cycle processes. It defines the documentation process from the acquirers standpoint and the suppliers standpoint. The accurate description of the re
34、quirements for user documentation is essential in order to ensure that the documentation meets the needs of its users. This International Standard addresses the identification, definition, and fulfillment of user documentation requirements as part of the acquisition and supply processes. This Intern
35、ational Standard covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the Proposal. It also discusses the use of a Documentation Management Plan and a Document
36、 Plan as they arise in the acquisition and supply processes. This International Standard is independent of the software tools that can be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for
37、 systems including hardware as well as software. Earlier standards tended to view the results of the documentation process as a single book or multi-volume set: a one-time deliverable. Increasingly, documentation acquirers and suppliers recognize that most user documentation is now produced from man
38、aged re-use of previously developed information (single-source documentation) adapted for new software versions, or presentation in various on-screen and printed media. While this International Standard does not describe how to set up a content management system, it is applicable for documentation o
39、rganizations practising single-source documentation, as well as for acquirers and suppliers of one-time deliverables. Anyone who uses application software needs accurate information about how the software will help the user accomplish a task. The documentation can be the first tangible item that the
40、 user sees, and so influences the users first impressions of the software product. If the information is supplied in a convenient form and is easy to find and understand, the user can quickly become proficient at using the product. Therefore, well-designed documentation not only assists the user and
41、 helps to reduce the cost of training and support, but also enhances the reputation of the product, its producer, and its suppliers. Although software developers intend to design user interfaces that behave so intuitively that very little separate documentation is needed, this is rarely possible. To
42、days software offers increasingly robust functionality, not only within applications, but also across applications which intelligently exchange information with one another. Further, most software includes underlying rules and calculations, or algorithms that affect the results a user can obtain whe
43、n using the software. These underlying programming mechanics are discernable by users, but only through laborious testing. For these and other reasons, user documentation remains an essential component of usable software products. Documentation is often regarded as something done after the software
44、has been implemented. However, for high-quality software documentation, its development needs to be regarded as an integral part of the software life cycle. In fact, quality documentation or information management services are important enough to require specific planning. Related standards for thos
45、e acquiring and supplying software user documentation include ISO/IEC 26514:2008 (IEEE Std 26514-2010), Systems and software engineering Requirements for designers and developers of user documentation, and ISO/IEC 26513:2009 (IEEE Std 26513-2010), Systems and software engineering Requirements for te
46、sters and reviewers of user documentation. Other International Standards are in preparation or planned to address the documentation and information management processes from the viewpoint of managers and agile projects. BS ISO/IEC 26512:2011 ISO/IEC/IEEE 26512:2011(E) ISO/IEC 2011 All rights reserve
47、d IEEE 2011 All rights reserved viiThis International Standard is consistent with ISO/IEC 12207:2008 (IEEE Std 12207-2008) as an implementation of the Acquisition and Supply processes, which comprise the Agreement processes, and of the Information Management and Software Documentation Management Pro
48、cesses. This International Standard is intended for use in all types of organizations, whether they have a dedicated documentation department or not. It can be used as a basis for local standards and procedures. Readers are assumed to have experience or knowledge of general agreement processes for a
49、cquisition and supply of products and services. The order of clauses in this International Standard does not imply that the acquisition activities need to be performed in this order, nor that documentation needs to be developed in this order or presented to the user in this order. In each clause, the requirements are media-independent, as far as possible. The checklists in Annexes A and B can be used to track conformance with the requirements of this International Standard for acquirers and suppliers of doc
