Device for supporting complex system demand integrity modeling and evaluation

Abstract

The invention discloses a device for supporting complex system demand integrity modeling and evaluation, and relates to the technical field of system engineering, and the device comprises demand modeling, demand integrity evaluation, design process modeling, demand and design process ontology integration, and demand traceability expression and evaluation. The demand modeling module comprises demand entry model construction and demand content constraint definition; the main function of the demand modeling module is to create a demand model based on the proposed demand integrity expression rule and constraint, and ensure the integrity of demand content in the created demand model; in the demand modeling module, a demand content constraint definition sub-module provides constraints for a demand entry model construction sub-module, and in the demand modeling module, a demand engineer uses an entry model construction technology to decompose high-level demands into specific and operable entries, so that deep understanding of the demands is promoted, and the demand modeling efficiency is improved. And each demand is ensured to be accurately defined and recorded.

Description

Technical Field

[0001] The invention belongs to the technical field of system engineering, and in particular relates to a device supporting complex system requirement integrity modeling and evaluation. Background Art

[0002] In the field of software development and system engineering, especially when it comes to complex systems, the core of requirements management is to ensure that the requirements of all stakeholders are correctly understood, recorded and implemented. However, with the increasing complexity of the system, the requirements management process faces many challenges. It is difficult for traditional requirements management systems to effectively track the change history of each requirement. Requirements engineering methods often focus on the collection and analysis of requirements, while ignoring the dynamic changes and interdependencies of requirements throughout the system development life cycle. In addition, existing tools are insufficient in dealing with the mapping relationship between requirements and designs, resulting in the lack of requirements traceability, making it difficult to track the implementation and changes of requirements during the system development and maintenance stages. Therefore, we propose a device that supports the modeling and evaluation of complex system requirements integrity. Summary of the invention

[0003] The purpose of the present invention is to provide a device that supports modeling and evaluation of the integrity of complex system requirements. In the requirement modeling module, the requirement engineer uses the itemized model building technology to decompose high-level requirements into more specific and operational items, thereby solving the problem that the existing requirement management methods are difficult to effectively track the change history of each requirement. The requirement engineering method often focuses on the collection and analysis of requirements, but ignores the dynamic changes and interdependencies of requirements throughout the system development life cycle.

[0004] In order to solve the above technical problems, the present invention is achieved through the following technical solutions:

[0005] The present invention is a device that supports modeling and evaluation of complex system requirements integrity, including requirements modeling, requirements integrity evaluation, design process modeling, requirements and design process ontology integration, and requirements traceability expression and evaluation;

[0006] The requirement modeling module includes the construction of the requirement itemization model and the definition of requirement content constraints; the main function of the requirement modeling module is to realize the creation of the requirement model based on the proposed requirement integrity expression rules and constraints, and to ensure the integrity of the requirement content in the created requirement model; in the requirement modeling module, the requirement content constraint definition submodule provides constraints to the requirement itemization model construction submodule, and since the two are highly coupled, they are designed as a plug-in in the subsequent design; in order to realize the creation of the requirement model that meets the proposed requirement integrity criteria and constraints, in the Eclipse modeling framework and jdk1.8 environment, first, the requirement attribute content creation interface in the Eclipse ProR open source project is obtained, and secondly, based on the proposed requirement integrity expression criteria and constraints, the interface is redesigned to support the creation of the requirement model based on the proposed requirement integrity expression criteria and constraints. Finally, the interface development is implemented based on the Eclipse RCP framework and Java programming language, and the interface and ProR project are packaged into a demand modeling plug-in and integrated with the demand modeling and evaluation system; the demand itemization model construction is responsible for supporting the demand engineer to perform itemization modeling of the demand according to the proposed demand integrity expression criteria; the demand content constraint definition is responsible for supporting the demand engineer to perform structural constraints on the demand content in the process of demand model creation according to the defined demand constraints, so as to ensure the integrity of the demand content in the demand modeling process;

[0007] The requirement integrity assessment module includes external requirement model integration and requirement integrity assessment; the main function of the requirement integrity assessment module is to evaluate the integrity of the requirement content in the integrated external requirement model to ensure the integrity of the requirement content in the integrated external requirement model; in the requirement integrity assessment module, the external requirement model integration submodule realizes the reading of external requirement model information in three formats of word, csv and reqif through the interface; then it is integrated into the requirement model of the requirement itemization model construction submodule through the interface, and the requirement integrity assessment submodule realizes the reading of the attribute content information of the requirement model in the requirement itemization model construction submodule through the interface, and then evaluates the integrity of the external integrated requirement content; the external requirement model integration is responsible for supporting the requirement engineer to integrate the external requirement model; the requirement modeling and assessment system supports the integration of requirement models in word (.docx), csv and reqif formats. In order to realize the integration of external requirement models in word, csv and reqif formats, in the Eclipse modeling framework and jdk1.8 environment, first of all, it is necessary to design and develop an interface for reading requirement model information in word (.docx), csv and reqif formats.Based on the Java library Apache POI, an interface for reading the demand model information in word (.docx) format is designed; based on the Java library OpenCSV, an interface for reading the demand model information in csv format is designed; the demand model in reqif format can be directly integrated without further design and development. Then, it is necessary to design and develop an interface for generating the demand model. Since the underlying format of the demand model is XML format, the Java third-party library dom4j is a feature-rich, flexible and easy-to-use Java XML library, which is suitable for various XML document processing requirements, including parsing, creation, operation and query, etc. Therefore, dom4j is used to design and develop an interface for generating the demand model. Finally, these interfaces are developed based on the Eclipse RCP framework and Java programming language, and packaged into the form of an external demand model integration plug-in, which is integrated with the demand modeling and evaluation system. The demand integrity assessment is responsible for supporting the demand engineer to evaluate the integrity of the demand content in the integrated external demand model. In order to realize the integrity assessment of the demand attribute content in the demand model, in the Eclipse modeling framework and jdk1.8 environment, first, the Java third-party library dom4j is used to design and develop an interface for reading the attribute content information of the demand model in XML data format. Secondly, Stanford The Java interface of CoreNLP is used to analyze and process the requirement attribute content text in the requirement model. Then, the requirement integrity evaluation function and interface are designed and developed. For the requirement attribute content text after analysis and processing, the proposed requirement integrity constraint is constructed using regular expressions. The requirement attribute content after analysis and processing is matched with the evaluation criteria and the matching results are output. Then, the evaluation result visualization function is designed and developed based on SWT to analyze the matching results and highlight and visualize the requirement content that does not meet the integrity evaluation criteria. Then, the evaluation result output function is designed and developed based on SWT to output the requirement integrity evaluation results on the console. Finally, the development of these interfaces and functional modules is implemented based on the Eclipse RCP framework and the Java programming language, and they are packaged into the form of a requirement integrity evaluation plug-in and integrated with the requirement modeling and evaluation system.

[0008] The design process model modeling module includes the construction of design process metamodel and design process model; the main function of the design process modeling module is to support the unified construction of design process models in different fields and at different levels; in the design process modeling module, the design process model creation submodule reads the metamodel information in the design process metamodel creation submodule through the interface; the design process modeling tool supports the graphical construction of system design process metamodel and model based on the KARMA modeling language; first, design and construct attribute metamodel, object metamodel, point metamodel, role metamodel, relationship metamodel, and graph metamodel, including defining the metamodel name and related description, specifying the fixed syntax of the metamodel, that is, the specific Style, including graphic shape, display text description, color, etc.; finally, set the metamodel connection rules through configuration, including "inclusion", "attribute connection", "binding", "association", etc., to complete the design process metamodel construction; after completing the construction of the design process metamodel library, you can use each metamodel to build the model. First, use the graph metamodel to create a graph model in the tool. Open the graph metamodel to see the modeling canvas, and drag the object and relationship metamodel on the right side of the canvas to complete the model construction; the design process metamodel creation is responsible for supporting system engineers to build metamodels based on existing modeling languages, or to create metamodels based on domain characteristics; the design process model creation is responsible for supporting system engineers to use metamodels to build models;

