Mars rover demand multi-view dynamic analysis and modeling method based on mission-operation
Through a mission-operation-based multi-view dynamic analysis method, combined with modeling languages such as SysML and ReqIF, the problem of incomplete requirements analysis in rover system design is solved, and multi-dimensional requirements recognition and dynamic adaptation to complex systems is achieved, and the accuracy and adaptability of the design is improved.
Patent Information
- Application Number
- CN202510316454.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-18
- Publication Date
- 2025-08-05
AI Technical Summary
The existing MBSE method lacks sufficient consideration of the external environment and actual operating conditions in complex system designs such as Mars rovers, resulting in incomplete requirements analysis and difficult to identify dynamic requirements and complex dependencies. The traditional RFLP method cannot meet the variability and dynamic needs of complex systems.
The multi-perspective dynamic analysis method based on mission-run is adopted. Through mission analysis and operation analysis, combined with the full life cycle model of the interest system, the multi-level multi-perspective requirements of the system are identified, and the demand description is used for modeling languages such as SysML and ReqIF to ensure the comprehensiveness and dynamicity of the demand source.
It realizes multi-dimensional demand identification for complex systems such as Mars rovers, improves the accuracy and reliability of the design, adapts to complex environments and tasks, reduces design defects, and improves the adaptability and robustness of the system.
Smart Images

