Automatic functional model checking method based on SysML language

Abstract

The invention discloses an automatic functional model checking method based on a SysML language. The automatic functional model checking method comprises an automatic functional model demand completeness checking method based on the SysML language and an automatic functional model interface and signal design correctness checking method based on the SysML language. The method mainly comprises the steps of defining inspection requirements, compiling inspection rule codes, deploying the inspection rule codes and operating a function model to display an inspection result. By adopting the automatic functional model checking method based on the SysML language, an effective means for carrying out data exchange and functional model consistency checking on the whole and a subsystem based on the functional model is provided, the influence of artificial subjective factors on the quality of the functional model can be reduced, the checking time and the labor cost are reduced, the checking efficiency of the functional model is improved, and the checking efficiency of the functional model is improved. Whether the functional model has the problems of non-standard functional modeling and the like is automatically verified, frequent change of the functional model due to low-level problems in design is avoided, and the functional model is ensured to meet subsequent design verification requirements.

Description

Technical Field

[0001] The invention relates to an automatic checking method for a function model based on SysML language, and belongs to the field of digital design of aerospace products. Background Art

[0002] In recent years, model-based system engineering technology has become a hot topic in the research of complex system design at home and abroad, with its advantages of standardized description, consistent understanding, convenient cross-domain data model transmission, data change and traceability, and is also an effective means to solve the complex system design of aerospace products at home and abroad. In the field of new generation aerospace products, the use of SysML language to build functional models can realize design and verification, improve the core capabilities of aerospace products, and effectively support the digital construction of aerospace products.

[0003] With the application of MBSE technology, the functional model becomes the only data source for expressing system design information, and will serve as the data basis for subsequent system solution verification. Therefore, the correctness check of the functional model is particularly important in the development of aerospace products. However, on the one hand, due to the different design habits, uneven design levels, and different familiarity with functional modeling tools of designers, there may be problems in the completeness of the requirements of the functional model, the correctness of the interface and signal design, etc., which will eventually affect the quality of aerospace product development and cause design repetitions; on the other hand, the functional model based on the SysML language for the new generation of aerospace products involves thousands of SysML diagrams, a large number of model elements, and a relatively complex model architecture. There are great limitations in the use of manual methods for inspection, which requires a lot of inspection time and has low inspection efficiency, which may affect the development progress of aerospace products and make it difficult to ensure that the quality of the functional model meets the needs of the product.

[0004] In summary, there is an urgent need to study the automated checking method of functional models based on the SysML language, so as to ensure the correctness and completeness of the functional model while reducing the problems of low efficiency and high time cost caused by manual checking. Summary of the invention

[0005] The technical problem solved by the present invention is: to overcome the above-mentioned deficiencies of the prior art and provide a method for automatically checking functional models based on the SysML language, thereby promoting the improvement of the design quality of the functional models and ensuring that the quality of the functional models meets the requirements of subsequent work.

[0006] The technical solution of the present invention is: a method for automatically checking a functional model based on the SysML language, comprising:

[0007] Based on SysML language, automatic check of functional model requirements completeness is performed;

[0008] Based on the SysML language, the correctness of the functional model interface and signal design is automatically checked.

[0009] The method for automatically checking the completeness of functional model requirements based on the SysML language includes:

[0010] Define the requirements completeness requirements in the functional model, and write the requirements completeness check rule code based on the OCL language according to the requirements completeness requirements;

[0011] Deploy the requirement completeness check rule code to the functional model to be checked;

[0012] Run the function model to be checked, display the result of the function model requirement completeness check, automatically filter out the requirement items in the function model that do not meet the requirement completeness requirements, and display the error information of the requirement completeness check.

[0013] The requirement completeness of the requirements in the functional model is that the functional model has the requirement relationship of inheritance, refinement, traceability and satisfaction.

[0014] The method of deploying the requirement completeness check rule code to the functional model to be checked includes: establishing a "requirement check rule" real-time simulation check type folder in the aerospace product functional model to be checked, establishing a check "requirement completeness check" constraint in the folder, embedding the requirement completeness check rule OCL code into the constraint, and setting the constraint attribute to be callable and the constraint type to the requirement type.

[0015] The function model to be checked is run, and the result of the function model requirement completeness check is displayed. The requirement items that do not meet the requirement completeness requirements in the function model are automatically screened out, and the error information of the requirement completeness check is displayed, including:

[0016] When the functional model to be checked is run, requirements without detailed requirement relationships are screened out, and the error information of the requirement item is displayed, showing that the error type is defined as "warning", the error description is "the requirement is not refined by the functional model", and the error display effect is highlighted in yellow; requirements without traceable requirement relationships are screened out and the error type is displayed as "error", and the error content is "the requirement is not traced by downstream requirements".

[0017] The error message includes the error type, error description, and error severity.

[0018] The SysML language is used to automatically check the correctness of the functional model interface and signal design, including:

[0019] Define the requirements for correctness of interface and signal design, and compile the interface and signal design correctness checking rule codes according to the above requirements;

[0020] Deploy the interface and signal design correctness check rule code to the functional model to be checked;

[0021] Run the functional model to display the results of the functional model interface and signal design correctness check rules, automatically filter out the interfaces or signals in the functional model that do not meet the interface and signal design correctness requirements, and display the interface or signal design correctness check error information.

[0022] The interface and signal design correctness requirements include interface design correctness requirements and signal design correctness requirements; the interface design correctness requirement means that the external interface of the system at this level is fully covered during the logical simulation of the system functional model, otherwise the interface design is incorrect; the signal design correctness requirement means that the interactive signals designed in the overall functional model should be fully covered when the interactive signals are designed in the subsystem functional model, otherwise the signal design is incorrect.

[0023] The method of deploying the interface and signal design correctness check rule code to the functional model to be checked includes: establishing a "requirement check rule" real-time simulation check type folder in the aerospace product functional model to be checked, establishing a "requirement completeness check" constraint in the folder, embedding the requirement completeness check rule OCL code into the constraint, and setting the constraint attribute to be callable and the constraint type to the requirement type.

[0024] The function model is run, and the results of the function model interface and signal design correctness check rules are displayed, and the interfaces or signals in the function model that do not meet the interface and signal design correctness requirements are automatically screened out, and the interface or signal design correctness check error information is displayed, including: running the function model to be checked, the requirements that do not have a detailed requirement relationship are screened out, and the error information of the requirement item is displayed at the same time, showing its error type as "warning", the error description is "the requirement has not been refined by the function model", and the error display effect is highlighted in yellow; the requirements that do not have a traceable requirement relationship are screened out and the error type is displayed as "error", the error content is "the requirement has not been traced by downstream requirements", and the error display effect is highlighted in red.

[0025] The advantages of the present invention compared with the prior art are:

[0026] (1) The relevant standard requirements and design experience of the functional model are solidified in the automated inspection method of the functional model. By applying the inspection rules, the impact of human subjective factors on the quality of the functional model is reduced, and the inspection standards of the functional model are unified.

[0027] (2) The use of an automated functional model inspection method reduces inspection time and labor costs, improves the inspection efficiency of the functional model, and automatically verifies whether the functional model has problems such as non-standard functional modeling, avoids frequent changes to the functional model due to low-level problems during the design, and ensures that the functional model meets the subsequent design verification requirements.

[0028] (3) The use of an automated functional model inspection method provides an effective means for the overall and subsystems to exchange data and verify the consistency of functional models based on the functional model, thereby improving the quality and efficiency of model and data transmission between the overall and subsystem factories. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 Automating the inspection methodology process for functional models;

[0030] Figure 2 This is a diagram showing the results of the functional model requirement completeness check;

[0031] Figure 3 This is a schematic diagram of the correctness check result of the functional model interface design;

[0032] Figure 4 This is an illustration of the correctness check results of the functional model signal design. DETAILED DESCRIPTION

[0033] The invention discloses an automatic checking method for a functional model based on SysML language, including an automatic checking method for completeness of functional model requirements based on SysML language and an automatic checking method for correctness of design of functional model interface and signal based on SysML language.

[0034] (1) The automatic checking method for the completeness of functional model requirements based on SysML language mainly includes three steps: defining the completeness requirements of requirements and writing the completeness checking rule code for requirements, deploying the completeness checking rule code for requirements, and running the functional model to display the completeness checking results of the functional model requirements. Figure 1 As shown;

[0035] The specific technical solutions are as follows:

[0036] 1) Define the requirements for completeness of requirements in the functional model. Combined with the characteristics of aerospace product development, it can be defined as follows in implementation: the requirements in the functional model should have inheritance, refinement, traceability, and satisfaction, otherwise the requirements are incomplete. According to the defined requirements completeness requirements, write the requirements completeness check rule code based on the OCL language.

