26531 reilly


Published on

New content management standard

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

26531 reilly

  1. 1. 1New International Standard forContent ManagementAnnette ReillySTC Standards CouncilMay 7, 2013
  2. 2. What will we be talking about? How are standards developed? What standards are relevant to technical communicators What in content management should be standardized? What’s in the draft ISO standard for Content Management—draft 26531 Aimed at acquirers, users, and producers Aimed at documentation of systems, software, andservices Content management systems use systems engineeringand systems/services managementMay 2013 2Annette Reilly
  3. 3. Why have standards? Support interoperability Further world trade Promote consistent products Allow repeatable processes and process improvement Basis for contracts and audits Obtain ISO/IEEE standards at www.iso.org orwww.ansi.org orhttp://www.techstreet.com/ieee OASIS standards at https://www.oasis-open.org/standardsMay 2013 3Annette Reilly
  4. 4. What is a technical standard? ―… [A] formal document that establishes uniform engineeringor technical criteria, methods, processes and practices‖(Wikipedia) Issued by a respected, authoritative entity IEEE – Computer Society and Standards Association Membership based International Standards Organization (ISO) Nation-based, Software and Systems Engineering documentationstandards from JTC 1/SC7 National standards organizations American National Standards Organization (ANSI) Other national organizations (BSI, Standards Bureau of Canada,etc.) National Information Standards Organization (NISO) Carnegie Mellon University Software Engineering Institute (SEI) Project Management Institute (Guidance) W3C (web standards) OASIS--DITAMay 2013 4Annette Reilly
  5. 5. When is it really a standard? Covers a process or product Not proprietary, tool-bound, or vendor-specific Open participation from all interestedstakeholders The result of consensus agreement froma balance of stakeholders Maintained by a recognized, impartialstandards-producing organization Normative (mandatory) or guidance?May 2013 5Annette Reilly
  6. 6. How do standards getdeveloped? Project proposal and approval Development and review of drafts bya working group or fast-track Ballot by interested parties Revise and reballot 24-36 months start to publish Publish, maintain, sell Periodic reviews – update, withdraw,stabilizeMay 2013 6Annette Reilly
  7. 7. ISO/IEC/IEEE suite of standards forsoftware, systems, services documentation 26511: Requirements for managers of user documentation 26512: Requirements for acquirers and suppliers of userdocumentation 26513: Requirements for testers and assessors of userdocumentation 26514: Requirements for designers and developers of userdocumentation 26515: Developing user documentation in an agileenvironment 15289: Content of life-cycle documentation (informationitems) Developed by STC members working with other technicalcommunicatorsMay 2013 7Annette Reilly
  8. 8. Where does the workingdraft come from? Existing organizational, national, or internationalstandards Book and article descriptions of best practices STC Summit presentations Working group discussions about best practices For content management – draft by STC members JoAnn Hackos, STC Fellowhttp://comtech-serv.com//index.php?main_page=contact_us Casey Jordanhttp://easydita.com Ralph Robinson, STC Fellow ralphrobinson1@hotmail.comMay 2013 8Annette Reilly
  9. 9. What’s in this new Content Managementstandard 26531 Requirements and recommended practices for Developing a content management strategy Checklist for organizations – business case Developing a workflow for content management Content management system functionsMay 2013Annette Reilly9 Not-- How to use DITA Which CM system to buyPublication late 2014
  10. 10. Business Case for content management Current state of documentation Customer benefits Consistent, easy to find information Reduction in support calls through self-service information Finding same information through multiple devices and media Cost reduction opportunities Acquisition and implementation costs Return on investment RisksMay 2013Annette Reilly10
  11. 11. Content Management Processes Business Case Development Requirements Definition Content ManagementPlanning – process andproject Information Model Definition Authoring Guidelines Content Reuse Strategy Workflow Specification Quality Management Content Review and ApprovalMay 2013Annette Reilly11 Metadata Model Content Search Content Conversion Content Authoring Graphics and MultimediaManagement Content Localization Release Management Content Publication Content Deletion Content Archiving
  12. 12. Workflow for the content life-cycle Project initiation – content conversion or authoring Content editing and proofreading Content technical review Content testing Content approval Content translation Content publication Content sustainment and reuse Content archiving after initial and subsequent releasesMay 2013Annette Reilly12
  13. 13. What’s in the information model forstructured authoring Document type definitions (outlines, templates) Definitions of the information types procedure, process, policy Structure of the information type (content units and theirsequence) Definitions of content units paragraphs, lists, tables, illustrations, examples, warnings Collections of content objects chapters, parts, sections, books Content object metadata author, date, subject, version Reuse mechanisms File naming conventions for text and graphicsMay 2013Annette Reilly13
  14. 14. Content Management system requirements Repository management Content object and asset management Check-out, check-in, link management, search, versioning Graphics and multimedia management System administration Authoring functions Workflow functions Content publication Localization and translation management System interoperabilityMay 2013Annette Reilly14
  15. 15. ISOspeak ISO/IEC: International Organization forStandardization/International ElectrotechnicalCommission JTC1/SC7: Joint Technical Committee 1,subcommittee 7, responsible for software andsystems engineering standards WG2: Working group 2, responsible for systemsand user documentation http://isotc.iso.org/livelink/livelink?func=ll&objId=8914719May 2013 15Annette Reilly
  16. 16. What is unique aboutISO/IEC standards? Represent the efforts of experts from aminimum of 5 countries Iteratively drafted and balloted, with alltechnical comments resolved Published by ISO and widely adopted aroundthe world The vast majority of WG members are volunteers.May 2013 16Annette Reilly
  17. 17. Getting involved with standards Adopt a single-sourcing approach Have models for your process andproducts Use standards at work Support a capability assessment Become a standards reviewer or editor Join IEEE-Standards Association, OASIS,W3C, PMIMay 2013 17Annette Reilly
  18. 18. Your turn Questions? Comments? Experience with content managementor other standards? Obtain ISO/IEEE standards at www.iso.org orwww.ansi.org or http://www.techstreet.com/ieee OASIS standards athttps://www.oasis-open.org/standardsContact annette.reilly at computer.orgMay 2013 18Annette Reilly