[0009] The requirement and design process ontology integration module includes model-to-ontology mapping, ontology-to-model mapping and ontology visualization; the main function of the requirement and design process ontology integration module is to achieve semantically consistent expression of the requirement model and the design process model, thereby laying the foundation for the creation of traceability relationships between heterogeneous requirement models and design process models; in the requirement and design process ontology integration module, the ontology-to-model mapping submodule reads external integrated ontology information through an interface, and then generates the requirement model in the requirement itemization model construction submodule, the design process metamodel in the design process metamodel creation submodule, the design process model in the design process model creation submodule, and the traceability relationship model in the requirement traceability relationship creation submodule through the interface; the model-to-ontology mapping submodule reads the requirement model in the requirement itemization model construction submodule, the design process metamodel in the design process metamodel creation submodule, the design process model in the design process model creation submodule, and the traceability relationship in the requirement traceability relationship creation submodule through the interface to generate an integrated ontology, and the ontology visualization submodule generates an integrated ontology through the interface. Read the integrated ontology information and display it visually; the model-to-ontology mapping is responsible for supporting the mapping of the requirement model and the design process model into an integrated ontology, and realizing the semantically consistent expression of the requirement model and the design process model; in order to realize the mapping of the requirement model, the design process model and the traceability relationship between the two into an integrated ontology, first of all, an interface that can read the requirement model, the design process model and the traceability relationship between the two is required; secondly, an interface for generating the ontology is required. The design process modeling tool provides an interface for reading the design process metamodel and model. For the interface for reading the requirement model and the traceability relationship, this paper uses the Java third-party library dom4j to design and develop interfaces for reading the requirement model and the traceability relationship in XML data format. For the ontology generation interface, Jena is a set of Java third-party libraries for supporting RDF / RDFS and OWL, which provides a large number of OWL format file reading and generation interfaces, and can easily access and operate the classes, instances and attributes in OWL. Therefore, this paper uses Jena to design and develop interfaces for generating integrated ontology. Finally, these interfaces are developed based on the Eclipse RCP framework and Java programming language, and packaged into a model-to-ontology mapping plug-in for integration with the requirements modeling and evaluation system; the ontology-to-model mapping is responsible for supporting the conversion of the integrated ontology mapping of requirements and design processes into the requirements model and design process model to ensure the consistency of the model; in order to realize the conversion of the integrated ontology mapping into the requirements model, design process model and the traceability relationship between the two in the requirements modeling and evaluation system, first, an interface for reading the ontology is required, and secondly, an interface that can generate the requirements model, design process model and the traceability relationship between the two is required. For the ontology reading interface, Jena is used to design and develop an interface for reading the integrated ontology.In order to generate the interface of the demand model and the traceability relationship, dom4j is used to design and develop the interface of the demand model and the traceability relationship in XML data format. The design process modeling tool provides the interface for generating the design process metamodel and model. Finally, the development of these interfaces is realized based on the Eclipse RCP framework and Java programming language, and the interface is packaged in the form of a body-to-model mapping plug-in, which is integrated with the demand modeling and evaluation system; the ontology visualization is responsible for supporting the visualization of the graph of the requirements, design process elements and the relationship between the two, so that designers can clearly understand the traceability relationship between the requirements and the design process; in order to more intuitively and clearly display the traceability relationship between the demand model and the design process model, an ontology visualization plug-in is developed to support the visualization of the traceability relationship. First, the ontology reading interface developed in the ontology-to-model mapping plug-in is called to read the traceability relationship information of the demand model and the design process model in the ontology; then, the ontology visualization graph plug-in is designed and developed based on the ElipseZest plug-in; finally, the development of these interfaces is realized based on the Eclipse RCP framework and Java programming language, and the interface is packaged in the form of a body visualization plug-in, which is integrated with the demand modeling and evaluation system;.

[0010] The requirement traceability expression and evaluation module includes requirement traceability relationship construction and requirement traceability evaluation; the main function of the requirement traceability expression and evaluation module is to support the construction of the traceability relationship between requirements and design process and the evaluation of requirement traceability; in the requirement traceability expression and evaluation module, the requirement traceability relationship construction submodule reads the requirement model information of the requirement itemization model construction submodule through the interface, and reads the design process model information in the design process model construction submodule through the interface; the requirement traceability evaluation submodule reads the integrated ontology information through the interface to perform requirement traceability evaluation; the requirement traceability relationship construction is responsible for supporting the construction of the traceability relationship between requirements and design process based on the integrated ontology of requirements and design process, or in the system The traceability relationship between the requirement model and the design process model is constructed in the integrated ontology, and mapped to the traceability relationship between the requirement and the design process in the integrated ontology; in order to realize the construction of the traceability relationship between the requirement model and the design process model, first of all, it is necessary to be able to read the requirement model and design process model interfaces. For reading the requirement model interface, the underlying data format of the requirement model is XML. Therefore, this paper uses the Java third-party library dom4j to design and develop an interface for reading the requirement model in XML data format; for reading the design process model interface, the design process modeling tool itself provides a design process metamodel and model reading interface in Java data format, which can support the reading of the design process model and metamodel. Secondly, it is necessary to generate an interface for the traceability relationship model. Since the underlying storage format of the traceability relationship model is also in XML data format, dom4j is also used to design and develop the interface of the traceability relationship model in XML data format. Finally, the development of these interfaces is implemented based on the Eclipse RCP framework and Java programming language, and they are packaged into the form of a requirement traceability relationship construction plug-in, which is integrated with the requirement modeling and evaluation system; the requirement traceability evaluation is responsible for supporting the requirement engineer to evaluate the requirement traceability based on the integrated ontology; in order to realize the evaluation of requirement traceability based on the integrated ontology, first of all, it is necessary to be able to read the interface of the integrated ontology. In the requirement and design process ontology integration module, the interface for reading the integrated ontology has been designed and developed based on Jena, which can be called here. At the same time, Jena supports processing RDF data, executing SPARQL queries, etc. Therefore, this paper uses Jena to design a requirement traceability evaluation interface based on SPARQL. Finally, the development of these interfaces is implemented based on the Eclipse RCP framework and Java programming language, and they are packaged into the form of a requirement traceability evaluation plug-in, which is integrated with the requirement modeling and evaluation system.

[0011] As a preferred technical solution, the demand modeling and evaluation system includes four layers: data layer, core driver layer, business logic layer and user interface layer; the data layer represents the specific data form of modeling, conversion and evaluation involved in the demand modeling and evaluation system, and is driven by the core driver layer to provide underlying data support for the implementation of business logic, including the following five types: XML data: used to store demand models and traceability relationship models, and supports mutual conversion with OWL data and JAVA data; JAVA data: used to store and process information within the system to support the functions and logic of the system; JAVA data supports interaction with XML data, such as using the JAVA library DOM to access XML data. L documents can be read and operated; at the same time, JAVA data supports interaction with OWL data, such as parsing and processing OWL ontology through the JAVA library Jena; KARMA data: used to store design process metamodels and models, and supports mutual conversion with OWL data; graphical model data: used to store data of the design process model in the canvas, including layout, objects, relationships, etc., and supports mutual conversion with KARMA data; OWL data: used to store data information of integrated ontology, and can support related functions related to ontology, such as semantic query and reasoning, etc.; supports mutual conversion with XML data, JAVA data, KARMA data and graphical model data.

