Model-based system architecture distributed collaborative modeling method

Abstract

The invention provides a model-based system architecture distributed collaborative modeling method. The method comprises the following steps of capturing a top-layer use case; further decomposing the top-layer use case, and capturing an atomic use case; performing labor division and progress control on the atomic use case; establishing an independent use case development work package for the atomic use case which each person in charge is responsible for, and independently developing the atomic use case development work; establishing an independent function decomposition work package for the atomic use case in charge of each person in charge; according to the method, collaborative architecture modeling software is applied, an atomization use case modeling method is adopted to construct and decompose use cases, work is divided on the architecture modeling top layer based on the high-cohesion and low-coupling thought, independent use case modeling and function modeling work packages are established, and collaborative modeling, project division and progress management are achieved.

Description

Technical Field

[0001] The present application belongs to the technical field of overall design of complex equipment, and in particular, relates to a distributed collaborative modeling method of system architecture based on a model. Background Art

[0002] The core of Model-Based Systems Engineering (MBSE) is model-based system architecture design, which supports the system's requirements, design, analysis, verification and validation activities from the conceptual design stage to the development stage and subsequent life cycle stages by using models as a formal expression method.

[0003] The system architecture model is the core of model-based system engineering. In the process of model practice, tens of thousands of system architecture model elements need to be constructed. The modeling workload is large, the scope is wide, and many people are involved. It is a huge challenge to build a high-quality architecture model with clear hierarchy and consistent granularity. The traditional model-based system engineering methodology does not describe collaborative modeling. Summary of the invention

[0004] Purpose of the invention: This application applies collaborative architecture modeling software, adopts atomic use case modeling method to build and decompose use cases, divides the work at the top level of architecture modeling based on the idea of ​​high cohesion and low coupling, establishes independent use case modeling and functional modeling work packages, and realizes collaborative modeling, project division of labor and progress management.

[0005] The present application provides a distributed collaborative modeling method for a model-based system architecture, the method comprising the following steps:

[0006] Capture top-level use cases;

[0007] Further decompose the top-level use case to capture atomic use cases;

[0008] Divide the work and control the progress of the atomic use cases;

[0009] For each atomic use case that each responsible person is responsible for, an independent use case development work package is established to independently carry out atomic use case development work;

[0010] For each atomic use case that each responsible person is responsible for, establish an independent functional decomposition work package.

[0011] Preferably, the top-level use case includes a takeoff use case; further decomposing the top-level use case to capture atomic use cases includes:

[0012] The takeoff use case is further decomposed into one-key takeoff, manual takeoff, first navigation and first communication.

[0013] Preferably, the top-level use case includes a cruise use case, and further decomposing the top-level use case to capture atomic use cases includes:

[0014] The cruise use case is further decomposed into automatic cruise, manual cruise, second navigation and second communication; wherein the first navigation is the same as the second navigation, and the first communication is the same as the second communication.

[0015] Preferably, the division of labor and progress control of the atomic use cases include:

[0016] The one-key takeoff, the manual takeoff, the first navigation and the first communication are assigned to persons in charge of corresponding professions, and the persons in charge can update the progress at any time.

[0017] Preferably, the one-key takeoff, the manual takeoff, the first navigation and the first communication are assigned to persons in charge of corresponding professions, and the persons in charge can update the progress at any time, including:

[0018] Assigning the one-key takeoff and the manual takeoff to a person in charge of the flight major, who can update the progress at any time;

[0019] Assigning the first navigation to the person in charge of the navigation specialty, who can update the progress at any time;

[0020] The first communication is assigned to the person in charge of the communication major, who can update the progress at any time.

[0021] Preferably, for each atomic use case that each responsible person is responsible for, an independent use case development work package is established to independently carry out atomic use case development work, including:

[0022] For the person in charge of the flight profession, the one-key takeoff and the manual takeoff shall be responsible for establishing independent use case development work packages, and independently carry out the development work of the one-key takeoff and the manual takeoff;

