BS ISO IEC IEEE 26531-2015 pdf free download – Systems and software engineering — Content management for product life- cycle, user and service management documentation.
This standard states requirements for efficient development and management of content produced
throughout the life-cycle of a system and software product;
for the provision of user documentation for systems and software;for the management of lT services.
This standard is independent of the tools, protocols, and systems used for content management. It does notaddress 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,lvideos 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, use cases, personas, project management plans,lfeature requests, models, scripts, testing plans, test scripts, defect reports;
service management items such as service-level agreements, records, policies,procedures, and otherldocuments.
The purpose of this standard is to define a process for content management and the requirements of acomponent 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 shouldsupport documents or topics and content units that may be assembled to produce complete documents forprint, electronic output, or content collections published through electronic media. This database is defined asa 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 throughlinking mechanisms in multiple output formats, including but not limited to documents.
The intended users of this International Standard are managers and developers of information (technicaldocumentation) and acquirers and suppliers of content management systems. Any organization that developscontent，regardless of size,can benefit from maintaining an effective content management solution andfollowing best practices for the development and management of technical content.
Systems conforming to this standard can fulfill business needs for content development and management,especially the need for a single source of authoritative information. Content objects that are unique and aremaintained as independent database objects are efficient to review, approve, and update; may be combinedto produce multiple deliverables; and are cost-effective to translate.
This standard is not a management system standard.
The content management process presented in clauses 6 through 11 of this International Standard is aspecialization (lower-level process) of the Information Management process required in ISOIECIEEE15288:2008 and lSO/IEC/IEEE 12207:2008.
2Conformance
This International Standard may be used as a conformance or a guidance document for projects andorganizations claiming conformance to ISO/IECIEEE15288:2008,Systems and software engineering -System lie cycle processes,or lSOIECIEEE 12207:2008 Systems and software engineering – Software lifecycle processes.
Throughout this International Standard, “shall is used to express a provision that is binding, “should” toexpress a recommendation among other possibilities, and “may” to indicate a course of action permissiblewithin the limits of this International Standard.
Use of the nomenclature of this International Standard for the parts of documentation, such as topics, contentunits, modules, is not required to claim conformance.
This International Standard may be included or referenced in contracts or similar agreements when the parties(called the acquirer and the supplier) agree that the supplier will deliver services and systems in accordancewith the standard.This International Standard may also be adopted as an in-house standard by a project ororganization that decides to acquire documentation from another part of the organization in accordance withthe standard.
3 Normative references
There are no Normative References applicable to this standard.
4Terms and definitions
For the purposes of this standard，the terms and definitions given in ISO/IECIEEE 24765,available atwww.computer.org/sevocab and the following apply.
4.1
application programming interface
software component that allows software applications to communicate with one another
4.2
branching
method of development in which a set of components is duplicated so the components may be modfied inparallel and optionally synchronized at a later time
4.3
component
an object with a discrete information type that is stored in the CCMS, such as a topic,prerequisite, section,image, or video.BS ISO IEC IEEE 26531 pdf download.