Deep space exploration task level demand analysis method

Abstract

The invention provides a deep space exploration task level demand analysis method, which comprises the steps of forming a task mission based on strategic planning, domestic and overseas trend development and engineering foundation; stage division and periodic task planning are carried out, benefit-related parties of the task are sorted, appeals of the benefit-related parties for the task are investigated, and a target system of the task is obtained based on task constraints; performing task scene analysis, task scene refinement, task capability analysis and task index analysis, and outputting a task capability system; carrying out capability clustering, capability index construction, system architecture design and system interface design to obtain a system architecture design model and a capability distribution model; and finally obtaining a deep space exploration task flow. According to the method, visual expression and analysis are carried out on deep space exploration mission and demands based on multiple views, initial design of deep space exploration mission tasks and system demands is achieved, then based on analysis of capability demands, a large system architecture is formed, initial logic design is completed, and finally a task-level demand model is formed.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a deep space exploration mission-level requirement analysis method. Background Art

[0002] The deep space exploration project is a complex system project that integrates demand analysis, overall design, and product development. Its development process is a spiral iterative process from top to bottom, from scratch, and from rough to fine. In addition to completing basic goals, deep space exploration missions also need to carry out research on related engineering technologies to lay a solid foundation for subsequent deep space exploration missions. This makes deep space exploration missions complex, engineering risks high, and overall implementation difficult, which puts forward higher requirements for the overall optimization of engineering overall design work, system coordination, inheritance, and innovation.

[0003] Faced with increasingly complex system engineering tasks, the traditional document-based task requirements analysis method may face at least the following problems: 1) Inaccurate information transmission: Information is transmitted between documents in the form of natural language text, which may lead to ambiguity 2) Complex information management: Deep space exploration missions are becoming increasingly complex, and the amount of information is growing explosively, leading to an increasing workload in managing related design parameters. 3) Difficulty in version control: When updating information in multiple documents, version inconsistencies are prone to occur, leading to confusion and errors, which is particularly common in large projects.

[0004] Obviously, there are a large number of mission-level requirements and design information interactions in each stage of deep space exploration missions, and the requirements for version iteration and information management are unprecedented. At present, there is a lack of mission-level requirements analysis methods for each stage of deep space exploration missions. Incomplete requirements analysis processes will lead to frequent rework, waste of resources, and extended development cycles.

[0005] Therefore, the present invention provides a method for analyzing deep space exploration mission-level requirements. Taking the new round of scientific and technological revolution and digital transformation as an opportunity, the present invention introduces model-based systems engineering, closely integrates it with deep space exploration missions, takes mission-level requirements analysis as the application background, actively explores and forms a new model of localized digital development, and improves the comprehensiveness of the overall engineering mission-level requirements analysis and capability planning through digital means. Summary of the invention

[0006] The purpose of the present invention is to provide a deep space exploration mission-level requirement analysis method in response to the deficiencies of the prior art. The method can use multiple views to visualize and analyze deep space exploration missions and requirements, realize the initial design and interactive verification of deep space exploration mission tasks and system requirements, and then form a large system architecture and complete preliminary logical design based on the analysis of capability requirements, and finally form a mission-level requirement model.

[0007] In a first aspect, the present invention provides a method for analyzing deep space exploration mission-level requirements, comprising the following steps: Step A: Mission analysis. This step takes the overall planning content of deep space exploration as input, combines the current and future expected international overall situation, domestic and international development trends, and existing research and mission results, completes the strategic planning analysis, domestic and international development trend analysis, and engineering foundation analysis of deep space exploration missions, and forms the mission of deep space exploration missions; Step B: Mission objective analysis. This step takes the mission of the deep space exploration mission in step A as input, completes the phase division and periodic mission planning of the deep space exploration mission, sorts out the stakeholders of the mission, and investigates the demands of the stakeholders for the mission. Then, based on the current mission constraints, all demands are analyzed and weighed as a whole to preliminarily obtain the mission objectives. Step C: Capability requirement analysis. This step uses the task objectives, task phases, and task constraints of step B as inputs to complete the task scenario analysis, task scenario refinement, task capability analysis, and task indicator analysis of the deep space exploration mission, obtain the main task scenarios and sub-scenario of each task phase, and finally output the corresponding task capability system. Step D: Preliminary design of mission architecture. Based on the analysis results of the mission capability system in step C, this step completes the capability clustering, capability indicator construction, overall system architecture design and system architecture interface design of the deep space exploration mission, and obtains the overall system architecture design model and capability allocation model. Step E: Preliminary design of the mission logic process, based on the tasks and task constraints of each stage obtained in step B, the mission capability system obtained in step C, and the overall system architecture design model and capability allocation model obtained in step D, finally realize the preliminary design of the entire mission process and obtain the deep space exploration mission process.

