Demand management report generation method and device, storage medium and computer equipment

Abstract

The invention provides a demand management report generation method and device, a storage medium and computer equipment. The method comprises the steps that storage position information of a code management tool is acquired, and to-be-queried information for code demand management is acquired; wherein the to-be-queried information comprises a user identifier of a to-be-queried user; based on the storage position information and the user identifier, analyzing to obtain a demand task identifier of demand management submitted by the to-be-queried user in demand management; and generating a demand management report of the to-be-queried user according to the demand task identifier and the user information of the to-be-queried user. The effect of improving the efficiency of completing the demand management report can be achieved.

Description

Technical Field

[0001] The present application relates to the field of data management technology, and in particular to a method, device, storage medium, and computer equipment for generating a demand management report. Background Art

[0002] With the development of software technology, software functions are increasing. At the same time, the demand for software development management is also increasing. Usually, requirement management tools are used to manage software requirements, and version management tools are used to manage software codes.

[0003] For software developers, in addition to completing daily development tasks, they also need to regularly complete demand management reporting work, etc. In related technologies, software developers manually complete demand management reports after consulting demand management and other documents.

[0004] However, during the implementation process, the applicant discovered that the related technology at least has the problem of low efficiency in completing demand management reports. Summary of the invention

[0005] Based on this, the purpose of this application is to solve at least one of the above-mentioned technical defects, especially the technical defect of low efficiency in completing demand management reports in the prior art, and to provide a demand management report generation method, device, storage medium, and computer equipment.

[0006] In a first aspect, the present application provides a method for generating a demand management report, the method comprising:

[0007] Obtaining storage location information of the code management tool, and obtaining information to be queried for code demand management; wherein the information to be queried includes a user identifier of a user to be queried;

[0008] Based on the storage location information and the user ID, the requirement task ID of the requirement management submitted by the user to be queried is obtained by parsing;

[0009] Generate a demand management report for the user to be queried based on the demand task identifier and the user information of the user to be queried.

[0010] In one of the embodiments, the information to be queried also includes query time;

[0011] Based on the storage location information and the user ID, the requirement task ID of the requirement management submitted by the user to be queried is obtained through parsing, including:

[0012] Determine the query instruction based on the user identifier and the query time;

[0013] According to the storage location information and the query instruction, the required task identifier corresponding to the user to be queried is obtained by parsing.

[0014] In one embodiment, generating a demand management report of the user to be queried according to the demand task identifier and the user information of the user to be queried includes:

[0015] According to the demand task identifier and the user information of the user to be queried, the target detailed information of each demand task of the user to be queried is obtained;

[0016] Generate a demand management report for the user to be queried based on the target detailed information.

[0017] In one embodiment, according to the required task identifier and the user information of the user to be queried, the target detailed information of each required task of the user to be queried is obtained, including:

[0018] Determine the interface status of the requirements management tool;

[0019] When the interface status represents that the requirement management tool has an application development interface, the application development interface is called, and the target detailed information of each requirement task for the user to be queried is obtained by using the requirement task identifier and the user information of the user to be queried.

[0020] In one of the embodiments, after determining the interface status of the requirement management tool, the method further includes:

[0021] In the case where the interface status represents that the requirement management tool does not have an application development interface, an interface for the requirement management list is obtained after logging into the requirement management tool based on user information of the user to be queried;

[0022] Obtain input parameter information and request information for demand management;

[0023] Call the interface of the demand management list, and use the input parameter information, request information and demand task identifier to obtain the target detailed information of each demand task for the user to be queried.

[0024] In one embodiment, the requirements management report includes the labor hours required;

[0025] Generate a demand management report for the user to be queried based on the target detailed information, including:

[0026] Determine the cycle length of demand management reporting;

[0027] From the target detailed information, obtain the number of submissions corresponding to each requirement task identifier and the total number of submissions of multiple requirement task identifiers;

[0028] Based on the cycle duration and the ratio between the number of submissions corresponding to each demand task identifier and the total number of submissions, the working hours corresponding to each demand task identifier are determined.

[0029] In one embodiment, obtaining storage location information of a code management tool includes:

[0030] Get the storage directory of the code management tool;

[0031] From the storage directory, traverse the directory of the extension information corresponding to the storage path to obtain the storage location information.

[0032] In a second aspect, the present application provides a demand management report generating device, the device comprising:

[0033] An acquisition module, used to acquire storage location information of a code management tool and to acquire information to be queried for code demand management; wherein the information to be queried includes a user ID of a user to be queried;

[0034] A parsing module, used for parsing and obtaining the demand task identifier of the demand management submitted by the user to be queried in the demand management based on the storage location information and the user identifier;

[0035] The generation module is used to generate a demand management report of the user to be queried according to the demand task identifier and the user information of the user to be queried.

[0036] In a third aspect, the present application provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0037] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the above method when the computer program is executed by a processor.

[0038] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0039] The present application provides a method, device, storage medium, and computer equipment for generating a demand management report. Through the storage location information of the code management tool and the user identifier of the user to be queried, it is possible to parse the demand task identifier of the demand management submitted by the user, and to generate a demand management report for the user to be queried based on the demand task identifier and the user information. In this way, the present application can automatically generate a demand management report associated with the user to be queried by parsing the demand task identifier, thereby automating the completion of the demand management report and further improving the efficiency of completing the demand management report. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0041] Figure 1 A schematic diagram of the principle of a method for generating a demand management report in a related technology provided by this application;

[0042] Figure 2 A schematic diagram of a method for generating a demand management report provided for this application Figure 1 ;

[0043] Figure 3 A schematic diagram of a method for generating a demand management report provided for this application Figure 2 ;

[0044] Figure 4 A schematic diagram of a method for generating a demand management report provided for this application Figure 3 ;

[0045] Figure 5 A schematic diagram of a method for generating a demand management report provided for this application Figure 4 ;

[0046] Figure 6 A schematic diagram of the principle of a method for generating a demand management report provided for this application;

[0047] Figure 7 A schematic diagram of a method for generating a demand management report provided for this application Figure 5 ;

[0048] Figure 8 A schematic diagram of the structure of a demand management report generation device provided in this application;

[0049] Fig. 9 A schematic diagram of the internal structure of a computer device provided in this application. DETAILED DESCRIPTION

[0050] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0051] With the development of software technology, software functions are increasing. At the same time, the demand for software development management is also increasing. Usually, requirement management tools are used to manage software requirements, and version management tools are used to manage software codes.

[0052] For software developers, in addition to completing daily development tasks, they also need to regularly complete demand management reporting work, etc. In related technologies, software developers manually complete demand management reports after consulting demand management and other documents.

[0053] Figure 1 A schematic diagram of the principle of a method for generating a demand management report in a related technology provided by this application; Figure 1 As shown, user 101 generates work report 103 by executing step S102. Step S102 includes: self-meeting, reviewing requirement documents, code submission records, and sorting them one by one. In this process, there are usually the following problems: it takes a lot of time, which will squeeze the development time of software developers; the completion details of the requirements are easy to be misremembered or missed.

[0054] Based on the above background, it can be seen that for software development management, related technologies usually require workers to organize demand management reports by themselves, which easily leads to problems of low efficiency and high error rate.

[0055] Based on this, the present application provides a method, device, storage medium, and computer equipment for generating a demand management report. The present application can automatically parse the demand task identifier related to the user to be queried through the submission records of the demand management tool and the code management tool, and automatically generate the demand management report associated with the user to be queried based on the demand task identifier, thereby improving the efficiency of completing the demand management report and reducing the error rate of the demand management report.

[0056] In an exemplary embodiment, Figure 2 A schematic diagram of a method for generating a demand management report provided for this application Figure 1 ,like Figure 2 As shown, this embodiment uses the method applied to a terminal as an example. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method includes steps: S201 to S203, wherein:

[0057] S201. Obtain storage location information of a code management tool, and obtain information to be queried for code requirement management; wherein the information to be queried includes a user identifier of a user to be queried.

[0058] The code management tool can be a version control tool in software development, which can be used to save different versions of files and roll back to any historical version when needed. The code management tool can be used to keep the development progress and change records of multiple developers. For example, the code management tool can be Git.

[0059] The storage location information may refer to the local repository path of the code management tool. For example, in the Git repository path, there is a directory for storing code; that is, based on each directory folder, a path for storing code is formed.

[0060] Code requirement management may refer to the requirement management of different versions. The information to be queried may refer to the requirement task information that needs to be queried, for example, the information to be queried may include the user information who completes the requirement task, the time information of the requirement task, etc. Among them, the user information may include the user identifier (such as user name, user number, etc.), and the time information may include the start time, end time, etc.

[0061] Exemplarily, the terminal may obtain the repository path of the code management tool in a local specified directory, that is, may determine the local storage location information of the code management tool, so that the terminal may obtain the submission record in the code management tool.

