Architecture design method based on requirements and functions and computer equipment

Abstract

The invention relates to the technical field of system engineering based on models, in particular to an architecture design method based on requirements and functions and computer equipment. The method comprises the following steps: creating a scheme template of a system architecture based on a demand list, and matching the demand list in a full-quantity model to obtain a function set corresponding to each design demand in the demand list; matching each function set in the full-quantity model to obtain an instance set corresponding to each target function; a plurality of initial schemes are constructed based on the scheme template, each initial scheme is retrieved based on a mutual exclusion relationship, a target scheme is determined from all the initial schemes according to a retrieval result, a corresponding target architecture is constructed based on all the target schemes, and all the target architectures are architecture schemes corresponding to the demand list. By adopting the method, the comprehensiveness of architecture design for complex equipment can be improved.

Description

Technical Field

[0001] This application relates to the technical field of model-based systems engineering, and particularly to an architecture design method and a computer device based on requirements and functions. Background Art

[0002] With the development of the field of systems engineering, model-based systems engineering (MBSE) has gradually become an important system design method. In the related art, designers take the design requirements of a product as input and carry out the following system design work by manually constructing a system model: analyze the functions that the system needs to possess from the requirements; then, aiming at realizing the system functions, carry out system architecture design for the product; and select instances for each component in the architecture to complete the system design of the product.

[0003] In the design process of complex equipment, model-based systems engineering is also an important auxiliary design means. In the related art, in the design stage of complex equipment, when designers adopt systems engineering to design the system model of complex equipment, they are easily restricted by personal knowledge and experience and it is difficult to obtain the full amount of domain knowledge as technical support; designers often propose one or several possible configurations based on historical experience and then carry out subsequent design processes on this basis. This method cannot comprehensively explore the design domain, so it is impossible to obtain a wider range of system architecture possibilities, resulting in an incomplete architecture design.

[0004] Therefore, how to improve the comprehensiveness of the architecture design for complex equipment is an urgent problem to be solved. Summary of the Invention

[0005] Based on this, in view of the above technical problems, it is necessary to provide an architecture design method and a computer device based on requirements and functions that can improve the comprehensiveness of the architecture design for complex equipment.

[0006] In a first aspect, this application provides an architecture design method based on requirements and functions, including:

[0007] Create a scheme template for the system architecture based on the requirements list and match the requirements list in the full model to obtain a function set corresponding to each design requirement in the requirements list; the function set includes at least one target function, and the full model includes the corresponding relationship between requirements and functions;

[0008] Match each function set in the full model to obtain an instance set including at least one target instance corresponding to each target function, and the full model further includes the corresponding relationship between instances and functions;

[0009] Construct multiple initial solutions based on the solution template, where each initial solution includes the functional elements of one of the target functions corresponding to each design requirement, and the instance elements of one of the target instances corresponding to each target function;

[0010] Retrieve each initial solution based on the mutual exclusion relationship, and determine the target solution from each initial solution according to the retrieval result. The target solution is the initial solution where there is no mutual exclusion relationship between elements; the full model also includes the mutual exclusion relationships between elements;

[0011] Construct the corresponding target architectures based on each target solution, and each target architecture is the architecture solution corresponding to the requirements list.

[0012] In one embodiment, the matching of each function set in the full model to obtain the instance set corresponding to each target function includes:

[0013] Match each function set in the full model to obtain a component set corresponding to each target function, and the component set includes at least one target component;

[0014] Match each component set in the full model to obtain an instance set corresponding to each target component. The full model also includes the corresponding relationship between components and functions, and the corresponding relationship between instances and components.

[0015] In one embodiment, the matching of each function set in the full model to obtain the instance set corresponding to each target function includes:

[0016] Retrieve each target function in the full model, and classify each target function into a first target function and a second target function according to the retrieval result; the first target function is a lower-level function that can be split in the full model, and the second target function is a lower-level function that cannot be split in the full model. The full model also includes the upper and lower level relationships between functions;

[0017] Retrieve each second target function in the full model to obtain the instance set corresponding to each second target function;

[0018] In the function set corresponding to the first target function, replace the first target function with each lower-level function corresponding to the first target function to obtain the updated function set.

[0019] In one embodiment, the method further includes:

[0020] For each of the initial solutions, retrieve the initial solution in the full model, and match corresponding connectors to the initial solution. The connectors are used to connect elements corresponding to instances with a connection relationship, and the connection relationship represents at least one interaction relationship among substances, information, and energy between instances.

[0021] In one embodiment, the requirements list further includes relationship requirements. Retrieving each of the initial solutions based on the mutual exclusion relationship and determining a target solution from each of the initial solutions according to the retrieval results includes:

[0022] Retrieving each of the initial solutions based on the first mutual exclusion relationship represented by the relationship requirements to obtain a first retrieval result;

[0023] Retrieving each of the initial solutions based on the second mutual exclusion relationship included in the full model to obtain a second retrieval result;

[0024] Determining a target solution from each of the initial solutions based on the first retrieval result and / or the second retrieval result.

[0025] In one embodiment, constructing a corresponding target architecture based on each of the target solutions includes:

[0026] For each of the target solutions, deleting elements that do not exist in the target solution in the full model to obtain the target architecture corresponding to the target solution.

[0027] In a second aspect, the present application further provides an architecture design device based on requirements and functions. The device includes a first matching module, a second matching module, an initial solution construction module, a target solution screening module, and a target architecture construction module, where:

[0028] The first matching module is configured to create a solution template for the system architecture based on a requirements list, and match the requirements list in the full model to obtain a function set corresponding to each design requirement in the requirements list; the function set includes at least one target function, and the full model includes the correspondence between requirements and functions;

[0029] The second matching module is configured to match each of the function sets in the full model to obtain an instance set including instances corresponding to each of the target functions. The instance set includes at least one target instance, and the full model further includes the correspondence between instances and functions;

[0030] An initial solution construction module, configured to construct a plurality of initial solutions based on the solution template, where each initial solution includes a function element of one target function corresponding to each design requirement, and an instance element of one target instance corresponding to each target function;

[0031] A target solution screening module, configured to retrieve each initial solution based on the mutual exclusion relationship, and determine a target solution from each initial solution according to the retrieval result, where the target solution is the initial solution in which there is no mutual exclusion relationship between elements; the full-scale model also includes the mutual exclusion relationship between elements;

