Work hour management method, device, equipment and medium in research and development and test process

Abstract

The application relates to the field of software research and development demand management, in particular to a work hour management method, device, equipment and medium in the research and development and test process. The method comprises the following steps: acquiring user information of a user currently performing a work hour entry operation, and determining a user role of the user based on the user information; determining a work hour statistical dimension and an entry rule corresponding to the work hour entry time based on the user role; and managing input work hour information based on the work hour statistical dimension and the entry rule. Through the fine entry rule and constraint mechanism of the research and development and test work hour, the application realizes efficient management of the research and development and test work, ensures the accuracy of the managed work hour information, ensures the work hour information entry specification based on the entry rule, thereby improving the subsequent work efficiency and quality, avoiding common errors of manual recording, providing reliable data support for efficiency evaluation and team resource management.

Description

Technical Field

[0001] This application relates to the field of software development requirements management, specifically to methods, devices, equipment, and media for managing work hours during the development and testing process. Background Technology

[0002] With the rapid development of the software development industry and the increasing complexity of projects, the refined management of the development process has become increasingly important. Traditional development management methods often rely on manual recording and statistics, which are not only inefficient but also prone to data omissions or inaccuracies.

[0003] In recent years, with the continuous advancement of project management tools and technologies, more and more companies have begun to introduce digital tools to optimize requirements management processes. However, in current technical solutions, the recording and management of testing and research time information usually relies on the self-discipline of R&D personnel and the simple reminder functions of project management tools. This approach cannot ensure that all requirements can have their time scheduling information recorded in a timely and accurate manner.

[0004] Since the collection of work hours during the demand development and testing process is a key link in improving team efficiency and management level, if this key information, such as research and testing work hours, cannot be recorded in a timely and accurate manner, it will not only make it difficult to carry out team efficiency assessment, but also make it difficult for team leaders to have the necessary data support when managing the team. Summary of the Invention

[0005] In view of this, this application provides a method, device, equipment, and medium for managing working hours during the research and development and testing process, in order to solve the problem that the recording and management methods of working hours information in related technologies cannot record working hour scheduling information in a timely and accurate manner, which leads to difficulties in effectively carrying out team performance evaluation and lack of necessary data support during team management.

[0006] Firstly, this application provides a method for managing work hours during research and development and testing processes, the method comprising: Obtain the user information of the user currently performing the work hour entry operation, and determine the user's role based on the user information; Based on the user role, determine the working hour statistics dimensions and the corresponding entry rules when entering working hours; The input work hour information is managed based on the work hour statistics dimension and the input rules.

[0007] Furthermore, based on the user role, the dimensions for work hour statistics and the corresponding entry rules for work hour entry are determined, including: When the user role is a research and development role, the first requirement information and task information are obtained; Based on the first requirement information and the task information, a first working hour statistics dimension is constructed; Obtain development man-hours, integration testing man-hours, and the first time interval between the task start time and the task end time; The input rules are constructed based on the development time, the integration time, and the first time interval.

[0008] Furthermore, the step of determining the time statistics dimension and the corresponding entry rules based on the user role includes: When the user role is a test role, obtain the second requirement information; Based on the second requirement information, a second working hour statistics dimension is constructed; Obtain the test man-hours and the second time interval between the task start time and the task end time; The input rules are constructed based on the test hours and the second time interval.

[0009] Furthermore, the management of the input work hour information based on the work hour statistics dimension and the input rules includes: The input time information is managed based on the input rules for each of the time statistics dimensions. If the input work hour information does not meet the input rules, the input operation will be intercepted and a prompt message will be output.

[0010] Furthermore, after managing the input time information based on the time statistics dimension and the input rules, the method further includes: When the user receives a task and is currently in the development phase, the entered work hour information is verified to determine whether the work hour information under the task has been successfully entered. If the verification fails, the process will be blocked and the user will be redirected to the work hour entry page.

[0011] Furthermore, after managing the input time information based on the time statistics dimension and the input rules, the method further includes: When entering the testing phase, obtain the target requirements selected by the users; Determine whether the working hour information corresponding to the target requirement has been successfully entered; If the verification fails, the system will be blocked and proceed to the testing phase, redirecting the user to the work hour entry page.

