An apparatus supporting integrity modeling and evaluation of complex system requirements

Abstract

The application discloses a device for supporting complex system requirement integrity modeling and evaluation, and relates to the technical field of system engineering, and comprises requirement modeling, requirement integrity evaluation, design process modeling, requirement and design process ontology integration, requirement traceability expression and evaluation; the requirement modeling module comprises requirement entry modeling and requirement content constraint definition; the requirement modeling module mainly functions to realize requirement model creation based on requirement integrity expression rules and constraints, and guarantee requirement content integrity in the created requirement model; in the requirement modeling module, the requirement content constraint definition submodule provides constraints to the requirement entry modeling submodule; the application uses entry modeling technology to decompose high-level requirements into specific and operable entries in the requirement modeling module, which promotes in-depth understanding of the requirements and ensures that each requirement is accurately defined and recorded.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of system engineering, and particularly relates to a device for supporting complex system requirement integrity modeling and evaluation. BACKGROUND

[0002] In the field of software development and system engineering, especially when complex systems are involved, the core of requirement management is to ensure that all stakeholders' requirements are correctly understood, recorded and implemented, however, as the complexity of the system increases, the requirement management process faces many challenges, the traditional requirement management system is difficult to effectively track the change history of each requirement, the requirement engineering method often focuses on the collection and analysis of requirements, and ignores the dynamic changes and mutual dependencies of requirements in the entire system development life cycle, in addition, the existing tools have defects in processing the mapping relationship between requirements and design, resulting in the lack of requirement traceability, making it difficult to track the implementation and changes of requirements in the system development and maintenance stage, therefore, the application provides a device for supporting complex system requirement integrity modeling and evaluation. SUMMARY

[0003] The application aims to provide a device for supporting complex system requirement integrity modeling and evaluation, in the requirement modeling module, the requirement engineer uses the entry model construction technology to decompose high-level requirements into more specific and operable entries, which solves the problem that the existing requirement management method is difficult to effectively track the change history of each requirement, and the requirement engineering method often focuses on the collection and analysis of requirements, and ignores the dynamic changes and mutual dependencies of requirements in the entire system development life cycle.

[0004] To solve the above technical problems, the application is realized by the following technical scheme:

[0005] The application is a device for supporting complex system requirement integrity modeling and evaluation, which comprises requirement modeling, requirement integrity evaluation, design process modeling, requirement and design process ontology integration, requirement traceability expression and evaluation.

[0006] The requirement modeling module includes requirement entry model construction and requirement content constraint definition; the main function of the requirement modeling module is to realize the creation of requirement model based on the 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 entry model construction submodule, and because of the high coupling degree between the two, they are designed as a plug-in in the subsequent design; in order to realize the creation of requirement model that meets the 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, second, based on the requirement integrity expression criteria and constraints, the interface is designed again to support the creation of requirement model based on the requirement integrity expression criteria and constraints. Finally, based on the Eclipse RCP framework and Java programming language, the development of the interface is realized, and the interface and the ProR project are packaged in the form of requirement modeling plug-in, which is integrated with the requirement modeling and evaluation system; the requirement entry model construction is responsible for supporting the requirement engineers to carry out the entry modeling of requirements according to the requirement integrity expression criteria; the requirement content constraint definition is responsible for supporting the requirement engineers to structure the constraints of the requirement content in the requirement model creation process according to the defined requirement constraints, and to ensure the integrity of the requirement content in the requirement modeling process;

[0007] The requirement integrity evaluation module includes external requirement model integration and requirement integrity evaluation. The main function of the requirement integrity evaluation module is to evaluate the integrity of the requirement content in the integrated external requirement model, and ensure the integrity of the requirement content in the integrated external requirement model. In the requirement integrity evaluation module, the external requirement model integration submodule reads the requirement model information in three formats of word, csv and reqif through an interface. Then, the requirement model information is integrated into the requirement model of the requirement entry model construction submodule through an interface. The requirement integrity evaluation submodule reads the attribute content information of the requirement model in the requirement entry model construction submodule through an interface, and then evaluates the integrity of the integrated external requirement content. The external requirement model integration is responsible for supporting the integration of external requirement models by requirement engineers. The requirement modeling and evaluation system supports the integration of requirement models in word (.docx), csv and reqif formats. In order to integrate the external requirement models in word, csv and reqif formats, under the Eclipse modeling framework and jdk1.8 environment, first, an interface for reading the requirement model information in word (.docx), csv and reqif formats needs to be designed and developed.An interface for reading requirement model information in word (.docx) format is designed based on Java library Apache POI, and an interface for reading requirement model information in csv format is designed based on Java library OpenCSV; the requirement model in reqif format can be directly integrated without further design and development; then, an interface for generating requirement model is designed and developed; since the underlying format of the requirement model is XML format, dom4j, a Java third-party library, is a Java XML library with rich functions, flexibility and ease of use, and is suitable for various XML document processing requirements, including parsing, creating, operating and querying, etc., therefore, dom4j is used to design and develop the interface for generating requirement model; finally, the development of the interface is realized based on Eclipse RCP framework and Java programming language, and is packaged in the form of external requirement model integration plug-in, and is integrated with the requirement modeling and evaluation system; the requirement integrity evaluation is responsible for supporting the requirement engineer to evaluate the integrity of the requirement content in the integrated external requirement model; in order to realize the integrity evaluation of the requirement attribute content in the requirement model, under the Eclipse modeling framework and jdk1.8 environment, firstly, a Java third-party library dom4j is used to design and develop an interface for reading attribute content information of the requirement model in XML data format; secondly, the Java interface of Stanford CoreNLP is called 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 analyzed and processed requirement attribute content text, regular expressions are used to construct the proposed requirement integrity constraints, the analyzed and processed requirement attribute content is matched with the evaluation criteria, and the matching result is output; thereafter, the evaluation result visualization function is designed and developed based on SWT, the matching result is analyzed, and the requirement content that does not meet the integrity evaluation criteria is highlighted and visually displayed; then, the evaluation result output function is designed and developed based on SWT, and the requirement integrity evaluation result is output on the console; finally, the development of the interface and function module is realized based on Eclipse RCP framework and Java programming language, and is packaged in the form of requirement integrity evaluation plug-in, and is integrated with the requirement modeling and evaluation system.

[0008] The design process modeling module includes design process meta-model construction and design process model construction; the main function of the design process modeling module is to support unified construction of design process models in different domains and different levels; in the design process modeling module, a design process model creation submodule reads meta-model information in a design process meta-model creation submodule through an interface; a design process modeling tool supports graphical construction of system design process meta-models and models based on KARMA modeling language; first, attribute meta-models, object meta-models, point meta-models, role meta-models, relationship meta-models and graph meta-models are designed and constructed, including defining meta-model names and related descriptions, specifying fixed syntax of the meta-models, i.e. specific styles of the models in a modeling environment, including graphical shapes, display text descriptions, colors and the like; finally, meta-model connection rule settings are performed through configuration, including "containment", "attribute connection", "binding", "association" and the like, to complete design process meta-model construction; after completion of design process meta-model library construction, each meta-model can be used to construct a model; first, a graph model is created in the tool using a graph meta-model; opening the graph meta-model can see a modeling canvas; objects and relationship meta-models on the right side of the canvas are dragged to complete model construction; the design process meta-model creation is responsible for supporting system engineers to construct meta-models according to existing modeling languages or to create meta-models according to domain characteristics; the design process model creation is responsible for supporting system engineers to construct models using meta-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 realize semantic consistent expression of requirement model and design process model, thereby laying foundation for creation of traceability relationship between heterogeneous requirement model and design process model; in the requirement and design process ontology integration module, the ontology-to-model mapping submodule reads external ontology information through an interface, and then generates requirement model in the requirement entry modeling submodule, design process metamodel in the design process metamodel creation submodule, design process model in the design process model creation submodule and traceability relationship model in the requirement traceability relationship creation submodule through an interface; the model-to-ontology mapping submodule reads requirement model in the requirement entry modeling submodule, design process metamodel in the design process metamodel creation submodule, design process model in the design process model creation submodule and traceability relationship in the requirement traceability relationship creation submodule through an interface, and generates integrated ontology, and the ontology visualization submodule reads integrated ontology information through an interface and performs visual display; the model-to-ontology mapping is responsible for supporting mapping conversion of requirement model and design process model into integrated ontology, and realizing semantic consistent expression of requirement model and design process model; in order to realize mapping conversion of requirement model, design process model and traceability relationship therebetween into integrated ontology, firstly, an interface capable of reading requirement model, design process model and traceability relationship therebetween is needed; secondly, an interface for generating ontology is needed, and the design process modeling tool provides an interface for reading design process metamodel and model; for the interface for reading requirement model and traceability relationship, a Java third-party library dom4j is used to design and develop an interface for reading requirement model and traceability relationship in XML data format; for the ontology generation interface, Jena is a Java third-party library for supporting RDF / RDFS and OWL, and provides a large number of interfaces for reading and generating OWL format files, and can easily access and operate information such as classes, instances and properties in OWL, therefore, Jena is used to design and develop the interface for generating integrated ontology. Finally, the interfaces are developed based on Eclipse RCP framework and Java programming language, and are packaged in the form of model-to-ontology mapping plug-in, and are integrated with the requirement modeling and evaluation system; the ontology-to-model mapping is responsible for supporting mapping conversion of integrated ontology of requirement and design process into requirement model and design process model, and ensuring consistency of the models; in order to realize mapping conversion of integrated ontology into requirement model, design process model and traceability relationship therebetween in the requirement modeling and evaluation system, firstly, an interface for reading ontology is needed, and secondly, an interface capable of generating requirement model, design process model and traceability relationship therebetween is needed. For the ontology reading interface, Jena is used to design and develop an interface for reading integrated ontology.For the interface of generating requirement model and tracing relationship, the interface of generating requirement model and tracing relationship in XML data format is designed and developed by using dom4j. The interface of generating design process metamodel and model is provided by the design process modeling tool. Finally, the development of these interfaces is implemented based on Eclipse RCP framework and Java programming language, and packaged in the form of ontology to model mapping plug-in, integrated with the requirement modeling and evaluation system; the ontology visualization is responsible for supporting the graph visualization of requirements, design process elements and the relationship between them, so that designers can clearly understand the tracing relationship between requirements and design process; in order to more intuitively and clearly show the tracing relationship between requirement model and design process model, the ontology visualization plug-in is developed to support the visualization graph display of tracing relationship, firstly, the ontology reading interface developed in the ontology to model mapping plug-in is called to read the tracing relationship information of requirement model and design process model in ontology; then, the ontology visualization graph plug-in is designed and developed based on ElipseZest plug-in; finally, the development of these interfaces is implemented based on Eclipse RCP framework and Java programming language, and packaged in the form of ontology visualization plug-in, integrated with the requirement 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 construction of requirement and design process traceability relationship and evaluation of requirement traceability; in the requirement traceability expression and evaluation module, the requirement traceability relationship construction submodule reads requirement model information of the requirement entry modeling module through an interface and reads design process model information in the design process model construction submodule through an interface; the requirement traceability evaluation submodule reads integrated ontology information through an interface and performs requirement traceability evaluation; the requirement traceability relationship construction is responsible for supporting construction of requirement and design process traceability relationship based on integrated ontology of requirement and design process or constructing traceability relationship between requirement model and design process model in the system and mapping to traceability relationship of requirement and design process in integrated ontology; in order to realize construction of traceability relationship between requirement model and design process model, firstly, an interface for reading requirement model and design process model is needed; for the interface for reading requirement model, the underlying data format of the requirement model is XML, therefore, the interface for reading the requirement model in XML data format is designed and developed by using the Java third-party library dom4j; for the interface for reading the design process model, the design process modeling tool itself provides a design process metamodel in java data format and a model reading interface, which can support reading of the design process model and the metamodel; secondly, an interface for generating a traceability relationship model is needed; since the underlying storage format of the traceability relationship model is also XML data format, the interface for generating the traceability relationship model in XML data format is also designed and developed by using dom4j; finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language and is packaged in the form of a requirement traceability relationship construction plug-in and integrated with the requirement modeling and evaluation system; the requirement traceability evaluation is responsible for supporting requirement engineers in evaluating requirement traceability based on integrated ontology; in order to realize evaluation of requirement traceability based on integrated ontology, firstly, an interface for reading integrated ontology is needed; the interface for reading integrated ontology has been designed and developed based on Jena in the requirement and design process ontology integration module and can be called here; meanwhile, Jena supports processing of RDF data and execution of SPARQL queries, therefore, the requirement traceability evaluation interface based on SPARQL is designed by using Jena; finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language and is packaged in the form of a requirement traceability evaluation plug-in and integrated with the requirement modeling and evaluation system.

[0011] As a preferred technical scheme, the requirement modeling and evaluation system comprises four levels of data layer, core driving layer, business logic layer and user interface layer; the data layer represents specific data forms of modeling, conversion and evaluation involved in the requirement modeling and evaluation system, and provides underlying data support for the realization of business logic driven by the core driving layer, and comprises the following five kinds: XML data: used for storing requirement models and traceability relationship models, supporting mutual conversion with OWL data and JAVA data; JAVA data: used for storing and processing information in the system to support the functions and logic of the system; JAVA data supports interaction with XML data, such as reading and operating XML documents through JAVA library DOM; 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 for storing design process meta-models and models, supporting mutual conversion with OWL data; graph model data: used for storing data of design process models in the canvas, including layout, object, relationship and the like, supporting mutual conversion with KARMA data; OWL data: used for storing data information of ontology sets, and capable of supporting related functions related to ontology, such as semantic query and reasoning and the like; supporting mutual conversion with XML data, JAVA data, KARMA data and graphical model data.

