Model-based human factor analysis integrated modeling method and system

Abstract

The invention discloses a model-based human factor analysis integrated modeling method and system. The method comprises the following steps: establishing an operation task list from a stakeholder perspective by using an operation concept analysis method; constructing a task scene case based on the operation task list and a SysML modeling language; human factor task analysis is carried out based on the task scene use case, the operation task list and the interaction relation, and human factor requirements related to the task are identified; a task, demand and system mapping table is formed based on the SysML modeling language, and a task and demand integrated model is obtained; and carrying out satisfaction verification on the task and demand integrated model by adopting professional human factor analysis software, and taking the task and demand integrated model passing the verification as a human factor analysis integrated model. According to the method, human factor task and demand modeling is carried out on the SysML modeling language, system engineering and human factor engineering are closely linked together, and the problems that in the complex system design process, human factor problems are not fully considered, and the human factor problem iteration period span is long are solved.

Description

Technical Field

[0001] The present invention relates to the field of aerospace modeling, and in particular to a model-based human factors analysis integrated modeling method and system. Background Art

[0002] In complex systems, people are key components and an important factor affecting the performance and safety of the entire system. However, current system design faces the challenge of lack of early human factors considerations, which prolongs the cycle of problem identification and correction and significantly increases R&D costs. Although model-based systems engineering (MBSE) has become a mainstream system design method, when conducting system design according to the MBSE method, human factors requirements are still conveyed in a traditional text-based manner, resulting in poor consistency in human factors expression, difficulty in tracking and verifying human factors requirements, and MBSE tends to regard people as interactors outside the system rather than organic components within the system, resulting in deficiencies in dealing with the non-functional design dimension of human factors.

[0003] The design of complex systems follows the "people-oriented" design thinking. The key is to deeply understand the task requirements and behavioral characteristics of users in specific situations, that is, to conduct human-factor task and demand analysis. Human-factor task and demand analysis is a basic research method in fields such as human-computer interaction and engineering psychology. It aims to scientifically and systematically explore and define the real needs and limitations of users when interacting with complex systems. As a bridge connecting users and technology, it can not only promote technology to be close to engineering needs, but also promote the construction of a harmonious human-computer relationship.

[0004] Dov Dori et al. proposed using OPM (Object-Process Methodology) task analysis method to conduct task requirement analysis in human factors engineering. By combining objects (system components) and processes (activities), with the help of graphics (Object-Process Diagrams) and text (Object-Process Language), system tasks are made more comprehensive and easier to understand. OPM can be used to model systems, define architectures, etc., but it cannot be integrated into MBSE and can only be used as an independent task requirement analysis tool, which cannot solve the problem of separation between human factors engineering and system engineering.

[0005] Currently, fields such as aerospace are beginning to pursue unified modeling languages ​​and tools for the requirements, design, and verification stages. Research on requirements modeling methods can be divided into three categories: (1) Extending graphical unified modeling languages ​​such as UML and SysML. (2) Extending graphical modeling languages ​​such as Simulink for synchronous data flows. (3) Requirements modeling methods in the form of restricted natural languages. After summarizing and analyzing the advantages and disadvantages of the three, Xu Heng et al. proposed a domain requirements modeling language MTRDL and extended the language to SysML to form a new requirements modeling method to carry out automatic flight system mode conversion requirements verification. This requirements modeling method links requirements, design, and verification in the system design process, but in the requirements modeling process, it only stays at the functional requirements modeling stage and does not conduct research on human factors requirements modeling.

[0006] The graphical modeling language SysML has greatly improved the ambiguity and vagueness inherent in text-based requirement descriptions and improved the consistency and accuracy of requirement understanding. However, current requirement modeling practices often focus on the structural and functional expression of the system, while neglecting to consider human behavior, ability limitations, and interaction requirements as intrinsic elements of system design. This has caused a gap between ergonomics and system engineering, forcing the design team to repeatedly backtrack and correct ergonomics design in the later design stages, greatly extending the project cycle and significantly increasing design costs. Summary of the invention

[0007] In order to solve the problem that the existing technical requirement modeling practice often focuses on the structure and functional expression of the system, but ignores the consideration of human behavior, ability limitations and interaction requirements as endogenous factors of system design, resulting in a gap between human factors engineering and system engineering, forcing the design team to repeatedly retrospectively correct the human factors design in the later design stage, greatly prolonging the project cycle and significantly increasing the design cost, the present invention proposes a model-based human factors analysis integrated modeling method, including:

[0008] Use the operational concept analysis method to establish an operational task list from the perspective of stakeholders;

[0009] Build task scenario use cases based on operational task lists and SysML modeling language;

[0010] Perform human factor task analysis based on the task scenario use cases, operation task lists and interaction relationships to identify human factor requirements related to the task;

[0011] Based on the SysML modeling language, a task, requirement and system mapping table is formed to obtain an integrated model of tasks and requirements;

[0012] The professional human factors analysis software is used to verify the satisfaction of the task and demand integration model, and the verified task and demand integration model is used as the human factors analysis integration model.

[0013] Optionally, the construction of a task scenario use case based on the operation task list and SysML modeling language includes:

[0014] Identify participants based on the operational task list;

[0015] Based on the operation task list and the participants, the human-computer interaction relationship of the participants is mined, and the mutual information theory in information entropy is used to mine the correlation relationship between the subsystems interacting with the participants;

[0016] The SysML modeling language is used to construct task scenario use cases based on the human-computer interaction relationship between participants and the association relationship between subsystems that interact with participants.

[0017] Optionally, constructing a task scenario use case using SysML modeling language based on the participants and the human-computer interaction relationship of the participants includes:

[0018] Define the actor model library using the block diagram in the SysML modeling language;

[0019] Use the use case diagram in the SysML modeling language to define the human-computer interaction relationship between participants;

[0020] A task scenario use case is constructed by a participant model library and the human-computer interaction relationship of the participants.

[0021] Optionally, mining the human-computer interaction relationship of the participants based on the operation task list and the participants, and using the mutual information theory in information entropy to mine the association relationship between the subsystems interacting with the participants, includes:

[0022] The operation object corresponding to the operation task is regarded as a system or subsystem, and the possible value of the system or subsystem is represented as an interval;

[0023] Calculate the interval entropy of the state of the system or subsystem based on the interval of each system or subsystem;

[0024] Calculate the joint entropy of any two system or subsystem states occurring together based on the intervals of each system or subsystem;

[0025] Calculate the mutual information between the arbitrary two systems based on the interval entropy of the system or subsystem state and the joint entropy of the joint occurrence of the arbitrary two system states;

[0026] Compare the mutual information between any two systems and / or subsystems with a set standard value; if the mutual information between any two systems or subsystems contains the set standard value, then there is an association relationship between the any two systems or subsystems; otherwise, there is no association relationship;

[0027] Wherein, the system includes subsystems.

[0028] Optionally, the interval entropy of the system or subsystem state is calculated as follows:

[0029]

[0030] Where H(X) is the interval entropy of the system or subsystem state, p i is the supremum of the probability that the system X takes the i-th value, n is the total number of values, and i is the ordinal number of the value.

[0031] Optionally, the joint entropy is calculated as follows:

[0032] H(X,Y)=[-∑ i,j p ij logp ij ,∑ i,j (1-p ij )log(1-p ij )]

[0033] Where H(X,Y) is the joint entropy; P ij It is the supremum of the probability that X and Y take the i-th and j-th values ​​at the same time;

[0034] Preferably, the mutual information between any two systems is calculated as follows:

[0035] I(X,Y)=[max(H(X)+H(Y)-H(X,Y)),min(H(X)+H(Y)-H(X,Y))]

[0036] Where H(X) and H(Y) are the interval entropies of system X and system Y, I(X,Y) is the mutual information of system X and system Y, and X and Y are the system serial numbers respectively.

[0037] Optionally, performing human factor task analysis based on the task scenario use case, the operation task list, and the interaction relationship to identify human factor requirements related to the task includes:

[0038] Based on the task scenario use case, the activity diagram in the SysML modeling language is used to define the running activities and interaction relationships in the task, and construct an expression task scenario;

[0039] Based on the expression of task scenarios, the human needs of participants are identified and defined using the requirements diagram in the SysML modeling language.

[0040] Optionally, the use of professional human factors analysis software to verify the satisfiability of the task and demand integration model, and using the verified task and demand integration model as the human factors analysis integration model, includes:

[0041] Use professional human factors analysis software to conduct multi-dimensional ergonomics evaluation, build objective functions based on ergonomics results to find the optimal solution, and verify whether the task and demand integration model meets human factors requirements;

[0042] If the results of the ergonomics evaluation meet the human factors requirements, the task and requirement integration model is used as the human factors analysis integration model. Otherwise, the task, requirement and system mapping table is further formed based on the SysML modeling language to obtain the task and requirement integration model to continue the ergonomics evaluation.

[0043] Optionally, forming a task, requirement and system mapping table based on the SysML modeling language to obtain a task and requirement integrated model includes:

[0044] Conduct an integrated analysis of tasks and requirements, and obtain a task-requirement refinement matrix and a system-requirement satisfaction matrix based on SysML modeling;

[0045] Based on the task-requirement refinement matrix and the system-requirement satisfaction matrix, the SysML modeling language is used to establish the task, requirement, and system mapping table to obtain an integrated model of tasks and requirements.

[0046] On the other hand, the present application also provides a model-based human factors analysis integrated modeling system, including:

[0047] A checklist building module for building an operational task checklist from a stakeholder perspective using an operational concept analysis approach;

[0048] Use case building module, used to build task scenario use cases based on the operational task list and SysML modeling language;

[0049] A human factors demand analysis module, used to perform human factors task analysis based on the task scenario use case, operation task list and interaction relationship, and identify human factors demand related to the task;

[0050] The initial model building module is used to form a task, requirement and system mapping table based on the SysML modeling language to obtain a task and requirement integrated model;

[0051] The verification module is used to verify the satisfaction of the task and demand integration model using professional human factor analysis software, and use the verified task and demand integration model as the human factor analysis integration model.

[0052] Optional, use case building blocks, including:

[0053] A participant determination submodule, for determining participants based on an operation task list;

[0054] A relationship mining submodule is used to mine the human-computer interaction relationship of the participants based on the operation task list and the participants, and to mine the association relationship between the subsystems interacting with the participants by using the mutual information theory in information entropy;

[0055] The use case construction submodule is used to construct task scenario use cases using the SysML modeling language based on participants and participant human-computer interaction relationships.

[0056] Optionally, the relationship mining submodule is specifically used for:

[0057] The operation object corresponding to the operation task is regarded as a system or subsystem, and the possible value of the system or subsystem is represented as an interval;

[0058] Calculate the interval entropy of the state of the system or subsystem based on the interval of each system or subsystem;

[0059] Calculate the joint entropy of any two system or subsystem states occurring together based on the intervals of each system or subsystem;

[0060] Calculate the mutual information between the arbitrary two systems based on the interval entropy of the system or subsystem state and the joint entropy of the joint occurrence of the arbitrary two system states;

[0061] Compare the mutual information between any two systems and / or subsystems with a set standard value; if the mutual information between any two systems or subsystems contains the set standard value, then there is an association relationship between the any two systems or subsystems; otherwise, there is no association relationship;

[0062] Wherein, the system comprises a subsystem;

[0063] Preferably, the interval entropy of the system or subsystem state is calculated as follows:

[0064]

[0065] Where H(X) is the interval entropy of the system or subsystem state, p i is the supremum of the probability that the system X takes the i-th value, n is the total number of values, and i is the ordinal number of the value;

[0066] Preferably, the joint entropy is calculated as follows:

[0067] H(X,Y)=[-∑ i,j p ij logp ij ,∑ i,j (1-p ij )log(1-p ij )]

[0068] Where H(X,Y) is the joint entropy; Pij It is the supremum of the probability that X and Y take the i-th and j-th values ​​at the same time;

[0069] Preferably, the mutual information between any two systems is calculated as follows:

[0070] I(X,Y)=[max(H(X)+H(Y)-H(X,Y)),min(H(X)+H(Y)-H(X,Y))]

[0071] Where H(X) and H(Y) are the interval entropies of system X and system Y, I(X,Y) is the mutual information of system X and system Y, and X and Y are the system serial numbers respectively.

[0072] Optional, human factors demand analysis module, specifically used for:

[0073] Based on the task scenario use case, the activity diagram in the SysML modeling language is used to define the running activities and interaction relationships in the task, and construct an expression task scenario;

[0074] Based on the expression of task scenarios, the human needs of participants are identified and defined using the requirements diagram in the SysML modeling language.

[0075] Optional, verification module, specifically used to:

[0076] Use professional human factors analysis software to conduct multi-dimensional ergonomics evaluation, build objective functions based on ergonomics results to find the optimal solution, and verify whether the task and demand integration model meets human factors requirements;

[0077] If the results of the ergonomics evaluation meet the human factors requirements, the task and requirement integration model is used as the human factors analysis integration model. Otherwise, the task, requirement and system mapping table is further formed based on the SysML modeling language to obtain the task and requirement integration model to continue the ergonomics evaluation.

[0078] Optional, initial model building module, specifically for:

[0079] Conduct an integrated analysis of tasks and requirements, and obtain a task-requirement refinement matrix and a system-requirement satisfaction matrix based on SysML modeling;

[0080] Based on the task-requirement refinement matrix and the system-requirement satisfaction matrix, the SysML modeling language is used to establish the task, requirement, and system mapping table to obtain an integrated model of tasks and requirements.

[0081] In another aspect, the present application further provides an electronic device, comprising: at least one processor and a memory; the memory and the processor are connected via a bus;

[0082] The memory is used to store one or more programs;

[0083] When the one or more programs are executed by the at least one processor, the model-based human factors analysis integrated modeling method as described above is implemented.

[0084] On the other hand, the present application also provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed, the model-based human factors analysis integrated modeling method as described above is implemented.

[0085] Compared with the prior art, the present invention has the following beneficial effects:

[0086] The present invention provides a model-based human factors analysis integrated modeling method, including: using an operation concept analysis method to establish an operation task list from the perspective of stakeholders; constructing a task scenario use case based on the operation task list and the SysML modeling language; performing human factors task analysis based on the task scenario use case, the operation task list and the interaction relationship, and identifying the human factors requirements related to the task; forming a task, requirement and system mapping table based on the SysML modeling language to obtain a task and requirement integrated model; using human factors professional analysis software to verify the satisfaction of the task and requirement integrated model, and using the verified task and requirement integrated model as a human factors analysis integrated model. The present invention performs human factors task analysis, considers human factors when designing a system, ensures that technology development is perfectly matched with the physiological, psychological and cognitive abilities of human operators, allows the design team to identify and solve potential human-computer interaction problems at an early stage, reduces the cost and risk of subsequent design changes, and thus improves the overall effectiveness of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] Figure 1 A flow chart of a model-based integrated modeling method for human factors analysis of the present invention;

[0088] Figure 2 A flow chart for integrated modeling of complex system human factors task and demand analysis of the present invention;

[0089] Figure 3 A diagram of participants in a lander extravehicular mission scenario of the present invention;

[0090] Figure 4 It is a participant diagram of the lander of the present invention;

[0091] Figure 5 This is a use case diagram of the lander extravehicular mission scenario of the present invention;

[0092] Figure 6 It is a human factors correlation diagram of astronauts and the hatch of the present invention;

[0093] Figure 7 This is a diagram of the lander's extravehicular activity of the present invention;

[0094] Figure 8 A schematic diagram of the human factors requirements for the lander to exit the cabin of the present invention;

[0095] Fig. 9 The lander extravehicular mission, requirements and system mapping diagram of the present invention;

[0096] Fig.10 A schematic diagram of a matrix for detailing the tasks and requirements of the present invention;

[0097] Fig.11 A schematic diagram of the system and requirements satisfaction matrix of the present invention;

[0098] Fig.12 The figure is a schematic diagram of the structure of an electronic device of the present invention. DETAILED DESCRIPTION

[0099] In view of the above limitations, it is urgent to explore a human factors modeling method to strengthen the intrinsic position of people in system design. Therefore, a model-based integrated modeling method for human factors analysis is proposed, which aims to fully consider human factors design in the early stage of system design and solve the problems of inconsistent expression, difficult tracking and verification of human factors requirements caused by traditional text-based delivery methods.

[0100] The MBSE method is used to analyze the human factors tasks and requirements of complex systems, and an extended sysml language is proposed to realize human factors task and requirement modeling, which closely links system engineering with human factors engineering. Human factors design constraints are fully considered in the early stage of system design to solve the problems of insufficient consideration of human factors issues in the early stage of complex system design and long iteration cycle of human factors issues.

[0101] In order to better understand the present invention, the content of the present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0102] Example 1

[0103] A model-based integrated modeling approach for human factors analysis, such as Figure 1 As shown, including:

[0104] Step S1: Use the operational concept analysis method to establish an operational task list from the perspective of stakeholders;

[0105] Step S2: construct task scenario use cases based on the operation task list and SysML modeling language;

[0106] Step S3: Performing human factor task analysis based on the task scenario use case, operation task list and interaction relationship to identify human factor requirements related to the task;

[0107] Step S4: Form a task, requirement and system mapping table based on the SysML modeling language to obtain a task and requirement integrated model;

[0108] Step S5: Use professional human factor analysis software to verify the satisfiability of the task and demand integration model, and use the verified task and demand integration model as the human factor analysis integration model.

[0109] Through mapping analysis of MBSE and human-centered design activities, a modeling method based on SysML to describe the integration of human factors tasks and requirements analysis processes is proposed. The basic steps of this method are as follows:

