Integration method and device of demand modeling tool and demand management system, and medium

Abstract

The invention belongs to the field of document tool integration, and relates to an integration method and device of a demand modeling tool and a demand management system and a medium. Comprising a data interface standard, a data format requirement, a data transmission protocol, a data conversion rule and a data adaptation requirement meeting a demand scene; analyzing the modeling tool, analyzing an engineering file in the tool, performing data model mapping with a demand management system, and establishing a relationship between the model engineering and the demand management system; and importing data of a demand management system through an interface by using a demand modeling tool, and performing entries of data management. According to the method, a unified integration specification is provided, data of modeling tools are effectively mapped to the demand management system, received demand information is tracked, monitored and managed in the demand management system, the difficulty of transmission and sharing of the demand information among different tools is broken through, management of the demand information is effectively improved, and the demand management efficiency is improved. The efficiency and accuracy of demand management are greatly improved, and efficient integration and cooperative work are realized.

Description

Technical Field

[0001] This invention belongs to the field of document tool integration, and relates to a method, apparatus and medium for integrating a requirements modeling tool and a requirements management system. Background Technology

[0002] Currently, requirement modeling tools and requirement management systems play crucial roles in software development and project management. However, most requirement modeling tools and requirement management systems currently operate independently, lacking effective integration methods. This situation leads to several problems, including: Information transfer barriers: Requirements information is difficult to transfer smoothly between different tools. When requirements are adjusted or optimized in the requirements modeling tool, these changes cannot be synchronized to the requirements management system in a timely and accurate manner. This results in discrepancies in the requirements information obtained by the development team at different stages, easily leading to misunderstandings and incorrect judgments.

[0003] Data sharing difficulties: Due to a lack of integration, big data in requirements modeling tools and requirements management systems cannot be shared. This not only results in duplicate data entry, wasting a significant amount of time and manpower, but also easily leads to data inconsistencies.

[0004] Low collaboration efficiency: Independently operated tools create numerous inconveniences for project team members when collaborating. Members in different roles need to switch back and forth between multiple tools to obtain complete requirements-related information, which significantly reduces work efficiency. At the same time, the lack of a unified platform for communication and collaboration also increases communication costs and the risk of information omissions. Summary of the Invention

[0005] The technical problem solved by this invention is to address the issues of information transmission barriers, data sharing difficulties, and low collaboration efficiency that exist in most current independent demand modeling tools and demand management systems. Therefore, the purpose of this invention is to provide a method, apparatus, and storage medium for integrating demand modeling tools and demand management systems. This invention provides a unified integration standard that effectively maps data from modeling tools to the demand management system, and tracks, monitors, and manages received demand information within the demand management system. This breaks down the difficulties in transmitting and sharing demand information between different tools, effectively improves the management of demand information, greatly enhances the efficiency and accuracy of demand management, and achieves highly efficient integration and collaborative work.

[0006] Technical solution of the present invention A method for integrating a requirements modeling tool with a requirements management system includes the following steps: Step S1: Define the model according to the requirements management system and create a modeling tool integration specification, including data interface standards, data format requirements, data transmission protocols, data conversion rules, and data adaptation requirements that meet the requirements scenario; Step S2: Analyze the modeling tool, parse the project files in the tool, map the data model with the requirements management system, and establish the relationship between the model project and the requirements management system; Step S3: Use the requirements modeling tool to import data from the requirements management system through the interface for itemized data management.

[0007] Furthermore, step S1 includes: Step S1.1: Analyze the data structure and requirement model of the requirement management system, and clarify its components, including requirement items, data elements contained in the items, and relationships between items; Step S1.2: Design a unified model definition, which includes requirement items, data elements, and relationships between items; Step S1.3: Define the modeling tool integration specifications.

[0008] Furthermore, step S1.2 includes: Step S1.2.1: Design multiple requirement item models to store different requirement data; Step S1.2.2: Design the data elements for each requirement item, including element storage type, retrieval method, validity check rules, length / size, and default value.