[0012] As a preferred technical solution, the core driving layer is a key part of the system, 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 the corresponding operations are executed according to the business requirements; the core driving layer includes the following eight core driving engines: ProR core engine: support for parsing and generating ReqIF requirement model in XML format; requirement expression constraint engine: support for structuring constraints on requirement content based on the proposed requirement integrity expression constraints; CoreNLP engine: support for processing natural language requirement text, including word segmentation, part-of-speech tagging, named entity recognition, syntax analysis, and reference resolution; regular expression matching engine: support for regular expression matching of natural language processing results output by the CoreNLP engine based on the proposed requirement integrity evaluation criteria; meta-model interpretation engine: support for parsing system design process meta-model developed based on graph, object, point, attribute, relationship, and role meta-meta-model and its constraints, reading the design meta-model through the engine, and interpreting it into KARMA backend data structure to generate the meta-model library; model interpretation engine: support for parsing the design process model constructed based on the design process meta-model, reading the design process model through the engine, and interpreting it into KARMA backend data structure, while supporting conversion with graph model data; trace engine: support for obtaining requirement model and design process model data, and establishing trace relationship between the requirement model and the design process model; ontology engine: based on JAVA library Jena, parse and process OWL ontology, support mutual conversion between XML data, KARMA data, and graph model data and OWL ontology data, and support query reasoning based on OWL data, as well as visualization of OWL data.

[0013] As a preferred technical solution, the business logic layer represents the specific operations that the requirement modeling and evaluation system allows users to complete, which are driven by the core driving layer and participate in the implementation of business-level functions. The business logic layer includes the following eleven functions: requirement entry model construction: support for constructing a requirement entry model based on requirement integrity expression rules; requirement content constraint definition: support for structuring constraints on requirement content during the construction of a requirement model based on requirement integrity expression constraints; external requirement model integration: support for integrating external word (.docx), csv, reqif format requirement models; requirement integrity evaluation: the system has built-in requirement integrity evaluation criteria, supporting users to evaluate the integrity of the requirement content in the externally integrated requirement model, output the requirement integrity evaluation result, and highlight the requirement content that does not meet the integrity rules; design process meta-model creation: support for constructing a design process meta-model based on graph, object, point, attribute, relationship, role meta-meta-model and constraints; design process model creation: based on the design process meta-model, support users to construct a design process model through drag and drop or configuration; model to ontology mapping: after the creation of the requirement model, the design process model and the traceability relationship between them, support users to convert the graphical model data to OWL ontology data; ontology to model mapping: support users to read the integrated ontology, convert the OWL ontology data to graphical model data, and complete the creation of the requirement, design process model and the traceability relationship between them; ontology visualization: support for visualizing OWL ontology data through graph atlas; requirement traceability relationship construction: support for obtaining requirement model, design process model information, and constructing the traceability relationship between them; or support for constructing the traceability relationship between them through the integrated ontology of requirement and design process; requirement traceability evaluation: support for performing corresponding traceability evaluation based on the proposed requirement traceability evaluation criteria, and output the requirement traceability evaluation result.

[0014] As a preferred technical solution, the user interface layer provides specific applications for designers by modeling and evaluating the requirements of the specific function combination of the business logic layer, and the user interface layer includes the following five applications: requirement modeling: support for building requirement entry models based on requirement integrity rules and constraints, and realize complete expression of requirement content; requirement integrity evaluation: support for evaluating the integrity of requirement attribute content in the requirement model based on proposed requirement integrity evaluation criteria; design process modeling: support for building design process meta-model and model based on graph, object, point, attribute, relationship, role meta-model and constraint methods; requirement and design process ontology integration: support for the mutual conversion between the integrated ontology of requirement model, system design process model and the traceability relationship between them, realize semantic consistency of requirement model and design process model, support semantic expression of requirement traceability; at the same time, support integrated ontology visualization, clearly show the traceability relationship between requirement model and design process model; requirement traceability expression and evaluation: support for building the traceability relationship between requirement model and design process model; based on the defined requirement traceability evaluation criteria, execute requirement traceability evaluation for the integrated ontology, and output evaluation results.

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

[0016] In the requirement modeling module, the requirement engineer uses the entry model construction technology to decompose high-level requirements into more specific and operational entries, this method promotes in-depth understanding of requirements, and ensures that each requirement is accurately defined and recorded, at the same time, requirement content constraint provides a mechanism for requirement engineers to ensure that all relevant business rules and constraint conditions are considered during modeling, such as requirement consistency, unambiguity, testability and implementability, these constraints help to reduce errors and omissions in the requirement model, thereby improving the accuracy and integrity of the requirement model.

[0017] The requirement integrity evaluation module allows the requirement engineer to systematically evaluate the integrated external requirement model to verify its integrity, which includes checking whether each aspect of the requirement is covered and whether there is contradiction or repetition between them, this process ensures that all requirements remain consistent throughout the project life cycle and are consistent with business goals and customer requirements, at the same time, the requirement traceability expression and evaluation module provides powerful tools to establish and maintain traceability from original requirements to design, implementation and testing.

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

[0019] Of course, implementing any product of the application does not necessarily require achieving all the advantages described above at the same time. BRIEF DESCRIPTION OF DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the application, the drawings needed for the embodiments will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative effort on the basis of these drawings.

[0021] Figure 1 A functional architecture diagram of the device for supporting complex system requirement integrity modeling and evaluation of the application;

[0022] Figure 2 A specific architecture diagram of the data layer, the core driving layer, the business logic layer and the user interface layer of the application;

[0023] Figure 3 An interface interaction relationship diagram between the modules of the application;

[0024] Figure 4 A timing diagram of the execution process of the modules of the application;

[0025] Figure 5 A Chinese diagram of the front-end interface of the requirement modeling plug-in of the application;

[0026] Figure 6 An English diagram of the front-end interface of the requirement modeling plug-in of the application;

[0027] Figure 7 A front-end interface of the csv format external requirement model integration plug-in of the application;

[0028] Figure 8 A front-end interface of the word format external requirement model integration plug-in of the application;

[0029] Figure 9 A Chinese diagram of the front-end interface of the requirement integrity evaluation plug-in of the application;

[0030] Figure 10 An English diagram of the front-end interface of the requirement integrity evaluation plug-in of the application;

[0031] Figure 11 Interface for the meta-model of the present application;

[0032] Figure 12 Interface for the model construction of the present application;