[0012] Furthermore, after managing the input time information based on the time statistics dimension and the input rules, the method further includes: Based on the user role, obtain the key information and visualization format corresponding to the working hour information; The key information is displayed based on the aforementioned visual presentation format.

[0013] Secondly, this application provides a time management device for the research and development and testing process, the device comprising: The first acquisition module is used to acquire user information of the user currently performing the work hour entry operation, and determine the user role of the user based on the user information; The first determining module is used to determine the working hour statistics dimension and the corresponding entry rules for working hour entry based on the user role; The management module is used to manage the input working hour information based on the working hour statistics dimension and the input rules.

[0014] Thirdly, this application provides a computer device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to perform the time management method for the research and development and testing process described in the first aspect or any corresponding embodiment.

[0015] Fourthly, this application provides a computer-readable storage medium storing computer instructions for causing a computer to execute the time management method for the research and development and testing process described in the first aspect or any corresponding embodiment.

[0016] In this embodiment, the user role of the user currently performing the work hour entry operation is determined. Based on the user role, the work hour statistics dimension and the corresponding entry rules are determined. Then, the input work hour information is managed based on the work hour statistics dimension and the entry rules. Thus, this application achieves efficient management of R&D and testing work through refined entry rules and constraints, ensuring the accuracy of managed work hour information. Simultaneously, the entry rules ensure standardized entry of work hour information, thereby improving subsequent work efficiency and quality, avoiding common errors in manual recording, and providing reliable data support for performance evaluation and team resource management. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1This is a flowchart illustrating a method for managing work hours during the research and development and testing process according to an embodiment of this application; Figure 2 This is a schematic diagram of the interface for the R&D input rules according to an embodiment of this application; Figure 3 This is a schematic diagram of the interface for the test entry rules according to an embodiment of this application; Figure 4 This is a diagram of a prompt interface indicating that the working hour information does not conform to the entry rules according to an embodiment of this application; Figure 5 This is a screenshot of the prompt interface for creating a new test plan according to an embodiment of this application; Figure 6 This is an interface diagram showing the R&D man-hour information according to an embodiment of this application; Figure 7 This is an interface diagram showing test time information according to an embodiment of this application; Figure 8 This is a schematic diagram of the overall process of time management in the research and development and testing process according to an embodiment of this application; Figure 9 This is a block diagram of a time management device for the research and development and testing process according to an embodiment of this application; Figure 10 This is a schematic diagram of the hardware structure of a computer device according to an embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0021] In the field of software development requirements management, the collection of work hours during the requirements development and testing process is a crucial step in improving team efficiency and management. In relevant technical solutions, the recording and management of development and testing work hours typically rely on the self-discipline of developers and simple reminder functions of project management tools. However, this model has significant limitations. First, developers and testers are prone to neglecting timely recording of work hours amidst their busy work schedules, leading to compromised data integrity. Second, the lack of standardized constraints makes it difficult to verify the accuracy of work hour information, resulting in estimation errors or recording mistakes. Furthermore, the management of development and testing schedules in relevant technical solutions is relatively loose, failing to ensure that all requirements are recorded with timely and accurate work hour schedules, thus failing to provide reliable data support for subsequent performance evaluation and team resource management.

[0022] Based on this, according to the embodiments of this application, an embodiment of a method for managing working hours during the research and development and testing process is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0023] This embodiment provides a method for managing work hours during the research and development and testing process, such as... Figure 1 As shown, Figure 1 This is a flowchart illustrating a method for managing work hours during the research and development and testing process according to an embodiment of this application. This method can be applied to the system side of work hour management, and the process includes the following steps: Step S101: Obtain the user information of the user currently performing the work hour entry operation, and determine the user's user role based on the user information.

[0024] Optionally, a time management system can be set up. This system first captures the identity information of the user who initiates the time entry operation. The core acquisition dimensions include: basic identity identifier: user name, team (such as team A, team B, test team, etc.), and unique account ID (implied in the system operation permission verification). The entry points for user-initiated operations (such as the "Claim R&D Task" entry point and the "Create Test Plan" entry point), and the associated work objects (such as specific R&D tasks and specific test requirements).

