CN119806870A - A Requirements Traceability Method Based on OSLC Standard - Google Patents

Abstract

The invention discloses a demand tracing method based on OSLC standard, which comprises the following steps of S1, developing a demand software adapter, S2, developing a modeling software adapter, S3, designing a client application to acquire and display data, S4, establishing a tracing relation between demand and a model, S5, inquiring and visually displaying the tracing relation, and S6, analyzing the influence of demand change. According to the invention, OSLC standards are fully utilized, seamless integration of heterogeneous tools can be realized without large-scale transformation by data standardization of required software and modeling software, so that the universality and interoperability among tools are greatly improved, the implementation cost is effectively reduced, the bidirectional traceability between the requirements and the models is provided, the required integrity and the model consistency are ensured, and the quality management capability in the system development process is remarkably improved.

Description

Demand tracing method based on OSLC standard

Technical Field

The invention belongs to the technical field of computer software, relates to a demand tracing method, and in particular relates to a demand tracing method based on OSLC (open service life cycle collaboration) standards.

Background

In the development process of modern complex systems, demand management and system modeling are two core links. Demand management tools (e.g., IBM DOORS, jama Connect) are widely used to capture and manage system demands, while modeling tools (e.g., MATLAB/Simulink, modelica, rhapsody) are used to translate demands into a system design model. With the expansion of the system scale and the increase of the complexity, traceability management between the requirements and the models becomes particularly important, which has important significance in ensuring that the requirements are correctly realized, reducing design defects and improving the development efficiency of the system. However, there is often a lack of efficient integration between the required software and modeling software, which is mainly manifested by the following problems:

1. The data island is that the demand management tool and the modeling tool usually run independently, and the data storage and management formats among different tools are different, so that the tools cannot interact directly, and an information island is generated.

2. The tracing is difficult, the relevance between the requirement and the model cannot be automatically maintained by tools, a development team needs to trace by relying on manual or external document recording, and the tracing error risk and management cost are increased.

3. Demand change management is difficult because when demand changes, models associated therewith cannot be quickly located and updated, which may lead to subsequent design deviations from demand.

To address these challenges OSLC is an open standard that provides a general solution for integration between heterogeneous tools. OSLC defines a unified resource model and an interface protocol by carrying out unified standardized description on resources, so that data interaction and collaboration between a demand management tool and a modeling tool are possible, and therefore, the demand tracing across tool chains can be supported.

In OSLC-based integration frameworks, requirements and models can be used as standardized resources, and mutually referenced through RESTful interfaces to construct a retrospective relationship across tool chains. However, in practical applications, there are significant differences in the interfaces and data formats of the different required software and modeling software, which results in a certain complexity and limitation of implementation using the OSLC standard directly. Therefore, developing an adapter conforming to OSLC standard, unifying the data format of heterogeneous tools, and establishing and maintaining a traceability relationship between the requirements and the model through the client becomes a key technical means for solving the problems.

Currently, related research and application of demand tracing are mainly focused on tracing relation management in a single tool chain, and a tracing solution based on OSLC is still in an exploration stage in a multi-tool chain and heterogeneous environment. Especially, how to realize efficient tracing and support the development requirement of complex systems in a standardized way between the required software and the modeling software is still a subject worthy of intensive research.

Disclosure of Invention

In order to realize demand tracing between demand software and modeling software and solve the problems of independent operation, data island and difficult tracing between demand and model of the existing tool, the invention provides a demand tracing method based on OSLC standard. The method designs a technical scheme that OSLC is standardized on data of demand software and modeling software through a development adapter, and a traceability relation between demand and a model is established through a client. Through the method and the system, a user can easily realize bidirectional traceability between the requirements and the model in a heterogeneous tool environment, and efficiency and consistency of a system development process are improved.

The invention aims at realizing the following technical scheme:

a demand tracing method based on OSLC standard comprises the following steps:

step S1, developing a demand software adapter, namely developing the demand software adapter aiming at a demand management tool, wherein the demand software adapter can access data of the demand management tool and convert the data into a resource description format conforming to OSLC standard, and providing a RESTful interface for a client to access, and the specific steps are as follows:

S1.1, carrying out demand analysis on an adapter, clearly developing an adapter system to acquire demand data in a demand management tool and standardizing the demand data OSLC, determining the type of resources to be exposed by the demand management tool and the service capacity of the resources after clearly determining the target, wherein for the demand management tool, core resources are demands, and management of the demands is main service provided by the demand management tool;

S1.2, defining a mapping relation between data to be exposed by a demand management tool and OSLC resources, wherein items in the demand management tool are organization units of demands, each item contains a large number of demands, the hierarchical relation is expressed in OSLC standard through a relation between ServiceProvider and ChangeRequest, the demands are mapped into ChangeRequest by mapping the items into ServiceProvider, a mapping relation model is built, the design of resource classes is unfolded after the mapping relation is determined, and the resources in a target system are modeled;

Step S1.3, developing the design of the adapter, comprising a functional design and a nonfunctional design, wherein the functional design mainly focuses on the realization of core service, namely data standardization, and the nonfunctional design focuses on the aspects of performance, usability, safety and expansibility of the system;

Step S1.4, realizing adapter service, including creating service provider and CRUD operation realization;

s1.5, authentication and security configuration are completed, wherein authentication and authorization of user identity are realized through an integrated OAuth protocol;

step S2, developing a modeling software adapter, namely developing the modeling software adapter aiming at a modeling tool, wherein the modeling software adapter can access model data of the modeling tool and standardize the model data into data conforming to OSLC resource formats, and provides a uniform access interface, and the specific steps are as follows:

S2.1, carrying out demand analysis on the adapter, clearly developing an adapter system to obtain model data in a modeling tool and standardizing the model data OSLC, determining the type of resources to be exposed by the modeling tool and the service capacity of the resources after clearly determining the target, wherein for the modeling tool, core resources are models, and management of the models is main service provided by the modeling tool;

S2.2, defining the mapping relation between the data to be exposed by the modeling tool and OSLC resources, namely mapping the model in the modeling tool into ChangeRequest in OSLC, mapping each model into an independent ChangeRequest example for adapting OSLC standard, wherein the mapping is realized by inheriting ChangeRequest types, and expanding the design of other resource types after determining the mapping relation;

Step S2.3, developing the design of the adapter, comprising a functional design and a nonfunctional design, wherein the functional design mainly focuses on the realization of core service, namely data standardization, and the nonfunctional design focuses on the aspects of performance, usability, safety and expansibility of the system;

Step S2.4, realizing the adapter service, including creating the realization of service provider and CRUD operation;

s2.5, authentication and security configuration are completed, wherein authentication and authorization of user identity are realized through an integrated OAuth protocol;

Step S3, designing a client application to acquire and display data, wherein the client application acquires data resources meeting OSLC standards by calling an adapter interface of demand software and modeling software, realizes a data analysis function in a client, displays the acquired demand data in a list form, and displays the modeling data in a graphical form, and the method comprises the following specific steps of:

Step S3.1, the client application acquires data resources meeting OSLC standard by calling an adapter interface of a demand tool and a modeling tool, wherein the data formats directly supported by OSLC are RDF, JSON and XML;

step S3.2, the client application needs to design analysis modules aiming at the demand data and the modeling data respectively, extracts key information in the analysis modules, displays the analyzed data in a list form, provides an intuitive table or tree view for the demand data, and is used for displaying the hierarchical relationship and detailed information of the demand;

And S4, establishing a traceability relation between the requirements and the models, namely realizing the establishment and management of the traceability relation between the requirements and the models through the client, storing the traceability relation established in the client by a user into a traceability relation database, updating data in an adapter, ensuring long-term maintenance and usability of the traceability relation, and facilitating consistency check, wherein the method comprises the following specific steps of:

S4.1, defining a plurality of traceability relation types to meet the requirements of system engineering, including dependency relation, realization relation and verification relation, wherein a user manually selects the requirements and model elements through a client interface, creates the traceability relation and designates the types thereof;

S4.2, storing a traceability relation established by a user in the client into a traceability relation database, and simultaneously updating data of related resources in the adapter, wherein the traceability relation database comprises a key table structure including a requirement table, a model element table and a relation table;

step S5, realizing the query and visual display of the traceability relation, wherein the client supports the two-way traceability of the requirements and the models and can be displayed by a graphical interface by starting from a certain requirement of the requirement management tool and querying modeling tool model elements related to the requirements or starting from a certain model element of the modeling tool and tracing back to the corresponding requirement, and the specific steps are as follows:

Step S5.1, realizing a query function comprises a requirement-to-model query and a model-to-requirement query, wherein in the requirement-to-model query, a user selects a certain requirement in a requirement management tool, and a client automatically retrieves all model elements related to the certain requirement, and supports a condition screening and fuzzy search function; in the inquiry from the model to the requirement, a user selects a certain model element in a client, and the client backtracks to a requirement list associated with the client to support model element type screening and hierarchical navigation;

Step S5.2, the query result is displayed in a topological graph or relationship graph form, nodes represent requirements or model elements, edges represent the traceability relationship between the requirements or model elements, colors or line types are used for distinguishing relationship types, the interactive operation is supported by the graph, besides, the query result is displayed in a matrix form by the client support, the lines represent the requirements elements, the columns represent the model elements, and if the traceability relationship exists, the traceability relationship is represented in a corresponding cell by a special mark;

S5.3, the query result is exported into PDF, excel or image files, so that analysis and archiving are facilitated, and a client generates a visual traceability relation report according to the query result, wherein the visual traceability relation report comprises a chart, a data table and an analysis abstract;

S6, realizing demand change influence analysis, namely analyzing the influence of demand change on a model based on the established traceability relation, traversing the traceability relation, determining the influenced model resource and displaying the influenced model resource in an interface, wherein the specific steps are as follows:

step S6.1, when the demand of the client is changed, the system automatically traverses the traceability relation related to the demand, positions the model elements directly related to the demand, further analyzes the interaction relation of the model elements, and identifies indirectly influenced model resources;

And S6.2, classifying the model resources directly related to the change demands as direct influences and classifying the model resources caused by the interaction relationship of the directly related resources as indirect influences according to the influence scope by the system.

Compared with the prior art, the invention has the following advantages:

1. According to the invention, the standard OSLC is fully utilized, and the heterogeneous tool integration is supported, namely, the data standardization of the demand software and the modeling software is realized through the OSLC standard, the universality and the interoperability of the data are improved, the seamless butt joint of the demand software and the modeling software is realized, the integration of the heterogeneous tool can be realized without large-scale reconstruction of the existing tool, and the implementation cost is greatly reduced.

2. The invention provides forward and backward traceability between the requirements and the model, ensures the integrity of the requirements and the consistency of the model, remarkably improves the quality management capability in the system development process, and simplifies the development and verification process of the complex system.

3. The invention can freely define and modify the traceability relation between the requirement and the model at the client, and uniformly manage the traceability relation through the database, support the version control and the change management of the requirement and the model, and adapt to the requirements of different development flows.

4. The invention reduces the impact of the requirement change on the system development and improves the maintainability of the system through the automatic influence range analysis. Meanwhile, through the standardized interface, the invention promotes the efficient cooperation of the demand management team and the modeling team, reduces the information island phenomenon, and is beneficial to the efficient development of a complex system.

5. The invention has high flexibility in the development of the adapter and the design of the client, can be customized and expanded according to different required software and modeling tools, and is suitable for various development scenes. Meanwhile, the adapter design and the client side architecture support integration of more tools in the future, and a good development space is provided for complex system engineering.

Drawings

FIG. 1 is a flow chart of a demand traceability method based on OSLC;

FIG. 2 is a workflow diagram of an adapter, including a requirements tool adapter and a modeling tool adapter;

FIG. 3 is a diagram of an example modeling of demand resources in a demand tool adapter;

FIG. 4 is a development flow diagram of an adapter;

FIG. 5 is a diagram of modeling examples of model resources in a modeling tool adapter, (a) is a diagram of examples of use in sysml, where the Actor class and UseCase class used by the attributes require user definition, (b) is a diagram of examples of modeling examples of attributes UseCase in (a), and (c) is a diagram of examples of modeling examples of blocks in sysml;

FIG. 6 is an exemplary diagram of service provider data resources converted to conform to OSLC standard, (a) data resources in RDF+XML format, (b) data resources in JSON format, and (c) data resources in XML format;

Fig. 7 is a functional block diagram of a demand traceback client.

Detailed Description