[0033] Figure 13 Interface for the model-to-ontology mapping plug-in of the present application;

[0034] Figure 14 Interface for the ontology-to-model mapping plug-in of the present application;

[0035] Figure 15 Interface for the ontology visualization plug-in of the present application;

[0036] Figure 16 Interface for the traceability construction plug-in of the present application;

[0037] Figure 17 Interface for the requirement traceability evaluation plug-in of the present application. DETAILED DESCRIPTION

[0038] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all the other embodiments obtained by those skilled in the art without creative work fall within the protection scope of the present application.

[0039] Please refer to Figure 1 As shown in the figure, the present application is an apparatus for supporting the integrity modeling and evaluation of complex system requirements, including requirement modeling, requirement integrity evaluation, design process modeling, requirement and design process ontology integration, requirement traceability expression and evaluation.

[0040] The requirement modeling module includes requirement entry model construction and requirement content constraint definition. The main function of the requirement modeling module is to realize the creation of the requirement model based on the 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 entry model construction submodule. Since the coupling degree between the two is high, they are designed as a plug-in in the subsequent design. In order to realize the creation of the requirement model that meets the 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. Second, based on the requirement integrity expression criteria and constraints, the interface is designed again to support the creation of the requirement model based on the requirement integrity expression criteria and constraints. Finally, based on the Eclipse RCP framework and the Java programming language, the development of the interface is realized, and the interface and the ProR project are packaged in the form of a requirement modeling plug-in, which is integrated with the requirement modeling and evaluation system. The requirement entry model construction is responsible for supporting the requirement engineers to perform the entry modeling of the requirements according to the requirement integrity expression criteria. The requirement content constraint definition is responsible for supporting the requirement engineers to perform the structured constraint on the requirement content in the requirement model creation process according to the defined requirement constraints, and to ensure the integrity of the requirement content in the requirement modeling process.

[0041] The demand integrity evaluation module includes external demand model integration and demand integrity evaluation. The main function of the demand integrity evaluation module is to evaluate the integrity of the demand content in the integrated external demand model, and ensure the integrity of the demand content in the integrated external demand model. In the demand integrity evaluation module, the external demand model integration submodule reads the demand model information in the three formats of external word, csv and reqif through an interface. Then, the demand model is integrated into the demand entry model construction submodule through an interface. The demand integrity evaluation submodule reads the attribute content information of the demand model in the demand entry model construction submodule through an interface, and then evaluates the integrity of the externally integrated demand content. The external demand model integration is responsible for supporting the demand engineer to integrate the external demand model. The demand modeling and evaluation system supports the integration of demand models in the formats of word (.docx), csv and reqif. In order to realize the integration of external word, csv and reqif format demand model, under the Eclipse modeling framework and jdk1.8 environment, first, the interface for reading the demand model information in the formats of word (.docx), csv and reqif needs to be designed and developed.An interface for reading requirement model information in word (.docx) format is designed based on Java library Apache POI, and an interface for reading requirement model information in csv format is designed based on Java library OpenCSV; the requirement model in reqif format can be directly integrated without further design and development; then, an interface for generating requirement model is designed and developed; since the underlying format of the requirement model is XML format, dom4j, a Java third-party library, is a Java XML library with rich functions, flexibility and ease of use, and is suitable for various XML document processing requirements, including parsing, creating, operating and querying, therefore, dom4j is used to design and develop the interface for generating requirement model; finally, the development of the interface is realized based on Eclipse RCP framework and Java programming language, and is packaged in the form of external requirement model integration plug-in, and is integrated with the requirement modeling and evaluation system; the requirement integrity evaluation is responsible for supporting the requirement engineer to evaluate the integrity of the requirement content in the integrated external requirement model; in order to realize the integrity evaluation of the requirement attribute content in the requirement model, under the Eclipse modeling framework and jdk1.8 environment, firstly, a Java third-party library dom4j is used to design and develop an interface for reading attribute content information of the requirement model in XML data format; secondly, the Java interface of Stanford CoreNLP is called 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 analyzed and processed requirement attribute content text, regular expressions are used to construct the proposed requirement integrity constraints, the analyzed and processed requirement attribute content is matched with the evaluation criteria, and the matching result is output; thereafter, the evaluation result visualization function is designed and developed based on SWT, the matching result is analyzed, and the requirement content that does not meet the integrity evaluation criteria is highlighted and visually displayed; then, the evaluation result output function is designed and developed based on SWT, and the requirement integrity evaluation result is output on the console; finally, the development of the interface and function module is realized based on Eclipse RCP framework and Java programming language, and is packaged in the form of requirement integrity evaluation plug-in, and is integrated with the requirement modeling and evaluation system.

[0042] The design process model modeling module includes design process meta-model construction and design process model construction. The main function of the design process modeling module is to support the unified construction of design process models in different domains and at different levels. In the design process modeling module, the design process model creation submodule reads the meta-model information in the design process meta-model creation submodule through an interface. The design process modeling tool supports the graphical construction of system design process meta-models and models based on KARMA modeling language. First, the attribute meta-model, object meta-model, point meta-model, role meta-model, relationship meta-model and graph meta-model are designed and constructed, including defining the meta-model name and related description, specifying the fixed syntax of the meta-model, i.e. the specific style of the model in the modeling environment, including the graphical shape, display text description, color, etc. Finally, the meta-model connection rule setting is configured, including "contains", "attribute connection", "binding", "association", etc., to complete the design process meta-model construction. After the design process meta-model library construction is completed, each meta-model can be used for model construction. First, a graph model is created in the tool using the graph meta-model. Opening the graph meta-model can see the modeling canvas. The object and relationship meta-models on the right side of the canvas are dragged to complete the model construction. The design process meta-model creation is responsible for supporting system engineers to construct meta-models according to the existing modeling language or to create meta-models according to the domain characteristics. The design process model creation is responsible for supporting system engineers to construct models using meta-models.

