CN117649183A - Software project planning whole process management system and method - Google Patents
Software project planning whole process management system and method Download PDFInfo
- Publication number
- CN117649183A CN117649183A CN202210984025.4A CN202210984025A CN117649183A CN 117649183 A CN117649183 A CN 117649183A CN 202210984025 A CN202210984025 A CN 202210984025A CN 117649183 A CN117649183 A CN 117649183A
- Authority
- CN
- China
- Prior art keywords
- estimation
- project
- software
- estimated
- planned
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 76
- 238000007726 management method Methods 0.000 title claims abstract description 49
- 238000013439 planning Methods 0.000 title claims abstract description 40
- 238000010276 construction Methods 0.000 claims description 10
- 238000013278 delphi method Methods 0.000 claims description 9
- 238000011161 development Methods 0.000 claims description 8
- 238000000354 decomposition reaction Methods 0.000 claims description 3
- 230000000694 effects Effects 0.000 description 8
- 238000004458 analytical method Methods 0.000 description 4
- 238000012360 testing method Methods 0.000 description 4
- 238000012356 Product development Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000009472 formulation Methods 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000009795 derivation Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a software project planning whole process management system and a method, wherein the method comprises the following steps: selecting a system model of a software project to be planned; determining each stage of the software project process and workload proportion recommendation of each stage based on the selected system model and project related parameters; estimating the product scale of the software project to be planned; automatically estimating a total workload based on the estimated product scale; automatically determining the workload of each stage based on the estimated total workload and the workload proportion recommendation of each stage; based on the workload, project time periods and task progress are automatically calculated and task work packages are determined. The method realizes scientific planning management and progress estimation of the software project, and ensures that the project is carried out in a controllable state.
Description
Technical Field
The invention belongs to the field of military software project planning management, and particularly relates to a software project planning whole process management system and method.
Background
The GJB5000B-2021 military software capability maturity model (hereinafter referred to as the GJB5000B standard) specifies the relevant practices in military software demonstration, development, testing and maintenance activities. The practices are classified according to the practice domain, so that organizations are guided to conduct fine process management, the organization process is continuously improved, the quality and the process performance are improved, and the customer satisfaction is improved. The practice domain is managed according to a classification and grading mode and is divided into an organization management class, a project management class, an engineering class and a support class.
According to the GJB5000B standard, project planning is an independent practice domain of the project management class. The planning work of military software projects takes working products and project requirements as starting points, plans and estimates the related working products and requirements, and evaluates and tracks required resources, related parties, data storage and the like. Negotiating commitments, developing progress, and identifying and analyzing project risks.
In the actual work of military software projects, scientific planning management and progress estimation are carried out on the current projects according to GJB5000B standards and historical project experience according to the current project conditions, the projects are guaranteed to be carried out in a controllable state, and meanwhile experience data are accumulated to provide comparison basis for subsequent software projects.
Disclosure of Invention
In view of the above analysis, the present invention aims to provide a software project planning whole process management system and method, which realize military software project planning whole process management, provide a weighted Delphi method and an analogy method to estimate the product scale of a software project, automatically estimate the total workload of the software project based on the product scale, automatically determine the workload of each stage based on the proportional relation between the total workload and the workload of each stage corresponding to a system model built in the system, realize scientific planning management and progress estimation of the software project, and ensure that the project is performed in a controllable state.
In one aspect, the invention provides a software project planning whole process management method, which specifically comprises the following steps:
selecting a system model of a software project to be planned;
determining each stage of the software project process and workload proportion recommendation of each stage based on the selected system model and project related parameters;
estimating the product scale of the software project to be planned;
estimating a total workload based on the estimated product scale;
based on the estimated total workload and the workload proportion recommendation for each stage, determining the workload for each stage.
Further, the architecture model includes: the new product develops a general model, an incremental model and a quick development model.
Further, the project-related parameters include: project mode, military input, project scale, safety key level, project characteristics and quality requirements.
Further, the estimating the product scale of the software item to be planned includes:
decomposing the software project to be planned according to the deliverable result to obtain a work decomposition structure WBS;
and estimating the product scale by using a weighted Delphi method or an analogy method aiming at the WBS to obtain the product scale of the software project to be planned.
Further, the estimating the product scale by using the weighted Delphi method comprises:
s11, determining an estimation object, an estimation difference threshold value and an estimation assumption;
s12, based on the estimation assumption, estimating each estimation object by a plurality of estimation staff, wherein each estimation staff gives a maximum value, a minimum value and a most possible value for the estimation object;
s13, for each estimation object, calculating a weighted average value of estimation results of each estimation person as an estimation value of each estimation object:
s14, for each instituteThe estimation object calculates an estimation difference: based on the estimated values of all the estimators obtained in s13, an estimated difference is calculated,wherein, the maximum estimated value and the minimum estimated value refer to taking the maximum estimated value and the minimum estimated value from the estimated values of all the estimated staff,
s15, for each estimated object, when the estimated difference is greater than the estimated difference threshold, all the estimators re-estimate the object until the estimated difference does not exceed the threshold;
s16, calculating a final estimation result based on the estimation value of each estimation person satisfying s15 for each estimation object:wherein the intermediate estimate refers to the arithmetic average of other estimates divided by the minimum and maximum estimates;
and s17, accumulating the final estimation results of all the estimation objects to obtain the product scale of the software project to be planned.
Further, the estimating of the product scale using the analogy method includes:
s21, acquiring historical item data similar to a software item to be planned, wherein the historical item data comprises WBS and estimation assumptions of the historical item;
s22, checking whether the estimation assumption of the history item is consistent with the estimation assumption of the software item to be planned, if so, executing step S23, continuing to use the analogy method for estimation, and if not, discarding the analogy method, and not executing steps S23-S24;
s23: based on the WBS of the history item and the WBS of the software item to be planned, comparing item by item to obtain the proportional relation of the scale of the history item and the software item to be planned;
and S24, estimating the product scale of the software project to be planned based on the proportional relation.
Further, the estimating the total workload based on the estimated product scale includes, total workload = product scale/person-average productivity.
On the other hand, the invention also provides a software project planning whole process management system, which comprises: the system comprises a project planning module, an automatic estimation module and a user management module;
project planning module: the system comprises a system model for selecting a software project to be planned, and a stage for determining the inclusion of the software project process based on the selected system model and project related parameters;
and an automatic estimation module: estimating a product scale of a software project to be planned, estimating a total workload based on the estimated product scale, determining each stage workload of the software project process based on the estimated total workload, and determining each stage construction period node based on each stage workload;
and a user management module: for user management and user rights management of software project team members.
Further, the selecting the system model of the software item to be planned includes selecting a system model suitable for the software item to be planned from system recommended system models, if no suitable system model exists, creating a new system model and selecting the model.
Further, the determining the stages included in the software project process based on the selected system model and the project related parameters includes, based on the selected system model and the project related parameters, the system presenting all stages that the software project process matching the selected system model and the project related parameters should include, clipping or merging based on the all stages, and determining the stages included in the final project process.
The invention can realize at least one of the following beneficial effects:
1. the product scale of the software project is estimated by providing a weighted Delphi method and an analogy method, the total workload of the software project is automatically estimated based on the product scale, and the workload of each stage is automatically determined based on the proportional relation between the total workload and the workload of each stage corresponding to a system model built in the system, so that the project is ensured to be carried out in a controllable state.
2. By providing analogy to estimate the product scale and the proportional relation of the workload of each stage corresponding to the system model built in the system, the historical experience data is fully utilized, and the planning management of the whole software project planning process science is realized.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The drawings are only for purposes of illustrating particular embodiments and are not to be construed as limiting the invention, like reference numerals being used to refer to like parts throughout the several views.
FIG. 1 is a block diagram of a software project planning overall process management system of the present invention.
Detailed Description
Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which form a part hereof, and together with the description serve to explain the principles of the invention, and are not intended to limit the scope of the invention.
Method embodiment
The invention discloses a software project planning whole process management method, which specifically comprises the following steps:
step S1: a hierarchal model of the item of software to be planned is selected.
Specifically, the system model comprises a new product development general model, an increment model and a rapid development model.
Step S2: based on the selected architecture model and project related parameters, each stage of the software project process and the workload proportion recommendation for each stage are determined.
Specifically, the project-related parameters include: project mode, military input, project scale, safety key level, project characteristics and quality requirements.
Preferably, the new product development general model comprises the following stages and workload proportions of the stages: project planning and software requirement analysis phase (23%), software design phase (18%), software implementation and unit integration test phase (24%), software qualification test phase (23%), software acceptance and delivery phase (12%).
Specifically, the incremental model includes stages and the workload rates of the stages are determined by the specific project formulation rules.
Preferably, the rapid development model comprises the following stages and workload proportions of the stages: project planning and software requirement analysis phase (28%), software development and testing phase (62), software acceptance and delivery node (10%).
Step S3: estimating the product scale of the software project to be planned: decomposing the software project to be planned according to the deliverable result to obtain a work decomposition structure WBS; and estimating the product scale by using a weighted Delphi method or an analogy method aiming at the WBS to obtain the product scale of the software project to be planned.
Specifically, the product scale estimation using the weighted Delphi method includes the steps of:
s11, determining an estimation object, an estimation difference threshold value and an estimation assumption;
s12, based on the estimation assumption, estimating each estimation object by a plurality of estimation staff, wherein each estimation staff gives a maximum value, a minimum value and a most probable value for the estimation object;
s13, for each estimation object, calculating a weighted average value of estimation results of each estimation person as an estimation value of each estimation object:
s14, calculating an estimation difference for each estimation object: based on the estimated values of all the estimators obtained in s13, an estimated difference is calculated,wherein the maximum and minimum estimatesThe calculation value refers to taking the maximum and minimum estimated values among the estimated values of all the estimated persons,
s15, for each estimated object, when the estimated difference is greater than the estimated difference threshold, all the estimators re-estimate the object until the estimated difference does not exceed the threshold;
s16, calculating a final estimation result based on the estimation value of each estimation person satisfying s15 for each estimation object:wherein the intermediate estimate refers to the arithmetic average of other estimates divided by the minimum and maximum estimates;
and s17, accumulating the final estimation results of all the estimation objects to obtain the estimation result of the product scale of the software project to be planned.
Specifically, the product scale estimation using the analogy method includes the steps of:
s21, acquiring historical item data similar to a software item to be planned, wherein the historical item data comprises WBS and estimation assumptions of the historical item;
s22, checking whether the estimation assumption of the history item is consistent with the estimation assumption of the software item to be planned, if so, executing step S23, continuing to use the analogy method for estimation, and if not, discarding the analogy method, and not executing steps S23-S24;
s23, comparing item by item based on the WBS of the history item and the WBS of the software item to be planned, and obtaining the proportional relation of the scale of the history item and the scale of the software item to be planned;
and S24, estimating the product scale of the software project to be planned based on the proportional relation.
S4, estimating the total workload based on the estimated product scale;
specifically, total workload = product scale/per person productivity.
And S5, determining the workload of each stage based on the estimated total workload and the workload proportion recommendation of each stage.
The embodiment discloses a software project planning whole process management method, which estimates the product scale of a software project through a weighted Delphi method and an analogy method, automatically estimates the total workload of the software project based on the product scale, automatically determines the workload of each stage based on the proportional relation between the total workload and the workload of each stage corresponding to a system model built in a system, ensures that the project is carried out in a controllable state, and realizes the planning management of the software project planning whole process science.
System embodiment
The invention discloses a software project planning whole process management system, which specifically comprises a project planning module, an automatic estimation module and a user management module.
Project planning module: for selecting a hierarchy model of a software project to be planned, and determining phases involved in the software project process based on the selected hierarchy model and project related parameters.
Specifically, the project planning module comprises a software model selection sub-module, a model proportion setting sub-module and a project affiliated planning sub-module.
Specifically, the software model selection submodule is used for selecting a system model suitable for a software project to be planned from system recommended system models, and determining the stage included in the software project process based on the selected system model and project related parameters. Wherein the architecture model comprises a new generic model, an incremental model, or a fast developing model, if there is no suitable architecture model, a new architecture model is created and selected. Further, based on the selected architecture model and project related parameters, the system presents all phases that should be included in the software project process that match the selected architecture model and project related parameters, and based on the all phases, the phases that are included in the final project process are clipped or combined.
Specifically, the model proportion setting submodule is used for setting the workload proportion of each stage of the software project process.
Preferably, the new product development generic model comprises stages and the workload ratio of each stage is shown in table 1:
TABLE 1
Alternatively, the primary activities at each stage of the new development generic model and the workload distribution ratios for each primary activity are shown in Table 2, for example:
TABLE 2
Specifically, the incremental model includes stages and the workload rates of the stages are determined by the specific project formulation rules.
Preferably, the rapid development model comprises stages and the workload ratio of each stage is shown in table 3:
TABLE 3 Table 3
Alternatively, the primary activities at each stage of the rapid development model and the workload distribution ratios for each primary activity are shown in Table 4, for example:
TABLE 4 Table 4
Specifically, the project affiliated plan submodule is used for uploading, downloading and consulting the project affiliated plan, and comprises the following steps: risk management programs, resource management programs, relevant management programs, training management programs, and data storage programs.
And an automatic estimation module: the method comprises the steps of estimating a product scale of a software project to be planned, estimating a total workload based on the estimated product scale, determining a workload of each stage of a software project process based on the estimated total workload, and determining a project period node of each stage based on the workload of each stage.
Specifically, the automatic estimation module comprises a software scale estimation module, a workload estimation module, a construction period export module, a work task package estimation module and a task schedule export module.
Specifically, the software scale estimation submodule is used for estimating the product scale of the software project to be planned, and the estimation process is the same as step S3 in the method embodiment.
Specifically, the workload estimation submodule is used for estimating the total workload and the workload of each stage, and the estimation process comprises the following steps:
step S101 of estimating a total workload based on the estimated product scale, total workload=product scale/average productivity;
step S102, determining the workload of each stage based on the estimated total workload and the workload proportion recommendation of each stage;
step S103, determining the workload of the main activities of each stage based on the workload of each stage and the distribution proportion of the workload of the main activities of each stage;
specifically, the construction period derivation submodule is used for determining the total construction period and the construction period of each stage based on the total workload and the workload of each stage.
Specifically, the work task package estimation submodule is used for determining the work task package of each stage based on the total construction period and the construction period of each stage.
Specifically, the export task schedule submodule is used for determining a schedule of a work task package based on the construction period of each stage and the work task package.
And a user management module: for user management and user rights management of software project team members. The system comprises a member management module and a member authority management module.
The embodiment discloses a software project planning whole process management system, which realizes the data calculation and analysis automation process in project planning, and improves the efficiency of project planning stage. By automatically calculating the total workload and the workload of each stage according to the WBS and the estimation algorithm, and automatically scheduling the construction period based on the workload, the task schedule is determined, the scientific management of software project planning is realized, and the estimation process is ensured to meet the software model and the proportion requirement of the GJB5000B military standard.
Because the software project planning whole process management system and the software project planning whole process management method are based on the same invention conception, the related parts can be mutually referred, and therefore, the same technical effect can be realized.
The present invention is not limited to the above-mentioned embodiments, and any changes or substitutions that can be easily understood by those skilled in the art within the technical scope of the present invention are intended to be included in the scope of the present invention.
Claims (10)
1. The software project planning whole process management method is characterized by comprising the following steps:
selecting a system model of a software project to be planned;
determining each stage of the software project process and workload proportion recommendation of each stage based on the selected system model and project related parameters;
estimating the product scale of the software project to be planned;
estimating a total workload based on the estimated product scale;
based on the estimated total workload and the workload proportion recommendation for each stage, determining the workload for each stage.
2. The method of management according to claim 1, wherein the hierarchy model includes: the new product develops a general model, an incremental model and a quick development model.
3. The method of claim 1, wherein the project-related parameters include: project mode, military input, project scale, safety key level, project characteristics and quality requirements.
4. The method of claim 1, wherein estimating the product size of the item of software to be planned comprises:
decomposing the software project to be planned according to the deliverable result to obtain a work decomposition structure WBS;
and estimating the product scale by using a weighted Delphi method or an analogy method aiming at the WBS to obtain the product scale of the software project to be planned.
5. The method of managing as set forth in claim 4, wherein said estimating the product size using a weighted Delphi method includes:
s11, determining an estimation object, an estimation difference threshold value and an estimation assumption;
s12, based on the estimation assumption, estimating each estimation object by a plurality of estimation staff, wherein each estimation staff gives a maximum value, a minimum value and a most possible value for the estimation object;
s13, for each estimation object, calculating a weighted average value of estimation results of each estimation person as an estimation value of each estimation object:
s14, calculating an estimated difference for each estimated object: based on the estimated values of all the estimators obtained in s13, an estimated difference is calculated,wherein, the maximum estimated value and the minimum estimated value refer to taking the maximum estimated value and the minimum estimated value from the estimated values of all the estimated staff,
s15, for each estimated object, when the estimated difference is greater than the estimated difference threshold, all the estimators re-estimate the object until the estimated difference does not exceed the threshold;
s16, calculating a final estimation result based on the estimation value of each estimation person satisfying s15 for each estimation object:wherein the intermediate estimate refers to the arithmetic average of other estimates divided by the minimum and maximum estimates;
and s17, accumulating the final estimation results of all the estimation objects to obtain the product scale of the software project to be planned.
6. The method of claim 4, wherein said using analogy to make product scale estimates comprises:
s21, acquiring historical item data similar to a software item to be planned, wherein the historical item data comprises WBS and estimation assumptions of the historical item;
s22, checking whether the estimation assumption of the history item is consistent with the estimation assumption of the software item to be planned, if so, executing step S23, continuing to use the analogy method for estimation, and if not, discarding the analogy method, and not executing steps S23-S24;
s23: based on the WBS of the history item and the WBS of the software item to be planned, comparing item by item to obtain the proportional relation of the scale of the history item and the software item to be planned;
and S24, estimating the product scale of the software project to be planned based on the proportional relation.
7. The method of managing of claim 4, wherein estimating the total workload based on the estimated product size comprises total workload = product size/person-average productivity.
8. The software project planning whole process management system is characterized by comprising a project planning module, an automatic estimation module and a user management module;
project planning module: the system comprises a system model for selecting a software project to be planned, and a stage for determining the inclusion of the software project process based on the selected system model and project related parameters;
and an automatic estimation module: estimating a product scale of a software project to be planned, estimating a total workload based on the estimated product scale, determining each stage workload of the software project process based on the estimated total workload, and determining each stage construction period node based on each stage workload;
and a user management module: for user management and user rights management of software project team members.
9. The management system of claim 8, wherein the selecting a hierarchy model for the item of software to be planned includes selecting a hierarchy model suitable for the item of software to be planned from among the hierarchy models recommended by the system, and if there is no suitable hierarchy model, creating a new hierarchy model and selecting the model.
10. The management system of claim 9, wherein determining the stages involved in the software project process based on the selected architecture model and project-related parameters comprises, based on the selected architecture model and project-related parameters, the system presenting all stages that the software project process matching the selected architecture model and project-related parameters should involve, clipping or merging based on the all stages, determining the stages involved in the final project process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210984025.4A CN117649183A (en) | 2022-08-17 | 2022-08-17 | Software project planning whole process management system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210984025.4A CN117649183A (en) | 2022-08-17 | 2022-08-17 | Software project planning whole process management system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117649183A true CN117649183A (en) | 2024-03-05 |
Family
ID=90045630
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210984025.4A Pending CN117649183A (en) | 2022-08-17 | 2022-08-17 | Software project planning whole process management system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117649183A (en) |
-
2022
- 2022-08-17 CN CN202210984025.4A patent/CN117649183A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Kim et al. | A two-stage stochastic integer programming approach to integrated staffing and scheduling with application to nurse management | |
| Singh | Resource constrained multi-project scheduling with priority rules & analytic hierarchy process | |
| US8190463B2 (en) | System and method for managing mobile workers | |
| Shen et al. | Dynamic software project scheduling through a proactive-rescheduling method | |
| Alfieri et al. | A project scheduling approach to production planning with feeding precedence relations | |
| Asaul et al. | The latest information systems in the enterprise management and trends in their development | |
| Megow et al. | Decision support and optimization in shutdown and turnaround scheduling | |
| Alsheddy et al. | Empowerment scheduling for a field workforce | |
| Lamersdorf et al. | A multi-criteria distribution model for global software development projects | |
| US20130054289A1 (en) | System and Method for Budget-Compliant, Fair and Efficient Manpower Management | |
| Özdamar et al. | Uncertainty modelling in software development projects (with case study) | |
| Agyapong-Kodua et al. | Systems approach to modelling cost and value dynamics in manufacturing enterprises | |
| Nurre et al. | Online scheduling problems with flexible release dates: Applications to infrastructure restoration | |
| Januszczak et al. | Simulation standard for business process management | |
| Gong et al. | Logic-based multiobjective optimization for restoration planning | |
| Attia et al. | Flexible resources allocation techniques: characteristics and modelling | |
| CN117350640A (en) | Project progress management method and system | |
| CN117649183A (en) | Software project planning whole process management system and method | |
| Neubert et al. | Flow shop operator scheduling through constraint satisfaction and constraint optimisation techniques | |
| Kohli | Enterprise project management using primavera P6 EPPM | |
| Habla et al. | A finite capacity production planning approach for semiconductor manufacturing | |
| Meixell et al. | Activity structures in a project-based environment: A coordination theory perspective | |
| CA2832806A1 (en) | Method for optimizing schedule compression in projects using accelerating and overlapping of activities | |
| Zebro et al. | Process mining in project management for smart cities | |
| Jadallah et al. | The how? when? and what? for the process of re-planning for product releases |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |