BS ISO IEC IEEE 26531-2015 Systems and software engineering Content management for product lifecycle user and service management documentatio《系统和软件工程 产品寿命周期 用户和服务管理文档的内容管理》.pdf

1、BSI Standards PublicationBS ISO/IEC/IEEE 26531:2015Systems and softwareengineering Contentmanagement for productlife-cycle, user and servicemanagement documentationBS ISO/IEC/IEEE 26531:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO/IEC/IEEE26531:2015.The

2、 UK participation in its preparation was entrusted to TechnicalCommittee IST/15, Software and systems engineering.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions of a contract. U

3、sers are responsible for its correctapplication. The British Standards Institution 2015. Published by BSI StandardsLimited 2015ISBN 978 0 580 83363 2ICS 35.080Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of th

4、eStandards Policy and Strategy Committee on 30 June 2015.Amendments issued since publicationDate Text affectedBS ISO/IEC/IEEE 26531:2015Reference numberISO/IEC/IEEE 26531:2015(E)ISO/IEC 2015IEEE 2015INTERNATIONAL STANDARDISO/IEC/IEEE26531First edition2015-05-15Systems and software engineering Conten

5、t management for product life-cycle, user and service management documentation Ingnierie des systmes et du logiciel Gestion de contenu relatif a la documentation du cycle de vie du produit, de lutilisateur, et de la gestion de service BS ISO/IEC/IEEE 26531:2015ISO/IEC/IEEE 26531:2015(E) PDF disclaim

6、er 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 acce

7、pt 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 fou

8、nd 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 Centr

9、al Secretariat or IEEE at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2015 IEEE 2015 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 microfil

10、m, 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 Tel.

11、 + 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 2015 All rights reserved IEEE 2015 All rights reservedBS ISO/IEC/IEEE 26531:2015ISO/IEC/IEEE 26

12、531:2015(E) ISO/IEC 2015 All rights reserved IEEE 2015 All rights reserved iiiContents Page1 Scope 1 2 Conformance . 2 3 Normative references 2 4 Terms and definitions . 2 5 Abbreviated terms . 5 6 Content management process . 6 7 Content management project initiation . 8 7.1 Developing a business c

13、ase 8 7.2 Defining requirements for a CCMS 9 7.2.1 Requirements definition . 9 7.2.2 Output requirements . 9 7.2.3 Storage and retrieval requirements . 10 7.2.4 Assembly and linking requirements 10 7.2.5 Authoring and workflow requirements . 10 8 Content management project plan 11 8.1 Implementation

14、 plan 11 8.2 Information model . 11 8.3 Information model specification 12 8.4 Authoring guidelines . 13 8.4.1 Training authors 13 8.4.2 Code reviews . 13 8.5 Reuse strategy . 14 8.5.1 Content inclusion 14 8.5.2 Content variables 14 8.5.3 Content conditional processing 14 8.6 Metadata schema . 15 8.

15、6.1 Administrative metadata . 16 8.6.2 Descriptive metadata 16 8.6.3 Processing metadata 16 8.7 Workflow specification . 17 8.7.1 Workflow approvals 17 8.7.2 Translation workflow . 18 8.7.3 Workflow completion 18 8.8 Schedule of activities, deliverables, and responsibilities . 18 8.9 Training plan 1

16、8 8.10 Stylesheet development . 18 8.11 Pilot project specification . 19 8.12 Organizational rollout . 19 9 Information development 19 9.1 Content conversion . 19 9.2 Content authoring . 20 9.2.1 Structured authoring . 20 9.2.2 Unstructured authoring 20 9.2.3 Content granularity . 21 10 Management a

17、nd control 21 10.1 Managing quality . 21 10.2 Review and approval of content 22 10.3 Search and retrieval 23 BS ISO/IEC/IEEE 26531:2015ISO/IEC/IEEE 26531:2015(E) iv ISO/IEC 2015 All rights reserved IEEE 2015 All rights reserved10.4 Localization and translation .23 10.4.1 Content management for trans

18、lation .24 10.4.2 Publication of translated content .24 10.4.3 Translation of vector graphics .24 10.5 Content deletion .24 10.6 Content and component archiving 25 11 Publication 25 11.1 Release management 25 11.2 Version management 26 11.3 Publication of content .26 12 Component Content Management

19、System requirements .27 12.1 General 27 12.2 Component Content Management System framework 28 12.2.1 General storage requirements 28 12.2.2 Content types .28 12.2.3 Metadata structures .28 12.2.4 Organizational structures .29 12.3 Component Content Management System management 29 12.3.1 Component cr

