Demand splitting method, device, computer equipment and readable storage medium

Abstract

The embodiment of the present invention provides a method, device, computer equipment and readable storage medium for splitting requirements, which can be used in the field of big data or other fields; wherein the method comprises the following steps: receiving a requirement specification, which is filled out based on a requirement template; identifying the chapter structure of the requirement specification; identifying the smallest chapter in each chapter; and splitting the requirement items in each smallest chapter. The solution is conducive to improving the efficiency of requirement splitting, realizing the requirement splitting in an agile mode, helping to reduce or avoid misunderstandings, and helping to improve the accuracy of requirement splitting.

Description

Technical Field

[0001] The present invention particularly relates to a demand splitting method, device, computer equipment and readable storage medium. It should be noted that the demand splitting method, device, computer equipment and readable storage medium of the present invention can be used in the field of big data, and can also be used in any field except the field of big data. The present invention does not limit the application field of the demand splitting method, device, computer equipment and readable storage medium. Background Art

[0002] The agile thinking of value-driven and continuous delivery should run through the entire engineering activity. Faced with the complex and huge requirement specifications proposed by the business, how to efficiently and quickly split the requirements and arrange the value of the requirements is an important task of demand management.

[0003] Currently, demand splitting mainly relies on communicating with business personnel to split demand items according to business descriptions, or reviewing demand documents and manually splitting demand items according to the directory structure.

[0004] The existing demand splitting methods have the following defects: relying on the existing communication process, it is easy to have misunderstandings, waste a lot of manpower, and be inefficient; or in the face of huge demands, it is difficult to achieve continuous delivery, rapid iteration, and implement agile thinking without splitting the demands. Summary of the invention

[0005] The embodiment of the present invention provides a method for demand splitting to solve the technical problems of low efficiency and low accuracy in demand splitting in the prior art. The method comprises:

[0006] receiving a requirement specification, wherein the requirement specification is filled out based on a requirement template;

[0007] Identify the chapter structure of the requirements specification;

[0008] Identify the smallest section in each chapter;

[0009] Split the requirements into minimum sections.

[0010] The embodiment of the present invention also provides a demand splitting device to solve the technical problems of low efficiency and low accuracy in demand splitting in the prior art. The device includes:

[0011] A receiving module, used for receiving a requirement specification, wherein the requirement specification is filled in based on a requirement template;

[0012] A structure recognition module, used to recognize the chapter structure of the requirement specification;

[0013] A minimum chapter identification module, used to identify the minimum chapter in each chapter;

[0014] The requirement item splitting module is used to split the requirement items into each minimum chapter.

[0015] An embodiment of the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements any of the above-mentioned demand splitting methods to solve the technical problems of low efficiency and low accuracy in demand splitting in the prior art.

[0016] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program for executing any of the above-mentioned demand splitting methods to solve the technical problems of low efficiency and low accuracy in demand splitting in the prior art.

[0017] In an embodiment of the present invention, it is proposed to receive a requirement specification based on a requirement template, then identify the chapter structure of the requirement specification, and then identify the smallest chapter in each chapter. Finally, the requirement items in each smallest chapter can be split, thereby realizing the gradual splitting of the requirement items based on the structure and smallest chapter of the requirement template. Compared with the prior art, it avoids manual splitting of requirements, is conducive to improving the efficiency of requirement splitting, and realizes the requirement splitting of an agile mode. In addition, splitting requirements based on the structure and smallest chapter of the requirement template is conducive to reducing or avoiding misunderstandings and improving the accuracy of requirement splitting compared with manual communication and other methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present invention, constitute a part of the present application, and do not constitute a limitation of the present invention. In the drawings:

[0019] Figure 1 is a flow chart of a demand splitting method provided by an embodiment of the present invention;

[0020] Figure 2 is a flow chart for identifying the chapter structure of the requirement specification provided by an embodiment of the present invention;

[0021] Figure 3 A flowchart for splitting the requirements in each minimum chapter provided by an embodiment of the present invention;

[0022] Figure 4 is a structural block diagram of a computer device provided by an embodiment of the present invention;

[0023] Figure 5 It is a structural block diagram of a demand splitting device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the embodiments and the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0025] In an embodiment of the present invention, a method for splitting requirements is provided, such as Figure 1 As shown, the method includes:

[0026] Step 102: receiving a requirement specification, wherein the requirement specification is filled out based on a requirement template;