[0012] As a preferred technical solution, the core driver layer is a key part of the system, which directly interacts with the data layer and is responsible for implementing the business logic and functions of the system. By calling the data services provided by the data layer, the data is processed and analyzed, and corresponding operations are performed according to business needs; the core driver layer includes the following eight core driver engines: ProR core engine: supports parsing and generation of ReqIF requirement models in XML format; requirement expression constraint engine: supports structural constraints on requirement content based on the proposed requirement integrity expression constraints; CoreNLP engine: supports processing natural language requirement texts, including word segmentation, part-of-speech tagging, named entity recognition, syntactic analysis, reference resolution and other tasks; regular expression matching engine: supports regular expression matching of natural language processing results output by the CoreNLP engine based on the proposed requirement integrity assessment criteria; metamodel interpretation engine: supports parsing of meta-metamodels based on graphs, objects, points, attributes, relationships, roles and their conventions The system design process metamodel developed by the bundle is read through the engine, and it is interpreted as the KARMA backend data structure to realize the generation of the metamodel library; Model interpretation engine: supports the parsing of the design process model built based on the design process metamodel. The design process model is read through the engine and is interpreted as the KARMA backend data structure, and it also supports the conversion with the graph model data; Traceability engine: supports the acquisition of requirement model and design process model data, and the establishment of the traceability relationship between the requirement model and the design process model; Ontology engine: parses and processes OWL ontology based on the JAVA library Jena, supports the mutual conversion between XML data, KARMA data, graph model data and OWL ontology data, and supports query reasoning based on OWL data, as well as the visualization of OWL data.

[0013] As a preferred technical solution, the business logic layer represents the specific operations that the demand modeling and evaluation system allows users to complete. It is driven by the core driver layer and participates in the implementation of business-level functions. The business logic layer includes the following eleven functions: Demand entry model construction: supports the construction of demand entry models based on demand integrity expression rules; demand content constraint definition: supports structural constraints on demand content in the process of building demand models based on demand integrity expression constraints; external demand model integration: supports the integration of external word (.docx), csv, and reqif format demand models; demand integrity assessment: the system has built-in demand integrity assessment criteria, supports users to assess the integrity of demand content in external integrated demand models, outputs demand integrity assessment results, and highlights demand content that does not meet integrity rules; design process metamodel creation: supports the construction of meta-metamodels and constraints based on graphs, objects, points, attributes, relationships, roles, etc. Build a design process metamodel; Design process model creation: Based on the design process metamodel, users are supported to build a design process model by dragging or configuring; Model to ontology mapping: After the requirement model, design process model and the traceability relationship between the two are created, users are supported to convert the graphical model data into OWL ontology data; Ontology to model mapping: Users are supported to read the integrated ontology, convert the OWL ontology data into graphical model data, and complete the creation of the requirement, design process model and the traceability relationship between the two; Ontology visualization: Supports visual display of OWL ontology data in the form of a graph; Requirement traceability relationship construction: Supports obtaining requirement model and design process model information, and building a traceability relationship between the two; or supports building a traceability relationship between the two through the integrated ontology of requirements and design processes; Requirement traceability evaluation: Supports executing the corresponding traceability evaluation based on the proposed requirement traceability evaluation criteria, and outputs the requirement traceability evaluation results.

[0014] As a preferred technical solution, the user interface layer represents the specific applications provided by the demand modeling and evaluation system for designers by combining the specific functions of the business logic layer. The user interface layer includes the following five applications: demand modeling: supporting the construction of a demand entry model based on demand integrity rules and constraints to achieve complete expression of demand content; demand integrity evaluation: supporting the evaluation of the integrity of demand attribute content in the demand model based on the proposed demand integrity evaluation criteria; design process modeling: supporting the construction of design process metamodels and models based on graphs, objects, points, attributes, relationships, role metamodels and their constraints; demand and design process ontology integration: supporting the mutual conversion between demand models, system design process models, and the traceability relationship between the two and the integrated ontology, achieving semantic consistency between the demand model and the design process model, and supporting the semantic expression of demand traceability; at the same time, supporting integrated ontology visualization, clearly showing the traceability relationship between the demand model and the design process model; demand traceability expression and evaluation: supporting the construction of traceability relationship between the demand model and the design process model; for the integrated ontology, based on the defined demand traceability evaluation criteria, perform demand traceability evaluation and output the evaluation results.

[0015] The present invention has the following beneficial effects:

[0016] In the requirement modeling module of the present invention, the requirement engineer uses the itemized model building technology to decompose the high-level requirements into more specific and operational items. This method promotes a deep understanding of the requirements and ensures that each requirement is accurately defined and recorded. At the same time, the requirement content constraint definition provides a mechanism for the requirement engineer to ensure that all relevant business rules and constraints are considered in the modeling process, such as the consistency, unambiguity, testability and feasibility of the requirements. These constraints help reduce errors and omissions in the requirement model, thereby improving the accuracy and completeness of the requirement model.

[0017] The requirement integrity assessment module of the present invention allows requirement engineers to systematically assess the integrated external requirement model to verify its integrity, which includes checking whether all aspects of the requirements are covered and whether there are contradictions or duplications between them. This process ensures that all requirements remain consistent throughout the project life cycle and are consistent with business goals and customer needs. At the same time, the requirement traceability expression and assessment module provides powerful tools to establish and maintain traceability from original requirements to design, implementation and testing.

[0018] The metamodel of the present invention is an abstract model that defines the structure, rules and constraints that the design process should follow. This abstract layer makes the design process more standardized and reduces the possibility of design deviation. The requirement and design process ontology integration module realizes the semantic consistency between the requirement model and the design process model through ontology technology. Ontology, as a form of knowledge representation, provides a shared vocabulary and conceptual framework so that the relationship between requirements and design can be clearly expressed and understood.

[0019] Of course, any product implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for describing the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.

[0021] Figure 1 A functional architecture diagram of a device supporting complex system requirement integrity modeling and evaluation according to the present invention;

[0022] Figure 2 It is a specific architecture diagram of the data layer, core driver layer, business logic layer and user interface layer of the present invention;

[0023] Figure 3 It is a diagram of the interface interaction relationship between the modules of the present invention;

[0024] Figure 4 It is a timing diagram of the execution process of each module of the present invention;

[0025] Figure 5 A Chinese diagram of the front-end interface of the demand modeling plug-in of the present invention;

[0026] Figure 6 The English diagram of the front-end interface of the demand modeling plug-in of the present invention;

[0027] Figure 7 It is the front-end interface of the plug-in integrated with the external demand model in csv format of the present invention;

[0028] Figure 8 It is the front-end interface of the plug-in integrated with the external demand model in word format of the present invention;

[0029] Fig. 9 This is a Chinese picture of the front-end interface of the demand integrity assessment plug-in of the present invention;

[0030] Fig.10 This is an English diagram of the front-end interface of the requirement integrity assessment plug-in of the present invention;

[0031] Fig.11 Designing an interface for the metamodel of the present invention;