[0023] For the first navigation, the person in charge of the navigation specialty shall establish an independent use case development work package and independently carry out the development work of the first navigation;

[0024] For the first communication, for which the person in charge of the communication major is responsible, an independent use case development work package is established to independently carry out the development work of the first communication.

[0025] Preferably, the functional decomposition work package includes a functional decomposition tree, a functional description table and a functional traceability matrix.

[0026] Preferably, the method further comprises:

[0027] Performing functional decomposition based on the functional decomposition tree;

[0028] Carry out functional requirement description based on the functional description table;

[0029] The traceability relationship of functions to stakeholder requirements is captured based on the functional traceability matrix.

[0030] Beneficial technical effects of this application:

[0031] This application decomposes complex system architecture modeling problems layer by layer. Each designer only needs to focus on the perspective he is familiar with to carry out modeling. The modeling software automatically summarizes and integrates, simplifies complex problems, and clarifies simple problems, which can achieve the team's "1+1>2" effect, significantly improve modeling efficiency, improve model building quality, and shorten the work cycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a typical top-level use case diagram provided in the embodiment of the present application;

[0033] Figure 2 It is a schematic diagram of an atomic use case provided in an embodiment of the present application;

[0034] Figure 3 It is a schematic diagram of project division of labor and project progress management based on a model provided in an embodiment of the present application;

[0035] Figure 4 This is a schematic diagram of an independent work package for use case development provided in an embodiment of the present application;

[0036] Figure 5 It is a use case development diagram provided by an embodiment of the present application;

[0037] Figure 6 It is a schematic diagram of independent work packages of functional decomposition provided in an embodiment of the present application;

[0038] Figure 7 It is a schematic diagram of a functional decomposition tree provided in an embodiment of the present application;

[0039] Figure 8 It is a functional description schematic diagram provided by an embodiment of the present application;

[0040] Fig. 9 It is a functional tracing schematic diagram provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] This application uses a combination of "tools + methodology + training" to construct a collaborative architecture modeling method of "collaborative modeling software + atomic use case division + personal modeling interface" based on the decomposition idea of ​​"high cohesion and low coupling". Complex problems are decomposed layer by layer, so that each designer only needs to focus on the perspective he is familiar with to carry out modeling, and the summary and synthesis are automatically completed by the software, ultimately achieving the effect of "1+1>2".

[0042] This application uses the collaborative modeling software TeamworkC l oud as a collaborative modeling tool and MagicDraw as a system architecture modeling tool.

[0043] This application uses the atomic use case modeling method to construct and decompose use cases, and divides the work at the top level of architecture modeling based on the idea of ​​high cohesion and low coupling. The method is divided into five steps, the first step is to capture the top-level use cases. The aircraft mission profile is used as the input for use case analysis, and use cases are captured in the order of executing tasks, including pre-takeoff preparation, takeoff, climb, cruise, descent, and landing, such as Figure 1 shown.

[0044] The second step is to further decompose the top-level use cases and capture atomic use cases. The top-level use cases are further decomposed according to the idea of ​​high cohesion and low coupling, and the use case decomposition is carried out according to the different modes in the execution process. Taking takeoff as an example, the takeoff use case can be further decomposed into one-key takeoff, manual takeoff, navigation and communication, such as Figure 2 As shown. The pre-takeoff preparation use case can be further decomposed into refueling and pre-flight inspection; the climb use case can be further decomposed into automatic climb, manual climb, navigation and communication; the cruise use case can be further decomposed into automatic cruise, manual cruise, navigation and communication; the descent use case can be further decomposed into automatic descent, manual descent, communication and navigation; the landing use case can be further decomposed into automatic landing, manual landing, communication and navigation. Navigation and communication use cases are decomposed in the takeoff, climb, cruise and other use cases, and only need to be developed once in the actual development process. The atomic decomposition of use cases realizes the decoupling between use cases. Use cases with similar functions can be developed by specific professional designers, reducing the communication costs caused by overlapping work.

[0045] The third step is to divide the work and control the progress of the atomic use cases. This application uses a model-based approach to carry out work division and project progress management. Work items and progress information will be updated in real time with the model, so that changes in one place can be updated everywhere. After completing the atomic use case decomposition, the project division and progress control are carried out for the atomic use cases. A model-based approach is used to build a model table, such as Figure 3 As shown. Flight-related use cases can be uniformly assigned to flight professional designers for development; communication-related use cases can be assigned to communication professional designers for development; navigation-related use cases are developed by navigation professional designers. If any use case is added, deleted, or the responsible person is changed during the atomic use case development process, the use case item of the project control table will be updated immediately to ensure the uniqueness of the data source.

[0046] The fourth step is to establish an independent use case development work package for each responsible person's atomic use case, and independently carry out the atomic use case development work. This application uses a professional independent modeling interface to build an independent work package, and establishes a modeling interface exclusive to each person for each work, so that each designer can focus on his or her own professional modeling without having to pay attention to the entire project. According to the atomic use case division, an independent work package can be established for each responsible person to independently carry out the use case development work, such as Figure 4 As shown. A is a flight professional designer, whose work package includes all flight-related atomic use cases, such as one-key takeoff and manual takeoff; B is a navigation professional designer, responsible for the development of navigation-related atomic use cases; C is a communication professional designer, responsible for the development of communication-related atomic use cases. This application conducts use case modeling and function development based on SysML activity diagrams, such as Figure 5 Taking the one-key takeoff use case as an example, modeling is carried out based on the activity diagram. The pilot performs the one-key takeoff operation. The aircraft receives the one-key takeoff command and first automatically takes off vertically. After reaching a safe altitude, it starts to automatically hover and waits for subsequent operation instructions. After the team members complete the use case modeling of their respective divisions of labor, the entire model has completed the use case development.

[0047] The fifth step is to establish an independent functional decomposition work package for each atomic use case responsible for each responsible person. This application focuses on functional decomposition and functional definition, and establishes an independent functional decomposition work package based on the division of labor of use cases, including a functional decomposition tree, a functional description table, and a functional traceability matrix, such as Figure 6 .

[0048] This application builds a function decomposition tree based on the relationship diagram. Taking one-key takeoff as an example, it can be decomposed into functions such as operating one-key takeoff, receiving one-key takeoff instructions, automatic vertical takeoff, and safe height hovering. Figure 7 After team members complete the functional decomposition tree of their respective responsibilities, the functional decomposition tree of the entire model can be automatically generated.

[0049] This application constructs a functional description based on a table, which specifically includes that after the aircraft flies to a specified location, it should have the function of vertical landing; the aircraft should be able to automatically hover after vertical takeoff to a safe height; the aircraft should have a navigation function during flight; the aircraft should be able to take off manually according to the pilot's operating instructions; the aircraft should be able to accept the pilot's one-key takeoff instruction; the aircraft should be able to automatically descend along the established route in the automatic flight mode; the aircraft should have the function of vertical takeoff in the automatic flight mode; the aircraft should be able to automatically cruise to the destination along the established route; the aircraft should have the function of communicating with other aircraft on the ground and in the air according to the pilot's instructions, such as Figure 8 After team members complete the functional description of their respective responsibilities, the functional description of the entire model can be automatically generated.

[0050] This application constructs a traceability relationship between capture functions and stakeholder needs based on a traceability matrix, where vertical pursuit, safe altitude hovering, receiving one-key takeoff instructions, automatic descent, automatic vertical takeoff, automatic cruise and other functions can be traced back to the automatic flight needs mentioned by stakeholders; the manual takeoff function can be traced back to the manual flight needs mentioned by stakeholders; the navigation function can be traced back to the navigation needs mentioned by stakeholders; the communication function can be traced back to the communication needs mentioned by stakeholders, such as Fig. 9 After team members complete the functional traceability of their respective responsibilities, the functional traceability of the entire model can be automatically generated.

[0051] The modeling content and modeling steps of the above work packages require training for designers. Designers only need to complete the assigned modeling content based on their expertise and can carry out collaborative modeling work without having to understand the complex language, tools and methods of model-based system engineering.

