Modeling reduction method for MBSE demand model quality
Through SysML and strict regulation methods, the quality problem of demand model is solved, the accuracy and efficiency of system design is improved, the clarity and verifiability of demand is ensured, and the problem of insufficient quality of demand model in MBSE is solved.
Patent Information
- Application Number
- CN202410914584.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-09
- Publication Date
- 2024-11-01
AI Technical Summary
In model-based system engineering, the quality of the requirement model is not effectively standardized, resulting in ambiguity in expression, incomplete content, inconsistent logic, difficult verification, unclear structure, redundant information and lack of certainty, which affects system design and development Flexibility and safety.
SysML is used for demand modeling, and strict structural, atomized, ambiguity, certainty, integrity, consistency and verifiable regulations are formulated, through hierarchical division, naming rules, link management, semantic analysis, and demand traceability matrix , formal analysis tools and verification standards to ensure the quality of the requirements model.
It improves the quality of the requirements model, ensures the accuracy and efficiency of system design, reduces project risks, and ensures the clarity and verifiability of requirements.
Smart Images

Figure CN118885155A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of model-based system engineering, and in particular to a modeling specification method oriented to MBSE requirement model quality. Background Art
[0002] MBSE, or "Model-Based Systems Engineering", is a specific practice and application of system engineering thinking. It emphasizes the use of modeling technology to describe, design, analyze, verify and confirm complex engineering systems throughout the system life cycle. The system development process is closely centered around requirements. The requirement model connects multiple engineering links such as design and verification in MBSE, playing a key central role.
[0003] In model-based systems engineering (MBSE), the quality of the requirements model has a decisive influence on the quality of system design and implementation. However, in the process of requirements modeling, the clear definition of model quality is often ignored, which easily leads to various problems in the requirements model, such as ambiguous expressions, incomplete content, inconsistent logic, difficult verification, unclear structure, redundant information, and lack of certainty. These problems will not only hinder the smooth design and development of the system, but also greatly increase the potential risks of the project. Therefore, in order to ensure the success of system design and implementation, the quality of the requirements model must be strictly controlled and clearly specified. Summary of the invention
[0004] In view of the defects in the prior art, the purpose of the present invention is to provide a modeling specification method for MBSE requirement model quality. The present invention can improve the modeling specification of the requirement model quality, set strict requirements and constraints for the construction of the model, and improve the accuracy and efficiency of the design.
[0005] To solve the above problems, the technical solution of the present invention is:
[0006] A modeling specification method for MBSE requirement model quality includes the following steps:
[0007] Use SysML for requirements modeling, structural specifications for requirements modeling, and ensure that related requirements are combined to form a more orderly and coordinated system;
[0008] Atomic specification for demand modeling to ensure that each demand avoids redundancy and duplication;
[0009] Reduce ambiguity in the model and conduct in-depth analysis of its semantics to avoid potential ambiguities;
[0010] Deterministic specifications for requirements modeling, focusing on the correct recording, internal consistency, and completeness of requirements for product functions, performance, and attributes, making them clear and concise;
[0011] The completeness specification of demand modeling is to check the sufficiency of all upper-level demands from the perspective of current-level demands, that is, to check whether the current-level demands are sufficient to satisfy the upper-level demands; and to check the necessity of all downwardly allocated demands from the perspective of current-level demands, that is, to check whether all current-level demands are satisfied by the lower-level demands.
[0012] Model the requirements consistently, identify any possible conflicts in requirements, and ensure that there are no contradictory requirements throughout the requirements specification;
[0013] The specification of the verifiability of requirement modeling. The verifiability of requirements means that the requirements can be verified through some method or process to confirm whether they are implemented correctly.
[0014] Preferably, the steps of using SysML for requirements modeling, structural specification of requirements modeling, and ensuring that related requirements are combined together to form a more orderly and coordinated system specifically include:
[0015] Divide the demand level into four levels: customer demand, product demand, subsystem demand, and component demand;
[0016] Use reasonable naming conventions to help quickly identify the nature and level of requirements and the relationship between requirements;
[0017] Use "links" in the requirement diagram to manage the structure of the requirement tree.
[0018] Preferably, the steps of reducing ambiguity in the model and conducting in-depth analysis of its semantics to avoid potential ambiguity specifically include:
[0019] Through refinement relationships, some ambiguous requirements at the same level are subdivided into multiple related specific requirements;
[0020] Develop and follow a set of modeling guidelines or standards to partially structure the text and use consistent modeling conventions;
[0021] The use of quantitative indicators ensures that design and evaluation have clear benchmarks and can be verified and evaluated objectively and quantitatively.
[0022] When quantitative expression is not possible, appropriate attributes such as user feedback and qualitative characteristics are used to accurately explain the specific content of the needs.
[0023] Preferably, the completeness specification of the demand modeling includes the steps of checking the sufficiency of all upper-layer demands from the perspective of the demands of the current layer, i.e., checking whether the demands of the current layer are sufficient to satisfy the upper layer, and checking the necessity of all downwardly allocated demands from the perspective of the demands of the current layer, i.e., checking whether all the demands of the current layer are satisfied by the lower layer, and specifically including:
[0024] Establish a demand traceability matrix to track the relationship between upper-level requirements and current-level requirements, and current-level requirements and lower-level requirements;
[0025] Use the big model to generate contextualized predictions for the gaps in the requirements, and analyze possible missing and incomplete information based on the most likely alternatives predicted by the big model.
[0026] Preferably, the steps of modeling requirements consistently, identifying any possible requirements conflicts, and ensuring that there are no contradictory requirements in the entire requirements specification include:
[0027] Use formal analysis tools to automatically detect logical conflicts in requirement descriptions;
[0028] Filter by attributes to focus on similar or related requirements, and analyze these filtered requirements to ensure that there are no conflicts between requirements of the same type;
[0029] Make sure there are not two or more conflicting requirements;
[0030] Compare different versions of requirement documents, track changes in requirements over time, and ensure that any changes meet consistency requirements;
[0031] By establishing traceability links between requirements and between them and design, implementation, and verification, changes in requirements can be tracked in a timely manner, thereby identifying changes that conflict with existing requirements.
[0032] Preferably, the specification of the verifiability of the requirement modeling, the verifiability of the requirement refers to the steps that the requirement can be verified by a certain method or process to confirm whether it is correctly implemented, specifically including:
[0033] Establish verifiability criteria for requirements and define a clear verification criterion for each requirement;
[0034] Consider the constraints on implementing requirements, review whether the requirements can be implemented within a given cost, time, technical capabilities, and regulatory compliance, and adjust the requirements if necessary to adapt to actual project conditions.
[0035] Compared with the prior art, the present invention proposes a set of comprehensive modeling specifications to address the common deficiencies in requirement modeling in MBSE. The high-quality construction of the requirement model is achieved by specifying key dimensions such as structure, atomization, ambiguity, certainty, integrity, consistency and verifiability. This set of specifications ensures the clarity of system engineering at the requirement stage and improves the accuracy and efficiency of the design. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:
[0037] Figure 1 It is a flowchart of the modeling specification method for MBSE requirement model quality of the present invention;
[0038] Figure 2 The figure is a schematic diagram of the steps of the demand modeling specification method in an embodiment of the present invention. DETAILED DESCRIPTION
[0039] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.
[0040] The present invention takes the access control system as a specific embodiment and provides a modeling specification method for MBSE requirement model quality. Figure 1 and Figure 2 As shown, the method comprises the following steps:
[0041] S1: Use SysML for requirements modeling, structural specifications for requirements modeling, and ensure that related requirements are combined to form a more orderly and coordinated system;
[0042] Specifically, the step S1 includes the following steps:
[0043] S11: Divide the demand level into four levels: customer demand, product demand, subsystem demand, and component demand;
[0044] The subsystem requirements are divided into the exit button subsystem requirements, the magnetic lock subsystem requirements, the power subsystem requirements and the access control machine subsystem requirements. The component requirements can also be similarly divided according to the different parts of the system.
[0045] S12: Use reasonable naming conventions to help quickly identify the nature and level of requirements and the relationship between requirements;
[0046] Among them, the number prefix of customer requirements is set to CR (Customer Requirements), the prefix of product requirements is set to PR (Product Requirements), the prefix of subsystem requirements is set to SR (Subsystem Requirements), and the prefix of component requirements is set to COMR (Component Requirements).
[0047] S13: Use “links” in the requirement diagram to manage the structure of the requirement tree;
[0048] Use demand relationships such as derivation, satisfaction, tracking, and refinement to show how demands are derived from upper-level demands and how they are passed to lower-level demands, so as to avoid the formation of a complex network structure.
[0049] S2: Atomization specification for demand modeling to ensure that each demand avoids redundancy and duplication;
[0050] If necessary, the requirement can be decomposed into two separate and more specific requirements.
[0051] S3: Reduce ambiguity in the model and conduct in-depth analysis of its semantics to avoid potential ambiguity;
[0052] Specifically, step S3 includes the following steps:
[0053] S31: Subdivide some ambiguous requirements at the same level into multiple related specific requirements through refinement relationships;
[0054] S32: Develop and follow a set of modeling guidelines or standards to partially structure the text, using consistent modeling conventions, including but not limited to:
[0055] Use positive expressions and avoid passive and negative expressions;
[0056] Set specific requirement definition items, including elements, execution conditions, execution characteristics, execution constraints, execution objects, object expressions, execution descriptions, etc.
[0057] In this embodiment, as shown in Table 1 below, the security verification process is defined as the access control system requires checking key personal information points in the security verification process, and the attached identity recognition function is completed within 3 seconds, and the goal of allowing or prohibiting users from passing through the access control is achieved.
[0058]
[0059] Table 1
[0060] The use of quantitative indicators ensures that design and evaluation have clear benchmarks and can be verified and evaluated objectively and quantitatively.
[0061] When quantitative expression is not possible, appropriate attributes such as user feedback and qualitative characteristics are used to accurately explain the specific content of the needs.
[0062] S4: Deterministic specification for requirements modeling, focusing on the correct recording, internal consistency and completeness of requirements for product functions, performance and attributes, making them clear and concise;
[0063] S5: Completeness specification for demand modeling, check the sufficiency of all upper-level demands from the perspective of current-level demands, that is, check whether the current-level demands are sufficient to satisfy the upper-level demands, and check the necessity of all downwardly allocated demands from the perspective of current-level demands, that is, check whether all current-level demands are satisfied by the lower-level demands;
[0064] Specifically, step S5 includes the following steps:
[0065] S51: Establish a demand traceability matrix to trace the relationship between upper-level requirements and current-level requirements, and between current-level requirements and lower-level requirements;
[0066] S52: Use the big model to generate contextualized predictions for the missing parts in the requirements, and analyze possible information missing and incompleteness based on the most likely alternative words predicted by the big model.
[0067] S6: Consistency specification for requirements modeling, identifying any possible requirements conflicts and ensuring that there are no contradictory requirements in the entire requirements specification;
[0068] Specifically, step S6 includes the following steps:
[0069] S61: Use formal analysis tools to automatically detect logical conflicts in requirement descriptions;
[0070] S62: Perform attribute filtering to focus on similar or related requirements, and analyze these filtered requirement sets to ensure that there are no conflicts between requirements of the same type;
[0071] S63: Ensure that there are no two or more conflicting requirements, such as opposing functional descriptions, existing at the same time;
[0072] S64: Compare different versions of requirement documents, track changes in requirements over time, and ensure that any changes meet consistency requirements;
[0073] S65: Ensure that changes in requirements can be tracked in a timely manner by establishing traceability links between requirements and between requirements and design, implementation, and verification, thereby identifying changes that conflict with existing requirements.
[0074] S7: Specification for the verifiability of requirement modeling. The verifiability of requirements means that the requirements can be verified through some method or process to confirm whether they are implemented correctly.
[0075] Specifically, the so-called "verifiability" includes all the requirements of certainty, completeness and consistency through steps S4, S5 and S6, including the following steps:
[0076] S71: Establish verifiability criteria for requirements. Define a clear verification criterion for each requirement, that is, how and under what conditions the requirement is considered met. This may include specific test cases, review criteria, or other evaluation methods.
[0077] S72: Consider the constraints on implementing requirements and review whether the requirements can be implemented within the given cost, time, technical capabilities, and regulatory compliance. If necessary, adjust the requirements to adapt to actual project conditions.
[0078] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.
Claims
1. A modeling specification method for MBSE requirement model quality, characterized by: The method comprises the following steps: Use SysML for requirements modeling, structural specifications for requirements modeling, and ensure that related requirements are combined to form a more orderly and coordinated system; Atomic specification for demand modeling to ensure that each demand avoids redundancy and duplication; Reduce ambiguity in the model and conduct in-depth analysis of its semantics to avoid potential ambiguities; Deterministic specifications for requirements modeling, focusing on the correct recording, internal consistency, and completeness of requirements for product functions, performance, and attributes, making them clear and concise; The completeness specification of demand modeling is to check the sufficiency of all upper-level demands from the perspective of current-level demands, that is, to check whether the current-level demands are sufficient to satisfy the upper-level demands; and to check the necessity of all downwardly allocated demands from the perspective of current-level demands, that is, to check whether all current-level demands are satisfied by the lower-level demands. Model the requirements consistently, identify any possible conflicts in requirements, and ensure that there are no contradictory requirements throughout the requirements specification; The specification of the verifiability of requirement modeling. The verifiability of requirements means that the requirements can be verified through some method or process to confirm whether they are implemented correctly.
2. The modeling specification method for MBSE requirement model quality according to claim 1 is characterized in that: The steps of using SysML for requirements modeling and structural specification of requirements modeling to ensure that related requirements are combined together to form a more orderly and coordinated system include: Divide the demand level into four levels: customer demand, product demand, subsystem demand, and component demand; Use reasonable naming conventions to help quickly identify the nature and level of requirements and the relationship between requirements; Use "links" in the requirement diagram to manage the structure of the requirement tree.
3. The modeling specification method for MBSE requirement model quality according to claim 1 is characterized in that: The steps of reducing ambiguity in the model and conducting in-depth analysis of its semantics to avoid potential ambiguity specifically include: Through refinement relationships, some ambiguous requirements at the same level are subdivided into multiple related specific requirements; Develop and follow a set of modeling guidelines or standards to partially structure the text and use consistent modeling conventions; The use of quantitative indicators ensures that design and evaluation have clear benchmarks and can be verified and evaluated objectively and quantitatively. When quantitative expression is not possible, appropriate attributes such as user feedback and qualitative characteristics are used to accurately explain the specific content of the needs.
4. The modeling specification method for MBSE requirement model quality according to claim 1 is characterized in that: The completeness specification of demand modeling includes the steps of checking the sufficiency of all upper-layer demands from the perspective of current-layer demands, i.e., checking whether the current-layer demands are sufficient to satisfy the upper-layer demands, and checking the necessity of all downwardly allocated demands from the perspective of current-layer demands, i.e., checking whether all current-layer demands are satisfied by the lower-layer demands, specifically including: Establish a demand traceability matrix to track the relationship between upper-level requirements and current-level requirements, and current-level requirements and lower-level requirements; Use the big model to generate contextualized predictions for the gaps in the requirements, and analyze possible missing and incomplete information based on the most likely alternatives predicted by the big model.
5. The modeling specification method for MBSE requirement model quality according to claim 1 is characterized in that: The consistency specification of requirement modeling identifies any possible requirement conflicts and ensures that there are no contradictory requirements in the entire requirement specification, including: Use formal analysis tools to automatically detect logical conflicts in requirement descriptions; Filter by attributes to focus on similar or related requirements, and analyze these filtered requirements to ensure that there are no conflicts between requirements of the same type; Make sure there are not two or more conflicting requirements; Compare different versions of requirement documents, track changes in requirements over time, and ensure that any changes meet consistency requirements; By establishing traceability links between requirements and between them and design, implementation, and verification, changes in requirements can be tracked in a timely manner, thereby identifying changes that conflict with existing requirements.
6. The modeling specification method for MBSE requirement model quality according to claim 1 is characterized in that: The specification of the verifiability of requirement modeling, the verifiability of requirements refers to the steps that requirements can be verified through a certain method or process to confirm whether they are correctly implemented, specifically including: Establish verifiability criteria for requirements and define a clear verification criterion for each requirement; Consider the constraints on implementing requirements, review whether the requirements can be implemented within a given cost, time, technical capabilities, and regulatory compliance, and adjust the requirements if necessary to adapt to actual project conditions.