The following description of the present invention is provided with reference to the accompanying drawings, but is not limited to the following description, and any modifications or equivalent substitutions of the present invention should be included in the scope of the present invention without departing from the spirit and scope of the present invention.

The invention provides a demand tracing method based on OSLC standard, which comprises the following steps:

step S1, developing a demand software adapter aiming at a demand management tool (such as IBM DOORS and Jama Connect), wherein the demand software adapter can access data of the demand management tool and convert the data into a resource description format conforming to OSLC standard, and provides a RESTful interface for a client to access, and the workflow of the demand software adapter is shown in figure 2. This step is one of the basis of the entire traceback process, ensuring that the acquired data OSLC can be standardized to support subsequent interactions and tracebacks.

In this step, development of the required software adapter is realized based on Eclipse Lyo SDK and invoking OSLC methods in library. The development of the demand software adapter is to complete the data standardization of the demand management tool, that is, the data source of the demand software adapter is the demand management tool, and OSLC resources meeting OSLC standard are obtained after the demand software adapter is used for standardizing the source data.

In this step, the function of the demand software adapter is to act as a bridge between the client and the demand management tool, enabling them to work cooperatively under a unified standard, which plays a central role in system integration. Before developing the required software adapter, it is necessary to specify the data to be exposed by the requirement management tool and its mapping relationship with OSLC resources. The method is a key step for requiring software adapter design, and because the correct mapping relation can ensure the semantic consistency of data, the interoperability and expansibility of the system can be greatly improved. If the mapping relation is improper, the data semantic loss may be caused, so that a user misunderstands or the data docking between tools fails, thereby destroying the collaboration of the whole tool chain and bringing additional burden to subsequent expansion and maintenance.

In this step, for the requirement management tool, its core function is typically to record, manage and track the requirements in the project. Items in the demand management tool are often organizational units of demands, each item containing a large number of demands. This hierarchical relationship may be expressed in OSLC standards by the relationship of ServiceProvider and ChangeRequest.

In the OSLC standard, serviceProvider is a type of resource that represents a provider of a service or a collection of resources in a particular context. For a demand management tool, an item is often a logical grouping unit of demand, which defines an independent range of demand. Mapping the items to ServiceProvider can clearly reflect this grouping structure, providing a clear context for subsequent demand management and retrospective relationship establishment. In a multi-project environment, the requirements of different projects can be separately managed through different servicepaviders, so that the flexibility of the system is enhanced. Each ServiceProvider can independently expose a specific set of requirements, and the requirements software adapter can control access rights of data according to item scope.

In OSLC, changeRequest is a resource type that describes specific requirements, change requests, flaws, or improvement suggestions. Each requirement in the requirement management tool can be mapped to one ChangeRequest because the semantics of the two are highly consistent in that each requirement typically contains information such as identification, title, description, status, priority, etc., which can be mapped directly to attributes of ChangeRequest. Second, changeRequest provides rich extension attributes that can map various specific fields of the requirements, supporting flexible extensions. After the requirements are exposed in ChangeRequest form, unified data flows can be established with other OSLC compatible tools, so that the collaboration capability of the system is enhanced.

In this step, a mapping relation model with clear logic and consistent semantics can be constructed by mapping the item to ServiceProvider and the requirement to ChangeRequest. The mapping mode can exert the advantages of OSLC standard to the maximum extent, and lays a solid foundation for the data interoperability between the demand management tool and other engineering tools.

In this step, after the mapping relationship is determined, the resource can be modeled, that is, the OSLC representation of the resource in the target system is defined, and in this step, OSLC annotations (such as @ OslcName, @ OslcNamespace) can be used to define the resource class. FIG. 3 is an example of demand resource modeling, in which an attribute state is used to indicate whether the current demand is successfully traced back, and if so, the value is true, otherwise false, and an attribute father is used to indicate the parent demand of the current demand, and if the current demand is the top-level demand, the value father is-1. The use of OSLC notes above the Get method provides a description and specification of each attribute, where @ OslcOccurs is used to specify the number of occurrences of the attribute. Service capabilities are then implemented OSLC, including query capabilities, creation capabilities, update capabilities, and provided RESTfulAPI. A specific required software adapter development flow is shown in fig. 4.

