Some standard content:
National Standard of the People's Republic of China
GB/T18976--2003/IS0 13407:1999 Human-centred design processes for interactive systems (IS0) 13407:1999, IDT)
2003-02-21 Issued
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China
2003-08-01 Implementation
GD/T18976--2003/ISO13407:1999 This standard is equivalent to ISO13407:1999 Human-centred design processes for interactive systems Model 3 (English version) 3407 Starting point
This standard is equivalent to ISO13407:1999 Human-centred design processes for interactive systems Model 3 (English version) 3407 Starting point
This standard is equivalent to the standard, and the appendix 11 and the appendix are informative appendices. This standard is proposed by the China Standard Research Center. This standard is organized by the National Ergonomics Standardization Committee, and the drafting units of this standard are National Standard Research Center, Dawei Maritime University, Shenyang Software Co., Ltd., the Fourth Air Force Research Institute, Qinghai Haier Group, Peking University, and Ronghaitong Software Management Technology Co., Ltd. The main drafters of this standard are Chen Yuanqiao, Liu Zhengti, Jing Xiangdong, Bu Xiaochao, Zhang Hanqi, Shi Sheng, Guan Chaoyi, and Chen Lian: GR/T18976-2003/LS013407, 1999 Introduction
Human-centered design is a concurrent method for interactive systems that is particularly beneficial to system usability. It is a multidisciplinary activity that integrates ergonomic knowledge and technology. Applying ergonomics knowledge to the design of communication systems can help users improve the effectiveness and efficiency of their work, while minimizing the adverse effects that may occur on health, safety and performance during use. Applying ergonomics to system design requires considering human differences, skills, limitations and requirements. A human-centered system should support users in their work and inspire them to learn. The point is to improve work efficiency, reduce support and training costs, and increase user satisfaction. Although the knowledge of ergonomics in design has been developed recently, most of it is not known to these beginners. In order to help these beginners manage the human factors in the design of software and hardware, the standard of human-centered design can be used to supplement the existing design process methods. 134D7:1999 Human-centered interactive system design
Human-centered design activities are practiced by computers. This standard provides a human-centered design guideline. It is aimed at managers of the design process and provides guidance on the human-centered design team's response and standard tour:
This standard involves the hardware part of the system. The system must be able to obtain different names based on its benefits. Examples include: (listed) hot products, industry-related systems, industrial systems, automated banking systems, consumer codes, etc. This standard is for the daily policy and requirements of human-centered design projects. This standard does not cover all aspects of human-centered design. It does not describe in detail the methods and techniques required for human-centered design, nor does it describe the issues related to design and safety requirements. Since the content of this standard is intended for users and managers, this standard explores the necessary technical issues related to human-centered design so that managers can understand the relevance and importance of technical aspects of human-centered design in the design process and in the design process. For these issues, as a supplement to this standard, (/T, (see Appendix A and references) H97 is mainly aimed at developers, specification developers and implementers: Although this standard still involves all aspects of human-centered system development, All parties, including the users of the system, have the guidance of the relevant parts of this standard. 2 Terms and definitions
Terms and definitions are used in this standard. 2.1 Interactive system Interartvesystern
A combination of hardware and software units that enable human users to perform tasks and send specific information to human users to support users in performing tasks. Note: The term "system" must be used, and the term "system" is more important. 2.2
Original system
Base system represents the overall representation of the system, although the representativeness is limited in some aspects, it can be calculated with availability, efficiency and satisfaction as the standard, in order to show the process of providing convenience for specific users in a certain environment. (139242-11:15983.) 2. 4
Efficiency
Efficiency and accuracy of the product. (IS921-11,15.2) 2.5
Efficiency
Accuracy and accuracy of the product. (IS9241-11:13.% standard definition) 8/T18976——2003/15013407:1999 2.6
Satisfacllom
No suitable product, (S4-834) 2. 7
Use background cmitextnr nqe
Users are individuals who use products, services, equipment (financial, equipment and materials), (3.5 definition)
Users are individuals who interact with systems. (IS) 9241-10:1996 2.2 definition 3 Structure of this standard
Chapter 4 provides reasons for adopting human-centered design, which may be used to adopt human-centered design concepts or to prioritize resource allocation within a project. Chapter 5 provides guidance on the principles of human-centered design. Chapter 6 provides guidance on the principles of human-centered design. Chapter 7 provides guidance on the principles of human-centered design. Chapter 8 provides guidance on the principles of human-centered design. Chapter 9 provides guidance on the principles of human-centered design. Chapter 10 provides guidance on the principles of human-centered design. Chapter 11 provides guidance on the principles of human-centered design. Chapter 12 provides guidance on the principles of human-centered design. Chapter 13 provides guidance on the principles of human-centered design. Chapter 14 provides guidance on the principles of human-centered design. Chapter 15 provides guidance on the principles of human-centered design. Chapter 16 provides guidance on the principles of human-centered design. Chapter 17 provides guidance on the principles of human-centered design. Chapter 18 provides guidance on the principles of human-centered design. Chapter 19 ... 4. Adopt the concept of human-centered design process. All operating systems should follow the ergonomic principles described in /T1625116, and adopt people-centered design methods to develop systems to produce human benefits, protect users from adverse health and safety hazards, and meet the needs of users and organizations. Such systems:
) are easy to understand and use, thereby reducing training and support costs; h) increase user satisfaction and reduce discomfort and tension; ) improve user conversion rate; ) improve product quality; : attract users, increase competitive advantage, and deepen system communication with people-centered design. The payback can be determined by calculating the system life cycle including architecture, design, implementation, support, usage and maintenance costs:
5 Human-centered design principles
5. General
There are many industry and proprietary standard methods for designing computer-based systems. This standard does not adopt any standard process or cover all the different activities required to ensure effective system design. Instead, it complements existing methods and provides a human-centered paradigm that can be integrated into the design process in a form that is suitable for specific environments. All the human-centered design methods given in Chapter 7 can be applied to the development process in one way or another, especially the human-centered methods introduced by the design process and the job analysis. They all have the following characteristics: a) active participation and a clear understanding of users and their task requirements; b) appropriate allocation of energy between users and systems; d) iterative design and multidisciplinary design. 5.2 Active participation of users and a clear understanding of users and their task requirements GB/T 18976-2003/I5013407:The effectiveness of user participation increases as interaction between developers and users increases. The nature of user participation varies depending on the design activities undertaken. When developing a product, the users and the tasks to be performed can be directly linked to the design process. The organization that purchases the system has the opportunity to directly influence the design at the beginning of the design, and the project can evaluate the design capabilities of the personnel who will actually use the system. This participation also increases the user's recognition of the product's rights and obligations. When developing a general-purpose product or consumer product, the users are very involved and are unlikely to be easily accessible, but it is still necessary to involve users or appropriate representatives in the development work so that relevant user and service requirements can be identified and incorporated into the system concept, and to provide feedback through testing of the submitted design.
5.3 Appropriate allocation of functions between users and systems Appropriate allocation of functions is a key principle of human-centered design, that is, specifying which functions can be performed by the system and which responsibilities are the responsibility of the system. These design decisions determine the process by which a given task, task, function or responsibility is performed automatically or manually.
Such decisions should be based on many factors, such as the relative ability of people and systems to perform tasks in terms of reliability, accuracy, power, flexibility, cost, success or safety of completing tasks, and the safety and security of the product: such decisions should not be based simply on such a process, that is, determining which functions the system can perform, then allocating the remaining functions to different uses, and finally relying on their flexibility to make the system work. The final allocation of functions to people should form a set of meaningful tasks. For more advanced design solutions and decision-making, see 1509841-2 and GH/T1521, 5. 4 Re-design scheme
In the reverse design method, the feedback information from the user is a related information source. The repeated design method is combined with the active participation of the user, which can effectively reduce the risk of the system not meeting the user and organizational requirements (the results of some problems can be clearly defined) to a minimum. The reverse design method can test the initial design scheme according to the "real world" design field record: the results can be reflected back to the complete solution
The improvement design method can also be combined with other design methods. Even in the "net task\ model (a type of model with a system user-side structure and cross-layer feedback design is not allowed between layers), the complex design method can also be widely used in the intermediate layers. .
55 Multidisciplinary Design
People-centered design requires multiple skills. For this reason, a team is needed to be responsible for the human aspects of design. This requires the integration of multidisciplinary teams into the human-centered design process: such teams can be flexible and flexible, and only exist during the execution of the project. The composition of the team should reflect the relationship between the technical development team and the consumer. The main positions can be:
End user!
Buyer User!
User domain expert, business analyst:
System analyst, system modeler and programmer; d
cMarketing personnel, advertising personnel:
)User interface And designers, half designers; 1) ergonomics experts, human-machine interaction experts: h) technical design writers, training personnel, and other support personnel are required. A single team of personnel can come from different technical fields and generations, and the scale of the subject group does not have to be large. The composition of the team should be diverse enough to make appropriate trade-offs for the design scheme. 3
GB/18376—2003/[80313407:19996 Planning the human-centered design process
A plan should be formulated to specify how human-centered activities are integrated into the overall system development process. The plan identifies and explains the human-centered design activities described in the first section, namely: understanding the scientific requirements, determining the application requirements, Generative, effective evaluation of the design and development process (e.g., design and measurement of the domain); the individuals and organizations responsible for the human-centered design activities and the skills they provide; the appropriateness of the human-centered activities in the overall design development process; and the appropriateness of the human-centered activities in the overall design development process. The development of the human-centered design process should be included as part of the overall cumulative development plan and in conjunction with other relevant project requirements (change control) to ensure that it is consistently and effectively implemented. The plan should be modified, reviewed, and updated as required, and the status of missing activities discussed should be reviewed. In addition, the project cost-effectiveness is considered in the design and user management of the overall plan, and sometimes it is necessary to learn effective communication between the design team members, as well as the coordination of potential conflicts. The team members together form a broad network, and the mutual communication and creativity between the members can quickly gain benefits in the project, which will bring more expenditures in the later stage of the project. Therefore, many problems in this industry will be solved through scientific research, which will save a lot of investment in the later stage. The contractor's design is a people-centered design that reduces the limit on the current transition process: before bidding, this package will be refined, the source type, measurement and matching will be determined, and appropriate use will be made. If the contractor's development team has a quality system with a point-to-point design plan, then the person in charge can directly start the process of the film and television plan. The type of drug used will be changed, and the quality control issue involved: ? 7:1 Total purchase During the development of a system, the following four people-centered factors must be met: a) To ensure the best use of the system and to meet the needs of the user and organization: b) To provide a design solution and to evaluate the design requirements. c) To evaluate the design solutions and to assess the design requirements. As shown in Figure 1, the following should be done early in the design process: d) To ensure the effectiveness of the product or system, the design should be conducted in the early stages of the development process, or to meet the requirements of the system. Step by step, the hall is bad, for example, the suburbs meet the consumers' pressure requirements, especially for the long channel, there is no people-centered design method, when planning a system Sichuan development project, it is advisable to complete every 5 minutes and change its description of the engineering work and use it as the thinking or selection of the people-centered design method. The technical clothing policy guide for the rapid opening of the port has been discovered: there are some advanced soldiers in the design of the room, and the quality of the game is low. This is determined by the product's heat model type, such as: a large-scale pre-product single system In contrast, a small project, such as a product or solution targeting a small market, may require a smaller design team (each member of which can be responsible for multiple project packages) to use a limited number of technical skills to effectively support the design of these sites. CB/T18976--2003/IS013407:1999 User and environment factors 1 Human-centered design 7.2 Understand and specify the use context 7.2.1 The use context, organizational and physical environment characteristics determine the system's usability: Understand the context and understand the context to guide early decision-making and evaluation. Announce new products and system usage information: If the existing system will be upgraded or enhanced, the details of these information have been provided, and the changes will be made. If there are a large number of users, the desktop sales department will have a good understanding of the situation. This information can determine the priority of the system for modification and improvement.System usage should be identified from the following aspects: User characteristics
Relevant characteristics of users include knowledge and skills, training characteristics, habits, preferences and abilities. Different types of users can be identified by their relevant characteristics, such as: different experience levels, different tasks (such as security guards, installers, etc.).
5 The task summary should include the overall performance of the system to improve the performance of the task and the impact it can have on the quality of the service: the amount of money received and the duration of the service. Liu results and health and safety (for example: controlling the behavior of a computer-controlled production machine, this aspect is still fully described, and the task is inferred to include the overall quality and coordination between people and system resources. It is not appropriate to describe the task only from the perspective of a certain product or system function or feature). The user's intended use of the system environment should include all independent components, materials, and their sales selection according to the service-oriented product (one or more of which may be described from a human-centered perspective, or based on the technology, software or other non-Western or performance aspects of the selected product. Characteristics of the physical and social environment should also be described. These characteristics include meaningful standards, as well as the wider technical environment (for example: a local area network is good or bad). Xiao (creative shrimp: workplace, furniture) use of the country environment (creative rainbow, happiness and humidity type), grammar bad wear (example plan: legal partner and legal items and regulations: social benefits environment for example: three work reading, group correction of station tree benefits magic: characteristics of proof. 7.2.2 The activity points out that the promotion is a beautiful product for supply, the task environment provides a full range of related characteristics for description and delivery, and the work is accurate in the control of the recognition of which aspects of the special support for the system design flat big impact (there are unique use of this report furnace more product whole 502! Note: the product category description may not be a total change of the output type, the space change design has not passed the period of Yuanlong is a "two single piece" with a "share" big thank you trip·hot has been carried out at the time of proof, with the purpose of maintaining the existence of expansion, support innovation. The description of the room speed
company can fully stipulate the scope of the user's tasks and environment, 5) Help with appropriate sources of support for design activities:
! After product confirmation, or in the absence of confirmation, non-accountable people who can represent the vast majority of the process to make changes
CB/T18976-2003/1S0134071999d to form a sufficient extension of the document;
) The design team will be used to support design activities in an appropriate manner at an appropriate time. 7.3 Specify user and organizational requirements
7.3.1 In most design processes, defining the functional and other requirements of the system is not one of the main activities or, for people-centered design, these activities are limited to make it difficult to establish a clear statement of user and organizational requirements that are often used: In order to identify the user and organizational requirements that are often used: The following requirements should be considered: the continuity of the new system in operation and maintenance: 6) the compliance requirements (including safety and usability requirements) and the coordination and communication between other relevant parties: the efficiency of the work (including task allocation, user speed and motivation): the performance of tasks, etc.: the design and organization of the following tasks; the feasibility of operation and maintenance: the design of the human-machine interface and workstation. 7.3. The requirements of user efficiency and organization efficiency should be appropriately reduced on the basis of the appropriate contraction of the requirements, and the compliance with the requirements should be specified: the system should specify the "functional allocation", that is, the system work should be divided into manual tasks and oral tasks. These requirements should be stated in the form of a future design test so that the product can be recognized and tested during the life cycle of the project. ISO:IEC15S%1 contains the elements of how to send the test to specify the more standardized requirements of the user and organization:
) Identify the relevant users in the design and design for other people; 6) Clearly state the human-centered design criteria; ) Determine the appropriate priority for the requirements; ) Propose a quantitative standard against which the design stages can be evaluated; ) Be recognized by the broad interests of the people who use the product or in the process; Include formal requirements;
Form an agreed document.
74 Propose design plan
7.4.1 General principles
It is advisable to propose possible design plans based on the previous analysis results and the overall planning and planning to support the use of the background. The activities may include the following:
1. Propose design plans that reflect academic and professional knowledge; 2. Prepare a quick design plan that is more convenient for users to design and improve the environment, bed type, etc.; 3. Show the design plan to users and let them use the plan to carry out the task (or provide feedback from users); 4. Provide design feedback to users. 7.4.2 Use existing knowledge to propose design solutions that reflect multidisciplinary considerations: Human resources, psychology, cognitive science, product design and other related disciplines have rich scientific knowledge and theories that can provide a basis for possible design solutions: many materials have user interfaces, style guides, product knowledge and market reputation, which can help support the initial design, especially for your product. General ergonomic design guidelines can be found in relevant Appendix A lists the relevant standard documents and provides the information sources. 7.4.3 Use simulation, model, design prototype and other methods to make the design more specific, so that the simulation model, design prototype and other methods can make the communication between the designer and the user more effective and reduce the possibility of rejection when the product is produced, sometimes the initial version is provided to the end-user and needs to be collected later. The advantages of this method are: 1) it allows team members to make decisions more clearly (it allows team members to track each other within a certain period of time); 2) it allows designers to weigh and compare multiple design ideas before settling on a single solution; 3) it allows users to integrate design ideas into the development process; 4) it allows for repeated design and selection of a single design solution; 5) it improves the quality and completeness of the design specification, and allows designers to use as much information as possible from the earliest design stage! For example: from the prototype to the prototype, you can use the prototype method. "A prototype can be very simple, such as a schematic diagram, or it can be very complex, such as a technical prototype whose structure is indistinguishable from the real product. 7.4.4 Show the design to users and have them perform tasks with it (or simulate tasks) quickly and efficiently, so that users can interact with the design early and in the real world. This can include showing users the system; showing them a single image and requiring verification, for example, that the system works well under real-world conditions. For hard products, a two-dimensional prototype made of simple materials can be used to evaluate the system's working accuracy quickly and inexpensively. The prototype can be used to achieve similar effects and early evaluation. Simple prototypes are more useful than multiple design concepts. It is a good idea to design a design that is as realistic as possible. The key is not to waste too much time, money and investment in design in principle. In the human-centered design method, prototypes are not used to simply replace users, but to collect user feedback to improve the design. If you cannot show users in the early stage, you can get accurate evaluation from experts. Experts often negotiate prices, which is an extremely effective method. , which can be supplemented by production testing. However, for the human-centered design process, the most important thing to note is that testing (which is rare) is still the most important thing to verify the user experience. 7.4.5 Modify the design based on user feedback until the human-centered design goals are met. The prototype level and feedback process take multiple times, including optimization of important design elements. In the actual design of the product, the prototype method can start with a visual prototype on paper and, after several rounds of feedback, until the interactive image is sufficient to support some product services, the prototype can be evaluated in a more appropriate environment in order to gain more information. To maximize the benefits, it is advisable to conduct a formal evaluation in a real environment to ensure that the overall objectives have been met. For example, the evaluation should be conducted in the presence of support or interference, user feedback, and the difficulties encountered in using the prototype. This provides a guide for changing the functional design to improve the system's usability. In some cases, this feedback information can also help clarify the scope of use of the system (see 7, 5, 1). 7.4.6 Manage the design of the support plan. In order to manage and promote the progress of the design, 7.4.3 to 4.5. The station shall record the results. This record may be the entire product documentation, or it may include the design product body, such as some prototype hardware and software. The record includes: ! The source of existing knowledge and standards, and how this knowledge was used or not used; h) The steps taken to ensure that the original bomb meets the requirements and new good practices are implemented; Identify the nature of the problems that arise and subsequent long-term design improvements. 7.5 Evaluation of design according to requirements
7.5.1 General
Evaluation is a basic step in the design process and can be carried out at all stages of the system life cycle: Evaluation can be used to:
a) Provide feedback that can be used to improve the design; b) Assess whether the organization's goals are being achieved (B/T.18976-2003/ISO13407:1999) Monitor the long-term use of the product or system. In the mid-term design stage, the sub-points are used to obtain feedback for guidance. Feedback from the design can be obtained in the later stages when a relatively complete prototype is available (see 3. In the early stages of the design process: the cost of changing the design is relatively low. As the development time increases, the more complete the system development is, the higher the cost of changing the design will be. Therefore, it is very important to start the evaluation early. 7.5.2 Evaluation plan
Establish an evaluation plan with the following aspects in mind: 6) People-centered design objectives:
b) People responsible for evaluation:
What parts of the system will be evaluated and how these parts will be evaluated (for example: application scenarios, design principles or prototypes, etc.):
How to conduct the evaluation and develop the quality sequence:) Evaluation activities, analysis of results and timely access to resources required by users are important. Evaluation activities are timetabled and their use in the project environment is critical: feedback and other use of design activity results. Different evaluation systems implement different evaluations and evaluation techniques vary in terms of quality, rigor, and degree of user involvement. Evaluation activities are timetabled and their use is important: feedback and other use of design activity results. Different systems implement different evaluations and evaluation techniques vary in terms of quality, rigor, and degree of user involvement. Evaluation activities are timetabled and their use is important: feedback and other use of design activity results. Evaluation activities are timetabled and their use is critical: feedback and other use of design activity results. Different systems implement different evaluations and evaluation techniques vary in terms of quality, rigor, and degree of user involvement. Evaluation activities are timetabled and their use is important: feedback and other use of design activities ... The design is designed to meet the needs of users and users; the user evaluation is to identify the main issues, but it is not to ensure a successful transaction. The system requirements and references are listed in the attached document as the basis for the process and criteria for this process. In any early stage of design, user evaluation can provide feedback: Early stage: Users can participate in the evaluation of the field and simple paper design prototypes or headquarters prototypes. For details on the iterative design, see 7.1. As the design solution evolves, the evaluation of user participation will be based on the continuous improvement and system experience. When trying to improve the prototype to meet the human-centered design goals, a collaborative evaluation method (evaluators and users discuss issues that arise with the company 1.5.4 Evaluation whether the goals have been achieved
Evaluation is used to prove that the design meets the certain human-centered requirements; b. Assess compliance with surrounding standards, industry standards, local standards or corporate standards: For more advanced evaluation criteria, please refer to the special standards listed in 4. In order to obtain effective results, the evaluation stage should be appropriate, and the selection of evaluation criteria should avoid the real-world errors. For each evaluation criteria, the selection of evaluation criteria should be based on the requirements of the product and the needs of the organization that reveal the criteria: the criteria can be used to support one main purpose (for example: state reliability), the city day (for example: successful implementation). Change an object) or a minor day (for example: maintainability, the day will be used to focus on the most important day of the product. If you understand other functions, it means that the goal is usually the best and most realistic approach. There is no specific goal for a specific day, and then the development process will not be evaluated accordingly. At the same time, it is not necessary to meet the minimum acceptable level of internal standards for the evaluation criteria. Further: Good faith! 211.5
7.5.5 Field verification
GD/T18975—2003/1W)13407:1999 The purpose of field verification is to test the entire system function to ensure that it meets the requirements of users, tasks and environments, and to quickly use the main technologies, including desktop and help materials, other field reports, actual user feedback, lock effect data, health impact reports, equipment acceptance and change requests.
7.5.E Long-term monitoring
There should be a long-term monitoring process for the use of the product in a planned process. In a people-centered design, as part of the design and evaluation process, the system also needs to include the people who use the product. Long-term monitoring means that if the system is used over a period of time and under different circumstances, there will be a big difference between short-term and long-term evaluation. Sometimes the system is used for a period of time, or there are still effects caused by external factors (such as unforeseen changes in previous operating practices), some of the impacts of the system will not be recognized.
Continuation effectiveness verification and company reports can provide assessment parameters for the long-term evaluation process. In the design phase, the design principles of human decision-making are the most important assessment parameters. The effectiveness verification may be very straightforward: how is the system operating to the "productivity code?" Information can be obtained from economic and market research, or from cost analysis. Modification! Requirements and their averages: Criteria and measurement methods are used to determine the initial stage, so that system failures or problems can be identified in the initial stage. : Product, meaning, clothing, individual behavior, and the effectiveness of the single certification. Recognize the psychological effects of the second-class design and make up for the disease. 7.5.7 Report results
7.5.7.1 In order to make the design intelligent, the evaluation The results are recorded in a systematic way. Appendix 1 provides a summary of the design and marketing information of the announcement, including examples of product design, product design, and other aspects of the announcement. The design is intended to be submitted by all parties, whether they are consumers or reviewers, and the appendix also lists relevant information about the appropriate evidence for the full evaluation. The following aspects should be appropriately used. a) The number of users is small enough and these users are representative of the user group identified in the test for the main human-centered drug test: 6
The test data collection method used is not effective ; J: The test results are handled appropriately;
The test conditions are appropriate.
There are three types of evaluation reports that can be used for design. This depends on the purpose of the evaluation; is it to provide feedback information? Is there enough evidence to hold the test results to a certain standard? Is the test conducted by the testers recognized as people-centered? (Example: in the market for health and safety aspects of usability or production?
7.5.7.2 Reports that provide feedback information on the design should be: generated during the common period of non-safety processes; ·· Based on appropriate evaluation sources, example: planning: design review: - provide technical support for design decision-making information: - provide a demonstrable history of the effectiveness of the system (planning 7.5.7.3 Report on design testing in accordance with approved standards: Provide evidence that the personnel who conducted the test according to appropriate procedures have conducted the test; Provide evidence that the overall system results are meaningful and that more than one part of the system has been tested. How to deal with non-conformities in the design; 7.5.7.4 Request for user testing: Determine the duration of the trial period for evaluation; Provide information about the requirements of the product organization: The necessary product and design requirements, such as: Product prototype:1999) Monitor the long-term use of a product or system. In the mid-term design stage, the point is to obtain feedback to guide the design. In the later stages, when a relatively complete prototype is available, it can be used and organized as a target (see, 3. In the concurrent and unimplemented stages of the design process: the cost of changing the design is relatively low. As the development time increases, the more complete the system development is, the higher the cost of changing the design. Therefore, it is extremely important to start the evaluation early. 7.5.2 Evaluation plan
Establish an evaluation plan with the following aspects in mind: 6) People-centered design objectives:
b) Personnel responsible for evaluation:
Will evaluate other parts of the system and how to plan these parts. For example: test scenarios, design principles or prototypes, etc.:
How to conduct the evaluation to develop the quality sequence:) Evaluation activities, site results analysis and necessary visits to users! Evaluation activities are the key to timetable and project planning: feedback and other use of design activity results. Different evaluation methods are used differently and evaluation techniques vary in terms of quality, rigor, and degree of user involvement. Evaluation activities are dependent on the time and resources required and occur at the stage of the implementation cycle required to develop the system. 7.5.3 Provide feedback on the design All risks should be evaluated during the life of the system in order to influence the atmosphere of the delivery. Specific evaluation points should be addressed to one or more specific objectives: 1. Assess the extent to which the system meets the organizational objectives: 2. Identify problems in the system, support materials, workstation environment or design, and identify any issues that may arise during the implementation cycle. 3. Focus on the evaluation process. Choose a design that meets the needs of the users; further evaluation of the user experience is both fast and economical, and identifies key issues, but it is not to ensure a successful transaction. The system requirements and references are listed in the process and criteria for this process. At any stage of the design, user evaluation can provide feedback: Early stage: Users can participate in the evaluation of the field and simple paper design prototypes or headquarters prototypes. For details on the design of the prototype, see 7.1. As the design solution evolves, the user-involved evaluation will be based on the continuous improvement and practical experience of the system. When trying to improve the prototype to meet the human-centered design goals, a collaborative evaluation method (evaluators and users discuss issues that arise with the company 1.5.4 Evaluation whether the goals have been achieved
Evaluation is used to prove that the design meets the certain human-centered requirements; b. Assess compliance with surrounding standards, industry standards, local standards or corporate standards: For more advanced evaluation criteria, please refer to the special standards listed in 4. In order to obtain effective results, the evaluation stage should be appropriate, and the selection of evaluation criteria should avoid the real-world errors. For each evaluation criteria, the selection of evaluation criteria should be based on the requirements of the product and the needs of the organization that reveal the criteria: the criteria can be used to support one main purpose (for example: state reliability), the city day (for example: successful implementation). Change an object) or a minor day (for example: maintainability, the day will be used to focus on the most important day of the product. If you understand other functions, it means that the goal is usually the best and most realistic approach. There is no specific goal for a specific day, and then the development process will not be evaluated accordingly. At the same time, it is not necessary to meet the minimum acceptable level of internal standards for the evaluation criteria. Further: Good faith! 211.5
7.5.5 Field verification
GD/T18975—2003/1W)13407:1999 The purpose of field verification is to test the entire system function to ensure that it meets the requirements of users, tasks and environments, and to quickly use the main technologies, including desktop and help materials, other field reports, actual user feedback, lock effect data, health impact reports, equipment acceptance and change requests.
7.5.E Long-term monitoring
There should be a long-term monitoring process for the use of the product in a planned process. In a people-centered design, as part of the design and evaluation process, the system also needs to include the people who use the product. Long-term monitoring means that if the system is used over a period of time and under different circumstances, there will be a big difference between short-term and long-term evaluation. Sometimes the system is used for a period of time, or there are still effects caused by external factors (such as unforeseen changes in previous operating practices), some of the impacts of the system will not be recognized. bZxz.net
Continuation effectiveness verification and company reports can provide assessment parameters for the long-term evaluation process. In the design phase, the design principles of human decision-making are the most important assessment parameters. The effectiveness verification may be very straightforward: how is the system operating to the "productivity code?" Information can be obtained from economic and market research, or from cost analysis. Modification! Requirements and their averages: Criteria and measurement methods are used to determine the initial stage, so that system failures or problems can be identified in the initial stage. : Product, meaning, clothing, individual behavior, and the effectiveness of the single certification. Recognize the psychological effects of the second-class design and make up for the disease. 7.5.7 Report results
7.5.7.1 In order to make the design intelligent, the evaluation The results are recorded in a systematic way. Appendix 1 provides a summary of the design and marketing information of the announcement, including examples of product design, product design, and other aspects of the announcement. The design is intended to be submitted by all parties, whether they are consumers or reviewers, and the appendix also lists relevant information about the appropriate evidence for the full evaluation. The following aspects should be appropriately used. a) The number of users is small enough and these users are representative of the user group identified in the test for the main human-centered drug test: 6
The test data collection method used is not effective ; J: The test results are handled appropriately;
The test conditions are appropriate.
There are three types of evaluation reports that can be used for design. This depends on the purpose of the evaluation; is it to provide feedback information? Is there enough evidence to hold the test results to a certain standard? Is the test conducted by the testers recognized as people-centered? (Example: in the market for health and safety aspects of usability or production?
7.5.7.2 Reports that provide feedback information on the design should be: generated during the common period of non-safety processes; ·· Based on appropriate evaluation sources, example: planning: design review: - provide technical support for design decision-making information: - provide a demonstrable history of the effectiveness of the system (planning 7.5.7.3 Report on design testing in accordance with approved standards: Provide evidence that the personnel who conducted the test according to appropriate procedures have conducted the test; Provide evidence that the overall system results are meaningful and that more than one part of the system has been tested. How to deal with non-conformities in the design; 7.5.7.4 Request for user testing: Determine the duration of the trial period for evaluation; Provide information about the requirements of the product organization: The necessary product and design requirements, such as: Product prototype:1999) Monitor the long-term use of a product or system. In the mid-term design stage, the point is to obtain feedback to guide the design. In the later stages, when a relatively complete prototype is available, it can be used and organized as a target (see, 3. In the concurrent and unimplemented stages of the design process: the cost of changing the design is relatively low. As the development time increases, the more complete the system development is, the higher the cost of changing the design. Therefore, it is extremely important to start the evaluation early. 7.5.2 Evaluation plan
Establish an evaluation plan with the following aspects in mind: 6) People-centered design objectives:
b) Personnel responsible for evaluation:
Will evaluate other parts of the system and how to plan these parts. For example: test scenarios, design principles or prototypes, etc.:
How to conduct the evaluation to develop the quality sequence:) Evaluation activities, site results analysis and necessary visits to users! Evaluation activities are the key to timetable and project planning: feedback and other use of design activity results. Different evaluation methods are used differently and evaluation techniques vary in terms of quality, rigor, and degree of user involvement. Evaluation activities are dependent on the time and resources required and occur at the stage of the implementation cycle required to develop the system. 7.5.3 Provide feedback on the design All risks should be evaluated during the life of the system in order to influence the atmosphere of the delivery. Specific evaluation points should be addressed to one or more specific objectives: 1. Assess the extent to which the system meets the organizational objectives: 2. Identify problems in the system, support materials, workstation environment or design, and identify any issues that may arise during the implementation cycle. 3. Focus on the evaluation process. Choose a design that meets the needs of the users; further evaluation of the user experience is both fast and economical, and identifies key issues, but it is not to ensure a successful transaction. The system requirements and references are listed in the process and criteria for this process. At any stage of the design, user evaluation can provide feedback: Early stage: Users can participate in the evaluation of the field and simple paper design prototypes or headquarters prototypes. For details on the design of the prototype, see 7.1. As the design solution evolves, the user-involved evaluation will be based on the continuous improvement and practical experience of the system. When trying to improve the prototype to meet the human-centered design goals, a collaborative evaluation method (evaluators and users discuss issues that arise with the company 1.5.4 Evaluation whether the goals have been achieved
Evaluation is used to prove that the design meets the certain human-centered requirements; b. Assess compliance with surrounding standards, industry standards, local standards or corporate standards: For more advanced evaluation criteria, please refer to the special standards listed in 4. In order to obtain effective results, the evaluation stage should be appropriate, and the selection of evaluation criteria should avoid the real-world errors. For each evaluation criteria, the selection of evaluation criteria should be based on the requirements of the product and the needs of the organization that reveal the criteria: the criteria can be used to support one main purpose (for example: state reliability), the city day (for example: successful implementation). Change an object) or a minor day (for example: maintainability, the day will be used to focus on the most important day of the product. If you understand other functions, it means that the goal is usually the best and most realistic approach. There is no specific goal for a specific day, and then the development process will not be evaluated accordingly. At the same time, it is not necessary to meet the minimum acceptable level of internal standards for the evaluation criteria. Further: Good faith! 211.5
7.5.5 Field verification
GD/T18975—2003/1W)13407:1999 The purpose of field verification is to test the entire system function to ensure that it meets the requirements of users, tasks and environments, and to quickly use the main technologies, including desktop and help materials, other field reports, actual user feedback, lock effect data, health impact reports, equipment acceptance and change requests.
7.5.E Long-term monitoring
There should be a long-term monitoring process for the use of the product in a planned process. In a people-centered design, as part of the design and evaluation process, the system also needs to include the people who use the product. Long-term monitoring means that if the system is used over a period of time and under different circumstances, there will be a big difference between short-term and long-term evaluation. Sometimes the system is used for a period of time, or there are still effects caused by external factors (such as unforeseen changes in previous operating practices), some of the impacts of the system will not be recognized.
Continuation effectiveness verification and company reports can provide assessment parameters for the long-term evaluation process. In the design phase, the design principles of human decision-making are the most important assessment parameters. The effectiveness verification may be very straightforward: how is the system operating to the "productivity code?" Information can be obtained from economic and market research, or from cost analysis. Modification! Requirements and their averages: Criteria and measurement methods are used to determine the initial stage, so that system failures or problems can be identified in the initial stage. : Product, meaning, clothing, individual behavior, and the effectiveness of the single certification. Recognize the psychological effects of the second-class design and make up for the disease. 7.5.7 Report results
7.5.7.1 In order to make the design intelligent, the evaluation The results are recorded in a systematic way. Appendix 1 provides a summary of the design and marketing information of the announcement, including examples of product design, product design, and other aspects of the announcement. The design is intended to be submitted by all parties, whether they are consumers or reviewers, and the appendix also lists relevant information about the appropriate evidence for the full evaluation. The following aspects should be appropriately used. a) The number of users is small enough and these users are representative of the user group identified in the test for the main human-centered drug test: 6
The test data collection method used is not effective ; J: The test results are handled appropriately;
The test conditions are appropriate.
There are three types of evaluation reports that can be used for design. This depends on the purpose of the evaluation; is it to provide feedback information? Is there enough evidence to hold the test results to a certain standard? Is the test conducted by the testers recognized as people-centered? (Example: in the market for health and safety aspects of usability or production?
7.5.7.2 Reports that provide feedback information on the design should be: generated during the common period of non-safety processes; ·· Based on appropriate evaluation sources, example: planning: design review: - provide technical support for design decision-making information: - provide a demonstrable history of the effectiveness of the system (planning 7.5.7.3 Report on design testing in accordance with approved standards: Provide evidence that the personnel who conducted the test according to appropriate procedures have conducted the test; Provide evidence that the overall system results are meaningful and that more than one part of the system has been tested. How to deal with non-conformities in the design; 7.5.7.4 Request for user testing: Determine the duration of the trial period for evaluation; Provide information about the requirements of the product organization: The necessary product and design requirements, such as: Product prototype:3 Provide feedback on the design All risks should be evaluated during the life of the system to influence the atmosphere delivered. Specific evaluations should be based on individual or specific goals. 2 Assess the extent to which the system meets the goals: Identify problems in the design, support materials, workstation environment or training plan, and make specific improvements. Select a design that meets the needs of the user; further evaluate the system to ensure that it is both fast and economical, and identify the main issues, but it is not to ensure a successful delivery. The system requirements and reference standards listed in the warranty and quality guidelines are used as the basis for this process and criteria. At any stage of the design process, user evaluation can provide feedback: Early stage: User evaluation of real-time and simple paper prototypes or prototypes. For details on the iteration of the design process, see 7.1. As the design plan evolves, user evaluation will be based on the continuous improvement and experience of the system. When trying to improve the prototype to meet the human-centered design goals, a collaborative evaluation method (evaluators and users discuss issues that arise with the company 1.5.4 Evaluation whether the goals have been achieved
Evaluation is used to prove that the design meets the certain human-centered requirements; b. Assess compliance with surrounding standards, industry standards, local standards or corporate standards: For more advanced evaluation criteria, please refer to the special standards listed in 4. In order to obtain effective results, the evaluation stage should be appropriate, and the selection of evaluation criteria should avoid the real-world errors. For each evaluation criteria, the selection of evaluation criteria should be based on the requirements of the product and the needs of the organization that reveal the criteria: the criteria can be used to support one main purpose (for example: state reliability), the city day (for example: successful implementation). Change an object) or a minor day (for example: maintainability, the day will be used to focus on the most important day of the product. If you understand other functions, it means that the goal is usually the best and most realistic approach. There is no specific goal for a specific day, and then the development process will not be evaluated accordingly. At the same time, it is not necessary to meet the minimum acceptable level of internal standards for the evaluation criteria. Further: Good faith! 211.5
7.5.5 Field verification
GD/T18975—2003/1W)13407:1999 The purpose of field verification is to test the entire system function to ensure that it meets the requirements of users, tasks and environments, and to quickly use the main technologies, including desktop and help materials, other field reports, actual user feedback, lock effect data, health impact reports, equipment acceptance and change requests.
7.5.E Long-term monitoring
There should be a long-term monitoring process for the use of the product in a planned process. In a people-centered design, as part of the design and evaluation process, the system also needs to include the people who use the product. Long-term monitoring means that if the system is used over a period of time and under different circumstances, there will be a big difference between short-term and long-term evaluation. Sometimes the system is used for a period of time, or there are still effects caused by external factors (such as unforeseen changes in previous operating practices), some of the impacts of the system will not be recognized.
Continuation effectiveness verification and company reports can provide assessment parameters for the long-term evaluation process. In the design phase, the design principles of human decision-making are the most important assessment parameters. The effectiveness verification may be very straightforward: how is the system operating to the "productivity code?" Information can be obtained from economic and market research, or from cost analysis. Modification! Requirements and their averages: Criteria and measurement methods are used to determine the initial stage, so that system failures or problems can be identified in the initial stage. : Product, meaning, clothing, individual behavior, and the effectiveness of the single certification. Recognize the psychological effects of the second-class design and make up for the disease. 7.5.7 Report results
7.5.7.1 In order to make the design intelligent, the evaluation The results are recorded in a systematic way. Appendix 1 provides a summary of the design and marketing information of the announcement, including examples of product design, product design, and other aspects of the announcement. The design is intended to be submitted by all parties, whether they are consumers or reviewers, and the appendix also lists relevant information about the appropriate evidence for the full evaluation. The following aspects should be appropriately used. a) The number of users is small enough and these users are representative of the user group identified in the test for the main human-centered drug test: 6
The test data collection method used is not effective ; J: The test results are handled appropriately;
The test conditions are appropriate.
There are three types of evaluation reports that can be used for design. This depends on the purpose of the evaluation; is it to provide feedback information? Is there enough evidence to hold the test results to a certain standard? Is the test conducted by the testers recognized as people-centered? (Example: in the market for health and safety aspects of usability or production?
7.5.7.2 Reports that provide feedback information on the design should be: generated during the common period of non-safety processes; ·· Based on appropriate evaluation sources, example: planning: design review: - provide technical support for design decision-making information: - provide a demonstrable history of the effectiveness of the system (planning 7.5.7.3 Report on design testing in accordance with approved standards: Provide evidence that the personnel who conducted the test according to appropriate procedures have conducted the test; Provide evidence that the overall system results are meaningful and that more than one part of the system has been tested. How to deal with non-conformities in the design; 7.5.7.4 Request for user testing: Determine the duration of the trial period for evaluation; Provide information about the requirements of the product organization: The necessary product and design requirements, such as: Product prototype:3 Provide feedback on the design All risks should be evaluated during the life of the system to influence the atmosphere delivered. Specific evaluations should be based on individual or specific goals. 2 Assess the extent to which the system meets the goals: Identify problems in the design, support materials, workstation environment or training plan, and make specific improvements. Select a design that meets the needs of the user; further evaluate the system to ensure that it is both fast and economical, and identify the main issues, but it is not to ensure a successful delivery. The system requirements and reference standards listed in the warranty and quality guidelines are used as the basis for this process and criteria. At any stage of the design process, user evaluation can provide feedback: Early stage: User evaluation of real-time and simple paper prototypes or prototypes. For details on the iteration of the design process, see 7.1. As the design plan evolves, user evaluation will be based on the continuous improvement and experience of the system. When trying to improve the prototype to meet the human-centered design goals, a collaborative evaluation method (evaluators and users discuss issues that arise with the company 1.5.4 Evaluation whether the goals have been achieved
Evaluation is used to prove that the design meets the certain human-centered requirements; b. Assess compliance with surrounding standards, industry standards, local standards or corporate standards: For more advanced evaluation criteria, please refer to the special standards listed in 4. In order to obtain effective results, the evaluation stage should be appropriate, and the selection of evaluation criteria should avoid the real-world errors. For each evaluation criteria, the selection of evaluation criteria should be based on the requirements of the product and the needs of the organization that reveal the criteria: the criteria can be used to support one main purpose (for example: state reliability), the city day (for example: successful implementation). Change an object) or a minor day (for example: maintainability, the day will be used to focus on the most important day of the product. If you understand other functions, it means that the goal is usually the best and most realistic approach. There is no specific goal for a specific day, and then the development process will not be evaluated accordingly. At the same time, it is not necessary to meet the minimum acceptable level of internal standards for the evaluation criteria. Further: Good faith! 211.5
7.5.5 Field verification
GD/T18975—2003/1W)13407:1999 The purpose of field verification is to test the entire system function to ensure that it meets the requirements of users, tasks and environments, and to quickly use the main technologies, including desktop and help materials, other field reports, actual user feedback, lock effect data, health impact reports, equipment acceptance and change requests.
7.5.E Long-term monitoring
There should be a long-term monitoring process for the use of the product in a planned process. In a people-centered design, as part of the design and evaluation process, the system also needs to include the people who use the product. Long-term monitoring means that if the system is used over a period of time and under different circumstances, there will be a big difference between short-term and long-term evaluation. Sometimes the system is used for a period of time, or there are still effects caused by external factors (such as unforeseen changes in previous operating practices), some of the impacts of the system will not be recognized.
Continuation effectiveness verification and company reports can provide assessment parameters for the long-term evaluation process. In the design phase, the design principles of human decision-making are the most important assessment parameters. The effectiveness verification may be very straightforward: how is the system operating to the "productivity code?" Information can be obtained from economic and market research, or from cost analysis. Modification! Requirements and their averages: Criteria and measurement methods are used to determine the initial stage, so that system failures or problems can be identified in the initial stage. : Product, meaning, clothing, individual behavior, and the effectiveness of the single certification. Recognize the psychological effects of the second-class design and make up for the disease. 7.5.7 Report results
7.5.7.1 In order to make the design intelligent, the evaluation The results are recorded in a systematic way. Appendix 1 provides a summary of the design and marketing information of the announcement, including examples of product design, product design, and other aspects of the announcement. The design is intended to be submitted by all parties, whether they are consumers or reviewers, and the appendix also lists relevant information about the appropriate evidence for the full evaluation. The following aspects should be appropriately used. a) The number of users is small enough and these users are representative of the user gro
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.