Aero-engine demand analysis method and system based on graphical modeling language
Through graphical modeling language, aero engine life cycle and usage scenarios are constructed, system boundaries and interactive activities are identified, requirements are defined, and the problem of incomplete demand capture in the aero engine field is solved, and the efficiency improvement and standardization of demand analysis is achieved, and the efficiency of demand analysis is improved and standardized, and the circumvention is avoided. The problem of long iteration cycle under the traditional model is achieved.
Patent Information
- Application Number
- CN202411062232.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-05
- Publication Date
- 2024-11-29
AI Technical Summary
The field of aero engines has been used in system engineering and model-based system engineering technology late, resulting in incomplete demand capture, many coordination times and long iteration cycles.
Using aero engine requirements analysis method based on graphical modeling language, the engine life cycle stage and usage scenarios are constructed through tools such as state machine diagrams, use case diagrams, internal block diagrams, and activity diagrams, identify system boundaries and stakeholders, and analyze interactions. Activities, define functional and non-functional requirements, form a demand map, and improve the integrity and rationality of demand.
Effectively improves the efficiency and integrity of aircraft engine demand analysis, avoids the problems of incompleteness of demand identification and long iteration cycle under the traditional document-based model, is highly standardized and operable, is easy to promote and apply, and has good economic benefits. and practical engineering application value.
Smart Images

