Demand model construction method and system for aerospace mission scheme argumentation stage

Abstract

The invention provides a demand model construction method and system in a space task scheme argumentation stage, and relates to the technical field of space exploration, and the method comprises the steps: constructing an engineering-level task demand model, an engineering-level benefit related party demand model and an engineering-level system demand model based on a task target of a space task, and determining an engineering-level demand model; based on the engineering-level system demand model, constructing a system-level task demand model, a system-level benefit related party demand model and a system-level system demand model, and determining a system-level demand model; and according to the engineering-level demand model and the system-level demand model, determining a demand model in the aerospace mission scheme argumentation stage. By establishing the standardized demand model, hierarchical description is performed on the demand model generated in the aerospace mission scheme argumentation stage, and the definition and consistency of the demand model are improved.

Description

Technical Field

[0001] The present invention relates to the field of aerospace exploration technology, and in particular to a method and system for constructing a demand model in a space mission program demonstration phase. Background Art

[0002] Compared with manned space missions in Earth orbit, manned lunar exploration missions are farther from the Earth. The cost of normal mission support and emergency rescue projects is high, and the support and rescue cycle is long, which increases the difficulty of mission implementation. At the same time, since manned lunar exploration missions need to experience three different gravity environments: Earth gravity, zero gravity, and lunar gravity, the technical development difficulty of related mission systems is increased. Existing manned lunar exploration missions mainly rely on documents for task management and system design. Document-based system engineering defines various technical elements in different documents, including different technical information. The integrity, consistency, and interrelationships of technical elements are difficult to evaluate, resulting in difficulty in keeping synchronization between demand design, top-level design, system design, and underlying product detailed design. In the process of system design improvement, the workload of maintaining or reusing requirements and designs is large.

[0003] The existing method for constructing demand models in the demonstration phase of space mission plans takes a single system or product as the object, and has a poor degree of satisfaction for complex tasks, such as manned lunar exploration missions, and is unable to meet the requirements of describing complex tasks. At the same time, the existing demand models in the demonstration phase of space mission plans are not standardized enough and lack unified modeling process specifications, resulting in low quality of demand models and great difficulty in integrating demand models. Summary of the invention

[0004] In order to overcome the above-mentioned deficiencies of the prior art, the present invention provides a method for constructing a demand model in the space mission program demonstration phase, comprising:

[0005] Based on the mission objectives of the space mission, construct the engineering-level mission requirement model, engineering-level stakeholder requirement model and engineering-level system requirement model; determine the engineering-level requirement model based on the engineering-level mission requirement model, engineering-level stakeholder requirement model and engineering-level system requirement model;

[0006] Based on the engineering-level system requirement model, construct the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model; determine the system-level requirement model based on the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model;

[0007] Determine the demand model for the space mission program demonstration phase based on the engineering-level demand model and the system-level demand model.

[0008] Preferably, based on the mission objectives of the space mission, an engineering-level mission requirement model, an engineering-level stakeholder requirement model, and an engineering-level system requirement model are constructed, including:

[0009] Based on the space mission objectives, an engineering-level mission requirement model is constructed to obtain the engineering-level mission requirement results of the mission objectives;

[0010] Based on the engineering-level task requirement results of the task objectives, an engineering-level stakeholder requirement model is constructed to obtain the engineering-level stakeholder requirement results of the task objectives;

[0011] Based on the engineering-level stakeholder demand results of the task objectives, an engineering-level system demand model is constructed to obtain the engineering-level system demand results of the task objectives.

[0012] Preferably, based on the engineering-level system requirement model, a system-level task requirement model, a system-level stakeholder requirement model and a system-level system requirement model are constructed, including:

[0013] Based on the engineering-level system requirement results of the task objectives, a system-level task requirement model is constructed to obtain the system-level task requirement results of the task objectives;

[0014] Based on the system-level task requirement results of the task objectives, a system-level stakeholder requirement model is constructed to obtain the system-level stakeholder requirement results of the task objectives;

[0015] Based on the system-level stakeholder demand results of the mission objectives, a system-level system demand model is constructed to obtain the system-level system demand results of the mission objectives.

[0016] Preferably, based on the mission objectives of the space mission, an engineering-level mission requirement model is constructed to obtain the engineering-level mission requirement results of the mission objectives, including:

[0017] Determine the gap between existing products for space missions and stated mission objectives; develop a mission analysis strategy for mission objectives based on the gap; identify the mission systems required to achieve mission objectives based on the mission analysis strategy;

[0018] Identify the trade-offs required to achieve the mission objectives; based on the trade-offs and the mission systems required to achieve the mission objectives, obtain the problems to be solved to achieve the mission objectives;

[0019] Determine the initial operational concept of the mission objectives and the life cycle of the mission objectives; determine alternative implementation plans for the mission objectives based on the initial operational concept of the mission objectives and the problems to be solved in achieving the mission objectives;

[0020] According to the trade-off factors required to achieve the task objectives, select the preferred implementation plan of the task objectives from the alternative implementation plans of the task objectives;

[0021] According to the problems to be solved in achieving the task objectives and the preliminary operational conception of the task objectives, the preferred implementation scheme is converted into the engineering-level task requirements of the task objectives, and the engineering-level task requirement set is obtained according to the engineering-level task requirements; a scheme-problem tracing relationship between the engineering-level task requirements-the preferred implementation scheme of the task objectives-the problems to be solved in achieving the task objectives is established; and an engineering-level task requirement model is constructed according to the engineering-level task requirement set and the scheme-problem tracing relationship;

[0022] Output the engineering-level task requirement results of the task objectives. The engineering-level task requirement results include: preliminary operation concept and engineering-level task requirement set.

[0023] Preferably, based on the engineering-level task requirement results of the task objectives, an engineering-level stakeholder requirement model is constructed to obtain the engineering-level stakeholder requirement results of the task objectives, including:

[0024] Based on the engineering-level task requirements of the task objectives, identify the preliminary operational concept of the task objectives and the engineering-level stakeholders within the life cycle of the task objectives at the task level, and determine the task roles and task responsibilities of the engineering-level stakeholders; according to the task roles, classify the importance of the engineering-level stakeholders, determine the importance level of the engineering-level stakeholders, and formulate the task definition strategy required by the engineering-level stakeholders, which includes task roles, task responsibilities, and importance levels;

[0025] Clarify the mission environment based on the initial operational concept of the mission objectives; identify the needs of engineering-level stakeholders based on the needs guided by engineering-level stakeholders and the needs of engineering-level stakeholders identified by understanding domain expertise and mission context;

[0026] Combined with the operation scenario of the mission objective, the preliminary operation concept of the mission objective is refined to obtain a refined engineering-level mission operation concept;

[0027] Transform engineering-level stakeholder needs into engineering-level stakeholder requirements by identifying the task constraints of the preferred implementation plan of the task objectives and identifying stakeholder requirements related to the key characteristics of the task objectives;

[0028] Obtain an engineering-level stakeholder requirement set based on the engineering-level stakeholder requirements, classify and sort the engineering-level stakeholder requirements, identify the performance indicators required for each engineering-level stakeholder requirement, and feed back each engineering-level stakeholder requirement to the corresponding engineering-level stakeholder;

[0029] Establish the task-requirement traceability relationship between engineering-level task requirements-task operation scenarios-engineering-level stakeholder needs-engineering-level stakeholder requirements; build an engineering-level stakeholder requirement model based on the engineering-level stakeholder requirement set and the task-requirement traceability relationship;

[0030] Output the engineering-level stakeholder demand results of the task objectives. The engineering-level stakeholder demand results include: engineering-level stakeholder demand set, engineering-level task operation concept and task constraints.

[0031] Preferably, based on the engineering-level stakeholder demand results of the task objectives, an engineering-level system demand model is constructed to obtain the engineering-level system demand results of the task objectives, including:

[0032] Based on the engineering-level stakeholder demand results of the mission objectives, define the capability boundaries of the mission execution system according to the engineering-level stakeholder demand results;

[0033] Based on the capability boundary of the task execution system, obtain the capability required by the task execution system to complete the task objectives from the task level, and identify the constraints on the capability required by the system state of the task execution system; obtain the engineering-level system requirements based on the system state, constraints, and required capabilities, and determine the attributes of the engineering-level system requirements;

[0034] Obtain an engineering-level system requirement set based on the engineering-level system requirements, analyze the engineering-level system requirements in the engineering-level system requirement set, and feed back the analyzed engineering-level system requirements to corresponding engineering-level stakeholders;

[0035] Establish engineering-level requirements-model traceability relationships between engineering-level system requirements-engineering-level stakeholder requirements, and engineering-level system requirements-system design models respectively; obtain the engineering-level system requirements model based on the engineering-level system requirements set, system status, and engineering-level requirements-model traceability relationship;

[0036] Output the engineering-level system requirement results of the task objectives. The engineering-level system requirement results include: engineering-level system requirement set, engineering-level requirement-model traceability relationship and system status.

[0037] Preferably, based on the engineering-level system requirement results of the task target, a system-level task requirement model is constructed to obtain the system-level task requirement results of the task target, including:

[0038] Based on the engineering-level system requirement results of the task objectives, the task objectives of the target system are obtained according to the engineering-level system requirement results; according to the task objectives of the target system, the target analysis strategy of the target system is determined;

[0039] Decompose the target system mission objectives into sub-goals, analyze the capabilities required for each of the sub-goals, and determine the envelope of the capabilities required for the target system;

[0040] Determine the preliminary operation concept of the target system based on the required capabilities of the target system, and determine the alternative capability realization plan of the target system based on the preliminary operation concept of the target system;

[0041] Combine the resources of the capability realization scheme and select the optimal capability realization scheme of the target system from the alternative capability realization schemes of the target system;