[0062] For example, when the code management tool is Git, the parent directory with the .git file in the directory where the Git code is stored locally can be used as the Git repository path, that is, it can be used as storage location information.

[0063] For example, when a demand report needs to be generated, the user can enter relevant information about the query demand management in the terminal, such as the user ID corresponding to the user to be queried and the time period to be queried, etc. In this way, the terminal can determine the information to be queried for code demand management.

[0064] As an example, obtaining the information to be queried for code requirement management may include: after reaching a preset time, the terminal may directly obtain a preset user identifier and a preset time period information to be queried to determine the information to be queried for code requirement management. In this way, the information to be queried may be further automatically determined without the user having to input the user information and the time information to be queried multiple times.

[0065] Optionally, when performing requirement management on the code, the requirement task identifier corresponding to the requirement management tool needs to be attached when submitting the code to the code management tool. In this way, the requirement management detailed information can be matched to each requirement task identifier.

[0066] S202: Based on the storage location information and the user identifier, the requirement task identifier of the requirement management submitted by the user to be queried is obtained by parsing.

[0067] The requirement task identifier may refer to the requirement task ID or the requirement ID. For the requirement management tool, when the requirement management is generated, a requirement ID, that is, the requirement task identifier, will be generated. It can be understood that the requirement task identifier includes the requirement ID and may also include the requirement task name, etc. The requirement ID is one form of the requirement task identifier.

[0068] Exemplarily, the terminal may obtain submission records in the code management tool through the storage location information of the code management tool and the user identifier to be queried, and may parse out a requirement task identifier for requirement management based on the submission record.

[0069] For example, the terminal can obtain all submission records of the author within the specified query date range by combining the Git repository path, instructions for viewing the Git submission log, author username, query date range, etc. Based on the submission records, each required task identifier can be parsed.

[0070] As an example, the instruction for viewing the Git commit log is also the Git view commit log instruction. The query date range can be determined based on the author user name and the query date range. By using the Git view commit log instruction and the Git repository path, running the exec function can parse and obtain the requirement ID.

[0071] In this way, through the above steps or embodiments, it is possible to obtain the demand task identifier for demand management, which is conducive to the subsequent generation of a demand management report using the demand task identifier.

[0072] S203: Generate a demand management report of the user to be queried according to the demand task identifier and the user information of the user to be queried.

[0073] The user information may refer to the user's information in the requirement management tool, for example, information used to verify the user's identity, user login information, etc. The requirement management report may refer to the user's work report on requirement management, for example, the requirement management report may include requirement task identification, requirement name, requirement description, priority, contact person, start time, end time, working hours, etc.

[0074] The demand management report may include detailed information on demand management, and may also include interface information applied to each demand, as well as the start time and end time of the application interface.

[0075] Exemplarily, the terminal can call the interface of the demand management tool, and use the demand task identifier and the user information corresponding to the user to be queried to determine the detailed information of the demand corresponding to the user to be queried from the demand management tool, such as title, description, related personnel, priority, etc. In this way, the detailed information of the demand associated with the user can be used to generate a demand management report corresponding to the user.

[0076] Optionally, based on the user information of the user to be queried, the requirement management tool may be logged in, and detailed information of the corresponding requirement may be obtained through the requirement task identifier.

[0077] Optionally, detailed information of the requirement corresponding to the requirement task identifier associated with the user information may also be obtained through a web crawler.

[0078] Exemplarily, the terminal can determine the cycle duration corresponding to the demand management report, and based on the cycle duration, determine the start time and end time corresponding to each demand. For example, the initial submission time and the final submission time corresponding to the demand task identifier can be used as the start time and the end time corresponding to the demand task identifier, respectively. The terminal can also determine the approximate working hours of each demand based on the number of submissions corresponding to the demand task identifier and the total number of submissions of all demand task identifiers.

[0079] In this way, through the above steps or embodiments, the detailed information of the requirements corresponding to the requirement task identifier associated with the user information can be effectively determined, and the user's requirement management report can be generated without the user having to manually complete the requirement management report, thereby improving the efficiency of completing the requirement management report and reducing the error rate of the requirement management report.

[0080] In this embodiment, through the storage location information of the code management tool and the user identifier of the user to be queried, the requirement task identifier of the requirement management submitted by the user can be parsed, and based on the requirement task identifier and the user information, a requirement management report for the user to be queried can be generated. In this way, the present application can automatically generate a requirement management report associated with the user to be queried by parsing the requirement task identifier, thereby realizing automated completion of the requirement management report, and further improving the efficiency of completing the requirement management report.

