IEEE 26515-2012 en Systems and software engineering - Developing user documentation in an agile environment (IEEE Computer Society)《系统和软件工程 在敏捷环境中开发用户文档(IEEE计算机.pdf

《IEEE 26515-2012 en Systems and software engineering - Developing user documentation in an agile environment (IEEE Computer Society)《系统和软件工程 在敏捷环境中开发用户文档(IEEE计算机.pdf》由会员分享，可在线阅读，更多相关《IEEE 26515-2012 en Systems and software engineering - Developing user documentation in an agile environment (IEEE Computer Society)《系统和软件工程 在敏捷环境中开发用户文档(IEEE计算机.pdf（36页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference numberISO/IEC/IEEE 26515:2012(E)ISO/IEC 2012IEEE 2012INTERNATIONAL STANDARD ISO/IEC/IEEE26515First edition2011-12-01Corrected version2012-03-15Systems and software engineering Developing user documentation in an agile environment Ingnierie du logiciel et des systmes Dveloppement de la doc

2、umentation de lutilisateur dans un environnement agile ISO/IEC/IEEE 26515:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 IEEE 2012 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, incl

3、uding photocopying and microfilm, 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 Ge

4、neva 20 NY 10016-5997, USA 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 2012 All rights reserved IEEE 2012 All rights reservedISO/IEC/IE

5、EE 26515:2012(E) ISO/IEC 2012 All rights reserved IEEE 2012 All rights reserved iiiContents Page Foreword iv Introduction . v 1 Scope 1 2 Conformance . 1 2.1 Application of conformance . 1 3 Normative references 2 4 Terms and definitions . 2 5 User documentation processes in an agile environment . 4

6、 5.1 Relationship between user and life cycle documentation processes . 4 5.2 Life cycle software documentation in an agile environment 5 5.3 Life cycle documentation in agile development 6 6 Management of information development in an agile environment 6 6.1 Documentation management considerations

7、for agile development 6 6.2 Change management when moving to an agile development process . 7 6.3 Composition of agile development teams 7 6.3.1 Communication in agile development teams . 8 6.3.2 Teams working in different locations 8 6.4 Management of information development across teams using agil

8、e development 9 6.5 Management of tasks across sprints 9 6.5.1 Planning the project as a whole . 9 6.5.2 Sizing and resourcing each sprint . 10 6.5.3 Handling last-minute documentation changes 11 6.6 Monitoring and analysing progress in an agile environment . 11 6.6.1 Status meetings . 11 6.6.2 Moni

9、toring progress 12 6.6.3 Rework and changing requirements . 13 6.7 Stakeholder involvement 13 6.8 Improving the user documentation process in an agile environment . 14 6.8.1 Assessing customer satisfaction 14 7 Developing user documentation in an agile environment 14 7.1 What agile development means

10、 for information development . 14 7.2 Product design and developing the user documentation . 15 7.3 Design and development of user documentation in an agile environment 16 7.3.1 Design techniques . 16 7.3.2 Information development tasks . 20 7.3.3 Planning of information units 20 7.4 Testing and rev

11、iewing documentation in an agile environment 20 7.4.1 Reviewing user documentation . 20 7.4.2 System test of documentation . 21 7.4.3 Usability testing of user documentation . 21 7.5 Translation and localisation of user documentation . 22 7.6 Production for manufacturing cycles 22 Annex A (informati

12、ve) Agile Development Practices 23 Annex B (informative) Example interview questions 25 Bibliography 27 ISO/IEC/IEEE 26515:2012(E) iv ISO/IEC 2012 All rights reserved IEEE 2012 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotech

13、nical 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 deal with particular fields of technical ac

14、tivity. 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 IEC have established a joint technical com

15、mittee, 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) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National St

16、andards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in t

17、he consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its standards. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is t

18、o prepare 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. Attention is called to the possib

19、ility 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 to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essenti

20、al 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 any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Li

21、censing 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 validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further info

22、rmation may be obtained from ISO or the IEEE Standards Association. ISO/IEC/IEEE 26515 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and Software Engineering Committee of the IEEE

23、Computer Society, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE. In this corrected version, the cover pages, front matter, page headers and footers have been corrected to reflect that ISO/IEC/IEEE 26515 is a joint development project under the Partne

24、r Standards Development Organization cooperation agreement between ISO and IEEE. ISO/IEC/IEEE 26515:2012(E) ISO/IEC 2012 All rights reserved IEEE 2012 All rights reserved vIntroduction Anyone who uses application software needs accurate information about how the software will help the users accompli

25、sh a task. The documentation may be the first tangible item that the user sees, and so influences the first impressions the users have of the product. If the information is supplied in a convenient form and is easy to find and understand, the users can quickly become proficient at using the product.

26、 Hence, well designed documentation not only assists the users and helps to reduce the cost of training and support, but also enhances the reputation of the product, its producer, and its suppliers. Projects that implement agile development focus on providing rapid and frequent deliveries of high va

27、lue software. These methods often involve detailed planning only for the short term, and the implementation of processes in parallel, rather than planning for an entire project in distinct phases. Although agile development methods often advocate less life cycle documentation, the users of a softwar

28、e product still expect and require quality user documentation to be provided with these software products. Although the end results of the user documentation process are the same, the methods to get there may be very different in an agile environment. Agile development methods may lead to the produc

29、tion of less user documentation, but the user documentation developed must be sufficient to meet the needs and requirements of the users. If the deliverables of user documentation and associated life cycle documentation are agreed in a contractual relationship between an acquirer and a supplier, the

30、n the deliverables that are produced are dictated by the terms of the contract. In these circumstances, the user and life cycle documentation deliverables that are agreed upon will depend on the demands of the acquiring organization regardless of the types of development methodologies used to produc

31、e them. Technical writers and other personnel involved in the production of user documentation should understand the agile development processes used by their organization, and use the most effective agile development methods to produce relevant and useful user documentation. Because of the nature o

32、f agile development methods, the traditional means of developing the end user documentation (both print and onscreen) as described in the current ISO/IEC 2651n family of International Standards are not entirely applicable. This International Standard was developed to assist users of ISO/IEC 15288:20

33、08 (IEEE Std 15288:2008), Systems and software engineering System life cycle processes, or ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering Software life cycle processes, and ISO/IEC 26514, Systems and software engineering Requirements for designers and developers of user d

34、ocumentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering Requirements for Designers and Developers of User Documentation) and others in the ISO/IEC 2651n family of International Standards. It provides requirements and gui

35、dance to technical writers and related roles on how to adapt the processes described in the ISO/IEC 2651n family of International Standards to develop quality user documentation. This International Standard is independent of the agile development methods and tools that are used to produce the softwa

36、re. This International Standard will conform to ISO/IEC 12207:2008 (IEEE Std 12207:2008) as an implementation of the user documentation part of 6.1: Documentation. The primary references for this International Standard are ISO/IEC 26514:2008 and ISO/IEC 26513:2009. INTERNATIONAL STANDARD ISO/IEC/IEE

37、E 26511:2012(E) ISO/IEC 2012 All rights reserved IEEE 2012 All rights reserved 1Systems and software engineering Developing user documentation in an agile environment 1 Scope This clause presents the scope, purpose, organization, and candidate uses of this International Standard. This International

38、Standard supports the interest of technical writers and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This International Standard takes a process standard approach to specify the way in which user documentation can be de

39、veloped in agile development projects. This International Standard provides requirements on information management and documentation processes appropriate for software projects that are using agile development methods. Clause 5 covers the overall requirements for documentation in the software life c

40、ycle. Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment. Clause 7 covers the relationship between the user documentation process and life cycle documentation process in agile development. Thi

41、s International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods. This International Standard provides guidance on processes appropriate for developers of user documentation in software and systems projects that are using agile

42、development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle. This International Standard is intended for use in all organizations that are using agile development, or are cons

43、idering implementing their projects using these techniques. It is assumed that users of this International Standard have experience or general knowledge of traditional user documentation processes. 2 Conformance This International Standard may be used as a conformance or a guidance document for proj

44、ects and organizations claiming conformance to ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering System life cycle processes and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering Software life cycle processes. 2.1 Application of conformance Throug

45、hout this International Standard, “shall” is used to express a provision that is binding, “should” to express a recommendation among other possibilities, and “may” to indicate a course of action permissible within the limits of this International Standard. ISO/IEC/IEEE 26515:2012(E) 2 ISO/IEC 2012 A

46、ll rights reserved IEEE 2012 All rights reservedUse of the nomenclature of this International Standard for the features of agile methodology or the parts of user documentation (that is, scrum, sprint, chapters, topics, pages, screens, windows, etc.) is not required to claim conformance. Conformance

47、to this International Standard may only be claimed by an organization if all of the requirements in this International Standard can be met by the organization. When conformance is claimed for a multi-supplier program, it may be the case that no individual supplier may claim conformance because no si

48、ngle contract calls for all the required activities. Nevertheless, the program, as a whole, may claim conformance if each of the required activities are performed by an identified party. This International Standard may be included or referenced in contracts or similar agreements when the parties (ca

49、lled the acquirer and the supplier) agree that the supplier shall deliver user documentation services in accordance with this International Standard. It may also be adopted as an in-house standard by a project or organization that decides to develop documentation in accordance with this International Standard. Organizations, projects, or multi-supplier programs intending to claim tailored conformance should consult ISO/IEC 12207/IEEE Std 12207:2008, Annex A, Tailoring Process. 3 Normative references The following ref