[0032] A target architecture construction module, configured to construct a corresponding target architecture based on each target solution, and each target architecture is an architecture solution corresponding to the requirement list.

[0033] In a third aspect, the present application further provides a computer device, including a memory and a processor, where the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0034] Create a solution template for the system architecture based on the requirement list, and match the requirement list in the full-scale model to obtain a function set corresponding to each design requirement in the requirement list; the function set includes at least one target function, and the full-scale model includes the corresponding relationship between requirements and functions;

[0035] Match each function set in the full-scale model to obtain an instance set including at least one target instance corresponding to each target function, and the full-scale model further includes the corresponding relationship between instances and functions;

[0036] Construct a plurality of initial solutions based on the solution template, where each initial solution includes a function element of one target function corresponding to each design requirement, and an instance element of one target instance corresponding to each target function;

[0037] Retrieve each initial solution based on the mutual exclusion relationship, and determine a target solution from each initial solution according to the retrieval result, where the target solution is the initial solution in which there is no mutual exclusion relationship between elements; the full-scale model also includes the mutual exclusion relationship between elements;

[0038] Construct a corresponding target architecture based on each target solution, and each target architecture is an architecture solution corresponding to the requirement list.

[0039] In a fourth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0040] Create a solution template for the system architecture based on the requirements list, and match the requirements list in the full model to obtain a function set corresponding to each design requirement in the requirements list; the function set includes at least one target function, and the full model includes the corresponding relationship between requirements and functions;

[0041] Match each of the function sets in the full model to obtain an instance set including target instances corresponding to each of the target functions, the instance set includes at least one target instance, and the full model further includes the corresponding relationship between instances and functions;

[0042] Construct a plurality of initial solutions based on the solution template, the initial solutions include function elements of one of the target functions corresponding to each design requirement, and instance elements of one of the target instances corresponding to each target function;

[0043] Retrieve each of the initial solutions based on the mutual exclusion relationship, and determine a target solution from each of the initial solutions according to the retrieval result, the target solution is the initial solution in which there is no mutual exclusion relationship between elements; the mutual exclusion relationship between each element is also included in the full model;

[0044] Construct corresponding target architectures based on each of the target solutions, and each of the target architectures is an architecture solution corresponding to the requirements list.

[0045] In a fifth aspect, the present application also provides a computer program product, including a computer program, which when executed by a processor implements the following steps:

[0046] Create a solution template for the system architecture based on the requirements list, and match the requirements list in the full model to obtain a function set corresponding to each design requirement in the requirements list; the function set includes at least one target function, and the full model includes the corresponding relationship between requirements and functions;

[0047] Match each of the function sets in the full model to obtain an instance set including target instances corresponding to each of the target functions, the instance set includes at least one target instance, and the full model further includes the corresponding relationship between instances and functions;

[0048] Construct a plurality of initial solutions based on the solution template, the initial solutions include function elements of one of the target functions corresponding to each design requirement, and instance elements of one of the target instances corresponding to each target function;

[0049] Retrieve each of the initial solutions based on the mutual exclusion relationship, and determine the target solution from each of the initial solutions according to the retrieval result, where the target solution is the initial solution in which there is no mutual exclusion relationship between elements; the full-scale model also includes the mutual exclusion relationships between elements.

[0050] Construct corresponding target architectures based on each of the target solutions, where each of the target architectures is the architecture solution corresponding to the requirements list.

[0051] The above architecture design method, device, computer device, storage medium, and computer program product based on requirements and functions pre-construct a full-scale model including the corresponding relationship between requirements and functions and the corresponding relationship between functions and instances, so that after obtaining the requirements list, the corresponding function sets can be matched one by one for the design requirements in the requirements list from the full-scale model, and then the instance sets corresponding to each target function in the function sets can be matched; establish a solution template based on the requirements list, and then construct multiple initial solutions based on the solution template and the matched function sets and instance sets, and further screen from each initial model based on the mutual exclusion relationship between elements to obtain the target solution in which there is no mutual exclusion relationship between elements, and then construct the corresponding target architecture based on each target solution, where each target architecture is all possible architectures corresponding to the requirements list; since a pre-constructed full-scale model is used to support the matching of elements at each level, the subjective participation of people is reduced in this process, so the design stage is less restricted by personal knowledge and experience; thus, more comprehensive target architectures can be obtained, improving the comprehensiveness of complex equipment design. Brief Description of the Drawings

[0052] To more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following will briefly introduce the drawings required for use in the description of the embodiments or related technologies. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0053] Figure 1 It is a schematic flowchart of an architecture design method based on requirements and functions in an embodiment;

[0054] Figure 2 It is a schematic diagram of the construction process of a full-scale model in an embodiment;

[0055] Figure 3 It is a schematic diagram of the refinement relationship between functions and design requirements in an embodiment;

[0056] Figure 4 It is a schematic diagram of the refinement relationship between complex functions and simple functions in an embodiment;

[0057] Figure 5 Schematic diagram of the allocation relationship between functions and components in an embodiment;

[0058] Figure 6 Schematic diagram of the relationship between components and instances in an embodiment;

[0059] Figure 7 Schematic diagram of the connection relationship between instances in an embodiment;

[0060] Figure 8 Schematic diagram of the mutual exclusion relationship between functions, components, and instances in an embodiment;

[0061] Figure 9 Schematic diagram of the mutual exclusion relationship between component attributes and connectors in an embodiment;

[0062] Figure 10 Partial schematic diagram of the full-scale model constructed in an embodiment;

[0063] Figure 11 Schematic diagram of the process for obtaining an instance set by matching a target function in an embodiment;

[0064] Figure 12 Structural block diagram of an architecture design device based on requirements and functions in an embodiment;

[0065] Figure 13 Internal structure diagram of a computer device in an embodiment. Detailed implementation manners

[0066] In order to make the objectives, technical solutions, and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0067] The architecture design method based on requirements and functions provided by the embodiments of the present application is executed by a computer device; wherein, the computer device can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, and servers, etc.; the server can be implemented by an independent server or a server cluster composed of multiple servers.

