Already a subscriber? 
MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
Security check
Please login to your personal account to use this feature.
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
ISO/IEC/IEEE International Standard - Systems and software engineering--Content management for product life cycle, user and service management information for users (Redline), 2023
- Front Cover
- Foreword
- Introduction
- 1 Scope
- 2 Normative references
- 3 Terms, definitions and abbreviated terms [Go to Page]
- 3.1 Terms and definitions
- 3.2 Abbreviated terms
- 4 Conformance
- 5 Component content management system development and implementation
- 6 Content management project initiation [Go to Page]
- 6.1 Developing a business case
- 6.2 Defining requirements for a CCMS [Go to Page]
- 6.2.1 Requirements definition
- 6.2.2 Output requirements
- 6.2.3 Storage and retrieval requirements
- 6.2.4 Assembly and linking requirements
- 6.2.5 Writing, reviewing and workflow requirements
- 7 Project planning for CCMS implementation [Go to Page]
- 7.1 Implementation plan
- 7.2 Information model
- 7.3 Information model specification
- 7.4 Writing guidelines
- 7.5 Automation-assisted reviews
- 7.6 Reuse strategy [Go to Page]
- 7.6.1 Content conditional processing
- 7.6.2 Content inclusion
- 7.6.3 Content variables
- 7.7 Metadata schema [Go to Page]
- 7.7.1 General
- 7.7.2 Administrative metadata
- 7.7.3 Descriptive metadata
- 7.7.4 Processing metadata
- 7.8 Workflow [Go to Page]
- 7.8.1 Workflow specification
- 7.8.2 Workflow approvals
- 7.8.3 Translation workflow
- 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
- 7.13 Organizational rollout
- 8 Content development [Go to Page]
- 8.1 Content creation [Go to Page]
- 8.1.1 General
- 8.1.2 Structured writing
- 8.1.3 Unstructured writing
- 8.1.4 Content granularity
- 8.2 Content conversion [Go to Page]
- 8.2.1 General
- 8.2.2 Microcontent
- 9 Management and control [Go to Page]
- 9.1 Managing quality
- 9.2 Review of content
- 9.3 Approval of content
- 9.4 Search and retrieval
- 9.5 Localization and translation [Go to Page]
- 9.5.1 Translation management
- 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
- 9.6 Content deletion
- 9.7 Content and component archiving
- 10 Publication [Go to Page]
- 10.1 Release management
- 10.2 Version management
- 10.3 Publication of content
- 11 Component content management system requirements [Go to Page]
- 11.1 General
- 11.2 Component content management system framework [Go to Page]
- 11.2.1 General storage requirements
- 11.2.2 Content types
- 11.2.3 Metadata structures
- 11.2.4 Administrative metadata
- 11.2.5 Descriptive metadata
- 11.2.6 Classification
- 11.2.7 Additional metadata requirements
- 11.2.8 Organizational structures
- 11.3 Component content management system management [Go to Page]
- 11.3.1 Component creation and modification
- 11.3.2 Import/export
- 11.3.3 Bulk export
- 11.3.4 Dependency export
- 11.3.5 Archiving
- 11.4 Content object check-out and check in [Go to Page]
- 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
- 11.6 Search [Go to Page]
- 11.6.1 General
- 11.6.2 Full text search
- 11.6.3 Metadata search
- 11.6.4 Structured search
- 11.6.5 Advanced search capabilities
- 11.7 Versioning [Go to Page]
- 11.7.1 General
- 11.7.2 Branch and merge
- 11.7.3 Release management
- 11.8 Graphics and multimedia management
- 11.9 Component content management system administration [Go to Page]
- 11.9.1 User administration
- 11.9.2 Security
- 11.10 Content creation and acquisition [Go to Page]
- 11.10.1 Writing interface
- 11.10.2 Content and metadata functions
- 11.10.3 Scientific notation and vector graphics
- 11.10.4 Writing integration
- 11.10.5 Acquisition
- 11.11 Workflow [Go to Page]
- 11.11.1 Workflow creation
- 11.11.2 Workflow specification
- 11.11.3 Workflow reporting
- 11.12 Content publication [Go to Page]
- 11.12.1 General
- 11.12.2 Export to publishing support
- 11.12.3 Centralized publishing support
- 11.12.4 Publishing interface
- 11.12.5 XML publishing pipeline
- 11.12.6 Dynamic publishing
- 11.13 Localization and translation management [Go to Page]
- 11.13.1 General
- 11.13.2 XLIFF support
- 11.14 Component content management system interoperability [Go to Page]
- 11.14.1 General
- 11.14.2 Libraries and frameworks
- 11.14.3 Web services
- 11.14.4 Application Programming Interface methods
- 11.14.5 Webhooks and triggers
- Annex A (informative) Business case considerations for content management
- Bibliography
- IEEE notices and abstract
- 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 [Go to Page]