[0043] The demand and design process ontology integration module includes model-to-ontology mapping, ontology-to-model mapping and ontology visualization; the main function of the demand and design process ontology integration module is to realize the semantic consistent expression of the demand model and the design process model, thereby laying the foundation for the creation of the traceability relationship between the heterogeneous demand model and the design process model; in the demand and design process ontology integration module, the ontology-to-model mapping submodule reads external ontology information through an interface, and then generates the demand model in the demand 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 demand traceability relationship creation submodule through an interface; the model-to-ontology mapping submodule reads the demand model in the demand 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 demand traceability relationship creation submodule through an interface, and generates the integrated ontology, and the ontology visualization submodule reads the integrated ontology information through an interface and performs visual display; the model-to-ontology mapping is responsible for supporting the mapping conversion of the demand model and the design process model into the integrated ontology, realizing the semantic consistent expression of the demand model and the design process model; in order to realize the mapping conversion of the demand model, the design process model and the traceability relationship therebetween into the integrated ontology, firstly, an interface capable of reading the demand model, the design process model and the traceability relationship therebetween is needed; secondly, an interface for generating the ontology is needed, the design process modeling tool provides an interface for reading the design process metamodel and the model, for the interface for reading the demand model and the traceability relationship, this paper uses the Java third-party library dom4j to design and develop the interface for reading the demand model and the traceability relationship in XML data format, for the ontology generation interface, Jena is a Java third-party library for supporting RDF / RDFS and OWL, which provides a large number of interfaces for reading and generating OWL format files, and can easily access and operate the class, instance and property information in OWL, therefore, this paper uses Jena to design and develop the interface for generating the integrated ontology. Finally, based on the Eclipse RCP framework and the Java programming language, the development of these interfaces is realized, and they are packaged in the form of model-to-ontology mapping plug-ins, integrated with the demand modeling and evaluation system; the ontology-to-model mapping is responsible for supporting the mapping conversion of the integrated ontology of the demand and the design process into the demand model and the design process model, ensuring the consistency of the models; in order to realize the mapping conversion of the integrated ontology into the demand model, the design process model and the traceability relationship therebetween in the demand modeling and evaluation system, firstly, an interface for reading the ontology is needed, secondly, an interface capable of generating the demand model, the design process model and the traceability relationship therebetween is needed. For the ontology reading interface, Jena is used to design and develop the interface for reading the integrated ontology.For the interface of generating requirement model and tracing relationship, the interface of generating requirement model and tracing relationship in XML data format is designed and developed by using dom4j. The interface of generating design process metamodel and model is provided by the design process modeling tool. Finally, the development of these interfaces is implemented based on Eclipse RCP framework and Java programming language, and packaged in the form of ontology to model mapping plug-in, integrated with the requirement modeling and evaluation system; ontology visualization is responsible for supporting the graph visualization of requirements, design process elements and the relationship between them, so that designers can clearly understand the tracing relationship between requirements and design process; in order to more intuitively and clearly show the tracing relationship between requirement model and design process model, ontology visualization plug-in is developed to support the visualization graph display of tracing relationship. First, the ontology reading interface developed in the ontology to model mapping plug-in is called to read the tracing relationship information of requirement model and design process model in ontology; then, ontology visualization graph plug-in is designed and developed based on Eclipse Zest plug-in; finally, the development of these interfaces is implemented based on Eclipse RCP framework and Java programming language, and packaged in the form of ontology visualization plug-in, integrated with the requirement modeling and evaluation system.

[0044] The demand traceability expression and evaluation module includes demand traceability relationship construction and demand traceability evaluation. The main function of the demand traceability expression and evaluation module is to support the construction of demand and design process traceability relationship and the evaluation of demand traceability. In the demand traceability expression and evaluation module, the demand traceability relationship construction submodule reads the demand model information of the demand entry modeling module through the interface and reads the design process model information in the design process model construction submodule through the interface. The demand traceability evaluation submodule reads the integrated ontology information through the interface and performs demand traceability evaluation. The demand traceability relationship construction is responsible for supporting the construction of demand and design process traceability relationship based on the integrated ontology of demand and design process, or constructing the traceability relationship between the demand model and the design process model in the system and mapping the traceability relationship between the demand and the design process in the integrated ontology. In order to realize the construction of the traceability relationship between the demand model and the design process model, firstly, the demand model and the design process model interface need to be read. For the demand model interface, the underlying data format of the demand model is XML, so the interface for reading the XML data format of the demand model is designed and developed using the Java third-party library dom4j. For the design process model interface, the design process modeling tool itself provides the design process metamodel in java data format and the model reading interface, which can support the reading of the design process model and the metamodel. Secondly, the interface for generating the traceability relationship model is needed. Since the underlying storage format of the traceability relationship model is also XML data format, the interface for generating the XML data format of the traceability relationship model is also designed and developed using dom4j. Finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language, and is packaged in the form of demand traceability relationship construction plug-in and integrated with the demand modeling and evaluation system. The demand traceability evaluation is responsible for supporting the demand engineers to evaluate the demand traceability based on the integrated ontology. In order to realize the evaluation of demand traceability based on the integrated ontology, firstly, the interface for reading the integrated ontology is needed. The interface for reading the integrated ontology has been designed and developed based on Jena in the demand and design process ontology integration module, which can be called here. At the same time, Jena supports processing RDF data and executing SPARQL queries, so the demand traceability evaluation interface based on SPARQL is designed using Jena. Finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language, and is packaged in the form of demand traceability evaluation plug-in and integrated with the demand modeling and evaluation system.The demand modeling and evaluation system includes four levels of data layer, core driving 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, which is driven by the core driving layer to provide underlying data support for the realization of business logic, including the following five kinds: XML data: used to store demand models and traceability relationship models, supporting mutual conversion with OWL data and JAVA data; JAVA data: used to store and process information within the system to support system functions and logic; JAVA data supports interaction with XML data, such as reading and operating XML documents through JAVA library DOM; 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 meta-models and models, supporting mutual conversion with OWL data; graph model data: used to store data of design process models in the canvas, including layout, objects, relationships, etc., supporting mutual conversion with KARMA data; OWL data: used to store data information of the ontology set, which can support related functions related to ontology, such as semantic query and reasoning, etc.; supporting mutual conversion with XML data, JAVA data, KARMA data and graphical model data.

[0045] The core driving layer is the 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 the corresponding operations are performed according to the business requirements; the core driving layer includes the following eight core driving engines: ProR core engine: supports the parsing and generation of ReqIF requirement model in XML format; requirement expression constraint engine: supports the structured constraint of requirement content based on the proposed requirement integrity expression constraint; CoreNLP engine: supports processing natural language requirement text, including word segmentation, part-of-speech tagging, named entity recognition, syntax analysis, and reference resolution; regular expression matching engine: supports regular expression matching of natural language processing results output by CoreNLP engine based on the proposed requirement integrity evaluation criteria; meta-model interpretation engine: supports parsing the system design process meta-model developed based on graph, object, point, attribute, relationship, and role meta-meta-model and its constraints, and realizes the reading of the design meta-model through the engine, and interprets it as KARMA backend data structure, realizes the generation of meta-model library; model interpretation engine: supports parsing the design process model constructed based on the design process meta-model, and realizes the reading of the design process model through the engine, and interprets it as KARMA backend data structure, and supports the conversion with graph model data; trace engine: supports obtaining requirement model and design process model data, and establishing the trace relationship between requirement model and design process model; ontology engine: based on JAVA library Jena, parses and processes OWL ontology, supports the mutual conversion of XML data, KARMA data and graph model data and OWL ontology data, and supports query reasoning based on OWL data, and visualization of OWL data.