[0032] Fig.12 Constructing an interface for the model of the present invention;

[0033] Fig.13 It is the front-end interface of the model-to-ontology mapping plug-in of the present invention;

[0034] Fig.14 It is the front-end interface of the ontology-to-model mapping plug-in of the present invention;

[0035] Fig.15 It is the front-end interface of the ontology visualization plug-in of the present invention;

[0036] Fig.16 Constructing a plug-in front-end interface for the traceability relationship of the present invention;

[0037] Fig.17 It is the front-end interface of the requirement traceability assessment plug-in of the present invention. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0039] See also Figure 1 As shown, the present invention is a device that supports modeling and evaluation of complex system requirements integrity, including requirements modeling, requirements integrity evaluation, design process modeling, requirements and design process ontology integration, requirements traceability expression and evaluation;

[0040] The requirement modeling module includes the construction of the requirement itemization model and the definition of requirement content constraints; the main function of the requirement modeling module is to realize the creation of the requirement model based on the proposed requirement integrity expression rules and constraints, and to ensure the integrity of the requirement content in the created requirement model; in the requirement modeling module, the requirement content constraint definition submodule provides constraints to the requirement itemization model construction submodule. Since the two are highly coupled, they are designed as a plug-in in the subsequent design; in order to realize the creation of the requirement model that meets the proposed requirement integrity criteria and constraints, in the Eclipse modeling framework and jdk1.8 environment, first, the requirement attribute content creation interface in the Eclipse ProR open source project is obtained, and secondly, based on the proposed requirement integrity expression criteria and constraints, the interface is redesigned to support the creation of the requirement model based on the proposed requirement integrity expression criteria and constraints, and finally, based on Eclipse The RCP framework and Java programming language are used to implement the development of the interface, and the interface and the ProR project are packaged into a demand modeling plug-in to be integrated with the demand modeling and evaluation system; the demand itemization model construction is responsible for supporting the demand engineers to carry out itemization modeling of the demand according to the proposed demand integrity expression criteria; the demand content constraint definition is responsible for supporting the demand engineers to structurally constrain the demand content in the process of demand model creation according to the defined demand constraints, so as to ensure the integrity of the demand content in the demand modeling process;

[0041] The requirement integrity assessment module includes external requirement model integration and requirement integrity assessment; the main function of the requirement integrity assessment module is to evaluate the integrity of the requirement content in the integrated external requirement model to ensure the integrity of the requirement content in the integrated external requirement model; in the requirement integrity assessment module, the external requirement model integration submodule uses an interface to read the external requirement model information in three formats: word, csv, and reqif; then it is integrated into the requirement model of the requirement itemization model construction submodule through an interface, and the requirement integrity assessment submodule uses an interface to read the attribute content information of the requirement model in the requirement itemization model construction submodule, and then evaluates the integrity of the external integrated requirement content; the external requirement model integration is responsible for supporting the requirement engineer to integrate the external requirement model; the requirement modeling and assessment system supports the integration of requirement models in word (.docx), csv, and reqif formats. In order to realize the integration of external requirement models in word, csv, and reqif formats, in the Eclipse modeling framework and jdk1.8 environment, first of all, it is necessary to design and develop an interface to read the requirement model information in word (.docx), csv, and reqif formats.Based on the Java library Apache POI, an interface for reading the demand model information in word (.docx) format is designed; based on the Java library OpenCSV, an interface for reading the demand model information in csv format is designed; the demand model in reqif format can be directly integrated without further design and development. Then, it is necessary to design and develop an interface for generating the demand model. Since the underlying format of the demand model is XML format, the Java third-party library dom4j is a feature-rich, flexible and easy-to-use Java XML library, which is suitable for various XML document processing requirements, including parsing, creation, operation and query, etc. Therefore, dom4j is used to design and develop an interface for generating the demand model. Finally, these interfaces are developed based on the Eclipse RCP framework and Java programming language, and packaged into the form of an external demand model integration plug-in, which is integrated with the demand modeling and evaluation system. The demand integrity assessment is responsible for supporting the demand engineer to evaluate the integrity of the demand content in the integrated external demand model. In order to realize the integrity assessment of the demand attribute content in the demand model, in the Eclipse modeling framework and jdk1.8 environment, first, the Java third-party library dom4j is used to design and develop an interface for reading the attribute content information of the demand model in XML data format. Secondly, Stanford The Java interface of CoreNLP is used to analyze and process the requirement attribute content text in the requirement model. Then, the requirement integrity evaluation function and interface are designed and developed. For the requirement attribute content text after analysis and processing, the proposed requirement integrity constraint is constructed using regular expressions. The requirement attribute content after analysis and processing is matched with the evaluation criteria and the matching results are output. Then, the evaluation result visualization function is designed and developed based on SWT to analyze the matching results and highlight and visualize the requirement content that does not meet the integrity evaluation criteria. Then, the evaluation result output function is designed and developed based on SWT to output the requirement integrity evaluation results on the console. Finally, the development of these interfaces and functional modules is implemented based on the Eclipse RCP framework and the Java programming language, and they are packaged into the form of a requirement integrity evaluation plug-in and integrated with the requirement modeling and evaluation system.

[0042] The design process model modeling module includes the construction of design process metamodel and design process model; the main function of the design process modeling module is to support the unified construction of design process models in different fields and at different levels; in the design process modeling module, the design process model creation submodule reads the metamodel information in the design process metamodel creation submodule through the interface; the design process modeling tool supports the graphical construction of system design process metamodel and model based on the KARMA modeling language; first, design and construct attribute metamodel, object metamodel, point metamodel, role metamodel, relationship metamodel, and graph metamodel, including defining the metamodel name and related description, and specifying the fixed syntax of the metamodel, that is, the specific meaning of the model in the modeling environment. Style, including graphic shape, display text description, color, etc.; finally, set the metamodel connection rules through configuration, including "inclusion", "attribute connection", "binding", "association", etc., to complete the construction of the design process metamodel; after completing the construction of the design process metamodel library, you can use each metamodel to build the model. First, use the graph metamodel to create a graph model in the tool. Open the graph metamodel to see the modeling canvas, and drag the object and relationship metamodel on the right side of the canvas to complete the model construction; the design process metamodel creation is responsible for supporting system engineers to build metamodels based on existing modeling languages, or to create metamodels based on domain characteristics; the design process model creation is responsible for supporting system engineers to use metamodels to build models;