[0068] In an exemplary embodiment, as Figure 1 shown, a method for architecture design based on requirements and functions is provided, including the following steps 110 - step 150, wherein:

[0069] Step 110: Create a solution template for the system architecture based on the requirements list, and match the requirements list in the full-scale model to obtain the function set corresponding to each design requirement in the requirements list; the function set includes at least one target function, and the full-scale model includes the corresponding relationship between requirements and functions.

[0070] For the embodiments of the present application, the various design requirements in the requirements list may be directly input by the user. However, since the information input by the user is usually natural language, it is necessary to perform word segmentation and semantic analysis on the natural language input by the user before obtaining each user requirement. Since the obtained user requirements may not be standardized, directly matching the corresponding function set from the full-scale model based on the user requirements has relatively low accuracy. In order to obtain more standardized requirements, in the embodiments of the present application, each design requirement is further retrieved and searched in the full-scale model to obtain the standardized design requirement corresponding to each user requirement in the full-scale model. Then, based on the design requirement corresponding to each user requirement, the function set is matched in the full-scale model.

[0071] In another implementation manner, the various design requirements in the full-scale model can also be displayed to the user in a visual manner. Therefore, the various design requirements in the requirements list can also be selected from the full-scale model based on the selection instructions input by the user. In this way, more accurate design requirements can be directly obtained based on the user's selection, and at the same time, the time for semantic analysis is reduced, and the generation efficiency of the requirements list is improved. The various design requirements in the requirements list are arranged in a preset order. The arrangement order can be based on the generation time of the design requirements or the order of the name characters. The embodiments of the present application do not specifically limit the logic of the arrangement order.

[0072] For the full-scale model, the full-scale model includes the corresponding relationship between the elements at each level required in the design stage of the aeroengine; in a possible example, in the design stage of the aeroengine, the elements at each level are, from top to bottom: requirements - functions - components - instances; the elements at each level can also be other hierarchical relationships, and the embodiments of the present application do not specifically limit this. In the order of the arrangement of the requirements involved in the requirements list, each design requirement is used as the input information of the full-scale model and retrieved and matched in the full-scale model in turn, so as to construct the function set corresponding to the design requirement from the various target functions corresponding to the design requirement in the full-scale model. Specifically, the initial solution template constructed based on the requirements list is one, and this solution template includes various design requirements and leads out the corresponding lower-level branches for each design requirement. Each lower-level branch corresponds to a target function in the function set.

[0073] Step 120: Match each function set in the full-scale model to obtain an instance set corresponding to each target function. The instance set includes at least one target instance. The full-scale model also includes the corresponding relationship between instances and functions.

[0074] For the embodiments of the present application, for each function set, each target function in the function set is arranged in a set order; each target function is used as the input information of the full-scale model to perform retrieval and matching in the full-scale model to obtain each target instance corresponding to each target function; for each target function, each target instance corresponding to each target function is used to construct the instance set corresponding to this target function.

[0075] Step 130: Construct multiple initial solutions based on the solution template. The initial solution includes the function elements of one target function corresponding to each design requirement, and the instance elements of one target instance corresponding to each target function.

[0076] For the embodiments of the present application, there are two realizable ways to construct multiple initial solutions based on the solution template. The first realizable way is: taking the design requirement as the element of the first level, when matching the lower-level set corresponding to the element of any level in the full-scale model, sequentially match the corresponding lower-level set in the full-scale model according to the arrangement order of the elements in the element of this level. The lower-level set includes the corresponding lower-level elements. If there are N lower-level elements in the lower-level set of an element, then copy the current solution template N - 1 times, and then correspond the N lower-level elements to the N solution templates one by one, and fill a non-repeated lower-level element in each solution template to the position of the lower-level branch of the corresponding element; where N is a positive integer greater than 1. Match from the upper-level element to the lower-level element in sequence according to the upper-lower relationship of the elements; in this process, the solution template is continuously copied and increased, and finally all possible solution templates are obtained as the initial template.

[0077] The second achievable way is as follows: taking the design requirements as the elements at the first level, when matching the elements at any level in the full model, sequentially match the corresponding lower-level sets in the full model according to the arrangement order of the elements in that level. The lower-level sets include the corresponding lower-level elements. When each lower-level set corresponding to an element is matched, fill the lower-level elements in the lower-level set to the positions of the lower-level branches of the corresponding element in the solution template. Further, according to the upper-lower relationship of the elements, match from the upper-level elements to the lower-level elements in sequence, and finally obtain a solution model including the lower-level branch relationships of the elements at each level from the design requirements downwards. Split from each branch chain corresponding to a design requirement to obtain each independent branch corresponding to each design requirement. In each independent branch, there is only one lower-level element at each level, and the independent branches do not repeat each other. Then, arrange and combine the independent branches corresponding to each design requirement to form multiple non-repeating combined solutions, and then fill each combined solution into a new solution template as an initial solution. Among them, a combined solution includes one independent branch corresponding to each design requirement.

[0078] Step 140: Retrieve each initial solution based on the mutual exclusion relationship, and determine the target solution from each initial solution according to the retrieval result. The target solution is the initial solution in which there is no mutual exclusion relationship between elements; the mutual exclusion relationships between elements are also included in the full model.

[0079] Step 150: Construct the corresponding target architecture based on each target solution. Each target architecture is the architecture solution corresponding to the requirements list.

[0080] For the embodiments of the present application, for each initial solution, perform a mutual exclusion relationship check, that is, retrieve each initial solution based on the mutual exclusion relationship, and the retrieval result indicates whether there is a mutual exclusion relationship. The mutual exclusion relationship can include the mutual exclusion relationship between elements at the same level, and can also include the mutual exclusion relationship between elements across levels. Further, for the initial solution whose retrieval result indicates the existence of a mutual exclusion relationship, directly delete it; then use the initial solution whose retrieval result indicates the non-existence of a mutual exclusion relationship as the target solution.

[0081] For each target solution, the target architecture can be a file in other formats constructed based on the target solution, or the relationship of the elements in the target solution reconstructed in a template with other structures. The embodiments of the present application do not specifically limit this. The final obtained target architectures are the various achievable architectures corresponding to the requirements list.

