IEEE ISO IEC 26512 2011
$55.79
IEEE/ISO/IEC Systems and software engineering — Requirements for acquirers and suppliers of user documentation
Published By | Publication Date | Number of Pages |
IEEE | 2011 | 48 |
New IEEE Standard – Active. ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer’s standpoint and the supplier’s standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.
PDF Catalog
PDF Pages | PDF Title |
---|---|
1 | ISO/IEC/IEEE26512 Front cover |
3 | Contents |
5 | Foreword |
6 | Introduction |
9 | 1 Scope |
10 | 2 Conformance 2.1 Definition of conformance |
11 | 2.2 Conformance situations 3 Normative references 4 Terms and definitions |
16 | 5 User documentation within a system/software life cycle 5.1 Software documentation management process |
17 | 5.2 Information management process |
18 | 6 User documentation agreement processes within a system/software life cycle 6.1 User documentation acquisition process |
19 | 6.2 User documentation acquisition activities and tasks |
22 | 6.3 User documentation supply process 6.4 User documentation supply activities and tasks |
26 | 7 Defining user documentation requirements and constraints 7.1 Aspects of requirements and constraints 7.2 Schedule constraints |
27 | 7.3 Usability requirements 7.4 Product modification requirements |
28 | 7.5 Localization and translation requirements 7.6 Legal requirements |
29 | 7.7 Security requirements 7.8 Standards and conventions 7.9 Quality management requirements 8 User Documentation Specification |
30 | 9 User documentation Statement of Work |
31 | 10 Request for Proposal 10.1 Request for Proposal topics 10.2 Project objectives |
32 | 10.3 Requirements for supporting processes 10.4 Supplier capabilities and experience 10.5 Instructions for bidders 10.6 List of deliverable user documentation products or services |
33 | 10.7 Terms and conditions 10.8 Proposal evaluation criteria 11 Documentation proposal 11.1 Documentation proposal contents |
34 | 11.2 Understanding of requirements 11.3 Scope of the project |
35 | 11.4 Processes 11.5 Experience, capabilities, and available resources |
36 | 11.6 Schedule 11.7 Deliverables 11.8 Price proposal |
37 | Annex A (informative) Requirements clauses and checklist for acquirers |
42 | Annex B (informative) Requirements clauses and checklist for suppliers |
45 | Bibliography |
47 | IEEE Notice to Users |