This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans.<\/p>\n
This document provides an overview of the information-management processes that are specific for the management of information for users. It addresses the following activities:<\/p>\n
developing a comprehensive strategy for information development;<\/p>\n<\/li>\n
assessing user information needs;<\/p>\n<\/li>\n
planning and managing an information-development project;<\/p>\n<\/li>\n
staffing and forming information-development teams;<\/p>\n<\/li>\n
reviewing and testing information for users;<\/p>\n<\/li>\n
managing the translation process;<\/p>\n<\/li>\n
publishing and delivering information for users;<\/p>\n<\/li>\n
evaluating customer satisfaction and information quality;<\/p>\n<\/li>\n
measuring productivity, efficiency, and costs; and<\/p>\n<\/li>\n
evaluating organizational maturity.<\/p>\n<\/li>\n<\/ul>\n
The guidance in this document applies to multiple project management approaches, including both agile and traditional practices. Traditional practices can encompass predictive, waterfall, or other top-down management methods. Where certain practices are common in agile project management, they are noted.<\/p>\n
This document is applicable for use by managers of information for users or organizations with information developers. This document can also be consulted by those with other roles and interests in the process of developing information for users:<\/p>\n
managers of the product and system development process;<\/p>\n<\/li>\n
acquirers of information for users prepared by suppliers;<\/p>\n<\/li>\n
experienced information developers who prepare information for users;<\/p>\n<\/li>\n
human-factors experts who identify principles for making information for users more accessible and easily used; and<\/p>\n<\/li>\n
user interface designers and ergonomics experts working together to design the presentation of information.<\/p>\n<\/li>\n<\/ul>\n
This document can be applied to manage the following types of information for users, although it does not cover all aspects of them:<\/p>\n
information for user assistance, training, marketing, and systems documentation for product design and development, based on reuse of user information topics;<\/p>\n<\/li>\n
multimedia marketing presentations using animation, video, and sound;<\/p>\n<\/li>\n
information developed for virtual and augmented reality presentations;<\/p>\n<\/li>\n
computer-based training (CBT) packages and course materials intended primarily for use in formal training programs; and<\/p>\n<\/li>\n
information describing the internal operation of products.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 2 Normative references 3 Terms, definitions, and abbreviations 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 3.2 Abbreviations <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 4 Conformance <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 5 Managing strategy for information development 5.1 Information-development strategy defined 5.1.1 Purpose of strategy 5.1.2 Responsibility for strategic planning <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 5.1.3 Frequency of strategic work 5.1.4 Reporting structure 5.1.5 Compliance <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 5.2 Stakeholders <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 5.3 Manager\u2019s strategic tasks and potential actions to support them 5.3.1 General 5.3.2 Business environment and organization situation <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 5.3.3 Organizational alignment 5.3.4 Product portfolio 5.3.5 Information-development organization <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 5.3.6 Stakeholder needs 5.3.7 User needs 5.3.8 Vision 5.3.9 Executing strategy <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 5.4 Key decisions 5.4.1 General 5.4.2 Information-product delivery structure 5.4.3 Intellectual property 5.4.4 Content management system 5.4.5 Staffing <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 5.4.6 Communication 5.4.7 Information development methodology 5.4.8 Project management 5.4.9 Information management, version and change control, and archiving <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 5.4.10 Establishing a long-term content life cycle policy 5.4.11 Managing distribution 5.4.12 Security and disaster recovery <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 5.4.13 Acquisitions 5.5 Translation and localization 6 Conducting a user needs assessment 6.1 User needs assessment defined 6.2 Components of the user needs assessment <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 7 Planning an information-development project 7.1 Information-development project planning defined 7.2 Developing the information-development project plan <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 7.2.1 Identifying project goals 7.2.2 Analyzing project scope 7.2.3 Describing users of information <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 7.2.4 Describing topics to be developed <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 7.2.5 Specifying an information reuse strategy 7.2.6 Describing accessibility requirements 7.2.7 Describing translation and localization requirements 7.2.8 Describing project deliverables <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 7.2.9 Identifying project tools requirements 7.2.10 Identifying quality, review, and testing requirements 7.2.11 Determining the information-development project schedule <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 7.2.12 Estimating the time and costs required to complete the project <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 7.2.13 Analyzing risks 7.2.14 Identifying information-development project team members <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 7.3 Developing an integrated information plan 8 Managing an information-development project 8.1 Information-development project actions 8.2 Managing the project team 8.2.1 Promoting project success 8.2.2 Establishing team communications <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 8.2.3 Promoting team collaboration 8.2.4 Orienting new team members 8.2.5 Managing productivity and performance issues <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 8.2.6 Implementing quality processes 8.2.7 Managing staff changes <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 8.3 Tracking project deliverables and schedule 8.3.1 General 8.3.2 Managing project planning documents 8.3.3 New development tools 8.3.4 Managing scheduling issues <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 8.4 Managing project changes 8.4.1 Managing change control 8.4.2 Planning and preparing for changes <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 8.4.3 Assessing the impact of project changes 8.4.4 Revising project estimates 8.4.5 Recalculating the project due to changes in scope <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 8.4.6 Maintaining quality and the project vision <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 8.4.7 Instigating changes 8.4.8 Discovering quality issues <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 8.5 Communicating with the project team and management 8.5.1 General 8.5.2 Communicating with the project team 8.5.3 Communicating with stakeholders <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 8.5.4 Communicating with senior management 9 Staffing and forming teams 9.1 Staffing and forming teams defined 9.1.1 Identifying and assessing required skills <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 9.1.2 Defining roles and responsibilities <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 9.1.3 Hiring and training staff <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 9.1.4 Outsourcing staff <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 9.1.5 Evaluating staff 9.1.6 Developing staff <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 9.1.7 Succession planning 9.2 Aligning teams with the engineering life cycle <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 10 Managing technical reviews 11 Managing the translation process 11.1 Translation requirements 11.1.1 Languages <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 11.1.2 Character sets 11.1.3 Timing 11.1.4 Deliverables <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | 11.2 Selecting translation and localization approaches and services provider(s) 11.3 Translation cost estimates 11.4 Translation memory management 11.5 Machine translation <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 11.6 Translation review and quality control 11.7 Terminology management 11.8 Writing for translation <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | 11.9 Managing the translation and localization of the user interface 11.10 Guidelines for user interface translation and localization: 12 Managing final production and delivery 12.1 Final production and delivery defined 12.1.1 Final approvals <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | 12.1.2 During production 12.1.3 At delivery <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | 12.2 Before production time 13 Measuring content quality and user satisfaction 13.1 Measuring content quality and user satisfaction defined <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | 13.1.1 Measuring quality defects <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | 13.1.2 Measuring user satisfaction <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | 13.1.3 Correcting quality defects and improving the process 13.1.4 Using user feedback to validate measurements and improve processes <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | 13.2 Identifying predictive measurements for preventive action 14 Measuring productivity, efficiency, and cost 14.1 Importance of measuring cost, productivity, and efficiency <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | 14.1.1 Operational costs 14.1.2 Labor costs 14.1.3 Non-labor costs 14.1.4 Translation, printing, and publishing costs 14.2 Project costs and time tracking <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | 14.2.1 Time intervals 14.2.2 Time allocation 14.2.3 Typical activities for tracking time 14.2.4 Overtime <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | 14.2.5 Monitoring project costs 14.2.6 Reporting project costs 14.3 Productivity measurements <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | 14.4 Efficiency measurements <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | 14.4.1 Content re-use 14.4.2 Content rework <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | 14.4.3 Cycle time 15 Evaluating organization process maturity 15.1 Organization process maturity evaluation <\/td>\n<\/tr>\n | ||||||
| 71<\/td>\n | 15.2 Process Improvement <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | Annex A (informative) User and task analysis <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | Annex B (informative) Project plan example <\/td>\n<\/tr>\n | ||||||
| 79<\/td>\n | Annex C (informative) Translation management <\/td>\n<\/tr>\n | ||||||
| 86<\/td>\n | Bibliography <\/td>\n<\/tr>\n | ||||||
| 88<\/td>\n | IEEE notices and abstract <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Systems and software engineering. Requirements for managers of information for users of systems, software, and services<\/b><\/p>\n |