A method for generating a functional architecture based on a SysML model
By constructing the functional architecture of spacecraft systems using SysML models, the problems of unclear description of dynamic tracking and interaction relationships between functions were solved, achieving efficient functional architecture generation, reducing omissions, and improving the design efficiency of spacecraft systems.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-09
- Publication Date
- 2026-03-03
AI Technical Summary
Existing technologies for generating spacecraft system functional architecture suffer from problems such as the inability to dynamically track functions and unclear descriptions of interaction relationships, resulting in low generation efficiency and a high risk of omissions.
The SysML model is used to construct task use cases. The functional structure is constructed through the object flow of use cases and use case activities. Functional groups are divided according to the preset cohesion criteria to generate the functional architecture of the internal module diagram of SysML, so as to realize the intuitive and traceable generation of the functional architecture.
It improves the efficiency of system functional architecture generation, reduces omissions in functional decomposition, and provides an effective method and approach for the overall design of spacecraft systems.
Smart Images
Figure CN116304197B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to a functional architecture generation method based on SysML models, belonging to the field of model-based systems engineering (MBSE) technology. Background Technology
[0002] Spacecraft systems bear diverse and complex mission requirements, face multiple operational scenarios, and perform various roles and functions. In model-based spacecraft development, this manifests as numerous use cases, a large number and variety of corresponding activities, and their interrelationships. Furthermore, from a functional implementation perspective, the functions of current spacecraft systems are often carried out by multiple physical components, and a single physical component often performs multiple functions. Against this backdrop, how to enable a single spacecraft system to support so many diverse and complex mission activities requires a system architecture that is detached from the perspective of specific technical implementation and takes a functional approach—a functional architecture. This functional architecture supports the system in supporting complex mission requirements across multiple scenarios through system functional logic and mode switching.
[0003] Traditionally, functional architecture is primarily achieved through functional decomposition. This involves breaking down the top-level functions of a spacecraft system into sub-functions according to a specific method, and then assigning the decomposed functional requirements and related performance requirements to appropriate sub-functions. This multi-level decomposition continues until the lowest-level functional elements can be supported by specific physical solutions. However, this approach remains based on static, document-driven descriptions, which suffers from problems such as the inability to dynamically track inter-function relationships and unclear descriptions of interaction relationships. Summary of the Invention
[0004] The technical problem solved by this invention is to overcome the shortcomings of existing technologies and provide a functional architecture generation method based on SysML models, generating functional architecture from task use cases. Furthermore, based on the task use cases constructed in SysML, a functional structure is constructed according to the use cases and the object flow within the use case activities. The use case activities in the functional structure are divided into corresponding functional groups according to a preset cohesion criterion. The use case activities assigned to the corresponding functional groups are used as functional elements. Combined with the functional structure, a functional architecture in the form of a SysML internal module diagram is generated, thereby achieving a direct and intuitive way to obtain the functional architecture from use cases. This invention, relying on a model-based method, can improve the efficiency of system functional architecture generation, reduce omissions in functional decomposition, and provide an effective method and approach for the overall design of spacecraft systems.
[0005] The technical solution of this invention is: a method for generating functional architecture based on a SysML model, comprising:
[0006] Build use cases and use case activities based on requirements;
[0007] Construct the functional structure based on the use cases and the object flow in the use case activities;
[0008] Divide the functional structure into functional groups and group the use case activities in the functional structure into the corresponding functional groups according to the preset cohesion criteria;
[0009] Use case activities assigned to the corresponding functional groups are used as functional elements, and the functional architecture is generated by combining them with the functional structure.
[0010] Furthermore, the use cases include system-level use cases and subsystem-level use cases; the system-level use cases are the use cases of the spacecraft system corresponding to the functional architecture, and the subsystem-level use cases are the use cases of each subsystem of the spacecraft system; the object flow in the use case activities includes information, signals, materials, forces, and energy between use case activities.
[0011] Furthermore, the functional structure includes a functional structure tree, which displays the tree-like relationship of function calls between use case activities; the parent node calls the child node function, and the root node of the functional structure tree is a system-level use case activity that has a one-to-one relationship with the system-level use case.
[0012] Furthermore, all nodes in the functional structure tree, except for the leaf nodes, are grouped into a system group to ensure that the system functions in the functional structure tree are assigned to a group.
[0013] Furthermore, the method for dividing functional groups includes grouping use cases that are directly related to the participants, have calling relationships between functions, involve common data or objects in the functional relationship, can be abstracted into an abstract use case, or are referenced or called by multiple other use cases.
[0014] Furthermore, for each functional group, a functional component with the same name is created. Through this functional component, a tracing relationship is applied to link it to the functional group of origin. Through the combination relationship of all functional components, all functional components other than the spacecraft system become part of the spacecraft system.
[0015] Furthermore, the generation functional architecture includes:
[0016] Functions within the same functional group are connected according to their functional logic: they are connected through ports and flow attributes in the SysML internal block diagram to form a functional architecture; the connection relationship between ports is determined based on the object flow defined in the use case activity model.
[0017] Furthermore, use case activities include functional areas representing the interests of system users and functional areas connecting system users to relevant systems for input / output interaction.
[0018] A computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the functional architecture generation method based on a SysML model.
[0019] A functional architecture generation device based on a SysML model includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the functional architecture generation method based on a SysML model.
[0020] The advantages of this invention compared to the prior art are:
[0021] This invention aims to provide a functional architecture generation method based on SysML models, generating functional architecture from task use cases. Based on task use cases, activity diagrams are used to refine the use cases. After decomposing the system into functional components through functional decomposition, the interaction relationships between functional components are defined according to how the use case activities are implemented. This allows for the direct and intuitive generation of the functional architecture from the use cases. This model-based approach improves the efficiency of system functional architecture generation, reduces omissions in functional decomposition, and provides an effective method and approach for the overall design of spacecraft systems. Attached Figure Description
[0022] Figure 1 This is a schematic diagram of the method flow of the present invention;
[0023] Figures 2-4 This is a schematic diagram illustrating an embodiment of the present invention. Detailed Implementation
[0024] To better understand the above technical solutions, the technical solutions of this application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of this application and the specific features in the embodiments are detailed descriptions of the technical solutions of this application, rather than limitations on the technical solutions of this application. In the absence of conflict, the embodiments of this application and the technical features in the embodiments can be combined with each other.
[0025] The following description, in conjunction with the accompanying drawings, provides a more detailed explanation of a functional architecture generation method based on a SysML model provided in this application. Specific implementation methods may include (e.g.) Figures 1-4 As shown):
[0026] Build use cases and use case activities based on requirements;
[0027] Construct the functional structure based on the use cases and the object flow in the use case activities;
[0028] Divide the functional structure into functional groups and group the use case activities in the functional structure into the corresponding functional groups according to the preset cohesion criteria;
[0029] Use case activities assigned to the corresponding functional groups are used as functional elements, and the functional architecture is generated by combining them with the functional structure.
[0030] Furthermore, the use cases include system-level use cases and subsystem-level use cases; the system-level use cases are the use cases of the spacecraft system corresponding to the functional architecture, and the subsystem-level use cases are the use cases of each subsystem of the spacecraft system; the object flow in the use case activities includes information, signals, materials, forces, and energy between use case activities.
[0031] Define the relevant concepts in the functional architecture generation process, such as:
[0032] Function refers to the input and output relationships of information, signals, matter, forces, and energy elements within the system.
[0033] Functional architecture specifies and precisely defines the capabilities and services the system will provide and the tasks the system will perform, and describes the messages and data transmitted between functions. Functional architecture decomposes the system into functional components and defines how these components interact to achieve system requirements.
[0034] A functional component is an abstract representation of a physical component; it performs the functions of the system without imposing constraints on its technical implementation.
[0035] Functional structure is a tree structure obtained by decomposing functions and functional components layer by layer.
[0036] A use case is a description of how a system achieves a specific goal by providing a series of services to a user or external system.
[0037] A use case activity is a description of one or more related behaviors that occur when a use case is instantiated.
[0038] A method for generating a functional architecture based on a SysML model mainly includes the following steps:
[0039] (1) Construct use cases and use case activities based on requirements; Construct use cases around requirements, and describe requirements in detail in the form of use cases. Through detailed description of use cases, the system requirements, the participants of requirements, the use case activities to implement requirements, and the external environment and system involved in use case activities are clearly defined.
[0040] (2) Refine use case activities and construct a functional structure; refine use cases into use case activities, and implement the functional points expressed by a series of refined use case activities. Focus on the analysis of object flow in use case activities, including information, signals, materials, forces, and energy between use case activities. Construct the above activities into a functional structure and display the tree structure relationship between activities. The tree structure displays the hierarchical structure of function calls: the parent node calls the child node function, and the root of the activity tree is the activity with a one-to-one relationship with the system use case, with the same name as the use case. The root node of the function tree structure is the system-level use case activity with a one-to-one relationship with the system-level use case.
[0041] (3) Identify functional groups; based on the functional structure tree, group the activities in the tree structure into functional groups according to the cohesion criterion. The general principles for dividing functional groups are given below.
[0042] Functional group division principles:
[0043] 1. Functions directly related to participants: Functions directly related to participants are part of the system's input / output logic. Usually, these functions are not very related to the system's internal functions (such as how the system processes an input into an output) and should be grouped together.
[0044] 2. Functions that have calling relationships: Function calls imply cohesion, with similar functional themes, forming a functional cluster structure, which can constitute possible functional groups.
[0045] ●3. Functional relationships involving common data or objects: If multiple functions involve processing the same data, it indicates that they are in related domains and constitute a possible functional group.
[0046] 4. Multiple use cases can be abstracted into a single abstract use case: This demonstrates the cohesion of functional use cases, meaning their related activities can be grouped into a functional group.
[0047] 5. If the same use case is referenced or called by multiple other use cases: This indicates the cohesion of the use case, and related activities should be grouped into a functional group.
[0048] Group all nodes in the functional structure tree except the leaf nodes into a system group to ensure that system functions in the functional structure tree are assigned to a group.
[0049] In one possible implementation, for each functional group, a functional component with the same name is created, and a tracing relationship is applied through this functional component to link it to the functional group of origin. Through the combination relationship of all functional components, all functional components other than the spacecraft system become part of the spacecraft system.
[0050] (4) Construct the functional architecture; determine the system functional architecture by combining functional groups, functional components, and the connections and interactions between functional components. Functions within the same functional group are connected according to their functional logic relationships. Based on the functional grouping principles described in step three, connections are made in the internal block diagram using port and flow attributes. The connection relationships between ports are based on the object flow of the activity model. The internal block diagram clearly visualizes and describes the matter, and displays the objects flowing between different functions.
[0051] Furthermore, the generation of the functional architecture includes: connecting functions within the same functional group according to their functional logical relationships; connecting them through the port and flow attributes of the SysML internal block diagram to form the functional architecture; the connection relationship between ports is determined based on the object flow defined in the use case activity model.
[0052] Use case activities include functional areas that represent the interests of system users and functional areas that connect system users to relevant systems for input and output interaction.
[0053] The specific implementation methods of the solutions provided in the embodiments of this application may include (such as...) Figures 1-4 As shown):
[0054] Step 1: Build use cases and use case activities based on requirements.
[0055] Taking a remote sensing satellite payload system as an example, the remote sensing payload has three requirements: high-definition imaging, image pixel adjustment, and online recharging. Based on these requirements, use cases are constructed to describe them in detail, as shown in the figure below.
[0056] The functional requirements were refined using three use cases with the same name, clarifying the system boundaries. The participants in these three use cases are ground station observers. The observers use the remote sensing payload system to perform activities such as image observation, pixel adjustment, and online power charging. Among them, image observation is related to the environment outside the system boundaries, and online power charging is related to the external system—the spaceborne energy source.
[0057] The second step is to refine use case activities and construct the functional structure.
[0058] Using a functional structure, use cases are broken down into use case activities. Each use case is implemented through a series of detailed use case activities, focusing on the analysis of object flows within these activities, including information, signals, materials, forces, and energy flows between them. This structure displays a tree-like relationship between activities. The tree structure shows the hierarchical structure of function calls: parent nodes call child nodes, and the root of the activity tree contains activities with a one-to-one relationship to system use cases, sharing the same name as the use cases.
[0059] Step 3: Identify Function Groups
[0060] Use case activities are intuitively important elements from a system behavior perspective. Functional architecture is a structural view of the system and does not include its dynamic behavior. Therefore, control flow between use case activities does not need to be considered in functional architecture analysis, while object flow is intuitively important. Object flow describes the input-output relationships between activities.
[0061] First, according to principle 1, the functional architecture is divided into two parts: system and input / output components. Activities directly related to actors and the external environment in the use case are assigned to the system, while other input / output related activities are uniformly assigned to the input / output components, as shown in Table 1 below.
[0062] Table 1 Initial Function Allocation Table
[0063] Functional architecture components / features Input / output components system Observe high-resolution remote sensing images distribute Acquire input signal distribute High-definition imaging Generate image distribute Adjust pixels distribute Perform pixel control distribute Calculate gain Perform gain control Generate pixel-adjusted images distribute Energy supply distribute Obtaining energy distribute Energy transmission
[0064] Next, it was noted that some use case activities had not been assigned. Among them, the activities of applying high-definition imaging and performing gain control share a common object, "image signal." According to principle 3, these activities are grouped into a functional group and assigned to high-definition processing. Corresponding functional components were then added to the other unassigned activities. This completed the functional group identification, as shown in Table 2 below.
[0065] Table 2 Functional Group Identification Table
[0066]
[0067] Step 4: Build the functional architecture
[0068] Functional elements, combined with functional structures, constitute the system's functional architecture. Functional elements within the same functional group are connected according to their functional logic, and in accordance with the functional grouping principles described in step three, these connections are made in the internal block diagram using ports and flow attributes. The connection relationships between ports are based on the object flow of the activity model. The internal block diagram clearly visualizes and describes the matter, and displays the objects flowing between different functional elements.
[0069] As shown in the figure below, the functional grouping forms a functional logic architecture. According to the grouping principle, the generated image and the generated pixel-adjusted image are merged through the common object of the image, which is the image output component; gain control and high-definition imaging have the common object of the image signal and need to be connected; the calculated gain and the executed gain control share the gain control value and are merged to form the gain processing unit, which receives the input pixel setting value; the energy acquisition and energy transmission have the common object of the onboard battery unit and are merged, and an additional energy management unit is set up to receive and distribute the energy.
[0070] Based on the functional group division, the final system functional architecture is determined, and all input and output modules are opened and specified. According to principle 3, the generated image and the image with pixel adjustments share a common object image, therefore they are uniformly assigned to the image output module. This completes the functional architecture analysis, as shown in Table 3 below.
[0071] Table 3 Functional Architecture Table
[0072]
[0073]
[0074] The final internal block diagram of the system functional architecture is as follows: Figure 4 As shown, system modules serve as interfaces for interaction between the system and users, and between the system and the external environment, thereby constructing a functional architecture oriented towards system requirements and use cases.
[0075] This application provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to perform... Figure 1 The method described.
[0076] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.
[0077] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0078] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0079] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0080] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.
[0081] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.
[0082] The contents not described in detail in this specification are common knowledge to those skilled in the art.
Claims
1. A method for generating a functional architecture based on a SysML model, characterized in that, The application relates to a method for constructing a space vehicle system, and a computer program product and a processor. The method comprises the following steps: constructing a use case and a use case activity according to requirements; constructing a function structure according to objects in the use case and the use case activity; dividing the function groups, and grouping the use case activities in the function structure into corresponding function groups according to preset cohesion standards; generating a function architecture by combining the function structure with the use case activities grouped into the corresponding function groups; grouping all nodes of the function structure tree except leaf nodes into a system group, so as to ensure that system functions in the function structure tree are allocated to one group; the method for dividing the function groups comprises the following steps: grouping the use cases which have a direct relationship with functions and participants, a calling relationship between functions, a function relationship involving public data or objects, a plurality of use cases which can be abstracted into an abstract use case, and a use case which is referenced or called by a plurality of other use cases; for each function group, a function component with the same name is created, the function component is applied to link to the function group from which the function component originates, and all function components are combined to form a part of a space vehicle system except the space vehicle system. The use case comprises a system-level use case and a subsystem-level use case; the system-level use case is a use case of a space vehicle system corresponding to the function architecture; and the subsystem-level use case is a use case of each subsystem of the space vehicle system. The object flow in the use case activity comprises information, signals, materials, forces and energy between use case activities. The function structure comprises a function structure tree, and is used for displaying a tree structure relationship of function calling between use case activities. A parent node calls a function of a child node, and a root node of the function structure tree is a system-level use case activity which has a one-to-one relationship with a system-level use case. The method for generating the function architecture comprises the following steps: connecting functions in the same function group according to function logical relationships; connecting the functions by using port and flow attributes of a SysML internal block diagram to construct the function architecture; and determining a connection relationship between ports according to the object flow defined in the use case activity model. The use case activity comprises a function partition representing a user interest of a system and a function partition connecting the user to a related system for input and output interaction.
2. The method for generating a functional architecture based on a SysML model according to claim 1, characterized in that, The computer program is executed by the processor to realize the steps of the method according to any one of claims 1 to 5. The processor executes the computer program to realize the steps of the method according to any one of claims 1 to 5.
3. The method of claim 2, wherein, 4. The method of claim 1, wherein, 5. The method of claim 4, wherein, 6. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1-5. 7. A SysML model-based functional architecture generation device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that:
Citation Information
Patent Citations
Hierarchical system integration design modeling method
CN107944095A