[0081] In an exemplary embodiment, Figure 3 A schematic diagram of a method for generating a demand management report provided for this application Figure 2 ,like Figure 3 As shown, in Figure 2Based on the above, the steps in the method for generating a demand management report are described in detail, wherein the information to be queried also includes the query time; in step S202, based on the storage location information and the user identifier, the demand task identifier of the demand management submitted by the user to be queried is parsed and obtained, including S301 and S302, wherein:

[0082] S301: Determine a query instruction based on a user identifier and a query time.

[0083] S302: According to the storage location information and the query instruction, the required task identifier corresponding to the user to be queried is obtained by parsing.

[0084] The query time may refer to a query date range, that is, a date range for querying requirements, and the query date range may be determined based on a start time and an end time. The query instruction may refer to an instruction for searching for a required task in a storage path.

[0085] Exemplarily, the terminal can determine the query instruction to be used, and obtain the query instruction for querying the demand task identifier through the user identifier and the query time. The terminal can parse the demand task identifier corresponding to the user to be queried by using the storage location information and the query instruction through the function of the relevant execution code. For example, the terminal can obtain the demand task identifier associated with the user by using the storage location information and the query instruction through the exec() function.

[0086] Optionally, the terminal can form a corresponding query instruction according to the query date range and the user name, and the query instruction is used to query the demand corresponding to the demand task identifier associated with the above user name within the above query date range. The demand task identifier needs to be found from the storage location information, that is, the above steps can effectively determine the demand task identifier corresponding to the user to be queried.

[0087] In this embodiment, the query instruction is determined by the user identifier and the query time, so that the demand task identifier corresponding to the user to be queried can be further parsed according to the storage location information and the query instruction, which is conducive to the automatic generation of the demand management report, thereby improving the efficiency of completing the demand management report and providing a basis for the demand management report.

[0088] In an exemplary embodiment, Figure 4 A schematic diagram of a method for generating a demand management report provided for this application Figure 3 ,like Figure 4 As shown, in Figure 2Based on the above, the steps in the method for generating a demand management report are described in detail. Step S203 generates a demand management report for the user to be queried according to the demand task identifier and the user information of the user to be queried, including S401 and S402, wherein:

[0089] S401, obtaining target detailed information of each demand task of the user to be queried according to the demand task identifier and the user information of the user to be queried;

[0090] S402: Generate a demand management report for the user to be queried based on the target detailed information.

[0091] The requirement task is the requirement corresponding to the requirement task identifier. The target detailed information may refer to the detailed information content corresponding to the requirement, for example, it may be information about a code version update.

[0092] Exemplarily, the terminal can obtain the target detailed information of each requirement submitted and completed by the user corresponding to the user information by calling the application development interface provided by the requirement management tool, using the requirement task identifier and the user information to be queried. In other words, the terminal can obtain the target detailed information corresponding to each requirement associated with the user, and further, it is conducive to generating a requirement management report for the user through the target detailed information, that is, a report on the requirement work submitted and completed by the user can be formed in the above manner. Furthermore, the requirement management report can be used to reflect the work content, efficiency and other indicators of the user (worker).

[0093] In this embodiment, through the requirement task identification and the user information of the user to be queried, the target detailed information of each requirement task related to the user can be obtained; based on each target detailed information, a requirement management report related to the user to be queried can be generated, thereby eliminating the need for software development workers to complete the requirement management report by themselves, thereby improving the efficiency of completing the requirement management report and reducing the error rate of the requirement management report.

[0094] In an exemplary embodiment, according to the required task identifier and the user information of the user to be queried, the target detailed information of each required task of the user to be queried is obtained, including:

[0095] Determine the interface status of the requirements management tool;

[0096] When the interface status represents that the requirement management tool has an application development interface, the application development interface is called, and the target detailed information of each requirement task for the user to be queried is obtained by using the requirement task identifier and the user information of the user to be queried.

[0097] The interface status may indicate whether the requirement management tool provides an application development interface. The application development interface may be an API interface.

[0098] For example, the terminal can determine whether the requirement management tool has an application development interface. If the requirement management tool has an application development interface, the terminal can call the application development interface and use the requirement task identifier and user information such as user name and password to obtain the target detailed information of the requirements corresponding to each requirement task identifier associated with the user.

[0099] Optionally, call the API interface, add the requirement ID, and add the username and password information to the request header, and you can get detailed information about the requirement corresponding to the requirement ID from the requirement management tool, such as title, description, related personnel, priority, etc.

