A demand management method and device, electronic equipment, and storage medium

Abstract

The application discloses a demand management method and device, an electronic device, and a storage medium. The method comprises the following steps: obtaining an original demand document and a pre-constructed demand data model; converting the original demand document into structured demand data with a nested structure according to the demand data model, and storing the structured demand data with the nested structure into a database; and performing a recursive operation on the structured demand data with the nested structure in the database to realize demand management. According to the technical scheme, the original demand document is converted into the structured demand data with the nested structure, so that the demand management system can perform demand management on the structured demand data in the database based on recursive logic instead of iterative logic, the software development cost of the demand management system can be reduced, the code quality can be improved, and the demand management system has better expansibility.

Description

Technical Field

[0001] This application relates to the field of information management technology, and in particular to a demand management method, apparatus, electronic device, and storage medium. Background Technology

[0002] In the R&D management of various business systems, it is necessary to design requirement documents based on business needs in order to manage the business system through information technology. For example, requirements can be broken down hierarchically according to the requirement documents, and each level of requirements can be mapped to the corresponding subsystems, components, software modules, and other implementation units, or to the corresponding responsible departments, persons in charge, and other executors. Finally, detailed R&D / design work can be carried out based on all the existing requirements.

[0003] In the process of informatization, it is necessary to parse a large number of unstructured requirement documents, automatically create requirements at all levels, establish the dependencies between requirements, and build a requirement structure system, thereby replacing manual input of requirements, accelerating the informatization process, and improving the accuracy of informatization.

[0004] like Figure 1 As shown, the original requirements document is usually obtained through Figure 1 The description shown is based on unstructured data described by natural language. When structuring the original requirement document, the existing technology generally builds a tree structure and saves it to a relational database. When using management tools to manage structured data in relational databases, the management tools often need to use iterative algorithms during the development phase. Management tools based on iterative algorithms need to specify the number of iterations and the definition of each variable at each level during the tool development phase.

[0005] For example, when a hierarchy is added or changed, a large amount of repetitive or similar development work is usually required. When requirements change, modifications need to be made sequentially at each level. If any are missed, problems may arise in the modifications to those levels. Furthermore, the use of repetitive code results in a large amount of code in the management tool, making it prone to errors and difficult to manage. Summary of the Invention

[0006] To overcome at least one of the problems mentioned above, embodiments of this application provide a demand management method, apparatus, electronic device, and storage medium.

[0007] The embodiments of this application adopt the following technical solutions:

[0008] In a first aspect, embodiments of this application provide a demand management method, comprising:

[0009] Obtain the original requirements document and a pre-built requirements data model, wherein the requirements data model is used to convert the original requirements document into structured requirements data with a nested structure;

[0010] The original requirement document is converted into structured requirement data with a nested structure according to the requirement data model, and the structured requirement data with a nested structure is stored in the database.

[0011] Requirements management is achieved by recursively operating on the structured requirements data with nested structures in the database.

[0012] Secondly, embodiments of this application provide a demand management device, the device comprising:

[0013] The data acquisition unit is used to acquire the original requirement document and the pre-built requirement data model, wherein the requirement data model is used to convert the original requirement document into structured requirement data with a nested structure.

[0014] The data processing unit is used to convert the original requirement document into structured requirement data with a nested structure according to the requirement data model, and to store the structured requirement data with a nested structure into a database.

[0015] The data management unit is used to perform recursive operations on the structured requirement data with nested structures in the database to achieve requirement management.

[0016] Thirdly, embodiments of this application also provide an electronic device, including: a processor; and a memory arranged to store computer-executable instructions, which, when executed, cause the processor to perform a demand management method.

[0017] Fourthly, embodiments of this application also provide a computer-readable storage medium that stores one or more programs, which, when executed by an electronic device including multiple applications, cause the electronic device to perform a demand management method.

[0018] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects:

[0019] This application embodiment converts the original requirement document into structured requirement data with a nested structure through a requirement data model and stores it in a database. In this way, during the development phase of the requirement management system, the requirement management system can be developed quickly based on recursive logic, avoiding the repetitive development of functions in the software development process due to iterative algorithms. This can reduce the amount of research and development in the software development process, improve code quality, and make the requirement management system more scalable. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0021] Figure 1 This is a schematic diagram illustrating a process for structuring an original requirements document in an embodiment of this application;

[0022] Figure 2 This is a flowchart illustrating a demand management method according to an embodiment of this application;

[0023] Figure 3 This is a schematic diagram of the components of a demand data model in an embodiment of this application;

[0024] Figure 4 This is a schematic diagram illustrating the nested effect of a main requirement and its sub-requirements at all levels in an embodiment of this application.