[0008] In a second aspect, the present invention provides a deep space exploration mission-level demand analysis system, comprising: Mission analysis module, responsible for mission analysis of deep space exploration missions; Mission objective analysis module, responsible for constructing mission objectives based on the mission of deep space exploration mission; Capability requirement analysis module, responsible for building a task capability system based on task objectives, task phases, and task constraints; The task architecture preliminary design module is responsible for designing the overall system architecture design model and capability allocation model based on the task capability system; The preliminary design module of the mission logic process is responsible for realizing the preliminary design of the entire mission process according to the tasks of each stage, mission constraints, mission capability system, overall system architecture design model, and capability allocation model to obtain the deep space exploration mission process.

[0009] In a third aspect, the present invention provides a computing device including a memory and a processor, wherein the memory stores executable code, and when the processor executes the executable code, the deep space exploration mission-level requirement analysis method is implemented.

[0010] The beneficial effects of the present invention are: The present invention integrates different aspects of deep space exploration missions into a unified model. By using models instead of natural language text, a more intuitive and structured system description is provided, which can effectively manage and organize a large amount of information. The model designed by the present invention makes information updates and version control more systematic and consistent. Since all information is concentrated in one model, the team can more easily track and manage version changes, avoid inconsistencies in multiple documents, and thus reduce confusion and errors.

[0011] In summary, the present invention integrates digital models to carry out model-based deep space exploration mission-level demand model construction, clarifies the technical route of demand analysis, and ensures the overall completeness of demand capture during the conceptual design period of the deep space exploration system. The present invention visualizes and analyzes deep space exploration missions and requirements based on multiple views, realizes the initial design of deep space exploration missions and system requirements, and then forms a large system architecture and completes the preliminary logical design based on the analysis of capability requirements, and finally forms a mission-level demand model. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 Flow chart of the method of the present invention.

[0013] Figure 2 Analyze requirements maps for strategic planning.

[0014] Figure 3 It is a demand map for domestic and international development trends.

[0015] Figure 4 This is a demand map of the overall international situation.

[0016] Figure 5 Requirement diagram for implementation of basic analysis.

[0017] Figure 6 Defines graphs for the mission analysis module.

[0018] Figure 7 It is the state machine diagram of the task stage.

[0019] Figure 8 Module definition diagram for the mission development phase.

[0020] Fig. 9 This is the internal module diagram of the mission development phase.

[0021] Fig.10Capture state machine diagrams for stakeholders.

[0022] Fig.11 Organize package diagrams for stakeholders.

[0023] Fig.12 Extract state machine diagrams for stakeholder demands.

[0024] Fig.13 Analyze the requirements graph for task constraints.

[0025] Fig.14 Determine the requirements graph for the mission objectives.

[0026] Fig.15 Analyze use case diagrams for task scenarios.

[0027] Fig.16 Refine the activity diagram for the task scenario.

[0028] Fig.17 Define graphs for the mission capability analysis module.

[0029] Fig.18 Define graphs for the task metrics analysis module.

[0030] Fig.19 Defines a graph for the capability clustering module.

[0031] Fig. 20 Define graphs for the task metrics analysis module.

[0032] Fig.21 This is a diagram that defines the preliminary architecture modules of the system.

[0033] Fig. 22 Analyze activity diagrams for interfaces.

[0034] Fig.23 This is the internal module diagram of the system interaction.

[0035] Fig.24 Analyze the state machine diagram for the flight scenario. DETAILED DESCRIPTION

[0036] The purpose, technical solutions and advantages of the present invention will be described clearly and completely below in conjunction with the accompanying drawings and embodiments. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0037] like Figure 1As shown, this embodiment provides a deep space exploration mission-level requirements analysis method. Taking the Artemis 3 mission as an example, by integrating the digital model, the model-based deep space exploration mission-level requirements model construction work is carried out, the technical route of the requirements analysis is clarified, and the overall completeness of the requirements capture during the conceptual design period of the deep space exploration system is ensured. Specifically, the following steps are included:

[0038] Step A: Mission analysis. This step takes the overall planning content of deep space exploration as input, combines the current and future expected international overall situation, domestic and international development trends, and existing research and mission results, completes the strategic planning analysis, domestic and international development trend analysis, and engineering foundation analysis of the deep space exploration mission, and forms the mission of the deep space exploration mission.