[0100] Furthermore, the target detailed information of the requirements corresponding to each requirement task identifier associated with the user to be queried can be used to generate the requirement management report of the user. In this way, the detailed information can be automatically obtained and the requirement management report can be generated, thereby improving the efficiency of completing the requirement management report and reducing the error rate.

[0101] In this embodiment, when the demand management tool has an application development interface, the application development interface is called, and the target detailed information of each demand task for the user to be queried can be obtained by using the demand task identifier and the user information of the user to be queried. In this way, the target detailed information of the demand can be directly obtained, thereby providing a data basis for the generation of the demand management report.

[0102] In an exemplary embodiment, after determining the interface status of the requirement management tool, the method further includes:

[0103] In the case where the interface status represents that the requirement management tool does not have an application development interface, an interface for the requirement management list is obtained after logging into the requirement management tool based on user information of the user to be queried;

[0104] Obtain input parameter information and request information for demand management;

[0105] Call the interface of the demand management list, and use the input parameter information, request information and demand task identifier to obtain the target detailed information of each demand task for the user to be queried.

[0106] The input parameter information may refer to the parameter information required for calling the interface, and the request information may refer to the data used to generate the request.

[0107] Exemplarily, if the requirement management tool does not have an application development interface, the terminal can respond to the user-triggered requirement management tool login operation and log in to the requirement management tool using the user information of the user to be queried. After logging in to the requirement management tool, the terminal can determine the interface of the requirement list and obtain the input parameter information and request information of the requirement list, call the interface of the requirement management list, and input the input parameter information, request information and requirement task identifier to obtain the target detailed information of the requirement corresponding to the requirement task identifier.

[0108] In this way, when the requirements management tool does not provide a development interface, detailed information on the requirements can be effectively obtained, providing an effective data basis for generating requirements management reports.

[0109] In this embodiment, when the requirements management tool does not have an application development interface, it is possible to determine the interface of the requirements management list after logging into the requirements management tool based on the user information of the user to be queried, and by calling the interface of the requirements management list, using the input parameter information, request information and requirement task identifier, obtain the target detailed information of each requirement task for the user to be queried, thereby effectively determining the target detailed information of the requirements corresponding to each requirement task identifier, providing a basis for generating a requirements management report.

[0110] In an exemplary embodiment, if the demand management tool does not provide a development interface and the demand management tool does not have an anti-crawler system, a crawler can be used to crawl the target detailed information of the demand task identifier corresponding to the user information. In this way, when the demand management tool does not provide a development interface, detailed information of the demand can be effectively obtained, providing an effective data basis for generating a demand management report.

[0111] In an exemplary embodiment, Figure 5 A schematic diagram of a method for generating a demand management report provided for this application Figure 4 ,like Figure 5 As shown, in Figure 4 On the basis of the above, the steps in the method for generating a demand management report are described in detail, wherein the demand management report includes the required working hours; in step S402, based on the target detailed information, a demand management report of the user to be queried is generated, including S501 to S503, wherein:

[0112] S501. Determine the cycle length of the demand management report.

[0113] S502: Obtain the number of submissions corresponding to each required task identifier and the total number of submissions of multiple required task identifiers from the target detailed information.

[0114] S503: Determine the working hours corresponding to the requirements of each demand task identifier based on the cycle duration and the ratio between the number of submissions corresponding to each demand task identifier and the total number of submissions.

[0115] Among them, the cycle duration can refer to the cycle included in the report. For example, if it is a weekly report for demand management, then the cycle duration can be one week's working hours, which can be 40 hours. The total number of submissions refers to the sum of the submission times of all demand tasks, that is, the sum of the submission times corresponding to the demand task identifiers. For example, if the demand task identifiers include A and B, the number of demand submissions for demand task identifier A is n times, and the number of demand submissions for demand task identifier B is m times, then the total number of submissions for the demand task identifiers is m+n. The working hours duration refers to the working hours corresponding to a demand task identifier.

[0116] Exemplarily, the terminal may determine the total working hours of a cycle corresponding to the demand management report to be generated based on the attributes of the demand management report. For example, the cycle duration may be based on user settings, such as when the user needs to generate a weekly report, the terminal may determine that the cycle duration is 40 hours.