[0025] Figure 5 This is a pseudocode diagram of a sub-requirement query function in an embodiment of this application;

[0026] Figure 6 This is a schematic diagram illustrating the effect of a demand query process in one embodiment of this application;

[0027] Figure 7 This is a pseudocode diagram of a sub-requirement appending function in an embodiment of this application;

[0028] Figure 8 This is a pseudocode diagram of a sub-demand statistics function in an embodiment of this application;

[0029] Figure 9 This is a schematic diagram of the structure of a demand management device according to an embodiment of this application;

[0030] Figure 10 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0032] This application provides a requirement management method, such as... Figure 2The diagram shows a flowchart of a demand management method according to an embodiment of this application. The method includes at least the following steps S210 to S230:

[0033] Step S210: Obtain the original requirement document and the pre-built requirement data model, wherein the requirement data model is used to convert the original requirement document into structured requirement data with a nested structure.

[0034] The method in this application embodiment can be executed by hardware or software such as a demand management platform, a demand management system, or a demand management engine. For ease of description, this application embodiment uses a demand management system as an example to illustrate the demand management method in this application embodiment.

[0035] As mentioned earlier, in existing technologies, when managing structured requirement data in relational databases using management tools, the management tools iterate over the structured requirement data in the relational database to achieve requirement management. However, the software code development corresponding to iterative operations suffers from drawbacks such as low development efficiency, large code size, susceptibility to errors, and inconvenience for secondary development.

[0036] To address the aforementioned issues, research has found that the development process of requirements management can be divided into the development of the requirements data model and the development of functions for data manipulation, with the latter based on the requirements data model. Therefore, this application's embodiments design structured requirements data with a nested structure based on the recursive attributes inherent in each requirement within the original requirements document. Thus, during the development of data manipulation functions, corresponding management functions can be designed using recursive logic. These management functions can then perform recursive operations on the structured requirements data, avoiding the aforementioned problems associated with iterative data manipulation.

[0037] The requirement data model constructed in this application embodiment can, on the one hand, transform the original requirement documents into a structured form, enabling the transformed structured requirement data with nested structures to support recursive operations; on the other hand, the requirement data model in this application embodiment can transform the data structure of the original requirement documents in batches, without the need to design a separate template for each original requirement document, thereby improving the transformation efficiency and template development efficiency.

[0038] In this application's embodiments, the "original requirement document" can be understood as a requirement document described in natural language. It typically requires specific software to open and view, lacks a fixed structure, and is difficult to manage. Structured data refers to data with a certain structure, divisible into fixed basic components, and represented by one or more two-dimensional tables. "Nested structure" refers to any structured requirement data including all hierarchical relationships from main requirements to basic requirements. This nested structure provides data support for subsequent recursive operations. "Basic requirements" refer to the lowest-level requirements in the original requirement document's requirement directory; in a tree structure, basic requirements can also be understood as the requirements corresponding to leaf nodes. "Main requirements" refer to the highest-level requirements in the original requirement document's requirement directory; in a tree structure, main requirements can also be understood as the requirements corresponding to the root node.

[0039] Step S220: Based on the requirement data model, the original requirement document is converted into structured requirement data with a nested structure, and the structured requirement data with a nested structure is stored in the database.

[0040] The embodiments of this application can use a relational database or a non-relational database for structured requirements data with nested structures. Those skilled in the art can choose the specific database type according to their needs.

[0041] Step S230: Perform recursive operations on the structured requirement data with nested structures in the database to achieve requirement management.

[0042] based on Figure 1 As can be seen from the requirements management method shown, the embodiments of this application convert the original requirements document into structured requirements data with nested structure through the requirements data model and store it in the database. In this way, during the development stage of the requirements management system, the requirements management system can be developed quickly based on recursive logic, avoiding the repetitive development of functions in the software development process by iterative algorithms, reducing the amount of research and development in the software development process, improving code quality, and making the requirements management system more scalable.

[0043] In some embodiments of this application, the demand data model can be constructed through the following steps:

[0044] The components of the construction requirement include attribute information and nested structure. The attribute information includes multi-dimensional attributes corresponding to the requirement data. The nested structure includes component information and internal variable information. The component information includes direct sub-requirement information. The internal variable information includes sub-requirements at all levels of the direct sub-requirement and nested information corresponding to each level of sub-requirement. The nested information is used to indicate the relationship between each level of sub-requirement and the direct sub-requirement information in the component information.

[0045] The demand data model is constructed based on the information of the components of the demand.