[0009] Furthermore, step S1.3 includes: Step S1.3.1: Define the data format specification, which includes the order of requirement item elements, the representation method, length, encoding format, and verification method of item elements; Step S1.3.2: Define the interface and communication protocol between the requirements modeling tool and the requirements management system; Step S1.3.2 includes: Step S1.3.2.1: Define the format of the interface, including URL structure, request format, response format, return code, parameter description, and exception information; Step S1.3.2.2: Define the communication protocol, including the requirements for each process of data sending, receiving, processing and verification, as well as performance, real-time and reliability requirements.

[0010] Furthermore, step S2 includes: Step S2.1: Analyze the modeling tool, parse the project files in the model, and parse the information including model structure, images, file objects, text, and attributes in the model; Step S2.2: Map the parsed modeling tools to the requirements management system. This mapping includes: (1) The mapping includes the mapping between model engineering files and the management structure of the requirements management system; (2) Mapping includes the mapping between model structure and requirement items; (3) Mapping of images, file objects, text, attribute element information and entry data elements in the model; Step S2.3: According to the modeling tool integration specifications, convert and adapt the parsed data to the correct format. Furthermore, step S2.3 includes: Step S2.3.1: During the conversion and adaptation process, the data is verified in real time to ensure the quality and availability of the data; Step S2.3.2: During the conversion and adaptation process, clean the data to remove redundant, duplicate, or invalid information; Step S2.3.3: During the conversion and adaptation process, ensure that the converted data meets the requirements of the target format, including data structure, field naming, and data type.

[0011] Furthermore, step S3 includes: Step S3.1: Import the adapted data information into the requirements management system; Step S3.2: Establish a tracking relationship for each required data entry, wherein the tracking relationship includes: (1) Tracking information for model engineering and management structures; (2) Tracking information of model structure and requirement items; (3) Tracking information of images, file objects, text, attribute elements and entry data elements in the model; Step S3.3: Provide query, statistics and analysis functions in the demand management system to help users manage and utilize demand information.

[0012] An apparatus for use in the integration method, comprising: The model definition and specification creation module is used to define models according to the requirements management system and create modeling tool integration specifications, including data interface standards, data format requirements, data transmission protocols, data conversion rules, and data adaptation requirements that meet the requirements scenarios. The analysis module is used to analyze the modeling tools, parse the project files in the tools, map the data model with the requirements management system, and establish the relationship between the model project and the requirements management system. The data management module is used to import data from the requirements management system through an interface using the requirements modeling tool, and to perform itemized data management.

[0013] A computer storage medium storing computer-executable instructions that, when executed by a processor, implement the integrated method described above.

[0014] Beneficial effects This invention provides a method, apparatus, and medium for integrating a requirement modeling tool with a requirement management system. It provides a unified integration standard, effectively maps the data from the modeling tool to the requirement management system, and tracks, monitors, and manages the received requirement information within the requirement management system. This breaks down the difficulties in transmitting and sharing requirement information between different tools, effectively improves the management of requirement information, greatly enhances the efficiency and accuracy of requirement management, and achieves efficient integration and collaborative work.

[0015] The method and apparatus proposed in this invention provide an effective solution to the problems existing in the prior art. Through a unique integration technology, the requirements modeling tool and the requirements management system are seamlessly combined, enabling seamless transfer and sharing of requirements information between the two systems. This not only reduces the difficulty of requirements analysis, allowing development teams to understand requirements more comprehensively and accurately, and reducing errors and rework caused by information asymmetry, but also greatly improves the efficiency of requirements management. Through automated information synchronization and a unified management platform, project team members can collaborate more easily, grasp the dynamic changes in requirements in real time, and respond and adjust promptly, thereby effectively improving the overall speed and quality of project progress and bringing a new revolution to software development and project management. Attached Figure Description

[0016] Figure 1 This is a flowchart of the method of the present invention. Detailed Implementation

[0017] The features and illustrative embodiments of various aspects of the present invention will now be described in detail. Numerous specific details are set forth in the following detailed description to provide a thorough understanding of the invention. However, it will be apparent to those skilled in the art that the invention may be practiced without requiring some of these specific details. The following description of embodiments is merely intended to provide a better understanding of the invention by illustrating examples of the invention. The invention is by no means limited to any specific setups and methods set forth below, but covers any improvements, substitutions, and modifications to structures, methods, and devices without departing from the spirit of the invention. Well-known structures and techniques are not shown in the drawings and the following description to avoid unnecessarily obscuring the invention.