[0046] The business logic layer represents specific operations that the requirement modeling and evaluation system allows users to complete, which are driven by the core driving layer and participate in the implementation of business-level functions. The business logic layer includes the following eleven functions: requirement entry model construction: support for constructing a requirement entry model based on requirement integrity expression rules; requirement content constraint definition: support for structuring constraints on requirement content during the construction of a requirement model based on requirement integrity expression constraints; external requirement model integration: support for integrating external word (.docx), csv, reqif format requirement models; requirement integrity evaluation: the system has built-in requirement integrity evaluation criteria, which support users to evaluate the integrity of the requirement content in the externally integrated requirement model, output the requirement integrity evaluation results, and highlight the requirement content that does not meet the integrity rules; design process meta-model creation: support for constructing a design process meta-model based on graph, object, point, attribute, relationship, and role meta-meta-model and their constraints; design process model creation: based on the design process meta-model, support users to construct a design process model through dragging or configuration; model to ontology mapping: after the creation of the requirement model, the design process model, and the traceability relationship between them, support users to convert the graphical model data into OWL ontology data; ontology to model mapping: support users to read the integrated ontology and convert the OWL ontology data into graphical model data to complete the creation of the requirement, design process model, and the traceability relationship between them; ontology visualization: support for visualizing OWL ontology data through a graph atlas; requirement traceability relationship construction: support for obtaining requirement model, design process model information, and constructing the traceability relationship between them; or support for constructing the traceability relationship between them through the integrated ontology of requirements and design processes; requirement traceability evaluation: support for performing corresponding traceability evaluation based on the proposed requirement traceability evaluation criteria, and output the requirement traceability evaluation results.

[0047] The user interface layer provides the specific application of the design personnel by modeling and evaluating the requirements of the specific function combination of the business logic layer, and includes the following five applications: requirement modeling: supporting the construction of requirement entry models based on requirement integrity rules and constraints, and realizing the complete expression of requirement content; requirement integrity evaluation: supporting the evaluation of the integrity of requirement attribute content in the requirement model based on the proposed requirement integrity evaluation criteria; design process modeling: supporting the construction of design process meta-model and model based on the graph, object, point, attribute, relationship, role meta-model and constraint method; requirement and design process ontology integration: supporting the mutual conversion between the requirement model, system design process model, and the traceability relationship and integrated ontology between them, realizing the semantic consistency of the requirement model and design process model, supporting the semantic expression of requirement traceability; at the same time, supporting the visualization of the integrated ontology, and clearly showing the traceability relationship between the requirement model and design process model; requirement traceability expression and evaluation: supporting the construction of the traceability relationship between the requirement model and design process model; based on the defined requirement traceability evaluation criteria, the requirement traceability evaluation is performed on the integrated ontology, and the evaluation result is output.

[0048] One specific application of the embodiment is as follows: first, the design personnel integrates the external requirement model through the external requirement model integration submodule, and evaluates the requirement content through the requirement integrity evaluation submodule, and iteratively modifies the incomplete requirement through the requirement modeling module; or the design personnel directly constructs the requirement meeting the integrity through the requirement modeling module, ensures that the requirement modeling module outputs the requirement model meeting the integrity requirement, then guides the design process meta-model and model construction in the design process model construction module, then the requirement traceability relationship construction submodule realizes the construction of the traceability relationship between the two by calling the complete requirement model in the requirement modeling module and the design process model in the design process model construction module, on the basis of which, the model-to-ontology mapping module maps and converts the complete requirement model output by the requirement modeling module, the design process meta-model and model in the design process model construction module, and the traceability relationship in the requirement traceability relationship construction module into the integrated ontology, realizes the semantic consistent expression of the requirement model and design process model, thereby realizing the expression of requirement traceability, finally, the converted integrated ontology is output to the requirement traceability evaluation submodule to perform requirement traceability evaluation, and the integrated ontology is output to the ontology visualization submodule for atlas visualization display, in addition, the design personnel can map and convert the external integrated ontology into the requirement model in the requirement modeling module, the design process meta-model and model in the design process model construction module, and the traceability relationship in the requirement traceability relationship construction module through the ontology-to-model mapping submodule, to ensure the semantic consistency of the model.

[0049] It is worth noting that the above system embodiments, including each unit is only divided according to the functional logic, but is not limited to the above division, as long as the corresponding function can be realized; in addition, the specific name of each functional unit is only for the convenience of mutual distinction, and is not used to limit the protection scope of the present application.

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

[0051] The preferred embodiments of the application disclosed above are only used to help explain the application. The preferred embodiments do not describe all the details and do not limit the application to the specific embodiments described. Obviously, many modifications and variations can be made according to the content of the present application. The present application selects and describes these embodiments in order to better explain the principles and practical applications of the present application, so that those skilled in the art can well understand and utilize the present application. The present application is limited only by the claims and their full scope and equivalents.

Claims