[0046] Optionally, the component information records the direct sub-requirement ID of the current requirement, and the internal variable information records the IDs of other sub-requirements at all levels besides the direct sub-requirements, as well as the nesting information of these sub-requirement IDs. It should be noted that in some embodiments, the internal variable information may also record the direct sub-requirements.

[0047] As can be seen, unlike the structured requirement data in existing technologies, the nested structure of the structured requirement data in this application embodiment includes sub-requirement information at each level of directly subordinate sub-requirements and the nested information corresponding to each level of sub-requirement information. This allows for recursive querying to obtain the target requirement. Furthermore, by dividing the nested structure, this application embodiment enables the requirement management function to first query the component information of the structured requirement data when performing recursive operations on the structured requirement data. If the component information does not include the target requirement ID, then a recursive query is performed using the sub-requirement IDs at each level and their nested information recorded in the internal variable information of the current structured requirement data, thereby improving query efficiency.

[0048] like Figure 3 As shown, the attribute information of structured requirement data includes, for example, ID (Identity), name, parent requirement ID, level, current level sequence, and requirement business attributes. Figure 3 The symbols <> in the text represent the data type of each attribute. Of course, other attributes can be set in other embodiments of this application, and this application does not specifically limit this.

[0049] Among them, ID should be UUID (Universally Unique Identifier), and each requirement's ID must be unique and cannot be repeated; name can be the actual name of the requirement; parent requirement ID is the ID of the parent requirement to which this requirement belongs; level refers to the nesting level from the starting requirement level, with the starting requirement level being 0; current level sequence refers to the sequence number of all child requirements of the requirement in its parent requirement; requirement business attributes are used for attribute management of requirements in the actual business process, and can be extended and set according to the actual situation, such as specific business information such as "update date", "responsible person", and "requirement source".

[0050] The internal variables in this application's embodiments are intermediate results stored when performing corresponding operations on the required data object, and do not have any practically perceptible meaning. (See reference...) Figure 3For example, the internal variables in this application embodiment include the current operation sub-requirement pointer ID and the direct sub-requirement overlay mapping; wherein the current operation sub-requirement pointer ID is used to mark the sub-requirement ID that is currently being edited or operated, so as to facilitate continuous information editing of the same requirement; and the direct sub-requirement overlay mapping is used to record the sub-requirement IDs of each subordinate sub-requirement of the current requirement and the relationship between each level of sub-requirement ID and the direct sub-requirement ID in the component information.

[0051] It is understood that the internal variable information in the embodiments of this application may also include other internal variables, which can be set as needed by those skilled in the art, and this application does not make any specific limitations in this regard.

[0052] like Figure 4 As shown, assume that the direct sub-requirements of main requirement 1 include requirement 1-1 and requirement 1-2, the direct sub-requirements of requirement 1-1 include requirement 1-1-1 and requirement 1-1-2, the direct sub-requirements of requirement 1-1-2 include requirement 1-1-2-1, and the direct sub-requirements of requirement 1-2 include requirement 1-2-1.

[0053] Thus, the component information for main requirement 1 includes: "0002" and "0003";

[0054] The direct sub-requirements of main requirement 1 are mapped to include: “0004”: “0002”, “0005”: “0002”, “0006”: “0003” and “0007”: “0002”;

[0055] Where “A” and “B” are the numerical representations of the nested information of requirement A, “A” represents the ID of the subordinate sub-requirement of the direct sub-requirement of the main requirement 1, and “B” represents the ID of the direct sub-requirement corresponding to requirement A in the component information of the main requirement 1. In practical applications, the relationship between requirement A and requirement B is not necessarily a direct parent-child relationship; it could also be a grandparent-grandchild relationship, or a great-grandparent-grandchild relationship, etc.

[0056] Thus, this application embodiment provides a query method and query scope for demand queries through the nested results of structured demand data. When performing recursive queries, the lower-level recursive objects can be quickly queried based on the nested information of demand A, thereby improving the efficiency of demand query.

[0057] It should be noted that in practical applications, the recording content of the component information and direct sub-requirement coverage mapping of the structured requirement data can be flexibly designed according to the needs. For example, the recording content of the component information can be processed by default, while the direct sub-requirement ID of the current structured requirement data can be recorded in the direct sub-requirement coverage mapping. Those skilled in the art can flexibly design the combination of the recording content of the component information and the direct sub-requirement coverage mapping according to actual needs. This application does not impose specific restrictions on this.

[0058] like Figure 1 As shown, the original requirements document includes a requirements directory, which includes at least one main requirement and sub-requirements at each level corresponding to each main requirement. In this embodiment of the application, the main requirement is the direct sub-requirement of the starting requirement.

[0059] In some embodiments of this application, step S220 above, which converts the original requirement document into structured requirement data with a nested structure according to the requirement data model, specifically includes:

[0060] Obtain the attribute information and nesting structure of each requirement based on the requirement catalog, and refer to... Figure 3 It can obtain various attribute information, direct sub-requirement coverage mapping, component information, etc. for each requirement;

[0061] Using the aforementioned demand data model, and based on the attribute information and nested structure of each demand, each demand in the demand catalog is converted into structured demand data with a nested structure.

[0062] After converting the original requirement document of this application embodiment into structured requirement data with a nested structure and storing it in the database, management such as adding, deleting, modifying and querying can be achieved by recursively operating on the structured requirement data in the database.

[0063] In some embodiments of this application, the recursive operation on the structured requirement data with nested structures in the database in step S230 above to achieve requirement management specifically includes:

[0064] Upon receiving a requirement management request, the corresponding target requirement management function is obtained from the pre-built requirement management function according to the requirement management request. The requirement management function is a function for managing structured requirement data based on recursive logic.

[0065] The structured requirement data in the database is managed according to the requirement management request and the target requirement management function.

[0066] In this application, the requirements management requests include, for example, requirements query requests, requirements addition requests, requirements modification requests, requirements deletion requests, and requirements statistics requests. The processing steps for requirements modification requests and requirements deletion requests can be referred to the relevant processing steps for requirements query requests and requirements addition requests in the following embodiments of this application. These will not be described in detail in the embodiments of this application.

[0067] The pre-built demand management functions in this application include sub-demand query functions, sub-demand addition functions, sub-demand modification functions, sub-demand deletion functions, and sub-demand statistics functions, etc. For the pseudocode of the sub-demand modification function and the sub-demand deletion function, those skilled in the art can refer to the pseudocode of the sub-demand query function and the sub-demand addition function in the following embodiments of this application. The embodiments of this application will not be described in detail here.

[0068] <Management Scenarios Regarding Request Queries>