[0025] By integrating the above information, the system can accurately locate the user subject performing the work hour entry operation and determine the user role, such as: R&D role, testing role.

[0026] Step S102: Based on user roles, determine the working hour statistics dimensions and the corresponding entry rules for working hour entry.

[0027] Optionally, corresponding time statistics dimensions and entry rules can be set for different user roles. Here, dedicated statistical dimensions are designed to address the differences in work scenarios between R&D and testing, ensuring that time records deeply align with actual workflows. This avoids scheduling chaos caused by single-dimensional statistics and ensures that all required time scheduling information is traceable and controllable. The significance of setting entry rules lies in the fact that traditional time management relies on employee self-discipline, which commonly suffers from data gaps, recording errors, and estimation biases. Setting entry rules, however, avoids these problems at the source through constraint settings.

[0028] Step S103: Manage the input working hour information based on working hour statistics dimensions and input rules.

[0029] Optionally, the system manages the input time information based on the input rules from the perspective of time statistics, and verifies in real time whether the input data conforms to the rules; if the verification fails, the system immediately intercepts the operation and gives clear modification prompts (such as "the R&D time for the corresponding task has not been set" or "the test time must not be 0"), guiding the user to correct according to the input rules.

[0030] In this embodiment, the user role of the user currently performing the work hour entry operation is determined. Based on the user role, the work hour statistics dimensions and corresponding entry rules are determined. Then, the input work hour information is managed based on the work hour statistics dimensions and entry rules. Thus, this application achieves efficient management of R&D and testing work through refined entry rules and constraints, ensuring the accuracy of managed work hour information. Simultaneously, the entry rules ensure standardized entry of work hour information, thereby improving subsequent work efficiency and quality, avoiding common errors in manual recording, and providing reliable data support for performance evaluation and team resource management.

[0031] As an optional implementation, based on user roles, the dimensions for work hour statistics and the corresponding entry rules for work hour entry are determined, including: When the user role is a research and development role, obtain the primary requirement information and task information; Based on the primary demand information and task information, construct the primary working hour statistics dimension; Obtain development man-hours, integration testing man-hours, and the first time interval between the task start time and the task end time; Input rules are constructed based on development time, integration testing time, and the first time interval.

[0032] Optionally, when the user role is a research and development role, the statistical dimensions and entry rules corresponding to the research and development role are specified.

[0033] The first dimension for work hour statistics is "requirement-task". This means that specific requirements are first associated, and then the individual R&D tasks under those requirements are focused on. The statistical dimension is accurate to "the team to which the task belongs + the person who performs the task + the specific task item". It supports the integration and display of data by task dimension.

[0034] Work hour entry rules: Unit of measurement: The smallest unit for development man-hours and commissioning man-hours is 0.5 man-days; Numerical constraints: Development time and integration time can be 0 individually, but their sum must not be 0; Time Constraint: The total working hours entered must strictly fall within the first time interval between the start and end times of the R&D task. The start and end times of the R&D task can be flexibly set, or they can be pre-set and cannot be changed.

[0035] See Figure 2 The interface diagram shown is as follows. Figure 2 Multiple tasks are pre-built according to requirements and are available for users to select from via drop-down menus. The settings for development time, integration time, start time and end time must be entered according to the development time entry rules.

[0036] In this embodiment, role-based differentiated management meets the work needs of different roles, improving the targeting and effectiveness of work hour management. A standardized constraint mechanism ensures timely and accurate recording of required work hour scheduling information, laying a solid data foundation for team collaboration and management, and helping to improve team collaboration and management levels. Simultaneously, multi-dimensional work hour statistics provide detailed and accurate data for project management, helping managers accurately grasp project progress and resource allocation.

[0037] As an optional implementation, based on user roles, the dimensions for work hour statistics and the corresponding entry rules for work hour entry are determined, including: When the user role is a test role, obtain the second requirement information; Based on the second demand information, a second dimension for work hour statistics is constructed; Obtain the test man-hours and the second time interval between the task start time and the task end time; Based on the test duration and the second time interval, input rules are constructed.