20、eation and modification 30 12.3.2 Import/export 30 12.4 Content object management 31 12.4.1 Check-out/check-in 31 12.4.2 Bulk check-out/check-in .31 12.4.3 Link management 31 12.4.4 Search .32 12.4.5 Advanced search capabilities 34 12.4.6 Versioning 35 12.4.7 Branch and merge .35 12.4.8 Release mana

21、gement 36 12.5 Graphics and multimedia management 36 12.6 Component Content Management System administration .37 12.6.1 Component Content Management System user administration .37 12.6.2 Security and auditing 37 12.6.3 Security provisions37 12.7 Content authoring 38 12.7.1 General authoring 39 12.7.

22、2 Native authoring .39 12.7.3 Authoring integration 39 12.7.4 Acquisition .40 12.8 Workflow .40 12.8.1 Workflow functionality 40 12.8.2 Enhanced workflow functionality .41 12.8.3 Workflow reporting 41 12.9 Content publication .42 12.9.1 Export to publishing support .42 12.9.2 Centralized publishing

23、support 42 12.9.3 Publishing interface 42 12.9.4 XML publishing pipeline .43 12.10 Localization and translation management 43 12.10.1 Link management support 43 12.10.2 XLIFF support .43 12.11 Component Content Management System interoperability 44 12.11.1 Application Programming Interface .44 12.11

24、.2 Libraries and frameworks .44 12.11.3 Web services 44 12.11.4 Advanced Application Programming Interface methods 44 Annex A (Informative) Business case considerations for content management .46 Bibliography 48 BS ISO/IEC/IEEE 26531:2015ISO/IEC/IEEE 26531:2015(E) ISO/IEC 2015 All rights reserved IE

25、EE 2015 All rights reserved vList of Illustrations Figure 1 Content Management process and activities 7 Table 1 Content data types in a CCMS information model . 12 Table 2 Templates for CCMS metadata . 12 BS ISO/IEC/IEEE 26531:2015ISO/IEC/IEEE 26531:2015(E) vi ISO/IEC 2015 All rights reserved IEEE 2

26、015 All rights 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 S

27、tandards 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

28、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. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA)

29、 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

30、Institute 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

31、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 to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an Int

32、ernational 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

33、 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

34、 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

35、 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 26531 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information Technology, Subco

36、mmittee SC 7, Systems and Software Engineering in cooperation with the Systems and Software Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE. BS ISO/IEC/IEEE 26531:2015ISO/IEC/IEEE 26531:2015

37、(E) ISO/IEC 2015 All rights reserved IEEE 2015 All rights reserved viiIntroduction This International Standard was developed to assist users of ISO/IEC/IEEE 15288:2008, Systems and software engineering System life cycle processes, ISO/IEC/IEEE 12207:2008, Systems and software engineering Software li

38、fe cycle processes, or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology Service management Part 1: Service management system requirements, in the management of the content used in product life-cycle, user, and service management documentation. The accurate description of the requ

39、irements for content management helps documentation meet the needs of its users and be efficiently produced. This International Standard is independent of the software tools that may be used to manage documentation content and applies to both printed documentation and on-screen documentation. Conten

40、t management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple de

41、liverable formats. A consequence of content management is increased collaboration on content development across the enterprise. Technical authors, instructional designers, support staff, and others may develop a body of content together that is written once and supports many needs. Documentation is

42、often regarded as something done after the software has been implemented. However, for high-quality software documentation, its development should be regarded as an integral part of the software life cycle. In fact, quality documentation or information management services are important enough to req

43、uire specific planning. This International Standard is consistent with ISO/IEC/IEEE 15288, System and Software Engineering System life cycle processes, and ISO/IEC/IEEE 12207, Systems and software engineering Software life cycle processes, as an implementation of the Information Management Process.

44、This standard is not a management system standard. This International Standard is intended for use in all types of organizations, whether they have a dedicated documentation department or not. It may be used as a basis for local standards and procedures. Readers are assumed to have experience or kno

45、wledge of general processes for information management, project management, and document development. This International Standard is intended for managing technical content which is included in: User information such as topic collections, manuals, guides, multimedia, user assistance displayed with s

46、oftware, style guides, and other content that supports the effective use of a system or software product. Product life cycle information such as design documents, use cases, personas, project management plans, feature requests, and testing plans. Service management items such as service level agreem

47、ents, records, policies, procedures, and other documents. The order of clauses in this International Standard does not imply that the content management activities should be performed in this order, nor that documentation should be developed in this order or presented to the organization in this ord

48、er. In each clause, the requirements are independent of media and document creation and management specifications. BS ISO/IEC/IEEE 26531:2015BS ISO/IEC/IEEE 26531:2015ISO/IEC/IEEE 26531:2015(E) ISO/IEC 2015 All rights reserved IEEE 2015 All rights reserved 1Systems and software engineering Content m

49、anagement for product life-cycle, user and service management documentation 1 Scope This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software