[0039] Step B: Mission objective analysis. This step uses the mission of the deep space exploration mission in step A as input, completes the phase division and periodic mission planning of the deep space exploration mission, sorts out the stakeholders of the mission, and investigates the demands of the stakeholders for the mission. Then, based on the current mission constraints, all demands are analyzed and weighed as a whole to preliminarily obtain the mission objectives. The current mission constraints include science, economy, politics, engineering, and environment. Step C: Capability requirement analysis. This step uses the task objectives, task phases, and task constraints of step B as inputs to complete the task scenario analysis, task scenario refinement, task capability analysis, and task indicator analysis of the deep space exploration mission, obtain the main task scenarios and sub-scenario of each task phase, and finally output the corresponding task capability system. Step D: Preliminary design of mission architecture. Based on the analysis results of the mission capability system in step C, this step completes the capability clustering, capability indicator construction, overall system architecture design and system architecture interface design of the deep space exploration mission, and obtains the overall system architecture design model and capability allocation model. Step E: Preliminary design of the mission logic process, based on the tasks and task constraints of each stage obtained in step B, the mission capability system obtained in step C, and the overall system architecture design model and capability allocation model obtained in step D, the preliminary design of the entire mission process is finally realized to obtain the deep space exploration mission process; The entire analysis process uses SysML state machine diagrams to carry the refined task implementation stages and relationships. Based on the obtained stage task requirements, each state is created and expressed by state elements; the execution flow between states is established using conversion relationships; after refining the entire task process, the deep space exploration task process is finally obtained; Step F: Demand summary, carrying the requirements analyzed in the first five stages to form an overall model framework.

[0040] Specifically, the step A comprises: Step A1: Conduct a strategic analysis of the overall planning content of deep space exploration. At the same time, combined with the stage of the deep space exploration mission, preliminarily formulate the general tasks to be completed by the deep space exploration project to form the required strategic plan; the entire analysis process uses the SysML requirement diagram and uses the custom element "Strategic Planning" to express the strategic plan; the analysis example is as follows Figure 2 As shown, these include "completing an unmanned lunar flight", "sending the first woman and an astronaut to the moon", "establishing a lunar space station", and "laying the foundation for future Mars exploration".

[0041] Step A2: Conduct an analysis of the current and future domestic and international development trends and the overall international situation of the development and planning of deep space exploration in relevant countries or organizations, so as to understand the overall development trend of deep space exploration in the world, and use this as a reference for the formulation of the country's deep space exploration mission plan; the entire analysis process uses the SysML requirement diagram; the custom elements "situation analysis, development trend" are used to express the current and future domestic and international development trends and the overall international situation, and the inclusion relationship is used to express the hierarchical relationship between the domestic and international development trends and the overall international situation; the analysis examples of "domestic and foreign development trends" are as follows: Figure 3 As shown in the figure, it includes "detection mode", "detection focus", "spatial movement", "key detection area", and "cooperation mode"; the analysis examples of "international overall situation" are as follows Figure 4 As shown, including "ESA", "South Korea", "Israel", "Russia", etc.

[0042] Step A3: Based on the existing deep space exploration project research and mission results, the mission objectives and key results of similar projects are used as description objects to conduct engineering basic analysis, and finally form the capability foundation of the current project; the entire analysis process uses SysML requirement diagrams, and uses the custom element "Model Mission" to express the code of the previous deep space exploration mission and the mission itself; The similar projects refer to the same series of deep space exploration projects; in this embodiment, the similar projects refer to Artemis 1 and 2 missions; the analysis example is as follows Figure 5 As shown, including "Artemis-1", "Artemis-2"; Step A4: With strategic planning as input, the overall international situation and domestic and international development trends as constraints, and the current engineering capability base as support, output the mission of the deep space exploration mission and construct the SysML module definition diagram of the mission analysis, see Figure 6 .

[0043] The analysis of domestic and international development trends in step A2 specifically explores the current development trend of deep space exploration from five dimensions: space movement, detection mode, detection focus, key detection area, and cooperation mode. The above-mentioned overall international situation analysis specifically takes the aerospace powers as the starting point, investigates the recent status of deep space exploration in various countries, and finally condenses the overall international situation of space exploration.

[0044] Specifically, the step B comprises: Step B1: Divide the mission implementation process of the deep space exploration mission into phased tasks, decompose complex tasks into relatively independent modules; the entire analysis process uses the SysML state machine diagram to carry the phase division results, where the state element expresses each phase under the task, and the conversion relationship expresses the execution logic between the phases; like Figure 7 , use the state machine diagram to carry the analysis results of Artemis 3, use the state elements to carry the four mission stages of launch, transfer, landing, and return, and use the conversion relationship to describe the conversion between the four stage states.

