Revision Standard – Active. This document provides requirements for the management of the content used in product life cycle, software, and service management system information for users. Content 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 multiple deliverable formats and the reuse of content objects among deliverables. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This document defines the characteristics of an effective and efficient process through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or other content published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this document can fulfil business needs for content development and management, especially the need for a single source of authoritative information. This document includes business case considerations for acquisition of a content management system. This document is independent of the software tools and markup languages that may be used to manage information for users and applies to both printed and on-screen information for users.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 1<\/td>\n | Front Cover <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 1 Scope 2 Normative references 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 4 Conformance 5 Component content management system development and implementation <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 6 Content management project initiation 6.1 Developing a business case <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 6.2 Defining requirements for a CCMS 6.2.1 Requirements definition 6.2.2 Output requirements 6.2.3 Storage and retrieval requirements <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6.2.4 Assembly and linking requirements <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 6.2.5 Writing, reviewing and workflow requirements <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 7 Project planning for CCMS implementation 7.1 Implementation plan 7.2 Information model <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 7.3 Information model specification <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 7.4 Writing guidelines <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 7.5 Automation-assisted reviews 7.6 Reuse strategy 7.6.1 Content conditional processing 7.6.2 Content inclusion <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 7.6.3 Content variables 7.7 Metadata schema 7.7.1 General <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.7.2 Administrative metadata <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 7.7.3 Descriptive metadata 7.7.4 Processing metadata 7.8 Workflow 7.8.1 Workflow specification 7.8.2 Workflow approvals <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 7.8.3 Translation workflow <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 7.8.4 Workflow completion 7.9 Schedule of activities, deliverables, and responsibilities 7.10 Training plan 7.11 Style sheet development 7.12 Pilot project specification <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 7.13 Organizational rollout 8 Content development 8.1 Content creation 8.1.1 General 8.1.2 Structured writing 8.1.3 Unstructured writing <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 8.1.4 Content granularity 8.2 Content conversion 8.2.1 General <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 8.2.2 Microcontent 9 Management and control 9.1 Managing quality <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 9.2 Review of content <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 9.3 Approval of content 9.4 Search and retrieval 9.5 Localization and translation 9.5.1 Translation management <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 9.5.2 Content management for translation 9.5.3 Publication of translated content 9.5.4 Publication of multilingual content 9.5.5 Translation of vector graphics <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 9.6 Content deletion 9.7 Content and component archiving <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 10 Publication 10.1 Release management 10.2 Version management <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 10.3 Publication of content <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 11 Component content management system requirements 11.1 General 11.2 Component content management system framework 11.2.1 General storage requirements <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 11.2.2 Content types 11.2.3 Metadata structures 11.2.4 Administrative metadata 11.2.5 Descriptive metadata <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 11.2.6 Classification 11.2.7 Additional metadata requirements 11.2.8 Organizational structures 11.3 Component content management system management 11.3.1 Component creation and modification <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 11.3.2 Import\/export 11.3.3 Bulk export 11.3.4 Dependency export <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 11.3.5 Archiving 11.4 Content object check-out and check in 11.4.1 General 11.4.2 Bulk check-out\/check-in 11.4.3 Check-out and check-in after restart 11.5 Link management <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 11.6 Search 11.6.1 General 11.6.2 Full text search <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 11.6.3 Metadata search 11.6.4 Structured search 11.6.5 Advanced search capabilities <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | 11.7 Versioning 11.7.1 General 11.7.2 Branch and merge <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 11.7.3 Release management 11.8 Graphics and multimedia management <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 11.9 Component content management system administration 11.9.1 User administration 11.9.2 Security <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 11.10 Content creation and acquisition 11.10.1 Writing interface 11.10.2 Content and metadata functions <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 11.10.3 Scientific notation and vector graphics 11.10.4 Writing integration 11.10.5 Acquisition <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 11.11 Workflow 11.11.1 Workflow creation 11.11.2 Workflow specification <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 11.11.3 Workflow reporting <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 11.12 Content publication 11.12.1 General 11.12.2 Export to publishing support 11.12.3 Centralized publishing support 11.12.4 Publishing interface <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | 11.12.5 XML publishing pipeline 11.12.6 Dynamic publishing 11.13 Localization and translation management 11.13.1 General <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 11.13.2 XLIFF support 11.14 Component content management system interoperability 11.14.1 General 11.14.2 Libraries and frameworks 11.14.3 Web services <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | 11.14.4 Application Programming Interface methods <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | 11.14.5 Webhooks and triggers <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | Annex\u00a0A (informative) Business case considerations for content management <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | Bibliography <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | IEEE notices and abstract <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | This document provides requirements for the management of the content used in product life cycle,software, and service management system information for users. Content management allows anorganization to control the storage and retrieval of content objects, track content revisions, maintaina content audit trail, and enable a collaborative environment. Component content managementsupports multiple deliverable formats and the reuse of content objects among deliverables. Contentobjects that are unique and are maintained as independent database objects are efficient to review,approve, and update; may be combined to produce multiple deliverables; and are cost-effective totranslate. This document defines the characteristics of an effective and efficient process throughwhich content is gathered, managed, and published, including the requirements of a system thatis supported by an electronic database. Such a database should support documents or topics andcontent units that may be assembled to produce complete documents for print, electronic output, orother content published through electronic media. This database is defined as a component contentmanagement system (CCMS), as distinct from a document management system. The objective ofcomponent content management is to create content objects once and use them through linkingmechanisms in multiple output formats including but not limited to documents. Systems conformingto this document can fulfil business needs for content development and management, especiallythe need for a single source of authoritative information. This document includes business caseconsiderations for acquisition of a content management system. This document is independent of thesoftware tools and markup languages that may be used to manage information for users and appliesto both printed and on-screen information for users. Back Cover <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" ISO\/IEC\/IEEE International Standard – Systems and software engineering–Content management for product life cycle, user and service management information for users (Redline)<\/b><\/p>\n |