Deep space exploration task forward collaborative design method

Abstract

The invention discloses a deep space exploration task forward collaborative design method, and belongs to the technical field of deep space exploration. According to the method, on the basis of a MagicGrid methodology and in combination with a SysML modeling language, a'concept-problem-scheme 'three-level incremental iterative modeling framework is constructed, and full-process digital collaboration from task analysis to subsystem design is achieved. Through four-pillar linkage of demands, behaviors, structures and parameters, automatic association of model elements and design traceability are ensured, and demand verification efficiency and design consistency are significantly improved. Meanwhile, FMEA reliability analysis is embedded into a design process, model issuing, subsystem design and integration processes are standardized in collaborative development, and internal and external division cooperation is supported. According to the method, a standardized and reusable forward design solution is provided for a complex spacecraft system, and the method has high engineering popularization value.

Description

Technical Field

[0001] This invention belongs to the field of deep space exploration technology, specifically relating to a forward collaborative design method for deep space exploration missions. Background Technology

[0002] Traditional spacecraft development often employs text-based systems engineering methods, relying on natural language descriptions and discrete documents to convey system information. While this approach offers flexible and highly readable information expression, it has significant limitations: in the iterative process of complex systems, it is difficult to ensure consistency of information between documents, traceability is challenging, ambiguity can easily arise, leading to iterative design, low collaboration efficiency, and severely hindering the correctness of system design and development progress.

[0003] As space missions become increasingly complex, deep space exploration tasks place higher demands on spacecraft reliability, system integration, and multidisciplinary collaboration. Traditional text-driven models are no longer adequate for the refined, digitalized, and collaborative needs of modern spacecraft development.

[0004] Model-based systems engineering (MBSE) has emerged, using formal modeling languages ​​at its core. It replaces traditional documents with graphical models to describe systems from multiple levels and perspectives, establishing relationships between model elements and effectively solving problems of information consistency and traceability. SysML, as a widely supported standardized modeling language for MBSE, provides strong support for the unified expression of system requirements, structure, behavior, and parameters.

[0005] However, the application of the general MBSE method in the aerospace field still faces challenges: how to combine the characteristics of spacecraft development to construct a complete modeling process covering mission analysis, system design, and subsystem collaboration; how to achieve seamless requirement transfer and indicator decomposition from the overall system to subsystems and then to individual units; and how to embed reliability analysis in the early stages of design to achieve fault prevention. Therefore, there is an urgent need for a new systems engineering method that can achieve information structuring, correlation visualization, and process traceability. Summary of the Invention

[0006] To address the aforementioned technical challenges, this invention provides a forward collaborative design method for deep space exploration missions. It constructs a three-tiered incremental iterative modeling framework—"concept-problem-solution"—enabling end-to-end digital collaboration from mission analysis to subsystem design. Through the linkage of four pillars—requirements, behavior, structure, and parameters—automatic association of model elements and design traceability are ensured, significantly improving the efficiency of requirement verification and design consistency. Simultaneously, FMEA (Failure Mode and Effects Analysis) reliability analysis is embedded into the design process, standardizing model distribution, subsystem design, and integration processes during collaborative development, supporting internal and external division of labor and collaboration.

[0007] To achieve the above objectives, the present invention adopts the following technical solution:

[0008] A forward collaborative design methodology for deep space exploration missions includes:

[0009] Step 1: Based on the MagicGrid methodology, construct an incremental iterative modeling framework covering the concept layer, problem layer, and solution layer;

[0010] Step 2: At the conceptual layer, the spacecraft system is treated as a black box. Mission environment interaction analysis, mission profile analysis, and top-level parameter analysis are performed. SysML requirement diagrams, use case diagrams, activity diagrams, and parameter diagrams are used to transform stakeholder requirements into system functions, interfaces, and top-level performance indicators. A mission analysis model is established to trace the overall requirements.

[0011] Step 3: At the problem layer, the spacecraft system is treated as a white box. Based on the mission analysis model, the system functions are decomposed, the architecture is designed, and the indicators are decomposed downward to generate subsystem technical requirements and establish a traceability relationship between the system design model and the system requirements.