And S2, developing a modeling software adapter aiming at a modeling tool (such as Simulink, modelica, rhapsody), wherein the modeling software adapter can access model data of the modeling tool and standardize the model data into data conforming to a OSLC resource format, and a unified access interface is provided. This step is one of the bases of the trace back, ensuring that the acquired model data OSLC can be normalized.

In this step, the development of the modeling software adapter is realized based on Eclipse Lyo SDK, calling OSLC methods in library. The development of the modeling software adapter is to complete the data standardization of the modeling tool, namely, the data source of the modeling software adapter is the modeling tool, and OSLC resources meeting OSLC standards are obtained after the source data is standardized through the modeling software adapter.

In this step, models are the design elements of the core when modeling tool adapters are constructed, and these models need to be mapped with the resource types defined by OSLC standards to ensure interoperability of data between different tools. Each model often involves multiple systems or subsystems in the modeling software and may have multiple different representations or versions, so to be consistent with the OSLC resource model, the model is mapped as ChangeRequest in OSLC.

ChangeRequest is a resource type that is typically used to represent a particular change request or demand item in OSLC. In modeling software, each model needs to be mapped into a separate ChangeRequest instance in order to adapt OSLC standards, although the model itself is not directly equivalent to the change request. This mapping may be implemented by inheriting ChangeRequest classes to provide specialized extension or customization properties for each type of model or model element. For example, a particular model or module in modeling software may be made to conform to the standard format of OSLC by inheriting the ChangeRequest classes and adding new fields (e.g., model version, state, belonging components) to it, while not losing the semantics of the original model.

In this step, serviceProvider is used as a core component of OSLC, and is mainly used for providing services for resources, such as resource creation, updating and query functions. However, serviceProvider does not map directly to a specific concept in modeling software, but rather designs around resources. Its purpose is to provide a unified interface through which clients can interact with different types of resources (e.g., models). Thus, service providers need to pay attention to how to provide services for these resources at design time, without having to be tightly bound to specific model types or concepts in the modeling software. The design makes ServiceProvider more universal and flexible, and can provide consistent access modes for various types of resources.

In this step, a special attribute is added to the model resource to represent the association or trace-back path between the model and the demand. However, in the preliminary phase of resource conversion, this traceback attribute is typically null, since the specific establishment of the traceback relationship is done in the client. The client establishes an association between the model and the demand through an interactive interface or based on business logic, and stores these retrospective relationships in a database. In this way, the client can ensure accurate traceability between the model and the demand, and can maintain dynamic update and management of traceability relations. An example of modeling of a model resource is shown in fig. 5, where (a) is a diagram of examples of use cases in sysml, where the relationship between the executor and the use cases is represented in an Actor class, and the relationship between the use cases is shown in UseCase class, (b) is an example of modeling of an attribute UseCase in (a), and the relationship between the use cases is represented by a List, and (c) is a diagram of examples of modeling of blocks in sysml.

And step S3, designing a client application to acquire and display data, wherein the client application acquires data resources meeting OSLC standards by calling an adapter interface of the requirement software and the modeling software. And realizing a data analysis function in the client, displaying the acquired demand data in a list form, and displaying the modeling data in a graphical form.

In this step, the client application obtains the data resource meeting OSLC standard by calling the adaptor interfaces of the demand tool and the modeling tool, and the data formats directly supported by OSLC are three types, namely RDF, JSON and XML. Fig. 6 is an example of service provider data.

In this step, the client application needs to design an parsing module for the demand data and the modeling data, and extract the key information therein, and convert the key information into a format suitable for display. The suggestion client displays the requirement data in a list form to provide an intuitive table or tree view for displaying the hierarchical relationship and detailed information of the requirement, and displays the model data in a topological graph, a flow chart or other interactive views by using a graphical tool (such as D3.js, plotly or an embedded graph library) to display the interactive relationship among the system components.

In the step, in order to improve the flexibility and expandability of the system, a modularized architecture is adopted, a client application is divided into three modules, namely a data processing module, a demand tracing module and a demand change influence analysis module, wherein the data processing module is mainly responsible for data acquisition, analysis and display of the system and is the basis of demand tracing and analysis, the client acquires data from an adapter and then analyzes the acquired data and displays the acquired data in various forms, the demand tracing module is mainly responsible for establishing and maintaining a tracing relation between demands and a model, ensuring the traceability and consistency of the demands and comprises a tracing relation establishment function, a consistency check function and a tracing relation display function, and the demand change influence analysis module is used for analyzing potential influences of demand change on the model and other demands and comprises searching the affected model and the model with the affected display. A functional block diagram of the client is shown in fig. 7.