[0082] In the above architecture design method based on requirements and functions, a full-scale model including the correspondence between requirements and functions and the correspondence between functions and instances is pre-constructed. Thus, after obtaining the requirements list, the corresponding function sets can be matched one by one for the design requirements in the requirements list from the full-scale model, and then the instance sets corresponding to each target function in the function sets can be matched; a solution template is established based on the requirements list, and then multiple initial solutions are constructed based on the solution template and the matched function sets and instance sets. Further, a target solution in which there are no mutually exclusive relationships between elements is selected from the initial models based on the mutually exclusive relationships between elements, and then the corresponding target architecture is constructed based on each target solution. Each target architecture is all possible architectures corresponding to the requirements list; since a pre-constructed full-scale model is used to support the matching of elements at all levels, the subjective participation of people is reduced in this process. Therefore, the design stage is less restricted by personal knowledge and experience; thus, more comprehensive target architectures can be obtained, improving the comprehensiveness of complex equipment design.

[0083] In one embodiment, the full-scale model is constructed based on the domain knowledge in an aeroengine, where the domain knowledge includes documents such as literature, books, standard specification documents, various demonstration and research reports in the aeroengine field; then, information related to system architecture design such as requirements, functions, components, and instances and the relationships between the information are extracted from the domain knowledge to construct the full-scale model. Among them, the process of extracting information and relationships from the domain knowledge can be realized through an LLM (Large Language Model) model, that is, the various documents of the domain knowledge are used as the input information of the LLM model, and the corresponding prompt words and Prompt (prompt) template instances are input as the prompt information of the LLM model to obtain the summary data of the relevant information and relationships in the domain knowledge output by the LLM model; then, the full-scale model is further constructed according to the summary data.

[0084] In one embodiment, a SysML model based on the SysML (Systems Modeling Language) language is used as a blank template, and the domain knowledge is expressed in the blank template to construct the full-scale model; the composition process of the full-scale model is as Figure 2 shown, and specifically may include step S01-step S06, where:

[0085] S01. Construct the relationship between design requirements and functions.

[0086] S02. Express the relationship between functions.

[0087] S03. Express the relationship between functions and components.

[0088] S04. Express the relationship between components and examples.

[0089] Specifically, for step S01: The design requirements come from the expectations and requirements of the intended users for the product system (aero-engine). The design requirements are divided into two categories: functional requirements and non-functional requirements (relationship requirements). Among them, the functional requirements clarify what the system should do, and the non-functional requirements clarify the conditions and constraints that the system must meet. The function describes the behavior that the system needs to execute to meet the requirements and can be analyzed from the functional requirements. In the SysML model (blank template), the Requirement element is used to represent requirements, and the Activity element is used to represent functions. A Refine relationship is created between the requirement element and the activity element to indicate that the activity element is obtained by analyzing the information of the requirement element. Using domain knowledge as the input of the LLM model, obtain all the relationships between requirements and functions in the domain knowledge output by the LLM model and express them in the SysML model (blank template).

[0090] Create a BDD diagram (Block Definition Diagram) in the SysML model. In the BDD diagram, create a Requirement element to express the design requirements and an Activity element to express the functions. Create a Refine relationship between the requirement element and the activity element to indicate that the function is analyzed from the connected design requirements. Among them, for the connection line expressing the Refine relationship, the arrow end points to the upper-level element; that is, for the connection line of the Refine relationship between the design requirements and the function, the arrow points from the function to the design requirements. In an example, the Refine relationship between the function and the design requirements is as Figure 3 shown, and it can be seen from Figure 3 that both function OA and function OB are analyzed from design requirement RA, while function OC is analyzed from design requirement RB.

[0091] For step S02: A function may be a simple function or a complex function; the functions directly analyzed from the functional requirements are of a relatively high complexity, usually all complex functions, which is not conducive to the accuracy of subsequent matching. Therefore, it is necessary to combine domain knowledge to decompose the complex function into more specific simple functions. The simple function is a sub-function of the complex function. In the SysML model, both the complex function and its sub-functions are represented by the Activity element. A Refine relationship is created between the activity element representing the complex function and the activity element representing the sub-function to indicate that the sub-function is the lower-level function of the complex function.

[0092] In one example, generating thrust is a complex function. Intake, compression, combustion, expansion work, and exhaust are all sub-functions of the complex function of generating thrust, and each is a simple function.

[0093] Using domain knowledge as the input to the LLM model, obtain all the relationships between complex functions and simple functions output by the LLM model and express them in the SysML model. Create an Activity element in the BDD diagram to represent a function, and create a Refine relationship between two Activity elements to indicate that the function is decomposed from the connected function elements. As Figure 4 shown, it is a schematic diagram of the Refine relationship between complex functions and simple functions in one example; from Figure 4 it can be seen that simple function DA and simple function DB are both decomposed from complex function OB, while simple functions DC, DD, and DE are all decomposed from complex function OC.

[0094] For step S03: In the SysML model, use a Block element to represent the components of the system; further, create an Allocate relationship between the Activity element representing the function and the Block element representing the component to indicate that the function is executed by the component. Using domain knowledge as the input to the LLM model, obtain all the relationships between functions and components output by the LLM model and express them in the SysML model. Create an Activity element in the BDD diagram to represent the function, create a Block element to represent the component, and create an Allocate relationship between the Activity element and the Block element to indicate that the function is executed by the connected component. Among them, for the connection line expressing the Allocate relationship, the arrow end points to the Block element corresponding to the component. As Figure 5 shown, it is a representation of the Allocate relationship between the Activity element of the function and the Block element of the component in a BDD diagram. From Figure 5 it can be seen that function OA can be executed by components BA and BB, and functions DB and DC can both be executed by component BD. The relationships between other functions and components are similar and will not be elaborated here.

[0095] An instance is the physical implementation solution of a component. The difference between a component and an instance is that a component is an abstract logical concept that only contains part of the information to support the system design to meet the requirements; an instance is the specific expression of a component in the real world. Common forms of manifestation can be real product component objects or product component models fully defined in the virtual space; an instance has more and more specific information compared to the corresponding component.