[0117] The terminal can obtain the number of submissions of each requirement task identifier corresponding to the requirement from the target detailed information obtained by parsing. For example, a requirement may need to be processed and submitted multiple times, so the number of submissions corresponding to the requirement task identifier can be determined based on the multiple submissions. In addition, the terminal can determine the total number of submissions of multiple requirements corresponding to multiple requirement task identifiers.

[0118] The terminal can obtain the working time ratio of each demand task identifier corresponding to the demand based on the ratio between the number of submissions corresponding to each demand task identifier and the total number of submissions. That is, for each demand task identifier, the terminal can use the ratio between the number of submissions corresponding to the demand task identifier and the total number of submissions as the working time ratio of the demand corresponding to the demand task identifier. The terminal can obtain the working time length of the demand corresponding to the demand task identifier based on the product of the cycle length of the demand management report and the working time ratio.

[0119] Optionally, the terminal can obtain the initial submission time and the final submission time of each requirement task identifier within the cycle duration from the target detailed information obtained by parsing, and use them as the start time and end time of the corresponding requirement in the cycle. In this way, the requirement management report can include the start time and end time of each requirement task identifier corresponding to the requirement, so that the work content of the software developer can be more intuitively reflected.

[0120] Optionally, the terminal can determine the total working hours of a cycle set by the user, for example, based on a 40-hour working week, it can be set to 40; determine the start time and end time of the corresponding demand based on the initial submission time and the final submission time of each demand ID within the cycle; calculate the time proportion of each demand based on the number of submissions of each demand ID within the cycle, combined with the total number of submissions, and then multiply it by the total working hours of 40 within the cycle to calculate the approximate working hours of each demand; the terminal can generate a demand management report based on the above data, and the format of the demand management report can include: demand ID, demand name, demand description, priority, contact person, start time, end time, working hours, etc.

[0121] In this embodiment, by determining the cycle duration of the demand management report and obtaining the number of submissions corresponding to each demand task identifier and the total number of submissions of multiple demand task identifiers from the target detailed information, the working hours corresponding to each demand task identifier can be determined based on the cycle duration and the ratio between the number of submissions corresponding to each demand task identifier and the total number of submissions. In this way, the working hours of each demand can be effectively determined, which is conducive to objectively and intuitively reflecting the work efficiency and work content of the staff.

[0122] In an exemplary embodiment, obtaining storage location information of a code management tool includes:

[0123] Get the storage directory of the code management tool.

[0124] From the storage directory, traverse the directory of the extension information corresponding to the storage path to obtain the storage location information.

[0125] The storage directory may refer to a directory where the code management tool stores the code.

[0126] Exemplarily, the terminal can determine the storage directory of the code management tool in the local, and the storage directory may contain multiple levels of parent directories and child directories. In this way, the terminal can determine the storage location information from the multiple levels of storage directories.

[0127] The terminal can recursively traverse all folders with extension information corresponding to the storage paths under the storage directory, so as to obtain the storage location information of the code management tool.

[0128] For example, if the code management tool is git, the terminal can use the fs.readdir() function to recursively traverse all folders under the specified directory (the directory where the Git code is stored locally) and get the parent directories of all .git files, which is the Git warehouse path (storage location information).

[0129] In this embodiment, by obtaining the storage directory of the code management tool, the directory of the extension information corresponding to the storage path can be traversed from the storage directory to obtain the storage location information. This can effectively determine the storage location information of the code management tool, which can facilitate the automation of demand management report generation.

[0130] In an exemplary embodiment, obtaining information to be queried for code requirement management includes:

[0131] In response to the user's query information input operation, obtaining the input user identifier and query time;

[0132] Based on the user ID and query time, the information to be queried is obtained.

[0133] The query time may refer to a query date range.

[0134] For example, a user may input the required task information to be queried in the terminal so as to generate a required management report. In response to the user inputting the query information, the terminal may obtain the user identifier (such as user name, user number, etc.) to be queried and the time period to be queried (date range for which the report needs to be generated) input by the user. In this way, the terminal may generate the information to be queried based on the user identifier and the query time.

[0135] In this embodiment, through the above implementation steps, the relevant information for which a report needs to be generated can be effectively determined, which is conducive to automatically generating a demand management report, thereby improving the generation efficiency of the demand management report and reducing the error rate of the demand management report.

[0136] In an exemplary embodiment, Figure 6 A schematic diagram of the principle of a method for generating a demand management report provided for this application; Figure 6 As shown in the figure, the principles of the demand management report generation method are explained in detail, including:

[0137] The user 601 initiates an operation instruction for generating a demand management report in the terminal, and the terminal executes S602 to output a demand management report 603 .