[0012] Step 4: At the solution layer, the technical requirements of the subsystems are distributed in the form of models. Each subsystem designs its internal architecture, functions and indicators based on the distributed models. After the subsystem modeling is completed, the subsystem models are submitted and integrated.

[0013] In a second aspect, the present invention provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs; wherein, when the one or more programs are executed by the one or more processors, the one or more processors implement the aforementioned forward collaborative design method for deep space exploration missions.

[0014] Thirdly, the present invention provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enable the processor to implement the aforementioned forward collaborative design method for deep space exploration missions.

[0015] The beneficial effects of this invention are as follows:

[0016] Enhance design consistency and traceability: By using SysML modeling, the entire process of requirements, functions, structure and parameters is digitally linked and automatically associated, which effectively solves the problems of information dispersion and traceability difficulties in traditional text engineering, ensuring that the design process strictly follows the top-level requirements and greatly reducing design rework caused by misunderstandings.

[0017] Enhanced collaborative development efficiency: A standardized modeling and distribution integration process covering the mission level, system level, and subsystem level has been established, supporting parallel design and model collaboration among multiple departments and disciplines. The model transfer, integration, and verification mechanisms have been clarified, significantly improving internal and external collaboration efficiency and data consistency.

[0018] Achieve integration of reliability analysis and design: Embed FMEA analysis into each design phase (concept, function, hardware) to enable early identification of failure modes and design feedback, capture and verify reliability requirements at the model level, and improve the inherent reliability of the system from the design source.

[0019] Supports simulation verification and automated calculation of indicators: By integrating with parametric graphs and external simulation tools (such as Matlab), it enables automated calculation and verification of key performance indicators, supports multi-scheme trade-offs and performance simulations during the design phase, and improves the scientificity and efficiency of design decisions.

[0020] It provides a standardized and reusable methodology: it has formed a positive design paradigm applicable to the development of complex spacecraft, with strong scalability and engineering applicability, and provides a collaborative design solution that can be referenced for the efficient and high-quality implementation of similar missions. Attached Figure Description

[0021] Figure 1 A schematic diagram of the three-tier modeling framework;

[0022] Figure 2 Schematic diagram for task analysis modeling;

[0023] Figure 3 Design the schematic diagram for the system scheme. Detailed Implementation

[0024] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0025] This invention provides a forward collaborative design method for deep space exploration missions, the method comprising:

[0026] Step 1: Establish a three-tier modeling framework: Based on the MagicGrid methodology, construct an incremental iterative modeling framework covering the concept layer, problem layer, and solution layer;

[0027] Step 2, Task Analysis Phase: At the conceptual layer, the spacecraft system is treated as a black box. Task environment interaction analysis, task profile analysis, and top-level parameter analysis are performed. SysML requirement diagrams, use case diagrams, activity diagrams, and parameter diagrams are used to transform stakeholder requirements into system functions, interfaces, and top-level performance indicators. A task analysis model is established to trace the overall requirements.

[0028] Step 3, System Solution Design Phase: At the problem level, the spacecraft system is treated as a white box. Based on the mission analysis model, system function decomposition, architecture design, and indicator decomposition are carried out to generate subsystem technical requirements and establish a traceability relationship between the system design model and system requirements.

[0029] Step 4, Collaborative Distribution and Subsystem Design: At the solution layer, the technical requirements of the subsystems are distributed in the form of models. Each subsystem designs its internal architecture, functions and indicators based on the distributed models. After the subsystem modeling is completed, the subsystem models are submitted and integrated.

[0030] Step 5, Integration Verification and FMEA Analysis: In the subsystem model integration phase, conduct comprehensive verification of structure, behavior and indicators, and embed FMEA analysis into each design phase. Conduct concept FMEA in the concept phase, functional FMEA in the functional analysis phase, and hardware FMEA in the design synthesis phase to achieve deep integration of reliability requirements and forward design process.

[0031] Specifically, in step 1:

[0032] Based on the MagicGrid methodology, an incremental iterative modeling framework covering the concept layer, problem layer, and solution layer is constructed. For example... Figure 1 As shown, this framework is supported by the four pillars of MBSE (Requirements, Behaviors, Structure, and Parameters). By building and iterating system models, it integrates and synthesizes core steps in systems engineering, such as requirements analysis, function definition, logical design, and physical implementation, thereby forming a standardized forward design process. This framework serves as the top-level guide and organizational form for all subsequent specific design activities.

[0033] In step 2:

[0034] At the conceptual level, such as Figure 2 As shown, the entire spacecraft system is treated as a black box, focusing on its interaction with the external environment and top-level mission requirements, without considering its internal implementation details.

[0035] First, the overall mission requirements of the spacecraft (including functional, performance, interface, technical specifications, and product assurance requirements) are itemized and entered into the system, and then transformed into a SysML graphical requirement model as the top-level input for the design. These requirements are captured as Requirement elements in SysML, forming a structured requirement system.

[0036] Then, based on the overall requirements, a mission environment interaction analysis is conducted. The spacecraft's operating environment (system context) is defined, all external systems interacting with the spacecraft (such as ground control stations, launch vehicles, ground data processing centers, user terminals, etc.) are identified, and system boundaries are clarified. By creating a mission environment definition diagram and internal module diagrams, the connection relationships between the spacecraft and external systems are illustrated.

[0037] Next, mission profile and business scenario analysis are conducted based on flight mission scenarios. SysML use case diagrams are used to define mission profiles for different phases (such as launch-to-orbit phase, on-orbit operation phase, etc.), describing the tasks the system needs to complete in a specific phase. For each mission profile use case, activity diagrams are further used for decomposition, with swimlanes representing the participating systems (including the spacecraft itself and external systems), activities representing the functions performed by each system, and object flows representing the energy, matter, or signals exchanged between systems. In this way, the specific execution flow of each mission phase is described in detail.

[0038] Simultaneously, top-level indicator analysis is conducted. Non-functional requirements (such as performance and reliability indicators) within the overall requirements are analyzed, and value attributes are established in the model to capture and define the top-level performance parameter requirements of the spacecraft system.

[0039] Finally, at the end of the task analysis phase, a task-level traceability relationship must be established. By creating a traceability matrix, the specific fulfillment and refinement relationships of various design model elements (such as activities, ports, and value attributes) generated during the task analysis phase with the overall top-level requirements are clarified. This includes: functional requirements being refined from activity elements; interface requirements being refined from port elements; and performance indicator requirements being refined from value attributes. This traceability ensures consistency between the design source and the top-level requirements.

[0040] In step 3:

[0041] like Figure 3 As shown, at the problem layer, the spacecraft system is treated as a white box, its internal structure is opened, and functional decomposition and architectural design are carried out to solve the problem of how to achieve the top-level requirements.

[0042] First, capture system design requirements. Formally capture and transform the system-level functions (corresponding activity elements), interfaces (port elements), and metrics (value attributes) output from the task analysis phase into explicit system design requirement items, forming a system requirement table as the design input for this phase. Simultaneously, establish a two-way traceability relationship between these system requirements and the elements of the upper-level task analysis model, as well as the original overall requirements.

[0043] Next, system architecture design is carried out. Based on actual business and design experience, the subsystems that make up the spacecraft are defined, and a system architecture diagram is created. Based on this architecture, and on the basis of subsequent functional analysis, detailed interaction diagrams between the subsystems are created, clarifying the interfaces and connections between each subsystem.

[0044] Next, system function analysis is conducted. For system-level functions inherited from the task layer that require further decomposition, activity diagrams are created for detailed breakdown. The analysis examines how the various subsystems should collaborate to complete the function, progressively decomposing the function to the subsystem level. Through functional analysis, the system's logical architecture can be clarified and optimized.

[0045] Simultaneously, subsystem performance metrics are decomposed. System-level performance metrics are broken down and assigned to each subsystem according to design rules and business inputs. Performance metric requirements for each subsystem are clarified by defining value attributes for each subsystem.