[0042] Convert the preferred capability realization scheme of the target system into the system-level task requirements of the target system, and obtain the system-level task requirement set according to the system-level task requirements; establish the scheme-goal traceability relationship between the system-level task requirements-the preferred capability realization scheme of the target system-the system goal; and construct the system-level task requirement model according to the system-level task requirement set and the scheme-goal traceability relationship;

[0043] Output the system-level task requirement results of the task objectives. The system-level task requirement results include: preliminary operation concept of the target system and system-level task requirement set.

[0044] Preferably, based on the system-level task requirement results of the task objectives, a system-level stakeholder requirement model is constructed to obtain the system-level stakeholder requirement results of the task objectives, including:

[0045] Based on the system-level task requirements of the task objectives, identify the preliminary operation concept of the target system and the system-level stakeholders in the life cycle of the target system at the system level, and determine the system roles and system responsibilities of the system-level stakeholders; divide the importance of the system-level stakeholders according to the system roles, and determine the importance level of the system-level stakeholders; determine the system definition strategy required by the system-level stakeholders, which includes: system roles, system responsibilities, and importance levels;

[0046] Identify the needs of system-level stakeholders based on the needs obtained through the guidance of system-level stakeholders and the needs of system-level stakeholders identified through understanding of domain expertise and task background; refine the preliminary operation concept of the target system in combination with the operation scenario of the target system to obtain a refined system-level task operation concept;

[0047] Transform system-level stakeholder needs into system-level stakeholder requirements by identifying the system constraints of the target system's preferred capability implementation solution and identifying stakeholder requirements related to the key characteristics of the system's objectives;

[0048] Obtain a set of system-level stakeholder requirements based on system-level stakeholder requirements, classify and sort the system-level stakeholder requirements, identify the performance indicators required for each system-level stakeholder requirement, and feed back each system-level stakeholder requirement to the corresponding system-level stakeholder;

[0049] Establish a system-requirement traceability relationship between system-level task requirements-system operation scenarios-system-level stakeholder needs-system-level stakeholder requirements; build a system-level stakeholder requirement model based on the system-level stakeholder requirement set and the system-requirement traceability relationship;

[0050] Output the system-level stakeholder demand results of the target system. The system-level stakeholder demand results include: system-level stakeholder demand set, system-level task operation concept and system constraints.

[0051] Preferably, based on the system-level stakeholder demand results of the mission objectives, a system-level system demand model is constructed to obtain the system-level system demand results of the mission objectives, including:

[0052] Based on the system-level stakeholder requirements results of the target system, define the behavior of the system and system elements at the system boundary according to the system-level stakeholder requirements results of the target system;

[0053] Based on the behaviors on the system boundary, the capabilities required by the target system to complete the mission objectives are obtained from the system level, and the constraints on the system state and required capabilities of the target system are identified; based on the system state, constraints, and required capabilities, the system-level system requirements are obtained, and the attributes of the system-level system requirements are determined;

[0054] Obtain a system-level system requirement set according to the system-level system requirements, analyze the system-level system requirements in the system-level system requirement set, and feed back the analyzed system-level system requirements to corresponding system-level stakeholders;

[0055] Establish system-level requirement-model traceability relationships between system-level system requirement model-system-level stakeholder requirements and system-level system requirement model-system design model respectively; obtain system-level system requirement model according to system-level system requirement set and system-level requirement-model traceability relationship;

[0056] Output the system-level system requirement results of the target system. The system-level system requirement results include: the system-level system requirement set of the target system and the system operation plan of the target system.

[0057] Based on the same inventive concept, the present invention also provides a demand model building system for the space mission program demonstration stage, the system comprising:

[0058] An engineering-level requirement model determination module is used to construct an engineering-level task requirement model, an engineering-level stakeholder requirement model and an engineering-level system requirement model based on the mission objectives of the space mission; and to determine the engineering-level requirement model based on the engineering-level task requirement model, the engineering-level stakeholder requirement model and the engineering-level system requirement model;

[0059] A system-level requirement model determination module is used to construct a system-level task requirement model, a system-level stakeholder requirement model and a system-level system requirement model based on the engineering-level system requirement model; and to determine a system-level requirement model based on the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model;

[0060] The module for determining the requirement model in the mission plan demonstration phase is used to determine the requirement model in the space mission plan demonstration phase based on the engineering-level requirement model and the system-level requirement model.

[0061] Based on the same inventive concept, the present invention also provides an electronic device, comprising: at least one processor and a memory; the memory and the processor are connected via a bus;

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

[0063] When the one or more programs are executed by the at least one processor, the demand model building method for the aerospace mission program demonstration phase as described above is implemented.

[0064] Based on the same inventive concept, the present invention also provides a readable storage medium having an execution program stored thereon. When the execution program is executed, the demand model construction method for the aerospace mission program demonstration phase as described above is implemented.

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

[0066] The present invention provides a method for constructing a demand model in the demonstration phase of a space mission program, including: constructing an engineering-level task demand model, an engineering-level stakeholder demand model and an engineering-level system demand model based on the task objectives of the space mission; determining the engineering-level demand model according to the engineering-level task demand model, the engineering-level stakeholder demand model and the engineering-level system demand model; constructing a system-level task demand model, a system-level stakeholder demand model and a system-level system demand model based on the engineering-level system demand model; determining the system-level demand model according to the system-level task demand model, the system-level stakeholder demand model and the system-level system demand model; determining the demand model in the demonstration phase of the space mission program according to the engineering-level demand model and the system-level demand model. The present invention hierarchically describes the demand model generated in the demonstration phase of the space mission program, that is, establishes an engineering-level demand model and a system-level demand model, and establishes a task demand model, a stakeholder demand model and a system demand model at each demand model level, and satisfies the description requirements of complex tasks through the established standardized demand model, and the unified modeling process specification can improve the clarity and consistency of the demand model, improve the quality of the demand model, and reduce the difficulty of model integration. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 A flow chart of a method for constructing a demand model in the space mission program demonstration phase provided by the present invention;

[0068] Figure 2 A schematic diagram of the demand traceability relationship of the demand model in the space mission solution demonstration phase provided by the present invention;

[0069] Figure 3 A structural diagram of a demand model building system for the space mission program demonstration phase provided by the present invention;

[0070] Figure 4 A schematic diagram of an electronic device provided by the present invention. DETAILED DESCRIPTION

[0071] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and should not be construed as limiting the present invention.

[0072] Embodiment 1:

[0073] The present invention provides a method for constructing a demand model in the demonstration phase of a space mission plan, specifically, Figure 1 A flow chart of a method for constructing a demand model in the space mission solution demonstration phase provided by an embodiment of the present invention includes the following steps as shown in the figure:

[0074] S1: Based on the mission objectives of the space mission, construct the engineering-level mission requirement model, engineering-level stakeholder requirement model and engineering-level system requirement model; determine the engineering-level requirement model based on the engineering-level mission requirement model, engineering-level stakeholder requirement model and engineering-level system requirement model;

[0075] S2: Based on the engineering-level system requirement model, construct the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model; determine the system-level requirement model based on the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model;

[0076] S3: Determine the demand model for the space mission program demonstration phase based on the engineering-level demand model and the system-level demand model.

[0077] Aiming at the mission objectives of the space mission, the present invention establishes a standardized demand model, hierarchically describes the demand model generated by the space mission program demonstration, and improves the clarity and consistency of the demand model.

[0078] The method for constructing a space mission program demonstration demand model provided by the present invention includes establishing an engineering-level demand model and a system-level demand model, and modeling is performed in the order of first the engineering-level demand model and then the system-level demand model. After the engineering-level demand model is modeled, three engineering-level demand models (engineering-level tasks, engineering-level stakeholders, and engineering-level systems) are obtained. After the system-level demand model is modeled, three system-level demand models (system-level tasks, system-level stakeholders, and system-level systems) are obtained. The types of demand models at the two levels are consistent, which is convenient for system engineers to manage models.

[0079] The method for constructing a space mission program demonstration requirement model provided by the embodiment of the present invention is applicable to various types of space missions, such as large space missions, ordinary space missions, manned space missions, unmanned space missions, etc. The method is particularly applicable to complex space missions.

[0080] Space missions refer to the work content, methods and requirements determined for space activities, or military, civil or commercial goals achieved by using spacecraft. Space missions are divided into manned space missions and unmanned space missions according to whether they are manned or not. Manned space missions are missions carried out by manned spacecraft such as space stations, space shuttles, and manned spacecraft; unmanned space missions are missions carried out by unmanned spacecraft such as artificial satellites and space probes. Space missions are divided into military space missions, civil space missions and commercial space missions according to their specific uses. Space missions that achieve military goals are called military space missions; space missions that achieve civil goals are called civil space missions; and space missions that achieve commercial goals are called commercial space missions. Space missions can also be distinguished according to the difficulty and complexity of space missions. For example, space missions with high difficulty and complexity are called large space missions, and space missions with low difficulty and complexity are called ordinary space missions. For example, space missions in near-Earth orbit are called ordinary space missions, and space missions for exploration around other planets such as the moon are called large space missions.

[0081] In S1, based on the mission objectives of the space mission, the engineering-level mission requirement model, engineering-level stakeholder requirement model and engineering-level system requirement model are constructed, including:

[0082] S1-1, based on the space mission objectives, build an engineering-level mission requirement model to obtain the engineering-level mission requirement results of the mission objectives;

[0083] S1-2, based on the engineering-level task requirement results of the task objectives, construct an engineering-level stakeholder requirement model to obtain the engineering-level stakeholder requirement results of the task objectives;

[0084] S1-3, based on the engineering-level stakeholder demand results of the task objectives, build an engineering-level system demand model to obtain the engineering-level system demand results of the task objectives.

[0085] In S1-1, based on the space mission objectives, an engineering-level mission requirement model is constructed to obtain the engineering-level mission requirement results of the mission objectives, including:

[0086] Determine the gap between existing products for space missions and stated mission objectives; develop a mission analysis strategy for mission objectives based on the gap; identify the mission systems required to achieve mission objectives based on the mission analysis strategy;

[0087] Identify the trade-offs required to achieve the mission objectives; based on the trade-offs and the mission systems required to achieve the mission objectives, obtain the problems to be solved to achieve the mission objectives;

[0088] Determine the initial operational concept of the mission objectives and the life cycle of the mission objectives; determine alternative implementation plans for the mission objectives based on the initial operational concept of the mission objectives and the problems to be solved in achieving the mission objectives;

[0089] According to the trade-off factors required to achieve the task objectives, select the preferred implementation plan of the task objectives from the alternative implementation plans of the task objectives;

[0090] According to the problems to be solved in achieving the task objectives and the preliminary operational concept of the task objectives, the preferred implementation plan is converted into the engineering-level task requirements of the task objectives, and the engineering-level task requirement set is obtained according to the engineering-level task requirements; a solution-problem traceability relationship between the engineering-level task requirements-the preferred implementation plan of the task objectives-the problems to be solved in achieving the task objectives is established; an engineering-level task requirement model is constructed according to the engineering-level task requirement set and the solution-problem traceability relationship;

[0091] Output the engineering-level task requirement results of the task objectives. The engineering-level task requirement results include: preliminary operation concept and engineering-level task requirement set.

[0092] In S1-2, based on the engineering-level task requirement results of the task objectives, an engineering-level stakeholder requirement model is constructed to obtain the engineering-level stakeholder requirement results of the task objectives, including:

[0093] Based on the engineering-level task requirements of the task objectives, identify the preliminary operational concept of the task objectives and the engineering-level stakeholders within the life cycle of the task objectives at the task level, and determine the task roles and task responsibilities of the engineering-level stakeholders; according to the task roles, classify the importance of the engineering-level stakeholders, determine the importance level of the engineering-level stakeholders, and formulate the task definition strategy required by the engineering-level stakeholders, which includes task roles, task responsibilities, and importance levels;

[0094] Clarify the mission environment based on the initial operational concept of the mission objectives; identify the needs of engineering-level stakeholders based on the needs guided by engineering-level stakeholders and the needs of engineering-level stakeholders identified by understanding domain expertise and mission context;

[0095] Combined with the operation scenario of the mission objective, the preliminary operation concept of the mission objective is refined to obtain a refined engineering-level mission operation concept;

[0096] Transform engineering-level stakeholder needs into engineering-level stakeholder requirements by identifying the task constraints of the preferred implementation plan of the task objectives and identifying stakeholder requirements related to the key characteristics of the task objectives;

[0097] Obtain an engineering-level stakeholder requirement set based on the engineering-level stakeholder requirements, classify and sort the engineering-level stakeholder requirements, identify the performance indicators required for each engineering-level stakeholder requirement, and feed back each engineering-level stakeholder requirement to the corresponding engineering-level stakeholder;

[0098] Establish the task-requirement traceability relationship between engineering-level task requirements-task operation scenarios-engineering-level stakeholder needs-engineering-level stakeholder requirements; build an engineering-level stakeholder requirement model based on the engineering-level stakeholder requirement set and the task-requirement traceability relationship;

[0099] Output the engineering-level stakeholder demand results of the task objectives. The engineering-level stakeholder demand results include: engineering-level stakeholder demand set, engineering-level task operation concept and task constraints.

[0100] In S1-3, based on the engineering-level stakeholder demand results of the task objectives, an engineering-level system demand model is constructed to obtain the engineering-level system demand results of the task objectives, including:

[0101] Based on the engineering-level stakeholder demand results of the mission objectives, define the capability boundaries of the mission execution system according to the engineering-level stakeholder demand results;

[0102] Based on the capability boundary of the task execution system, obtain the capability required by the task execution system to complete the task objectives from the task level, and identify the constraints on the capability required by the system state of the task execution system; obtain the engineering-level system requirements based on the system state, constraints, and required capabilities, and determine the attributes of the engineering-level system requirements;

[0103] Obtain an engineering-level system requirement set based on the engineering-level system requirements, analyze the engineering-level system requirements in the engineering-level system requirement set, and feed back the analyzed engineering-level system requirements to corresponding engineering-level stakeholders;

[0104] Establish engineering-level requirements-model traceability relationships between engineering-level system requirements-engineering-level stakeholder requirements, and engineering-level system requirements-system design models respectively; obtain the engineering-level system requirements model based on the engineering-level system requirements set, system status, and engineering-level requirements-model traceability relationship;

[0105] Output the engineering-level system requirement results of the task objectives. The engineering-level system requirement results include: engineering-level system requirement set, engineering-level requirement-model traceability relationship and system status.

[0106] The engineering-level requirement model is determined through the engineering-level task requirement model, engineering-level stakeholder requirement model and engineering-level system requirement model established through S1-1 to S1-3.

[0107] In S2, based on the engineering-level system requirement model, the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model are constructed, including:

[0108] S2-1, based on the engineering-level system requirement results of the task objectives, build a system-level task requirement model to obtain the system-level task requirement results of the task objectives;

[0109] S2-2, based on the system-level task requirement results of the task objectives, build a system-level stakeholder requirement model to obtain the system-level stakeholder requirement results of the task objectives;

[0110] S2-3, based on the system-level stakeholder demand results of the mission objectives, build a system-level system demand model to obtain the system-level system demand results of the mission objectives.

[0111] In S2-1, based on the engineering-level system requirement results of the task objectives, a system-level task requirement model is constructed to obtain the system-level task requirement results of the task objectives, including:

[0112] Based on the engineering-level system requirement results of the task objectives, the task objectives of the target system are obtained according to the engineering-level system requirement results; according to the task objectives of the target system, the target analysis strategy of the target system is determined;

[0113] Decompose the target system mission objectives into sub-goals, analyze the capabilities required for each of the sub-goals, and determine the envelope of the capabilities required for the target system;

[0114] Determine the preliminary operation concept of the target system based on the required capabilities of the target system, and determine the alternative capability realization plan of the target system based on the preliminary operation concept of the target system;

[0115] Combine the resources of the capability realization scheme and select the optimal capability realization scheme of the target system from the alternative capability realization schemes of the target system;

[0116] Convert the preferred capability realization scheme of the target system into the system-level task requirements of the target system, and obtain the system-level task requirement set according to the system-level task requirements; establish the scheme-goal traceability relationship between the system-level task requirements-the preferred capability realization scheme of the target system-the system goal; and construct the system-level task requirement model according to the system-level task requirement set and the scheme-goal traceability relationship;

[0117] Output the system-level task requirement results of the task objectives. The system-level task requirement results include: preliminary operation concept of the target system and system-level task requirement set.

[0118] In S2-2, based on the system-level task requirement results of the task objectives, a system-level stakeholder requirement model is constructed to obtain the system-level stakeholder requirement results of the task objectives, including:

[0119] Based on the system-level task requirements of the task objectives, identify the preliminary operation concept of the target system and the system-level stakeholders in the life cycle of the target system at the system level, and determine the system roles and system responsibilities of the system-level stakeholders; divide the importance of the system-level stakeholders according to the system roles, and determine the importance level of the system-level stakeholders; determine the system definition strategy required by the system-level stakeholders, which includes: system roles, system responsibilities, and importance levels;

[0120] Identify the needs of system-level stakeholders based on the needs obtained through the guidance of system-level stakeholders and the needs of system-level stakeholders identified through understanding of domain expertise and task background; refine the preliminary operation concept of the target system in combination with the operation scenario of the target system to obtain a refined system-level task operation concept;

[0121] Transform system-level stakeholder needs into system-level stakeholder requirements by identifying the system constraints of the target system's preferred capability implementation solution and identifying stakeholder requirements related to the key characteristics of the system's objectives;

[0122] Obtain a set of system-level stakeholder requirements based on system-level stakeholder requirements, classify and sort the system-level stakeholder requirements, identify the performance indicators required for each system-level stakeholder requirement, and feed back each system-level stakeholder requirement to the corresponding system-level stakeholder;

[0123] Establish a system-requirement traceability relationship between system-level task requirements-system operation scenarios-system-level stakeholder needs-system-level stakeholder requirements; build a system-level stakeholder requirement model based on the system-level stakeholder requirement set and the system-requirement traceability relationship;

[0124] Output the system-level stakeholder demand results of the target system. The system-level stakeholder demand results include: system-level stakeholder demand set, system-level task operation concept and system constraints.

[0125] In S2-3, based on the system-level stakeholder demand results of the mission objectives, a system-level system demand model is constructed to obtain the system-level system demand results of the mission objectives, including:

[0126] Based on the system-level stakeholder requirements results of the target system, define the behavior of the system and system elements at the system boundary according to the system-level stakeholder requirements results of the target system;

[0127] Based on the behaviors on the system boundary, the capabilities required by the target system to complete the mission objectives are obtained from the system level, and the constraints on the system state and required capabilities of the target system are identified; based on the system state, constraints, and required capabilities, the system-level system requirements are obtained, and the attributes of the system-level system requirements are determined;

[0128] Obtain a system-level system requirement set according to the system-level system requirements, analyze the system-level system requirements in the system-level system requirement set, and feed back the analyzed system-level system requirements to corresponding system-level stakeholders;

[0129] Establish system-level requirement-model traceability relationships between system-level system requirement model-system-level stakeholder requirements and system-level system requirement model-system design model respectively; obtain system-level system requirement model according to system-level system requirement set and system-level requirement-model traceability relationship;

[0130] Output the system-level system requirement results of the target system. The system-level system requirement results include: the system-level system requirement set of the target system and the system operation plan of the target system.

[0131] Determine the system-level requirement model through the system-level task requirement model, system-level stakeholder requirement model and system-level system requirement model established through S2-1 to S2-3.