[0037] 2) Configure the requirement completeness check rule code to the checked functional model. In combination with the characteristics of the aerospace product functional model, a "requirement check rule" real-time simulation check type folder can be established in the checked aerospace product functional model during implementation, and a check "requirement completeness check" constraint can be established in the folder. The requirement completeness check rule OCL code is embedded in the constraint, and the constraint attribute is set to be callable, and the constraint type is the requirement type.

[0038] 3) Run the functional model to display the functional model requirement completeness check results, display the functional model requirement completeness check results, realize automatic screening of requirement items that do not meet the requirement completeness requirements in the functional model, and display the requirement completeness check error information, which includes detailed descriptions such as error type, error description, and error severity. In combination with the characteristics of aerospace product functional models, the checked functional model is run during implementation, and requirements that do not have detailed requirement relationships are screened out, and the error information of the requirement item is displayed, showing that the error type is "warning", the error description is "the requirement has not been refined by the functional model", and the error display effect is highlighted in yellow; requirements that do not have traceable requirement relationships are screened out and the error type is displayed as "error", and the error content is "the requirement has not been traced by downstream requirements", and the error display effect is highlighted in red. Figure 2 shown.

[0039] (2) An automated checking method for the correctness of the interface and signal design of a functional model based on the SysML language mainly includes three steps: defining the requirements for the correctness of the interface and signal design and writing the code for checking the correctness of the interface and signal design; deploying the code for checking the correctness of the interface and signal design; and running the functional model to display the results of checking the correctness of the interface and signal design. Figure 3 shown.

[0040] The specific technical solutions are as follows:

[0041] 1) Define the requirements for correctness of interface and signal design. Combined with the characteristics of aerospace product development, they can be defined as follows during implementation: Requirements for correctness of interface and signal design include requirements for correctness of interface design and correctness of signal design. The correctness requirement of interface design refers to the complete coverage of the external interface of the system at this level during the logical simulation of the system functional model, otherwise the interface design is incorrect; the correctness requirement of signal design refers to the fact that the interactive signals designed in the overall functional model should be completely covered when the interactive signals are designed in the subsystem functional model, otherwise the signal design is incorrect; based on the Java language, write the interface design correctness check rule code according to the defined interface correctness requirements, and write the signal design correctness check rule code according to the defined signal correctness requirements.

[0042] 2) Deploy the interface and signal design correctness check rule code to the checked functional model. In combination with the characteristics of the aerospace product functional model, during implementation, an "interface check rule" real-time simulation check type folder and a "signal check rule" real-time simulation check type folder can be established in the checked aerospace product functional model, and "interface design correctness" check constraints and "signal design correctness" check constraints can be established in the folders. The interface design correctness check rule Java code is embedded in the "interface design correctness" check constraint, and the constraint attribute is set to callable, and the constraint type is interface type. The signal design correctness check rule Java code is embedded in the "signal design correctness" check constraint, and the constraint attribute is set to callable, and the constraint type is signal type.

[0043] 3) Run the functional model, display the results of the functional model interface and signal design correctness check rules, automatically filter out the interfaces or signals in the functional model that do not meet the interface and signal design correctness requirements, and display the interface or signal design correctness check error information, which includes detailed descriptions such as error type, error description, and error severity. In combination with the characteristics of aerospace product functional models, the functional model to be checked is run during implementation, and incorrectly designed interfaces are screened out. At the same time, the interface error information is displayed, showing that the error type is "error" and the error description is "external interface is missing in functional logic simulation". The error display effect is highlighted in red, such as Figure 4 As shown in the figure, incorrectly designed signals are screened out and the error information of the signal is displayed at the same time, showing that the error type is "error" and the error description is "the overall signal is omitted in the subsystem design". The error display effect is highlighted in red, such as Figure 4 shown.

[0044] Although the present invention has been disclosed as above in the form of a preferred embodiment, it is not intended to limit the present invention. Any person skilled in the art can make possible changes and modifications to the technical solution of the present invention by using the technical contents disclosed above without departing from the spirit and scope of the present invention. Therefore, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention shall fall within the protection scope of the technical solution of the present invention.

Claims