In the step, OSLC J or other open source libraries supporting OSLC standard are used for realizing data interface calling and analysis in client application development, a user interface is developed by adopting a modern front-end technical stack (such as compact, vue. Js or Angular), graphical presentation of modeling data is realized by combining a graphical library (such as D3.js or Cytoscape. Js), and a rear-end service is constructed by using Spring Boot or Flask and other lightweight frames to provide data support for the front end.

S4, establishing a traceability relation between the requirements and the models, namely realizing establishment and management of the traceability relation between the requirements and the models through the client, storing the traceability relation established in the client by a user into a traceability relation database, updating data in an adapter, ensuring long-term maintenance and usability of the traceability relation, and facilitating consistency check;

In this step, a plurality of trace back relationship types are defined to meet the requirements of system engineering, including dependency relationships, implementation relationships, and verification relationships. The user can manually select the requirements and model elements through the client interface, create retrospective relationships and specify their types. In the manual creation process, the client may provide suggested retrospective relationships for the user to confirm or edit.

In the step, the traceable relation database needs to contain the following key table structures including a requirement table for storing information such as unique identification, name, priority and the like of the requirement, a model element table for storing information such as unique identification, type, description and the like of the model element, and a relation table for storing relation information between the requirement and the model, wherein the relation table comprises relation types and metadata (such as creation time and maintainer). The data of the relevant resources in the adapter are also changed after the traceability relation is established.

And S5, inquiring and visually displaying the traceability relation, namely, the client supports to inquire modeling tool model elements related to the requirements from a certain requirement of the requirement management tool or to trace back the corresponding requirements from a certain model element of the modeling tool, so that the requirements and the models can be traced back bidirectionally and displayed in a graphical interface.

In this step, the implementation of the query function includes a demand-to-model query and a model-to-demand query. In the model-to-demand query, the user selects a certain model element in the client, the client backtracks to a demand list associated with the client, and the model element type screening (such as components, interfaces and signals) and hierarchical navigation are supported.

In this step, the query result may be displayed in the form of a topological graph or a relational graph, the nodes represent requirements or model elements, the edges represent traceable relationships between the two, and the relationship types are distinguished by using colors or lines, so that interactive operations, such as dragging, scaling and clicking on the nodes to view details, are graphically supported. In addition, the client supports displaying the query result in a matrix form, wherein the rows represent the requirement elements, the columns represent the model elements, and if a traceability relationship exists, the corresponding cells are represented by special marks.

In the step, the query result can be exported into PDF, excel or image files, so that analysis and archiving are facilitated, and the client generates a visual traceability relation report according to the query result, wherein the visual traceability relation report comprises a chart, a data table and an analysis abstract.

And S6, realizing demand change influence analysis, namely analyzing the influence of demand change on the model based on the established traceability relationship, traversing the traceability relationship, determining the influenced model resources and displaying the influenced model resources in the interface.

In this step, when the demand of the client is changed, the system automatically traverses the traceability relation related to the demand, locates the model elements directly related to the demand, further analyzes the interaction relation of the model elements, and identifies indirectly affected model resources. The system classifies model resources directly related to the change demands as direct influences and classifies model resources caused by interaction relations of the directly related resources as indirect influences according to the influence scope.

According to the invention, OSLC standards are fully utilized, seamless integration of heterogeneous tools can be realized without large-scale transformation by data standardization of required software and modeling software, so that the universality and interoperability among tools are greatly improved, the implementation cost is effectively reduced, the bidirectional traceability between the requirements and the models is provided, the required integrity and the model consistency are ensured, and the quality management capability in the system development process is remarkably improved. Meanwhile, the invention can flexibly define and manage the traceability relation between the requirements and the model, support version control and change management, adapt to various development flow requirements, improve the maintainability of the system through automatic change influence analysis tools, promote team cooperation, reduce information island phenomenon and assist the efficient development of the complex system. In addition, the invention has high expandability, the design of the adapter and the client can be customized according to different requirements, and the invention can support the integration of more tools in the future, thereby providing a wide development space for complex system engineering.