[0110] Step S1: Use the operational concept analysis method to establish an operational task list from the perspective of stakeholders, including:

[0111] Define the task scenario list, that is, the operational task list.

[0112] The concept of operations analysis method is used to establish a panoramic view of the system operation tasks from the perspective of stakeholders, clearly depicting the goals, main operation processes and risk management of complex systems. The concept of operations analysis method (Concept of Operations, referred to as CONOPS) is a systematic methodology used to describe and define the operating framework of a system in its expected operating environment. It outlines the overall goals, operating methods, participants (including various stakeholders), key processes, information flows and interactions between the system and the external environment from a macro perspective. It is mainly used in the early stages of system design and development to ensure that all stakeholders have a common understanding of the system's goals, capabilities and usage.

[0113] The present invention defines the mission panorama as including four categories: normal scenario, emergency scenario, fault scenario, and special scenario. Different analyses are conducted on the mission scenarios according to the system goals and scenario characteristics. Normal scenario refers to the orderly operation of a complex system according to the plan, the preset time, resources, and processes; emergency scenario refers to the need for immediate action to maintain order or restore normality when a complex system faces an emergency or crisis; fault scenario refers to the inability of a complex system to work normally or performance degradation during operation; special scenario refers to a detailed situation or environment set for a specific purpose, demand, or goal.

[0114] Step S2: Construct task scenario use cases based on the operational task list and SysML modeling language, including:

[0115] Identify participants based on the operational task list;

[0116] Based on the operation task list and the participants, the human-computer interaction relationship of the participants is mined, and the mutual information theory in information entropy is used to mine the correlation relationship between the subsystems interacting with the participants;

[0117] The SysML modeling language is used to construct task scenario use cases based on the human-computer interaction relationship between participants and the association relationship between subsystems that interact with participants.

[0118] Furthermore, based on the human-computer interaction relationship between participants and participants and the association relationship between subsystems interacting with participants, the SysML modeling language is used to construct task scenario use cases, including:

[0119] Define the actor model library using the block diagram in the SysML modeling language;

[0120] Use the use case diagram in the SysML modeling language to define the human-computer interaction relationship between participants;

[0121] A task scenario use case is constructed by a participant model library and the human-computer interaction relationship of the participants.

[0122] Furthermore, based on the operation task list and the participants, the human-computer interaction relationship of the participants is mined, and the mutual information theory in information entropy is used to mine the association relationship between the subsystems interacting with the participants, including:

[0123] The operation object corresponding to the operation task is regarded as a system or subsystem, and the possible value of the system or subsystem is represented as an interval;

[0124] Calculate the interval entropy of the state of the system or subsystem based on the interval of each system or subsystem;

[0125] Calculate the joint entropy of any two system or subsystem states occurring together based on the intervals of each system or subsystem;

[0126] Calculate the mutual information between the arbitrary two systems based on the interval entropy of the system or subsystem state and the joint entropy of the joint occurrence of the arbitrary two system states;

[0127] Compare the mutual information between any two systems and / or subsystems with a set standard value; if the mutual information between any two systems or subsystems contains the set standard value, then there is an association relationship between the any two systems or subsystems; otherwise, there is no association relationship;

[0128] Wherein, the system includes subsystems.

[0129] Preferably, the interval entropy of the system or subsystem state is calculated as follows:

[0130]

[0131] Where H(X) is the interval entropy of the system or subsystem state, p iis the supremum of the probability that the system X takes the i-th value, n is the total number of values, and i is the ordinal number of the value;

[0132] Preferably, the joint entropy is calculated as follows:

[0133] H(X,Y)=[-∑ i,j p ij logp ij ,∑ i,j (1-p ij )log(1-p ij )]

[0134] Where H(X,Y) is the joint entropy; P ij It is the supremum of the probability that X and Y take the i-th and j-th values ​​at the same time;

[0135] Preferably, the mutual information between any two systems is calculated as follows:

[0136] I(X,Y)=[max(H(X)+H(Y)-H(X,Y)),min(H(X)+H(Y)-H(X,Y))]

[0137] Where H(X) and H(Y) are the interval entropies of system X and system Y, I(X,Y) is the mutual information of system X and system Y, and X and Y are the system serial numbers respectively.

[0138] Step S2 specifically includes:

[0139] (1) Define the participants in the task scenario.

[0140] According to the task scenario list, the participants involved in the system are analyzed, including stakeholders and the equipment required to perform the task, and the model library of the relevant parties is defined using the block definition diagram. At this time, people are no longer just triggers (black boxes) in the system, but need to be expanded. We must fully consider people's capabilities and limitations, extract the model that interacts with people from the full system model, and focus on the human-computer interface that directly interacts with people, including systems, subsystems, single machines, and components.

[0141] (2) Construct task scenario use cases.

[0142] Based on the defined task scenario list and task scenario participants, the task scenario is captured using a use case, and a use case diagram is constructed to determine the human-computer interaction relationship of the participants. With the task as a bridge, the relationship between the design parameters of the human-system or subsystem-subsystem is established, and the matching between the human-system-task is fully considered. The present invention proposes to use the mutual information theory in information entropy to fully explore whether there is a relationship between the subsystems in the complex system in an objective quantitative way. Due to the limitations of high uncertainty and small amount of data in manned spaceflight data, interval algebra is used to convert the mutual information value from an exact value to a probability distribution interval value. The calculation process is as follows:

[0143] First, the possible values ​​of the system are expressed as an interval.

[0144] Then, the interval entropy H(X) of the system state is calculated.

[0145]

[0146] p i is the supremum of the probability that the system X takes the i-th value, 1-p i It is the infimum.

[0147] Then the joint entropy of the joint occurrence of system X state and system Y state is calculated.

[0148] H(X,Y)=[-∑ i,j p ij logpij,∑ i,j (1-p ij )log(1-p ij )]

[0149] P ij is the supremum of the probability that X and Y take the i-th and j-th values ​​at the same time, and X and Y are the system serial numbers.