[0018] It should be noted that, unless otherwise specified, the embodiments of the present invention and the features thereof can be combined with each other, and the various embodiments can be referenced and cited in each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0019] One embodiment of the present invention is a method for integrating a requirements modeling tool with a requirements management system, comprising the following steps: Step S1: Define the model according to the requirements management system and create a modeling tool integration specification, including data interface standards, data format requirements, data transmission protocols, data conversion rules, and data adaptation requirements that meet the requirements scenario; Step S1 includes: Step S1.1: Analyze the data structure and requirement model of the requirement management system, and clarify its components, including requirement items, data elements contained in the items, and relationships between items; Step S1.2: Design a unified model definition, which includes requirement items, data elements, and relationships between items; Step S1.2 includes: Step S1.2.1: Design multiple requirement item models to store different requirement data; Step S1.2.2: Design the data elements for each requirement item, including element storage type, retrieval method, validity check rules, length / size, and default value.

[0020] Step S1.3: Define the modeling tool integration specification, wherein step S1.3 includes: Step S1.3.1: Define the data format specification, which includes the order of requirement item elements, the representation method, length, encoding format, and verification method of item elements; Step S1.3.2: Define the interface and communication protocol between the requirements modeling tool and the requirements management system; Step S1.3.2 includes: Step S1.3.2.1: Define the format of the interface, including URL structure, request format, response format, return code, parameter description, and exception information; Step S1.3.2.2: Define the communication protocol, including the requirements for each process of data sending, receiving, processing and verification, as well as performance, real-time and reliability requirements.

[0021] Step S2: Analyze the modeling tool, parse the project files in the tool, map the data model with the requirements management system, and establish the relationship between the model project and the requirements management system; Step S2 includes: Step S2.1: Analyze the modeling tools, parse the engineering files in the model, and parse the information including the model structure, images, file objects, text, and attributes in the model; in step S2.1, the (5) pairing mark recognition method was used to parse and identify the "title", "description", "attachment" and other elements in the requirements modeling project. Pairing mark recognition refers to the technology of recognizing, parsing or extracting information from structured data by detecting and parsing mark symbols with the characteristic of "appearing in pairs". Such marks usually wrap the content in the form of "start mark" and "end mark" to form a hierarchical structure.

[0022] Step S2.2: Map the parsed modeling tools to the requirements management system. This mapping includes: (1) The mapping includes the mapping between model engineering files and the management structure of the requirements management system; (2) Mapping includes the mapping between model structure and requirement items; (3) Mapping of images, file objects, text, attribute element information and entry data elements in the model; Step S2.2 uses a lossless compression algorithm to compress the image by removing redundant information (such as repeating pixels and blank areas) from the model image data. This significantly reduces the image size without losing any original image data, saving transmission and storage resources. Image compression refers to techniques that reduce the data size of image files while preserving visual quality as much as possible. Its core objective is to find a balance between "file size" and "image quality" for easy storage, transmission, and loading.

[0023] In step S2.2, the required data entries with hierarchical information are serialized into a tree structure according to the hierarchical information and stored, which improves the efficiency of storage and retrieval. A tree structure is a non-linear data structure that simulates the hierarchical relationship of a tree in nature, consisting of nodes and edges. Its core advantages lie in its "hierarchical organization" and "dynamic expansion" characteristics, which can adapt to the logical relationships of the real world and improve operational efficiency through algorithm optimization.

[0024] Step S2.3: According to the modeling tool integration specifications, convert and adapt the parsed data to the correct format. Step S2.3 includes: Step S2.3.1: During the conversion and adaptation process, the data is verified in real time to ensure the quality and availability of the data; Step S2.3.2: During the conversion and adaptation process, clean the data to remove redundant, duplicate, or invalid information; Step S2.3.3: During the conversion and adaptation process, ensure that the converted data meets the requirements of the target format, including data structure, field naming, and data type.