[0138] The step S602 executes the script, that is, executes the steps of the above-mentioned method for generating a demand management report. Specifically, the implementation of the step S602 can refer to the above-mentioned embodiments.

[0139] In this way, the work details within the cycle can be automatically obtained through the script, without the need to recall or look through the records by yourself, which greatly saves the time of writing reports and prevents mistakes and omissions.

[0140] In an exemplary embodiment, Figure 7A schematic diagram of a method for generating a demand management report provided for this application Figure 5 ,like Figure 7 As shown, the method for generating a demand management report is described in detail. The method for generating a demand management report includes S701 to S705, wherein:

[0141] S701, obtain the Git repository and determine the repository path;

[0142] S702, obtaining Git commit records within the period;

[0143] S703, obtain the target detailed information of the requirement, obtain the requirement task identifier (requirement ID), submission time, submission number, etc.

[0144] S704. Arrange and summarize, and calculate working hours.

[0145] S705. Output report, that is, output demand management report.

[0146] Exemplarily, steps S701 to S705 may be implemented with reference to the above-mentioned embodiments or a combination of multiple embodiments.

[0147] In this embodiment, the connection between the demand management tool and the Git submission log can be used to automatically generate weekly and monthly work reports, including working hour evaluation, start and end time records, etc., without the need to organize them by yourself, thereby saving time and effort and avoiding errors and omissions.

[0148] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0149] The demand management report generation device provided in the embodiment of the present application is described below. The demand management report generation device and the above-mentioned demand management report generation method have the same inventive concept, and the implementation solution for solving the problem provided by the device is similar to the implementation solution recorded in the above-mentioned method. Therefore, the specific limitations in one or more demand management report generation device embodiments provided below can refer to the limitations on the demand management report generation method in the above text. The demand management report generation device described below and the demand management report generation method described above can be referenced to each other, and will not be repeated here.

[0150] In an exemplary embodiment, Figure 8 A schematic diagram of the structure of a demand management report generating device 80 provided in this application, such as Figure 8 As shown, the device includes: an acquisition module 810, a parsing module 820 and a generation module 803, wherein:

[0151] The acquisition module 810 is used to acquire the storage location information of the code management tool and acquire the information to be queried for the code requirement management; wherein the information to be queried includes the user identification of the user to be queried.

[0152] The parsing module 820 is used to parse and obtain the demand task identifier of the demand management submitted by the user to be queried in the demand management based on the storage location information and the user identifier.

[0153] The generating module 803 is used to generate a demand management report of the user to be queried according to the demand task identifier and the user information of the user to be queried.

[0154] In an exemplary embodiment, the information to be queried also includes the query time. The parsing module includes a query instruction unit and a demand identification unit.

[0155] The query instruction unit is used to determine the query instruction based on the user identification and the query time. The demand identification unit is used to parse and obtain the demand task identification corresponding to the user to be queried according to the storage location information and the query instruction.

[0156] In an exemplary embodiment, the generating module includes a detailed information unit and a report generating unit.

[0157] The detailed information unit is used to obtain the target detailed information of each demand task of the user to be queried according to the demand task identifier and the user information of the user to be queried. The report generation unit is used to generate a demand management report of the user to be queried based on the target detailed information.

[0158] In an exemplary embodiment, the detailed information unit is used to determine the interface status of the requirement management tool; when the interface status indicates that the requirement management tool has an application development interface, the application development interface is called, and the requirement task identifier and the user information of the user to be queried are used to obtain the target detailed information of each requirement task for the user to be queried.

[0159] In an exemplary embodiment, the detailed information unit is also used to obtain an interface for a requirement management list after logging into the requirement management tool based on user information of the user to be queried when the interface status characterizes that the requirement management tool does not have an application development interface; obtain input parameter information and request information for requirement management; call the interface of the requirement management list, and use the input parameter information, request information and requirement task identifier to obtain target detailed information for each requirement task for the user to be queried.

[0160] In an exemplary embodiment, the requirements management report includes the man-hour duration of the requirements.

[0161] The report generation unit is used to determine the cycle duration of the demand management report; obtain the number of submissions corresponding to each demand task identifier and the total number of submissions of multiple demand task identifiers from the target detailed information; based on the cycle duration and the ratio between the number of submissions corresponding to each demand task identifier and the total number of submissions, determine the working hours corresponding to the demand for each demand task identifier.

[0162] In an exemplary embodiment, the acquisition module includes a storage directory unit and a location information unit.