[0132] In S3, the demand model for the space mission program demonstration phase is determined based on the three demand models of the engineering level demand model and the three demand models of the system level demand model.

[0133] In the present invention, a demand traceability for representing the association relationship between various demand elements in various demand models is also established, and the association relationship between various demand elements and other elements is also established. Through the association relationship, various demand elements can be engineering-level task requirements, engineering-level stakeholder requirements, engineering-level system requirements, or system-level task requirements, system-level stakeholder requirements, and system-level system requirements. Other elements can be model elements of design, analysis, verification, and confirmation processes, such as the preferred implementation plan of the task goal, the problem task operation scenario to be solved to achieve the task goal, and the needs of engineering-level stakeholders.

[0134] For example, when building an engineering-level stakeholder demand model, a task-demand traceability relationship is established between engineering-level task requirements-task operation scenarios-engineering-level stakeholder needs-engineering-level stakeholder needs, that is, the traceability relationship established includes an association relationship between the two types of demand elements, engineering-level task requirements and engineering-level stakeholder needs, and an association relationship between the demand elements of engineering-level task requirements, task operation scenarios, and engineering-level stakeholder needs and other elements. For another example, when building an engineering-level task demand model, a solution-problem traceability relationship is established between engineering-level task requirements-preferred implementation solutions for task objectives-problems to be solved to achieve task objectives, that is, the traceability relationship established includes an association relationship between demand elements and other elements.

[0135] The above-mentioned association relationship itself also uses specific symbolic and graphical model elements (called relationship elements) to indicate the type and attribute information of the relationship. Requirements traceability is divided into two categories: traceability between requirements elements and traceability between requirements elements and other elements. Those skilled in the art can standardize the use of relationship elements in various requirements views according to actual conditions, so as to clearly describe the requirements traceability characteristics at this level.

[0136] like Figure 2 As shown, it is a schematic diagram of the traceability relationship of the demand model provided by the present invention.

[0137] 1: Traceability between demand elements

[0138] The types and semantics of traceability relationships between requirement elements can refer to the requirements of 16.3.2 in OMG 2019SysML, which are expressed by two types of relationship elements: containment and derive.

[0139] a) Inclusion relationship

[0140] ① It is not allowed to establish inclusion relationships across levels. For example, a set of capability requirements in an engineering-level requirement model cannot include requirements in a certain system requirement model.

[0141] ② It is not allowed to establish inclusion relationships across processes. For example, a group of stakeholder requirements at the engineering level cannot include a certain item / group of system requirements at the engineering level.

[0142] b) Inheritance

[0143] ① It allows the establishment of an inheritance relationship between the stakeholder requirements (or task requirements) at this level and the system element requirements (from the system requirement definition process at the upper level) from top to bottom across levels. For example, a system element requirement in the engineering-level requirement model can establish an inheritance relationship with a corresponding stakeholder requirement / group in the system-level requirement model.

[0144] ② It allows the establishment of inheritance relationships between various types of requirements / needs at the same level across processes. For example, a stakeholder requirement in the engineering-level requirement model can establish an inheritance relationship with a corresponding stakeholder requirement / group.

[0145] 2: Traceability requirements between demand elements and other elements

[0146] The types and semantics of traceability relationships between requirement elements and other elements can refer to the requirements of 16.3.2 in OMG 2019SysML, which are expressed by four relationship elements: Trace, Refine, Verify, and Satisfy.

[0147] The types and semantics of traceability relationships between requirement elements and other elements can refer to the requirements of 16.3.2 in OMG 2019SysML, which are expressed by four relationship elements: Trace, Refine, Verify, and Satisfy.

[0148] a) Tracking relationships

[0149] ① Those skilled in the art can establish a tracing relationship between the demand elements at this level and other elements in the early stages of research and development; as system design and product design evolve, those skilled in the art should further clarify the type of tracing relationship between the demand elements and other elements, and can gradually replace the initial tracing relationship with the more precise tracing relationship types b) to d) below.

[0150] ② It is usually not allowed to establish a traceability relationship between the requirement elements at this level and the elements at other levels across levels. For example, the system requirements in the engineering-level requirement model cannot directly establish a traceability relationship with the system-level design elements.

[0151] ③ Allow cross-process identification and establishment of tracking relationships between demand elements at this level and other elements at this level.

[0152] b) Refinement relationship

[0153] ① Technical personnel in this field can identify and establish refined relationships between functional stakeholder requirements at this level and elements such as system operation scenarios and system functional activities during the process of defining stakeholder requirements at this level and system requirements.

[0154] ② It is usually not allowed to establish refinement relationships across levels. For example, the functional stakeholder requirements in the engineering-level requirements model cannot directly establish refinement relationships with the functional behavior elements at the system level.

[0155] c) Verify the relationship

[0156] ① Technical personnel in this field can establish a verification relationship between the system requirements at this level and the verification methods, technologies or verification results during the process of system requirement definition, system design and verification at this level.

[0157] ② It is usually not allowed to establish verification relationships across levels. For example, the system requirements in the engineering-level requirements model cannot establish verification relationships with the system-level verification methods, technologies, or verification results.

[0158] d) Satisfaction relationship

[0159] ① Technical personnel in this field can establish a satisfaction relationship between the system requirements at this level and the system design elements during the system requirement definition and system design process at this level.

[0160] ② It is usually not allowed to establish a satisfaction relationship across levels. For example, the system requirements in the engineering-level requirement model cannot directly establish a satisfaction relationship with the system-level design elements.

[0161] In some optional implementations, the present invention also proposes quality requirements for the demand model. The specific quality requirements for the demand attribute definition of the demand model are as follows:

[0162] Assigning attributes to requirements is a technique for organizing requirement information, which should be described in a structured manner.

[0163] Requirement attributes are applicable to all levels and types of requirement models in the requirement model design process, including engineering-level task requirements, engineering-level stakeholder requirements and engineering-level system requirements in the engineering-level requirement model, and system-level task requirements, system-level stakeholder requirements and system-level system requirements in the system-level system requirement model.

[0164] The requirements for the definition of demand attributes are shown in Table 1.

[0165]

[0166]

[0167] Table 1 Requirements attribute definition requirements

[0168] The demand model in the solution demonstration stage mainly focuses on solution requirements to ensure that the proposed solution can meet the mission requirements. The present invention establishes a complete demand model through aerospace mission solution demonstration, and uses digital means to establish the demand model, establishes an association with the system system design model in the solution demonstration process, improves the level and efficiency of solution demonstration, and establishes a digital model for the entire mission development cycle, providing a solid foundation for solution demonstration, helping to ensure that everyone has a common understanding of the requirements, and can serve as a basis for evaluating and selecting different solutions. The demand model is a key tool used in project management and system engineering to describe, analyze and record project requirements, helping project developers to clarify project goals, requirements, etc.

[0169] By adopting a model-based systems engineering approach, a requirement model design method for the space mission program demonstration stage was constructed to achieve standardization and generalization of the requirement modeling process, solve the problems of non-standard and incomplete requirement modeling, improve the efficiency and quality of requirement modeling, accelerate the iterative demonstration and program demonstration efficiency, and realize the transformation from document mode to digital model.

[0170] In the prior art, large-scale space missions in China and abroad have always adopted the system engineering concept as a task management method. The document-based system engineering method has discontinuous and inconsistent design models and low interaction efficiency, which brings risks to the implementation of large-scale tasks and is difficult to adapt to the needs of future space mission development. Compared with text-based system engineering, model-based system engineering (MBSE) models the entire design process, establishes model elements through system engineering software, and carries technical elements through models. The MBSE method has been widely used in the fields of aviation, unmanned spacecraft, missiles and launch vehicles, but is still in the exploratory stage in the field of manned spaceflight. The prior art also introduces the DoDAF system framework into the design and proposes an overall design process and method suitable for manned lunar exploration projects. The International Council for Systems Engineering (INCOSE) divides the entire mission cycle into 14 processes such as business or mission analysis and stakeholder requirements definition. Dassault's MagicGraid methodology places demand analysis in the problem domain and captures it layer by layer.

[0171] The existing demand modeling methods have the following main disadvantages:

[0172] (1) Existing demand modeling methods mostly take a single system or product as the object, have poor satisfaction with complex tasks, and lack modeling methods suitable for complex tasks.

[0173] (2) The existing demand modeling methods are not targeted enough and are not suitable for the characteristics of my country's space mission technology development.

[0174] (3) The existing demand modeling methods are not standardized enough and lack unified modeling process specifications, resulting in low model quality and difficulty in model integration.

[0175] The method for constructing a demand model in the stage of space mission program demonstration established by the present invention is based on the current status of system engineering research and development in my country, is adapted to the actual design process of system engineering research and development in my country, improves the comprehensiveness of the demand model, and guides the program demonstration. At the same time, the demand model provided by the present invention puts forward quality requirements, including traceability requirements and attribute definition requirements. A standardized demand model is established to improve the clarity and consistency of the demand model, which is convenient for updating, iteration and integration of the demand model. The present invention describes the demand model generated in the design process in a hierarchical manner, and clarifies the traceability relationship between the demand models between levels and within the level, so as to improve the traceability of the demand. Through the present invention, the efficiency and accuracy of the demand analysis of the space mission program demonstration are improved, the practicality of the demand model is improved, and designers are helped to better understand the demand and improve the level of program demonstration. A method for constructing a demand model in the stage of space mission program demonstration provided by the present invention has been used for internal program demonstration, and the results are feasible.

[0176] The method for constructing a demand model for space mission program demonstration provided by the present invention is described in detail below with reference to a specific embodiment.

[0177] In S1-1, according to the needs of customers or users, define engineering-level task requirements and establish an engineering-level task requirement model. Specifically, it includes:

[0178] (1) Input: The needs of the client or user (the client or user of the project), which can be a specific large-scale space mission goal, such as a manned lunar exploration mission, which is planned to have three astronauts carry wheat seeds to the northernmost part of the moon in September 2025.

[0179] (2) Steps for establishing the engineering-level task requirement model:

[0180] Step 1: Engineering Task Analysis

[0181] a) According to the needs of customers or users, clarify the gap between the current capabilities of domestic manned space flight, product status and mission objectives;

[0182] b) Translating the needs of customers or users into task objectives and clarifying the task analysis strategy, including task analysis methods, task milestones, and resources required for the task, will help elaborate on the task requirements;

[0183] c) Identify the systems required to achieve mission objectives, including mission execution systems and mission support systems.

[0184] Step 2: Define the problems that need to be solved to achieve the mission objectives

[0185] a) Identify the trade-offs that need to be considered in achieving mission objectives, including technological advancement, technological maturity, mission quality and scale, mission achievement risks, international cooperation, reliability and safety, and future mission planning.

[0186] b) Based on the trade-offs and the systems required to accomplish the task, briefly state the problems that need to be solved to accomplish the task.

[0187] Step 3: Describe the task implementation plan

[0188] a) Define the preliminary mission operation concept and mission life cycle process. Define the preliminary mission operation concept at the engineering level based on the mission objectives, the systems required for the mission, and the problems that the mission needs to solve, and provide a conceptual description of the mission cycle process in the mission operation concept. The relevant concepts of the mission life cycle process include planning, development, verification flight, mission execution, mission support, and after mission completion.

[0189] b) Identify feasible mission implementation plans. Based on the mission operation concept and the problems that the mission needs to solve, identify potential mission implementation plans.

[0190] Step 4: Evaluate the implementation plan of the task

[0191] Evaluate potential task implementation solutions based on the trade-off factors obtained in Step 2, and select one or more task implementation solutions from the potential task implementation solutions.

[0192] Step 5: Establish an engineering-level task requirement model

[0193] a) Define engineering-level task requirements. Based on the task problem, task system, task operation concept, etc., express the preferred task implementation plan as engineering-level task requirements through structured text, and form an engineering-level task requirement set.

[0194] b) Establish traceability of engineering-level task requirements. Establish a traceability relationship between engineering-level task requirements, task implementation solutions, and problems that need to be solved by the task.

[0195] (3) Output: preliminary mission operation concept and engineering-level mission requirements.

[0196] In S1-2, identify engineering-level stakeholders and their needs, analyze these needs and convert them into stakeholder requirements, form a stakeholder requirement set, and establish an engineering-level stakeholder requirement model. Specifically, it includes:

[0197] (1) Input: preliminary mission operation concept, engineering-level mission requirements

[0198] (2) Steps for establishing the engineering-level stakeholder demand model:

[0199] Step 1: Prepare engineering-level stakeholders to define

[0200] a) Identify stakeholders within the mission's initial operational concept and mission lifecycle.

[0201] Combined with the mission operation concept and mission life cycle, the engineering-level stakeholders are identified at the mission level, and their mission roles and mission responsibilities are indicated. Based on the roles of the engineering-level stakeholders at the mission level, the engineering-level stakeholders are divided into importance levels and their importance levels are clarified.

[0202] b) Define the strategy for defining the needs of project-level stakeholders. The strategy for defining the needs includes the roles and responsibilities, importance levels, resources, etc. of project-level stakeholders. Derive the needs of project-level stakeholders based on their roles and responsibilities in the task. Balance the conflicting needs of different stakeholders based on importance levels, resources, etc.

[0203] Step 2: Define engineering-level stakeholder needs

[0204] a) Clarify the mission environment based on the preliminary mission operation concept. The mission environment includes but is not limited to the mission operation space and mission operation environment.

[0205] b) Identify engineering-level stakeholder needs. Ways to identify engineering-level stakeholder needs include directly guiding stakeholders’ needs, or identifying implicit engineering-level stakeholder needs based on professional knowledge in the field and understanding of the task background. Common “questions” for defining stakeholder needs include: the value of the task goal, task mode, task operation scenario, task life cycle, task effectiveness indicators, user characteristics, etc.

[0206] Step 3: Refine the concept of engineering-level task operation

[0207] a) Define typical mission operation scenarios to identify the needs of all stakeholders. Operation scenarios help identify requirements that may be overlooked and refine the full-cycle mission operation concept.

[0208] b) Identify the interaction between this mission and other space missions, and the interaction between the execution systems of each mission, and summarize the factors affecting the interaction, including technical foundation, system resources, human factors, etc.

[0209] Step 4: Transform engineering-level stakeholder needs into engineering-level stakeholder requirements

[0210] a) Identify the constraints of the mission implementation plan. Constraints are also a type of requirements. Constraints can be obtained by identifying the stakeholders of the mission (such as mission planning, mission completion time, budget, etc.), mission lifecycle activities (operation, maintenance and repair), and mission indicators (such as performance, safety, reliability, maintainability, etc.).

[0211] b) Identify the needs of stakeholders related to mission-critical characteristics. Mission-critical characteristics include safety, environment, human factors, etc. Identifying and evaluating the degree of reuse of existing requirements and the degree of reuse is an important way to define engineering-level stakeholder requirements.

[0212] c) Build well-formatted requirement statements based on engineering-level stakeholder needs.

[0213] Step 5: Analyze engineering-level stakeholder needs

[0214] a) Analyze the engineering-level stakeholder requirements. The analysis mainly involves classifying and sorting the engineering-level stakeholder requirements. For reused previous stakeholder requirements, analyze their reuse based on factors such as applicability and feasibility, and check their consistency with the specific requirements of the task.

[0215] b) Identify the performance metrics required for each engineering-level stakeholder requirement.

[0216] c) Feedback the analyzed engineering-level stakeholder requirements to the engineering-level stakeholders to confirm that their needs and expectations have been fully captured and expressed. During the requirements analysis process, negotiate the conflicting requirements continuously, reach consensus on the appropriate trade-offs, and resolve conflicts as early as possible.

[0217] Step 6: Establish an engineering-level stakeholder demand model

[0218] a) Maintain the traceability of engineering-level stakeholder requirements. Record how formal requirements meet stakeholder needs, and establish corresponding traceability relationships between task requirements, operational scenarios, stakeholder needs, and stakeholder requirements.

[0219] b) Form a complete engineering-level stakeholder demand model and provide the required key information items. The key information items of the engineering-level stakeholder demand model include stakeholder demand set, mission operation concept, etc.

[0220] (3) Output: engineering-level stakeholder requirement set, mission operation concept, and mission constraints.

[0221] In S1-3, the purpose of defining engineering-level system requirements is to convert engineering-level stakeholder requirements into requirements for engineering-level task execution systems (black box systems) from a black box perspective. Specifically, it includes:

[0222] (1) Input: Engineering-level stakeholder requirements, mission operational concept, and mission constraints

[0223] (2) Steps to establish an engineering-level system requirements model

[0224] Step 1: Prepare engineering-level system requirements definition

[0225] Define the capability boundaries of each task execution system (black box) based on the task operation concept, task constraints and engineering-level stakeholder requirements.

[0226] Step 2: Define engineering-level system requirements

[0227] a) Define each capability required by the task execution system to achieve the task objectives at the task level.

[0228] b) Identify the state transitions and operation modes required by the task execution system. Specifically, the operation view can be used to describe the system's state transitions, operation modes and other dynamic behavior characteristics.

[0229] c) Identify the constraints on the task execution system to obtain the corresponding capabilities. Constraints can come from the task operation scenario and capability usage environment, or from the interaction between systems and regulatory requirements.

[0230] d) Identify engineering-level system requirements related to key characteristics such as system states, operating modes, constraints, capabilities, etc.

[0231] e) Define the attributes of engineering-level system requirements. Determine the attributes of engineering-level system requirements, including functional and non-functional characteristics, priorities, testing, verification, etc.

[0232] Step 3: Analyze engineering-level system requirements

[0233] a) Analyze the system requirements set. Check whether the system requirements are well stated and meet the formal requirements.

[0234] b) Feedback the analyzed requirements to engineering-level stakeholders for confirmation, ensure that the requirements of engineering-level stakeholders are correctly converted into engineering-level system requirements, and continuously resolve conflicts in the set of engineering-level system requirements.

[0235] Step 4: Establish an engineering-level system requirements model

[0236] a) Maintain the traceability of engineering-level system requirements. Establish a two-way traceability relationship between engineering-level system requirements and engineering-level stakeholder requirements, and between engineering-level system requirements and system design models.

[0237] b) Form a complete engineering-level system requirement model and provide the required key information items. The engineering-level system requirement model includes the engineering-level system requirement set, traceability relationship, system status, etc.

[0238] (3) Output: engineering-level system requirements set, traceability relationship, and system status.

[0239] In S2-1, based on the engineering-level system requirement set, traceability relationship, and system status input by the engineering-level system requirement model, the system-level task requirements are defined and the system-level task requirement model is established. Specifically, it includes:

[0240] (1) Input: engineering-level system requirements set, traceability relationship, and system status.

[0241] (2) Steps for establishing the system-level task requirement model:

[0242] Step 1: Prepare system-level task requirement definition:

[0243] a) Determine the mission objectives of the target system (SOI, System of Interest) based on the engineering-level system requirements model;

[0244] b) According to the SOI mission objectives, determine the SOI target analysis strategy, which includes the target decomposition method, the key nodes for target realization, the resources required for target realization, etc., which helps to elaborate the SOI target;

[0245] Step 2: Define the capabilities required for SOI:

[0246] Decompose the SOI task goal into sub-goals, and analyze the capabilities required for SOI based on each SOI sub-goal after decomposition. Analyze the capabilities required for each SOI sub-goal and comprehensively obtain the capability envelope required for SOI.