[0045] Step B2: Based on the characteristics and requirements of deep space exploration missions, the overall development cycle of deep space exploration missions is analyzed and the cycle and work items of each task development stage are clarified; the entire analysis process uses SysML module definition diagrams to define the overall composition of each task development stage and the key task attributes under each task development stage, where the custom element "module" is used to carry the overall task and each task development stage, the value attribute element carries the cycle and work items corresponding to each task development stage, and the composition relationship expresses that the overall task includes each task development stage; in addition, the SysML internal module diagram is used to describe the interaction of data between the various task development stages included in the deep space exploration mission, where the component attributes carry the development stages of each task that constitutes the deep space exploration mission, the value attributes carry the cycle and work items of each task development stage, and the project flow carries the data flow of each task development stage; like Figure 8 , use module elements to carry Artemis 3's mission and each mission development phase, including mission requirement analysis phase, feasibility demonstration phase, and program design phase; use value attribute elements to carry the corresponding cycles and work items of each phase; use composition relationships to describe the three mission development phases of Artemis 3; like Fig. 9 , using internal module diagrams to describe the data interaction between the various mission development stages included in Artemis 3, using component attributes to carry the various mission development stages that constitute the Artemis mission, using value attributes to carry the cycles and work items of each mission development stage, and using project flows to carry the data flows of each mission development stage, such as report documents, test data, etc. Specifically, it includes the transfer of general development requirements from the mission requirement analysis stage to the feasibility demonstration stage, and the transfer of feasibility demonstration reports from the feasibility demonstration stage to the scheme design stage.

[0046] Step B3: Identify the stakeholders involved based on the mission and task phases, and sort out and summarize all stakeholders by category; the entire analysis process uses SysML package diagrams to display stakeholders of the same category under each package element, where the executor element carries the stakeholders, and the association relationship expresses the relationship between the stakeholders and the relevant task phases; like Fig.10 , using executors to carry the captured scientists and research institutions as stakeholders, and using association relationships to describe that scientists and research institutions are connected to the four mission phases of launch, transfer, landing, and return; The summary results are as follows: Fig.11 shown.

[0047] Step B4: Based on the SysML state machine diagram in step B1, analyze all possible stakeholder demands based on the task stages associated with stakeholders; the entire analysis process uses the SysML requirement diagram, in which the custom element "Requirement" expresses the stakeholder demands, and the association relationship expresses the relationship between stakeholders and stakeholder demands; like Fig.12 ,Through analyzing the task process and the stakeholders associated with it, the demand elements are used to represent the demands such as “sample analysis and research”, and the association is used to express that the demand of sample analysis and research is the demand of the stakeholders such as scientists and research institutions; Step B5: By considering the five major task constraints of politics, economy, science, engineering, and environment under the current situation, the stakeholder demands obtained in step B4 are refined and screened to obtain the currently achievable stakeholder demands; the entire analysis process uses the SysML requirement diagram to carry the task constraints and achievable stakeholder demands, in which the custom element "Requirement" expresses the content of political, economic, scientific, engineering, environmental constraints and achievable stakeholder demands, and the included relationship represents the architectural relationship of task constraints or achievable stakeholder demands; like Fig.13 , use the demand graph to carry the contents of the five major constraints, namely political constraints, economic constraints, and scientific constraints, during the task process. For example, the demand elements are used to describe scientific constraints, including sampling requirements, and sampling requirements include constraints such as permanent preservation samples, popular science samples, and scientific research samples.

[0048] Step B6: Taking the stakeholders sorted out in step B3 and the demands of stakeholders in step B4 as input and the task constraints analyzed in step B5 as guidance, we finally get the technically feasible task objectives. The entire analysis process uses the SysML requirement diagram to describe the task objective architecture, in which the custom element "Requirement" carries the task objectives and contains the architectural relationships that describe the task objectives. The task objectives include two categories: scientific objectives and engineering objectives.

[0049] like Fig.14 , use the requirement elements to carry the task objectives, engineering objectives, and scientific objectives, and use the inclusion relationship to describe the overall structure of the task objectives, such as the task objectives include engineering objectives and scientific objectives.

[0050] Specifically, the step C comprises: Step C1: According to the task objectives of step B, capture the core main scenes required for each task stage from the perspective of task realization, and finally form the main scene set for each task stage; The entire analysis process uses SysML use case diagrams to present the analysis results, using module elements to describe the main scenario set, and use case elements to represent the main scenarios at each stage; like Fig.15 The main work scenarios of Artemis 3 during the landing phase include: soft landing in the designated area, astronaut exit from the vehicle, extravehicular activities and takeoff.

