IEEE ISO IEC 24748 2 2018
$52.54
ISO/IEC/IEEE International Standard – Systems and software engineering–Requirements for managers of information for users of systems, software, and services
Published By | Publication Date | Number of Pages |
IEEE | 2018 | 90 |
Revision Standard – Active. This document specifies requirements and procedures for managing information for users throughout the software-, services-, and systems-development life cycle. It applies to people or organizations producing suites of information, to those undertaking a single information-development project, and to information produced internally, as well as to information contracted to outside service organizations. It provides details of the information-development and project-management processes and also presents aspects of strategic planning and translation management that managers apply. It covers management activities related to starting a project, building a team, and managing information through the translation and localization process. It addresses productivity and quality measurements needed for management control. This document is independent of the software tools that may be used to produce or manage information for users and applies to both printed, embedded, and mobile information. Much of its guidance is applicable to information for users of systems of hardware as well as software, systems, and services.
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | Foreword |
7 | Introduction |
9 | 1 Scope |
10 | 2 Normative references 3 Terms, definitions, and abbreviations |
15 | 4 Conformance |
16 | 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 |
17 | 5.1.3 Frequency of strategic work 5.1.4 Reporting structure 5.1.5 Compliance |
18 | 5.2 Stakeholders |
19 | 5.3 Manager’s strategic tasks and potential actions to support them 5.3.1 General 5.3.2 Business environment and organization situation |
20 | 5.3.3 Organizational alignment 5.3.4 Product portfolio 5.3.5 Information-development organization |
21 | 5.3.6 Stakeholder needs 5.3.7 User needs 5.3.8 Vision 5.3.9 Executing strategy |
22 | 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 |
23 | 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 |
24 | 5.4.10 Establishing a long-term content life cycle policy 5.4.11 Managing distribution 5.4.12 Security and disaster recovery |
25 | 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 |
26 | 7 Planning an information-development project 7.1 Information-development project planning defined 7.2 Developing the information-development project plan |
28 | 7.2.1 Identifying project goals 7.2.2 Analyzing project scope 7.2.3 Describing users of information |
29 | 7.2.4 Describing topics to be developed |
30 | 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 |
31 | 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 |
32 | 7.2.12 Estimating the time and costs required to complete the project |
34 | 7.2.13 Analyzing risks 7.2.14 Identifying information-development project team members |
35 | 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 |
36 | 8.2.3 Promoting team collaboration 8.2.4 Orienting new team members 8.2.5 Managing productivity and performance issues |
37 | 8.2.6 Implementing quality processes 8.2.7 Managing staff changes |
38 | 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 |
39 | 8.4 Managing project changes 8.4.1 Managing change control 8.4.2 Planning and preparing for changes |
40 | 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 |
41 | 8.4.6 Maintaining quality and the project vision |
43 | 8.4.7 Instigating changes 8.4.8 Discovering quality issues |
44 | 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 |
45 | 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 |
47 | 9.1.2 Defining roles and responsibilities |
48 | 9.1.3 Hiring and training staff |
49 | 9.1.4 Outsourcing staff |
50 | 9.1.5 Evaluating staff 9.1.6 Developing staff |
51 | 9.1.7 Succession planning 9.2 Aligning teams with the engineering life cycle |
52 | 10 Managing technical reviews 11 Managing the translation process 11.1 Translation requirements 11.1.1 Languages |
53 | 11.1.2 Character sets 11.1.3 Timing 11.1.4 Deliverables |
54 | 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 |
55 | 11.6 Translation review and quality control 11.7 Terminology management 11.8 Writing for translation |
56 | 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 |
57 | 12.1.2 During production 12.1.3 At delivery |
58 | 12.2 Before production time 13 Measuring content quality and user satisfaction 13.1 Measuring content quality and user satisfaction defined |
59 | 13.1.1 Measuring quality defects |
60 | 13.1.2 Measuring user satisfaction |
61 | 13.1.3 Correcting quality defects and improving the process 13.1.4 Using user feedback to validate measurements and improve processes |
62 | 13.2 Identifying predictive measurements for preventive action 14 Measuring productivity, efficiency, and cost 14.1 Importance of measuring cost, productivity, and efficiency 14.1.1 Operational costs |
63 | 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 14.2.1 Time intervals |
64 | 14.2.2 Time allocation 14.2.3 Typical activities for tracking time 14.2.4 Overtime 14.2.5 Monitoring project costs |
65 | 14.2.6 Reporting project costs 14.3 Productivity measurements |
66 | 14.4 Efficiency measurements |
67 | 14.4.1 Content re-use 14.4.2 Content rework 14.4.3 Cycle time |
68 | 15 Evaluating organization process maturity 15.1 Organization process maturity evaluation |
69 | 15.2 Process Improvement |
70 | Annex A (informative) User and task analysis |
73 | Annex B (informative) Project plan example |
77 | Annex C (informative) Translation management |
84 | Bibliography |
86 | IEEE notices and abstract |