[0150] Finally, the mutual information between the state of system X and the state of system Y is calculated, which can be determined by the difference between the joint entropy of X and Y and the individual entropy to determine the upper and lower bounds of the interval:

[0151] I(X,Y)=[max(H(X)+H(Y)-H(X,Y)),min(H(X)+H(Y)-H(X,Y))]

[0152] The calculated entropy value is then compared with the standard value i set by the expert. If the calculated entropy value I interval contains the standard value i, there is a correlation between the two systems. The task is then associated with the subsystem defined in the block diagram through the use case diagram to facilitate the subsequent human factors demand analysis.

[0153] (3) Express the task scenario.

[0154] Based on the defined use case diagram, the activity diagram is used to express the operation activities and interaction relationships in the entire task, and human-factor task analysis is carried out. In the process of expressing tasks, the hierarchical task analysis method is used to decompose the tasks hierarchically into directly executable meta-tasks, map the interaction between people and the system from the smallest task unit, fully explore the human-factor design constraints, and through iterative human-centered design activities, the operation tasks are gradually improved and clarified as the system design is refined.

[0155] Step S3: Performing human factor task analysis based on the task scenario use case, operation task list and interaction relationship to identify human factor requirements related to the task, including:

[0156] Based on the task scenario use case, the activity diagram in the SysML modeling language is used to define the running activities and interaction relationships in the task, and construct an expression task scenario;

[0157] Based on the expression of task scenarios, the human needs of participants are identified and defined using the requirements diagram in the SysML modeling language.

[0158] Step S3 specifically includes: identifying human factors requirements based on task scenarios.

[0159] Based on the constructed task activity diagram, identify and define the task-related human factors requirements. Human factors requirements analysis needs to match the system requirements analysis process, and is continuously refined and improved with the top-down decomposition and iteration of system design, and finally forms a complete complex system human factors requirements table. The present invention defines that the human factors requirements table includes requirements hierarchy, requirement number, requirement name, requirement description, etc.

[0160] Step S4: Based on the SysML modeling language, a task, requirement and system mapping table is formed to obtain a task and requirement integrated model, including:

[0161] Conduct an integrated analysis of tasks and requirements, and obtain a task-requirement refinement matrix and a system-requirement satisfaction matrix based on SysML modeling;

[0162] Based on the task-requirement refinement matrix and the system-requirement satisfaction matrix, the SysML modeling language is used to establish the task, requirement, and system mapping table to obtain an integrated model of tasks and requirements.

[0163] Step S4 specifically includes:

[0164] Establish traceability relationships among scenario tasks, systems, and requirements.

[0165] The design of complex systems is in a process of continuous iteration and refinement. When the task scenario changes, there will be significant changes between the human factors design requirements and the system. It is necessary to establish a dynamic traceability relationship between the scenario tasks, systems and requirements to meet the requirements of quickly identifying the affected related systems and requirements. The present invention proposes to establish a task, requirement and system mapping table based on the SysML modeling language, and use the task-requirement refinement matrix and the system-requirement satisfaction matrix to construct a dynamic traceability relationship between the three. The system here refers to the design goal, which can be called a product in a narrow sense and a system in a broad sense. For example, the lunar suit, the operating task is to wear the lunar suit. When designing the lunar suit, it is necessary to consider the convenience of people wearing the lunar suit to ensure the smooth completion of the task of wearing the lunar suit.

[0166] Step S5: using professional human factor analysis software to verify the satisfiability of the task and demand integration model, and using the verified task and demand integration model as the human factor analysis integration model, including:

[0167] Use professional human factors analysis software to conduct multi-dimensional ergonomics evaluation, build objective functions based on ergonomics results to find the optimal solution, and verify whether the task and demand integration model meets human factors requirements;

[0168] If the results of the ergonomics evaluation meet the human factors requirements, the task and requirement integration model is used as the human factors analysis integration model. Otherwise, the task, requirement and system mapping table is further formed based on the SysML modeling language to obtain the task and requirement integration model to continue the ergonomics evaluation.

[0169] Step S5 specifically includes:

[0170] Verify human needs.

[0171] Unlike SysML, which integrates MATLAB, Modelica, etc. to realize mechanical dynamics or thermal simulation analysis, the current human factors professional analysis software (such as JACK, IMPRINT, HPMSS, etc.) is independent of the MBSE modeling tool system, so the verification of human factors needs can only be analyzed separately. The present invention proposes to first use advanced human factors professional analysis software to conduct a comprehensive and in-depth analysis and verification of the human factors needs proposed in the early stage of system design. This type of software usually integrates evaluation tools in multiple dimensions such as human-computer interaction, workload, cognitive load and user interface friendliness, and can scientifically evaluate whether the design scheme conforms to ergonomic principles and whether it can meet the user's actual operating habits and psychological expectations.

[0172] After completing the software verification of human factors requirements, a relationship function between comfort and joint angle is constructed. The objective function is optimized with the help of genetic algorithms to find the best matching value of comfort and joint angle. Finally, through manual intervention, the verified human factors requirements are accurately mapped and associated with the requirements model of model-based system engineering.

[0173] Example 2

[0174] In order to further explain the integrated modeling method proposed in the present invention, human factors task and demand analysis modeling is carried out for the extravehicular mission of the manned lunar lander in the Artemis program. The Artemis program is an international space exploration project led by the National Aeronautics and Space Administration (NASA). Its core goal is to send astronauts back to the moon and establish a foundation for long-term residence, paving the way for future exploration of Mars. The extravehicular mission of the manned lunar lander, as a vital part of the entire plan, is directly related to the safety of the astronauts, the smooth execution of the mission, and the effectiveness of scientific exploration. Therefore, the consideration of human factors is particularly critical. Figure 2 As shown in the figure, the operational concept analysis method is used to complete the mission scenario and scenario participant definition for the manned lunar lander extravehicular mission in the Artemis program. Then, the mission scenario is established based on the SysML modeling language to carry out human factors task and human factors demand analysis, and finally the human factors demand is verified with the help of professional analysis software. In the figure, block represents the block definition diagram, Package represents the package diagram, Legend represents the legend, and Satisfy represents the satisfy relationship.