[0051] Step C2: Taking the main mission scenario of step C1 as input, the main mission scenario is expanded and analyzed according to the task constraints of step B to form a key mission profile, roughly restore the logical flow of each mission stage of deep space exploration, and finally output the sub-scenario under each main scenario; The entire analysis process presents the refinement process of each main scenario through SysML activity diagrams, where activity elements express the ability to implement the main scenario of the task; "call behavior action" elements express the sub-scenario under each main scenario, control flow elements express the execution order of sub-scenario, object flow expresses the medium interaction relationship between sub-scenarios, and bolts represent the input and output of sub-scenario; the task process can be refined step by step until it can fully express the capabilities of the relevant systems in the current scenario; The soft landing scenario in a certain area is refined as follows: Fig.16 As shown in the figure, the main logic line of the main scene is to execute "braking and descent, landing point confirmation and vertical landing" in sequence from the "pre-landing preparation" sub-scene. The four sub-scenes all involve "Starship HLS measurement and control (input) and data monitoring and processing (output)" during execution. The model expression uses the "call behavior action" element to express the sub-scene under "predetermined area soft landing", the control flow element to express the execution order of the sub-scenes, and the object flow to express the medium interaction relationship between the sub-scenes.

[0052] Step C3: Taking the sub-scenario obtained in step C2 as input and the task constraint in step B as the analysis support, the analysis is carried out from the scene, activity, capability and system architecture levels to obtain the refined capability indicators; the entire analysis process is carried out by the SysML module definition diagram to carry the capability indicator analysis process, using the custom element "Capability" to express the capability of the task scenario, the module element to express the system architecture, and the refined relationship to express the association between the sub-scenario and the capability, so as to meet the relationship expression capability and the association between each system architecture; like Fig.17 Based on the sub-scenario set under the landing mission work scenario "soft landing in the predetermined area, astronauts leaving the spacecraft, extravehicular activities, and take-off and ascent", the capabilities supporting the realization of the sub-scenario are analyzed, and the system architecture that meets the capabilities is analyzed. For example, based on the sub-scenario of "pre-landing preparation, braking and descent, landing point confirmation, and vertical landing", the "pre-landing preparation, soft landing deceleration, attitude adjustment, obstacle detection and avoidance, pre-landing hovering, and landing capabilities" are refined respectively, and the above capabilities are analyzed to be realized by Starship HLS.

[0053] Step C4: Also using the sub-scenario obtained in step C2 as input and the task constraints in step B as analysis support items, the analysis is carried out from three levels: system architecture, capability, and derived indicators. The requirements covered by the capability and the quantifiable requirement indicators are obtained through analysis. The entire analysis process is carried out by the SysML module definition diagram to carry out the task indicator analysis process, the custom element "Customized Requirements" expresses the indicators analyzed by the capability, tracks the association between the relationship expression capability and the derived indicators, and refines the relationship expression derived indicators.

[0054] like Fig.18 , based on the capabilities of the space launch system, the analysis obtains indicators derived from the support to achieve the corresponding capabilities, such as analyzing indicators such as "fairing specifications" based on "rocket assembly capabilities".

[0055] Specifically, the step D comprises: Step D1: Taking the result of the task capability analysis in step C as input, based on the relationship between activity elements and lane elements, sort out the capability items of each system architecture of the deep space exploration project, and send them to each system architecture in the form of module attributes, which serve as the capability input at the system design level; the entire analysis process uses the SysML module definition diagram to present all capabilities, assigns the capabilities to the corresponding devices of each system architecture, and uses the satisfaction relationship to indicate that a certain capability can be satisfied by the device of a certain system architecture; the effect of capability clustering is as follows: Fig.19 As shown; The device refers to a specific device or component in each system architecture; Step D2: Taking the result of the task indicator analysis in step C as input, based on the allocation result of the capability in step D1, the quantitative requirement indicators of the item nature are carried in the form of module value attributes to form an indicator system and send it to the corresponding system architecture; the entire analysis process uses the traceability diagram to represent the allocation relationship between the system architecture and the capability, as well as the mapping relationship between the capability-derived indicator requirements, and uses the SysML module definition diagram to describe the carrying process of the capability indicator, converting the itemized performance requirements in the requirements into the value attribute carrying of the modules of each system architecture, and using the satisfaction relationship to associate the value attribute with the requirement model to form a traceability; like Fig. 20 , where the itemized performance requirements such as "target orbit" are converted into value attributes of the space launch system module, and the value attributes are associated with the requirement model using a satisfying relationship to form a traceability, indicating that the capability indicator requirements are satisfied by the value attributes under the space launch system.

[0056] Step D3: Using the results of the task capability analysis in step C as input, summarize the system architecture based on the realization of the corresponding capabilities; the entire analysis process uses the SysML module definition diagram to summarize the capabilities using the satisfaction relationship, intuitively displaying the magnitude and satisfaction of the capabilities at each level, and summarize the indicator system of D2 through composition association to form the overall system preliminary architecture; like Fig.21 , where the composition relationship shows that the Artemis mission system is composed of Starship HLS, Orion spacecraft, Lunar Gateway, and Space Launch System.