[0025] Step S2.3 uses a streaming data processing engine to perform data format conversion and adaptation. During this process, real-time data verification is primarily performed to ensure data quality and availability. Simultaneously, data cleaning is conducted to remove redundant, duplicate, or invalid information. A streaming data processing engine is a software system used to process continuous, rapidly flowing data. It can collect, calculate, analyze, and respond to real-time data streams, making it suitable for scenarios requiring rapid decision-making or real-time feedback. Its data exists in the form of a "stream," exhibiting unbounded and real-time characteristics. Streaming processing employs a receive-as-you-go model, resulting in very low latency, thus supporting high-throughput data ingestion and real-time analysis.

[0026] Step S3: Import data from the requirements management system through an interface using a requirements modeling tool, and perform itemized data management; Step S3 includes: Step S3.1: Import the adapted data information into the requirements management system; Step S3.2: Establish a tracking relationship for each required data entry, wherein the tracking relationship includes: (1) Tracking information for model engineering and management structures; (2) Tracking information of model structure and requirement items; (3) Tracking information of images, file objects, text, attribute elements and entry data elements in the model; Step S3.3: The demand management system provides query, statistical, and analytical functions to help users manage and utilize demand information. Step S3.3 uses an inverted index method to build inverted indexes for each statistical analysis dimension of the demand data entries. When queries requiring statistical analysis are needed, the results are calculated and displayed at extremely high speed. The inverted index achieves efficient information retrieval through the reverse mapping of "keywords to documents".

[0027] Step S3 uses the HTTPS communication protocol to establish a data transmission channel between the requirements modeling tool and the requirements management system, providing end-to-end encryption and security features against eavesdropping, tampering, and forgery. HTTPS is not an independent protocol; it is based on the Hypertext Transfer Protocol (HTTP) and incorporates TLS / SSL (Transport Layer Security), with the core objective of addressing the security vulnerabilities of HTTP. By encrypting requests and responses using symmetric encryption algorithms, with the key held only by the client and server, a security triangle of "encryption-authentication-integrity" is constructed, becoming a fundamental infrastructure of modern networks.

[0028] The second embodiment of the present invention is a method for integrating a requirements modeling tool with a requirements management system, as described above. Figure 1 As shown, the method performs the following steps: Step S1: Define the model according to the requirements management system and create a modeling tool integration specification, including data interface standards, data format requirements, data transmission protocols, data conversion rules, and any specific data adaptation requirements; Specifically, the steps include: Step S1.1: Analyze the data structure and requirement model of the requirement management system, and clarify its components, including requirement items, elements contained in the items, and relationships between items.

[0029] Step S1.2: Design a unified model definition, which includes requirement items, data elements, and relationships between items; Step S1.2.1: Design multiple requirement item models to store different requirement data, including "Requirement Item Table" (fields: Requirement ID, Name, Description, Priority, Creation Time) and "Requirement Association Table" (fields: Main Requirement ID, Associated Requirement ID, Association Type), define model constraints, and ensure that the requirement ID is unique; Step S1.2.2: Design the data elements for each requirement item, including element storage type, retrieval method, validity check rules, length / size, and default value; Step S1.3: Modeling tool integration specifications to ensure effective data exchange between the two parties; Step S1.3.1: Define the data format specification; the interface request / response data shall be in JSON format. Step S1.3.2: Define the interface and communication protocol between the requirements modeling tool and the requirements management system. The requirements system provides a RESTful interface, including a requirements query interface and a requirements import interface. Step S2: Analyze the modeling tool, parse the project files in the tool, map the data model with the requirements management system, and establish the relationship between the model project and the requirements management system; Specifically, the steps include: Step S2.1: Analyze the modeling tool, parse the project files in the model, and parse the information, including the model structure, images, file objects, text, and attributes in the model; Step S2.2: Map the parsed information to the demand management system through the demand query interface. This mapping mainly includes: - The mapping includes the mapping between model engineering files and the management structure of the requirements management system; - The mapping includes the mapping between the model structure and the requirement items; - The mapping between images, file objects, text, attribute element information and entry data elements in the model; Step S2.3: According to the modeling tool integration specifications, convert and adapt the parsed data to the correct format; Step S2.3.1: During the transformation and adaptation process, the data is verified in real time through the requirement query interface provided by the requirement system to ensure the quality and availability of the data; Step S2.3.2: During the kernel adaptation process, clean the data to remove redundant, duplicate, or invalid information. For example, if the demand priority level does not follow the specified enumeration value, the data will be cleaned by adjusting the mapping price in advance. Step S2.3.3: During the conversion and adaptation process, ensure that the converted data meets the requirements of the target format, including data structure, field naming, data type, etc. For example, if the font in the import requirement system description requires uniformity to be bold, the data will be converted according to the format requirements of the requirement system. Step S3: Use the requirements modeling tool to import data from the requirements management system via an interface for itemized data management; Specifically, the steps include: Step S3.1: Import the adapted data information into the requirements management system; Step S3.2: Establish a tracking relationship for each required data entry to facilitate subsequent tracking and management. The tracking relationship mainly includes: - Tracking information for model engineering and management structures; - Tracking information for model structure and requirement items; - Tracking information for images, file objects, text, attribute elements, and entry data elements in the model; Step S3.2.1: The requirements management system provides rich query, statistics and analysis functions to help users better manage and utilize requirements information. For example, the requirements management system has a list display, and the statistics page can view the completion status of requirements in the current iteration according to the iteration plan, and publish burn-down charts and defect trend charts.