[0175] 1. Define the task scenario list

[0176] From the perspective of astronauts, the operation concept analysis method is used to establish an operation task list, as shown in Table 1, which includes normal scenarios, emergency scenarios, fault scenarios, and special scenarios, and establishes the task operation process in each scenario to form a panoramic view of the mission scenario. For example, the normal scenario extravehicular task list means that the astronauts smoothly transfer from the inside of the lander to the lunar surface as planned, and need to perform the tasks of wearing lunar suits, going out of the cabin through the lock, opening the cabin door, going out of the cabin door, and going down the gangway in sequence.

[0177] Table 1 List of lander extravehicular missions

[0178]

[0179]

[0180] 2. Define the mission scenario participants

[0181] According to the mission scenario list defined in 1, the scenario participants of the lander extravehicular mission are defined, including astronauts, landers, and lunar suits. The block diagram in the SysML modeling language is used to define the model library of related parties, such as Figure 3As shown in Figure 2. The astronaut attributes are expanded to more comprehensively represent the capabilities and constraints of people. At this time, we only need to focus on the systems, subsystems, single machines and components that interact with astronauts. Figure 4 As shown, the subsystems of the lander interacting with astronauts include structural mechanisms, GNC, environmental control and life support, electronic information, crew equipment and products, etc.

[0182] 3. Build mission scenario use cases

[0183] Based on the mission scenario list and participants defined in 1 and 2, use cases are captured for the extravehicular mission scenario, such as Figure 5 As shown in the figure, the use case diagram in the SysML modeling language is used to define the human-computer interaction relationship of the participants, and the correlation between the astronaut's capabilities and the system design parameters is established by the mission. In the process, the mutual information entropy is used to fully explore whether there is a correlation between the subsystems in the complex system.

[0184] First, the possible values ​​of whether to wear a lunar suit and whether to open the hatch are expressed as intervals, which are [0 (not wearing a lunar suit), 1 (wearing a lunar suit)]; [0 (not opening the hatch), 1 (opening the hatch)]. Then, the interval entropy of the two subsystems is calculated respectively, H (wearing a lunar suit) = [-1, 1]; H (opening the hatch) = [-1, 1]. Then, the joint entropy of the two systems is calculated, and the interaction scenarios between the two subsystems are: {wearing a lunar suit, opening the hatch; wearing a lunar suit, not opening the hatch; not wearing a lunar suit, not opening the hatch;}, H (wearing a lunar suit, opening the hatch) = [-0.624, -0.352]. Finally, the mutual information of the two systems is calculated I (wearing a lunar suit, opening the hatch) = [1.648, 2.624]

[0185] The calculation of mutual information entropy shows that the standard value 1 is within the range, indicating that astronauts must wear lunar suits to perform the hatch door exit mission. Therefore, the unlocking handle task associates the astronauts / lunar suits with the hatch door parameters, indicating that the human factors design constraints of the human / suit system must be considered when designing the hatch, such as Figure 6 shown.

[0186] 4. Express the task scenario

[0187] According to the scenario use case defined in 3, the activity logic and interaction relationship in the extravehicular mission are defined using the activity diagram in the SysML modeling language, such as Figure 7 As shown in the figure, the extravehicular mission is executed in sequence according to the subtasks of "wearing lunar suit - passing through the hatch - opening the hatch - exiting the hatch - going down the gangway". Each subtask is further subdivided into many meta-tasks. For example, the extravehicular lock task can be further subdivided into "checking the initial status of the equipment - checking the air tightness of the suit - depressurizing - switching the suit to autonomous mode". Starting from the meta-tasks, the human factors requirements of the manned lunar lander extravehicular mission in the Artemis program are fully mapped one by one.

[0188] 5. Identify human needs based on scenarios

[0189] According to the extravehicular mission activity diagram constructed in 4, the requirements diagram in the SysML modeling language is used to identify and define the human factors requirements of the lander and the lunar suit, and form a human factors requirements table for system design. The human factors requirements analysis is matched with the system requirements analysis process, and is continuously refined and improved with the top-down decomposition and iteration of the system design. Figure 8 As shown in the figure, the unlocking handle mission requires that the size of the lander door handle should be convenient for astronauts to grasp and operate, and the unlocking force should meet the astronauts' operation requirements. At the same time, the unlocking handle mission requires that the lunar suit's operating capabilities meet the requirements. The unlocking handle meta-task completely maps the human factors design requirements for direct interaction with people in the lander's extravehicular mission in the Artemis program.

[0190] 6. Establish traceability between scenario tasks, systems and requirements

[0191] Establish a task, requirement, and system mapping table through the task and requirement refinement matrix and the system and requirement satisfaction matrix, such as Fig. 9 , Fig.10 and Fig.11 As shown, when the mission scenario changes, quickly respond to identify the affected systems and requirements.

[0192] 7. Verify human needs

[0193] After using professional human factors analysis tools such as SoErgo to verify the human factors requirements of extravehicular missions, such as accessibility, visibility, and workload, a correlation function between comfort and joint angle is constructed. This function is generally normally distributed. Then, the objective function is optimized with the help of genetic algorithms to obtain the best matching value between comfort and joint angle.

[0194] Taking the example of exiting the cabin in a bent-over posture, firstly, based on the SoErgo simulation data, the functional relationship between comfort and joint angle is constructed as follows:

[0195]

[0196] μ is the mean of the lumbar joint angles, and σ is the standard deviation.

[0197] Then, the objective function is optimized with the help of genetic algorithm. First, the population is initialized and the initial population is randomly generated with a size of 50. Each individual represents a lumbar joint angle. Then the "fitness evaluation-selection-crossover-mutation-update population" steps are iterated repeatedly until the termination condition is met. In this case, the mean μ = 30°; the standard deviation σ = 10°; the initial population size is 50; and the maximum number of iterations is 1000. Finally, the optimal solution is: the lumbar joint angle corresponding to the maximum comfort is 35°; the lumbar joint angle corresponding to the minimum comfort is 15°.