[0057] Step D4: Through the analysis results of the refined mission scenario in step C, the interactive relationship between the various system architectures of deep space exploration is obtained, so as to extract the interface relationship and transmission content that should exist between the various system architectures, and refine the system architecture to obtain the interface design model between the system architectures; the entire analysis process uses the "swimlane" element to analyze and identify the actions and logic performed by each system architecture, as well as the object flow transmitted between the system architectures in the SysML activity diagram; the module definition diagram is used to carry the interface definition results, in which the "interface module" element expresses the interface, the "flow attribute" expresses the internal medium of the interface, and the "module" element defines the type of the internal medium; the SysML internal module diagram is used to carry the interaction between the various system architectures, in which the "proxy port" element defines the system's own external interface, the "connector" element associates multiple interfaces that interact, and the "interface module" element defines the properties of each interface.

[0058] like Fig. 22 , which expresses the allocation of each sub-scenario in the pre-launch test scenario, that is, the actions and logic performed by each system, and the flow of objects transferred between systems.

[0059] like Fig.23 , expressing the interface types between the Orion spacecraft and the space launch system, which mainly include: mechanical interface, communication interface and electrical interface. The mechanical interface includes the connecting bolts between the two systems and the separation springs that ensure the reliable separation of the two systems; the communication interface includes the separation instructions for unlocking the two systems and related telemetry signals; the electrical interface includes the necessary power supply and cables to support the separation of the two systems, and the electrical connection of the two systems on the launch pad "separation plug, umbilical cable and relay antenna".

[0060] Step E: Fig.24The Artemis 3 flight plan includes four major stages: launch, transfer, landing and return. The launch stage can be subdivided into launch preparation, launch flight and entry into low Earth orbit according to the process; the transfer stage can be subdivided into orbit enhancement, orbit transfer and flight according to the process; the landing stage can be subdivided into rendezvous and docking stage, landing and descent stage, land work stage and land ascent stage according to the process; the return stage can be subdivided into rendezvous and docking stage, waiting stage, transfer stage, return to Earth stage and landing stage according to the process.

[0061] Step F: Demand summary, carrying the requirements analyzed in the first five stages to form an overall model framework.

[0062] The above embodiments are only for the purpose of describing the present invention, and are not intended to limit the scope of the present invention. The scope of the present invention is defined by the appended claims. Various equivalent substitutions and modifications made without departing from the spirit and principle of the present invention should be included in the scope of the present invention.

Claims

1. A deep space exploration mission-level requirements analysis method, characterized in that: The steps include: Step A: Mission analysis. This step takes the overall planning content of deep space exploration as input, combines the current and future expected international overall situation, domestic and international development trends, and existing research and mission results, completes the strategic planning analysis, domestic and international development trend analysis, and engineering foundation analysis of deep space exploration missions, and forms the mission of deep space exploration missions; Step B: Mission objective analysis. This step takes the mission of the deep space exploration mission in step A as input, completes the phase division and periodic mission planning of the deep space exploration mission, sorts out the stakeholders of the mission, and investigates the demands of the stakeholders for the mission. Then, based on the current mission constraints, all demands are analyzed and weighed as a whole to preliminarily obtain the mission objectives. Step C: Capability requirement analysis. This step uses the task objectives, task phases, and task constraints of step B as inputs to complete the task scenario analysis, task scenario refinement, task capability analysis, and task indicator analysis of the deep space exploration mission, obtain the main task scenarios and sub-scenario of each task phase, and finally output the corresponding task capability system. Step D: Preliminary design of mission architecture. Based on the analysis results of the mission capability system in step C, this step completes the capability clustering, capability indicator construction, overall system architecture design and system architecture interface design of the deep space exploration mission, and obtains the overall system architecture design model and capability allocation model. Step E: Preliminary design of the mission logic process, based on the tasks and task constraints of each stage obtained in step B, the mission capability system obtained in step C, and the overall system architecture design model and capability allocation model obtained in step D, finally realize the preliminary design of the entire mission process and obtain the deep space exploration mission process.

