A cross-system hierarchical SysML model collaborative design method

Abstract

A kind of SysML model collaborative design method across system level, it is based on the collaborative function TWC of CATIA-Magic, in combination with the latest developed model management platform, system-subsystem collaborative modeling and version control are carried out, the specific technical scheme includes:1). create system design model organization structure, 2). create subsystem technical requirement release model, 3). subsystem technical requirement model issue, 4). subsystem model design evolution, 5). subsystem design model hand in, 6). subsystem technical requirement change issue, 7). system design model synthesis, the method collaborative design operation is simple, and updating iteration is efficient, designer can efficiently complete the system-subsystem collaborative design based on SysML based on this design method, and can achieve mutual protection of intellectual property during collaborative design process.

Description

Technical Field

[0001] This invention relates to the field of SysML modeling technology for complex equipment, and in particular to a cross-system level SysML model collaborative design method. Background Technology

[0002] SysML (System Building Modeling Language) is a general-purpose modeling language for systems engineering applications. It supports the specification, analysis, design, verification, and validation of a wide range of systems and systems-wide systems. SysML was originally developed by an open-source specification project and includes an open-source license for distribution and use. SysML is defined as an extension of a subset of the Unified Modeling Language (UML) using UML's configuration file mechanism. Currently, in the process of complex equipment modeling and design based on SysML, collaborative design between superiors and subordinates requires interaction through models. Existing design methods cannot support convenient collaborative design between systems and subsystems based on SysML models, and designers lack standardized methodological guidance when collaboratively designing using SysML.

[0003] The lack of a guiding collaborative modeling design method in the SysML-based model design process between the system and subsystems leads to exceptionally complex SysML model design processes between different levels, severely impacting the model iteration and update speed. The absence of a unified collaborative modeling standard in SysML model collaborative design makes model interaction errors prone to occur during collaboration between designers at different levels, consuming significant review time and hindering design progress and effective communication.

[0004] This application introduces a collaborative modeling design method and standardized process based on SysML models. This method is simple to operate and efficient in updating and iterating. Designers can use this design method to efficiently complete the collaborative design of systems and subsystems based on SysML, and can achieve mutual protection of intellectual property rights during the collaborative design process. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides a cross-system-level SysML model collaborative design method. This method features simple collaborative design operations and efficient update iterations.

[0006] A cross-system-level SysML model collaborative design method, the specific technical solution of which is as follows:

[0007] Step 1: Constructing a system design model

[0008] This step involves building a system design model in the system architecture design tool CATAI-Magic, and following a certain methodology to guide the design process of system task analysis and requirements analysis, ultimately obtaining itemized expressions of the technical requirements of each subsystem. When the system design reaches a certain level of maturity, a model for issuing the technical requirements of the subsystem is created. This model in this version only contains the technical requirements of the subsystem.

[0009] Step 2: Subsystem Design Technical Requirements Model

[0010] After the subsystem technical requirements model is completed, the subsystem designer will reference the technical requirements in the CATIA-Magic tool using the Usage method. The referenced requirements can then be used as design input to carry out the subsystem solution design process.

[0011] Step 3: Construct design models for each subsystem

[0012] During the collaborative design process, once the technical requirements of other subsystems have matured, a version of the technical model for that subsystem is automatically released based on the system design model. The subsystem can then proceed with its design based on this version of the model.

[0013] Step 4: Distribution and reference of technical requirement models for each subsystem

[0014] Each subsystem can reference one version of the automatically generated release model. The referenced model version only contains the design content of this subsystem. By controlling the reference of different model versions, the technical requirements of each subsystem are protected from being seen by each other.

[0015] Step 5: Submit and reference the design models of each subsystem.

[0016] After the design of each subsystem is completed, the overall system designer will reference the design model of each subsystem through Usage, thus completing the submission of the design model of each subsystem.

[0017] Step Six: Issuance of Subsystem Technical Requirements Changes

[0018] The system as a whole continuously carries out design evolution work within its own design model. When it is discovered during the design process that a certain subsystem technology needs to be changed, a new version of the technical requirements model can be released at any time. The subsystem can then update the referenced technical requirements model to the new version, thus completing the process of issuing changes to the subsystem's technical requirements.

[0019] Furthermore, all steps are performed in the architecture design software CATIA Magic. This method is suitable for designers at different levels of complex equipment to develop system architecture designs based on the same design model using SysML models.

[0020] The beneficial effects of this invention are:

[0021] This invention proposes a collaborative modeling design method and standardized process based on SysML models. This method is simple to operate and efficient in updating and iterating. Designers can use this design method to efficiently complete the collaborative design of systems and subsystems based on SysML, and can achieve mutual protection of intellectual property rights during the collaborative design process.

[0022] This invention is based on the collaborative function TWC of CATIA-Magic, combined with the latest model management platform, to perform system-subsystem collaborative modeling and version control. It effectively connects the entire SysML collaborative modeling process from the overall system to the subsystems, and realizes data management and model version control, which effectively improves development efficiency and data validity. Attached Figure Description

[0023] Figure 1 This is a schematic diagram illustrating an example of a cross-system-level SysML model collaborative design method according to the present invention. Detailed Implementation

[0024] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] Example 1

[0026] A cross-system-level SysML model collaborative design method, the specific technical solution of which is as follows:

[0027] Step 1: Constructing a system design model

[0028] This step involves building a system design model in the system architecture design tool CATAI-Magic, and following a certain methodology to guide the design process of system task analysis and requirements analysis, ultimately obtaining itemized expressions of the technical requirements of each subsystem. When the system design reaches a certain level of maturity, a model for issuing the technical requirements of the subsystem is created. This model in this version only contains the technical requirements of the subsystem.