1. An apparatus for supporting complex system requirement integrity modeling and evaluation, comprising requirement modeling, requirement integrity evaluation, design process modeling, requirement and design process ontology integration, requirement traceability expression and evaluation; characterized in that: the requirement modeling module comprises requirement entry model construction and requirement content constraint definition; the requirement modeling module function is to realize the creation of requirement model based on the 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 entry model construction submodule, and since the coupling degree between them is high, they are designed as a plug-in in the subsequent design; in order to realize the creation of requirement model that meets the 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, second, based on the requirement integrity expression criteria and constraints, the interface is designed again to support the creation of requirement model based on the requirement integrity expression criteria and constraints, and finally, based on the Eclipse RCP framework and Java programming language, the interface is developed, and the interface and the ProR project are packaged into the form of requirement modeling plug-in, which is integrated with the requirement modeling and evaluation system; the requirement entry model construction is responsible for supporting the requirement engineers to perform entry modeling of requirements according to the requirement integrity expression criteria; the requirement content constraint definition is responsible for supporting the requirement engineers to perform structural constraint on the requirement content in the requirement model creation process according to the defined requirement constraints, and to ensure the integrity of the requirement content in the requirement modeling process; the requirement integrity evaluation module comprises external requirement model integration and requirement integrity evaluation; the requirement integrity evaluation module function is to evaluate the integrity of the requirement content in the integrated external requirement model, and to ensure the integrity of the requirement content in the integrated external requirement model; in the requirement integrity evaluation module, the external requirement model integration submodule reads the requirement model information in the external word, csv and reqif formats through the interface; then the requirement model is integrated into the requirement entry model construction submodule through the interface, and the requirement integrity evaluation submodule reads the attribute content information of the requirement model in the requirement entry 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 requirement engineers to integrate external requirement models; the requirement modeling and evaluation system supports the integration of requirement models in word (.docx), csv, reqif formats. In order to realize the integration of external word, csv, reqif format requirement models, in the Eclipse modeling framework and jdk1.8 environment, first, the interface for reading the requirement model information in word (.docx), csv, reqif format needs to be designed and developed. The interface for reading the requirement model information in word (.docx) format is designed based on the Java library Apache POI; the interface for reading the requirement model information in csv format is designed based on the Java library OpenCSV; the reqif format requirement model can be directly integrated, and there is no need to design and develop it again. Then, the interface for generating the requirement model needs to be designed and developed. Since the underlying format of the requirement model is XML format, the Java third-party library dom4j is a Java XML library with rich functions, flexibility and ease of use, which is suitable for various XML document processing requirements, including parsing, creating, operating and querying. Therefore, dom4j is used to design and develop the interface for generating the requirement model. Finally, the development of these interfaces is realized based on the Eclipse RCP framework and Java programming language, and is packaged in the form of external requirement model integration plug-in, which is integrated with the requirement modeling and evaluation system. The requirement integrity evaluation is responsible for supporting requirement engineers to evaluate the integrity of the requirement content in the integrated external requirement model. In order to realize the integrity evaluation of the requirement attribute content in the requirement model, in the Eclipse modeling framework and jdk1.8 environment, first, the interface for reading the attribute content information of the requirement model in XML data format is designed and developed using the Java third-party library dom4j. Second, the Java interface of Stanford CoreNLP is called 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 analyzed and processed requirement attribute content text, regular expressions are used to construct the proposed requirement integrity constraints, the analyzed and processed requirement attribute content is matched with the evaluation criteria, and the matching result is output. After that, the evaluation result visualization function is designed and developed based on SWT to analyze the matching result and visually display 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 result in the console. Finally, the development of these interfaces and function modules is realized based on the Eclipse RCP framework and Java programming language, and is packaged in the form of requirement integrity evaluation plug-in, which is integrated with the requirement modeling and evaluation system. The design process modeling module includes design process meta-model construction and design process model construction. The function of the design process modeling module is to support the unified construction of design process models in different domains and different levels. In the design process modeling module, the design process model creating submodule reads the metamodel information in the design process metamodel creating submodule through an interface; graphical construction of the model is supported; 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 description, specifying the fixed syntax of the metamodel, i.e. the specific style of the model in the modeling environment, including the graphical shape, display text description and color; finally, the metamodel connection rule setting is configured, including "contain", "attribute connection", "binding" and "association", and the design process metamodel construction is completed; After the design process metamodel library construction is completed, the model construction can be performed using the metamodel, first, a graph model is created in the tool using the graph metamodel, and the modeling canvas can be seen by opening the graph metamodel, and the model construction is completed by dragging the object and relationship metamodel on the right side of the canvas; The design process metamodel creating is responsible for supporting the system engineer to construct the metamodel according to the existing modeling language, or to create the metamodel according to the field characteristics; The design process model creating is responsible for supporting the system engineer to construct the model using the metamodel; The requirement and design process ontology integration module includes model-to-ontology mapping, ontology-to-model mapping and ontology visualization; the function of the requirement and design process ontology integration module is to realize the semantic consistent expression of the requirement model and the design process model, thereby laying a foundation for the creation of the traceability relationship between the heterogeneous requirement model and the design process model; In the requirement and design process ontology integration module, the ontology-to-model mapping submodule reads the external integrated ontology information through an interface, and then generates the requirement model in the requirement itemized model construction submodule, the design process metamodel in the design process metamodel creating submodule, the design process model in the design process model creating submodule and the traceability relationship model in the requirement traceability relationship creating submodule through an interface; The model-to-ontology mapping submodule generates the integrated ontology by reading the requirement model in the requirement itemized model construction submodule, the design process metamodel in the design process metamodel creating submodule, the design process model in the design process model creating submodule and the traceability relationship in the requirement traceability relationship creating submodule through an interface, and the ontology visualization submodule reads the integrated ontology information through an interface and performs visual display; The model-to-ontology mapping is responsible for supporting the mapping conversion of the requirement model and the design process model into the integrated ontology, realizing the semantic consistent expression of the requirement model and the design process model; in order to realize the mapping conversion of the requirement model, the design process model and the traceability relationship therebetween into the integrated ontology, first, the interface capable of reading the requirement model, the design process model and the traceability relationship therebetween is needed; Secondly, the interface for generating the ontology is needed, the design process modeling tool provides the interface for generating the design process meta-model, the model, the interface for reading the requirement model and the interface for tracing the relationship, this paper uses the Java third-party library dom4j to design and develop the interface for reading the requirement model and the interface for tracing the relationship of the XML data format respectively, for the interface for generating the ontology, Jena is a Java third-party library for supporting RDF / RDFS and OWL, which provides a large number of interfaces for reading and generating the OWL format file, and can easily access and operate the class, instance and attribute information in the OWL, therefore, this paper uses Jena to design and develop the interface for generating the integrated ontology, finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language, and is packaged into the form of the model-to-ontology mapping plug-in, which is integrated with the requirement modeling and evaluation system; The ontology-to-model mapping is responsible for supporting the mapping and conversion of the integrated ontology of the requirement and the design process into the requirement model and the design process model, and ensuring the consistency of the model; in order to realize the mapping and conversion of the integrated ontology into the requirement model, the design process model and the tracing relationship between them in the requirement modeling and evaluation system, firstly, the interface for reading the ontology is needed, secondly, the interface for generating the requirement model, the design process model and the tracing relationship between them is needed, for the interface for reading the ontology, Jena is used to design and develop the interface for reading the integrated ontology, for the interface for generating the requirement model and the tracing relationship, dom4j is used to design and develop the interface for generating the requirement model and the tracing relationship of the XML data format respectively, the design process modeling tool provides the interface for generating the design process meta-model and the model, finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language, and is packaged into the form of the ontology-to-model mapping plug-in, which is integrated with the requirement modeling and evaluation system; The ontology visualization is responsible for supporting the graph visualization display of the requirement, the design process element and the relationship between them, so that the designer can clearly understand the tracing relationship between the requirement and the design process; in order to more intuitively and clearly display the tracing relationship between the requirement model and the design process model, the ontology visualization plug-in is developed to support the visualization graph display of the tracing relationship, firstly, the ontology reading interface developed in the ontology-to-model mapping plug-in is called to read the tracing relationship information of the requirement model and the design process model in the ontology; then, the ontology visualization graph plug-in is designed and developed based on the Eclipse Zest plug-in, finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language, and is packaged into the form of the ontology visualization plug-in, which is integrated with the requirement modeling and evaluation system; The requirement traceability expression and evaluation module includes the requirement tracing relationship construction and the requirement traceability evaluation; The function of the requirement traceability expression and evaluation module is to support the construction of the tracing relationship between the requirement and the design process and the evaluation of the requirement traceability; In the demand traceability expression and evaluation module, the demand traceability relationship construction submodule reads the demand model information of the demand entry modeling submodule through an interface, and reads the design process model information in the design process model construction submodule through an interface; the demand traceability evaluation submodule reads the integrated ontology information through an interface, and performs demand traceability evaluation; The demand traceability relationship construction is responsible for supporting the construction of the traceability relationship between the demand and the design process based on the integrated ontology, or constructing the traceability relationship between the demand model and the design process model in the system and mapping the traceability relationship between the demand and the design process in the integrated ontology; in order to realize the construction of the traceability relationship between the demand model and the design process model, firstly, the demand model and the design process model interface need to be read, for the demand model reading interface, the underlying data format of the demand model is XML, therefore, the demand model interface reading XML data format is designed and developed by using the Java third-party library dom4j; For the design process model reading interface, the design process modeling tool itself provides the design process metamodel in java data format, the model reading interface, which can support the reading of the design process model and the metamodel, secondly, the traceability relationship model interface needs to be generated, since the underlying storage format of the traceability relationship model is also XML data format, the traceability relationship model interface generating XML data format is also designed and developed by using dom4j, finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language, and is packaged in the form of a demand traceability relationship construction plug-in, which is integrated with the demand modeling and evaluation system; The demand traceability evaluation is responsible for supporting the demand engineers to evaluate the demand traceability based on the integrated ontology; in order to realize the evaluation of the demand traceability based on the integrated ontology, firstly, the integrated ontology interface needs to be read, the integrated ontology interface has been designed and developed based on Jena in the demand and design process ontology integration module, which can be called here, at the same time, Jena supports processing RDF data and executing SPARQL queries, therefore, the demand traceability evaluation interface based on SPARQL is designed by using Jena, finally, the development of these interfaces is realized based on the Eclipse RCP framework and the Java programming language, and is packaged in the form of a demand traceability evaluation plug-in, which is integrated with the demand modeling and evaluation system.