[0046] After completing the system design, a system design traceability relationship must be established. A traceability matrix should be created for all design outputs at this stage (including refined functions, subsystem structures, internal interfaces, and allocated parameters) to the system design requirements, ensuring that the design solution fully covers and meets system-level requirements.

[0047] In step 4:

[0048] At the solution level, the technical requirements for each subsystem generated from the system-level design are distributed to the corresponding subsystem design departments for detailed solution design and to form specific implementation solutions.

[0049] First, the model is distributed. Following established distribution principles (e.g., inheritance for modules, copying for functions, and itemized requirements for metrics), the system model portion containing the subsystem's technical requirements is exported and distributed to each subsystem. Subsystem designers then develop detailed designs based on the received model, maintaining the model's organizational structure.

[0050] Taking the electric propulsion subsystem as an example, its detailed design process includes:

[0051] Subsystem Requirements Capture: Extract design information related to the electric propulsion subsystem from the issued system model (such as the functional activities that the subsystem should perform, external interface ports, and allocated performance index values), and combine it with other business requirements to form a detailed requirements table for the subsystem.

[0052] Subsystem Architecture Design: Define the individual components within the electric propulsion subsystem and create a subsystem architecture diagram. Then analyze the interactions between these individual components, create an inter-component interaction diagram, and clarify the individual component interfaces.

[0053] Subsystem Functional Analysis: The functions that the subsystem needs to implement are broken down into detailed components. Activity diagrams are used to analyze how each unit collaborates to complete these functions, and the functions are assigned to specific units.

[0054] Subsystem metric decomposition: The subsystem metrics are further decomposed to their respective individual units, and detailed parameters for each unit are defined.

[0055] Unit Requirements Capture and Traceability: Based on the detailed design results above, the design requirements of each unit are formally captured, and the traceability relationship between unit requirements and subsystem requirements, and between unit design elements and subsystem requirements is established.

[0056] After the detailed design of the subsystem is completed, the updated subsystem model will be submitted to the overall system department.

[0057] Finally, the overall system merges and integrates the models, integrating the detailed design models submitted by each subsystem back into the overall spacecraft system master model, thus completing the design closed loop from the overall system to the subsystems.

[0058] In step 5:

[0059] This step aims to comprehensively verify the integrated system model and deeply integrate reliability analysis into the design process.

[0060] First, system integration and comprehensive verification are conducted:

[0061] Structural integration: Summarize the design results of all subsystems, generate a complete list of spacecraft unit components, and integrate them to form a system-wide interaction diagram between units, clearly showing the information flow, energy flow, etc. of the entire ship.

[0062] Behavioral Synthesis: Using behavioral models such as state machine diagrams, verify the correctness and coordination of the integrated system's working mode and state transitions.

[0063] Comprehensive indicator analysis: Check whether the indicator system from the system to the subsystem and then to the single machine is complete, and verify whether the underlying indicators can meet the requirements of the top-level indicators through integration by means of parameter graphs and other methods.

[0064] Simulation verification: Using SysML parametric graphs, constraint equations for key performance parameters (such as power consumption and mass) are established, and external simulation tools can be linked for automated calculations to verify whether the design meets performance requirements.

[0065] Secondly, implement FMEA analysis throughout the entire process, embedding failure mode and effects analysis into each design phase:

[0066] Conceptual FMEA: In the mission analysis phase (conceptual layer), based on the overall mission requirements of the spacecraft, mission-level failure modes and their impacts are analyzed, and new system reliability design requirements are derived accordingly.

[0067] Functional FMEA: During the system design phase (problem layer), based on the system functional model, analyze the local and ultimate impacts of functional failures to identify the causes of failures. The analysis results are then fed back into functional decomposition and system architecture design to eliminate or mitigate failure modes through design improvements.

[0068] Hardware FMEA: In the detailed design phase of the subsystem (solution layer), for specific single equipment, a detailed failure mode, impact and hazard analysis is carried out based on its function and structure to identify weak points and propose prevention or detection measures, thereby improving the inherent reliability of the product.

