Cart
0
Product
Products
(empty)
No products
To be determined
Shipping
$0.00
Total
Product successfully added to your shopping cart
Quantity
Total
There are 0 items in your cart.
There is 1 item in your cart.
Total products
Total shipping
To be determined
Total
Reduced price!
View larger
View larger
IEEE 26531
New product
IEEE 26531 2015 Edition, January 1, 2015 Systems and software engineering - Content management for product life-cycle, user and service management documentation
More info
Description / Abstract:
This standard states requirements for efficient development and
management of content produced
This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets.
The content to be managed with this standard includes
The purpose of this standard is to define a process for content management and the requirements of a component content management system 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 content collections published through electronic media. This database is defined as a Component content Management System (CCMS), which differs 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.
- 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 assets.
The content to be managed with this standard includes
- User information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product;
- Product life cycle information such as design documents, se cases, personas, project management plans, feature request, models, scripts, testing plans, test scripts, defect reports;
- Service management items such as service-level agreements, records, policies, procedures, and other documents
The purpose of this standard is to define a process for content management and the requirements of a component content management system 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 content collections published through electronic media. This database is defined as a Component content Management System (CCMS), which differs 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.