Examples:

The embodiment provides a demand tracing method realized by using the flow, which specifically comprises the following steps:

Step A1, acquiring demand data in a demand management tool based on a demand software adapter which is developed in step S1 and can be in a unified data format, and converting the demand data into standardized data which accords with OSLC resource description formats, wherein the standardized data is usually in RDF, JSON or XML formats;

Step A2, model data in a modeling tool is obtained based on the modeling software adapter developed in the step S2, and is converted into a resource description format conforming to OSLC standard;

Step A3, obtaining OSLC standardized requirements and model data through a RESTful interface of an interactive interface call adapter in a client, and analyzing and displaying the data;

Step A4, selecting a demand resource and a modeling resource in a client interface, establishing a traceability relation for the selected resource, defining a relation type of the traceability relation, such as 'implementation', 'dependence' or 'implementation', updating the traceability relation to an adapter through a OSLC interface, and storing the traceability relation in a client database;

Step A5, consistency checking is carried out, and uncovered requirements or isolated models are marked;

And A6, carrying out demand change influence analysis, detecting the change of demand data, analyzing the influenced model resources through a traceable relation, and marking the influenced model resources.

Claims (8)

1. A demand tracing method based on OSLC standard is characterized by comprising the following steps:

Step S1, developing a demand software adapter, namely developing the demand software adapter aiming at a demand management tool, wherein the demand software adapter can access data of the demand management tool and convert the data into a resource description format conforming to OSLC standard, and providing a RESTful interface for a client to access;

Step S2, developing a modeling software adapter, namely developing the modeling software adapter aiming at a modeling tool, wherein the modeling software adapter can access model data of the modeling tool and standardize the model data into data conforming to OSLC resource formats, and a unified access interface is provided;

Step S3, designing a client application to acquire and display data, wherein the client application acquires data resources meeting OSLC standards by calling an adapter interface of the demand software and the modeling software, realizes a data analysis function in the client, displays the acquired demand data in a list form, and displays the modeling data in a graphical form;

S4, establishing a traceability relation between the requirements and the models, namely realizing establishment and management of the traceability relation between the requirements and the models through the client, storing the traceability relation established in the client by a user into a traceability relation database, updating data in an adapter, ensuring long-term maintenance and usability of the traceability relation, and facilitating consistency check;

Step S5, inquiring and visually displaying the traceability relation is realized, wherein the client supports to inquire modeling tool model elements related to the requirements from a certain requirement of a requirement management tool or to trace back the corresponding requirement from a certain model element of the modeling tool, so that the requirements and the models can be traced back in a bidirectional manner and displayed in a graphical interface;

and S6, realizing demand change influence analysis, namely analyzing the influence of demand change on the model based on the established traceability relation, traversing the traceability relation, determining the influenced model resource and displaying the influenced model resource in the interface.

2. The demand traceability method based on OSLC standard according to claim 1, wherein the specific steps of step S1 are as follows:

S1.1, carrying out demand analysis on an adapter, clearly developing an adapter system to acquire demand data in a demand management tool and standardizing the demand data OSLC, determining the type of resources to be exposed by the demand management tool and the service capacity of the resources after clearly determining the target, wherein for the demand management tool, core resources are demands, and management of the demands is main service provided by the demand management tool;

S1.2, defining a mapping relation between data to be exposed by a demand management tool and OSLC resources, wherein items in the demand management tool are organization units of demands, each item contains a large number of demands, the hierarchical relation is expressed in OSLC standard through a relation between ServiceProvider and ChangeRequest, the demands are mapped into ChangeRequest by mapping the items into ServiceProvider, a mapping relation model is built, the design of resource classes is unfolded after the mapping relation is determined, and the resources in a target system are modeled;

Step S1.3, developing the design of the adapter, comprising a functional design and a nonfunctional design, wherein the functional design mainly focuses on the realization of core service, namely data standardization, and the nonfunctional design focuses on the aspects of performance, usability, safety and expansibility of the system;

Step S1.4, realizing adapter service, including creating service provider and CRUD operation realization;

And S1.5, finishing authentication and security configuration, wherein the authentication and authorization of the user identity are realized through an integrated OAuth protocol.