[0247] Step 3: Characterize SOI capability implementation plan

[0248] Based on the capability envelope required by SOI, define the initial alternative capability implementation plan for SOI and clarify the concepts of each stage of the entire SOI operation cycle.

[0249] Step 4: Evaluate SOI alternative capability implementation solutions

[0250] Evaluate the feasible capability realization plans from the perspective of the resources available in the preliminary alternative capability realization plans (such as funds, personnel, time, materials, and technical basis), and select the preferred alternative capability realization plans (which can be one or more) from the preliminary alternative capability realization plans.

[0251] Step 5: Define system-level task requirements

[0252] a) Define system-level task requirements. Based on SOI goals, SOI capability envelope, etc., express the preferred SOI implementation solution as system-level task requirements through structured text, and form a system-level task requirement set.

[0253] b) Establish the traceability of system-level task requirements. Establish a traceability relationship between system-level task requirements, system implementation solutions, and system goals.

[0254] (3) Output: preliminary system operation concept and system-level task requirements.

[0255] In S2-2, a system-level stakeholder demand model is established based on the system's preliminary operational concept and system-level task requirements input into the system-level task requirements model. Specifically, it includes:

[0256] (1) Input: preliminary system operation concept and system-level task requirements.

[0257] (2) Steps for establishing a system-level stakeholder demand model

[0258] Step 1: Prepare SOI stakeholder requirements definition

[0259] a) Identify the initial operational concept of the SOI and the stakeholders in the SOI life cycle.

[0260] Combined with the initial SOI operation concept and SOI life cycle, identify system-level stakeholders at the system level and determine their roles and responsibilities. According to their roles at the system level, classify the importance of system-level stakeholders and clarify their importance levels.

[0261] b) Define strategies that clearly identify system-level stakeholder needs.

[0262] The strategy for defining the needs of system-level stakeholders includes the roles and responsibilities, importance levels, resources, etc. of system-level stakeholders. Based on the roles and responsibilities of system-level stakeholders in the task, their needs are derived. Based on the importance levels, resources, etc., the conflicting needs of different system-level stakeholders are balanced.

[0263] Step 2: Define SOI stakeholders’ needs

[0264] a) Refine the SOI operation concept.

[0265] Refine SOI operational scenarios to identify all stakeholder needs. Operational scenarios help identify requirements that may have been overlooked.

[0266] b) Identify system-level stakeholder needs.

[0267] Ways to identify system-level stakeholder needs include eliciting their needs directly from system-level stakeholders, or identifying implicit system-level stakeholder needs based on expertise in the field and understanding of the task context.

[0268] Step 3: Transform SOI stakeholder needs into SOI stakeholder requirements

[0269] a) Identify the constraints of the system implementation plan. Constraints are also a type of requirements. Constraints can be obtained from SOI stakeholders (such as production, manufacturing, operation, safety, reliability, maintainability), system indicators, etc.

[0270] b) Identify the system-level stakeholder requirements related to the system's key indicators. System key characteristics include technology maturity, development cycle, etc. Identifying and evaluating the reuse of existing requirements and the degree of reuse is an important way to define system-level stakeholder requirements.

[0271] c) Construct well-formatted requirement statements based on system-level stakeholder needs.

[0272] Step 4: Analyze SOI stakeholder needs

[0273] a) Analyze the system-level stakeholder requirements. This mainly involves classifying and sorting the system-level stakeholder requirements. For reused past stakeholder requirements, analyze their reuse based on factors such as applicability and feasibility, and check their consistency with the specific requirements of the task.

[0274] b) Identify the performance metrics required for each system-level stakeholder requirement.

[0275] c) Feedback the analyzed system-level stakeholder requirements to the system-level stakeholders to confirm that their needs and expectations have been fully captured and expressed. Continuously negotiate conflicting requirements during the requirements analysis process, reach consensus on appropriate trade-offs, and resolve conflicts as early as possible.

[0276] Step 5: Establish SOI stakeholder demand model

[0277] a) Establish traceability of system-level stakeholder requirements. Record how formal requirements meet stakeholder needs, and establish corresponding traceability relationships between operational scenarios, system-level stakeholder requirements, and system-level stakeholder requirements.

[0278] b) Form a complete system-level stakeholder demand model and provide the required key information items. The key information items of the stakeholder demand model include the system-level stakeholder demand set, system-level mission operation concept, etc.

[0279] (3) Output: system-level stakeholder requirements set, system-level mission operation concept, and mission constraints.

[0280] In S2-3, a system-level stakeholder demand model is established based on the system's preliminary operational concept and system-level mission requirements input into the system-level stakeholder demand model. Specifically, it includes:

[0281] (1) Input: system-level stakeholder requirement set, system-level mission operation concept, and mission constraints.

[0282] (2) Steps to establish a system-level system requirements model

[0283] Step 1: Prepare system-level system requirements definition

[0284] Define the functional boundaries of SOI based on the behavior of the system-level system. Combined with the system-level stakeholder requirements set and the system-level task operation concept, describe in detail the behavior of the system and system elements at the system boundary.

[0285] Step 2: Define system-level system requirements

[0286] a) Define each capability required by SOI to accomplish mission objectives at the system operation level.

[0287] b) Identify the operating status and operating mode of SOI. The operating view can be used to describe the dynamic behavior characteristics of the system, such as state changes and operating modes.

[0288] c) Identify the constraints faced by SOI in obtaining corresponding capabilities. Constraints can come from SOI operation scenarios and SOI operation environments, as well as from system interactions and regulatory requirements.

[0289] d) Identify system requirements related to key characteristics such as system states, operating modes, constraints, capabilities, etc.

[0290] e) Define the attributes of system-level system requirements. Determine the attributes of system-level system requirements, including type, priority, identifier, etc.

[0291] Step 3: Analyze system-level system requirements

[0292] a) Analyze the system-level system requirements set. Check whether the system-level system requirements are well stated and meet the formal requirements.

[0293] b) Feedback the analyzed system-level system requirements to the system-level stakeholders for confirmation, ensure that the system-level stakeholder requirements are correctly converted into system-level system requirements, and continuously resolve conflicts in the system requirements set.

[0294] c) Define the key indicators of system requirements. Determine the key indicators required to evaluate the realization of system requirements as the verification criteria for whether the system-level system requirements are met.

[0295] Step 4: Management system requirements definition

[0296] a) Maintain the traceability of system-level system requirements. Establish a two-way traceability relationship between system-level system requirements and system-level stakeholder requirements, and between system-level system requirements and system design models.

[0297] b) Form a complete system-level system requirement model and provide the required key information items, including system requirement set, traceability relationship, system status, etc.

[0298] (3) Output: system-level system requirements set and system operation plan.

[0299] Embodiment 2:

[0300] Based on the same inventive concept, the present invention also provides a system 300 for constructing a demand model for a space mission program demonstration phase. The system structure is as follows: Figure 3 As shown, the system 300 includes:

[0301] The engineering-level requirement model determination module 301 is used to construct an engineering-level task requirement model, an engineering-level stakeholder requirement model and an engineering-level system requirement model based on the task objectives of the space mission; and determine the engineering-level requirement model according to the engineering-level task requirement model, the engineering-level stakeholder requirement model and the engineering-level system requirement model;

[0302] The system-level requirement model determination module 302 is used to construct a system-level task requirement model, a system-level stakeholder requirement model and a system-level system requirement model based on the engineering-level system requirement model; and determine the system-level requirement model according to the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model;

[0303] The mission plan demonstration phase requirement model determination module 303 is used to determine the mission plan demonstration phase requirement model of the space mission target based on the engineering level requirement model and the system level requirement model.

[0304] Preferably, the engineering level requirement model determination module 301 includes:

[0305] The engineering-level task requirement model building module 3011 is used to build an engineering-level task requirement model based on the task objectives of the space mission and obtain the engineering-level task requirement results of the task objectives;

[0306] The engineering-level stakeholder demand model building module 3012 is used to build an engineering-level stakeholder demand model based on the engineering-level task demand results of the task objectives, and obtain the engineering-level stakeholder demand results of the task objectives;

[0307] The engineering-level system requirement model building module 3013 is used to build an engineering-level system requirement model based on the engineering-level stakeholder requirement results of the task objectives, and obtain the engineering-level system requirement results of the task objectives.

[0308] Preferably, the system-level requirement model determination module 302 includes:

[0309] The system-level task requirement model building module 3021 is used to build a system-level task requirement model based on the engineering-level system requirement results of the task target, and obtain the system-level task requirement results of the task target;

[0310] A system-level stakeholder demand model building module 3022 is used to build a system-level stakeholder demand model based on the system-level task demand results of the task objectives, and obtain the system-level stakeholder demand results of the task objectives;

[0311] The system-level system requirement model building module 3023 is used to build a system-level system requirement model based on the system-level stakeholder requirement results of the task objectives, and obtain the system-level system requirement results of the task objectives.

[0312] Preferably, the engineering-level task requirement model building module 3011 is specifically used for:

[0313] Determine the gap between existing products for space missions and stated mission objectives; develop a mission analysis strategy for mission objectives based on the gap; identify the mission systems required to achieve mission objectives based on the mission analysis strategy;

[0314] Identify the trade-offs required to achieve the mission objectives; based on the trade-offs and the mission systems required to achieve the mission objectives, obtain the problems to be solved to achieve the mission objectives;

[0315] Determine the initial operational concept of the mission objectives and the life cycle of the mission objectives; determine alternative implementation plans for the mission objectives based on the initial operational concept of the mission objectives and the problems to be solved in achieving the mission objectives;

[0316] According to the trade-off factors required to achieve the task objectives, select the preferred implementation plan of the task objectives from the alternative implementation plans of the task objectives;

