ISO IEC IEEE 26512 pdf free download
ISO IEC IEEE 26512 pdf free download.Systems and software engineering一 Requirements for acquirers and suppliers of user documentation.
2.2 Conformance situations
Conformance may be interpreted differently for various situations. The relevant situation shall be identified in the claim of conformance:
a) When conformance is claimed for an organization, the organization shall make public a document declaring its tailoring of the acquisition or supply process.
b) When conformance is claimed for a project using user documentation services, the project plans or the contract shall document the tailoring of the documentation management process.
NOTE 1 One possible way for an organization to deal with clauses that cite “the documentation plan” is to specify that they shall be interpreted in the project plans for any particular documentation project.
NOTE 2 A project’s claim of conformance is typically specified with respect to the organization’s claim of 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 documentation in accordance with this
International Standard. It may also be adopted as an in-house standard by a project or organization that
decides to acquire documentation from another part of the organization in accordance with this International
Standard.
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering — Software life cycle processes
ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering — System life cycle processes
ISO/IEC/IEEE 24765:2010, Systems and software engineering — Vocabulary
5 User documentation within a systemlsoftware life cycle
5.1 Software documentation management process
Acquirers and suppliers of user documentation work within the life cycle of the software product. Life cycle processes are defined in ISOIIEC 12207:2008 (IEEE Std 12207-2008). Clause 7.2.1 of ISO/IEC 12207:2008 (IEEE Std 12207-2008) describes the activities of the software documentation management process as process implementation; design and development; production; and maintenance. The Contract shall specify which of the Software Documentation Management process activities are required:
• process implementation, which includes setting objectives; project planning, management, and control; preparation of a documentation plan;
• analysis and design, which includes preparing the documentation designs for the project; collecting information about the software product and users, their tasks, and their needs for information, and designing documentation based on those needs;
• development and review, which includes structuring the content for usability, applying the documentation design by creating the written and graphic content, implementing the information in the specified media, and evaluating the user documentation with the rest of the product;
• production, which includes the integration, preparation, reproduction, and packaging and delivery of the documentation;
• maintenance, which includes keeping the documentation accurate throughout the software product life cycle, including modifications for improved usability.
Development of the user documentation should be part of the same processes as the software product life cycle, and ideally performed in conjunction with development of the software, so that the software and the user documentation may be acquired and maintained together. The specification of all the documentation, including on-screen documentation and printed documentation, should be a part of the development of the software product as a whole, not a separate exercise. ISO IEC IEEE 26512 pdf download.