[0198] Afterwards, the requirement model is manually associated with the test cases to achieve traceable verification of the requirements.

[0199] Example 3

[0200] The present invention based on the same inventive concept also provides a model-based human factors analysis integrated modeling system, comprising:

[0201] A checklist building module for building an operational task checklist from a stakeholder perspective using an operational concept analysis approach;

[0202] Use case building module, used to build task scenario use cases based on the operational task list and SysML modeling language;

[0203] A human factors demand analysis module, used to perform human factors task analysis based on the task scenario use case, operation task list and interaction relationship, and identify human factors demand related to the task;

[0204] The initial model building module is used to form a task, requirement and system mapping table based on the SysML modeling language to obtain a task and requirement integrated model;

[0205] The verification module is used to verify the satisfaction of the task and demand integration model using professional human factor analysis software, and use the verified task and demand integration model as the human factor analysis integration model.

[0206] Optional, use case building blocks, including:

[0207] A participant determination submodule, for determining participants based on an operation task list;

[0208] A relationship mining submodule is used to mine the human-computer interaction relationship of the participants based on the operation task list and the participants, and to mine the association relationship between the subsystems interacting with the participants by using the mutual information theory in information entropy;

[0209] The use case construction submodule is used to construct task scenario use cases using the SysML modeling language based on participants and participant human-computer interaction relationships.

[0210] Optionally, the relationship mining submodule is specifically used for:

[0211] The operation object corresponding to the operation task is regarded as a system or subsystem, and the possible value of the system or subsystem is represented as an interval;

[0212] Calculate the interval entropy of the state of the system or subsystem based on the interval of each system or subsystem;

[0213] Calculate the joint entropy of any two system or subsystem states occurring together based on the intervals of each system or subsystem;

[0214] Calculate the mutual information between the arbitrary two systems based on the interval entropy of the system or subsystem state and the joint entropy of the joint occurrence of the arbitrary two system states;

[0215] Compare the mutual information between any two systems and / or subsystems with a set standard value; if the mutual information between any two systems or subsystems contains the set standard value, then there is an association relationship between the any two systems or subsystems; otherwise, there is no association relationship;

[0216] Wherein, the system comprises a subsystem;

[0217] Preferably, the interval entropy of the system or subsystem state is calculated as follows:

[0218]

[0219] Where H(X) is the interval entropy of the system or subsystem state, p i is the supremum of the probability that the system X takes the i-th value;

[0220] Preferably, the joint entropy is calculated as follows:

[0221] H(X,Y)=[-∑ i,j p ij logp ij ,∑ i,j (1-p ij )log(1-p ij )]

[0222] Where H(X,Y) is the joint entropy; P ij It is the supremum of the probability that X and Y take the i-th and j-th values ​​at the same time;

[0223] Preferably, the mutual information between any two systems is calculated as follows:

[0224] I(X,Y)=[max(H(X)+H(Y)-H(X,Y)),min(H(X)+H(Y)-H(X,Y))]

[0225] Where H(X) and H(Y) are the interval entropies of system X and system Y, I(X,Y) is the mutual information of system X and system Y, and X and Y are the system serial numbers respectively.

[0226] Optional, human factors demand analysis module, specifically used for:

[0227] Based on the task scenario use case, the activity diagram in the SysML modeling language is used to define the running activities and interaction relationships in the task, and construct an expression task scenario;

[0228] Based on the expression of task scenarios, the human needs of participants are identified and defined using the requirements diagram in the SysML modeling language.

[0229] Optional, verification module, specifically used to:

[0230] Use professional human factors analysis software to conduct multi-dimensional ergonomics evaluation, build objective functions based on ergonomics results to find the optimal solution, and verify whether the task and demand integration model meets human factors requirements;

[0231] If the results of the ergonomics evaluation meet the human factors requirements, the task and requirement integration model is used as the human factors analysis integration model. Otherwise, the task, requirement and system mapping table is further formed based on the SysML modeling language to obtain the task and requirement integration model to continue the ergonomics evaluation.

[0232] Optional, initial model building module, specifically for:

[0233] Conduct an integrated analysis of tasks and requirements, and obtain a task-requirement refinement matrix and a system-requirement satisfaction matrix based on SysML modeling;

[0234] Based on the task-requirement refinement matrix and the system-requirement satisfaction matrix, the SysML modeling language is used to establish the task, requirement, and system mapping table to obtain an integrated model of tasks and requirements.

[0235] Example 4

[0236] like Fig.12 As shown, the present invention also provides an electronic device, which may be a computer device, a single-chip device, an intelligent mobile device, etc. The electronic device in this embodiment may include a processor, a memory, a transceiver component, etc. The memory, the processor, and the transceiver component are connected via a bus; the memory may be used to store an execution program, and an exemplary execution program may include instructions; the processor is used to execute the instructions stored in the memory. The memory may also be used to store data, which may be called and / or modified when the instructions are executed.

[0237] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. It is the computing core and control core of the terminal, which is suitable for implementing one or more instructions, specifically suitable for loading and executing one or more instructions in a storage medium to implement the corresponding method flow or corresponding functions, so as to implement the steps of a model-based integrated modeling method for human factors analysis in the above embodiment.

[0238] Example 5

[0239] Based on the same inventive concept, the present invention also provides a readable storage medium, specifically an electronic device readable storage medium (Memory), which is a memory device in an electronic device for storing programs and data. It can be understood that the storage medium here can include both built-in storage media in electronic devices and, of course, extended storage media supported by electronic devices. The storage medium provides a storage space, which stores the operating system of the terminal. In addition, one or more instructions suitable for being loaded and executed by a processor are also stored in the storage space, and these instructions can be one or more execution programs (including program codes). It should be noted that the storage medium here can be a high-speed RAM memory or a non-volatile memory, such as at least one disk memory. The processor loads and executes one or more instructions stored in the storage medium, which can implement the steps of a model-based integrated modeling method for human factors analysis in the above embodiment.