[0069] In a requirement query management scenario, the requirement management system receives requirement query requests and obtains sub-requirement query functions. The pseudocode for these sub-requirement query functions is provided below. Figure 5 As shown, the sub-requirement query function (i.e. Figure 5 The `FunctionsubRequirement = getSubRequirerment(requirementID)` is used to retrieve the current structured requirement data based on the current requirement ID, and query whether the component information of the current structured requirement data includes the requirement ID to be queried. If it does not include it, it queries the nesting information corresponding to each level of sub-requirement in the internal variable information of the current structured requirement data to obtain the next level requirement ID, and calls the sub-requirement query function itself to recursively query the next level requirement ID until the requirement ID to be queried is found.

[0070] In some embodiments of this application, demand management is performed on the structured demand data in the database according to the demand management request and the target demand management function, specifically including:

[0071] Based on the attribute information of the query request carried in the query request, obtain the query request ID and the main request ID to which the query request belongs;

[0072] The sub-requirement query function is assigned values ​​based on the main requirement ID and the requirement ID to be queried, so that the sub-requirement query function performs a recursive query starting from the main requirement ID, and obtains the structured requirement data corresponding to the requirement ID to be queried based on the return result of the sub-requirement query function.

[0073] like Figure 6 As shown, assume that the demand management system receives a demand query request. The demand query request carries the demand ID to be queried as "0007" and the main demand ID corresponding to the demand ID to be queried as "0002".

[0074] The sub-requirement query function queries the structured requirement data of Requirement 1 and performs a matching judgment. Since the ID recorded in the component information of Requirement 1 does not include "0007", the next-level requirement ID can be determined to be "0002" based on the record content of the direct sub-requirement overlay mapping of Requirement 1. At this time, the sub-requirement query function itself will be called again, which will query the structured requirement data corresponding to requirement ID "0002" to obtain Requirement 1-1. Since the ID recorded in the component information of Requirement 1-1 does not include "0007", the next-level requirement ID can be determined to be "0005" based on the record content of the direct sub-requirement overlay mapping of Requirement 1-1. At this time, the sub-requirement query function itself will be called again, which will query the structured requirement data corresponding to requirement ID "0005". Since the ID recorded in the component information of Requirement 1-1-2 includes "0007", the structured requirement data corresponding to requirement ID "0007" will be queried and returned. In this way, the query result corresponding to the requirement query request can be obtained based on the return result of the sub-requirement query function.

[0075] <Management Scenarios Regarding Additional Requirements>

[0076] In a requirement addition management scenario, the requirement management system receives a requirement addition request and obtains a sub-requirement addition function. The pseudocode for this sub-requirement addition function is shown below. Figure 7 As shown, the sub-requirement appending function (i.e. Figure 7 The function `Function addSuccess = addSubRequirment(newRequirment, parentRequirmentID)` is used to retrieve the current structured requirement data based on the current requirement ID, and query whether the component information of the current structured requirement data includes the parent requirement ID of the requirement to be added. If not, the nested information corresponding to the requirement ID to be added is added to the internal variable information of the current structured requirement data (specifically, the direct sub-requisite overriding mapping of the internal variable information). The function then queries the nested information corresponding to each level of sub-requisite in the internal variable information of the current structured requirement data to obtain the next-level requirement ID, and calls the sub-requisite addition function itself to recursively query the next-level requirement ID until the parent requirement ID of the requirement to be added is found and the requirement ID to be added is added to the component information of the parent requirement.

[0077] In some embodiments of this application, demand management is performed on the structured demand data in the database according to the demand management request and the target demand management function, specifically including:

[0078] Based on the attribute information of the additional requirement carried in the additional requirement request, obtain the nesting information corresponding to the additional requirement, the parent requirement ID corresponding to the additional requirement, and the main requirement ID to which the parent requirement to which the additional requirement belongs;

[0079] The sub-requirement appending function is assigned values ​​based on the nesting information corresponding to the requirement to be appended, the parent requirement ID corresponding to the requirement to be appended, and the main requirement ID to which the parent requirement belongs. This allows the sub-requirement appending function to perform recursive queries starting from the main requirement ID, add the nesting information corresponding to the requirement to be appended to the internal variable information of each parent requirement of the parent requirement, add the requirement ID to the component information of the parent requirement, and determine whether the requirement to be appended was successfully appended based on the return result of the sub-requirement appending function.

[0080] Continue with Figure 4 Taking the structured requirement data shown as an example, suppose the name of the requirement to be added is 1-1-2-1-1, the requirement ID is "0008", and its parent requirement is requirement 1-1-2-1. Then, the sub-requirement addition function in this embodiment will add "0008": "0002" to the direct sub-requirement coverage map of requirement 1, add "0008": "0005" to the direct sub-requirement coverage map of requirement 1-1, add "0008": "0007" to the direct sub-requirement coverage map of requirement 1-1-2, and add "0008" to the component information of requirement 1-1-2-1. It can be seen that during the sub-requirement addition process, the corresponding modifications are made to the direct sub-requirement coverage maps of the parent requirements of the requirement to be added, without modifying the component information; for the parent requirement of the requirement to be added, its component information is modified, without modifying the direct sub-requirement coverage maps.

[0081] <Management Scenarios Regarding Demand Statistics>

[0082] In a requirements statistics management scenario, the requirements management system receives a requirements statistics request and obtains a sub-requirement statistics function. The pseudocode for this sub-requirement statistics function is shown below. Figure 8 As shown, the sub-demand statistics function (i.e. Figure 8 The FunctionsumManHour = SumManHour() is used to query the attributes to be counted in the current structured requirement data and perform statistics on the queried attributes. It also calls the sub-requirement statistics function itself to query the attributes to be counted in the next level of structured requirement data and perform statistics on them, until the statistics of the attributes to be counted in each structured requirement data is completed.

[0083] In some embodiments of this application, demand management is performed on the structured demand data in the database according to the demand management request and the target demand management function, specifically including:

[0084] The attribute to be statistically analyzed carried in the demand statistics request is assigned to the sub-demand statistics function, so as to obtain the statistical result corresponding to the attribute to be statistically analyzed based on the return result of the sub-demand statistics function.

[0085] For example, assuming the specific business attribute of the requirement is the working hours attribute, and the specific statistical request is to sum the working hours, then correspondingly, a system like this can be developed: Figure 8 The sub-demand statistics function shown is Function sumManHour = SumManHour(), which can be used to obtain the summation result of working hours.

[0086] It should be noted that the embodiments of this application can perform statistics on any numerical value or any logical value, and the statistical methods include, but are not limited to, summation and averaging.

[0087] As can be seen from the above embodiments of this application, the embodiments of this application perform recursive operations on structured requirement data with nested structures in the database, realizing the management of requirements such as adding, modifying, deleting, querying, and statistics. For requirement management systems, management tools can be developed based on recursive algorithms, making the software extensibility of management tools stronger and the secondary development cost lower. Since for any management function, only one function needs to be developed to complete the framework development of the function, there is no need to repeatedly develop or similarly develop different levels of structured requirement data. This greatly reduces the amount of code for the overall functional development of the requirement management system, and for requirement management software with multiple management functions, it can significantly reduce the overall code volume.

[0088] Similar to the demand management methods described in the foregoing embodiments, this application also provides a demand management device 900, such as... Figure 9 As shown, a structural schematic diagram of a demand management device according to an embodiment of this application is provided. The demand management device 900 includes: a data acquisition unit 910, a data processing unit 920, and a data management unit 930, wherein:

[0089] The data acquisition unit 910 is used to acquire the original requirement document and the pre-built requirement data model, wherein the requirement data model is used to convert the original requirement document into structured requirement data with a nested structure.

[0090] The data processing unit 920 is used to convert the original requirement document into structured requirement data with a nested structure according to the requirement data model, and to store the structured requirement data with a nested structure into a database.

[0091] The data management unit 930 is used to perform recursive operations on the structured requirement data with nested structures in the database to achieve requirement management.

[0092] In one embodiment of this application, the apparatus 900 further includes a preprocessing unit;

[0093] The preprocessing unit is used to construct the constituent elements of the requirement. The constituent elements include attribute information and nested structure. The attribute information includes multi-dimensional attributes corresponding to the requirement data. The nested structure includes component information and internal variable information. The component information includes direct sub-requirement information. The internal variable information includes sub-requirements at all levels of the direct sub-requirements and nested information corresponding to each level of sub-requirements. The nested information is used to indicate the relationship between each level of sub-requirement and the direct sub-requirement information in the component information. The requirement data model is constructed based on the constituent element information of the requirement.

[0094] In one embodiment of this application, the original requirement document includes a requirement directory, which includes at least one main requirement and sub-requirements at each level corresponding to each main requirement. The data processing unit 920 is specifically used to obtain the attribute information and nested structure of each requirement according to the requirement directory; and through the requirement data model, and according to the attribute information and nested structure of each requirement, convert each requirement in the requirement directory into structured requirement data with a nested structure.

[0095] In one embodiment of this application, the data management unit 930 is specifically configured to, upon receiving a demand management request, obtain a corresponding target demand management function from a pre-built demand management function according to the demand management request, wherein the demand management function is a function for managing structured demand data based on recursive logic; and perform demand management on the structured demand data in the database according to the demand management request and the target demand management function.

[0096] In one embodiment of this application, the requirement management request includes a requirement query request, and the target requirement management function includes a sub-requirement query function. The sub-requirement query function is used to obtain the current structured requirement data based on the current requirement ID, and query whether the component information of the current structured requirement data includes the requirement ID to be queried. If it does not include it, it queries the nesting information corresponding to each level of sub-requirement in the internal variable information of the current structured requirement data to obtain the next level requirement ID and calls the sub-requirement query function itself to recursively query the next level requirement ID until the requirement ID to be queried is found.

[0097] The data management unit 930 is specifically used to obtain the ID of the request to be queried and the ID of the main requirement to which the request to be queried belongs based on the attribute information of the request to be queried carried in the request; to assign values ​​to the sub-requirement query function based on the main requirement ID and the ID of the request to be queried, so that the sub-requirement query function performs recursive query starting from the main requirement ID; and to obtain the structured requirement data corresponding to the ID of the request to be queried based on the return result of the sub-requirement query function.

[0098] In one embodiment of this application, the requirement management request includes a requirement addition request, and the target requirement management function includes a sub-requirement addition function. The sub-requirement addition function is used to obtain the current structured requirement data based on the current requirement ID, and query whether the component information of the current structured requirement data includes the parent requirement ID of the requirement to be added. If not, the nesting information corresponding to the requirement ID to be added is added to the internal variable information of the current structured requirement data, and the nesting information corresponding to each level of sub-requirement in the internal variable information of the current structured requirement data is queried to obtain the next-level requirement ID. The sub-requirement addition function itself is called to iteratively query the next-level requirement ID until the parent requirement ID of the requirement to be added is found and the requirement ID to be added is added to the component information of the parent requirement.

[0099] The data management unit 930 is specifically used to obtain the nesting information corresponding to the requirement to be added, the parent requirement ID corresponding to the requirement to be added, and the main requirement ID to which the parent requirement to which the requirement to be added belongs, based on the attribute information of the requirement to be added carried in the requirement addition request; to assign values ​​to the sub-requirement addition function based on the nesting information corresponding to the requirement to be added, the parent requirement ID corresponding to the requirement to be added, and the main requirement ID to which the parent requirement to which the requirement to be added belongs, so that the sub-requirement addition function performs recursive query starting from the main requirement ID, adds the nesting information corresponding to the requirement to be added to the internal variable information of each superior requirement of the parent requirement, adds the requirement ID to the component information of the parent requirement, and obtains whether the requirement to be added was successfully added based on the return result of the sub-requirement addition function.

[0100] In one embodiment of this application, the requirement management request includes a requirement statistics request, the target requirement management function includes a sub-requirement statistics function, the sub-requirement statistics function is used to query the attributes to be counted in the current structured requirement data and perform statistics on the queried attributes to be counted, and call the sub-requirement statistics function itself to query the attributes to be counted in the next level of structured requirement data and perform statistics, until the statistics of the attributes to be counted in each structured requirement data is completed;

[0101] The data management unit 930 is specifically used to assign the attribute to be statistically analyzed carried by the demand statistics request to the sub-demand statistics function, so as to obtain the statistical result corresponding to the attribute to be statistically analyzed based on the return result of the sub-demand statistics function.

[0102] It is understood that the aforementioned demand management device 900 can implement each step of the demand management method provided in the foregoing embodiments. The relevant explanations of the demand management method are applicable to the demand management device 900, and will not be repeated here.

[0103] Figure 10 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Please refer to it. Figure 10 At the hardware level, the electronic device includes a processor and memory, and optionally also includes an internal bus and a network interface. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for other business operations.

[0104] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 10 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0105] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0106] The processor reads the corresponding computer program from non-volatile memory into main memory and then runs it, forming a demand management device at the logical level. The processor executes the program stored in memory and specifically performs the following operations:

[0107] Obtain the original requirements document and a pre-built requirements data model, wherein the requirements data model is used to convert the original requirements document into structured requirements data with a nested structure;

[0108] The original requirement document is converted into structured requirement data with a nested structure according to the requirement data model, and the structured requirement data with a nested structure is stored in the database.

[0109] Requirements management is achieved by recursively operating on the structured requirements data with nested structures in the database.

[0110] The above is as stated in this application. Figure 2 The method executed by the demand management device disclosed in the illustrated embodiments can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads the information from the memory and, in conjunction with its hardware, completes the steps of the aforementioned requirement management method.

[0111] The electronic device can also perform Figure 2 The method executed by the demand management device, and the implementation of the demand management device in Figure 2 The functions of the embodiments shown are not described in detail here.

[0112] This application also proposes a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by an electronic device including multiple applications, enable the electronic device to perform... Figure 2The method executed by the demand management device in the illustrated embodiment is specifically used to perform:

[0113] Obtain the original requirements document and a pre-built requirements data model, wherein the requirements data model is used to convert the original requirements document into structured requirements data with a nested structure;

[0114] The original requirement document is converted into structured requirement data with a nested structure according to the requirement data model, and the structured requirement data with a nested structure is stored in the database.

[0115] Requirements management is achieved by recursively operating on the structured requirements data with nested structures in the database.

[0116] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0117] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0118] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0119] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0120] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0121] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0122] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0123] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0124] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0125] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A demand management method, characterized in that, The method includes: Obtain the original requirements document and a pre-built requirements data model, wherein the requirements data model is used to convert the original requirements document into structured requirements data with a nested structure; The original requirement document is converted into structured requirement data with a nested structure according to the requirement data model, and the structured requirement data with a nested structure is stored in the database. Requirements management is achieved by recursively operating on the structured requirements data with nested structures in the database. The required data model is constructed using the following steps: The components of the construction requirement include attribute information and nested structure. The attribute information includes multi-dimensional attributes corresponding to the requirement data. The nested structure includes component information and internal variable information. The component information includes direct sub-requirement information. The internal variable information includes sub-requirements at all levels of the direct sub-requirement and nested information corresponding to each level of sub-requirement. The nested information is used to indicate the relationship between each level of sub-requirement and the direct sub-requirement information in the component information. The demand data model is constructed based on the information of the components of the demand; The original requirement document includes a requirement directory, which includes at least one main requirement and sub-requirements at each level corresponding to each main requirement. The step of converting the original requirement document into structured requirement data with a nested structure according to the requirement data model includes: Obtain the attribute information and nesting structure of each requirement based on the requirement catalog; Using the aforementioned demand data model, and based on the attribute information and nested structure of each demand, each demand in the demand catalog is converted into structured demand data with a nested structure.