[0027] Step 104: Identify the chapter structure of the requirements specification;

[0028] Step 106: Identify the smallest chapter in each chapter;

[0029] Step 108: Split the requirements into each smallest section.

[0030] Depend on Figure 1 It can be seen from the process shown that in the embodiment of the present invention, it is proposed to receive the requirement specification based on the requirement template, then identify the chapter structure of the requirement specification, and then identify the smallest chapter in each chapter. Finally, the requirement items in each smallest chapter can be split, thereby realizing the gradual splitting of the requirement items based on the structure and smallest chapter of the requirement template. Compared with the prior art, manual splitting of requirements is avoided, which is conducive to improving the efficiency of requirement splitting and realizing the agile mode of requirement splitting. In addition, splitting requirements based on the structure and smallest chapter of the requirement template is conducive to reducing or avoiding misunderstandings and improving the accuracy of requirement splitting compared with manual communication and other methods.

[0031] In the specific implementation, it is proposed to receive the requirement specification based on the requirement template, that is, in the process of receiving the requirement specification, the content of the requirement specification is filled in according to the structure and format of the requirement template, and then the chapter structure of the requirement specification can be identified based on the requirement template. Identifying the chapter structure of the requirement template is to identify the chapter structure of the requirement specification, which makes the requirement identification and splitting more regular and structured.

[0032] During specific implementation, the above-mentioned demand templates can set different demand templates for different business types.

[0033] In specific implementation, after receiving the requirement specification, the chapter structure of the requirement specification can be identified. In order to accurately identify the chapter structure, in this embodiment, Figure 2 As shown in the figure, the process of identifying the chapter structure of the requirements specification is achieved through the following steps:

[0034] Step 202: Identify the titles of each level in the requirement specification according to the title numbers;

[0035] Step 204: Identify the parent title and subtitle relationship between titles at each level to obtain the chapter structure of the requirements specification.

[0036] In specific implementation, the requirement template can set up a multi-level title framework to describe the text content of each part of the requirement. When the user enters the requirement specification, he can choose to use several levels of titles according to the specific situation of the requirement. For example, the first-level title can have revision records, requirement overview, requirement function description, non-functional requirements, etc. The second-level title can have requirement background, requirement goals, functional module composition, name terms, requirement process, module general requirements, functional detailed description, stability, security, user interface requirements, operation requirements, etc. The third-level title can have key business processes, sub-function / module descriptions, data verification, application server requirements, etc., that is, each level of title has a corresponding editing content area. Users can select the required article structure to generate a requirement template according to their needs. The requirement template has a framework structure, and the business fills in the requirement content.

[0037] In specific implementation, based on the title structure of the requirements specification, this embodiment proposes that the titles of each level in the requirements specification can be identified according to the title number. For example, taking the three-level title as an example, the first-level title includes 1, 2, 3, etc., the second-level title includes 1.1, 1.2, ..., 2.1, 2.2 ..., 3.1, etc., and the third level includes 1.1.1, 1.1.2 ..., 1.2.1, ..., 2.1.1, ... 2.2.1 ..., 3.1.1 ..., etc., and so on. After identifying the titles of each level, the parent title and sub-title relationship between the titles of each level is identified, and the chapter structure of the requirements specification can be obtained. For example, when the first-level title 1 is the parent title, the second-level titles 1.1, 1.2, 1.3 ..., etc. are sub-titles. When the second-level title 1.1 is the parent title, the third-level titles 1.1.1, 1.1.2, 1.1.3 ..., etc. are sub-titles. By analogy, the belonging relationship or parent-child relationship between the titles of each level under the first-level title can be identified.

[0038] In specific implementation, the smallest chapter of each chapter can be further identified based on the chapter structure. For example, the subheadings at each level under the parent title can be identified according to the title number; each level of subheading is regarded as a parent title, and the subheadings at each level under the parent title are identified until the title with the smallest title number. The title with the smallest title number is the smallest chapter in the chapter.