[0043] The requirement and design process ontology integration module includes model-to-ontology mapping, ontology-to-model mapping and ontology visualization; the main function of the requirement and design process ontology integration module is to achieve semantically consistent expression of the requirement model and the design process model, thereby laying the foundation for the creation of traceability relationships between heterogeneous requirement models and design process models; in the requirement and design process ontology integration module, the ontology-to-model mapping submodule reads the external integrated ontology information through the interface, and then generates the requirement model in the requirement itemization model construction submodule, the design process metamodel in the design process metamodel creation submodule, the design process model in the design process model creation submodule, and the traceability relationship model in the requirement traceability relationship creation submodule through the interface; the model-to-ontology mapping submodule reads the requirement model in the requirement itemization model construction submodule, the design process metamodel in the design process metamodel creation submodule, the design process model in the design process model creation submodule, and the traceability relationship in the requirement traceability relationship creation submodule through the interface to generate an integrated ontology, and the ontology visualization submodule reads the external integrated ontology information through the interface, and then generates the requirement model in the requirement itemization model construction submodule, the design process metamodel in the design process metamodel creation submodule, the design process model in the design process model creation submodule, and the traceability relationship in the requirement traceability relationship creation submodule through the interface. Get the integrated ontology information for visual display; model-to-ontology mapping is responsible for supporting the mapping of the requirement model and the design process model into an integrated ontology, and realizing the semantically consistent expression of the requirement model and the design process model; in order to realize the mapping of the requirement model, the design process model and the traceability relationship between the two into an integrated ontology, first of all, it is necessary to be able to read the interface of the requirement model, the design process model and the traceability relationship between the two; secondly, it is necessary to generate the interface of the ontology. The design process modeling tool provides an interface for reading the design process metamodel and model. For the interface for reading the requirement model and the traceability relationship, this paper uses the Java third-party library dom4j to design and develop the interface for reading the requirement model and the traceability relationship in XML data format. For the ontology generation interface, Jena is a set of Java third-party libraries for supporting RDF / RDFS and OWL, which provides a large number of OWL format file reading and generation interfaces, and can easily access and operate the classes, instances and attributes in OWL. Therefore, this paper uses Jena to design and develop the interface for generating the integrated ontology. Finally, these interfaces are developed based on the EclipseRCP framework and Java programming language, and packaged into a model-to-ontology mapping plug-in for integration with the requirements modeling and evaluation system; the ontology-to-model mapping is responsible for supporting the conversion of the integrated ontology mapping of requirements and design processes into the requirements model and design process model to ensure the consistency of the model; in order to realize the conversion of the integrated ontology mapping into the requirements model, design process model and the traceability relationship between the two in the requirements modeling and evaluation system, first, an interface for reading the ontology is required, and secondly, an interface that can generate the requirements model, design process model and the traceability relationship between the two is required. For the ontology reading interface, Jena is used to design and develop an interface for reading the integrated ontology.In order to generate the interface of requirement model and traceability relationship, dom4j is used to design and develop the interface of requirement model and traceability relationship in XML data format. The design process modeling tool provides the interface of generating design process metamodel and model. Finally, the development of these interfaces is realized based on Eclipse RCP framework and Java programming language, and they are packaged in the form of entity to model mapping plug-in, and integrated with the requirement modeling and evaluation system; ontology visualization is responsible for supporting the visualization display of requirements, design process elements and the relationship between them, so that designers can clearly understand the traceability relationship between requirements and design process; in order to more intuitively and clearly display the traceability relationship between requirement model and design process model, ontology visualization plug-in is developed to support the visualization of traceability relationship. First, the ontology reading interface developed in the ontology to model mapping plug-in is called to read the traceability relationship information of requirement model and design process model in ontology; then, the ontology visualization graph plug-in is designed and developed based on Eclipse Zest plug-in; finally, the development of these interfaces is realized based on Eclipse RCP framework and Java programming language, and they are packaged in the form of entity visualization plug-in, and integrated with the requirement modeling and evaluation system;.

[0044] The requirement traceability expression and evaluation module includes the construction of requirement traceability relationship and the evaluation of requirement traceability; the main function of the requirement traceability expression and evaluation module is to support the construction of traceability relationship between requirement and design process and the evaluation of requirement traceability; in the requirement traceability expression and evaluation module, the requirement traceability relationship construction submodule reads the requirement model information of the requirement itemization model construction submodule through the interface, and reads the design process model information in the design process model construction submodule through the interface; the requirement traceability evaluation submodule reads the integrated ontology information through the interface to perform requirement traceability evaluation; the requirement traceability relationship construction is responsible for supporting the construction of traceability relationship between requirement and design process based on the integrated ontology of requirement and design process, or constructing in the system The traceability relationship between the requirement model and the design process model is mapped to the traceability relationship between the requirement and the design process in the integrated ontology; in order to realize the construction of the traceability relationship between the requirement model and the design process model, first of all, it is necessary to be able to read the requirement model and design process model interfaces. For reading the requirement model interface, the underlying data format of the requirement model is XML. Therefore, this paper uses the Java third-party library dom4j to design and develop an interface for reading the requirement model in XML data format; for reading the design process model interface, the design process modeling tool itself provides a design process metamodel and model reading interface in java data format, which can support the reading of the design process model and metamodel. Secondly, it is necessary to generate an interface for the traceability relationship model. Since the underlying storage format of the traceability relationship model is also in XML data format, dom4j is also used to design and develop the interface of the traceability relationship model in XML data format. Finally, the development of these interfaces is implemented based on the Eclipse RCP framework and Java programming language, and they are packaged into the form of a requirement traceability relationship construction plug-in, which is integrated with the requirement modeling and evaluation system; the requirement traceability evaluation is responsible for supporting the requirement engineer to evaluate the requirement traceability based on the integrated ontology; in order to realize the evaluation of requirement traceability based on the integrated ontology, first of all, it is necessary to be able to read the interface of the integrated ontology. In the requirement and design process ontology integration module, the interface for reading the integrated ontology has been designed and developed based on Jena, which can be called here. At the same time, Jena supports processing RDF data, executing SPARQL queries, etc. Therefore, this paper uses Jena to design a requirement traceability evaluation interface based on SPARQL. Finally, the development of these interfaces is implemented based on the Eclipse RCP framework and Java programming language, and they are packaged into the form of a requirement traceability evaluation plug-in, which is integrated with the requirement modeling and evaluation system.The demand modeling and evaluation system includes four layers: data layer, core driver layer, business logic layer and user interface layer; the data layer represents the specific data form of modeling, conversion and evaluation involved in the demand modeling and evaluation system, and is driven by the core driver layer to provide underlying data support for the implementation of business logic, including the following five types: XML data: used to store demand models and traceability relationship models, and supports mutual conversion with OWL data and JAVA data; JAVA data: used to store and process information within the system to support the functions and logic of the system; JAVA data supports interaction with XML data, such as reading and manipulating XML documents through the JAVA library DOM operation; at the same time, JAVA data supports interaction with OWL data, such as parsing and processing OWL ontology through JAVA library Jena; KARMA data: used to store design process metamodels and models, and supports mutual conversion with OWL data; Graphic model data: used to store data of design process models in the canvas, including layout, objects, relationships, etc., and supports mutual conversion with KARMA data; OWL data: used to store data information of integrated ontology, and can support related functions related to ontology, such as semantic query and reasoning, etc.; supports mutual conversion with XML data, JAVA data, KARMA data and graphical model data.

[0045] The core driver layer is the key part of the system. It interacts directly with the data layer and is responsible for implementing the business logic and functions of the system. By calling the data services provided by the data layer, the data is processed and analyzed, and corresponding operations are performed according to business needs. The core driver layer includes the following eight core driver engines: ProR core engine: supports parsing and generation of ReqIF requirement models in XML format; requirement expression constraint engine: supports structural constraints on requirement content based on the proposed requirement integrity expression constraints; CoreNLP engine: supports processing natural language requirement texts, including word segmentation, part-of-speech tagging, named entity recognition, syntactic analysis, reference resolution and other tasks; regular expression matching engine: supports regular expression matching of natural language processing results output by the CoreNLP engine based on the proposed requirement integrity assessment criteria; meta-model interpretation engine: supports parsing of graph-based, object-based, point-based, attribute-based, relationship-based, role-based meta-models and their constraints The system design process metamodel developed is used to read the design metamodel through this engine, and interpret it as the KARMA backend data structure to realize the generation of the metamodel library; Model interpretation engine: supports the parsing of the design process model built based on the design process metamodel, and reads the design process model through this engine, and interprets it as the KARMA backend data structure, and supports the conversion with the graph model data; Traceability engine: supports the acquisition of requirement model and design process model data, and establishes the traceability relationship between the requirement model and the design process model; Ontology engine: parses and processes OWL ontology based on the JAVA library Jena, supports the mutual conversion between XML data, KARMA data and graph model data and OWL ontology data, and supports query reasoning based on OWL data, as well as visualization of OWL data.

