Ergonomics of human-system interaction - Specification for the process assessment of human-system issues
Some standard content:
ICS13.180
National Standard of the People's Republic of China
GB/T23701—2009/ISO/PAS18152:2003 Ergonomics of human-system interactionSpecification for the processassessment of human-system issues（ISO/PAS18152:2003.IDT）
2009-05-06 Issued
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China Standardization Administration of the People's Republic of China
2009-11-01 Implementation
1 Scope
Conformance
Normative references
Terms and definitions
Symbols (abbreviations)
6 Model content and format
7 People-system process categories (reference code H S)
Appendix A (Informative Appendix)
Appendix B (Informative Appendix)
Appendix C (Informative Appendix)
Appendix D (Informative Appendix)
Appendix E (Informative Appendix)
Appendix F (Informative Appendix)
Appendix G (Informative Appendix)
Appendix H (Informative Appendix)
Appendix I (Informative Appendix)
References
Example of Evaluation Model
Structure and Scenarios of Human-System Model
Human Resource Processes
Use of Human-System Lifecycle Processes
ISO/IEC15504 Capability Levels and Attributes
Correspondence between processes in this standard
GB/T23701—2009/ISO/PAS18152:200315
Correspondence between GB/T18976--2003/ISO13407.1999 and ISO/TR18529·Correspondence to ISO/IEC15288
Correspondence to ISO/IEC155 04
Figure B.1 Entity-relationship diagram of the model
Figure B.2 People-system processes in the system life cycle and organizationTable 1 People-system life cycle processes
Table A.1 Participation in the life cycle (HS.1)People-system issues in the concept phase (HS.1.1)Table A.2
People-system issues in the development phase (HS.1.2)Table A.3
People-system issues in the production and use phase (HS.1.3)People-system issues in the use and support phase (HS.1.4)Table A. 6
Human-system issues in the exit phase (HS.1.5) Table A.7
Integrating human factors (HS.2) ...
Human-system issues in business strategy (HS.2.1)Human-system issues in quality management (HS.2.2)Human-system issues in authorization and control (HS.2.3)Management of human-system issues (HS.2.4)
Human factors in trade-offs and risk mitigationData management (HS.2.5)User involvement (HS.2.6)
Human-system integration (HS.2. 7)
GB/T23701—2009/ISO/PAS18152:2003 Table A.15
Development and reuse of human factors data (HS.2.8) Human-centered design (HS.3)
Use context (HS.3.1)
User needs (HS.3.2)
Formulate design plan (HS.3.3)
Evaluation of use (HS.3.4)
Human resources (HS.4)
Determine and implement human resources strategy Strategy (HS.4.1) Identify standard skills and identify gaps (HS.4.2) Design and delivery of human resource solutions (HS.4.3) Evaluate system solutions and obtain feedback (HS.4.4) Work output characteristics
Require or apply a higher level of maturity than that performed in human-system operations Point diagram of the correspondence between processes in the human-system model Point diagram of the correspondence between processes and work outputs in the human-system model…·Correspondence between the clauses in GB/T18976-2003/ISO13407:1999 and the human-system model Point diagram….Point diagram of the correspondence between the clauses in ISO/TR18529 and the human-system modelPoint diagram of the correspondence between the clauses in ISO/IEC15288 and the human-system model27
GB/T23701—2009/IS0/PAS18152:2003This standard is equivalent to ISO/PAS18152:2003 "Process Assessment Specification for Human-System Matters in Human Ergonomics of Human-System Interaction"
(English version) and is drafted based on the translation of ISO/PAS18152:2003. Appendices A to I of this standard are informative appendices. This standard is proposed and managed by the National Technical Committee for Ergonomics Standardization. The drafting units of this standard: Tsinghua University, China National Institute of Standardization, Beijing Yifenger Interface Design Co., Ltd., Beijing University of Aeronautics and Astronautics, Lenovo (Beijing) Co., Ltd.
The main drafters of this standard are: Rao Peilun, Liu Taijie, Yuan Xiaowei, Wang Lijing, Zhao Chaoyi, Ran Linghua, Chen Baihong, Qin Hua. GB/T23701—2009/ISO/PAS18152:2003 Introduction
The content of this standard mainly involves the definition and handling of issues related to people (users and other stakeholders) during the system life cycle, with the purpose of being used for process evaluation. This specification describes a series of processes that can be used to solve various people-related issues throughout the system life cycle. This standard describes the content and format of the human-system model (Chapter 6) and the classification of human-system processes (Chapter 7). A process refers to what is done when developing and operating a system or organization. The processes presented in this standard, such as the human-system process model or simply the human-system model, are models that integrate good practices in ergonomics (human factors) and user-centered design in the industrial field.
The process model provides the following help:
Analyze the organization's ability to create and (or) maintain the system to achieve the required performance level; 2) Analyze the obstacles that hinder the above capabilities; 3) Point out ways to make up for these deficiencies and reduce risks. This standard makes the content of GB/T18976-2003 easy to understand for process assessors and people who are familiar with or need process models. This standard extends the scope of processes in GB/T18976-2003. Distinguish between people-centered processes and people-centered designs in the system life cycle.
This standard provides information for users and developers who need to integrate ergonomics (human factors) processes in the life cycle of systems, hardware, and software to ensure the availability, health, and safety of the system. This standard was developed to achieve the following goals: Provide methods for assessing and mitigating risks from human-system issues that affect the availability of the system throughout its life cycle.
Provide a description of the human-system process for project planning and communication between disciplines. Provides a basis for suppliers, customers, or other stakeholders to improve the human-system process. TV
1 Scope
GB/T23701—2009/IS0/PAS18152:2003 Ergonomics of human-system interaction
Specification for process assessment of human-system issues
This standard provides a human-system model (HS) that can be used for conformity assessment of ISO/IEC 15504 to assess the maturity of an organization so that the organization can ensure the availability, health and safety of the system when implementing these processes. This standard specifies the processes for human-system issues and the results of these processes, and describes in detail the specific operations and work outputs produced to achieve each process result. The processes described in the model are only used to describe and assess availability, health and safety in detail, but do not indicate all the processes related to achieving the objectives.
Before using the model for assessment, the model should be tailored to the specific circumstances of the specific organization and system. Annex D provides suggestions for customized process models for various purposes. The HS model does not specify the specific responsibilities and competence requirements of the personnel who operate the HS processes. This standard is intended for use by process assessors and developers of process assessment models and tools. It provides rich information for personnel responsible for human factors activities and human factors experts. Human factors experts must master the vocabulary of process modeling and process evaluation before reading this standard. A large number of standards and texts are listed in the reference list for reference. This standard is suitable for use in conjunction with GB/T18976-2003 and ISO/IEC15504. The latter provides a framework for the use of process descriptions covered by this standard. The series of processes covered by this standard can be used in conjunction with other process standards such as ISO/IEC12207 and ISO/IEC15288.
Note 1: Users of this standard should be familiar with GB/T18976-2003 and ISO/IEC15504. This standard applies to the description, design, evaluation and operation of manual or embedded systems, hardware and software. The model can be used for general systems (such as consumer products), customized systems (such as control or protection systems) and systems that change continuously in response to changes in business and user environments (such as management system systems), but this standard must be customized according to the specific situation before each application. NOTE 2 Disclaimer of copyright for process descriptions: Users of this standard may reproduce the process descriptions in Clause 7 and Annex A of this standard free of charge as part of a process assessment model or as part of any description that is compatible with this standard for their own purposes. 2 Conformance
A process assessment model derived from this model must meet the requirements of 6.3 of ISO/IEC 15504-2:2003 to be considered in conformity with this standard. The proof of conformance in the annex to this standard gives an example of how to state conformance. 3 Normative references
The clauses in the following documents become clauses of this standard through reference in this standard. For dated references, all subsequent amendments (excluding errata) or revisions do not apply to this standard; however, parties to agreements based on this standard are encouraged to investigate whether the latest versions of these documents are applicable. For undated references, the latest versions apply to this standard. GB/T16251-2008 Ergonomic principles for work system design (ISO6385:2004, IDT) GB/T18976-2003 Human-centered interactive system design process (ISO13407:1999, IDT) GB/T18978.11-2004 Ergonomic requirements for office use with visual display terminals (VDTs) Part 11: Usability guide (ISO9241-11:1998, IDT)
ISO/IEC912 6-1:2001 Software engineering product quality Part 1: Quality model ISO/IEC15288:2002 Systems engineering System life cycle processes ISO/IEC15504-2:2003 Process evaluation Part 2: Execution evaluation 1
GB/T23701—2009/IS0/PAS18152:2003ISO/IEC15504 (all parts) Software engineering process evaluation
4 Terms and definitions
The following terms and definitions apply to this standard. 4.1
Process capabilityprocesscapability
The ability of a process to achieve its stated objectives.
[ISO/IECTR15504-9:1998]
Note 1: Capability here is different from human capability, military capability and operational capability. To avoid confusion, no alternative terms are used in this standard. Note 2: The capability levels used in ISO/IEC15504-2 are given in Annex E. 4.2
contextof use
Context of use
Users, tasks, equipment (hardware, software and materials), the physical and social environment in which the system is used. [GB/T18978.11—2004]
enablingsystem
A system that complements other systems of interest at various stages of its life cycle, but does not directly contribute to the functionality of the system. Note 1: For example, a (enabling) production system is required when the system enters the production life cycle stage. Note 2: Any enabling system has its own life cycle. This standard applies to all enabling systems when they are systems of interest. 4.4
Enterpriseenterprise
A part of an organization whose responsibility is to acquire and provide products and/or services in accordance with an agreement. [ISO/IEC15288:2002]
Note: An organization can be contained in multiple enterprises, and an enterprise can also contain one or more organizations. 4.5
Ergonomics
ergonomics
Human factors
The study of human capabilities and limitations, the interaction between humans and technology and the environment, and the application of this knowledge to products, processes and environments. Note: The new word ergonomics is derived from the Greek words \ergos\ and \nomos\, which originally means "the law of work." 4.6
Formative evaluationformativeevaluation This evaluation is designed and used to improve the object of evaluation, especially when the object still needs improvement. [Program Evaluation Standards Version 2]
Human Factors DataHFdata
is information about users and other stakeholders, which is generated and maintained by human-related sciences. Note: This includes such things as anthropometric data, health and safety data, psychometric data, ergonomic standards, access standards and expert knowledge of all humanities (such as psychology, sociology, medicine, human-computer interaction, behavioral science, anthropology, management science, education, personnel management) and the number of this information and knowledge (such as international standards, legislative requirements, valid patents, good practices, style guides and project standards). 4.8
Human-centered design hum an-centreddesign User-centred design is a design method characterized by active user participation, clear user and job requirements, appropriate functional configuration between users and technology, iteration of design solutions, and multidisciplinary design. 2
[GB/T18976—2003,5.1]
GB/T23701—2009/ISO/PAS18152:2003 Note: Usability engineering often replaces human-centered design in applications. However, the application of usability engineering methods does not require active users, which is the basis of human-centered design. In addition, usability engineering often overemphasizes evaluation methods, while human-centered design refers to processes such as analyzing usage scenarios, extracting user needs, making design solutions, and evaluating designs based on requirements, and repeatedly refers to this process in design.
Human factors integration human factors integrationA systematic approach to identifying, tracking, and resolving human-system issues to ensure balanced development between the technical and human factors aspects of operational capabilities. Note 1: The purpose is to ensure that project decisions are supported by sufficient human-related information and that project decisions take into account appropriate human factors data. Note 2: Quoted from the UK's Human Factor Integration - An Introductory Guide 2002. 4.10
Human-system issueshuman-systemissueIssues related to people (users and other stakeholders) and the systems they participate in or interact with at any time in the system life cycle (for example: needs, requirements, constraints, limitations, concerns, obstacles, factors or ideas). B.6 lists the areas where HS issues may occur. 4.11
Lifecycle
The stages and activities in the life of a system from the definition of requirements to the end of use. Including concept formation, development, operation, maintenance support and configuration.
Note: Quoted from the definitions in GB/T18976-2003, IEC61508 and ISO/IEC12207. 4.12
(Base) Practice: (base) practice Technical or management activities that contribute to process outputs (work outputs) or improve process performance. [ISO/IECTR15504-9:1998]
Process
A series of related activities that transform inputs into outputs. [ISO/IECTR15504-9:1998]
Process assessment
A normative assessment of an organization's processes with reference to a model. [ISO/IECTR15504-9:1998]
Process categoryprocess category
A collection of processes that cover the same scope of activities. [ISO/IECTR15504-9:1998]
Process improvementprocessimprovement
Activities undertaken to improve the processes of an enterprise so that the processes meet the business needs of the enterprise and can more effectively achieve the business objectives of the enterprise.
[ISO/IECTR15504-9:1998]
Projectproject
Activities undertaken to create a product or service with specified resources and requirements and within a specified start and end time. 3
GB/T23701--2009/ISO/PAS18152.2003[[ISO/IECTR15504-9:1998]
Note: The term project is not excluded from system development. Projects include long-term activities associated with the system, such as training, maintenance and support. 4.18
Prototype
An artifact used to demonstrate to users and to obtain feedback from test users. Note 1: Includes samples, full-size models, paper prototypes, simulations, role-playing and simulated systems or documents, storylines. Note 2: Cited from GB/T 18976-2003.
Stakeholder
An interested party who has power, a stake or a claim in the system or in the quality that meets the needs and/or expectations of one party. Examples: user, customer, owner, developer, regulatory body, maintainer, support staff. "Owner" includes those responsible for system staffing (e.g., configuration planner, training organization).
Note: The term "project stakeholders" used in this standard refers to organizational members who have an interest in the project, including such people as project managers, task leaders, technical personnel, management and quality assurance personnel. 4.20
Summative evaluation
summative evaluation
The evaluation is a summary of the evaluation that expresses the strength or value of the evaluation objectives and a recommendation as to whether they should be retained, modified or abolished. [Project Evaluation Standard, 2nd Edition]
systemsystem
A combination of interacting units organized to achieve one or more specified objectives. [ISO/IEC15288:2002]
Note 1: A system can be considered as a product or a service provided. Note 2: A system includes workplaces, physical equipment, computer software, documentation, manuals, human tasks and organizational or management procedures. When these are combined with users and implemented, the result is a work system, see 4.26. GB/T 16251-2008 gives guidance on the design and operation of work systems. 4.22
tasktask
The activities performed to achieve the intended results of a work system. Note 1: Cited from GB/T16251-2008/ISO6385:2004. Note 2: Tasks are not used to describe project activities, the term "practice" is used to describe project activities. 4.23
User user
Individuals who interact with the system.
［GB/T18976-2003]
Note: Organizational users can also be considered system users. 4.24
Usability usability
The degree to which a product can be used by a specific user for a specific purpose in a specific context of use, as indicated by effectiveness, efficiency and satisfaction. [GB/T18978.11]
workproduct
Work output
Product related to the execution of a process.
［ISO/IECTR15504-9:1998]
Note: A process can use, produce or change work outputs. 4
Work systemworksystem
GB/T23701—2009/ISO/PAS18152:2003A system composed of work environment, work space, people and work equipment that work together in the work process under the set conditions in order to complete the work task.
［GB/T16251-—2008]
5Symbols (abbreviations)
Basic operation
Human-centered design
Human factors integration
Human resources
Human-system
6Model content and format
6.1Application of the standard
The HS model expresses a special view of the system process, emphasizing the handling of human-system issues in the system life cycle and its process. The human-system process includes a series of processes, including various issues related to people in the system life cycle. HS processes provide potential users with systems that are usable, healthy, and safe throughout the lifecycle. Clause 7 contains three sets of process descriptions. Each set of process descriptions includes the purpose of the process, the goals to be achieved after execution, and the actions taken to achieve the process results. Annex A provides comments on each step of the action and a list of work outputs adopted and generated by the process. This standard includes informative appendices.
Appendix A contains descriptive comments on the processes and operations in Clause 7 and a list of the results produced by each process, which can be used as an assessment model. Annex B describes the technical components of the model, the relationship between the processes in the model, the life cycle and organization, and the environment that can be used as an assessment process standard and HFI.
Annex C describes a set of additional processes related to human resource activities and system availability. Annex D describes the use of the HS model in the definition, improvement, and evaluation process. Annex E describes the scope of ISO/IEC15504 and indicates the operations in the HS model (these operations can demonstrate that the organization is more mature than level 1).
Annex F indicates the relationship between processes and work outputs in the HS model. Appendix G and Appendix H describe the correspondence between the HS model and the process model of HCD and the system life cycle. Appendix I is the ISO/IEC15504 conformance statement of the HS model. 6.2 HS model format
The format used by the HS model in this standard is the same as the process assessment model. The process assessment model describes the best possible way for an organization to achieve its technical goals. The processes in this model are expressed in the HS.nm format and title using the format used in ISO/IEC15504. "HS\ indicates that this process comes from the HS model, "n\ is the process code (i.e., the parent process), and "m" is the sub-process code. The purpose of each process is also explained along with the benefits of performing this process. The results list lists a series of results achieved after performing this process. At the same time, a list of practices required to achieve these results is also given. These practices are specially coded with extended process codes and "BP" as the sequence number. The process model does not indicate the responsibilities of the relevant personnel who perform this process. The execution of the HS process has no special connection with tasks, professions, and occupations. Table 1 lists various human-system processes and indicates the human-system process type and reference code to which they belong. The reference codes reflect the links to the processes described in Clause 7 and to the annexes that provide further details. These annexes are described in 6.1. Annexes B and F provide details of the links to the processes in the HS model. The processes are used in the life cycle and in several parts of the organization.2003. This is because a system is often divided into subsystems and small feasible units, each of which is defined, developed and maintained in the implementation of related processes. On the other hand, this is also the result of system selection and development or continuous improvement. Once the conditions for implementation are met (conditions that can achieve the expected results), the process will start running immediately. The length and complexity of the process implementation depends on the specific situation and requirements. This standard adopts the concept of phase support system in ISO/IEC15288 as the basis for HS.1, the participation process in the life cycle. ISO/IEC15288 regards each phase in the system life cycle as a process. This standard adopts this concept and uses it to describe the human-system factors in these processes. In Table 1, according to the description of processes in ISO/IEC15504, each process is classified into three categories (basic, extended, and additional) and two levels (process and component). According to GB/T18976, they are combined as follows: a)
Basic process -
Similar to the process in GB/T18976.
Extended process - Extension of the process in GB/T18976, b)
- Process beyond the scope of the process in GB/T18976. New process one
Subprocess one
- One or more groups of GB/T18976 activities in the same process. Subprocess of the extended subprocess
.
New subprocess -
process.
一One or more groups of GB/T18976 activities in the same process, and other additions, is an extension of the process beyond the scope of the process in GB/T18976 One or more sub-processes, is a sub-process of the new or extended process Table 1 Human-system life cycle process
Reference code, process overview
Process name
Reference code
Process type
HS.1 This process anticipates specific human-system issues at specific stages of the life cycle and improves the efficiency of the system life cycle by focusing on the issues of people in the system that support each stage.
Note: These processes are generally grouped according to the sample stages in Annex B of ISO/IEC15288. However, in order to make more meaningful groupings of HS activities, the use phase is divided into the early stage (installation and transition to use) and the mainstream use phase of the system (operation and support of the system). Involvement in the life cycle
Human-system issues in the concept phase
Human-system issues in the development phase
Human-system issues in the production and use phasesHuman-system issues in the use and support phasesHuman-system issues in the exit phase
Extended process
Added subprocess
Extended subprocess
Added subprocess
Extended subprocess
Added subprocess
HS.2 This process ensures that appropriate stakeholders are involved in human-system issues. Reduce life cycle costs by ensuring that human-centered design is used in the appropriate organization.
Integrate human factors
Human-system issues in business strategy
Human-system issues in quality management
Human-system issues in authorization and control
Management of human-system issues
Human factors data in trade-offs and risk mitigation
User involvement
Human-system integration
Extend process
Add subprocess
Add subprocess
Extend subprocess
Extend subprocess
Add subprocess||tt| |Extended subprocess
Extended subprocess
Process name
Development and reuse of human factors data
Table 1 (continued)
Reference code, process overview
GB/T23701—2009/IS0/PAS18152:2003 Reference code
Process type
New subprocess
HS.3 This process gives appropriate attention to user-centered technical activities and helps improve the system by designing for users who use the system in their usage contexts.
Human-centered design
Context of use
User needs
Design formulation
Evaluation of use
Basic process
Subprocess
Subprocess
Subprocess
Subprocess
HS.4 This process addresses issues in the system through human rather than equipment aspects to ensure that most equipment has the correct number of competent people over the long term.
Note: The validation criteria for this process are different from HS.1-HS.3, so these contents are placed in Appendix C rather than in the main text. Human Resources
Human Resources Strategy
Identify standard skills and identify gaps
Design and deliver human resources solutionsEvaluate system solutions and obtain feedback
7 People-System Process Category (reference code HS)7.1 Participation in the life cycle (HS.1)
New process
New sub-process
New sub-process
New sub-process
New sub-process
The purpose of the participation in the life cycle process is to consider the interests and needs of individuals and/or organizations who use the system in their work. Successful implementation of this process can achieve the following results: the project can address or anticipate issues and risks arising from human-system interactions; a)
b) The life cycle, stage planning and resource allocation of the system can reduce human risks in a low-cost and efficient manner; c)
The needs of stakeholders in the system can be communicated to the organization; d)
HS processes are applied according to the needs of the life cycle. These can be achieved by performing the following subprocesses Note: Benefits include: System usability is emphasized; User satisfaction and acceptance of the system is improved; User working conditions are improved; Support and training costs are reduced; Users feel empowered, more capable and more willing to learn; Costs throughout the system life cycle are minimized and overall system efficiency is maximized; The system can be adjusted to user needs; Organizational changes including user and developer responsibilities are addressed.
7.1.1 People-System Issues in the Concept Phase (HS.1.1) The purpose of the People-System Issues in the Concept Phase process is to develop a focus on user issues in all parts of the organization as the organization addresses strategy, markets, options, and overall planning for the proposed system. Successful implementation of this process can achieve the following results: a) HS risks and their impact on stakeholders, existing systems, and the work environment are taken into account when developing and evaluating system concepts; b) Relevant and future stakeholder, organizational, social and legal requirements are expressed in the system strategy;1 This process anticipates the emergence of specific human-system issues at specific stages of the life cycle and improves the effectiveness of the system life cycle by focusing on the issues that support people in the system at each stage.
NOTE: The processes are generally grouped according to the sample stages in Annex B of ISO/IEC 15288. However, to allow for more meaningful grouping of HS activities, the use phase is divided into the early stages (installation and transition to use) and the mainstream use phase of the system (operation and support of the system). Involvement in the life cycle
Human-system issues in the concept phase
Human-system issues in the development phase
Human-system issues in the production and use phasesHuman-system issues in the use and support phasesHuman-system issues in the exit phase
Extended process
Added subprocess
Extended subprocess
Added subprocess
Extended subprocess
Added subprocess
HS.2 This process ensures that the appropriate stakeholders are focused on human-system issues. Reduce life cycle costs by ensuring that human-centered design is used within the organization.
Integrate human factors
Human-system issues in business strategy
Human-system issues in quality management
Human-system issues in empowerment and control
Management of human-system issues
Human factors data in trade-offs and risk mitigation
User involvement
Human-system integration
Extend process
Add subprocess
Add subprocess
Extend subprocess
Extend subprocess
Add subprocess
|Extended subprocess
Extended subprocess
Process name
Development and reuse of human factors data
Table 1 (continued)
Reference code, process overview
GB/T23701—2009/IS0/PAS18152:2003 Reference code
Process type
New subprocess
HS.3 This process gives appropriate attention to user-centered technical activities and helps improve the system by designing for users who use the system in their usage contexts.
Human-centered design
Context of use
User needs
Design formulation
Evaluation of use
Basic process
Subprocess
Subprocess
Subprocess
Subprocess
HS.4 This process addresses issues in the system through human rather than equipment aspects to ensure that most equipment has the correct number of competent people over the long term.
Note: The validation criteria for this process are different from HS.1-HS.3, so these contents are placed in Appendix C rather than in the main text. Human Resources
Human Resources Strategy
Identify standard skills and identify gaps
Design and deliver human resources solutionsEvaluate system solutions and obtain feedback
7 People-System Process Category (reference code HS)7.1 Participation in the life cycle (HS.1)
New process
New sub-process
New sub-process
New sub-process
New sub-process
The purpose of the participation in the life cycle process is to consider the interests and needs of individuals and/or organizations who use the system in their work. Successful implementation of this process can achieve the following results: the project can address or anticipate issues and risks arising from human-system interactions; a)
b) The life cycle, stage planning and resource allocation of the system can reduce human risks in a low-cost and efficient manner; c)
The needs of stakeholders in the system can be communicated to the organization; d)
HS processes are applied according to the needs of the life cycle. These can be achieved by performing the following subprocesses Note: Benefits include: System usability is emphasized; User satisfaction and acceptance of the system is improved; User working conditions are improved; Support and training costs are reduced; Users feel empowered, more capable and more willing to learn; Costs throughout the system life cycle are minimized and overall system efficiency is maximized; The system can be adjusted to user needs; Organizational changes including user and developer responsibilities are addressed.
7.1.1 People-System Issues in the Concept Phase (HS.1.1) The purpose of the People-System Issues in the Concept Phase process is to develop a focus on user issues in all parts of the organization as the organization addresses strategy, markets, options, and overall planning for the proposed system. Successful implementation of this process can achieve the following results: a) HS risks and their impact on stakeholders, existing systems, and the work environment are taken into account when developing and evaluating system concepts; b) Relevant and future stakeholder, organizational, social and legal requirements are expressed in the system strategy;1 This process anticipates the emergence of specific human-system issues at specific stages of the life cycle and improves the effectiveness of the system life cycle by focusing on the issues that support people in the system at each stage.
NOTE: The processes are generally grouped according to the sample stages in Annex B of ISO/IEC 15288. However, to allow for more meaningful grouping of HS activities, the use phase is divided into the early stages (installation and transition to use) and the mainstream use phase of the system (operation and support of the system). Involvement in the life cycle
Human-system issues in the concept phase
Human-system issues in the development phase
Human-system issues in the production and use phasesHuman-system issues in the use and support phasesHuman-system issues in the exit phase
Extended process
Added subprocess
Extended subprocess
Added subprocess
Extended subprocess
Added subprocess
HS.2 This process ensures that the appropriate stakeholders are focused on human-system issues. Reduce life cycle costs by ensuring that human-centered design is used within the organization.
Integrate human factors
Human-system issues in business strategy
Human-system issues in quality management
Human-system issues in empowerment and control
Management of human-system issues
Human factors data in trade-offs and risk mitigation
User involvement
Human-system integration
Extend process
Add subprocess
Add subprocess
Extend subprocess
Extend subprocess
Add subprocess
|Extended subprocess
Extended subprocess
Process name
Development and reuse of human factors data
Table 1 (continued)
Reference code, process overview
GB/T23701—2009/IS0/PAS18152:2003 Reference code
Process type
New subprocess
HS.3 This process gives appropriate attention to user-centered technical activities and helps improve the system by designing for users who use the system in their usage contexts.
Human-centered design
Context of use
User needs
Design formulation
Evaluation of use
Basic process
Subprocess
Subprocess
Subprocess
Subprocess
HS.4 This process addresses issues in the system through human rather than equipment aspects to ensure that most equipment has the correct number of competent people over the long term.
Note: The validation criteria for this process are different from HS.1-HS.3, so these contents are placed in Appendix C rather than in the main text. Human Resources
Human Resources Strategy
Identify standard skills and identify gaps
Design and deliver human resources solutionsEvaluate system solutions and obtain feedback
7 People-System Process Category (reference code HS)7.1 Participation in the life cycle (HS.1)
New process
New sub-process
New sub-process
New sub-process
New sub-process
The purpose of the participation in the life cycle process is to consider the interests and needs of individuals and/or organizations who use the system in their work. Successful implementation of this process can achieve the following results: the project can address or anticipate issues and risks arising from human-system interactions; a)bzxZ.net
b) The life cycle, stage planning and resource allocation of the system can reduce human risks in a low-cost and efficient manner; c)
The needs of stakeholders in the system can be communicated to the organization; d)
HS processes are applied according to the needs of the life cycle. These can be achieved by performing the following subprocesses Note: Benefits include: System usability is emphasized; User satisfaction and acceptance of the system is improved; User working conditions are improved; Support and training costs are reduced; Users feel empowered, more capable and more willing to learn; Costs throughout the system life cycle are minimized and overall system efficiency is maximized; The system can be adjusted to user needs; Organizational changes including user and developer responsibilities are addressed.
7.1.1 People-System Issues in the Concept Phase (HS.1.1) The purpose of the People-System Issues in the Concept Phase process is to develop a focus on user issues in all parts of the organization as the organization addresses strategy, markets, options, and overall planning for the proposed system. Successful implementation of this process can achieve the following results: a) HS risks and their impact on stakeholders, existing systems, and the work environment are taken into account when developing and evaluating system concepts; b) Relevant and future stakeholder, organizational, social and legal requirements are expressed in the system strategy;1)
New process
New sub-process
New sub-process
New sub-process
New sub-process
The purpose of the participation process in the life cycle is to consider the interests and needs of individuals and (or) organizations that use the system in their work. Successful implementation of this process can achieve the following results: the project can solve or anticipate issues and risks arising from human-system interaction; a)
b) The life cycle, stage planning and resource allocation of the system can reduce human risks at low cost and high efficiency; c)
The needs of stakeholders in the system can be informed to the organization; d)
The HS process can be applied according to the needs of the life cycle. These can be achieved by performing the following subprocesses Note: Benefits include: System usability is emphasized; User satisfaction and acceptance of the system is improved; User working conditions are improved; Support and training costs are reduced; Users feel empowered, more capable and more willing to learn; Costs throughout the system life cycle are minimized and overall system efficiency is maximized; The system can be adjusted to user needs; Organizational changes including user and developer responsibilities are addressed.
7.1.1 People-System Issues in the Concept Phase (HS.1.1) The purpose of the People-System Issues in the Concept Phase process is to develop a focus on user issues in all parts of the organization as the organization addresses strategy, markets, options, and overall planning for the proposed system. Successful implementation of this process can achieve the following results: a) HS risks and their impact on stakeholders, existing systems, and the work environment are taken into account when developing and evaluating system concepts; b) Relevant and future stakeholder, organizational, social and legal requirements are expressed in the system strategy;1)
New process
New sub-process
New sub-process
New sub-process
New sub-process
The purpose of the participation process in the life cycle is to consider the interests and needs of individuals and (or) organizations that use the system in their work. Successful implementation of this process can achieve the following results: the project can solve or anticipate issues and risks arising from human-system interaction; a)
b) The life cycle, stage planning and resource allocation of the system can reduce human risks at low cost and high efficiency; c)
The needs of stakeholders in the system can be informed to the organization; d)
The HS process can be applied according to the needs of the life cycle. These can be achieved by performing the following subprocesses Note: Benefits include: System usability is emphasized; User satisfaction and acceptance of the system is improved; User working conditions are improved; Support and training costs are reduced; Users feel empowered, more capable and more willing to learn; Costs throughout the system life cycle are minimized and overall system efficiency is maximized; The system can be adjusted to user needs; Organizational changes including user and developer responsibilities are addressed.
7.1.1 People-System Issues in the Concept Phase (HS.1.1) The purpose of the People-System Issues in the Concept Phase process is to develop a focus on user issues in all parts of the organization as the organization addresses strategy, markets, options, and overall planning for the proposed system. Successful implementation of this process can achieve the following results: a) HS risks and their impact on stakeholders, existing systems, and the work environment are taken into account when developing and evaluating system concepts; b) Relevant and future stakeholder, organizational, social and legal requirements are expressed in the system strategy;
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.