2. The demand management method as described in claim 1, characterized in that, The recursive operation on the structured requirement data with nested structures in the database to achieve requirement management includes: Upon receiving a requirement management request, the corresponding target requirement management function is obtained from the pre-built requirement management function according to the requirement management request. The requirement management function is a function for managing structured requirement data based on recursive logic. The structured requirement data in the database is managed according to the requirement management request and the target requirement management function.

3. The demand management method as described in claim 2, characterized in that, The requirement management request includes a requirement query request. The target requirement management function includes a sub-requirement query function. The sub-requirement query function is used to obtain the current structured requirement data based on the current requirement ID, and query whether the component information of the current structured requirement data includes the requirement ID to be queried. If it does not include it, it queries the nesting information corresponding to each level of sub-requirement in the internal variable information of the current structured requirement data to obtain the next level requirement ID and calls the sub-requirement query function itself to recursively query the next level requirement ID until the requirement ID to be queried is found. The step of managing the structured requirement data in the database according to the requirement management request and the target requirement management function includes: Based on the attribute information of the query request carried in the query request, obtain the query request ID and the main request ID to which the query request belongs; The sub-requirement query function is assigned values ​​based on the main requirement ID and the requirement ID to be queried, so that the sub-requirement query function performs a recursive query starting from the main requirement ID, and obtains the structured requirement data corresponding to the requirement ID to be queried based on the return result of the sub-requirement query function.