[0046] The business logic layer represents the specific operations that the demand modeling and evaluation system allows users to complete. It is driven by the core driver layer and participates in the implementation of business-level functions. The business logic layer includes the following eleven functions: Construction of demand itemization model: supports the construction of demand itemization model based on demand integrity expression rules; Definition of demand content constraints: supports structural constraints on demand content in the process of building demand models based on demand integrity expression constraints; External demand model integration: supports the integration of external word (.docx), csv, and reqif format demand models; Requirement integrity assessment: The system has built-in requirement integrity assessment criteria, supports users to evaluate the integrity of requirement content in external integrated requirement models, outputs requirement integrity assessment results, and highlights requirement content that does not meet integrity rules; Design process metamodel creation: supports the construction of design process metamodels based on graphs, objects, points, attributes, relationships, role metamodels and their constraints. model; Design process model creation: Based on the design process metamodel, users are supported to build the design process model by dragging or configuring; Model to ontology mapping: After the requirement model, design process model and the traceability relationship between the two are created, users are supported to convert the graphical model data into OWL ontology data; Ontology to model mapping: Users are supported to read the integrated ontology, convert the OWL ontology data into graphical model data, and complete the creation of the requirement, design process model and the traceability relationship between the two; Ontology visualization: Supports the visualization of OWL ontology data in the form of a graph; Requirement traceability relationship construction: Supports obtaining the requirement model and design process model information, and building the traceability relationship between the two; or supports building the traceability relationship between the two through the integrated ontology of the requirement and the design process; Requirement traceability evaluation: Supports the execution of the corresponding traceability evaluation based on the proposed requirement traceability evaluation criteria, and outputs the requirement traceability evaluation results.

[0047] The user interface layer represents the specific applications provided by the requirement modeling and evaluation system for designers by combining the specific functions of the business logic layer. The user interface layer includes the following five applications: Requirement modeling: supports the construction of requirement entry models based on requirement integrity rules and constraints to achieve complete expression of requirement content; Requirement integrity evaluation: supports the evaluation of the integrity of requirement attribute content in the requirement model based on the proposed requirement integrity evaluation criteria; Design process modeling: supports the construction of design process metamodels and models based on graphs, objects, points, attributes, relationships, role metamodels and their constraint methods; Requirements and design process ontology integration: supports the conversion between requirement models, system design process models, and the traceability relationship between the two and the integrated ontology, achieves the semantic consistency of the requirement model and the design process model, and supports the semantic expression of requirement traceability; at the same time, supports integrated ontology visualization to clearly display the traceability relationship between the requirement model and the design process model; Requirements traceability expression and evaluation: supports the construction of traceability relationships between the requirement model and the design process model; for the integrated ontology, based on the defined requirement traceability evaluation criteria, performs requirement traceability evaluation and outputs the evaluation results.

[0048] A specific application of this embodiment is: first, the designer integrates the external demand model through the external demand model integration submodule, and conducts integrity assessment on the demand content through the demand integrity assessment submodule, and iteratively modifies the incomplete demand through the demand modeling module; or the designer directly constructs the demand that meets the integrity through the demand modeling module, ensuring that the demand modeling module outputs the demand model that meets the integrity requirements, and then guides the design process metamodel and model construction in the design process model construction module, and then, the demand traceability relationship construction submodule realizes the construction of the traceability relationship between the two by calling the complete demand model in the demand modeling module and the design process model in the design process model construction module, on this basis, the model to ontology mapping module converts the demand modeling module input The complete requirement model, the design process metamodel and model in the design process model construction module, and the traceability relationship mapping in the requirement traceability relationship construction module are converted into an integrated ontology to achieve semantically consistent expression of the requirement model and the design process model, thereby achieving the expression of requirement traceability. Finally, the converted integrated ontology is output to the requirement traceability evaluation submodule to perform requirement traceability evaluation. At the same time, the integrated ontology is output to the ontology visualization submodule for graph visualization. In addition, designers can use the ontology to model mapping submodule to convert the external integrated ontology mapping into the requirement model in the requirement modeling module, the design process metamodel and model in the design process model construction module, and the traceability relationship in the requirement traceability relationship construction module to ensure the consistency of model semantics.

[0049] It is worth noting that in the above system embodiment, the various units included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0050] In addition, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiments can be completed by instructing related hardware through a program, and the corresponding program can be stored in a computer-readable storage medium.

[0051] The preferred embodiments of the present invention disclosed above are only used to help illustrate the present invention. The preferred embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the present invention, so that those skilled in the art can understand and use the present invention well. The present invention is limited only by the claims and their full scope and equivalents.

Claims