1. A method for automatic checking of functional models based on SysML language, characterized in that: include: Based on SysML language, automatic check of functional model requirements completeness is performed; Based on the SysML language, the correctness of the functional model interface and signal design is automatically checked.

2. The method for automatic checking of functional models based on SysML language according to claim 1, characterized in that: The method for automatically checking the completeness of functional model requirements based on the SysML language includes: Define the requirements completeness requirements in the functional model, and write the requirements completeness check rule code based on the OCL language according to the requirements completeness requirements; Deploy the requirement completeness check rule code to the functional model to be checked; Run the function model to be checked, display the result of the function model requirement completeness check, automatically filter out the requirement items in the function model that do not meet the requirement completeness requirements, and display the error information of the requirement completeness check.

3. The method for automatic checking of functional models based on SysML language according to claim 2, characterized in that: The requirement completeness of the requirements in the functional model is that the functional model has the requirement relationship of inheritance, refinement, traceability and satisfaction.

4. The method for automatically checking a functional model based on SysML language according to claim 2, characterized in that: The method of deploying the requirement completeness check rule code to the functional model to be checked includes: establishing a "requirement check rule" real-time simulation check type folder in the aerospace product functional model to be checked, establishing a "requirement completeness check" constraint in the folder, embedding the requirement completeness check rule OCL code into the constraint, and setting the constraint attribute to be callable and the constraint type to the requirement type.

5. The method for automatic checking of functional models based on SysML language according to claim 2, characterized in that: The function model to be checked is run, and the result of the function model requirement completeness check is displayed. The requirement items that do not meet the requirement completeness requirements in the function model are automatically screened out, and the error information of the requirement completeness check is displayed, including: When the functional model to be checked is run, requirements without detailed requirement relationships are screened out, and the error information of the requirement item is displayed, showing that the error type is defined as "warning", the error description is "the requirement is not refined by the functional model", and the error display effect is highlighted in yellow; requirements without traceable requirement relationships are screened out and the error type is displayed as "error", and the error content is "the requirement is not traced by downstream requirements".

6. The method for automatic checking of functional models based on SysML language according to claim 2, characterized in that: The error message includes the error type, error description, and error severity.

7. The method for automatic checking of functional models based on SysML language according to claim 1, characterized in that: The SysML language is used to automatically check the correctness of the functional model interface and signal design, including: Define the requirements for correctness of interface and signal design, and compile the interface and signal design correctness checking rule codes according to the above requirements; Deploy the interface and signal design correctness check rule code to the functional model to be checked; Run the functional model to display the results of the functional model interface and signal design correctness check rules, automatically filter out the interfaces or signals in the functional model that do not meet the interface and signal design correctness requirements, and display the interface or signal design correctness check error information.

8. The method for automatic checking of functional models based on SysML language according to claim 1, characterized in that: The interface and signal design correctness requirements include interface design correctness requirements and signal design correctness requirements; the interface design correctness requirements refer to the external interface of the system at this level being fully covered during the logic simulation of the system function model, otherwise the interface design is incorrect; The signal design correctness requirement means that the interactive signals designed in the overall functional model should be fully covered when designing the interactive signals in the subsystem functional model, otherwise the signal design is incorrect.

9. The method for automatic checking of functional models based on SysML language according to claim 1, characterized in that: The method of deploying the interface and signal design correctness check rule code to the functional model to be checked includes: establishing a "requirement check rule" real-time simulation check type folder in the aerospace product functional model to be checked, establishing a "requirement completeness check" constraint in the folder, embedding the requirement completeness check rule OCL code into the constraint, and setting the constraint attribute to be callable and the constraint type to the requirement type.

10. The method for automatic checking of functional models based on SysML language according to claim 1, characterized in that: The function model is run, and the results of the function model interface and signal design correctness check rules are displayed, and the interfaces or signals in the function model that do not meet the interface and signal design correctness requirements are automatically screened out, and the error information of the interface or signal design correctness check is displayed, including: running the function model to be checked, the requirements that do not have detailed requirement relationships are screened out, and the error information of the requirement item is displayed at the same time, showing its error type as "warning", the error description is "the requirement has not been refined by the function model", and the error display effect is highlighted in yellow; the requirements that do not have traceable requirement relationships are screened out and the error type is displayed as "error", the error content is "the requirement has not been traced by downstream requirements", and the error display effect is highlighted in red.

Images