2. The method according to claim 1, characterized in that The step A comprises: Step A1: Conduct a strategic analysis of the overall planning content of deep space exploration. Combined with the current stage of the deep space exploration mission, preliminarily formulate the general tasks to be completed by the deep space exploration project to form the required strategic plan. The entire analysis process uses the SysML requirement diagram, in which the custom element "Strategic Plan" expresses the strategic plan. Step A2: Conduct an analysis of the current and future domestic and international development trends and the overall international situation of the development and planning of deep space exploration, so as to understand the overall development trend of global deep space exploration and use it as a reference for the formulation of the country's deep space exploration mission plan; the entire analysis process uses the SysML requirement diagram, in which the custom elements "situation analysis, development trend" respectively express the current and future domestic and international development trends and the overall international situation, and the inclusion relationship represents the hierarchical relationship between the domestic and international development trends and the overall international situation; Step A3: Based on the existing deep space exploration project research and mission results, the project basic analysis is carried out with the mission objectives and key results of similar projects as the description objects, and finally the capability foundation of the current project is formed; the entire analysis process adopts the SysML requirement diagram, in which the custom element "Model Mission" expresses the code of the previous deep space exploration mission and the mission itself; Step A4: With strategic planning as input, the overall international situation and domestic and international development trends as constraints, and the current engineering capability base as support, output the mission of the deep space exploration mission and construct a SysML module definition diagram for mission analysis.

3. The method according to claim 2, characterized in that The analysis of domestic and international development trends in step A2 specifically explores the current development trend of deep space exploration from five dimensions: space movement, detection mode, detection focus, key detection area, and cooperation mode; The above-mentioned overall international situation analysis specifically takes the aerospace powers as the starting point, investigates the recent status of deep space exploration in various countries, and finally condenses the overall international situation of space exploration.

4. The method according to claim 1, characterized in that: The current task constraints described in step B include scientific, economic, political, engineering, and environmental constraints.

5. The method according to claim 1 or 4, characterized in that The step B comprises: Step B1: Divide the mission implementation process of the deep space exploration mission into phased tasks, decompose complex tasks into relatively independent modules; the entire analysis process uses the SysML state machine diagram to carry the phase division results, where the state element expresses each stage under the task, and the conversion relationship expresses the execution logic between stages; Step B2: Based on the characteristics and requirements of deep space exploration missions, the overall development cycle of deep space exploration missions is analyzed and the cycle and work items of each task development stage are clarified; the SysML module definition diagram is used in the entire analysis process to define the overall composition of each task development stage and the key task attributes under each task development stage, where the custom element "module" is used to carry the overall task and each task development stage, the value attribute element carries the cycle and work items corresponding to each task development stage, and the composition relationship expresses that the overall task includes each task development stage; in addition, the SysML internal module diagram is used to describe the interaction of data between the various task development stages included in the deep space exploration mission, where the component attribute carries the development stages of each task that constitutes the deep space exploration mission, the value attribute carries the cycle and work items of each task development stage, and the project flow carries the data flow of each task development stage; Step B3: Identify the stakeholders involved based on the mission and task phases, and sort out and summarize all stakeholders by category; the entire analysis process uses SysML package diagrams to display stakeholders of the same category under each package element, where the executor element carries the stakeholders, and the association relationship expresses the relationship between the stakeholders and the relevant task phases; Step B4: Based on the SysML state machine diagram in step B1, analyze all possible stakeholder demands based on the task stages associated with stakeholders; the entire analysis process uses the SysML requirement diagram, in which the custom element "Requirement" expresses the stakeholder demands, and the association relationship expresses the relationship between stakeholders and stakeholder demands; Step B5: By considering the current task constraints, the stakeholder demands obtained in step B4 are refined and screened to obtain the currently achievable stakeholder demands. The entire analysis process uses the SysML requirement diagram to carry the task constraints and achievable stakeholder demands, where the custom element "Requirement" expresses the content of the task constraints and achievable stakeholder demands, and the containment relationship represents the architectural relationship of the task constraints or achievable stakeholder demands. Step B6: Taking the stakeholders sorted out in step B3 and the demands of stakeholders in step B4 as input and the task constraints analyzed in step B5 as guidance, we finally get the technically feasible task objectives. The entire analysis process uses the SysML requirement diagram to describe the task objective architecture, in which the custom element "Requirement" carries the task objectives and contains the architectural relationships that describe the task objectives. The task objectives include two categories: scientific objectives and engineering objectives.