1. A device supporting modeling and evaluation of complex system requirements integrity, including requirements modeling, requirements integrity evaluation, design process modeling, requirements and design process ontology integration, requirements traceability expression and evaluation; characterized by: The requirement modeling module includes the construction of the requirement itemization model and the definition of requirement content constraints; the main function of the requirement modeling module is to realize the creation of the requirement model based on the proposed requirement integrity expression rules and constraints, and to ensure the integrity of the requirement content in the created requirement model; in the requirement modeling module, the requirement content constraint definition submodule provides constraints to the requirement itemization model construction submodule. Since the two are highly coupled, they are designed as a plug-in in the subsequent design; in order to realize the creation of the requirement model that meets the proposed requirement integrity criteria and constraints, in the Eclipse modeling framework and jdk1.8 environment, first, obtain the requirement attribute content creation interface in the Eclipse ProR open source project, and secondly, based on the proposed requirement integrity expression criteria and constraints, redesign the interface to support the creation of the requirement model based on the proposed requirement integrity expression criteria and constraints. Finally, the interface is developed based on the Eclipse RCP framework and Java programming language, and the interface and the ProR project are packaged into the form of a requirement modeling plug-in, and integrated with the requirement modeling and evaluation system; The requirement itemization model construction is responsible for supporting the requirement engineer to carry out itemization modeling of the requirement according to the requirement integrity expression criteria; The requirement content constraint definition is responsible for supporting the requirement engineer to perform structural constraints on the requirement content in the requirement model creation process according to the defined requirement constraints, so as to ensure the integrity of the requirement content in the requirement modeling process; The demand integrity assessment module includes external demand model integration and demand integrity assessment; the main function of the demand integrity assessment module is to assess the integrity of the demand content in the integrated external demand model to ensure the integrity of the demand content in the integrated external demand model; In the requirement integrity assessment module, the external requirement model integration submodule uses the interface to read the external requirement model information in three formats: word, csv, and reqif; then it is integrated into the requirement model in the requirement itemization model construction submodule through the interface. The requirement integrity assessment submodule uses the interface to read the attribute content information of the requirement model in the requirement itemization model construction submodule, and then evaluates the integrity of the external integrated requirement content; The external demand model integration is responsible for supporting demand engineers to integrate external demand models; the demand modeling and evaluation system supports the integration of demand models in word (.docx), csv, and reqif formats. In order to realize the integration of external demand models in word, csv, and reqif formats, in the Eclipse modeling framework and jdk1.8 environment, first, it is necessary to design and develop interfaces for reading demand model information in word (.docx), csv, and reqif formats. Based on the Java library Apache POI, an interface for reading demand model information in word (.docx) format is designed; based on the Java library OpenCSV, an interface for reading demand model information in csv format is designed; among them, the reqif format demand model can be directly integrated without further design and development. Then, it is necessary to design and develop an interface for generating demand models. Since the underlying format of the demand model is XML format, the Java third-party library dom4j is a feature-rich, flexible and easy-to-use Java XML library, which is suitable for various XML document processing requirements, including parsing, creation, operation and query, etc. Therefore, dom4j is used to design and develop interfaces for generating demand models. Finally, these interfaces are developed based on the Eclipse RCP framework and Java programming language, and packaged into the form of external demand model integration plug-ins, and integrated with the demand modeling and evaluation system; The requirement integrity assessment is responsible for supporting the requirement engineer to assess the integrity of the requirement content in the integrated external requirement model; in order to implement the integrity assessment of the requirement attribute content in the requirement model, in the Eclipse modeling framework and jdk1.8 environment, first, use the Java third-party library dom4j to design and develop an interface for reading the attribute content information of the requirement model in XML data format. Secondly, call the Java interface of Stanford CoreNLP to analyze and process the requirement attribute content text in the requirement model, and then design and develop the requirement integrity assessment function and interface. For the analyzed and processed requirement attribute content text, regular expressions are used to construct the proposed requirement integrity constraints, and the analyzed and processed requirement attribute content is matched with the assessment criteria to output the matching results. After that, the evaluation result visualization function is designed and developed based on SWT, the matching results are analyzed, and the requirement content that does not meet the integrity assessment criteria is highlighted and visualized. Then, the evaluation result output function is designed and developed based on SWT, and the requirement integrity assessment results are output on the console. Finally, the development of these interfaces and functional modules is implemented based on the EclipseRCP framework and Java programming language, and packaged into the form of a requirement integrity assessment plug-in, and integrated with the requirement modeling and assessment system; The design process model building module includes the design process metamodel building and the design process model building; the main function of the design process model building module is to support the unified construction of design process models in different fields and at different levels; In the design process modeling module, the design process model creation submodule reads the metamodel information in the design process metamodel creation submodule through an interface; supports the graphical construction of the model; First, the attribute metamodel, object metamodel, point metamodel, role metamodel, relationship metamodel, and graph metamodel are designed and constructed, including defining the metamodel name and related descriptions, and specifying the fixed syntax of the metamodel, that is, the specific style of the model in the modeling environment, including graphic shape, display text description, color, etc.; finally, the metamodel connection rules are set through configuration, including "inclusion", "attribute connection", "binding", "association", etc., to complete the construction of the design process metamodel; After completing the construction of the design process metamodel library, you can use each metamodel to build the model. First, use the metamodel to create a graph model in the tool. Open the metamodel to see the modeling canvas. Drag the object and relationship metamodel on the right side of the canvas to complete the model construction. The design process metamodel creation is responsible for supporting system engineers to build metamodels based on existing modeling languages, or to create metamodels based on domain characteristics; The design process model creation is responsible for supporting system engineers to use metamodels to build models; The requirement and design process ontology integration module includes model-to-ontology mapping, ontology-to-model mapping and ontology visualization; the main function of the requirement and design process ontology integration module is to achieve semantically consistent expression of the requirement model and the design process model, thereby laying a foundation for the creation of traceability relationships between heterogeneous requirement models and design process models; In the requirement and design process ontology integration module, the ontology-to-model mapping submodule reads the external integrated ontology information through the interface, and then generates the requirement model in the requirement entry model construction submodule, the design process metamodel in the design process metamodel creation submodule, the design process model in the design process model creation submodule, and the traceability relationship model in the requirement traceability relationship creation submodule respectively through the interface; The model-to-ontology mapping submodule generates an integrated ontology by reading the requirement model in the requirement entry model construction submodule, the design process metamodel in the design process metamodel creation submodule, the design process model in the design process model creation submodule, and the traceability relationship in the requirement traceability relationship creation submodule through the interface. The ontology visualization submodule reads the integrated ontology information through the interface for visualization. The model-to-ontology mapping is responsible for supporting the mapping of the requirement model and the design process model into an integrated ontology, so as to achieve semantically consistent expression of the requirement model and the design process model. In order to achieve the mapping of the requirement model, the design process model and the traceability relationship between the two into an integrated ontology, firstly, an interface capable of reading the requirement model, the design process model and the traceability relationship between the two is required. Secondly, it is necessary to generate the interface of the ontology. The design process modeling tool provides interfaces for the design process metamodel and model. For the interfaces for reading the requirement model and traceability relationship, this paper uses the Java third-party library dom4j to design and develop interfaces for reading the requirement model and traceability relationship in XML data format. For the ontology generation interface, Jena is a set of Java third-party libraries for supporting RDF / RDFS and OWL. It provides a large number of reading and generation interfaces for OWL format files, and can easily access and operate information such as classes, instances, and attributes in OWL. Therefore, this paper uses Jena to design and develop interfaces for generating integrated ontology. Finally, these interfaces are developed based on the Eclipse RCP framework and the Java programming language, and packaged into the form of a model-to-ontology mapping plug-in for integration with the requirement modeling and evaluation system. The ontology-to-model mapping is responsible for supporting the conversion of the integrated ontology mapping of requirements and design processes into requirement models and design process models to ensure the consistency of the models; in order to realize the conversion of the integrated ontology mapping into the requirement model, design process model and the traceability relationship between the two in the requirement modeling and evaluation system, first, an interface for reading the ontology is required, and secondly, an interface that can generate the requirement model, design process model and the traceability relationship between the two is required. For the ontology reading interface, Jena is used to design and develop an interface for reading the integrated ontology. For the interface for generating the requirement model and the traceability relationship, dom4j is used to design and develop interfaces for generating the requirement model and the traceability relationship in XML data format. The design process modeling tool provides an interface for generating design process metamodels and models. Finally, the development of these interfaces is implemented based on the Eclipse RCP framework and the Java programming language, and packaged in the form of an ontology-to-model mapping plug-in, which is integrated with the requirement modeling and evaluation system; The ontology visualization is responsible for supporting the visualization of requirements, design process elements and the relationship between them, so that designers can clearly understand the traceability relationship between requirements and design processes. In order to more intuitively and clearly display the traceability relationship between the requirement model and the design process model, an ontology visualization plug-in is developed to support the visualization of the traceability relationship. First, the ontology reading interface developed in the ontology-to-model mapping plug-in is called to read the traceability relationship information between the requirement model and the design process model in the ontology. Then, we designed and developed the ontology visualization graph plug-in based on the Eclipse Zest plug-in. Finally, we implemented the development of these interfaces based on the Eclipse RCP framework and Java programming language, and packaged them in the form of an ontology visualization plug-in to integrate with the requirements modeling and evaluation system. The requirement traceability expression and evaluation module includes the construction of requirement traceability relationship and the evaluation of requirement traceability; the main function of the requirement traceability expression and evaluation module is to support the construction of the traceability relationship between requirements and design process and the evaluation of requirement traceability; In the requirement traceability expression and evaluation module, the requirement traceability relationship construction submodule reads the requirement model information of the requirement itemization model construction submodule through the interface, and reads the design process model information in the design process model construction submodule through the interface; the requirement traceability evaluation submodule reads the integrated ontology information through the interface to perform requirement traceability evaluation; The requirement traceability relationship construction is responsible for supporting the construction of the traceability relationship between the requirement and the design process based on the integrated ontology of the requirement and the design process, or constructing the traceability relationship between the requirement model and the design process model in the system, and mapping it to the traceability relationship between the requirement and the design process in the integrated ontology; in order to realize the construction of the traceability relationship between the requirement model and the design process model, first of all, it is necessary to be able to read the interface of the requirement model and the design process model. For reading the interface of the requirement model, the underlying data format of the requirement model is XML. Therefore, this paper uses the Java third-party library dom4j to design and develop an interface for reading the requirement model in XML data format; For reading the design process model interface, the design process modeling tool itself provides the design process metamodel and model reading interface in Java data format, which can support the reading of the design process model and metamodel. Secondly, it is necessary to generate the interface of the traceability relationship model. Since the underlying storage format of the traceability relationship model is also in XML data format, dom4j is also used to design and develop the interface of the traceability relationship model in XML data format. Finally, these interfaces are developed based on the Eclipse RCP framework and Java programming language, and packaged into the form of a requirement traceability relationship construction plug-in, and integrated with the requirement modeling and evaluation system; The requirement traceability assessment is responsible for supporting requirement engineers to assess requirement traceability based on integrated ontology. In order to achieve the requirement traceability assessment based on integrated ontology, first of all, it is necessary to be able to read the interface of the integrated ontology. The requirement and design process ontology integration module has designed and developed an interface for reading the integrated ontology based on Jena, which can be called here. At the same time, Jena supports processing RDF data, executing SPARQL queries, etc. Therefore, this paper uses Jena to design a requirement traceability assessment interface based on SPARQL. Finally, these interfaces are developed based on the Eclipse RCP framework and Java programming language, and packaged into a requirement traceability assessment plug-in for integration with the requirement modeling and assessment system.