[0096] For step S04: In the SysML model, both components and their corresponding instances are represented by the Block element. A generalization relationship is created between the component and the corresponding instance element, indicating that the instance is a specific implementable solution of the component. Using domain knowledge as the input to the LLM model, all the relationships between components and instances output by the LLM model are obtained and expressed in the SysML model. In the BDD diagram, Block elements are created to represent components and instances, and a generalization relationship is created between the Block elements to indicate that the instance is a physical implementation solution of the component. In the connection line expressing the generalization relationship, the hollow arrow end points to the upper-level element, that is, from the Block element of the instance to the Block element representing the component. Refer to Figure 6 , which is a schematic diagram of the relationship between components and instances; as shown by Figure 6 , it can be seen that for component BD, there are two instances, BD1 and BD2, available for selection, and for component BF, there are four instances, BF1, BF2, BF3, and BF4, available for selection. The relationships between the remaining components and instances are similar and will not be elaborated here.

[0097] To more clearly distinguish the relationships between design requirements, functions, components, and instances, in the subsequent embodiments of this application, the activity elements corresponding to functions in the full-scale model are referred to as function elements, the Block elements corresponding to components in the full-scale model are referred to as component elements, and the Block elements corresponding to instances in the full-scale model are referred to as instance elements.

[0098] S05: Express the connection relationships between instance elements;

[0099] S06: Express the mutual exclusion relationships between elements.

[0100] For step S05: The product instance is formed by aggregating all instances, and each instance is a part of the product instance. Using domain knowledge as the input information to the LLM model, all the connection relationships between instances output by the LLM model are obtained and expressed in the SysML model. In the SysML model, a Block element is created to represent the product instance, and a directed composition relationship is created between the Block representing the product instance and the Blocks representing the instances. An Internal Block Diagram (IBD) based on the SysML language is created in the Block representing the product instance to display the instances in the form of component attributes, and the type of the component attribute is each instance element. The Connector element can be used to connect two component attributes to create the connection relationship between two instance elements, indicating that there is at least one relationship of material, information, or energy transfer between the components corresponding to these two instance elements and between these two instances. For exampleFigure 7 As shown, it is a schematic diagram of the connection relationship between example elements.

[0101] For step S06: In the system solution of the product, there may be incompatible elements. Appearing together in the same system solution will cause the solution to be unimplementable, or it can be foreseen according to domain knowledge that it will inevitably lead to the failure of the development result of the solution. In the SysML model, the Trace relationship is used to connect two incompatible elements to represent the mutual exclusion relationship between the elements. In the BDD diagram, the mutual exclusion relationship between functions, components, and instances can be shown, as Figure 8 shown. In the IBD diagram, the trace relationship connection line between the part property (Part Property) and the connector can be shown, which actually represents the mutual exclusion relationship between the instance and the connection relationship; Figure 9 It is a schematic diagram of the mutual exclusion relationship between the part property and the connector. From Figure 9 it can be known that: when the part property BB1 exists, the connector connecting the part properties BA1 and BC1 is deleted in the system architecture solution due to the mutual exclusion relationship with the part property BB1, and BA1 and BC1 are connected through BB1; when the part property BB1 does not exist, the connector connecting the part properties BA1 and BC1 will not be deleted, and the part property BA1 and the part property BC1 are connected through this connector.

[0102] Through the above steps S01 - S06, the construction of the full - scale model applied in this application can be completed; as Figure 10 shown, it is a partial schematic diagram of the constructed full - scale model. The full - scale model can be constructed immediately or pre - constructed. In the embodiments of this application, no specific limitation is made on this.

[0103] In step 130 above, two achievable ways of constructing each initial solution are described. The first way is that in the process from step 110 to step 120, each solution template is continuously copied and filled, and finally each initial solution is obtained. The following content elaborates on the first way in detail.

[0104] Specifically, in step 110, first construct a system architecture solution set: used to store each initial solution of the system generated in subsequent steps. Then create a solution template for the system architecture in the system architecture solution set. When the target function is matched from the full - scale model based on the design requirements in the subsequent steps, the matched target function is stored in the solution template. The number of design requirements in the requirements list has nothing to do with the number of created solution templates. That is to say, initially, only one solution template is constructed based on the requirements list.

[0105] In one example, if there is one requirement RA in the design list, a solution template is constructed in the system solution set, and the design requirement RA in the requirement list is filled into the solution template as an element. The final obtained system solution set is [RA].

[0106] Further, the design requirements are input into the full model in the order of the design requirements in the system architecture solution. The functional elements associated with the design requirements are matched in the full model to obtain the function set corresponding to each design requirement. If the function set corresponding to a design requirement includes only one target function, the functional element corresponding to the target function is written into the solution template. If there are two or more target functions in the function set corresponding to the design requirement, multiple solution templates need to be copied and generated in the system solution set. The number of copies is determined based on the number of target functions in the function set. For example, if the number of target functions in the function set is N, the number of copies required is N - 1. The solution template is copied N - 1 times in the system solution set, and finally, the number of solution templates in the system solution set is N. The N target functions in the function set are matched one by one with the N solution templates, so that one target function corresponds to one solution template, and the target functions corresponding to any two solution templates are not repeated. Further, for each target function, the functional element corresponding to the target function is written into the corresponding solution template.

[0107] In one example, with the design requirement RA as the input, the target functions OA and OB are matched from the full model. Then, the solution template is copied once in the system solution set, and the functional elements corresponding to the two target functions OA and OB are filled into the two solution templates respectively. The final obtained system solution set is [RA, OA; RA, OB], which contains two system architecture solutions. The information expressing different system solutions is separated by a semicolon ";".

[0108] Further, the functional elements in each solution template are functionally decomposed. In one possible implementation, the specific process of functional decomposition includes: retrieving each target function in the full model, and classifying each target function into a first target function and a second target function according to the retrieval result. The first target function has decomposable subordinate functions in the full model, and the second target function has no decomposable subordinate functions in the full model. Therefore, it can also be deduced that the subordinate functions are also second target functions. The full model also includes the hierarchical relationship between functions. Each second target function is retrieved in the full model to obtain the instance set corresponding to each second target function. In the function set corresponding to the first target function, the subordinate functions corresponding to the first target function are written into the function set where the first target function is located to obtain the updated function set.