4. The demand management method as described in claim 2, characterized in that, The requirement management request includes a requirement addition request. The target requirement management function includes a sub-requirement addition function. The sub-requirement addition function is used to obtain the current structured requirement data based on the current requirement ID, and query whether the component information of the current structured requirement data includes the parent requirement ID of the requirement to be added. If not, the nesting information corresponding to the requirement ID to be added is added to the internal variable information of the current structured requirement data. The function then queries the nesting information corresponding to each level of sub-requirement in the internal variable information of the current structured requirement data to obtain the next-level requirement ID and calls the sub-requirement addition function itself to recursively query the next-level requirement ID until the parent requirement ID of the requirement to be added is found and the requirement ID to be added is added to the component information of the parent requirement. The step of managing the structured requirement data in the database according to the requirement management request and the target requirement management function includes: Based on the attribute information of the additional requirement carried in the additional requirement request, obtain the nesting information corresponding to the additional requirement, the parent requirement ID corresponding to the additional requirement, and the main requirement ID to which the parent requirement to which the additional requirement belongs; The sub-requirement appending function is assigned values ​​based on the nesting information corresponding to the requirement to be appended, the parent requirement ID corresponding to the requirement to be appended, and the main requirement ID to which the parent requirement belongs. This allows the sub-requirement appending function to perform recursive queries starting from the main requirement ID, add the nesting information corresponding to the requirement to be appended to the internal variable information of each parent requirement of the parent requirement, add the requirement ID to the component information of the parent requirement, and determine whether the requirement to be appended was successfully appended based on the return result of the sub-requirement appending function.