[0317] According to the problems to be solved in achieving the task objectives and the preliminary operational conception of the task objectives, the preferred implementation scheme is converted into the engineering-level task requirements of the task objectives, and the engineering-level task requirement set is obtained according to the engineering-level task requirements; a scheme-problem tracing relationship between the engineering-level task requirements-the preferred implementation scheme of the task objectives-the problems to be solved in achieving the task objectives is established; and an engineering-level task requirement model is constructed according to the engineering-level task requirement set and the scheme-problem tracing relationship;

[0318] Output the engineering-level task requirement results of the task objectives. The engineering-level task requirement results include: preliminary operation concept and engineering-level task requirement set.

[0319] Preferably, the engineering-level stakeholder demand model building module 3012 is specifically used to:

[0320] Based on the engineering-level task requirements of the task objectives, identify the preliminary operational concept of the task objectives and the engineering-level stakeholders within the life cycle of the task objectives at the task level, and determine the task roles and task responsibilities of the engineering-level stakeholders; according to the task roles, classify the importance of the engineering-level stakeholders, determine the importance level of the engineering-level stakeholders, and formulate the task definition strategy required by the engineering-level stakeholders, which includes task roles, task responsibilities, and importance levels;

[0321] Clarify the mission environment based on the initial operational concept of the mission objectives; identify the needs of engineering-level stakeholders based on the needs guided by engineering-level stakeholders and the needs of engineering-level stakeholders identified by understanding domain expertise and mission context;

[0322] Combined with the operation scenario of the mission objective, the preliminary operation concept of the mission objective is refined to obtain a refined engineering-level mission operation concept;

[0323] Transform engineering-level stakeholder needs into engineering-level stakeholder requirements by identifying the task constraints of the preferred implementation plan of the task objectives and identifying stakeholder requirements related to the key characteristics of the task objectives;

[0324] Obtain an engineering-level stakeholder requirement set based on the engineering-level stakeholder requirements, classify and sort the engineering-level stakeholder requirements, identify the performance indicators required for each engineering-level stakeholder requirement, and feed back each engineering-level stakeholder requirement to the corresponding engineering-level stakeholder;

[0325] Establish the task-requirement traceability relationship between engineering-level task requirements-task operation scenarios-engineering-level stakeholder needs-engineering-level stakeholder requirements; build an engineering-level stakeholder requirement model based on the engineering-level stakeholder requirement set and the task-requirement traceability relationship;

[0326] Output the engineering-level stakeholder demand results of the task objectives. The engineering-level stakeholder demand results include: engineering-level stakeholder demand set, engineering-level task operation concept and task constraints.

[0327] Preferably, the engineering-level system requirement model building module 3013 is specifically used for:

[0328] Based on the engineering-level stakeholder demand results of the mission objectives, define the capability boundaries of the mission execution system according to the engineering-level stakeholder demand results;

[0329] Based on the capability boundary of the task execution system, obtain the capability required by the task execution system to complete the task objectives from the task level, and identify the constraints on the capability required by the system state of the task execution system; obtain the engineering-level system requirements based on the system state, constraints, and required capabilities, and determine the attributes of the engineering-level system requirements;

[0330] Obtain an engineering-level system requirement set based on the engineering-level system requirements, analyze the engineering-level system requirements in the engineering-level system requirement set, and feed back the analyzed engineering-level system requirements to corresponding engineering-level stakeholders;

[0331] Establish engineering-level requirements-model traceability relationships between engineering-level system requirements-engineering-level stakeholder requirements, and engineering-level system requirements-system design models respectively; obtain the engineering-level system requirements model based on the engineering-level system requirements set, system status, and engineering-level requirements-model traceability relationship;

[0332] Output the engineering-level system requirement results of the task objectives. The engineering-level system requirement results include: engineering-level system requirement set, engineering-level requirement-model traceability relationship and system status.

[0333] Preferably, the system-level task requirement model building module 3021 is specifically used for:

[0334] Based on the engineering-level system requirement results of the task objectives, the task objectives of the target system are obtained according to the engineering-level system requirement results; according to the task objectives of the target system, the target analysis strategy of the target system is determined;

[0335] Decompose the target system mission objectives into sub-goals, analyze the capabilities required for each of the sub-goals, and determine the envelope of the capabilities required for the target system;

[0336] Determine the preliminary operation concept of the target system based on the required capabilities of the target system, and determine the alternative capability realization plan of the target system based on the preliminary operation concept of the target system;

[0337] Combine the resources of the capability realization scheme and select the optimal capability realization scheme of the target system from the alternative capability realization schemes of the target system;

[0338] Convert the preferred capability realization scheme of the target system into the system-level task requirements of the target system, and obtain the system-level task requirement set according to the system-level task requirements; establish the scheme-goal traceability relationship between the system-level task requirements-the preferred capability realization scheme of the target system-the system goal; and construct the system-level task requirement model according to the system-level task requirement set and the scheme-goal traceability relationship;

[0339] Output the system-level task requirement results of the task objectives. The system-level task requirement results include: preliminary operation concept of the target system and system-level task requirement set.

[0340] Preferably, the system-level stakeholder demand model building module 3022 is specifically used to:

[0341] Based on the system-level task requirements of the task objectives, identify the preliminary operation concept of the target system and the system-level stakeholders in the life cycle of the target system at the system level, and determine the system roles and system responsibilities of the system-level stakeholders; divide the importance of the system-level stakeholders according to the system roles, and determine the importance level of the system-level stakeholders; determine the system definition strategy required by the system-level stakeholders, which includes: system roles, system responsibilities, and importance levels;

[0342] Identify the needs of system-level stakeholders based on the needs obtained through the guidance of system-level stakeholders and the needs of system-level stakeholders identified through understanding of domain expertise and task background; refine the preliminary operation concept of the target system in combination with the operation scenario of the target system to obtain a refined system-level task operation concept;

[0343] Transform system-level stakeholder needs into system-level stakeholder requirements by identifying the system constraints of the target system's preferred capability implementation solution and identifying stakeholder requirements related to the key characteristics of the system's objectives;

[0344] Obtain a set of system-level stakeholder requirements based on system-level stakeholder requirements, classify and sort the system-level stakeholder requirements, identify the performance indicators required for each system-level stakeholder requirement, and feed back each system-level stakeholder requirement to the corresponding system-level stakeholder;

[0345] Establish a system-requirement traceability relationship between system-level task requirements-system operation scenarios-system-level stakeholder needs-system-level stakeholder requirements; build a system-level stakeholder requirement model based on the system-level stakeholder requirement set and the system-requirement traceability relationship;

[0346] Output the system-level stakeholder demand results of the target system. The system-level stakeholder demand results include: system-level stakeholder demand set, system-level task operation concept and system constraints.

[0347] Preferably, the system-level system requirement model building module 3023 is specifically used for:

[0348] Based on the system-level stakeholder requirements results of the target system, define the behavior of the system and system elements at the system boundary according to the system-level stakeholder requirements results of the target system;

[0349] Based on the behaviors on the system boundary, the capabilities required by the target system to complete the mission objectives are obtained from the system level, and the constraints on the system state and required capabilities of the target system are identified; based on the system state, constraints, and required capabilities, the system-level system requirements are obtained, and the attributes of the system-level system requirements are determined;

[0350] Obtain a system-level system requirement set according to the system-level system requirements, analyze the system-level system requirements in the system-level system requirement set, and feed back the analyzed system-level system requirements to corresponding system-level stakeholders;

[0351] Establish system-level requirement-model traceability relationships between system-level system requirement model-system-level stakeholder requirements and system-level system requirement model-system design model respectively; obtain system-level system requirement model according to system-level system requirement set and system-level requirement-model traceability relationship;

[0352] Output the system-level system requirement results of the target system. The system-level system requirement results include: the system-level system requirement set of the target system and the system operation plan of the target system.

[0353] Embodiment 3:

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

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

[0356] Embodiment 4:

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

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

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

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

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

[0362] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit its protection scope. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the field should understand that after reading the present invention, those skilled in the art can still make various changes, modifications or equivalent substitutions to the specific implementation methods of the application, but these changes, modifications or equivalent substitutions are all within the protection scope of the claims to be approved.

Claims

1. A method for constructing a demand model in the space mission program demonstration phase, characterized in that: include: Based on the mission objectives of the space mission, construct an engineering-level mission requirement model, an engineering-level stakeholder requirement model and an engineering-level system requirement model; determine the engineering-level requirement model according to the engineering-level mission requirement model, the engineering-level stakeholder requirement model and the engineering-level system requirement model; Based on the engineering-level system requirement model, construct a system-level task requirement model, a system-level stakeholder requirement model and a system-level system requirement model; determine a system-level requirement model according to the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model; The demand model for the space mission program demonstration phase is determined based on the engineering-level demand model and the system-level demand model.

2. The method according to claim 1, characterized in that The engineering-level mission requirement model, engineering-level stakeholder requirement model and engineering-level system requirement model are constructed based on the mission objectives of the space mission, including: Based on the mission objective of the space mission, construct the engineering-level mission requirement model to obtain the engineering-level mission requirement result of the mission objective; Based on the engineering-level task requirement results of the task objectives, construct the engineering-level stakeholder requirement model to obtain the engineering-level stakeholder requirement results of the task objectives; Based on the engineering-level stakeholder demand results of the task objective, the engineering-level system demand model is constructed to obtain the engineering-level system demand results of the task objective.

3. The method according to claim 1 or 2, characterized in that: The step of constructing a system-level task requirement model, a system-level stakeholder requirement model and a system-level system requirement model based on the engineering-level system requirement model includes: Based on the engineering-level system requirement results of the task target, construct the system-level task requirement model to obtain the system-level task requirement results of the task target; Based on the system-level task requirement results of the task target, construct the system-level stakeholder requirement model to obtain the system-level stakeholder requirement results of the task target; Based on the system-level stakeholder demand results of the task objective, the system-level system demand model is constructed to obtain the system-level system demand results of the task objective.