[0069] Through the above five steps, this invention realizes a standardized and traceable positive collaborative design throughout the entire process from mission requirements to single-unit design. Through integrated verification and immersive FMEA analysis, it effectively ensures the correctness, coordination and high reliability of complex spacecraft system design.

[0070] In a second aspect, the present invention provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs; wherein, when the one or more programs are executed by the one or more processors, the one or more processors implement the aforementioned forward collaborative design method for deep space exploration missions.

[0071] Thirdly, the present invention provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enable the processor to implement the aforementioned forward collaborative design method for deep space exploration missions.

[0072] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for deep space exploration mission forward co-design, characterized in that, The method comprises the following steps: Step 1, based on the MagicGrid methodology, a incremental iterative modeling framework covering the concept layer, the problem layer and the scheme layer is constructed; Step 2, in the concept layer, the spacecraft system is regarded as a black box, task environment interaction analysis, task profile analysis and top-level parameter analysis are carried out, SysML requirement diagram, use case diagram, activity diagram and parameter diagram are used to convert the stakeholder requirements into system functions, interfaces and top-level performance indicators, and a task analysis model is established to trace the overall demand; Step 3, in the problem layer, the spacecraft system is regarded as a white box, based on the task analysis model, system function decomposition, architecture design and index decomposition are carried out, subsystem technical requirements are generated, and a system design model is established to trace the system requirements; Step 4, in the scheme layer, the subsystem technical requirements are issued in the form of a model, each subsystem carries out internal architecture, function and index design based on the issued model, and after the subsystem modeling is completed, the subsystem model is submitted and integrated.

2. The deep space exploration mission forward co-design method of claim 1, wherein, Step 5, in the subsystem model integration stage, comprehensive verification of structure, behavior and index is carried out, and FMEA analysis is embedded in each design stage to realize deep integration of reliability requirements and forward design process.

3. The deep space exploration mission forward co-design method of claim 1, wherein, In step 2, the establishment of the task analysis model to trace the overall demand specifically comprises: establishing a trace matrix to clearly show the satisfaction and refinement relationship of the design model elements generated in the task analysis stage to the top-level overall demand, wherein the functional requirements are refined by activity elements, the interface requirements are refined by port elements, and the performance index requirements are refined by value attributes.

4. The deep space exploration mission forward co-design method of claim 1, wherein, In step 3, the establishment of the system design model to trace the system requirements specifically comprises: establishing a trace matrix of all design outputs in the system scheme design stage to the system design requirements to ensure that the design scheme completely covers and meets the system-level requirements.

5. The deep space exploration mission forward co-design method of claim 1, wherein, In step 4, the model form issuing specifically comprises: according to the model content issuing principle, the system model part containing the subsystem technical requirements is exported and issued to each subsystem, and the subsystem designers carry out detailed design based on the received model and keep the model organization structure.

6. The deep space exploration mission forward co-design method of claim 2, wherein, The FMEA analysis embedded in each design stage specifically comprises: Carrying out concept FMEA in the concept layer to analyze task-level failure modes and their effects and derive system reliability design requirements; Carrying out function FMEA in the problem layer to analyze function failure effects based on the system function model and feed back to function decomposition and architecture design; Carrying out hardware FMEA in the scheme layer to carry out detailed failure mode, effect and criticality analysis for single machine equipment.

7. The deep space exploration mission forward co-design method of claim 1, wherein, In step 4, the subsystem modeling process comprises: subsystem requirement capture, subsystem architecture design, subsystem function analysis, subsystem index decomposition, single machine requirement capture and trace.

8. The deep space exploration mission forward co-design method of claim 2, wherein, The comprehensive verification in step 5 comprises: structure comprehensive, behavior comprehensive, index comprehensive and simulation verification through parameter diagram associated external simulation tool.

9. An electronic device, comprising: The method comprises the following steps: One or more processors; Memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors realize the deep space exploration mission forward collaborative design method in any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, A computer readable storage medium having stored thereon executable instructions that, when executed by a processor, enable the processor to realize the deep space exploration mission forward collaborative design method in any one of claims 1-8.

Images