[0163] The storage directory unit obtains the storage directory of the code management tool. The location information unit traverses the directory of the extension information corresponding to the storage path from the storage directory to obtain the storage location information.

[0164] In an exemplary embodiment, the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by one or more processors, the one or more processors execute the steps of the demand management report generation method in any of the above embodiments.

[0165] In one embodiment, the present application further provides a computer device having a computer program stored therein. When the computer program is executed by one or more processors, the one or more processors execute the steps of any of the demand management report generation methods in the above embodiments.

[0166] Indicatively, Fig. 9 As shown, Fig. 9This is a schematic diagram of the internal structure of a computer device provided by the present application. The computer device 900 can be provided as a server. Fig. 9 The computer device 900 includes a processing component 902, which further includes one or more processors, and a memory resource represented by a memory 901, for storing instructions executable by the processing component 902, such as an application. The application stored in the memory 901 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 902 is configured to execute a computer program to perform the method for generating a demand management report of any of the above embodiments.

[0167] The computer device 900 may further include a power supply component 903 configured to perform power management of the computer device 900, a wired or wireless network interface 904 configured to connect the computer device 900 to a network, and an input / output (I / O) interface 905. The computer device 900 may operate based on an operating system stored in the memory 901, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, Free BSD TM, or the like.

[0168] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0169] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply 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 process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0170] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can refer to each other.

[0171] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for generating a demand management report, characterized in that: The method comprises: Acquire storage location information of the code management tool, and acquire information to be queried for code demand management; wherein the information to be queried includes a user identifier of a user to be queried; Based on the storage location information and the user identifier, the requirement task identifier of the requirement management submitted by the to-be-queried user is obtained by parsing; A demand management report for the user to be queried is generated according to the demand task identifier and the user information of the user to be queried.

2. The method according to claim 1, characterized in that The information to be queried also includes the query time; The step of parsing to obtain the demand task identifier of the demand management submitted by the to-be-queried user in the demand management based on the storage location information and the user identifier includes: Determining a query instruction based on the user identifier and the query time; According to the storage location information and the query instruction, the required task identifier corresponding to the user to be queried is obtained by parsing.

3. The method according to claim 1, characterized in that: The step of generating a demand management report for the user to be queried according to the demand task identifier and the user information of the user to be queried includes: Obtaining target detailed information of each demand task of the user to be queried according to the demand task identifier and the user information of the user to be queried; Based on the target detailed information, a demand management report of the user to be queried is generated.

4. The method according to claim 3, characterized in that: The step of obtaining target detailed information of each required task of the user to be queried according to the required task identifier and the user information of the user to be queried includes: Determine the interface status of the requirements management tool; When the interface status indicates that the demand management tool has an application development interface, the application development interface is called, and the target detailed information of each demand task for the user to be queried is obtained by using the demand task identifier and the user information of the user to be queried.

5. The method according to claim 4, characterized in that After determining the interface status of the requirement management tool, the method further includes: In the case where the interface status indicates that the demand management tool does not have an application development interface, based on the user information of the user to be queried, an interface for the demand management list after logging into the demand management tool is obtained; Obtain input parameter information and request information for demand management; The interface of the demand management list is called, and the target detailed information of each demand task for the user to be queried is obtained by using the input parameter information, the request information and the demand task identifier.

6. The method according to claim 3, characterized in that The demand management report includes the required working hours; The generating, based on the target detailed information, a demand management report of the user to be queried includes: Determine the cycle length of the demand management report; Obtaining, from the target detailed information, the number of submissions corresponding to each of the required task identifiers and the total number of submissions of the plurality of required task identifiers; Based on the cycle duration and the ratio between the number of submissions corresponding to each required task identifier and the total number of submissions, the required working hours corresponding to each required task identifier are determined.

7. The method according to any one of claims 1 to 6, characterized in that: The step of obtaining the storage location information of the code management tool includes: Get the storage directory of the code management tool; From the storage directory, traverse the directory of the extension information corresponding to the storage path to obtain the storage location information.

8. A software development demand management report generation device, characterized in that: The device comprises: An acquisition module, used to acquire storage location information of a code management tool and to acquire information to be queried for code demand management; wherein the information to be queried includes a user ID of a user to be queried; A parsing module, configured to parse and obtain, based on the storage location information and the user identifier, a demand task identifier in the demand management submitted by the user to be queried; A generating module is used to generate a demand management report of the user to be queried according to the demand task identifier and the user information of the user to be queried.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images