[0030] The third embodiment of the present invention provides a method for integrating a requirement modeling tool with a requirement management system, specifically implemented as a method for importing requirement data into a target requirement management system through a unified and standardized requirement modeling tool.

[0031] First, based on the requirements management system, the model is defined, and a modeling tool integration specification is created. This specification defines the interfaces for requirements querying and importing, and standardizes the JSON format returned by the interfaces to ensure effective data exchange between the two systems. The modeling tool is analyzed, its project files are parsed, and a data model mapping is established with the requirements management system. Data from the requirements management system is imported through the interface using the requirements modeling tool, enabling itemized data management. Tracking information is established between the model and the management structure, between the model structure and requirement items, and between images, file objects, text, attribute elements, and item data elements within the model.

[0032] The requirements management system offers a wealth of query, statistics, and analysis functions to help users better manage and utilize requirements information. On the statistics page, users can view the completion status of requirements for the current iteration based on the iteration plan, and publish burn-down charts and defect trend charts.

[0033] A fourth embodiment of the present invention provides an apparatus for use in the integration method, comprising: The model definition and specification creation module is used to define models according to the requirements management system and create modeling tool integration specifications, including data interface standards, data format requirements, data transmission protocols, data conversion rules, and data adaptation requirements that meet the requirements scenarios. The analysis module is used to analyze the modeling tools, parse the project files in the tools, map the data model with the requirements management system, and establish the relationship between the model project and the requirements management system. The data management module is used to import data from the requirements management system through an interface using the requirements modeling tool, and to perform itemized data management.

[0034] A final embodiment of the present invention provides a computer storage medium having computer-executable instructions stored thereon, which, when executed by a processor, implement the aforementioned integration method.

[0035] In summary, the present invention provides an integration method, apparatus, and medium for a requirement modeling tool and a requirement management system. It provides a unified integration standard to effectively map the data of the modeling tool to the requirement management system, and tracks, monitors, and manages the received requirement information in the requirement management system. This breaks down the difficulties in transmitting and sharing requirement information between different tools, effectively improves the management of requirement information, greatly improves the efficiency and accuracy of requirement management, and achieves efficient integration and collaborative work.

[0036] The method and apparatus proposed in this invention provide an effective solution to the problems existing in the prior art. Through a unique integration technology, the requirements modeling tool and the requirements management system are seamlessly combined, enabling seamless transfer and sharing of requirements information between the two systems. This not only reduces the difficulty of requirements analysis, allowing development teams to understand requirements more comprehensively and accurately, and reducing errors and rework caused by information asymmetry, but also greatly improves the efficiency of requirements management. Through automated information synchronization and a unified management platform, project team members can collaborate more easily, grasp the dynamic changes in requirements in real time, and respond and adjust promptly, thereby effectively improving the overall speed and quality of project progress and bringing a new revolution to software development and project management.