[0038] Optionally, when the user role is a test role, the statistical dimensions and entry rules corresponding to the test role are specified.

[0039] The second dimension of work time statistics: The statistics adopt the first-level dimension of "requirement". The work time data is summarized by the test team to which the specific second requirement information (i.e. test requirements) is located. The statistical dimension focuses on "requirement + test team + test personnel" and supports the integration and display of data by team dimension.

[0040] Work hour entry rules: Unit of measurement: The smallest unit of testing man-hours is 0.5 man-days; Numerical constraint: Test time must not be 0 (must meet the requirement of being "greater than 0 and a multiple of 0.5"); Time Constraints: The duration of the entered test work hours must strictly fall within the second time interval between the start and end times of the test requirement. The start and end times of the test task can be flexibly set, or they can be pre-set and cannot be changed.

[0041] See Figure 3 The interface diagram shown is as follows. Figure 3 Multiple test teams can be pre-set according to requirements, and users can select their current team information through a drop-down menu. The test hours, start time and end time settings must be entered according to the test hour entry rules.

[0042] In this embodiment, role-based differentiated management meets the work needs of different roles, improving the targeting and effectiveness of work hour management. A standardized constraint mechanism ensures timely and accurate recording of required work hour scheduling information, laying a solid data foundation for team collaboration and management, and helping to improve team collaboration and management levels. Simultaneously, multi-dimensional work hour statistics provide detailed and accurate data for project management, helping managers accurately grasp project progress and resource allocation.

[0043] As an optional implementation, the input time information is managed based on time statistics dimensions and input rules, including: The system manages the input time information for each time statistics dimension based on the input rules. If the entered work hour information does not meet the entry rules, the entry operation will be intercepted and a prompt message will be output.

[0044] Optionally, when a user enters working hours into the system, statistics are performed for each working hour statistical dimension, and the entered data needs to be verified in real time to see if it conforms to the entry rules (such as whether the total R&D working hours are 0, whether the testing working hours are 0, whether the unit of measurement is an integer multiple of 0.5 person-days, and whether the time range exceeds the task / requirement cycle). If the verification fails, the system immediately blocks the operation and provides a clear prompt (such as "The corresponding task's development hours have not been set" or "Test hours cannot be 0"), guiding the user to correct the input according to the rules. See also Figure 4 The prompt interface shown.

[0045] As an optional embodiment, after managing the input work hour information based on work hour statistics dimensions and input rules, the method further includes: When a user receives a task and enters the development phase, the entered work hour information is verified to determine whether the work hour information under the task has been successfully entered. If the verification fails, the process will be blocked and the user will be redirected to the work hour entry page.

[0046] Optionally, when developers accept a task and prepare to enter the development phase, the system will automatically verify the current task's work hours. This verifies whether the user has entered work hour information that conforms to the entry rules. If the verification fails, the system will intercept the entry, redirecting the developer to the work hour entry page and prompting them to enter the work hours. Only after completing the development work hour entry according to the established rules can developers officially begin development work, thus ensuring the completeness and accuracy of the work hour records.

[0047] This application's embodiments utilize digital tools and standardized constraints to automate and standardize time management, significantly reducing management costs and improving management efficiency.

[0048] As an optional embodiment, after managing the input work hour information based on work hour statistics dimensions and entry rules, the method further includes: When entering the testing phase, obtain the target requirements selected by the users; Confirm whether the work hour information corresponding to the target requirement has been successfully entered; If the verification fails, the system will be blocked and proceed to the testing phase, redirecting the user to the work hour entry page.

[0049] Optionally, before entering the testing phase, testers must first create a test plan and associate it with relevant requirements. When a target requirement is selected, the system will automatically validate the test man-hours for that target requirement to ensure the user has entered man-hour information that conforms to the entry rules. If the validation fails, the system will intercept the request, redirecting the tester to the man-hour entry page and prompting them to enter the test man-hours. Only after completing the test man-hour entry according to the established rules can the tester continue with subsequent testing work. See also Figure 5 .