Figure CN120428953A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the fields of complex system design, model-based system engineering, and modeling methodology, and particularly relates to a multi-perspective dynamic analysis and modeling method for the requirements of a Mars rover based on mission and operation. Background Art
[0002] With the development of technological and industrial revolutions, the complexity of system design has become increasingly high. When designing, it is necessary to consider how to cope with the complexity and variability in the system operating environment. Traditional document-based system engineering (TBSE) has problems such as lagging document updates and poor document readability when conducting complex system design, making it difficult to effectively capture and express various requirements of complex systems, with poor design efficiency and increasingly obvious limitations. Model-based system engineering (MBSE) uses models instead of documents, quickly constructs, iterates, analyzes, and evaluates system design solutions in the early design stage, optimizes the R & D process of complex systems, improves design efficiency, and reduces R & D costs, becoming the preferred system design method in the R & D fields of complex systems such as aerospace.
[0003] The modeling methodology is a roadmap for MBSE to analyze systems and create models, which can ensure that the design team designs system models in a consistent manner when working collaboratively. It is one of the three major pillars of MBSE. The current MBSE methodology is mainly the requirements - function - logic - physical (RFLP) route, starting from the user / stakeholder requirements to clarify the functional requirements, performance requirements, reliability requirements, and other key requirements of the system. However, requirements analysis usually focuses on extracting requirements theoretically or from documents, and rarely considers the complexity and variability of the system in the actual operating environment. For example, the real - world external environment (such as weather, geographical location, operating conditions, etc.) may have a significant impact on the operation of the system, but these factors are usually difficult to be fully considered in the early - stage requirements analysis. This disconnection leads to the system design being unable to truly meet the actual requirements of the operating environment, thus affecting the feasibility and adaptability of the system. For example, the system design in the aerospace field may not fully consider the unforeseen environmental factors or conditions during the actual operation process, resulting in defects being exposed during the later - stage test adjustment or operation process. Especially in the design of a Mars rover, in the project of the Mars rover, the mission requirements are very complex, including multiple scientific experiments, sampling, autonomous navigation, and other functions. The traditional RFLP methodology may not be able to fully capture the complexity and variability of these requirements. The requirements stage often only focuses on static and superficial problems, while ignoring the potential interactions between requirements and the possibility of later - stage mission evolution. Because the RFLP methodology focuses on the sequential progression from requirements to physical implementation, the design team may not be able to comprehensively identify the dynamic requirements and complex dependencies in the mission at the initial stage, resulting in problems in the later - stage design and verification phases. Therefore, there is an urgent need for a requirements analysis method that not only starts from user requirements but also pays attention to the full life cycle of the system mission and the complexity of the actual operating environment.
[0004] The Chinese patent application for invention with the publication number CN112527245A discloses a model - based functional requirements analysis method for complex systems. This method proposes a model - based functional requirements analysis method applicable to the overall design of complex unmanned aerial vehicle systems, including the following steps: ① Design the scenario meta - model of the life - cycle fragment; ② Clarify the internal and external elements of the system, and establish the element category diagram and element instance diagram; ③ Establish the system element activity diagram and sequence diagram; ④ Classify, collect, define, and map the operational requirements and interactive requirements to form a functional requirements form; ⑤ Compile and form the design system functional requirements document. Although this model - based complex system requirements analysis method combines specific function scenarios in the system life cycle to identify requirements, it still lacks consideration of the requirements generated by factors such as user expectations, and the requirements analysis is not comprehensive enough. The existing MBSE modeling methods and requirements analysis lack actual requirements analysis oriented to missions and task scenarios, and there are problems such as imperfect requirement acquisition, unreasonable decomposition, and slow change response when facing complex systems like Mars rovers.
[0005] As can be seen from the above analysis, for the requirements analysis and modeling of complex systems such as rovers, the current requirements analysis methods have the following problems to be solved:
[0006] (1) Static nature of requirements analysis: Current requirements analysis methods often focus on extracting requirements theoretically or from documents, emphasizing the static nature and initial definition of requirements. This method ignores the characteristics of requirements evolution over time and in different environments in complex systems. For example, during the design process of a rover, mission requirements and operating conditions may change due to mission progress and external environmental changes. Traditional methods are difficult to capture these changes in a timely manner, resulting in the system being unable to meet new requirements or handle unforeseen challenges during actual operation.
[0007] (2) Insufficient consideration of external environment and actual operating conditions: In existing requirements analysis methods, there is often a lack of sufficient consideration of external environmental factors (such as extreme weather, geographical location, operating conditions, etc.) and actual operating conditions. These factors have an important impact on the operation of the system. Especially in complex systems like rovers, the extreme environment of Mars and the remote operating conditions may lead to significant changes in design and functional requirements.
[0008] (3) Lack of multi - perspective analysis of requirement sources: Existing MBSE modeling methodologies are mainly based on the RFLP architecture. Requirements are regarded as inputs for modeling design, and the sources of requirements mainly rely on project book descriptions. Only constraints are collected as much as possible, lacking the use of model analysis as a guide to identify requirements from multiple perspectives such as business goals, user expectations, environmental factors, and capabilities required by the system itself. The rover system has a high degree of disciplinary coupling and a complex working environment, making it difficult to directly consider all requirement sources. Requirements identified from a single perspective of top - level design are difficult to fully reveal the relationships and dependencies between different fields. Summary of the Invention
[0009] In view of this, the present invention provides a multi - perspective dynamic analysis and modeling method for rover requirements based on mission - operation. This method conducts multi - level and multi - perspective dissection and analysis of the overall requirements of stakeholders, uses the process of modeling analysis to derive capability requirements, and clarifies the sources of system requirements. Using this method to guide the design and development of rovers can ensure the comprehensiveness of requirement source analysis and effectively improve the usability of the established model.
[0010] To solve the above - mentioned technical problems, the present invention is implemented as follows.
[0011] A multi - perspective dynamic analysis and modeling method for rover requirements based on mission - operation includes a mission analysis and modeling process and an operation analysis and modeling process. This process forms requirement analysis results and system models that can support the research, development, and design of rover systems;
[0012] In the mission analysis and modeling process, first, conduct a top-level mission decomposition from the dimension of serving customers to determine the customers corresponding to the mission and the business objectives for measuring whether the mission is completed; then determine the mission stages required to complete the top-level mission, as well as the stakeholders and execution entities involved in each mission stage, analyze the specific activities in each mission stage, determine the capability requirements for completing all mission stages, and trace the capability requirements back to the corresponding execution entities;
[0013] In the operation analysis and modeling process, obtain the system with the most associated business objectives as the system of interest; from the perspective of the system of interest, analyze the interactions between other execution entities and within the execution entities of the system of interest during the mission execution activities; guided by the full life cycle model of the system of interest, decompose the operation stages of the system of interest to obtain the internal and external execution entities involved in each operation stage; then allocate the activity processes of each operation stage to the corresponding execution entities, and further identify the capability requirements from the activities of the operation stage; finally, summarize the stakeholder requirements corresponding to the top-level mission from the capability requirement results of the mission analysis and modeling and the motion analysis and modeling processes.
[0014] Preferably, the mission analysis and modeling process includes:
[0015] Step a1: Decompose the mission from the dimension of serving customers: Determine the customers corresponding to the input mission and the business objectives for measuring whether the mission is completed; describe the relationship between the mission, customers, and business objectives through form x1; each mission corresponds to at least 1 customer and has at least one business objective;
[0016] Step a2: Mission-entity traceability: Represent the mission with business objectives, identify the execution entity corresponding to each business objective, ensure that each business objective is completed by an execution entity, and establish a relationship traceability matrix x2 between the business objectives and the execution entities;
[0017] Step a3: Decompose the mission stages from the content dimension: Determine the mission stages required to complete the mission, and construct a transition diagram x3 that describes the content of each mission stage and the transition events between the mission stages;
[0018] Step a4: Analyze the mission stages: Analyze the execution entities participating in the realization of the mission stage tasks for each mission stage, and analyze the execution process of the activities in each mission stage; combine the activity process with the mission decomposition in step a3 to identify the capability requirements of the entire exploration project system, and construct a capability requirement analysis result x4 that describes the capability requirements, mission stages, and expected effects of the execution activities; <000004>
[0019] Step a5: Perform a capability gap analysis: Analyze whether each capability will be satisfied based on the relationship between the capability requirements of the entire exploration project system and the implementing entities, and form a capability traceability matrix x5;
[0020] Steps a1 - a5 provide a roadmap for mission-level requirements analysis and modeling. The diagrams, tables, and matrices formed constitute the modeling results corresponding to the mission analysis. The requirements analysis result x4 at the mission analysis level is obtained in a4.
[0021] Preferably, in step a1, a requirements entry form ReqIF is used to describe the relationship between the mission, customers, and business goals;
[0022] In step a3, a state machine diagram in the SysML language is used for modeling. The model describes the content of each mission stage and the transition events between mission stages;
[0023] In step a4, a module definition diagram is established to represent the implementing entities of each mission stage; an activity diagram is established to represent the execution process of activities in each stage; a list is used to describe the capability requirements of the entire exploration project system, the corresponding mission stages, and the expected effects.
[0024] Preferably, in step a4, when analyzing the implementing entities participating in the realization of mission stage tasks, the implementing entities are decomposed into components.
[0025] Preferably, the operation analysis and modeling process includes:
[0026] Step b1: Analyze the interest system: Based on the traceability relationship y1 between the capability requirements and the implementing entities obtained during the mission analysis and modeling process, determine at least one implementing entity or a component under the implementing entity with the closest capability requirements as the interest system; construct a context structure diagram y2 of the interest system to describe the subordination relationship between the components under the interest system; for each interest system, perform the following steps b2 - b5:
[0027] Step b2: Define the life cycle of the interest system and construct a transition diagram y3 that describes the content of each life cycle stage and the transition events between the life cycle stages;
[0028] Step b3: Analyze the operation stage: From the perspective of the interest system, decompose the operation stage in terms of content dimension, determine the execution events corresponding to the interest system in different operation stages and the transition process between operation stages, and construct a transition diagram y4 for description;
[0029] Step b4: For each operation stage, establish an association relationship y5 between the operation stage and the mission stage for the operation interaction and activities of the interest system and other external associated entities in the mission analysis stage;
[0030] Step b5: Stakeholder requirements analysis: Based on the operational interactions and activities during the operation phase, further identify new capability requirements y6, trace them back to the internal execution entities of the interest system, and form a supplementary capability traceability matrix y7.
[0031] Steps b1 - b5 provide a roadmap for operational level requirements analysis and modeling. The formed diagrams, relationships, and matrices constitute the modeling results corresponding to the operational analysis, and the results of the operational level requirements analysis are obtained in b5.
[0032] Preferably, in step b1, use a module diagram to represent the context structure diagram of the interest system.
[0033] In step b2, use a state machine diagram to describe the full life cycle of the interest system.
[0034] In step b3, use a state machine diagram for modeling, and the model describes the content of each operation phase and the transition events between operation phases.
[0035] In step b4, for the construction of the association relationship: establish a requirements item form to determine the corresponding relationship among the operation phase, mission phase, and interest system life cycle phase; use a module definition diagram to identify the entities participating in each phase; establish an internal module diagram to represent the operational interaction between the interest system and external entities; use an activity diagram to represent the implementation activities of the operation phase tasks.
[0036] Beneficial effects:
[0037] (1) Multi - perspective requirements analysis: Existing RFLP methods usually use a single perspective for requirements identification, mainly focusing on the functional requirements of the system and their constraints, ignoring other key factors (such as environment, user expectations, system capabilities, etc.). The multi - perspective requirements analysis method proposed in this application can comprehensively identify requirements from multiple different angles (including business goals, user expectations, environmental factors, system capabilities, etc.), ensuring that the system design can more accurately reflect the multi - dimensional requirements in a complex system. Especially in complex systems such as Mars rovers, considering the multi - dimensional requirement sources, it is possible to better identify and resolve the interaction and dependency relationships between requirements, thereby improving the accuracy and reliability of the design.
[0038] (2) Dynamic Requirement Identification and Evolution: The current MBSE method directly starts with requirements and uses the requirements identified in the early design work as the guidance for modeling and analysis. The requirements are relatively fixed, lacking the process of dynamic identification and evolution throughout the design process. The method proposed in this application takes the mission as the input and uses the model as the traction during the analysis process of the mission - operation two stages. The mission is decomposed into different stages, and then each mission stage is interpreted from the perspective of the interest system, giving the corresponding operation concept, so as to obtain the system capability requirements and stakeholder requirements that need to be met during the operation process. The process of requirement identification is dynamically evolving and progressive layer by layer. The result of requirement identification is more comprehensive and can better reflect the design requirements of complex systems such as Mars rovers.
[0039] (3) Comprehensive Consideration of the Impact of Environment and Operating Conditions: Traditional requirement analysis methods usually cannot fully consider the actual environmental conditions and operating backgrounds (such as extreme weather, terrain changes, etc.) under which the system operates, and these factors have an important impact on the actual operation of the system and the success of the mission. By introducing the perspective of environmental factors, this application enables requirement analysis to more comprehensively consider complex environmental conditions, especially applicable to systems such as Mars rovers that operate in extreme environments, ensuring that the design can meet various challenges in actual operation.
[0040] (4) Adaptation to the Complexity and Uncertainty of Complex System Design: Complex systems such as Mars rovers have a high degree of disciplinary coupling and task complexity, and traditional RFLP methods often cannot cope with these complexities and uncertainties. Through multi - perspective requirement analysis, this application can better handle the uncertainties in complex systems, identify potential problems in advance, and make timely adjustments during the system design and implementation stages, avoiding design defects caused by incomplete or inaccurate requirement identification.
[0041] In summary, compared with the existing RFLP architecture method, by introducing the multi - perspective requirement analysis method, this invention can more comprehensively, dynamically, and accurately identify the requirements of complex systems, is particularly applicable to the design of high - complexity and interdisciplinary systems such as Mars rovers, and has higher adaptability, feasibility, and robustness. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] Figure 1 It is the schematic diagram of the multi - perspective dynamic requirement analysis and modeling method for Mars rovers based on mission - operation of this invention.
[0043] Figure 2 It is the requirement item form showing the correspondence relationship between mission, customer, and business goals.
[0044] Figure 3 It is the relationship traceability matrix between business goals and execution entities.
[0045] Figure 4 It is the state machine diagram of the mission stage.
[0046] Figure 5 Module definition diagram for characterizing the execution entity in the mission phase.
[0047] Figure 6 Activity diagram for the activity execution process in the mission phase.
[0048] Figure 7 Capability requirement description table for exploring the project system.
[0049] Figure 8 Schematic diagram of the capability traceability matrix.
[0050] Figure 9 Context structure of the interest system characterized by using module diagrams.
[0051] Figure 10 Full life cycle of the interest system represented by using state machine diagrams.
[0052] Figure 11 Division of the operation phases of the interest system.
[0053] Figure 12 Corresponding relationship among the operation phase, mission phase, and life cycle phase of the interest system described by using requirement item forms.
[0054] Figure 13 Entities participating in each operation phase described by using module definition diagrams.
[0055] Figure 14 Operation interaction between the interest system and external entities represented by using module diagrams.
[0056] Figure 15 Implementation activities of the operation phase tasks represented by using activity diagrams.
[0057] Figure 16 Schematic diagram for identifying new capability requirements.
[0058] Figure 17 Schematic diagram of the supplementary traceability relationship corresponding to the new capability requirements.
[0059] Figure 18 Schematic diagram of the requirements of each stakeholder. Detailed implementation manners
[0060] The present invention will be described in detail below in conjunction with the accompanying drawings and by way of examples.
[0061] Based on the above problems, the present invention proposes a mission - operation - based multi - perspective dynamic requirement analysis and modeling method for a Mars rover. This process will form a series of graphs, tables, relationships, matrices, etc. These analysis results can form requirement analysis results and system models that support the research and development design of the Mars rover system, providing a means of multi - perspective dynamic requirement analysis and a modeling method for studying the complex system of the Mars rover using the MBSE method.
[0062] When facing the specific project requirement analysis, this method uses the model as an analysis means and divides the requirement analysis process into two stages: mission analysis and operation analysis.
[0063] Mission analysis stage: First, perform top - level mission decomposition from the dimension of service customers, determine the customers corresponding to the mission, and the business goals for measuring whether the mission is completed; then determine the stages through which the top - level mission needs to pass, as well as the stakeholders and execution entities involved in each mission stage, analyze the specific activities in each mission stage, determine the ability requirements for completing all mission stages, and trace the ability requirements to the corresponding execution entities.
[0064] Operation analysis stage: Obtain the system with the most associated business goals as the system of interest, which will become the main object of analysis in the operation stage. The goal of the operation - stage analysis is to analyze the interactions between the system of interest and other execution entities, as well as between the execution entities within the system of interest during the process of mission execution from the perspective of the system of interest. Guided by the full - life - cycle model of the system of interest, decompose the operation stage of the system of interest to obtain the execution entities (sub - systems) within the system of interest and other execution entities involved in each stage. Then allocate the activity processes of each operation stage to the corresponding execution entities, further identify the ability requirements from the activities in the operation stage; finally, in addition to the ability requirement results from the two stages, summarize the stakeholder requirements corresponding to the top - level mission. Among them, the above - mentioned stakeholders include all customers, all execution entities, the sub - systems of execution entities, and functional devices. An execution entity is all entities that perform functions and their sub - systems and functional devices. In the operation analysis stage, the analysis is carried out from the perspective of the system of interest. Therefore, for the system of interest, the internal execution entities refer to the sub - systems and specific functional devices of the system of interest, and the execution entities that do not belong to the system of interest are called external entities.
[0065] This method is mission - oriented, conducts multi - level and multi - perspective dissection and analysis of the overall requirements of stakeholders, uses the modeling analysis process to draw out the ability requirements, and clarifies the source of system requirements. Using this method to guide the design and development of the Mars rover can ensure the comprehensiveness of the requirement source analysis and effectively improve the usability of the established model. The specific steps of the modeling analysis are as Figure 1 shown.
[0066] The specific process of the modeling analysis is as follows:
[0067] The mission - based rover requirement analysis and modeling process is based on the multi - paradigm modeling language KARMA and the multi - paradigm modeling tool MetaGraph2.0. Using basic elements such as graphs, objects, relationships, roles, points, and attributes, it can customize the design of meta - models for specific domains, construct architecture models according to different requirements, and in the case, construct the internationally common MBSE modeling language SysML through the KARMA language, model using its syntax, and at the same time combine with the Requirement Interchange Format (ReqIF) for requirement description, which can better adapt to the design of complex systems such as rovers.
[0068] This invention uses a certain rover as a case for method illustration and uses the public planning content of the NASA 2020 Mars Exploration Program as the mission input for the case. Due to insufficient reference materials, there may be differences between the customer mission, the functions of the rover, and the subsystem description and the actual situation. However, the focus of the case illustration is on the process explanation. Although it cannot comprehensively describe the entire Mars exploration plan, it is sufficient to introduce the execution process of this method, describe clearly the process of requirement analysis and acquisition, and verify the feasibility of this method.
[0069] 1. Mission analysis:
[0070] (1) Analyze the mission input. The mission is defined from the customer's perspective. The customer is the beneficiary of the mission. The same mission may correspond to multiple customers and may have multiple business goals to measure whether the mission is completed. Use the Requirement Interchange Format to show the corresponding relationship between the mission and the customer and interpret the business goals for mission completion. This step ensures that each mission corresponds to at least one customer and has at least one completion - goal evaluation. As Figure 2 shown, in the Mars exploration plan, there are three missions, corresponding customers and business goals.
[0071] (2) Mission - entity traceability. In this step, use the business goal to represent the mission, identify the corresponding execution entity for each business goal, and ensure that each business goal has an execution entity to complete it. The purpose of this step is to ensure that the business goal and the mission it represents can be completed by an entity. Some execution entities may also be the customers in the first step, such as "NASA" in the case. The identity can be switched, but the identity of the execution entity is the executor of the business goal and the mission, while the identity of the customer is the service object of the mission. Establish a relationship traceability matrix as Figure 3 shown, "traceability" means that the execution entity needs to participate in the completion of this business goal.
[0072] (3) Define the mission stage concept. The mission stage concept refers to the solution of the mission, which represents the realization process of the mission in stages at this step. Describe the content of each mission stage and the transition events between stages. The previous mission decomposition is interpreted from the perspective of serving customers, while this step is from the perspective of process content. Multiple perspectives of interpretation are more conducive to obtaining requirements, and the modeling method is more complete. Use the state machine diagram in SysML language for modeling, and the model example is as Figure 4 shown.
[0073] (4) Analyze the mission stage. For each stage divided in the third step, analyze the execution entities participating in the realization of the task stage and the activity tasks of each mission stage. Then, combine the activity process with the previous mission decomposition to identify the capability requirements of the entire exploration project system and describe the expected effects of its execution activities. [[ID=?]] [[ID=?]]
[0074] Establish a module definition diagram to represent the execution entities of each stage, such as Figure 5 shown; establish an activity diagram to specifically represent the execution process of each stage activity, such as Figure 6 shown. Only the example diagrams are presented here. In the specific modeling analysis process, each stage defined in step (3) needs to be analyzed. The identification of capability requirements is as Figure 7 shown.
[0075] (5) Perform a capability gap analysis. In this step, based on the relationship between the capability requirements and the execution entities, analyze whether each capability will be met, form a capability traceability matrix, and determine the system boundary of the execution entity according to the evidence, that is, which functional subsystems and functional devices need to be included. As Figure 8 shown.
[0076] Steps (1)-(5) of the mission analysis stage provide a roadmap for mission-level requirements analysis and modeling. The diagrams, tables, and matrices formed constitute the modeling results corresponding to the mission analysis, and the requirements analysis results at the mission analysis level are obtained in a4 ( Figure 7 ). The essence of MBSE is to use models to carry the R & D design information of the system instead of documents. The modeling results of this invention are for the research and application of MBSE on complex systems such as Mars rovers. At the same time, this invention can also summarize the requirements analysis results for MBSE to use.
[0077] 2. Operational analysis modeling:
[0078] (1) Analyze the system of interest. The system of interest refers to a specific system that is the focus during the analysis process. It represents the core concern of the project and is usually the key part that needs to be studied and optimized in detail in the overall system.
[0079] It should be noted that there are some "?" in the translation where the original text has unclear or potentially incorrect tags. You may need to double-check the original text for accuracy.In the execution of the ability requirement traceability in the last step of mission analysis, it can be clearly understood which execution entities are needed to complete the system's ability requirements. In the case, execution entities such as "NASA" and "launch vehicle" achieve fewer ability requirements, and their system boundaries are larger, so no specific system analysis is required. Most of the ability requirements are realized by the functional subsystems of the rover, and the rover is the system of interest in this case. When using the method of the present invention in other scenarios, there may be multiple systems of interest, and then the subsequent analysis steps need to be performed on each system of interest. Use a module diagram to represent the context structure of the system of interest (the rover), such as Figure 9 as shown
[0080] (2) Define the life cycle of the system of interest. The life cycle of a system is a complete process from design and manufacture to decommissioning, covering all activities during its entire existence
[0081] Use a state machine diagram to represent the entire life cycle of the system of interest, and divide it into different stages according to the important nodes of the system operation, such as Figure 10 as shown. This is convenient for the subsequent analysis of the rover's operation activities and further identification of the ability requirements of the system of interest
[0082] (4) Analyze the operation stage. After dividing the operation stage, as in the mission analysis process, each stage needs to be analyzed in depth. Identify the operation interactions and activities between the system of interest and other external associated entities in the mission stage. Since the interpretation angles are different, the association relationship between the operation stage and the mission stage needs to be established
[0083] First, establish a requirement item form to determine the corresponding relationship among the operation stage, the mission stage, and the life cycle stage of the system of interest, such as Figure 12 as shown; then use a module definition diagram to identify the internal execution entities (subsystems, functional devices) of the system of interest and other execution entities participating in each stage, such as Figure 13 ; then establish an internal module diagram to represent the operation interaction between the system of interest and external entities, as Figure 14 shown; finally, use an activity diagram to represent the implementation activities of the tasks in the operation stage, such as Figure 15 as shown
[0084] (5) Stakeholder requirement analysis. After analyzing all the operation stages, first, based on the analysis of the interaction activities in the operation stage, further identify new ability requirements, such as Figure 16 as shown; and trace them back to the corresponding subsystems and functional devices of the system of interest. Some of the trace relationships are as Figure 17 shown
[0085] The above steps (1)-(5) in the operation analysis stage provide a route for operation-level requirement analysis and modeling. The formed diagrams, relationships, and matrices constitute the modeling results corresponding to the operation analysis, and the results of the operation-level requirement analysis are obtained at b5 ( Figure 16 and Figure 18 ).
[0086] Through the analysis of the mission and operation levels of this method, the planning mission and business objectives are interpreted and analyzed from multiple perspectives such as customers, interest systems, and execution entities. The ability requirements of complex systems (such as Mars rovers) are gradually obtained. Then, based on the ability requirements, analysis work is carried out to extract stakeholder requirements at a higher abstract level, and the requirements of the analyzed system for each stakeholder are obtained, as shown in Figure 18 .
[0087] Thus, the modeling analysis process based on the mission-operation level is completed. The overall stakeholder requirements are stratified, and identified and interpreted from perspectives such as users, interest systems, and ability requirements. The requirements of the project system and the ability requirements of specific execution entities are extracted. The modeling analysis of this method clearly obtains the ability requirement results and stakeholder requirement results of the execution entity, as shown in Figure 7 , Figure 16 , Figure 18 respectively. In addition, the context architecture of the interest system and the interaction and correlation relationships between each execution entity are obtained, and important subsystems or functional devices required by the interest system are identified. The results obtained by this method are key factors in the MBSE analysis process and can provide guidance for the construction of subsequent system architecture models such as function, logic, and physical models.
[0088] The Mars rover requirement analysis and modeling method based on mission-operation solves the problem of whether the requirements are complete in the modeling process of the MBSE analysis method through multi-level and multi-perspective requirement identification, and ensures that the established model is more practical.
[0089] The above specific embodiments only describe the design principle of the present invention. The shapes and names of the components in this description can be different and are not limited. Therefore, those skilled in the art of the present invention can modify or equivalently replace the technical solutions recorded in the foregoing embodiments; and these modifications and replacements do not depart from the spirit and technical solutions of the present invention, and shall all fall within the protection scope of the present invention.
Claims
1. A multi-perspective dynamic analysis and modeling method for Mars rover requirements based on mission-operation, characterized by: This includes mission analysis and modeling processes and operational analysis and modeling processes, which generate demand analysis results and system models that can support the development and design of the Mars rover system; During the mission analysis and modeling process, the top-level mission is first broken down from the customer service dimension to identify the customers for the mission and the business objectives for measuring mission completion. The mission stages required to complete the top-level mission are then determined, along with the stakeholders and executing entities involved in each mission stage. The specific activities in each mission stage are analyzed to determine the capability requirements for completing all mission stages, and these capability requirements are then traced back to the corresponding executing entities. In the operation analysis and modeling process, the system with the most business objectives is obtained as the interest system; with the interest system as the analysis perspective, the interaction between the interest system and other execution entities and the execution entities within the interest system during the mission execution activities is analyzed; with the interest system's full life cycle model as the guide, the operation phases of the interest system are decomposed to obtain the internal execution entities and external execution entities of the interest system involved in each operation phase; then the activity processes of each operation phase are assigned to the corresponding execution entities, and capability requirements are further identified from the activities of the operation phase; finally, the stakeholder requirements corresponding to the top-level mission are summarized from the capability requirement results of the mission analysis and modeling and the motion analysis and modeling processes.
2. The method according to claim 1, wherein The mission analysis and modeling process includes: Step a1: Decompose the mission from the perspective of serving customers: Identify the customers for the input mission and the business objectives that will measure mission completion. Use Form x1 to describe the relationship between the mission, customers, and business objectives. Each mission must correspond to at least one customer and have at least one business objective. Step a2: Mission-Entity Traceability: Use business objectives to represent the mission, identify the execution entity corresponding to each business objective, ensure that each business objective is completed by an execution entity, and establish the relationship traceability matrix x2 between business objectives and execution entities; Step a3: Decompose the mission phases from the content dimension: determine the mission phases required to complete the mission, and construct a transition diagram x3 that describes the content of each mission phase and the transition events between mission phases; Step a4: Analyze the mission phases: For each mission phase, analyze the entities involved in achieving the mission phase tasks and analyze the execution process of each mission phase activity. Combine the activity process with the mission decomposition in step a3 to identify the capability requirements of the entire exploration project system. Construct a capability requirement analysis result x4 that describes the capability requirements, mission phases, and the expected effects of the execution activities. Step a5: Execution capability gap analysis: Based on the relationship between the capability requirements of the entire exploration project system and the execution entity, analyze whether each capability will be met and form a capability traceability matrix x5; Steps a1-a5 provide a route for mission-level demand analysis and modeling. The resulting graphs, tables, and matrices constitute the modeling results corresponding to the mission analysis. In step a4, the demand analysis result x4 of the mission analysis level is obtained.
3. The method according to claim 2, wherein In step a1, the relationship between mission, customer and business objectives is described using the requirement entry form ReqIF; In step a3, a state machine diagram in the SysML language is used for modeling, and the model describes the content of each mission stage and the transition events between mission stages; In step a4, a module definition diagram is established to represent the execution entity of each mission stage; an activity diagram is established to represent the execution process of the activities in each stage; and a list is used to describe the capability requirements, corresponding mission stages and expected results of the entire exploration project system.
4. The method according to claim 2, wherein In the step a4, when analyzing the execution entities involved in the realization of the mission phase tasks, the execution entities are decomposed into components.
5. The method according to claim 1, wherein The operational analysis and modeling process includes: Step b1: Analyze the system of interest: Based on the traceability relationship y1 between capability requirements and execution entities obtained during mission analysis and modeling, identify at least one execution entity or component under the execution entity with the closest capability requirements as the system of interest; construct a context structure diagram y2 of the system of interest to describe the affiliation between the components under the system of interest; perform the following steps b2-b5 for each system of interest: Step b2: Define the life cycle of the system of interest, construct a transition diagram y3 that describes the content of each life cycle phase and declares the transition events between life cycle phases; Step b3: Analyze the operation phase: From the perspective of the interest system, decompose the operation phase based on the content dimension, determine the execution events corresponding to the interest system in different operation phases and the transition process between each operation phase, and construct a transition diagram y4 to describe it; Step b4: For each operation phase, the operation interactions and activities of the interest system and other external related entities in the mission analysis phase, establish the association relationship y5 between the operation phase and the mission phase; Step b5: Stakeholder needs analysis: Based on the operational interactions and activity analysis during the operational phase, further identify new capability requirements y6, which are traced back to the internal execution entities of the system of interest to form a supplementary capability traceability matrix y7; Steps b1-b5 provide a route for operational level demand analysis and modeling. The resulting graphs, relationships, and matrices constitute the modeling results corresponding to the operational analysis. The results of the operational level demand analysis are obtained in b5.
6. The method according to claim 5, wherein In the step b1, the context structure diagram of the interest system is represented by a module diagram; In step b2, the entire life cycle of the system of interest is described using a state machine diagram; In step b3, a state machine diagram is used for modeling, and the model describes the content of each operation stage and the transition events between the operation stages; In the step b4, the construction of the association relationship: establishing a requirement entry form to determine the correspondence between the operation stage, the mission stage, and the life cycle stage of the system of interest; using a module definition diagram to identify the entities involved in each stage; establishing an internal module diagram to represent the operation interaction between the system of interest and external entities; and using an activity diagram to illustrate the implementation activities of the operation stage tasks.
Citation Information
Patent Citations
Model-based equipment system function demand analysis method
CN112527245A