Figure CN119047076A_ABST
Abstract
Description
Technical Field
[0001] The invention relates to the technical field of aircraft engine system engineering demand development, and discloses an aircraft engine demand analysis method and system based on a graphical modeling language. Background Art
[0002] Model-based systems engineering (MBSE) is a forward design method that uses standardized modeling technology to replace the traditional R&D model based on document-based systems engineering. It uses a unified multi-architecture perspective of system, domain, project planning and lifecycle management, including a set of models such as requirements, functions, logic, physics, architecture and verification as an integrated R&D framework to achieve dynamic association of data and knowledge within the life cycle that can be verified, traced and shared across domains of R&D information, and then runs through the entire life cycle of the system from conceptual planning, engineering development, to scrapping and updating.
[0003] Unified modeling language is one of the three pillars of model-based systems engineering (MBSE). For example, SysML modeling language promoted by INOSE and OMG is mainly used to solve the effective communication about system requirements and design between various teams and disciplines in system engineering, so as to improve the quality and efficiency of system engineering process. SysML modeling language can be used for different teams and personnel, and describe any discipline, so that project personnel can use a unified method to describe the system they are responsible for, solving the problem of cross-disciplinary and cross-departmental communication.
[0004] Based on system engineering and system modeling languages, developed countries such as Europe and the United States have developed modeling methods for different complex systems. For example, the OOSEM modeling method launched by Lockheed Martin and the Software Association, the MagicGrid modeling method launched by Dassault Aviation of France, and the Harmony-SE modeling method launched by IBM can effectively guide the system requirement analysis, architecture design, trade-off analysis and other work of different products.
[0005] Due to the complexity of spacecraft missions and systems, China has taken the lead in launching a model-based development model in the aerospace field, and has formed modeling processes and methods in specific fields, effectively improving the quality and efficiency of aerospace model development. However, due to the late application of forward development of system engineering and model-based system engineering (MBSE) technology in the field of aero-engines in my country, the model-based development methods and modeling languages are not fully mastered. The current demand capture analysis of aero-engines still mainly relies on a document-based coordination model with users. Experience-based demand analysis will bring great risks to the integrity of engine system requirements. Summary of the invention
[0006] The purpose of the present invention is to provide an aircraft engine demand analysis method and system based on a graphical modeling language, which can effectively support the demand analysis in the early stage of aircraft engine research and development and improve the integrity and rationality of the demand; and can avoid the problems of incomplete demand identification, high coordination times and long iteration cycle in the traditional document-based aircraft engine demand capture mode, and has high standardization and operability.
[0007] In order to achieve the above technical effects, the technical solution adopted by the present invention is:
[0008] The aircraft engine demand analysis method based on graphical modeling language includes:
[0009] According to the life cycle of the engine from delivery to scrapping, a complete aircraft engine life cycle stage is constructed, and the engine life cycle stage analysis view is constructed using a state machine diagram;
[0010] Construct usage scenarios for each life cycle stage of the engine, divide the usage scenarios for each life cycle stage into multiple main scenarios, and use use cases to express each main scenario and the sub-scenario contained in the corresponding main scenario; the sub-scenario includes normal use sub-scenario and abnormal sub-scenario; the abnormal sub-scenario is obtained through analysis of three dimensions: external environment abnormality, aircraft input abnormality, and engine abnormality;
[0011] Analyze each usage scenario one by one, and use the internal block diagram to construct the engine and stakeholder identification view under the usage scenario. The engine and stakeholders in the identification view are expressed by blocks;
[0012] Taking the engine as the center, the substances, energy or information interacting between the engine and the stakeholders are analyzed in the black box state. The interactions between the blocks of the identification view are associated through connectors, and corresponding project flows are added to the connectors to express the names and directions of the interacting substances, energy or information.
[0013] Based on the constructed usage scenario, an activity diagram is used to construct a view of the interactive activity analysis of the engine usage scenario. The identified stakeholders are associated with the activity diagram through swimlanes. The activity diagram includes multiple activities and control flows and material flows between activities. According to the scenario goals to be achieved by the usage scenario, the corresponding responses and actions of the engine and stakeholders are analyzed through activities, control flows, and material flows to complete the construction of the interactive activity view of the engine usage scenario.
[0014] Carry out the definition of functional and non-functional requirements for a single scenario, and determine the activities that fall into the engine swim lane as the functional requirements of the engine;
[0015] Complete the definition of activities, functional requirements and non-functional requirements for all single scenarios, and use the requirement graph to construct a view of affinity analysis of requirements for all engine usage scenarios; then incorporate all requirements identified for each single scenario into the requirement graph, and perform affinity through the classification framework of functional requirements, interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements, and finally form the engine usage scenario requirements based on the requirement graph.
[0016] Furthermore, the aircraft engine life cycle stages include transportation, storage, installation, storage, combat use, maintenance, repair and scrapping.
[0017] Furthermore, the stakeholders include users, maintenance personnel and interactive systems.
[0018] Furthermore, the non-functional requirements include interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements.
[0019] In order to achieve the above technical effects, the present invention also provides an aircraft engine demand analysis system based on a graphical modeling language, comprising:
[0020] The life cycle view analysis module is used to construct a complete aircraft engine life cycle stage according to the life cycle of the engine from delivery to scrapping, and use the state machine diagram to construct the engine life cycle stage analysis view;
[0021] The scenario view construction module is used to construct the usage scenarios of each life cycle stage of the engine, divide the usage scenarios of each life cycle stage into multiple main scenarios, and use cases to express each main scenario and the sub-scenario contained in the corresponding main scenario; the sub-scenario includes a normal use sub-scenario and an abnormal sub-scenario; the abnormal sub-scenario is obtained by analyzing the three dimensions of external environment abnormality, aircraft input abnormality, and engine abnormality;
[0022] A scenario-related party identification module is used to analyze each scenario one by one, and use an internal block diagram to construct an engine and stakeholder identification view under the scenario. The engine and stakeholders in the identification view are expressed by blocks;
[0023] The project flow building module is used to analyze the substances, energy or information interacting between the engine and stakeholders in a black box state with the engine as the center. The interactions between the blocks of the identification view are associated through connectors, and corresponding project flows are added to the connectors to express the names and directions of the interacting substances, energy or information;
[0024] The usage scenario activity view analysis module is used to construct an interactive activity analysis view of the engine usage scenario based on the constructed usage scenario using an activity diagram, and associate the identified stakeholders to the activity diagram through swimlanes. The activity diagram includes multiple activities and control flows and material flows between activities; according to the scenario goals to be achieved by the usage scenario, the corresponding responses and actions of the engine and stakeholders are analyzed through activities, control flows, and material flows to complete the construction of the interactive activity view of the engine usage scenario;
[0025] The requirement division module is used to define the functional and non-functional requirements of a single scenario and determine the activities that fall into the engine swim lane as the functional requirements of the engine;
[0026] The requirement view analysis module is used to complete the definition of activities, functional requirements and non-functional requirements for all single scenarios, and use the requirement graph to construct a view of affinity analysis of requirements for all engine usage scenarios; then all requirements identified in each single scenario are incorporated into the requirement graph, and affinity is performed through the classification framework of functional requirements, interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements, ultimately forming the engine usage scenario requirements based on the requirement graph.
[0027] Furthermore, in the life cycle view analysis module, the aircraft engine life cycle stages include transportation, storage, installation, storage, combat use, maintenance, repair and scrapping.
[0028] Furthermore, in the usage scenario stakeholder identification module, the stakeholders include users, maintenance personnel and interactive systems.
[0029] Furthermore, in the requirement division module, the non-functional requirements include interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements.
[0030] Compared with the prior art, the present invention has the following beneficial effects:
[0031] 1. The present invention analyzes the life cycle stage through state machine diagrams, constructs usage scenarios through use case diagrams, identifies system boundaries and stakeholders through internal block diagrams, integrates standardized graphical system modeling languages into aircraft engine system demand analysis, and starts from the final usage scenario. By carrying out system boundary and stakeholder identification, system scenario interaction activity analysis, and demand definition modeling for a single scenario one by one, the present invention finally completes demand affinity analysis through functional requirements and non-functional requirements, thereby forming an aircraft engine demand analysis method with a graphical modeling language that can effectively improve demand capture efficiency, effectively support demand analysis in the early stage of aircraft engine R&D, and improve the integrity and rationality of demand.
[0032] 2. The aviation engine demand analysis method of the present invention can avoid the problems of incomplete demand identification, high coordination times and long iteration cycle in the traditional document-based aviation engine demand capture mode. It has high standardization and operability, is easy to promote and apply, and has good economic benefits and great practical engineering application value. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] Figure 1 A flow chart of the method for analyzing aircraft engine requirements based on a graphical modeling language in Embodiment 1 or 2;
[0034] Figure 2 The engine life cycle stage analysis view in Embodiment 1 or 2;
[0035] Figure 3 A schematic diagram of the relationship between a main scene and a sub-scene in Example 2 through inclusion relationship;
[0036] Figure 4 The engine and stakeholder identification view in the use scenario in Example 2;
[0037] Figure 5 A view of the engine system scenario interactive activity analysis in Example 2;
[0038] Figure 6 It is a structural block diagram of the aircraft engine demand analysis system based on the graphical modeling language in Example 1;
[0039] Among them, 1. Life cycle view analysis module; 2. Usage scenario view construction module; 3. Usage scenario stakeholder identification module; 4. Project flow construction module; 5. Usage scenario activity view analysis module; 6. Requirements division module; 7. Requirements view analysis module. DETAILED DESCRIPTION
[0040] The present invention is further described in detail below in conjunction with the embodiments and drawings. However, it should not be understood that the scope of the above subject matter of the present invention is limited to the following embodiments, and all technologies realized based on the content of the present invention belong to the scope of the present invention.
[0041] Example 1
[0042] See also Figure 1 , Figure 2 and Figure 6 , an aircraft engine demand analysis method based on a graphical modeling language, including:
[0043] According to the life cycle of the engine from delivery to scrapping, a complete aircraft engine life cycle stage is constructed, and the engine life cycle stage analysis view is constructed using a state machine diagram;
[0044] Construct usage scenarios for each life cycle stage of the engine, divide the usage scenarios for each life cycle stage into multiple main scenarios, and use use cases to express each main scenario and the sub-scenario contained in the corresponding main scenario; the sub-scenario includes normal usage sub-scenario (such as sea level start, plateau start, low temperature start, etc.) and abnormal sub-scenario; the abnormal sub-scenario is obtained through three-dimensional analysis of external environment abnormality, aircraft input abnormality, and engine abnormality;
[0045] Analyze each usage scenario one by one, and use the internal block diagram to construct the engine and stakeholder identification view under the usage scenario. The engine and stakeholders in the identification view are expressed by blocks;
[0046] Taking the engine as the center, the substances, energy or information interacting between the engine and the stakeholders are analyzed in the black box state. The interactions between the blocks of the identification view are associated through connectors, and corresponding project flows are added to the connectors to express the names and directions of the interacting substances, energy or information.
[0047] Based on the constructed usage scenario, an activity diagram is used to construct a view of the interactive activity analysis of the engine usage scenario. The identified stakeholders are associated with the activity diagram through swimlanes. The activity diagram includes multiple activities and control flows and material flows between activities. According to the scenario goals to be achieved by the usage scenario, the corresponding responses and actions of the engine and stakeholders are analyzed through activities (Action), control flows (ControlFlow), and material flows (Object Flow), and the construction of the interactive activity view of the engine usage scenario is completed.
[0048] Carry out the definition of functional requirements and non-functional requirements of a single scenario, and determine that the activities (Action) falling into the engine swimlanes (Swimlanes) are the functional requirements of the engine; the swimlanes in this embodiment divide the activities in the activity diagram into several groups, and assign each group to the system object responsible for this group of activities; the area separated by vertical solid lines is the swimlane, indicating which activities are responsible for which objects.
[0049] Complete the definition of activities, functional requirements and non-functional requirements for all single scenarios, and use the requirements diagram to build a view of affinity analysis of requirements for all engine usage scenarios; then incorporate all requirements identified for each single scenario into the requirements diagram, and perform affinity through the classification framework of functional requirements, interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements, and finally form the engine usage scenario requirements based on the requirements diagram.
[0050] In this embodiment, the life cycle stage is analyzed through the state machine diagram, the usage scenario is constructed through the use case diagram, the system boundary and stakeholders are identified through the internal block diagram, and the standardized graphical system modeling language is integrated into the aircraft engine system requirement analysis. Starting from the final usage scenario, the system boundary and stakeholder identification, system scenario interaction activity analysis, and requirement definition modeling of a single scenario are carried out one by one. Finally, the requirement affinity analysis is completed through functional requirements and non-functional requirements. An aircraft engine requirement analysis method with a graphical modeling language that can effectively improve the efficiency of requirement capture is formed, which can effectively support the initial requirement analysis of aircraft engine research and development and improve the integrity and rationality of requirements; and can avoid the problems of incomplete requirement identification, high coordination times, and long iteration cycle in the traditional document-based aircraft engine requirement capture mode. It has high standardization and operability, is easy to promote and apply, and has good economic benefits and great practical engineering application value.
[0051] Based on the same inventive concept, this embodiment also provides an aircraft engine demand analysis system based on a graphical modeling language, including:
[0052] The life cycle view analysis module is used to construct a complete aircraft engine life cycle stage according to the life cycle of the engine from delivery to scrapping, and use the state machine diagram to construct the engine life cycle stage analysis view;
[0053] The scenario view construction module is used to construct the usage scenarios of each life cycle stage of the engine, divide the usage scenarios of each life cycle stage into multiple main scenarios, and use cases to express each main scenario and the sub-scenario contained in the corresponding main scenario; the sub-scenario includes a normal use sub-scenario and an abnormal sub-scenario; the abnormal sub-scenario is obtained by analyzing the three dimensions of external environment abnormality, aircraft input abnormality, and engine abnormality;
[0054] A scenario-related party identification module is used to analyze each scenario one by one, and use an internal block diagram to construct an engine and stakeholder identification view under the scenario. The engine and stakeholders in the identification view are expressed by blocks;
[0055] The project flow building module is used to analyze the substances, energy or information interacting between the engine and stakeholders in a black box state with the engine as the center. The interactions between the blocks of the identification view are associated through connectors, and corresponding project flows are added to the connectors to express the names and directions of the interacting substances, energy or information;
[0056] The usage scenario activity view analysis module is used to construct the view of the interactive activity analysis of the engine usage scenario based on the constructed usage scenario using the activity diagram, and associate the identified stakeholders to the activity diagram through the swim lane. The activity diagram includes multiple activities and the control flow and material flow between the activities; according to the scenario goals to be achieved by the usage scenario, the corresponding responses and actions of the engine and stakeholders are analyzed through the activities (Action), control flow (Control Flow), and material flow (Object Flow), and the construction of the interactive activity view of the engine usage scenario is completed;
[0057] The requirement division module is used to define the functional and non-functional requirements of a single scenario and determine the activities (Actions) that fall in the engine swimlanes (Swimlanes) as the functional requirements of the engine;
[0058] The requirement view analysis module is used to complete the definition of activities, functional requirements and non-functional requirements for all single scenarios, and use the requirements diagram (Requirements Diagram) to build a view of affinity analysis of requirements for all engine usage scenarios; then all requirements identified in each single scenario are included in the requirements diagram, and affinity is performed through the classification framework of functional requirements, interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements, finally forming the engine usage scenario requirements based on the requirements diagram (Requirements Diagram).
[0059] Example 2
[0060] See also Figure 1-Figure 5 , an aircraft engine demand analysis method based on a graphical modeling language, including:
[0061] Step 1: Based on the life cycle of the engine from delivery to scrapping, a complete aircraft engine life cycle stage is constructed, and a state machine diagram is used to construct an engine life cycle stage analysis view;
[0062] In this embodiment, a state machine diagram is used to construct a view of the engine life cycle stage analysis, as shown in Figure 2 ,exist Figure 2 In the process, a state is used to express a life cycle stage; finally, each life cycle stage is linked in chronological order through transition to complete the analysis and construction of the life cycle use stage view. The life cycle use stage of an aircraft engine should cover the life cycle stage from delivery and transportation at the final assembly plant to final scrapping. As described in this embodiment, the life cycle stages of an aircraft engine include transportation, storage, installation, storage, combat use, maintenance, repair and scrapping.
[0063] Step 2: Construct usage scenarios for each life cycle stage of the engine, divide the usage scenarios for each life cycle stage into multiple main scenarios, and use use cases to express each main scenario and the sub-scenario contained in the corresponding main scenario; the sub-scenario includes normal usage sub-scenario (such as sea level start, plateau start, low temperature start, etc.) and abnormal sub-scenario; the abnormal sub-scenario is obtained through three-dimensional analysis of external environment abnormality, aircraft input abnormality, and engine abnormality;
[0064] In this embodiment, a use case diagram is used to construct a view of the engine usage scenario analysis:
[0065] Taking the life cycle usage phase view formed by the State Machine Diagram as input, first divide each main scenario. The normal use sub-scenario of each main scenario is divided into normal use sub-scenario according to factors such as external environment, usage mode, and working status; for the division of abnormal sub-scenario of each main scenario, the abnormal sub-scenario does not exist independently of the normal scenario. There are often multiple abnormal sub-scenarios during normal use. The abnormal sub-scenario is an effective supplement to the normal use sub-scenario and has a great impact on the completeness of demand capture. The abnormal sub-scenario should be combined with the normal use sub-scenario, considering the three aspects of external environment abnormality, aircraft input abnormality, and engine abnormality to identify the abnormal sub-scenario of each engine under the normal main scenario. Any scenario of the engine normal use sub-scenario and the abnormal sub-scenario is expressed by a use case. The relationship between the main scenario and the sub-scenario is associated through an include relationship (Include), see for details. Figure 3 Each use stage of the engine life cycle should have a corresponding use scenario to undertake or refine it.
[0066] Step 3: Analyze each usage scenario one by one, and use the internal block diagram to construct an engine and stakeholder identification view under the usage scenario, where the engine and stakeholders in the identification view are expressed by blocks;
[0067] In this embodiment, an internal block diagram is used to construct a view of the engine system boundary and stakeholder identification, as shown in Figure 4 The stakeholders include users, maintenance personnel and interactive systems.
[0068] Step 4: With the engine as the center, analyze the substances, energy or information interacting between the engine and stakeholders in the black box state. The interactions between the blocks of the identification view are associated through connectors, and corresponding project flows are added to the connectors to express the names and directions of the interacting substances, energy or information.
[0069] In this embodiment, the research object (aircraft engine) is taken as the center to analyze the users, maintenance personnel and interactive systems that interact with it in the black box state. The engine and its related stakeholders are expressed by blocks, and the interaction between systems is associated through connectors. The interactive materials, energy and information can be expressed by adding signal expressions by adding item flows.
[0070] Step 5: Based on the constructed usage scenario, an activity diagram is used to construct a view of the interactive activity analysis of the engine usage scenario. The identified stakeholders are associated with the activity diagram through swimlanes. The activity diagram includes multiple activities and control flows and material flows between activities. According to the scenario goals to be achieved by the usage scenario, the corresponding responses and actions of the engine and stakeholders are analyzed through activities (Action), control flows (Control Flow), and material flows (Object Flow), and the construction of the interactive activity view of the engine usage scenario is completed;
[0071] In this embodiment, after the system boundary and stakeholders are identified, the interaction between the engine and various systems and personnel can be analyzed. Scenario interaction analysis is the core content of graphical modeling requirements analysis, which sorts out the scenario interaction between the engine and various systems and personnel based on the goals that need to be achieved in the scenario.
[0072] First, based on the formed usage scenario, an activity diagram (SysML Activity Diagram) is used to construct a view of the engine system scenario interaction activity analysis, as shown in Figure 5 ; Secondly, identify stakeholders by linking them to the activity diagram through swimlanes for analysis; finally, for the scenario goals, analyze in detail how the engine and stakeholders respond, act, and interact through activities (Action), control flow (ControlFlow), material flow (Object Flow), etc., in order to achieve the established goals of the scenario and complete the system scenario interactive activity view.
[0073] Step 6: Define the functional and non-functional requirements for a single scenario, and determine the activities that fall in the engine swimlanes as the functional requirements of the engine;
[0074] In this embodiment, a single scenario requirement definition can be defined from both functional and non-functional aspects. Functional requirements can be defined from the activities (Action) of the engine lane in the system scenario interactive activity analysis view. The activities (Action) that fall into the engine lane (Swimlanes) are the functions that the engine system needs to complete. The engine functional requirements are clearly described in the text (Text) according to the requirement writing method specified by the system engineering. Non-functional requirements are also based on scenario system activities and interactions, and are defined in terms of relevance from aspects such as environmental adaptability, aircraft condition constraints, interface matching, and ergonomics. Each scenario requirement uses a requirement element (Requirement) to define the name, content, number, etc. As described in this embodiment, non-functional requirements include interface requirements, environmental adaptability requirements, constraint requirements, and ergonomics requirements.
[0075] Step 7. Complete the definition of activities, functional requirements and non-functional requirements for all scenarios, and use the requirements diagram to build a view of affinity analysis of requirements for all engine usage scenarios; then incorporate all requirements identified for each single scenario into the requirements diagram, and perform affinity through the classification framework of functional requirements, interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements, and finally form the engine usage scenario requirements based on the requirements diagram.
[0076] In this embodiment, all requirements identified in each single scenario are put into the requirements diagram for affinity analysis. Specifically, affinity is performed through the classification of functional requirements, interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements, and ultimately an engine usage scenario requirement based on the requirements diagram is formed.
[0077] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. The method for aircraft engine demand analysis based on graphical modeling language is characterized by: include: According to the life cycle of the engine from delivery to scrapping, a complete aircraft engine life cycle stage is constructed, and the engine life cycle stage analysis view is constructed using a state machine diagram; Construct usage scenarios for each life cycle stage of the engine, divide the usage scenarios for each life cycle stage into multiple main scenarios, and use use cases to express each main scenario and the sub-scenario contained in the corresponding main scenario; the sub-scenario includes normal use sub-scenario and abnormal sub-scenario; the abnormal sub-scenario is obtained through analysis of three dimensions: external environment abnormality, aircraft input abnormality, and engine abnormality; Analyze each usage scenario one by one, and use the internal block diagram to construct the engine and stakeholder identification view under the usage scenario. The engine and stakeholders in the identification view are expressed by blocks; Taking the engine as the center, the substances, energy or information interacting between the engine and the stakeholders are analyzed in the black box state. The interactions between the blocks of the identification view are associated through connectors, and corresponding project flows are added to the connectors to express the names and directions of the interacting substances, energy or information. Based on the constructed usage scenarios, an activity diagram is used to construct a view of the interactive activity analysis of the engine usage scenarios, and the identified stakeholders are associated with the activity diagram through swim lanes. The activity diagram includes multiple activities and control flows and material flows between activities; According to the scenario goals to be achieved by the usage scenario, the corresponding responses and actions of the engine and stakeholders are analyzed through activities, control flows, and material flows, and the interactive activity view of the engine usage scenario is built; Carry out the definition of functional and non-functional requirements for a single scenario, and determine the activities that fall into the engine swim lane as the functional requirements of the engine; Complete the definition of activities, functional requirements and non-functional requirements for all single scenarios, and use the requirement graph to construct a view of affinity analysis of requirements for all engine usage scenarios; then incorporate all requirements identified for each single scenario into the requirement graph, and perform affinity through the classification framework of functional requirements, interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements, and finally form the engine usage scenario requirements based on the requirement graph.
2. The method for analyzing aircraft engine requirements based on a graphical modeling language according to claim 1, characterized in that: The aircraft engine life cycle stages include transportation, storage, installation, storage, combat use, maintenance, repair and scrapping.
3. The method for analyzing aircraft engine requirements based on a graphical modeling language according to claim 1, characterized in that: The stakeholders include users, maintenance personnel and interactive systems.
4. The method for aircraft engine demand analysis based on graphical modeling language according to claim 1, characterized in that: The non-functional requirements include interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements.
5. The aircraft engine demand analysis system based on graphical modeling language is characterized by: include: The life cycle view analysis module is used to construct a complete aircraft engine life cycle stage according to the life cycle of the engine from delivery to scrapping, and use the state machine diagram to construct the engine life cycle stage analysis view; The scenario view construction module is used to construct the usage scenarios of each life cycle stage of the engine, divide the usage scenarios of each life cycle stage into multiple main scenarios, and use cases to express each main scenario and the sub-scenario contained in the corresponding main scenario; the sub-scenario includes a normal use sub-scenario and an abnormal sub-scenario; the abnormal sub-scenario is obtained by analyzing the three dimensions of external environment abnormality, aircraft input abnormality, and engine abnormality; A scenario-related party identification module is used to analyze each scenario one by one, and use an internal block diagram to construct an engine and stakeholder identification view under the scenario. The engine and stakeholders in the identification view are expressed by blocks; The project flow building module is used to analyze the substances, energy or information interacting between the engine and stakeholders in a black box state with the engine as the center. The interactions between the blocks of the identification view are associated through connectors, and corresponding project flows are added to the connectors to express the names and directions of the interacting substances, energy or information; A usage scenario activity view analysis module is used to construct an engine usage scenario interactive activity analysis view using an activity diagram based on the constructed usage scenario, and associate the identified stakeholders to the activity diagram through swim lanes. The activity diagram includes multiple activities and control flows and material flows between activities; According to the scenario goals to be achieved by the usage scenario, the corresponding responses and actions of the engine and stakeholders are analyzed through activities, control flows, and material flows, and the interactive activity view of the engine usage scenario is built; The requirement division module is used to define the functional and non-functional requirements of a single scenario and determine the activities that fall into the engine swim lane as the functional requirements of the engine; The requirement view analysis module is used to complete the definition of activities, functional requirements and non-functional requirements for all single scenarios, and use the requirement graph to construct a view of affinity analysis of requirements for all engine usage scenarios; then all requirements identified in each single scenario are incorporated into the requirement graph, and affinity is performed through the classification framework of functional requirements, interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements, ultimately forming the engine usage scenario requirements based on the requirement graph.
6. The aircraft engine demand analysis system based on graphical modeling language according to claim 5, characterized in that: In the life cycle view analysis module, the aircraft engine life cycle stages include transportation, storage, installation, storage, combat use, maintenance, repair and scrapping.
7. The aircraft engine demand analysis system based on graphical modeling language according to claim 5, characterized in that: In the usage scenario stakeholder identification module, the stakeholders include users, maintenance personnel and interactive systems.
8. The aircraft engine demand analysis system based on graphical modeling language according to claim 5, characterized in that: In the requirement division module, the non-functional requirements include interface requirements, environmental adaptability requirements, constraint requirements, and ergonomic requirements.
Citation Information
Cited By
System demand analysis method based on system scene
CN119645353A
Aero-engine design method based on SysML activity diagram native drive and AI autonomous decision
CN122334028A