[0039] Specifically, for example, taking the third-level titles as an example, when the first-level title 1 is the parent title, the second-level titles 1.1, 1.2, 1.3, etc. are sub-titles, and then the second-level titles 1.1, 1.2, 1.3, etc. are regarded as parent titles respectively, and the sub-titles of the second-level title 1.1 include the third-level titles 1.1.1, 1.1.2, 1.1.3, etc., and the sub-titles of the second-level title 1.2 include the third-level titles 1.2.1, 1.2.2, 1.2.3, etc. Level 1 title, the subtitles of the second-level title 1.3 include level 3 titles such as 1.3.1, 1.3.2, 1.3.3…, etc. At this time, it is found that the level 3 title is the title with the smallest title number, then the level 3 titles 1.1.1, 1.1.2, 1.1.3…, 1.2.1, 1.2.2, 1.2.3…, 1.3.1, 1.3.2, 1.3.3…, etc. are all the smallest chapters of the first-level title 1, and can form a minimum level chapter group.

[0040] Specifically, the various minimum directory chapters of the chapter can be identified based on the chapter that needs to refine the requirement items. For example, if the parent chapter is specified as chapter 3.2, the various minimum directory chapters identified are 3.2.1, 3.2.2, ... and so on.

[0041] In specific implementation, after identifying the chapter structure and the smallest chapter of each chapter, the requirements in each smallest chapter can be split to achieve fine-grained requirements, such as Figure 3 As shown, the following steps are used to split the requirements into each minimum chapter:

[0042] Step 302: Split each title in the smallest chapter into a title description according to the title number, and each title description forms a title group;

[0043] Step 304: Filter title descriptions related to the required content in the title group as required items.

[0044] Specifically, business or demand analysts can mark the level at which the demand structure is split, first level, second level, third level or fourth level, and extract the level group of each level. The title in the level group has attributes such as title number and title description. If the demand is split according to the third-level title, the third-level title group is extracted (for example, title 1.1.1 is split into title description 1; title 1.1.2 is split into title description 2; title 2.1.1 is split into title description 3; and so on). Then the demand manager selects the title description related to the demand content in the title group to form a set of demand items for this demand, and extracts the set of demand items according to a single title description to complete the splitting of the demand items.

[0045] In specific implementation, after splitting the requirements of the requirements specification, the splitting results can be fed back to the user by displaying, sending, etc. For example, the requirements and functional descriptions can be listed and then displayed to the user.

[0046] In specific implementation, the above-mentioned demand splitting method relies on identifying the structure of the demand template, marking key chapters and the smallest decomposition chapters, extracting functional requirements, and managing the requirements in a refined manner, which is conducive to continuous delivery; the identified functional requirements are synthesized into a demand item list and output to customers for rapid business identification, which is conducive to providing data basis for calibrating business value priorities and achieving high-value priority response.

[0047] In this embodiment, a computer device is provided, such as Figure 4 As shown, it includes a memory 402, a processor 404, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, any of the above-mentioned demand splitting methods is implemented.

[0048] Specifically, the computer device may be a computer terminal, a server or a similar computing device.

[0049] In this embodiment, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program for executing any of the above-mentioned demand splitting methods.

[0050] Specifically, computer-readable storage media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer-readable 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 technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable storage media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0051] Based on the same inventive concept, a demand splitting device is also provided in the embodiment of the present invention, as described in the following embodiment. Since the principle of solving the problem by the demand splitting device is similar to that of the demand splitting method, the implementation of the demand splitting device can refer to the implementation of the demand splitting method, and the repeated parts will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements predetermined functions. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0052] Figure 5 is a structural block diagram of a demand splitting device according to an embodiment of the present invention, such as Figure 5 As shown, the device comprises:

[0053] A receiving module 502 is used to receive a requirement specification, where the requirement specification is filled in based on a requirement template;

[0054] A structure identification module 504, used to identify the chapter structure of the requirement specification;

[0055] A minimum chapter identification module 506, used to identify the minimum chapter in each chapter;

[0056] The requirement item splitting module 508 is used to split the requirement items in each minimum chapter.

[0057] In one embodiment, the structure recognition module includes:

[0058] A title identification unit, used to identify the titles of various levels in the requirement specification according to the title numbers;

[0059] The title relationship identification unit is used to identify the parent title and subtitle relationship between titles at all levels to obtain the chapter structure of the requirements specification.

[0060] In one embodiment, the minimum chapter identification module is used to identify the sub-titles at each level under each parent title according to the title number; regard the sub-titles at each level as the parent title, and identify the sub-titles at each level under the parent title until the title with the smallest title number, and the title with the smallest title number is the smallest chapter in the chapter.

[0061] In one embodiment, the requirement item splitting module includes:

[0062] A title description splitting unit is used to split each title in the smallest chapter into a title description according to the title number, and each title description constitutes a title group;

[0063] The requirement item screening unit is used to screen the title descriptions related to the requirement content in the title group as requirement items.

[0064] The embodiments of the present invention achieve the following technical effects: it proposes receiving a requirement specification based on a requirement template, then identifying the chapter structure of the requirement specification, and then identifying the smallest chapter in each chapter. Finally, the requirement items in each smallest chapter can be split, thereby gradually splitting the requirement items based on the structure and smallest chapter of the requirement template. Compared with the prior art, manual splitting of requirements is avoided, which is beneficial to improving the efficiency of requirement splitting and realizing agile mode requirement splitting. In addition, splitting requirements based on the structure and smallest chapter of the requirement template is beneficial to reducing or avoiding misunderstandings and improving the accuracy of requirement splitting compared with manual communication and other methods.

[0065] Although the present invention provides method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the actual device or client product is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, in a parallel processor or multi-threaded processing environment).

[0066] It should be understood by those skilled in the art that the embodiments of this specification may be provided as methods, devices (systems) or computer program products. Therefore, the embodiments of this specification may take the form of complete hardware embodiments, complete software embodiments or embodiments combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0067] The present invention is described with reference to flowcharts and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as a combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0068] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0069] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0070] Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. In this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such a process, method, article or device. The orientation or position relationship indicated by the terms "upper", "lower", etc. is based on the orientation or position relationship shown in the drawings, which is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present invention. Unless otherwise expressly specified and limited, the terms "installed", "connected" and "connected" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be a connection between the two components. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances. It should be noted that the embodiments of the present invention and the features in the embodiments can be combined with each other in the absence of conflict. The present invention is not limited to any single aspect, nor to any single embodiment, nor to any combination and / or permutation of these aspects and / or embodiments. Moreover, each aspect and / or embodiment of the present invention can be used alone or in combination with one or more other aspects and / or embodiments thereof.

[0071] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. These modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be included in the scope of the claims and specification of the present invention.

Claims

1. A demand splitting method, characterized in that: include: Receiving a requirement specification, wherein the requirement specification is filled out based on a requirement template; Identify the chapter structure of the requirements specification; Identify the smallest section in each chapter; Split the requirements into each smallest section; The requirements in each minimum chapter are divided into: Split each title in the smallest chapter into a title description according to the title number, and each title description forms a title group; The title descriptions related to the required content are screened from the title group as the required items.

2. The demand splitting method according to claim 1, characterized in that: Identify the chapter structure of the requirements specification, including: Identify the various levels of titles in the requirements specification according to the title numbers; Identify the parent title and subtitle relationship between titles at each level to obtain the chapter structure of the requirement specification.

3. The demand splitting method according to claim 2, characterized in that: Identify the smallest sections within each chapter, including: Identify the sub-headings under each parent heading according to the heading number; Treat each level of subheadings as the parent title, identify each level of subheadings under the parent title, until the title with the smallest title number, which is the smallest chapter in the chapter.

4. A demand splitting device, characterized in that: include: A receiving module, used for receiving a requirement specification, wherein the requirement specification is filled in based on a requirement template; A structure recognition module, used to recognize the chapter structure of the requirement specification; A minimum chapter identification module, used to identify the minimum chapter in each chapter; The requirement item splitting module is used to split the requirement items into each minimum chapter; Demand item splitting module, including: A title description splitting unit is used to split each title in the smallest chapter into a title description according to the title number, and each title description constitutes a title group; The requirement item screening unit is used to screen the title descriptions related to the requirement content in the title group as requirement items.

5. The demand splitting device according to claim 4, characterized in that: Structure recognition module, including: A title identification unit, used to identify the titles of various levels in the requirement specification according to the title numbers; The title relationship identification unit is used to identify the parent title and subtitle relationship between titles at all levels to obtain the chapter structure of the requirements specification.

6. The demand splitting device according to claim 5, characterized in that: The minimum chapter identification module is used to identify the sub-titles under each parent title according to the title number; regard the sub-titles at each level as the parent title, and identify the sub-titles under the parent title until the title with the smallest title number. The title with the smallest title number is the smallest chapter in the chapter.

7. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the demand splitting method according to any one of claims 1 to 3 is implemented.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the demand splitting method according to any one of claims 1 to 3 is implemented.

Images