[0050] This application's embodiments utilize digital tools and standardized constraints to automate and standardize time management, significantly reducing management costs and improving management efficiency.

[0051] As an optional embodiment, after managing the input work hour information based on work hour statistics dimensions and entry rules, the method further includes: Based on the user's role, obtain key information and visual display format corresponding to the work hour information; Key information is presented using a visual display format.

[0052] Optionally, the entered R&D work hour data will be presented in list format, covering key information such as task name, team, executor, development hours, integration testing hours, start time, end time, status, work item, and operations. Data will be integrated according to task dimensions, and related information for the same task will be merged into single cells for optimized display. Furthermore, the list supports in-line editing and deletion, allowing users to flexibly adjust and manage data. See also Figure 6 .

[0053] The entered test time data will be presented in a list format by team, covering key information such as team affiliation, personnel name, test time, status, start time, end time, work item, and operation. Furthermore, this list supports in-line editing and deletion, and also provides the ability to add data under a team, allowing users to flexibly manage and maintain test time records. See also Figure 7 .

[0054] This application's embodiments enhance the convenience and flexibility of time management through flexible data display and operation methods, thereby further improving project management efficiency.

[0055] like Figure 8 As shown, Figure 8 This is a schematic diagram of the overall process of time management in the research and development and testing process according to an embodiment of this application. The specific process is as follows: Obtain demand information; For R&D users, development hours and integration testing hours are entered based on the requirements information. When a R&D user claims a task, it is determined whether the current task has already been entered with development hours. If it has been entered, the task is successfully claimed and development can begin; otherwise, the development hours and integration testing hours need to be entered again.

[0056] For test users, test hours are entered based on the requirements information. When preparing to conduct testing and creating a test plan, it is determined whether test hours have been entered for the current requirements. If they have, the test plan is created successfully; otherwise, test hours need to be entered again.

[0057] After development is complete and the test plan is completed and passed the tests, the system is deployed and launched.

[0058] This embodiment provides a time management device for the research and development and testing process, such as... Figure 9 As shown, it includes: The first acquisition module 901 is used to acquire user information of the user currently performing the work hour entry operation, and determine the user's user role based on the user information; The first determining module 902 is used to determine the working hour statistics dimension and the corresponding entry rules for working hour entry based on the user role; The management module 903 is used to manage the input work hour information based on work hour statistics dimensions and input rules.

[0059] In this embodiment, the user role of the user currently performing the work hour entry operation is determined. Based on the user role, the work hour statistics dimensions and corresponding entry rules are determined. Then, the input work hour information is managed based on the work hour statistics dimensions and entry rules. Thus, this application achieves efficient management of R&D and testing work through refined entry rules and constraints, ensuring the accuracy of managed work hour information. Simultaneously, the entry rules ensure standardized entry of work hour information, thereby improving subsequent work efficiency and quality, avoiding common errors in manual recording, and providing reliable data support for performance evaluation and team resource management.

[0060] In some optional implementations, the first determining module 902 is used to obtain first requirement information and task information when the user role is a research and development role; construct a first working hour statistics dimension based on the first requirement information and task information; obtain development working hours, integration testing working hours, and a first time interval between the task start time and the task end time; and construct input rules based on the development working hours, integration testing working hours, and the first time interval.

[0061] In some optional implementations, the first determining module 902 is used to obtain second requirement information when the user role is a test role; construct a second working time statistics dimension based on the second requirement information; obtain the test working time and a second time interval between the task start time and the task end time; and construct input rules based on the test working time and the second time interval.

[0062] In some optional implementations, the management module 903 is used to manage the input time information under each time statistics dimension based on the input rules; if the input time information does not meet the input rules, the input operation is intercepted and a prompt message is output.

[0063] In some alternative embodiments, the device further includes: The first verification module is used to manage the input time information based on the time statistics dimension and the input rules, and to verify the entered time information when the user receives the task and is currently in the development stage, and to determine whether the time information under the task has been successfully entered. The first redirect module is used to intercept the process if the verification fails, and redirect the user to the work hour entry page.