2. The apparatus of claim 1, wherein, The demand modeling and evaluation system includes four levels of data layer, core driving 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, which provides underlying data support for the realization of business logic driven by the core driving layer, including the following five kinds; XML data: used for storing demand models and traceability relationship models, supporting 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, reading and operating on XML documents through JAVA library DOM; at the same time, JAVA data supports interaction with OWL data, parsing and processing OWL ontology through JAVA library Jena; KARMA data: used to store design process meta-models and models, supporting mutual conversion with OWL data; Graph model data: used to store data of design process models in the canvas, including layout, objects, relationships, supporting mutual conversion with KARMA data; OWL data: used to store data information of the ontology, capable of supporting related functions related to ontology, semantic query and reasoning; supporting mutual conversion with XML data, JAVA data, KARMA data and graphical model data.

3. The apparatus of claim 2, wherein, The core driving layer is a key part of the system, directly interacting with the data layer, 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 the corresponding operations are executed according to the business requirements; the core driving layer includes the following eight core driving engines: ProR core engine: supports parsing and generating ReqIF requirement models in XML format; Requirement expression constraint engine: supports structuring constraints on requirement content based on the proposed requirement integrity expression constraints; CoreNLP engine: supports processing natural language requirement text, including word segmentation, part-of-speech tagging, named entity recognition, syntax analysis, and reference resolution 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 evaluation criteria; Meta-model interpretation engine: supports parsing system design process meta-models developed based on graph, object, point, attribute, relationship, and role meta-meta-models and their constraints; through this engine, the design meta-model is read and interpreted as a KARMA backend data structure, and a meta-model library is generated; Model interpretation engine: supports parsing design process models constructed based on design process meta-models; through this engine, the design process model is read and interpreted as a KARMA backend data structure, and conversion with graph model data is supported; Traceback engine: supports obtaining requirement model and design process model data, and establishing a traceback relationship between the requirement model and the design process model; Ontology engine: based on JAVA library Jena, the OWL ontology is parsed and processed, supporting mutual conversion between XML data, KARMA data and graph model data and OWL ontology data, and supporting query reasoning based on OWL data and visualization of OWL data.

4. The apparatus of claim 3, wherein, The business logic layer represents specific operations allowed to be completed by the user in the requirement modeling and evaluation system, driven by the core driving layer, participating in the implementation of business-level functions, the business logic layer includes the following eleven functions: Requirement entry modeling: supports building a requirement entry model based on requirement integrity expression rules; Requirement content constraint definition: support to express constraint on requirement content based on requirement integrity table during requirement modeling; External requirement model integration: support to integrate external requirement model in word(.docx), csv, reqif format; Requirement integrity evaluation: built-in requirement integrity evaluation criteria, support to evaluate the integrity of requirement content in external integrated requirement model, output requirement integrity evaluation result, and highlight the requirement content which does not meet the integrity rule; Design process meta-model creation: support to create design process meta-model based on graph, object, attribute, point, relationship, role meta-meta-model and constraint; Design process model creation: support to create design process model based on design process meta-model, by drag-and-drop or configuration; Model to ontology mapping: support to convert graphical model data to OWL ontology data after requirement model, design process model and their traceability relationship are created; Ontology to model mapping: support to convert OWL ontology data to graphical model data after integrated ontology is read, and complete the creation of requirement model, design process model and their traceability relationship; Ontology visualization: support to visualize OWL ontology data by graph; Requirement traceability relationship construction: support to construct traceability relationship between requirement model and design process model based on their information, or based on integrated ontology of requirement and design process; Requirement traceability evaluation: support to perform requirement traceability evaluation based on proposed requirement traceability evaluation criteria, and output requirement traceability evaluation result.

5. The apparatus of claim 4, wherein, The user interface layer provides specific applications for designers by combining specific functions of the business logic layer, and the user interface layer includes the following five applications: Requirement modeling: support to construct requirement entry model based on requirement integrity rule and constraint, and realize complete expression of requirement content; Requirement integrity evaluation: support to evaluate the integrity of requirement attribute content in requirement model based on proposed requirement integrity evaluation criteria; Design process modeling: support to construct design process meta-model and model based on graph, object, attribute, point, relationship, role meta-meta-model and constraint method; Requirement and design process ontology integration: support to convert between requirement model, system design process model, traceability relationship between them and integrated ontology, realize semantic consistency of requirement model and design process model, support semantic expression of requirement traceability; at the same time, support integrated ontology visualization, and clearly show the traceability relationship between requirement model and design process model; Requirement traceability expression and evaluation: support to construct traceability relationship between requirement model and design process model; For integrated ontology, perform requirement traceability evaluation based on defined requirement traceability evaluation criteria, and output evaluation result.

Images