[0052] It should be noted that:

[0053] (1) Atomic use case division;

[0054] (2) Model-based work division and project progress management;

[0055] (3) Independent use case modeling and functional modeling work packages.

[0056] This application decomposes complex system architecture modeling problems layer by layer. Each designer only needs to focus on the perspective he is familiar with to carry out modeling. The modeling software automatically summarizes and integrates, simplifies complex problems, and clarifies simple problems, which can achieve the team's "1+1>2" effect, significantly improve modeling efficiency, improve model building quality, and shorten the work cycle.

[0057] The present application provides a model-based distributed collaborative modeling method for system architecture, the method comprising the following steps: capturing top-level use cases; further decomposing the top-level use cases to capture atomic use cases; dividing the work and controlling the progress of the atomic use cases; establishing an independent use case development work package for the atomic use cases for each responsible person, and independently carrying out atomic use case development work; establishing an independent functional decomposition work package for the atomic use cases for each responsible person; the present invention applies collaborative architecture modeling software, adopts an atomic use case modeling method to construct and decompose use cases, divides the work at the top level of architecture modeling based on the idea of ​​high cohesion and low coupling, establishes independent use case modeling and functional modeling work packages, and realizes collaborative modeling, project division of work and progress management.

Claims

1. A distributed collaborative modeling method for system architecture based on a model, characterized in that: The method comprises the following steps: Capture top-level use cases; Further decompose the top-level use case to capture atomic use cases; Divide the work and control the progress of the atomic use cases; For each atomic use case that each responsible person is responsible for, an independent use case development work package is established to independently carry out atomic use case development work; For each atomic use case that each responsible person is responsible for, establish an independent functional decomposition work package.

2. The method according to claim 1, characterized in that The top-level use case includes a takeoff use case; the top-level use case is further decomposed to capture atomic use cases, including: The takeoff use case is further decomposed into one-key takeoff, manual takeoff, first navigation and first communication.

3. The method according to claim 2, characterized in that The top-level use case includes a cruise use case, and the top-level use case is further decomposed to capture atomic use cases, including: The cruise use case is further decomposed into automatic cruise, manual cruise, second navigation and second communication; wherein the first navigation is the same as the second navigation, and the first communication is the same as the second communication.

4. The method according to claim 2, characterized in that: The division of labor and progress control of the atomic use cases include: The one-key takeoff, the manual takeoff, the first navigation and the first communication are assigned to persons in charge of corresponding professions, and the persons in charge can update the progress at any time.

5. The method according to claim 4, characterized in that The one-key takeoff, the manual takeoff, the first navigation and the first communication are assigned to persons in charge of corresponding professions, and the persons in charge can update the progress at any time, including: Assigning the one-key takeoff and the manual takeoff to a person in charge of the flight major, who can update the progress at any time; Assigning the first navigation to the person in charge of the navigation specialty, who can update the progress at any time; The first communication is assigned to the person in charge of the communication major, who can update the progress at any time.

6. The method according to claim 5, characterized in that For each atomic use case that each responsible person is responsible for, an independent use case development work package is established to independently carry out atomic use case development work, including: For the person in charge of the flight profession, the one-key takeoff and the manual takeoff shall be responsible for establishing independent use case development work packages, and independently carry out the development work of the one-key takeoff and the manual takeoff; For the first navigation, the person in charge of the navigation specialty shall establish an independent use case development work package and independently carry out the development work of the first navigation; For the first communication, for which the person in charge of the communication major is responsible, an independent use case development work package is established to independently carry out the development work of the first communication.

7. The method according to claim 1, characterized in that The functional decomposition work package includes a functional decomposition tree, a functional description table and a functional traceability matrix.

8. The method according to claim 7, characterized in that The method further comprises: Performing functional decomposition based on the functional decomposition tree; Carry out functional requirement description based on the functional description table; The traceability relationship of functions to stakeholder requirements is captured based on the functional traceability matrix.

Images