5. The demand management method as described in claim 2, characterized in that, The demand management request includes a demand statistics request. The target demand management function includes a sub-demand statistics function. The sub-demand statistics function is used to query the attributes to be counted in the current structured demand data and perform statistics on the queried attributes. It also calls itself to query the attributes to be counted in the next level of structured demand data and perform statistics until the statistics of the attributes to be counted in each structured demand data is completed. The step of managing the structured requirement data in the database according to the requirement management request and the target requirement management function includes: The attribute to be statistically analyzed carried in the demand statistics request is assigned to the sub-demand statistics function, so as to obtain the statistical result corresponding to the attribute to be statistically analyzed based on the return result of the sub-demand statistics function.

6. A demand management device, characterized in that, The device includes: The data acquisition unit is used to acquire the original requirement document and the pre-built requirement data model, wherein the requirement data model is used to convert the original requirement document into structured requirement data with a nested structure. The data processing unit is used to convert the original requirement document into structured requirement data with a nested structure according to the requirement data model, and to store the structured requirement data with a nested structure into a database. The data management unit is used to perform recursive operations on the structured requirement data with nested structures in the database to achieve requirement management; The required data model is constructed using the following steps: The components of the construction requirement include attribute information and nested structure. The attribute information includes multi-dimensional attributes corresponding to the requirement data. The nested structure includes component information and internal variable information. The component information includes direct sub-requirement information. The internal variable information includes sub-requirements at all levels of the direct sub-requirement and nested information corresponding to each level of sub-requirement. The nested information is used to indicate the relationship between each level of sub-requirement and the direct sub-requirement information in the component information. The demand data model is constructed based on the information of the components of the demand; The original requirement document includes a requirement directory, which includes at least one main requirement and sub-requirements at each level corresponding to each main requirement. The step of converting the original requirement document into structured requirement data with a nested structure according to the requirement data model includes: Obtain the attribute information and nesting structure of each requirement based on the requirement catalog; Using the aforementioned demand data model, and based on the attribute information and nested structure of each demand, each demand in the demand catalog is converted into structured demand data with a nested structure.

7. An electronic device, characterized in that, The electronic device includes: Processor; and A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the demand management method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which, when executed by an electronic device including multiple applications, cause the electronic device to perform the demand management method as described in any one of claims 1-5.

Images