[0029] Step 2: Subsystem Design Technical Requirements Model

[0030] After the subsystem technical requirements model is completed, the subsystem designer will reference the technical requirements in the CATIA-Magic tool using the Usage method. The referenced requirements can then be used as design input to carry out the subsystem solution design process.

[0031] Step 3: Construct design models for each subsystem

[0032] During the collaborative design process, once the technical requirements of other subsystems have matured, a version of the technical model for that subsystem is automatically released based on the system design model. The subsystem can then proceed with its design based on this version of the model.

[0033] Step 4: Distribution and reference of technical requirement models for each subsystem

[0034] Each subsystem can reference one version of the automatically generated release model. The referenced model version only contains the design content of this subsystem. By controlling the reference of different model versions, the technical requirements of each subsystem are protected from being seen by each other.

[0035] Step 5: Submit and reference the design models of each subsystem.

[0036] After the design of each subsystem is completed, the overall system designer will reference the design model of each subsystem through Usage, thus completing the submission of the design model of each subsystem.

[0037] Step Six: Issuance of Subsystem Technical Requirements Changes

[0038] The system as a whole continuously carries out design evolution work within its own design model. When it is discovered during the design process that a certain subsystem technology needs to be changed, a new version of the technical requirements model can be released at any time. The subsystem can then update the referenced technical requirements model to the new version, thus completing the process of issuing changes to the subsystem's technical requirements.

[0039] Example 2

[0040] by Figure 1 For example, the specific collaboration method is as follows:

[0041] 1) Constructing a system design model

[0042] This step involves building a system design model in the system architecture design tool CATAI-Magic, and following a specific methodology to guide the design process through system task analysis and requirements analysis, ultimately resulting in a list of technical requirements for each subsystem. When the system design reaches a certain level of maturity, such as when the technical requirements for subsystem A are ready for issuance, a model is created for issuing the subsystem's technical requirements. This model in this version only contains the technical requirements for subsystem A.

[0043] 2) Subsystem Design Technical Requirements Model

[0044] After the technical requirements model of subsystem A is completed, the subsystem designer will reference the technical requirements in the CATIA-Magic tool using the Usage method. The referenced requirements can then be used as design input to carry out the subsystem design process.

[0045] 3) Construct design models for each subsystem

[0046] During the collaborative design process, once the technical requirements of subsystem B are mature, a version of the technical model of subsystem B is automatically released based on the system design model. Subsystem B can then proceed with its design based on this version of the model.

[0047] 4) Technical requirement models for each subsystem are distributed and referenced.

[0048] Each subsystem can reference one version of the automatically generated release model. The referenced model version only contains the design content of this subsystem. By controlling the reference of different model versions, the technical requirements of each subsystem are protected so that they are not visible to each other.

[0049] 5) Submit and reference the design models of each subsystem.

[0050] After the design of each subsystem is completed, the overall system designer references the design model of each subsystem through Usage, thus completing the submission of the design model of each subsystem.

[0051] 6) Issuance of subsystem technical requirement changes

[0052] The system as a whole continuously carries out design evolution work within its own design model. When it is discovered during the design process that a certain subsystem technology needs to be changed, a new version of the technical requirements model can be released at any time. The subsystem can then update the referenced technical requirements model to the new version, thus completing the technology release.

[0053] All the above steps are performed in the architecture design software CATIA Magic. This method is suitable for designers at different levels of complex equipment to develop system architecture designs using SysML models based on the same design model.

[0054] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. The various components mentioned in this invention are common technologies in the existing field. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A cross-system-level SysML model collaborative design method, the specific technical solution of which is as follows: Step 1: Constructing a system design model This step involves building a system design model in the system architecture design tool CATAI-Magic, and following a certain methodology to guide the design process of system task analysis and requirements analysis, ultimately obtaining itemized expressions of the technical requirements of each subsystem. When the system design reaches a certain level of maturity, a model for issuing the technical requirements of the subsystem is created. This model in this version only contains the technical requirements of the subsystem. Step 2: Subsystem Design Technical Requirements Model After the subsystem technical requirements model is completed, the subsystem designer will reference the technical requirements in the CATIA-Magic tool using the Usage method. The referenced requirements can then be used as design input to carry out the subsystem solution design process. Step 3: Construct design models for each subsystem During the collaborative design process, once the technical requirements of other subsystems have matured, a version of the technical model for that subsystem is automatically released based on the system design model. The subsystem can then proceed with its design based on this version of the model. Step 4: Distribution and reference of technical requirement models for each subsystem Each subsystem can reference one version of the automatically generated release model. The referenced model version only contains the design content of this subsystem. By controlling the reference of different model versions, the technical requirements of each subsystem are protected from being seen by each other. Step 5: Submit and reference the design models of each subsystem. After the design of each subsystem is completed, the overall system designer will reference the design model of each subsystem through Usage, thus completing the submission of the design model of each subsystem. Step Six: Issuance of Subsystem Technical Requirements Changes The system as a whole continuously carries out design evolution work within its own design model. When it is discovered during the design process that a certain subsystem technology needs to be changed, a new version of the technical requirements model can be released at any time. The subsystem can then update the referenced technical requirements model to the new version, thus completing the process of issuing changes to the subsystem's technical requirements.

2. The cross-system hierarchical SysML model collaborative design method according to claim 1, characterized in that... All steps are performed in the architecture design software CATIA Magic. This method is suitable for designers at different levels of complex equipment to develop system architecture designs based on the same design model using SysML models.

Images