[0037] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should be covered within the protection scope of the present invention.

Claims

1. A method for integrating a requirements modeling tool with a requirements management system, the method comprising: It comprises the following steps: Step S1: defining a model according to a requirement management system, creating a modeling tool integration specification, including data interface standards, data format requirements, data transmission protocols, data conversion rules, and data adaptation requirements conforming to the requirement scenario; Step S2: analyzing the modeling tool, parsing the engineering file in the tool, and mapping the data model with the requirement management system to establish the relationship between the model engineering and the requirement management system; Step S3: importing the data of the requirement management system through the interface by using the requirement modeling tool to perform entry-based data management.

2. The integration method of claim 1, wherein, The step S1 comprises: Step S1.1: analyzing the data structure and requirement model of the requirement management system to determine the constituent elements, including requirement entries, data elements contained in the entries, and relationships between the entries; Step S1.2: designing a unified model definition, which includes requirement entries, data elements, and relationships between the entries; Step S1.3: defining the modeling tool integration specification.

3. The integration method of claim 2, wherein, The step S1.2 comprises: Step S1.2.1: designing multiple requirement entry models for storing different requirement data; Step S1.2.2: designing the data elements possessed by each requirement entry, including element storage type, retrieval method, validity verification rule, length / size, and default value.

4. The integration method of claim 3, wherein, The step S1.3 comprises: Step S1.3.1: defining data format specifications, including requirement entry element order, entry element representation method, length, coding format, and verification method; Step S1.3.2: defining the interface mode and communication protocol between the requirement modeling tool and the requirement management system; step S1.3.2 comprises: Step S1.3.2.1: defining the format of the interface, including URL structure, request format, response format, return code, parameter description, and exception information; Step S1.3.2.2: defining the communication protocol, including data sending, receiving, processing, and verification process requirements, as well as performance, real-time, and reliability requirements.

5. The integration method of claim 4, wherein, The step S2 comprises: Step S2.1: analyzing the modeling tool, parsing the engineering file in the model, and parsing information including model structure, pictures, file objects, text, and attributes in the model; Step S2.2: mapping the parsed modeling tool with the requirement management system, which comprises: (1) mapping includes mapping the model engineering file with the requirement management system management structure; (2) mapping includes mapping the model structure with the requirement entries; (3) mapping the picture, file object, text, and attribute element information in the model with the entry data elements; Step S2.3: performing format conversion and adaptation of the parsed data according to the modeling tool integration specification.

6. The integration method of claim 5, wherein, The step S2.3 comprises: Step S2.3.1: performing real-time verification on the data during the conversion and adaptation process to ensure the quality and availability of the data; Step S2.3.2: cleaning the data during the conversion and adaptation process to remove redundant, repetitive, or invalid information; Step S2.3.3: ensuring that the converted data meets the requirements of the target format, including data structure, field naming, and data type.

7. The integration method of claim 6, wherein, The step S3 comprises: Step S3.1: importing the adapted data information into the requirement management system in the requirement management system; Step S3.2: establishing a tracking relationship for each requirement data entry, the tracking relationship comprising: (1) tracking information of the model engineering and the management structure; (2) tracking information of the model structure and the requirement entry; (3) tracking information of picture, file object, text, attribute element information in the model and the entry data element; Step S3.3: providing query, statistics and analysis functions in the requirement management system to help users manage and utilize the requirement information.

8. A device for use in the integration method of claim 7, characterized in that, Comprise: A model definition and specification creation module for defining a model according to the requirement management system, creating a modeling tool integration specification, including a data interface standard, a data format requirement, a data transmission protocol, a data conversion rule and a data adaptation requirement conforming to a requirement scenario; An analysis module for analyzing a modeling tool, parsing engineering files in the tool, performing data model mapping with the requirement management system and establishing a relationship between the model engineering and the requirement management system; A data management module for importing data of the requirement management system into the requirement management system by an interface and performing entry-based data management by using the requirement modeling tool. 9.A computer storage medium having computer-executable instructions stored thereon, the computer-executable instructions being executed by a processor to implement the integrated method of any one of claims 1-7.

Images