[0240] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0241] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0242] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0243] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0244] The above are merely embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention are included in the scope of the claims of the present invention to be approved.

Claims

1. A model-based integrated modeling method for human factors analysis, characterized in that: include: Use the operational concept analysis method to establish an operational task list from the perspective of stakeholders; Build task scenario use cases based on operational task lists and SysML modeling language; Perform human factor task analysis based on the task scenario use cases, operation task lists and interaction relationships to identify human factor requirements related to the task; Based on the SysML modeling language, a task, requirement and system mapping table is formed to obtain an integrated model of tasks and requirements; The professional human factors analysis software is used to verify the satisfaction of the task and demand integration model, and the verified task and demand integration model is used as the human factors analysis integration model.

2. The method according to claim 1, characterized in that The task scenario use case is constructed based on the operation task list and SysML modeling language, including: Identify participants based on the operational task list; Based on the operation task list and the participants, the human-computer interaction relationship of the participants is mined, and the mutual information theory in information entropy is used to mine the correlation relationship between the subsystems interacting with the participants; The SysML modeling language is used to construct task scenario use cases based on the relationships among participants, human-computer interaction relationships among participants, and the associations among subsystems that interact with participants.

3. The method according to claim 2, characterized in that The use case of constructing a task scenario using the SysML modeling language based on the participants and the human-computer interaction relationship of the participants includes: Define the actor model library using the block diagram in the SysML modeling language; Use the use case diagram in the SysML modeling language to define the human-computer interaction relationship between participants; A task scenario use case is constructed by a participant model library and the human-computer interaction relationship of the participants.

4. The method according to claim 2, characterized in that The mutual information theory in information entropy is used to mine the association between the subsystems interacting with the participants, including: The operation object corresponding to the operation task is regarded as a system or subsystem, and the possible value of the system or subsystem is represented as an interval; Calculate the interval entropy of the state of the system or subsystem based on the interval of each system or subsystem; Calculate the joint entropy of any two system or subsystem states occurring together based on the intervals of each system or subsystem; Based on the interval entropy of the system or subsystem state and the joint occurrence of any two system states Joint entropy calculation of the mutual information between any two systems; Compare the mutual information between any two systems and / or subsystems with a set standard value; if the mutual information between any two systems or subsystems contains the set standard value, then there is an association relationship between the any two systems or subsystems; otherwise, there is no association relationship; Wherein, the system comprises a subsystem; Preferably, the interval entropy of the system or subsystem state is calculated as follows: Where H(X) is the interval entropy of the system or subsystem state, p i is the supremum of the probability that the system X takes the i-th value, n is the total number of values, and i is the ordinal number of the value; Preferably, the joint entropy is calculated as follows: H(X,Y)=[-∑ i,j p ij logp ij ,∑ i,j (1-p ij )log(1-p ij )] Where H(X,Y) is the joint entropy; P ij It is the supremum of the probability that X and Y take the i-th and j-th values ​​at the same time; Preferably, the mutual information between any two systems is calculated as follows: I(X,Y)=[max(H(X)+H(Y)-H(X,Y)),min(H(X)+H(Y)-H(X,Y))] Where H(X) and H(Y) are the interval entropies of system X and system Y, I(X,Y) is the mutual information of system X and system Y, and X and Y are the system serial numbers respectively.

5. The method according to claim 1, characterized in that The human factors task analysis is performed based on the task scenario use case, operation task list and interaction relationship to identify the human factors requirements related to the task, including: Based on the task scenario use case, the activity diagram in the SysML modeling language is used to define the running activities and interaction relationships in the task, and construct an expression task scenario; Based on the expression of task scenarios, the human needs of participants are identified and defined using the requirements diagram in the SysML modeling language.

6. The method according to claim 1, characterized in that The use of professional human factors analysis software to verify the satisfiability of the task and demand integration model, and using the verified task and demand integration model as the human factors analysis integration model, includes: Use professional human factors analysis software to conduct multi-dimensional ergonomics evaluation, build an objective function based on the results of ergonomics evaluation to find the optimal solution, and verify whether the task and demand integration model meets the human factors requirements; If the results of the ergonomics evaluation meet the human factors requirements, the task and requirement integration model is used as the human factors analysis integration model. Otherwise, the task, requirement and system mapping table is further formed based on the SysML modeling language to obtain the task and requirement integration model to continue the ergonomics evaluation.

7. The method according to claim 1, characterized in that The task, requirement and system mapping table is formed based on the SysML modeling language to obtain a task and requirement integrated model, including: Conduct an integrated analysis of tasks and requirements, and obtain a task-requirement refinement matrix and a system-requirement satisfaction matrix based on SysML modeling; Based on the task-requirement refinement matrix and the system-requirement satisfaction matrix, the SysML modeling language is used to establish the task, requirement, and system mapping table to obtain an integrated model of tasks and requirements.

8. A model-based integrated human factors analysis modeling system, characterized in that: include: A checklist building module for building an operational task checklist from a stakeholder perspective using an operational concept analysis approach; Use case building module, used to build task scenario use cases based on the operational task list and SysML modeling language; A human factors demand analysis module, used to perform human factors task analysis based on the task scenario use case, operation task list and interaction relationship, and identify human factors demand related to the task; The initial model building module is used to form a task, requirement and system mapping table based on the SysML modeling language to obtain a task and requirement integrated model; The verification module is used to verify the satisfaction of the task and demand integration model using professional human factor analysis software, and use the verified task and demand integration model as the human factor analysis integration model.

9. An electronic device, characterized in that: include: at least one processor and memory; The memory and the processor are connected via a bus; The memory is used to store one or more programs; When the one or more programs are executed by the at least one processor, a model-based human factors analysis integrated modeling method as described in any one of claims 1 to 7 is implemented.

10. A readable storage medium, characterized in that: An execution program is stored thereon, and when the execution program is executed, a model-based human factors analysis integrated modeling method as described in any one of claims 1 to 7 is implemented.

Images