2. The device for supporting complex system requirement integrity modeling and evaluation according to claim 1, characterized in that: The demand modeling and evaluation system includes four layers: data layer, core driver layer, business logic layer and user interface layer; the data layer represents the specific data form of modeling, conversion and evaluation involved in the demand modeling and evaluation system, and is driven by the core driver layer to provide underlying data support for the implementation of business logic, including the following five types; XML data: used to store demand models and traceability relationship models, and supports conversion between OWL data and JAVA data. JAVA data: used to store and process information within the system to support the system's functions and logic; JAVA data supports interaction with XML data, such as reading and manipulating XML documents through the JAVA library DOM; at the same time, JAVA data supports interaction with OWL data, such as parsing and processing OWL ontologies through the JAVA library Jena. KARMA data: used to store design process metamodels and models, and supports conversion with OWL data. Graphical model data: used to store the data of the design process model in the canvas, including layout, objects, relationships, etc., and supports mutual conversion with KARMA data. OWL data: used to store data information of integrated ontology, and can support relevant functions related to ontology, such as semantic query and reasoning; supports conversion with XML data, JAVA data, KARMA data and graphical model data.

3. The device for supporting complex system requirement integrity modeling and evaluation according to claim 2, characterized in that: The core driver layer is the key part of the system, interacting directly with the data layer and responsible for implementing the business logic and functions of the system. By calling the data services provided by the data layer, the data is processed and analyzed, and corresponding operations are performed according to business needs; the core driver layer includes the following eight core driver engines: ProR core engine: supports parsing and generation of ReqIF requirement models in XML format. Requirements expression constraint engine: supports structural constraints on requirements content based on the requirements integrity expression constraints. CoreNLP engine: supports processing natural language demand text, including word segmentation, part-of-speech tagging, named entity recognition, syntactic analysis, coreference resolution and other tasks. Regular expression matching engine: supports regular expression matching of natural language processing results output by the CoreNLP engine based on the proposed requirement completeness assessment criteria. Metamodel interpretation engine: supports parsing the system design process metamodel developed based on graph, object, point, attribute, relationship, role metamodel and its constraints. The engine is used to read the design metamodel and interpret it as KARMA backend data structure to generate the metamodel library. Model interpretation engine: supports parsing the design process model built based on the design process metamodel. The engine is used to read the design process model and interpret it as the KARMA backend data structure. It also supports conversion with graph model data. Traceability engine: supports obtaining demand model and design process model data, and establishing a traceability relationship between the demand model and the design process model. Ontology engine: Parses and processes OWL ontology based on the JAVA library Jena, supports the conversion between XML data, KARMA data, and graph model data and OWL ontology data, and supports query reasoning based on OWL data, as well as visualization of OWL data.

4. The device for supporting complex system requirement integrity modeling and evaluation according to claim 3, characterized in that: The business logic layer represents the specific operations that the demand modeling and evaluation system allows users to complete. It is driven by the core driver layer and participates in the implementation of business-level functions. The business logic layer includes the following eleven functions: Demand entry model construction: Supports the construction of demand entry model based on demand integrity expression rules; Definition of requirement content constraints: Supports structural constraints on requirement content in the process of building requirement models based on requirement integrity expression constraints; External demand model integration: support integration of external demand models in word (.docx), csv, and reqif formats; Requirement integrity assessment: The system has built-in requirement integrity assessment criteria, which supports users to assess the integrity of requirement content in externally integrated requirement models, output requirement integrity assessment results, and highlight requirement content that does not meet integrity rules; Design process metamodel creation: Supports the construction of design process metamodel based on graphs, objects, attributes, nodes, relationships, role metamodels and constraints; Design process model creation: Based on the design process metamodel, it supports users to build a design process model by dragging or configuring; Model-to-ontology mapping: After the requirement model, design process model and the traceability relationship between them are created, users are supported to convert graphical model data into OWL ontology data; Ontology to model mapping: supports users to read integrated ontology, convert OWL ontology data into graphical model data, and complete the creation of requirements, design process models and the traceability relationship between the two; Ontology visualization: supports visualization of OWL ontology data through graphs; Demand traceability relationship construction: support the acquisition of demand model and design process model information, and build a traceability relationship between the two; or support the construction of a traceability relationship between the two through the integrated ontology of demand and design process; Requirements traceability assessment: supports the execution of corresponding traceability assessment based on the proposed requirements traceability assessment criteria, and outputs the requirements traceability assessment results.

5. The device for supporting complex system requirement integrity modeling and evaluation according to claim 4, characterized in that: The user interface layer represents the specific applications provided by the demand modeling and evaluation system for designers by combining the specific functions of the business logic layer. The user interface layer includes the following five applications: Demand modeling: supports the construction of demand entry models based on demand integrity rules and constraints to achieve complete expression of demand content. Requirements integrity assessment: Supports the assessment of the integrity of the requirements attribute content in the requirements model based on the proposed requirements integrity assessment criteria. Design process modeling: supports the construction of design process metamodels and models based on graphs, objects, attributes, nodes, relationships, role metamodels and constraint methods. Integration of requirements and design process ontology: supports the conversion between the requirements model, system design process model, and the traceability relationship between the two and the integrated ontology, achieves the semantic consistency of the requirements model and the design process model, and supports the semantic expression of requirements traceability; at the same time, supports integrated ontology visualization to clearly display the traceability relationship between the requirements model and the design process model. Requirements traceability expression and evaluation: Supports the construction of traceability relationship between requirement model and design process model; For the integrated ontology, based on the defined requirement traceability evaluation criteria, the requirement traceability evaluation is performed and the evaluation results are output.

Images