4. The method according to claim 2, characterized in that: The step of constructing the engineering-level mission requirement model based on the mission objective of the space mission and obtaining the engineering-level mission requirement result of the mission objective includes: Determine the gap between existing products for the space mission and the mission objectives; formulate a mission analysis strategy for the mission objectives based on the gap; identify the mission systems required to achieve the mission objectives based on the mission analysis strategy; Identify the trade-off factors required to achieve the mission objectives; obtain the problems to be solved to achieve the mission objectives based on the trade-off factors and the mission systems required to achieve the mission objectives; Determine the preliminary operational concept of the mission objective and the life cycle of the mission objective; determine alternative implementation plans for the mission objective based on the preliminary operational concept of the mission objective and the problems to be solved in achieving the mission objective; According to the trade-off factors required to achieve the task goal, select the preferred implementation plan of the task goal from the alternative implementation plans of the task goal; According to the problems to be solved in achieving the task objectives and the preliminary operational conception of the task objectives, the preferred implementation scheme is converted into the engineering-level task requirements of the task objectives, and an engineering-level task requirement set is obtained according to the engineering-level task requirements; a scheme-problem tracing relationship between the engineering-level task requirements-the preferred implementation scheme of the task objectives-the problems to be solved in achieving the task objectives is established; and the engineering-level task requirement model is constructed according to the engineering-level task requirement set and the scheme-problem tracing relationship; Output the engineering-level task requirement results of the task target, wherein the engineering-level task requirement results include: preliminary operation concept and engineering-level task requirement set.

5. The method according to claim 4, characterized in that The step of constructing the engineering-level stakeholder demand model based on the engineering-level task demand result of the task target to obtain the engineering-level stakeholder demand result of the task target includes: Based on the engineering-level task requirement results of the task target, identify the preliminary operational concept of the task target and the engineering-level stakeholders within the life cycle of the task target at the task level, and determine the task roles and task responsibilities of the engineering-level stakeholders; according to the task roles, classify the importance of the engineering-level stakeholders, determine the importance levels of the engineering-level stakeholders, and formulate the task definition strategy required by the engineering-level stakeholders, the task definition strategy includes task roles, task responsibilities, and importance levels; Based on the preliminary operational concept of the mission objectives, clarify the mission environment; identify the engineering level stakeholder needs based on the needs guided by the engineering level stakeholders and the engineering level stakeholder needs identified by understanding the domain expertise and mission context; Refining the preliminary operation concept of the mission objective in combination with the operation scenario of the mission objective to obtain a refined engineering-level mission operation concept; The engineering-level stakeholder needs are converted into engineering-level stakeholder requirements by identifying the task constraints of the preferred implementation solution of the task goal and identifying the stakeholder requirements related to the key characteristics of the task goal; Obtaining an engineering-level stakeholder requirement set according to the engineering-level stakeholder requirements, classifying and sorting the engineering-level stakeholder requirements, identifying the performance indicators required for each engineering-level stakeholder requirement, and feeding back each engineering-level stakeholder requirement to the corresponding engineering-level stakeholder; Establishing a task-requirement traceability relationship between the engineering-level task requirement-task operation scenario-engineering-level stakeholder needs-engineering-level stakeholder requirements; constructing the engineering-level stakeholder requirement model according to the engineering-level stakeholder requirement set and the task-requirement traceability relationship; Outputting the engineering-level stakeholder demand results of the task goal, the engineering-level stakeholder demand results comprising: an engineering-level stakeholder demand set, an engineering-level task operation conception, and task constraints.

6. The method according to claim 5, characterized in that The step of constructing the engineering-level system requirement model based on the engineering-level stakeholder requirement results of the task target to obtain the engineering-level system requirement results of the task target includes: Based on the engineering-level stakeholder demand results of the task objectives, define the capability boundary of the task execution system according to the engineering-level stakeholder demand results; Based on the capability boundary of the task execution system, the capability required by the task execution system to complete the task objectives is obtained from the task level, and the constraints on the capability required by the system state of the task execution system are identified; based on the system state, constraints, and required capability, the engineering-level system requirements are obtained, and the attributes of the engineering-level system requirements are determined; Obtaining an engineering-level system requirement set according to the engineering-level system requirements, analyzing the engineering-level system requirements in the engineering-level system requirement set, and feeding back the analyzed engineering-level system requirements to corresponding engineering-level stakeholders; Establishing engineering-level system requirements-engineering-level stakeholder requirements and engineering-level system requirements-system design models as traceability relationships respectively; obtaining an engineering-level system requirements model according to the engineering-level system requirements set, the system state and the engineering-level requirements-model traceability relationship; Output the engineering-level system requirement results of the task target, the engineering-level system requirement results including: an engineering-level system requirement set, the engineering-level requirement-model traceability relationship and the system status.

7. The method according to claim 3, characterized in that The step of constructing the system-level task requirement model based on the engineering-level system requirement result of the task target to obtain the system-level task requirement result of the task target includes: Based on the engineering-level system requirement results of the task target, obtaining the task target of the target system according to the engineering-level system requirement results; determining the target analysis strategy of the target system according to the task target of the target system; Decomposing the target system task goal into sub-goals, analyzing the capabilities required for each of the sub-goals, and determining the envelope of the capabilities required for the target system; Determine a preliminary operation concept of the target system based on the envelope of the required capabilities of the target system, and determine an alternative capability realization plan for the target system based on the preliminary operation concept of the target system; In combination with the resources of the capability implementation scheme, a preferred capability implementation scheme of the target system is selected from the candidate capability implementation schemes of the target system; Convert the preferred capability implementation scheme of the target system into the system-level task requirement of the target system, and obtain a system-level task requirement set according to the system-level task requirement; establish a scheme-target traceability relationship between the system-level task requirement-preferred capability implementation scheme of the target system-system target; and construct the system-level task requirement model according to the system-level task requirement set and the scheme-target traceability relationship; Output the system-level task requirement results of the task target, wherein the system-level task requirement results include: a preliminary operation concept of the target system and a system-level task requirement set.

8. The method according to claim 7, characterized in that The step of constructing the system-level stakeholder demand model based on the system-level task requirement result of the task target to obtain the system-level stakeholder demand result of the task target includes: Based on the system-level task requirement results of the task objectives, identify the preliminary operation concept of the target system and the system-level stakeholders within the life cycle of the target system at the system level, and determine the system roles and system responsibilities of the system-level stakeholders; classify the importance of the system-level stakeholders according to the system roles, and determine the importance levels of the system-level stakeholders; determine the system definition strategies required by the system-level stakeholders, and the system definition strategies include: system roles, system responsibilities, and importance levels; Based on the needs obtained through the guidance of system-level stakeholders and the system-level stakeholder needs identified through understanding of domain expertise and task background, identify the system-level stakeholder needs; in combination with the operation scenario of the target system, refine the preliminary operation concept of the target system to obtain a refined system-level task operation concept; Transforming the system-level stakeholder needs into system-level stakeholder requirements by identifying system constraints of the preferred capability realization scheme of the target system and identifying stakeholder requirements related to the key characteristics of the system objectives; Obtaining a set of system-level stakeholder requirements according to the system-level stakeholder requirements, classifying and ranking the system-level stakeholder requirements, identifying the performance indicators required for each system-level stakeholder requirement, and feeding back each system-level stakeholder requirement to the corresponding system-level stakeholder; Establishing a system-requirement traceability relationship between the system-level task requirements-system operation scenarios-system-level stakeholder needs-system-level stakeholder requirements; constructing the system-level stakeholder requirement model according to the system-level stakeholder requirement set and the system-requirement traceability relationship; Outputting the system-level stakeholder demand results of the target system, wherein the system-level stakeholder demand results include: a system-level stakeholder demand set, a system-level task operation conception, and a system constraint.

9. The method according to claim 8, characterized in that The system-level stakeholder requirement results based on the task objectives, constructing the system-level system requirement model, and obtaining the system-level system requirement results of the task objectives include: Based on the system-level stakeholder requirements results of the target system, define the behavior of the system and system elements on the system boundary according to the system-level stakeholder requirements results of the target system; Based on the behavior on the system boundary, the capabilities required for the target system to complete the task objectives are obtained from the system level, and the system state of the target system and the constraints of the required capabilities are identified; based on the system state, constraints, and required capabilities, system-level system requirements are obtained, and the attributes of the system-level system requirements are determined; Obtaining a system-level system requirement set according to the system-level system requirement, analyzing the system-level system requirements in the system-level system requirement set, and feeding back the analyzed system-level system requirements to corresponding system-level stakeholders; Establishing system-level requirement-model traceability relationships between system-level system requirement model and system-level stakeholder requirement, and between system-level system requirement model and system design model respectively; obtaining a system-level system requirement model according to the system-level system requirement set and the system-level requirement-model traceability relationship; Output the system-level system requirement results of the target system, wherein the system-level system requirement results include: a system-level system requirement set of the target system and a system operation plan of the target system.

10. A demand model building system for the space mission program demonstration phase, characterized in that: include: An engineering-level requirement model determination module is used to construct an engineering-level task requirement model, an engineering-level stakeholder requirement model and an engineering-level system requirement model based on the task objectives of the space mission; and to determine the engineering-level requirement model according to the engineering-level task requirement model, the engineering-level stakeholder requirement model and the engineering-level system requirement model; A system-level requirement model determination module, configured to construct a system-level task requirement model, a system-level stakeholder requirement model and a system-level system requirement model based on the engineering-level system requirement model; and determine a system-level requirement model according to the system-level task requirement model, the system-level stakeholder requirement model and the system-level system requirement model; The module for determining the demand model for the mission plan demonstration phase is used to determine the demand model for the space mission plan demonstration phase according to the engineering level demand model and the system level demand model.

Images