Revision Standard – Superseded. ISO\/IEC\/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply. It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO\/IEC\/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage 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.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 1<\/td>\n | ISO\/IEC\/IEEE 26511:2012(E) Front Cover <\/td>\n<\/tr>\n | ||||||
| 3<\/td>\n | Contents <\/td>\n<\/tr>\n | ||||||
| 5<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | 2 Conformance 2.1 Definition of conformance 2.2 Conformance situations <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 3 Normative references 4 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 5 User documentation management within life cycle processes 5.1 User documentation management within the software life cycle <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 5.2 Portfolio management and content management 5.3 Information management strategy and policies <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 6 Planning in documentation management 6.1 Work breakdown structures for documentation management <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 6.2 Planning for user documentation <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 6.2.1 Determination of purpose and audience <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 6.2.2 Design tasks 6.2.3 Development tasks <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6.2.4 Translation and localization tasks 6.2.5 Production tasks 6.2.6 Change management and maintenance tasks <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 7 User documentation plans 7.1 User documentation management plan compared to documentation plan <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 7.2 Contents of the documentation management plan 7.3 Contents of the documentation plan <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 8 Project activation 8.1 Authorization, procedures, and specifications <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 8.2 Infrastructure <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 8.3 Information development team 8.3.1 Definition of roles <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 8.3.2 Example roles for user documentation 8.3.2.1 Manager <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 8.3.2.2 Team leader 8.3.2.3 Information architect 8.3.2.4 Usability designer 8.3.2.5 Graphic designer <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 8.3.2.6 Information designer 8.3.2.7 Writer 8.3.2.8 Illustrator 8.3.2.9 Editor <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 8.3.2.10 Quality specialist 8.3.2.11 Indexer 8.3.2.12 Tester 8.3.2.13 Translation\/localization coordinator <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 8.3.2.14 Translator 8.3.2.15 Publisher 8.3.2.16 Print Coordinator 9 User documentation management control methods 9.1 Documentation measurements <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 9.1.1 User documentation product measurements <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 9.1.2 User documentation productivity measurements 9.1.3 User documentation quality measurements <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 9.1.4 Process improvement measurements 9.2 Documentation estimating <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 10 Applying management control to documentation 10.1 Purpose and outcomes 10.2 Change management 10.3 Schedule and cost control <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 10.4 Resource management 10.4.1 Project communication 10.4.2 Managing documentation team members and suppliers 10.4.3 Managing translation services <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 10.5 Quality management 10.5.1 Managing for product quality\u2014reviews and tests 10.5.2 Risk and problem management <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 10.5.3 Process improvement <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | Annex A (informative) Sample documentation plan <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | Annex B (normative) Information Management and Software Documentation Management Processes <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | Bibliography <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | IEEE Notice to Users <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" ISO\/IEC\/IEEE International Standard – Systems and software engineering — Requirements for managers of user documentation<\/b><\/p>\n |