A management system for R&D projects
By obtaining the actual cycle and measurement data of the R&D project, determining the project complexity and setting the planning cycle, the problem of relying on subjective factors in the existing technology to set the planned delivery time is solved, and the accuracy of the execution effect data of the R&D project is improved.
Patent Information
- Application Number
- CN202210131966.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-02-14
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2042-02-14
AI Technical Summary
In the prior art, the planned delivery time of R&D projects mainly depends on the experience settings of the person in charge, and the lack of personalized adaptation leads to inaccurate final evaluation results.
The actual R&D cycle and project measurement data are obtained through the project information data acquisition module, the project complexity is determined, and the planned R&D cycle is set based on the complexity, and then the execution effect data is evaluated.
It improves the adaptability of the planned R&D cycle and R&D projects, enhances the accuracy of execution effect data, and provides reliable data support for subsequent management and adjustments.
Smart Images

Figure CN114493544B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data processing, and in particular to a management system for research and development projects. Background Art
[0002] With the continuous emergence of product innovations in my country's financial industry and the rapid development of financial information technology, improving the efficiency of software product development and promoting rapid project delivery are important means to enhance the competitiveness of commercial banks. How to establish an effective measurement, evaluation and management system for project time indicators is the key to the success of technology enterprise projects.
[0003] At present, enterprises mainly use the overall actual delivery time and the overall planned delivery time of R&D projects as monitoring and assessment indicators. However, the overall planned delivery time is mainly set according to the experience or expectations of the person in charge, and cannot be well personalized to the R&D projects, resulting in inaccurate final evaluation results of the project. Summary of the invention
[0004] The present invention provides a management system for R&D projects to solve the problem of setting a planned R&D cycle based on subjective factors, improve the adaptability of the planned R&D cycle and the R&D projects, and further improve the accuracy of the execution effect data of the determined R&D projects.
[0005] According to one aspect of the present invention, a management system for R&D projects is provided, the system comprising:
[0006] A project information data acquisition module, used to acquire the actual R&D cycle of the R&D project and at least one project measurement data; wherein the project measurement data is used to characterize the parameter value of the quantifiable indicator of the R&D project;
[0007] A project complexity determination module, used to determine the project complexity corresponding to the R&D project based on at least one project measurement data;
[0008] A planned R&D cycle determination module, used to determine the planned R&D cycle corresponding to the R&D project based on the complexity of the project;
[0009] The execution effect data determination module is used to determine the execution effect data of the R&D project based on the actual R&D cycle and the planned R&D cycle.
[0010] According to another aspect of the present invention, a method for managing a research and development project is provided, the method comprising:
[0011] Acquire an actual R&D cycle of the R&D project and at least one project measurement data; wherein the project measurement data is used to characterize parameter values of quantifiable indicators of the R&D project;
[0012] Determining a project complexity corresponding to the R&D project based on at least one project metric data;
[0013] Based on the complexity of the project, determine the planned R&D cycle corresponding to the R&D project;
[0014] Based on the actual R&D cycle and the planned R&D cycle, the execution effect data of the R&D project is determined.
[0015] According to another aspect of the present invention, there is provided an electronic device, the electronic device comprising:
[0016] at least one processor; and
[0017] a memory communicatively connected to the at least one processor; wherein,
[0018] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the management method of the R&D project described in any embodiment of the present invention.
[0019] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the management method of a research and development project described in any embodiment of the present invention when executed.
[0020] The technical solution of the embodiment of the present invention determines the project complexity corresponding to the R&D project based on project measurement data, determines the planned R&D cycle of the R&D project based on the project complexity, and determines the execution effect data of the R&D project based on the actual R&D cycle and the planned R&D cycle of the R&D project. This solves the problem of setting the planned R&D cycle based on subjective factors, improves the adaptability of the planned R&D cycle to the R&D project, and further improves the accuracy of the execution effect data of the R&D project, providing reliable data support for the subsequent management and adjustment of the R&D project.
[0021] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0023] Figure 1 is a schematic diagram of a management system for a research and development project provided according to Embodiment 1 of the present invention;
[0024] Figure 2 is a schematic diagram of a management system for R&D projects provided according to Embodiment 2 of the present invention;
[0025] Figure 3 is a flow chart of a method for managing a research and development project provided according to Embodiment 3 of the present invention;
[0026] Figure 4 is a flowchart of a specific example of a management method for a research and development project provided in Embodiment 3 of the present invention;
[0027] Figure 5 It is a structural schematic diagram of an electronic device provided according to Embodiment 4 of the present invention. DETAILED DESCRIPTION
[0028] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.
[0029] It should be noted that the terms "including" and "having" and any variations thereof in the specification and claims of the present invention and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or apparatus.
[0030] Embodiment 1
[0031] Figure 1 is a schematic diagram of a management system for a research and development project provided according to the first embodiment of the present invention. This embodiment is applicable to the situation of managing and evaluating the life cycle of a research and development project, and the management system for the research and development project can be configured in a terminal device. Figure 1 As shown, the management system includes:
[0032] The project information data acquisition module 110 is used to acquire the actual R&D cycle of the R&D project and at least one project measurement data; wherein the project measurement data is used to characterize the parameter value of the quantifiable indicator of the R&D project;
[0033] A project complexity determination module 120, configured to determine a project complexity corresponding to a research and development project based on at least one project metric data;
[0034] A planned R&D cycle determination module 130 is used to determine a planned R&D cycle corresponding to the R&D project based on the project complexity;
[0035] The execution effect data determination module 140 is used to determine the execution effect data of the R&D project based on the actual R&D cycle and the planned R&D cycle.
[0036] Research and development is usually referred to as R&D, which includes all scientific research and technological development work. Research aims to explore the unknown, while development is to create a specific material form from potential or basic factors, such as new products, new theories, new processes, new materials or new technologies, etc. R&D projects can be used to describe the above research and development activities.
[0037] In one embodiment, the actual R&D cycle can be used to represent the time from the project establishment time node to the preset time node of the R&D project. The preset time node can be the current time node for obtaining the actual R&D cycle of the R&D project, or the completion time node of the R&D project, or any time node in the execution process of the R&D project, such as the first delivery time node.
[0038] In one embodiment, optionally, the project complexity includes at least one of business complexity, technical complexity, management complexity and comprehensive complexity. Accordingly, the project measurement data corresponding to the business complexity include at least one of the number of project requirement items, the number of project requirement issuance batches and the number of requirement changes. The project measurement data corresponding to the technical complexity include at least one of the project technical review level, the network security level protection level, the number of newly added interface consumption relationships and the total number of newly added computing resources. The project measurement data corresponding to the management complexity include at least one of the project workload, project plan change data and the number of project co-sponsoring departments.
[0039] This embodiment constructs a project complexity model according to the category dimension of project information, wherein the categories of project information include business, technology and management. Accordingly, project complexity includes at least one of business complexity, technology complexity, management complexity and comprehensive complexity.
[0040] Furthermore, in another embodiment, the project complexity model is optionally further divided according to the timeliness dimension of project information, wherein the timeliness of project information includes static and dynamic. Accordingly, the project complexity includes seven categories: business static complexity, business dynamic complexity, technical static complexity, technical dynamic complexity, management static complexity, management dynamic complexity and comprehensive complexity.
[0041] Table 1 is a mapping list between project complexity and project measurement data provided according to the first embodiment of the present invention.
[0042]
[0043] Specifically, the project plan change data includes the number of project plan changes and the extent of project plan changes.
[0044] Specifically, there is a positive correlation between project complexity and project measurement data. For example, the greater the project workload, the higher the management static complexity. The specific functional relationship corresponding to the positive correlation is not limited here. For example, the functional relationship can be a linear function or an exponential function, etc., and the user can set it according to actual needs.
[0045] Among them, illustratively, if the project measurement data only includes the number of project requirement items, the project complexity is the static complexity of the business; if the project measurement data only includes the project plan change data and the number of project co-sponsoring departments, the project complexity is the dynamic complexity of management.
[0046] In one embodiment, optionally, the project complexity determination module 110 is specifically used to: determine the business complexity of the R&D project based on at least one of the number of project requirement items, the number of project requirement issuance batches, and the number of project requirement changes; determine the technical complexity of the R&D project based on the project technical review level, the network security level protection level, the number of newly added interface consumption relationships, and the total number of newly added computing resources; determine the management complexity of the R&D project based on the project workload, project plan change data, and the number of project co-sponsoring departments; determine the comprehensive complexity of the R&D project based on the business complexity, technical complexity, and management complexity.
[0047] Among them, the comprehensive complexity S satisfies the formula:
[0048]
[0049] Among them, S A Indicates the business complexity, S B Indicates the technical complexity, S C represents the management complexity, n1, n2 and n3 represent the number of project measurement data corresponding to business complexity, technical complexity and management complexity respectively, A i , B i and C i Respectively represent the metric data of the i-th project corresponding to business complexity, technical complexity and management complexity, W Ai , W Bi and W Ci They respectively represent the measurement weights corresponding to the metric data of the i-th project corresponding to business complexity, technical complexity and management complexity.
[0050] It should be noted that, in this embodiment, the project complexity is business complexity, technical complexity, management complexity or comprehensive complexity, that is, the number of project complexity determined in this embodiment is 1.
[0051] In one embodiment, optionally, the planned R&D cycle determination module 130 is specifically used to: determine the classification level to which the R&D project belongs based on the project complexity, and determine the planned R&D cycle corresponding to the classification level based on the cycle mapping list; wherein the cycle mapping list contains at least one classification level and the planned R&D cycle corresponding to each classification level.
[0052] Specifically, the level mapping list is searched to determine the classification level corresponding to the project complexity. The level mapping list includes at least one classification level and the complexity intervals corresponding to each classification level. Exemplarily, the complexity interval corresponding to the first classification level is [0,100], and the complexity interval corresponding to the second classification level is [150,300]. The level mapping list is not limited here.
[0053] For example, in the cycle mapping list, the planned development cycle corresponding to the first classification level is 10 days, and the planned development cycle corresponding to the second classification level is 20 days. The cycle mapping list is not limited here.
[0054] In one embodiment, optionally, the planned development cycle is preset by a user.
[0055] In another embodiment, optionally, the management system also includes: a cycle mapping list determination module, which is used to obtain the project complexity and actual R&D cycle corresponding to at least two completed projects respectively based on the collection time node; add at least two classification levels determined based on the complexity of at least two projects to the cycle mapping list; for each classification level, add the planned R&D cycle determined based on the actual R&D cycle of at least one completed project corresponding to the classification level to the cycle mapping list.
[0056] Exemplarily, the collection time node may be the beginning of each month, the end of each month, each quarter or each year, etc.
[0057] Specifically, at least two classification levels are determined based on at least two project complexities. Assume that the completed projects include Project A, Project B, Project C, and Project D, and the project complexities corresponding to the completed projects are 100, 200, 350, and 500, respectively. In one embodiment, if the classification level includes a first classification level, a second classification level, a third classification level, and a fourth classification level, that is, each classification level corresponds to a completed project, then for each classification level, the actual R&D cycle of the completed project corresponding to the classification level is the planned R&D cycle corresponding to the classification level. In another embodiment, if the classification level includes a first classification level and a second classification level, illustratively, the first classification level corresponds to Project A and Project B, and the second classification level corresponds to Project C and Project D. Of course, the first classification level can also correspond to Project A, Project B, and Project C, and the second classification level corresponds to Project D. For each classification level, the maximum value, minimum value, median value, or average value of the actual R&D cycle of at least one completed project corresponding to the classification level is used as the planned R&D cycle corresponding to the classification level.
[0058] Specifically, the classification level can be determined based on the preset level range and the project complexity. The preset level range can be used to ensure the span of the project complexity corresponding to each classification level. Taking the above example, assuming that the preset level range is 100, the number of classification levels is 5, that is, the complexity ranges corresponding to the classification levels are [0,100], (100,200], (200,300], (300,400] and (400,500]. Assuming that the preset level range is 200, the number of classification levels is 3, that is, the complexity ranges corresponding to the classification levels are [0,200], (200,400] and (400,600].
[0059] The advantage of this setting is that different cycle mapping lists can be determined at different collection time nodes, so that the cycle mapping lists change dynamically with the collection time nodes, thereby realizing dynamic changes in the planned R&D cycles of different R&D projects at different collection time nodes, further improving the adaptability of the planned R&D cycle to the R&D projects and the accuracy of the execution effect data of the R&D projects.
[0060] Specifically, the execution effect data of the R&D project is determined according to the cycle difference between the actual R&D cycle and the planned R&D cycle. The execution effect data may be scoring data or effect level. In one embodiment, if the execution effect data is scoring data, the execution effect data is calculated by the functional relationship between the cycle difference and the execution effect data. In another embodiment, if the execution effect data is the effect level, the execution effect data is determined by an effect mapping list. The effect mapping list includes at least one cycle difference range and an effect level corresponding to each cycle difference range. Specifically, the larger the cycle difference, the higher the effect level, and the smaller the cycle difference, the lower the effect level.
[0061] The technical solution of this embodiment determines the project complexity corresponding to the R&D project based on the project measurement data, determines the planned R&D cycle of the R&D project based on the project complexity, and determines the execution effect data of the R&D project based on the actual R&D cycle and the planned R&D cycle of the R&D project. This solves the problem of setting the planned R&D cycle based on subjective factors, improves the adaptability of the planned R&D cycle to the R&D project, and further improves the accuracy of the execution effect data of the R&D project, providing reliable data support for the subsequent management and adjustment of the R&D project.
[0062] Embodiment 2
[0063] Figure 2 Schematic diagram of a management system for R&D projects provided according to Embodiment 2 of the present invention. This embodiment further refines the "actual R&D cycle" and "project measurement data". Specifically, the actual R&D cycle includes the actual R&D cycle corresponding to at least one target cycle indicator, and the project measurement data includes the project measurement data corresponding to at least one target cycle indicator. Figure 2 As shown, the management system includes:
[0064] The periodic indicator library management module 210 is used to store an indicator mapping list, wherein the indicator mapping list includes at least one R&D mode and at least one periodic indicator corresponding to each R&D mode;
[0065] The target cycle indicator determination module 220 is used to obtain the R&D mode of the R&D project and determine at least one target cycle indicator corresponding to the R&D project based on the indicator mapping list of the R&D mode;
[0066] The project information data acquisition module 230 is used to obtain the actual R&D cycle corresponding to at least one target cycle indicator of the R&D project and at least one project measurement data.
[0067] A project complexity determination module 240, for determining, for each target cycle indicator, a project complexity corresponding to the target cycle indicator based on at least one project measurement data corresponding to the target cycle indicator;
[0068] A planned development cycle module 250 is used to determine a planned development cycle corresponding to the target cycle indicator based on the project complexity corresponding to the target cycle indicator;
[0069] The execution effect data determination module 260 is used to determine the execution effect data corresponding to the target cycle indicator based on the actual R&D cycle and the planned R&D cycle corresponding to the target cycle indicator.
[0070] In one embodiment, optionally, in the indicator mapping list, the cycle indicators corresponding to the waterfall R&D model include at least one of the overall cycle indicators, demand development cycle indicators, design cycle indicators, development cycle indicators, testing cycle indicators and production cycle indicators, and the cycle indicators corresponding to the iterative R&D model or the agile R&D model include the overall cycle indicators and / or iterative cycle indicators.
[0071] Among them, the target cycle indicator determination module 210 is specifically used to: when the R&D mode is the waterfall R&D mode, obtain the R&D stage identifier of the R&D project, and determine at least one target cycle indicator corresponding to the R&D project based on the indicator mapping list, the R&D mode and the R&D stage identifier. Among them, the R&D stage identifier can be used to characterize the R&D stage of the R&D project. For example, assuming that the R&D stage identifier of the R&D project is "development stage", the target cycle indicator corresponding to the R&D project includes the overall cycle indicator and / or the development cycle indicator, and the R&D stage identifier of the R&D project is "testing stage", then the target cycle indicator corresponding to the R&D project includes the overall cycle indicator and / or the testing cycle indicator.
[0072] Among them, the project information data acquisition module 230 is specifically used to: obtain the actual R&D cycle corresponding to at least one target cycle indicator of the R&D project, and for each target cycle indicator, based on the metric mapping list, obtain at least one project metric data corresponding to the target cycle indicator; wherein the metric mapping list contains at least one cycle indicator and at least one project metric data corresponding to each cycle indicator.
[0073] Specifically, the actual R&D cycle corresponding to the target cycle indicator can be used to represent the time used by the R&D project in the R&D stage corresponding to the target cycle indicator.
[0074] In one embodiment, optionally, in the metric mapping list, the project metric data corresponding to the overall cycle indicators or the iteration cycle indicators include the number of project requirement items, the number of project requirement issuance batches and the number of project requirement changes, the project technical review level, the network security level protection level, the number of newly added interface consumption relationships and the total number of newly added computing resources, the project workload, the project plan change data and the number of project co-sponsoring departments; the project metric data corresponding to the demand development cycle include the number of project requirement items, the number of project requirement issuance batches and the number of project requirement changes; the project metric data corresponding to the design cycle indicators include the project technical review level; the project metric data corresponding to the development cycle indicators or the testing cycle indicators include the project technical review level, the network security level protection level, the number of newly added interface consumption relationships and the total number of newly added computing resources; the project metric data corresponding to the production cycle indicators include the project workload, the project plan change data and the number of project co-sponsoring departments.
[0075] The above embodiment only provides a setting method of the metric mapping list, but does not limit it. The user can perform personalized settings according to actual needs.
[0076] On the basis of the above embodiment, optionally, the management system also includes: an early warning module, which is used to determine the cycle difference for each target cycle indicator based on the actual R&D cycle and the planned R&D cycle corresponding to the target cycle indicator when the project type of the R&D project belongs to an ongoing project; if the cycle difference is less than a preset difference threshold, a early warning operation is performed based on the target cycle indicator.
[0077] Among them, exemplary, cycle difference = planned R&D cycle - actual R&D cycle. For example, assuming that the R&D model of the R&D project is a waterfall R&D model, the target cycle indicator includes the development cycle indicator, indicating that the R&D project is in the development stage at this time. If the cycle difference is less than the preset difference threshold and is positive, it means that the development task of the R&D project is about to expire. If the cycle difference is less than the preset difference threshold and is negative, it means that the development task of the R&D project has expired.
[0078] Exemplarily, the warning operation may be at least one of a text prompt, a text message notification, an indicator light prompt, a voice prompt, and emailing.
[0079] The advantage of this setting is that during the development process of the R&D project, by monitoring the actual R&D cycle, timely warnings can be given to the R&D cycle of the R&D project, so as to improve the execution efficiency of the R&D project.
[0080] On the basis of the above embodiment, optionally, the management system also includes: a research and development cycle deduction module, which is used to update the actual research and development cycle based on the cycle deduction data when the cycle deduction data corresponding to the research and development project is detected, so as to obtain an updated actual research and development cycle.
[0081] Specifically, the cycle deduction data may be deduction data corresponding to a certain target cycle indicator. Exemplarily, assuming that the cycle deduction data is deduction data corresponding to a development cycle indicator, the actual development cycle corresponding to the saved development cycle indicator is updated based on the deduction data. Assuming that the cycle deduction data is deduction data corresponding to the overall cycle indicator, after obtaining the actual development cycle corresponding to the overall cycle indicator, the actual development cycle is updated, and subsequent operations are performed based on the updated actual development cycle.
[0082] The advantage of this setting is that it can achieve flexible control of the actual R&D cycle in response to special circumstances where the project R&D cycle is affected by uncontrollable factors such as procurement and external supervision.
[0083] Based on the above embodiment, optionally, the management system also includes: a display module, which is used to obtain execution effect data of at least one R&D project corresponding to the display dimension when receiving the display dimension input by the user, and perform a display operation on at least one execution effect data; wherein the display dimension includes at least one of the project level, department level and enterprise level.
[0084] Specifically, when the display dimension includes the project level, the execution effect data of at least one R&D project corresponding to the project level will be displayed. When the display dimension includes the department level or the enterprise level, the displayed content includes the execution effect data of at least one R&D project corresponding to the department level or the enterprise level and / or the integrated execution effect data obtained by performing post-processing operations on each execution effect data. Exemplarily, the post-processing operation can be addition, subtraction, averaging, etc. The post-processing operation is not limited here.
[0085] The advantage of such a setting is that the execution effect data of at least one determined R&D project can be displayed according to different display dimensions, which can meet the different viewing needs of different personnel.
[0086] The technical solution of this embodiment, by obtaining the R&D model of the R&D project, determines at least one target cycle indicator corresponding to the R&D project based on the set indicator mapping list and R&D model, and for each target cycle indicator, separately determines the execution effect data corresponding to the target cycle indicator, thereby solving the problem that the overall cycle indicator cannot reflect the actual execution status of each R&D stage, achieving the purpose of cycle management of different R&D stages of the R&D project, improving the comprehensiveness of the evaluation of the R&D project, improving the level of refined and automated management of the R&D project by the enterprise, and providing targeted data support for the subsequent control and adjustment of the R&D project.
[0087] Embodiment 3
[0088] Figure 3 1 is a flowchart of a method for managing a research and development project according to Embodiment 3 of the present invention. This embodiment is applicable to managing and evaluating the life cycle of a research and development project. The method can be executed by the management system of the research and development project in the above embodiment. Figure 3 As shown, the method includes:
[0089] S310: Obtain an actual R&D cycle of a R&D project and at least one project measurement data.
[0090] In this embodiment, the project measurement data is used to characterize the parameter values of quantifiable indicators of the R&D project.
[0091] S320. Determine a project complexity corresponding to the R&D project based on at least one project measurement data.
[0092] In one embodiment, optionally, the project complexity includes at least one of business complexity, technical complexity, management complexity and comprehensive complexity. Accordingly, the project measurement data corresponding to the business complexity include at least one of the number of project requirement items, the number of batches of project requirements issued and the number of project requirement changes. The project measurement data corresponding to the technical complexity include at least one of the project technical review level, the network security level of protection, the number of newly added interface consumption relationships and the total number of newly added computing resources. The project measurement data corresponding to the management complexity include at least one of the project workload, project plan change data and the number of project co-sponsoring departments.
[0093] In one embodiment, optionally, based on at least one project measurement data, the project complexity corresponding to the R&D project is determined, including: determining the business complexity of the R&D project based on at least one of the number of project requirement items, the number of project requirement issuance batches, and the number of project requirement changes; determining the technical complexity of the R&D project based on the project technical review level, the network security level protection level, the number of newly added interface consumption relationships, and the total number of newly added computing resources; determining the management complexity of the R&D project based on the project workload, project plan change data, and the number of project co-sponsoring departments; determining the comprehensive complexity of the R&D project based on the business complexity, technical complexity, and management complexity.
[0094] S330. Based on the complexity of the project, determine the planned R&D cycle corresponding to the R&D project.
[0095] In one embodiment, optionally, a planned R&D cycle corresponding to the R&D project is determined based on the project complexity, including: determining the classification level to which the R&D project belongs based on the project complexity, and determining the planned R&D cycle corresponding to the classification level based on a cycle mapping list; wherein the cycle mapping list contains at least one classification level and the planned R&D cycle corresponding to each classification level.
[0096] In one embodiment, optionally, the method further includes: based on the collection time node, obtaining the project complexity and actual R&D cycle corresponding to at least two completed projects respectively; adding at least two classification levels determined based on the complexity of at least two projects to the cycle mapping list; for each classification level, adding the planned R&D cycle determined based on the actual R&D cycle of at least one completed project corresponding to the classification level to the cycle mapping list.
[0097] S340. Determine the execution effect data of the R&D project based on the actual R&D cycle and the planned R&D cycle.
[0098] The technical solution of this embodiment determines the project complexity corresponding to the R&D project based on the project measurement data, determines the planned R&D cycle of the R&D project based on the project complexity, and determines the execution effect data of the R&D project based on the actual R&D cycle and the planned R&D cycle of the R&D project. This solves the problem of setting the planned R&D cycle based on subjective factors, improves the adaptability of the planned R&D cycle to the R&D project, and further improves the accuracy of the execution effect data of the R&D project, providing reliable data support for the subsequent management and adjustment of the R&D project.
[0099] On the basis of the above embodiments, optionally, the actual R&D cycle includes an actual R&D cycle corresponding to at least one target cycle indicator, and the project measurement data includes project measurement data corresponding to at least one target cycle indicator. Accordingly, the method further includes: obtaining the R&D model of the R&D project, and determining at least one target cycle indicator corresponding to the R&D project based on the indicator mapping list of the R&D model; wherein the indicator mapping list includes at least one R&D model and at least one cycle indicator corresponding to each R&D model.
[0100] In one embodiment, optionally, in the indicator mapping list, the cycle indicators corresponding to the waterfall R&D model include at least one of the overall cycle indicators, demand development cycle indicators, design cycle indicators, development cycle indicators, testing cycle indicators and production cycle indicators, and the cycle indicators corresponding to the iterative R&D model or the agile R&D model include the overall cycle indicators and / or iterative cycle indicators.
[0101] Based on the above embodiments, optionally, the method also includes: when the project type of the R&D project belongs to an ongoing project, for each target cycle indicator, the cycle difference is determined based on the actual R&D cycle and the planned R&D cycle corresponding to the target cycle indicator; if the cycle difference is less than the preset difference threshold, an early warning operation is performed based on the target cycle indicator.
[0102] On the basis of the above embodiment, optionally, the method further includes: when period deduction data corresponding to the R&D project is detected, updating the actual R&D period based on the period deduction data to obtain an updated actual R&D period.
[0103] Based on the above embodiment, optionally, when a display dimension input by the user is received, execution effect data of at least one R&D project corresponding to the display dimension is obtained, and a display operation is performed on at least one execution effect data; wherein the display dimension includes at least one of the project level, department level and enterprise level.
[0104] Figure 4 is a flowchart of a specific example of a management method for a research and development project provided according to Embodiment 3 of the present invention. Specifically, Figure 4 The R&D cycle deduction management process, R&D cycle basic data calculation process and R&D cycle evaluation and early warning process in the management method of the R&D project are shown.
[0105] In the R&D cycle deduction management process, the project manager fills in and submits the R&D cycle deduction application form through the deduction application port. The R&D cycle administrator reviews the submitted R&D cycle deduction application form. If the review is passed, the cycle deduction data in the R&D cycle deduction application form is saved in the R&D cycle deduction library. If the review is not passed, it is returned to the deduction application port. The process ends and the R&D cycle deduction library data storage is completed.
[0106] In the R&D cycle basic data calculation process, the management system initiates the R&D cycle basic data calculation process of the R&D project based on the preset time node, and searches the R&D cycle indicator library for the target cycle indicators applicable to the R&D project according to the R&D model of the R&D project. According to the target cycle indicators, complete the information collection of the actual execution cycle of the R&D project. Query the R&D cycle deduction library to complete the calculation of the actual R&D cycle basic data. The management system automatically sends the actual R&D cycle data to the project manager for confirmation. The project manager can provide feedback on the data, and the data is finalized after confirmation by the R&D cycle administrator, and the actual R&D cycle after finalization is stored in the R&D cycle basic database. Among them, the R&D cycle basic database includes the actual R&D cycle and the actual R&D cycle of the completed project. At this point, the storage of basic data for the R&D cycle is completed.
[0107] In the R&D cycle evaluation and early warning process, the management system dynamically calculates the planned R&D cycle corresponding to at least one cycle indicator based on the project complexity model and the actual R&D cycle of the completed project in the R&D cycle basic database. Based on the actual R&D cycle in the R&D cycle basic database and its corresponding planned R&D cycle, the scoring data of the R&D project is generated and stored in the project R&D cycle scoring library. For completed projects, the execution effect data is displayed based on multiple display dimensions at the project level, department level, and enterprise level. For ongoing projects, early warning operations for overdue and upcoming overdue projects are performed based on the actual R&D cycle and the planned R&D cycle. The process ends and is carried out in batches every day.
[0108] Embodiment 4
[0109] Figure 5 1 is a schematic diagram of the structure of an electronic device provided according to Embodiment 4 of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.
[0110] like Figure 5 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0111] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0112] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a management method for a research and development project.
[0113] In some embodiments, the management method of the R&D project may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the management method of the R&D project described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the management method of the R&D project in any other appropriate manner (e.g., by means of firmware).
[0114] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0115] The computer program for implementing the management method of the R&D project of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program can be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0116] Embodiment 5
[0117] Embodiment 5 of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to execute a management method for a research and development project, the method comprising:
[0118] Obtain the actual R&D cycle of the R&D project and at least one project metric data;
[0119] Determining a project complexity corresponding to the research and development project based on at least one project metric data;
[0120] Determine the planned R&D cycle corresponding to the R&D project based on the complexity of the project;
[0121] Based on the actual R&D cycle and the planned R&D cycle, determine the execution effect data of the R&D project.
[0122] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0123] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).
[0124] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.
[0125] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.
[0126] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.
[0127] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims
1. A management system for R&D projects, characterized in that: include: A project information data acquisition module, used to acquire the actual R&D cycle of the R&D project and at least one project measurement data; wherein the project measurement data is used to characterize the parameter value of the quantifiable indicator of the R&D project; A project complexity determination module, for determining the project complexity corresponding to the R&D project based on at least one project measurement data; the project complexity includes at least one of business complexity, technical complexity, management complexity and comprehensive complexity; accordingly, the project measurement data corresponding to the business complexity includes at least one of the number of project requirement items, the number of project requirement issuance batches and the number of project requirement changes; the project measurement data corresponding to the technical complexity includes at least one of the project technical review level, the network security level protection level, the number of newly added interface consumption relationships and the total number of newly added computing resources; the project measurement data corresponding to the management complexity includes at least one of the project workload, project plan change data and the number of project co-sponsoring departments; The project complexity determination module is specifically used to: determine the business complexity of the R&D project based on at least one of the number of project requirement items, the number of project requirement batches issued, and the number of project requirement changes; determine the technical complexity of the R&D project based on the project technical review level, network security level protection level, the number of newly added interface consumption relationships, and the total number of newly added computing resources; determine the management complexity of the R&D project based on the project workload, project plan change data, and the number of project co-sponsoring departments; determine the comprehensive complexity of the R&D project based on the business complexity, the technical complexity, and the management complexity; A planned R&D cycle determination module, used to determine the planned R&D cycle corresponding to the R&D project based on the complexity of the project; The execution effect data determination module is used to determine the execution effect data of the R&D project based on the actual R&D cycle and the planned R&D cycle.
2. The management system according to claim 1, characterized in that: The planned R&D cycle determination module is specifically used for: Based on the project complexity, determine the classification level to which the R&D project belongs, and based on the cycle mapping list, determine the planned R&D cycle corresponding to the classification level; wherein the cycle mapping list includes at least one classification level and the planned R&D cycle corresponding to each classification level.
3. The management system according to claim 2, characterized in that: The management system also includes: A cycle mapping list determination module is used to obtain the project complexity and actual R&D cycle corresponding to at least two completed projects based on the collection time node; adding at least two classification levels determined based on at least two project complexities to the cycle mapping list; For each classification level, a planned R&D cycle determined based on an actual R&D cycle of at least one completed project corresponding to the classification level is added to the cycle mapping list.
4. The management system according to any one of claims 1 to 3, characterized in that: The actual R&D cycle includes an actual R&D cycle corresponding to at least one target cycle indicator, and the project measurement data includes project measurement data corresponding to at least one target cycle indicator. Accordingly, the management system further includes: A periodic indicator library management module, used to store an indicator mapping list, wherein the indicator mapping list includes at least one R&D mode and at least one periodic indicator corresponding to each R&D mode; The target cycle indicator determination module is used to obtain the R&D model of the R&D project and determine at least one target cycle indicator corresponding to the R&D project based on the indicator mapping list of the R&D model.
5. The management system according to claim 4, characterized in that: In the indicator mapping list, the cycle indicators corresponding to the waterfall R&D model include at least one of the overall cycle indicators, demand development cycle indicators, design cycle indicators, development cycle indicators, testing cycle indicators and production cycle indicators, and the cycle indicators corresponding to the iterative R&D model or the agile R&D model include overall cycle indicators and / or iterative cycle indicators.
6. The management system according to claim 4, characterized in that: The management system also includes: An early warning module, for determining a cycle difference for each target cycle indicator based on an actual R&D cycle and a planned R&D cycle corresponding to the target cycle indicator when the R&D project type belongs to an ongoing project; If the period difference is less than a preset difference threshold, an early warning operation is performed based on the target period indicator.
7. The management system according to claim 1, characterized in that: The management system also includes: The R&D cycle deduction module is used to update the actual R&D cycle based on the cycle deduction data when the cycle deduction data corresponding to the R&D project is detected, so as to obtain an updated actual R&D cycle.
8. The management system according to claim 1, characterized in that: The management system also includes: The display module is used to obtain the execution effect data of at least one R&D project corresponding to the display dimension when receiving the display dimension input by the user, and perform a display operation on at least one execution effect data; wherein the display dimension includes at least one of the project level, department level and enterprise level.