[0109] In another possible implementation, the process of functional decomposition may further include: using the functional elements in each solution template as the input information of the full-scale model; for each functional element, determining whether there is a refinement relationship between this functional element and other functional elements in the full-scale model, that is, determining whether there are subordinate sub-functional elements for this functional element. For each solution template, if there are subordinate sub-functional elements for the corresponding functional elements in the solution template, then fill each sub-functional element into the solution template. For each solution template, confirm whether there are mutually exclusive elements in the solution template. If there are mutually exclusive elements, then delete this solution template.

[0110] In an example, the functional element OA has no subordinate sub-functional elements, while the functional element OB has subordinate sub-functional elements DA and DB. Fill the two sub-functional elements DA and DB into the solution template where the functional element OB is located. The finally obtained system solution set is [RA, OA; RA, OB, DA, DB], including 2 system architecture solutions.

[0111] In a possible case, if a function can match multiple design requirements, that is, multiple design requirements match the same target function, then only one target function needs to be retained. Therefore, for each solution template, after writing new functional elements into the solution template, it is necessary to perform duplicate checking on the solution template. For duplicate functional elements, only one item is retained. Further, perform a mutual exclusion relationship check on each solution template after writing new elements, and delete the solution templates with mutual exclusion relationships from the system solution set. In an instance, both cargo transportation and passenger transportation are design requirements, and the target functions matched by these two design requirements both include generating thrust.

[0112] Specifically, the mutual exclusion relationship includes a first mutual exclusion relationship and a second mutual exclusion relationship; among them, the first mutual exclusion relationship is the mutual exclusion relationship between the functional elements represented by the non-functional requirements (relationship requirements) in the requirement list; the second mutual exclusion relationship is the mutual exclusion relationship between the functional elements represented in the full-scale model.

[0113] Further, in one of the embodiments, in step 120, the process of matching to obtain the instance set corresponding to each target function is as Figure 11 shown, and specifically may include step 121 and step 122, where:

[0114] Step 121: Match each function set in the full-scale model to obtain a component set corresponding to each target function, and the component set includes at least one target component.

[0115] Specifically, the constructed full-scale model also includes the correspondence between components and functions, and the correspondence between instances and components.

[0116] For each solution template obtained in step 110, use the sub - function elements in the solution template and the function elements without subordinate sub - function elements as the input information of the full - scale model. Match the component elements associated with each sub - function element and the component elements associated with each function element in the solution full - scale model. Then fill the matched component elements into the solution template. If the number of component elements associated with a function element is not unique, multiple copies of the solution template need to be made in the system solution set. The number of copies is determined based on the number of component elements associated with the function element. Suppose the number of component elements associated with a function element is M, and M > 2; then the number of copies is M - 1. That is to say, after replication, the number of solution templates obtained in the system solution set is M. Further, for each function element, fill the M component elements matched by this function element into M solution templates respectively, so that the component elements in each solution template are not repeated.

[0117] In a possible case, if a component element can be matched by multiple function elements, that is, the same component element is matched by multiple function elements, only one component element needs to be retained. Therefore, for each solution template, after writing the new component element into the solution template, it is necessary to check for duplicate component elements in the solution template. For duplicate component elements, only one item is retained. Further, check for mutual exclusion relationships for each solution template after writing the new elements, and delete the solution templates with mutual exclusion relationships from the system solution set.

[0118] Specifically, the mutual exclusion relationships include the first mutual exclusion relationship and the second mutual exclusion relationship. Among them, the first mutual exclusion relationship is the mutual exclusion relationship between component elements characterized by non - functional requirements in the requirements list, and the mutual exclusion relationship between component elements and function elements. The second mutual exclusion relationship is the mutual exclusion relationship between function elements characterized in the full - scale model, and the mutual exclusion relationship between component elements and function elements.

[0119] In an example, using functions OA, DA, and DB as the input information of the full - scale model for component matching: for function DA, component BC is matched, so BC is filled into the solution template containing DA. Similarly, component BD is matched by function DB. For function OA, two components BA and BB can be matched. Therefore, 1 solution template containing function OA needs to be copied in the system architecture solution set, and the component elements corresponding to BA and BB are filled into these two solution templates respectively. The finally obtained system solution set is [RA, OB, DA, DB, BC, BD; RA, OA, BA; RA, OA, BB], which contains 3 solution templates.

[0120] Step 122: Match each component set in the full model to obtain an instance set corresponding to each target component.

[0121] For each solution template obtained in Step 121, use the component elements in the solution template as the input information for the full model. Match the instance elements associated with each component element in the full model, and fill the matched instance elements into the system solution. If the instance elements associated with a component element are not unique, it is necessary to copy the solution templates containing this component element multiple times in the system solution set. Suppose there are Q instance elements associated with a component element and Q is greater than or equal to 2, then the number of copies is Q - 1. After copying, there are Q solution templates containing this component element in total. Further, correspond the Q instance elements to the Q solution templates one by one, and fill one instance element into each solution template, and the instance elements filled in each solution template are not repeated.

[0122] In a possible case, if an instance element can match multiple component elements, that is, the same instance element is matched by multiple component elements, only one instance element needs to be retained. Therefore, for each solution template, after writing a new instance element into the solution template, it is necessary to check for duplicate instance elements in the solution template, and only retain one of the duplicate instance elements. Further, check for mutual exclusion relationships in each solution template after writing new elements, and delete the solution templates with mutual exclusion relationships from the system solution set.

[0123] Specifically, the mutual exclusion relationships include the first mutual exclusion relationship and the second mutual exclusion relationship. Among them, the first mutual exclusion relationship is the mutual exclusion relationship between the instance elements characterized by the non-functional requirements in the requirements list, as well as the mutual exclusion relationship between the component element and the instance element. The second mutual exclusion relationship is the mutual exclusion relationship between the instance elements at the same level characterized in the full model, as well as the mutual exclusion relationships among the instance elements, component elements, and functional elements across different levels.

