IEEE 26531-2023(Redline)

$69.33

ISO/IEC/IEEE International Standard – Systems and software engineering–Content management for product life cycle, user and service management information for users (Redline)

Published By	Publication Date	Number of Pages
IEEE	2023

Guaranteed Safe Checkout

Category: IEEE

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

Description

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.

PDF Catalog

PDF Pages	PDF Title
1	Front Cover
6	Foreword
8	Introduction
11	1 Scope 2 Normative references 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions
15	3.2 Abbreviated terms
16	4 Conformance 5 Component content management system development and implementation
17	6 Content management project initiation 6.1 Developing a business case
19	6.2 Defining requirements for a CCMS 6.2.1 Requirements definition 6.2.2 Output requirements 6.2.3 Storage and retrieval requirements
20	6.2.4 Assembly and linking requirements
21	6.2.5 Writing, reviewing and workflow requirements
22	7 Project planning for CCMS implementation 7.1 Implementation plan 7.2 Information model
23	7.3 Information model specification
24	7.4 Writing guidelines
25	7.5 Automation-assisted reviews 7.6 Reuse strategy 7.6.1 Content conditional processing 7.6.2 Content inclusion
26	7.6.3 Content variables 7.7 Metadata schema 7.7.1 General
27	7.7.2 Administrative metadata
28	7.7.3 Descriptive metadata 7.7.4 Processing metadata 7.8 Workflow 7.8.1 Workflow specification 7.8.2 Workflow approvals
29	7.8.3 Translation workflow
30	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
31	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
32	8.1.4 Content granularity 8.2 Content conversion 8.2.1 General
33	8.2.2 Microcontent 9 Management and control 9.1 Managing quality
34	9.2 Review of content
35	9.3 Approval of content 9.4 Search and retrieval 9.5 Localization and translation 9.5.1 Translation management
36	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
37	9.6 Content deletion 9.7 Content and component archiving
38	10 Publication 10.1 Release management 10.2 Version management
39	10.3 Publication of content
40	11 Component content management system requirements 11.1 General 11.2 Component content management system framework 11.2.1 General storage requirements
41	11.2.2 Content types 11.2.3 Metadata structures 11.2.4 Administrative metadata 11.2.5 Descriptive metadata
42	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
43	11.3.2 Import/export 11.3.3 Bulk export 11.3.4 Dependency export
44	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
45	11.6 Search 11.6.1 General 11.6.2 Full text search
47	11.6.3 Metadata search 11.6.4 Structured search 11.6.5 Advanced search capabilities
48	11.7 Versioning 11.7.1 General 11.7.2 Branch and merge
49	11.7.3 Release management 11.8 Graphics and multimedia management
50	11.9 Component content management system administration 11.9.1 User administration 11.9.2 Security
51	11.10 Content creation and acquisition 11.10.1 Writing interface 11.10.2 Content and metadata functions
52	11.10.3 Scientific notation and vector graphics 11.10.4 Writing integration 11.10.5 Acquisition
53	11.11 Workflow 11.11.1 Workflow creation 11.11.2 Workflow specification
54	11.11.3 Workflow reporting
55	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
56	11.12.5 XML publishing pipeline 11.12.6 Dynamic publishing 11.13 Localization and translation management 11.13.1 General
57	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
58	11.14.4 Application Programming Interface methods
59	11.14.5 Webhooks and triggers
60	Annex A (informative) Business case considerations for content management
62	Bibliography
64	IEEE notices and abstract
68	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

Additional information

Standard Title	ISO/IEC/IEEE International Standard – Systems and software engineering–Content management for product life cycle, user and service management information for users (Redline)
Published Code	IEEE
Publication Date	2023

Preview PDF


PDF Format	Searchable	Printable	Preview Now

IEEE 26531-2023(Redline)

PDF Catalog

Related products