3. The demand traceability method based on OSLC standard according to claim 1, wherein the specific steps of step 2 are as follows:

S2.1, carrying out demand analysis on the adapter, clearly developing an adapter system to obtain model data in a modeling tool and standardizing the model data OSLC, determining the type of resources to be exposed by the modeling tool and the service capacity of the resources after clearly determining the target, wherein for the modeling tool, core resources are models, and management of the models is main service provided by the modeling tool;

S2.2, defining the mapping relation between the data to be exposed by the modeling tool and OSLC resources, namely mapping the model in the modeling tool into ChangeRequest in OSLC, mapping each model into an independent ChangeRequest example for adapting OSLC standard, wherein the mapping is realized by inheriting ChangeRequest types, and expanding the design of other resource types after determining the mapping relation;

Step S2.3, developing the design of the adapter, comprising a functional design and a nonfunctional design, wherein the functional design mainly focuses on the realization of core service, namely data standardization, and the nonfunctional design focuses on the aspects of performance, usability, safety and expansibility of the system;

Step S2.4, realizing the adapter service, including creating the realization of service provider and CRUD operation;

and S2.5, authentication and security configuration are completed, wherein authentication and authorization of the user identity are realized through an integrated OAuth protocol.

4. The demand traceability method based on OSLC standard according to claim 1, wherein the specific steps of step S3 are as follows:

Step S3.1, the client application acquires data resources meeting OSLC standard by calling an adapter interface of a demand tool and a modeling tool;

Step S3.2, the client application needs to design analysis modules aiming at the demand data and the modeling data respectively, extracts key information in the analysis modules, displays the analyzed data in a list form, provides an intuitive table or tree view for the demand data, is used for displaying the hierarchical relationship and detailed information of the demand, and displays the interactive relationship among the system components by utilizing a graphical tool and displaying the model data in a topological graph, a flow chart or other interactive views.

5. The method for tracing back requirements based on OSLC standard according to claim 4, wherein said OSLC directly supports three data formats of RDF, JSON and XML.

6. The demand traceability method based on OSLC standard according to claim 1, wherein the specific steps of step S4 are as follows:

S4.1, defining a plurality of traceability relation types to meet the requirements of system engineering, including dependency relation, realization relation and verification relation, wherein a user manually selects the requirements and model elements through a client interface, creates the traceability relation and designates the types thereof;

and S4.2, storing the traceability relation established by the user in the client into a traceability relation database, and simultaneously updating the data of the related resources in the adapter, wherein the traceability relation database comprises the following key table structures, namely a requirement table, a model element table and a relation table.

7. The demand traceability method based on OSLC standard according to claim 1, wherein the specific steps of step S5 are as follows:

Step S5.1, realizing a query function comprises a requirement-to-model query and a model-to-requirement query, wherein in the requirement-to-model query, a user selects a certain requirement in a requirement management tool, and a client automatically retrieves all model elements related to the certain requirement, and supports a condition screening and fuzzy search function; in the inquiry from the model to the requirement, a user selects a certain model element in a client, and the client backtracks to a requirement list associated with the client to support model element type screening and hierarchical navigation;

Step S5.2, the query result is displayed in a topological graph or relationship graph form, nodes represent requirements or model elements, edges represent the traceability relationship between the requirements or model elements, colors or line types are used for distinguishing relationship types, the interactive operation is supported by the graph, besides, the query result is displayed in a matrix form by the client support, the lines represent the requirements elements, the columns represent the model elements, and if the traceability relationship exists, the traceability relationship is represented in a corresponding cell by a special mark;

And S5.3, the query result is exported into PDF, excel or image files, so that analysis and archiving are facilitated, and the client generates a visual traceability relation report according to the query result, wherein the visual traceability relation report comprises a chart, a data table and an analysis abstract.

8. The demand traceability method based on OSLC standard according to claim 1, wherein the specific steps of step S6 are as follows:

step S6.1, when the demand of the client is changed, the system automatically traverses the traceability relation related to the demand, positions the model elements directly related to the demand, further analyzes the interaction relation of the model elements, and identifies indirectly influenced model resources;

And S6.2, classifying the model resources directly related to the change demands as direct influences and classifying the model resources caused by the interaction relationship of the directly related resources as indirect influences according to the influence scope by the system.