6. The method according to claim 1, characterized in that The step C comprises: Step C1: According to the task objectives of step B, capture the core main scenes required for each task stage from the perspective of task realization, and finally form the main scene set for each task stage; The entire analysis process uses SysML use case diagrams to present the analysis results, using module elements to describe the main scenario set, and use case elements to represent the main scenarios at each stage; Step C2: Taking the main mission scenario of step C1 as input, the main mission scenario is expanded and analyzed according to the task constraints of step B to form a key mission profile, roughly restore the logical flow of each mission stage of deep space exploration, and finally output the sub-scenario under each main scenario; The entire analysis process presents the refinement process of each main scenario through SysML activity diagrams, where activity elements express the ability to implement the main scenario of the task; "call behavior action" elements express the sub-scenario under each main scenario, control flow elements express the execution order of sub-scenario, object flow expresses the medium interaction relationship between sub-scenarios, and bolts represent the input and output of sub-scenario; the task process can be refined step by step until it can fully express the capabilities of the relevant systems in the current scenario; Step C3: Taking the sub-scenario obtained in step C2 as input and the task constraint in step B as the analysis support, the analysis is carried out from the perspectives of scenario, activity, capability and system architecture to obtain the refined capability index. The entire analysis process is carried out by the SysML module definition diagram. The custom element "Capability" is used to express the capability of the task scenario, the module element is used to express the system architecture, and the relationship between the sub-scenario and the capability is expressed by the refined relationship, so as to meet the relationship between the capability expression and each system architecture. Step C4: Taking the sub-scenario obtained in step C2 as input and the task constraint in step B as the analysis support item, the analysis is carried out from three levels: system architecture, capability and derived indicators, and the requirements covered by the capability and the quantifiable requirement indicators are obtained through analysis; the entire analysis process is carried out by the SysML module definition diagram to carry out the task indicator analysis process, the custom element "Customized Requirements" expresses the indicators analyzed by the capability, tracks the association between the relationship expression capability and the derived indicators, and refines the relationship expression derived indicators.

7. The method according to claim 1, characterized in that The step D comprises: Step D1: Taking the result of the task capability analysis in step C as input, based on the relationship between activity elements and lane elements, sort out the capability items of each system architecture of the deep space exploration project, and send them to each system architecture in the form of module attributes, which will serve as the capability input at the system design level; the entire analysis process uses SysML module definition diagrams to present all capabilities, assign capabilities to the corresponding tools of each system architecture, and use satisfaction relationships to indicate that a certain capability can be satisfied by the tools of a certain system architecture; Step D2: Taking the result of the task indicator analysis in step C as input, based on the allocation result of the capability in step D1, the quantitative requirement indicators of the item nature are carried in the form of module value attributes to form an indicator system and send it to the corresponding system architecture; the entire analysis process uses the traceability diagram to represent the allocation relationship between the system architecture and the capability, as well as the mapping relationship between the capability-derived indicator requirements, and uses the SysML module definition diagram to describe the carrying process of the capability indicator, converting the itemized performance requirements in the requirements into the value attribute carrying of the modules of each system architecture, and using the satisfaction relationship to associate the value attribute with the requirement model to form a traceability; Step D3: Using the results of the task capability analysis in step C as input, summarize the system architecture based on the realization of the corresponding capabilities; the entire analysis process uses the SysML module definition diagram to summarize the capabilities using the satisfaction relationship, intuitively displaying the magnitude and satisfaction of the capabilities at each level, and summarize the indicator system of D2 through composition association to form the overall system preliminary architecture; Step D4: Through the analysis results of the refined mission scenario in step C, the interactive relationship between the various system architectures of deep space exploration is obtained, so as to extract the interface relationship and transmission content that should exist between the various system architectures, and refine the system architecture to obtain the interface design model between the system architectures; the entire analysis process uses the "swimlane" element to analyze and identify the actions and logic performed by each system architecture, as well as the object flow transmitted between the system architectures in the SysML activity diagram; the module definition diagram is used to carry the interface definition results, in which the "interface module" element expresses the interface, the "flow attribute" expresses the internal medium of the interface, and the "module" element defines the type of the internal medium; the SysML internal module diagram is used to carry the interaction between the various system architectures, in which the "proxy port" element defines the system's own external interface, the "connector" element associates multiple interfaces that interact, and the "interface module" element defines the attributes of each interface.

8. The method according to claim 1, characterized in that: In step E, the entire analysis process uses the SysML state machine diagram to carry the refined task implementation stages and relationships. Based on the obtained stage task requirements, each state is created and expressed by state elements; The execution flow between states is established by using conversion relations; after refining the entire mission process, the deep space exploration mission process is finally obtained.

9. A deep space exploration mission-level requirements analysis system implementing the method described in any one of claims 1 to 8, characterized in that include: Mission analysis module, responsible for mission analysis of deep space exploration missions; Mission objective analysis module, responsible for constructing mission objectives based on the mission of deep space exploration mission; Capability requirement analysis module, responsible for building a task capability system based on task objectives, task phases, and task constraints; The task architecture preliminary design module is responsible for designing the overall system architecture design model and capability allocation model based on the task capability system; The preliminary design module of the mission logic process is responsible for realizing the preliminary design of the entire mission process according to the tasks of each stage, mission constraints, mission capability system, overall system architecture design model, and capability allocation model to obtain the deep space exploration mission process.

10. A computing device, comprising a memory and a processor, wherein the memory stores executable codes, and when the processor executes the executable codes, the method according to any one of claims 1 to 8 is implemented.

Images