[0124] In one example, component elements BA, BB, BC, and BD are used as the input information of the full-scale model for instance element matching: For component element BA, two instance elements BA1 and BA2 are retrieved. Therefore, one scheme template containing component element BA needs to be copied in the system architecture scheme set, and instance elements BA1 and BA2 are filled into these two scheme templates containing component element BA respectively; the same operations as instance elements BA1 and BA2 are performed on instance elements BB1 and BB2 retrieved by component element BB. For component elements BC and BD, since these two component elements exist in the same scheme template, and there are 3 instance elements associated with component element BC and 2 instance elements associated with component element BD, 5 copies of the scheme template containing component elements BC and BD need to be copied, and 6 instance combinations formed by the instance elements corresponding to component elements BC and BD are filled into these 6 scheme templates respectively.

[0125] The finally obtained system scheme set is [RA, OA, BA, BA1; RA, OA, BA, BA2; RA, OA, BB, BB1; RA, OA, BB, BB2; RA, OB, DA, DB, BC, BD, BC1, BD1; RA, OB, DA, DB, BC, BD, BC1, BD2; RA, OB, DA, DB, BC, BD, BC2, BD1; RA, OB, DA, DB, BC, BD, BC2, BD2; RA, OB, DA, DB, BC, BD, BC3, BD1; RA, OB, DA, DB, BC, BD, BC3, BD2]; this set contains a total of 10 scheme templates, and each of these 10 scheme templates serves as an initial scheme.

[0126] Furthermore, for each initial scheme, the initial scheme is retrieved in the full-scale model to match the corresponding connectors for the initial scheme; that is, for each initial scheme, the instance elements in the initial scheme are used as the input information of the full-scale model, and the connectors associated with each instance element are matched in the full-scale model. Among them, the connector is used to connect the elements corresponding to the instances with a connection relationship, and the connection relationship represents at least one interaction relationship among matter, information, and energy between the instances.

[0127] Furthermore, for each initial scheme, duplicate checking and mutual exclusion relationship checking are performed on each scheme to confirm whether there are mutually exclusive elements in each initial scheme; if there is a mutual exclusion relationship in the initial scheme, then the scheme is deleted. Among them, the checking of the mutual exclusion relationship specifically includes: based on the first mutual exclusion relationship represented by the relationship requirements, each initial scheme is retrieved to obtain the first retrieval result; based on the second mutual exclusion relationship included in the full-scale model, each initial scheme is retrieved to obtain the second retrieval result; based on the first retrieval result and / or the second retrieval result, the target scheme is determined from each initial scheme.

[0128] That is to say, for an initial solution, as long as any one of the first mutual exclusion relationship or the second mutual exclusion relationship exists among the elements in the solution, the solution meets the deletion condition. An initial solution in which there is no first mutual exclusion relationship and no second mutual exclusion relationship among the elements is determined as the final target solution, that is, the actually available solution. Further, for each target solution, the elements that do not exist in the target solution are deleted in the full-scale model to obtain the model of the target architecture corresponding to the target solution.

[0129] It should be understood that although the steps in the flowcharts involved in the above embodiments are sequentially displayed according to the indication of the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same moment, but can be executed at different moments. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0130] Based on the same inventive concept, an embodiment of the present application also provides a requirements- and function-based architecture design device for implementing the requirements- and function-based architecture design method described above. The solution provided by this device for solving problems is similar to the solution described in the above method. Therefore, the specific limitations in one or more embodiments of the requirements- and function-based architecture design device provided below can refer to the limitations on the requirements- and function-based architecture design method in the above text, and will not be repeated here.

[0131] In an exemplary embodiment, as Figure 12 shown, a requirements- and function-based architecture design device is provided. The device includes a first matching module 1201, a second matching module 1202, an initial solution construction module 1203, a target solution screening module 1204, and a target architecture construction module 1205, where:

[0132] The first matching module 1201 is used to create a solution template for the architecture solution based on the requirements list, and match the requirements list in the full-scale model to obtain a function set corresponding to each design requirement in the requirements list; the function set includes at least one target function, and the full-scale model includes the corresponding relationship between requirements and functions;

[0133] The second matching module 1202 is configured to match each function set in the full model to obtain an instance set corresponding to each target function, where the instance set includes at least one target instance, and the full model further includes the corresponding relationship between instances and functions;

[0134] The initial solution construction module 1203 is configured to construct a plurality of initial solutions based on the solution template. The initial solution includes a function element of a target function corresponding to each design requirement, and an instance element of a target instance corresponding to each target function;

[0135] The target solution screening module 1204 is configured to retrieve each initial solution based on the mutual exclusion relationship and determine a target solution from each initial solution according to the retrieval result. The target solution is an initial solution in which there is no mutual exclusion relationship between elements; the mutual exclusion relationship between elements is also included in the full model;

[0136] The target architecture construction module 1205 is configured to construct a corresponding target architecture based on each target solution, and each target architecture is an architecture solution corresponding to the requirements list.

[0137] In one embodiment, the second matching module 1202 is specifically configured to:

[0138] Match each function set in the full model to obtain a component set corresponding to each target function, where the component set includes at least one target component;

[0139] Match each component set in the full model to obtain an instance set corresponding to each target component. The full model further includes the corresponding relationship between components and functions, and the corresponding relationship between instances and components.

[0140] In one embodiment, the second matching module 1202 is specifically configured to:

[0141] Retrieve each target function in the full model and classify each target function into a first target function and a second target function according to the retrieval result; the first target function is a lower-level function that can be split in the full model, and the second target function is a lower-level function that cannot be split in the full model. The lower-level function is the second target function, and the full model further includes the upper and lower level relationships between functions;

[0142] Retrieve each second target function in the full model to obtain an instance set corresponding to each second target function;

[0143] In the function set corresponding to the first target function, replace the first target function with each lower-level function corresponding to the first target function to obtain an updated function set.

[0144] In one embodiment, the architecture design device based on requirements and functions further includes a connector retrieval module, which is specifically configured to:

[0145] For each initial solution, retrieve the initial solution in the full-scale model and match corresponding connectors to the initial solution. The connectors are used to connect the elements corresponding to the instances with a connection relationship, and the connection relationship represents at least one interaction relationship among matter, information, and energy between the instances.

[0146] In one embodiment, the initial solution determination module 1203 is specifically configured to:

[0147] Retrieve each initial solution based on the first mutual exclusion relationship represented by the relationship requirements to obtain a first retrieval result;

[0148] Retrieve each initial solution based on the second mutual exclusion relationship included in the full-scale model to obtain a second retrieval result;