[0064] In some alternative embodiments, the device further includes: The second acquisition module is used to acquire the target requirements selected by the user when entering the testing phase, after managing the input time information based on the time statistics dimension and input rules. The second determination module is used to determine whether the working hour information corresponding to the target requirement has been successfully entered. The second redirect module is used to intercept the process if the verification fails, and then redirect the user to the work hour entry page.

[0065] In some alternative embodiments, the device further includes: The third acquisition module is used to acquire key information and visualization format corresponding to the work time information based on the user role after managing the input work time information based on the work time statistics dimension and input rules. The presentation module is used to display key information in a visual format.

[0066] In this embodiment, the time management device for the research and development and testing process is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit), a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0067] This application also provides a computer device having the above-described features. Figure 9 The device shown is for managing work hours during the research and development and testing process.

[0068] Please see Figure 10 , Figure 10 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of this application, such as... Figure 10 As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 10 Take a processor 10 as an example.

[0069] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0070] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0071] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0072] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0073] The computer device also includes a communication interface 30 for communicating with other devices or communication networks.

[0074] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0075] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for managing work hours during research and development and testing processes, characterized in that, The method includes: Obtain the user information of the user currently performing the work hour entry operation, and determine the user's role based on the user information; Based on the user role, determine the working hour statistics dimensions and the corresponding entry rules when entering working hours; The input work hour information is managed based on the work hour statistics dimension and the input rules.

2. The method according to claim 1, characterized in that, The process of determining the statistical dimensions of working hours and the corresponding entry rules based on the user role includes: When the user role is a research and development role, the first requirement information and task information are obtained; Based on the first requirement information and the task information, a first working hour statistics dimension is constructed; Obtain development man-hours, integration testing man-hours, and the first time interval between the task start time and the task end time; The input rules are constructed based on the development time, the integration time, and the first time interval.

3. The method according to claim 1, characterized in that, The process of determining the statistical dimensions of working hours and the corresponding entry rules based on the user role includes: When the user role is a test role, obtain the second requirement information; Based on the second requirement information, a second working hour statistics dimension is constructed; Obtain the test man-hours and the second time interval between the task start time and the task end time; The input rules are constructed based on the test hours and the second time interval.

4. The method according to claim 2 or 3, characterized in that, The management of input time information based on the time statistics dimension and the input rules includes: The input time information is managed based on the input rules for each of the time statistics dimensions. If the input work hour information does not meet the input rules, the input operation will be intercepted and a prompt message will be output.

5. The method according to claim 2, characterized in that, After managing the input time information based on the time statistics dimension and the input rules, the method further includes: When the user receives a task and is currently in the development phase, the entered work hour information is verified to determine whether the work hour information under the task has been successfully entered. If the verification fails, the process will be blocked and the user will be redirected to the work hour entry page.

6. The method according to claim 3, characterized in that, After managing the input time information based on the time statistics dimension and the input rules, the method further includes: When entering the testing phase, obtain the target requirements selected by the users; Determine whether the working hour information corresponding to the target requirement has been successfully entered; If the verification fails, the system will be blocked and proceed to the testing phase, redirecting the user to the work hour entry page.

7. The method according to any one of claims 1 to 3, characterized in that, After managing the input time information based on the time statistics dimension and the input rules, the method further includes: Based on the user role, obtain the key information and visualization format corresponding to the working hour information; The key information is displayed based on the aforementioned visual presentation format.

8. A time management device for research and development and testing processes, characterized in that, The device includes: The first acquisition module is used to acquire user information of the user currently performing the work hour entry operation, and determine the user role of the user based on the user information; The first determining module is used to determine the working hour statistics dimension and the corresponding entry rules for working hour entry based on the user role; The management module is used to manage the input working hour information based on the working hour statistics dimension and the input rules.

9. A computer device, characterized in that, include: A memory and a processor are interconnected, the memory storing computer instructions, and the processor executing the computer instructions to perform the time management method for the research and development and testing process as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the time management method for the research and development and testing process as described in any one of claims 1 to 7.

Images