[0149] Determine a target solution from each initial solution based on the first retrieval result and / or the second retrieval result.

[0150] In one embodiment, the target architecture construction module 1205 is specifically configured to:

[0151] For each target solution, delete the elements that do not exist in the target solution in the full-scale model to obtain the target architecture corresponding to the target solution.

[0152] Each module in the above architecture design device based on requirements and functions can be implemented in whole or in part by software, hardware, and their combination. The above modules can be embedded in the processor in the computer device in hardware form or be independent of it, or be stored in the memory in the computer device in software form so that the processor can call and execute the operations corresponding to the above respective modules.

[0153] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as Figure 13As shown in the figure. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface, the display unit, and the input device are connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements an architecture design method based on requirements and functions. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, a trackball, or a touchpad provided on the housing of the computer device, or an external keyboard, touchpad, or mouse, etc.

[0154] Those skilled in the art can understand that Figure 13 the structure shown in the figure is only a block diagram of some structures related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have a different component layout.

[0155] In an exemplary embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, any step in the above-mentioned embodiment of the architecture design method based on requirements and functions is implemented.

[0156] In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by the processor, any step in the above-mentioned embodiment of the architecture design method based on requirements and functions is implemented.

[0157] In an embodiment, a computer program product is provided, including a computer program. When the computer program is executed by the processor, any step in the above-mentioned embodiment of the architecture design method based on requirements and functions is implemented.

[0158] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant regulations.

[0159] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memories. Non-volatile memories can include read-only memory (ROM), magnetic tapes, floppy disks, flash memories, optical memories, high-density embedded non-volatile memories, resistive random access memories (ReRAM), magnetoresistive random access memories (MRAM), ferroelectric random access memories (FRAM), phase change memories (PCM), graphene memories, etc. Volatile memories can include random access memory (RAM) or external cache memories, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, etc., without limitation.

[0160] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0161] The above embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several variations and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A method for architectural design based on requirements and functions, characterized in that: The method comprises: A solution template of the system architecture is created based on the requirement list, and the requirement list is matched in the full model to obtain a function set corresponding to each design requirement in the requirement list; the function set includes at least one target function, and the full model includes a correspondence between the requirement and the function; Matching each of the function sets in the full model to obtain an instance set corresponding to each of the target functions, the instance set including at least one target instance, and the full model also including a correspondence between the instance and the function; A plurality of initial solutions are constructed based on the solution template, wherein the initial solutions include a functional element of a target function corresponding to each design requirement and an instance element of a target instance corresponding to each target function; Retrieving each of the initial solutions based on the mutually exclusive relationship, and determining a target solution from each of the initial solutions according to the retrieval results, wherein the target solution is the initial solution in which no mutually exclusive relationship exists between elements; the full model also includes the mutually exclusive relationship between the elements; A corresponding target architecture is constructed based on each of the target solutions, and each of the target architectures is an architecture solution corresponding to the requirement list.

2. The method according to claim 1, characterized in that The matching of each function set in the full model to obtain a set of instances corresponding to each target function includes: Matching each of the function sets in the full model to obtain a component set corresponding to each of the target functions, wherein the component set includes at least one target component; Each of the component sets is matched in the full model to obtain a set of instances corresponding to each of the target components. The full model also includes a correspondence between components and functions, and a correspondence between instances and components.

3. The method according to claim 2, characterized in that The matching of each function set in the full model to obtain a set of instances corresponding to each target function includes: Retrieve each of the target functions in the full model, and classify each of the target functions into a first target function and a second target function according to the retrieval result; the first target function is a subordinate function that can be separated in the full model, the second target function is a subordinate function that cannot be separated in the full model, the subordinate function is the second target function, and the full model also includes a superior-female relationship between functions; Retrieving each of the second target functions in the full model to obtain a set of instances corresponding to each of the second target functions; In the function set corresponding to the first target function, the first target function is replaced with each of the subordinate functions corresponding to the first target function to obtain the updated function set.

4. The method according to claim 2 or 3, characterized in that: The method further comprises: For each of the initial solutions, the initial solution is retrieved in the full model, and the corresponding connectors are matched for the initial solution. The connectors are used to connect elements corresponding to instances with connection relationships, and the connection relationship represents the existence of at least one interactive relationship among matter, information and energy between the instances.

5. The method according to claim 4, characterized in that The requirement list also includes relationship requirements. The step of retrieving each of the initial solutions based on the mutually exclusive relationship and determining the target solution from each of the initial solutions according to the retrieval results includes: Based on the first mutually exclusive relationship represented by the relationship requirement, searching each of the initial solutions to obtain a first search result; Based on the second mutually exclusive relationship included in the full model, searching each of the initial solutions to obtain a second search result; Based on the first search result and / or the second search result, a target solution is determined from the initial solutions.

6. The method according to claim 5, characterized in that The corresponding target architecture is constructed based on each of the target solutions, including: For each of the target solutions, elements that do not exist in the target solution are deleted from the full model to obtain a target architecture corresponding to the target solution.

7. A device for designing an architecture based on requirements and functions, characterized in that: The device comprises a first matching module, a second matching module, an initial solution building module, a target solution screening module and a target architecture building module, wherein: A first matching module is used to create a solution template of the system architecture based on the requirement list, and match the requirement list in the full model to obtain a function set corresponding to each design requirement in the requirement list; the function set includes at least one target function, and the full model includes a correspondence between the requirement and the function; A second matching module is used to match each of the function sets in the full model to obtain an instance set corresponding to each of the target functions, wherein the instance set includes at least one target instance, and the full model also includes a correspondence between the instance and the function; An initial solution construction module, used to construct multiple initial solutions based on the solution template, wherein the initial solutions include a functional element of a target function corresponding to each design requirement and an instance element of a target instance corresponding to each target function; A target solution screening module, used for searching each of the initial solutions based on a mutually exclusive relationship, and determining a target solution from each of the initial solutions according to the search results, wherein the target solution is the initial solution in which no mutually exclusive relationship exists between elements; the full model also includes mutually exclusive relationships between elements; The target architecture construction module is used to construct a corresponding target architecture based on each of the target solutions, and each of the target architectures is an architecture solution corresponding to the requirement list.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images