Software function demand evaluation method and system based on function points, medium and equipment
Through the software function requirements evaluation method based on functional points, the problem of lack of unified evaluation standards and inconsistency in the existing technology is solved, the efficiency and accuracy of software functions and cost evaluation are achieved, and the technology and management modernization of the industry is promoted.
Patent Information
- Application Number
- CN202411452739.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-17
- Publication Date
- 2025-02-14
AI Technical Summary
The lack of unified software functions and cost evaluation standards and methods in the prior art, the benchmark data is inconsistent, and the rapid changes in technology and market make it difficult to update the evaluation standards in a timely manner.
The software function requirements evaluation method based on functional points is adopted. By decomposing the software to be evaluated into multiple functional points according to the estimated function, obtaining benchmark data based on historical project data, and using estimation models and adjustment factors to estimate the workload and cost of the software.
It improves the accuracy and efficiency of software functions and cost evaluation, optimizes operation and decision-making processes, promotes the modernization of the industry's technology and management, and ensures the standardization, accuracy and consistency of evaluation results.
Smart Images

Figure CN119443850A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of software evaluation, and in particular to a method, system, medium and device for evaluating software functional requirements based on function points. Background Art
[0002] Software development is the core competitiveness in the digital economy era, but in actual work, the evaluation of software functions and costs is relatively difficult, mainly manifested in: 1. Lack of unified evaluation standards and methods: The cost evaluation of software projects involves many aspects, including project scale, complexity, technical difficulty, experience of the development team, etc. In addition, different organizations and individuals may adopt different evaluation methods, which also increases the complexity of the evaluation. 2. Inconsistency of benchmark data: Benchmark data is an important reference for software cost evaluation, but benchmark data from different sources may differ, which makes the evaluation results lack comparability. For example, benchmark data released by different research institutions or industry associations may be based on different samples or use different statistical methods, resulting in inconsistent data. 3. Rapid changes in technology and market: The software industry has a fast technological iteration speed and market demand is constantly changing, which makes it difficult to update the evaluation standards in a timely manner to adapt to new situations. Summary of the invention
[0003] In view of the above problems, the purpose of the present invention is to provide a method, system, medium and device for evaluating software functional requirements based on function points, which can effectively improve the accuracy of estimation.
[0004] To achieve the above-mentioned purpose, the present invention adopts the following technical scheme: a software functional requirement evaluation method based on function points, which comprises: decomposing the software to be evaluated into multiple function points according to the estimated functions to estimate the overall function points of the software; obtaining benchmark data through historical project data, estimating the workload of the software by using the overall function points through the benchmark data and the estimation model, and introducing an adjustment factor to adjust the estimated value of the workload; determining the cost estimate through the estimated value of the workload, formulating an accurate software project plan based on the cost estimate and the estimated value of the workload, and monitoring the progress and quality of the project through the measurement of function points.
[0005] Furthermore, the software to be evaluated is decomposed into multiple functional points according to the estimated functions, including:
[0006] In the early stages of the project, a preliminary estimate of the software size is made to obtain the estimated function points;
[0007] Clarify the project requirements based on the estimated functional points, and decompose the software into multiple functional points based on the requirements.
[0008] Furthermore, the measurement of function points is based on a number of common measurement elements, including: data groups, data items, external inputs, external outputs, external queries, and external reports;
[0009] These metric elements are counted and weighted to estimate the overall function points of the software.
[0010] Furthermore, the international standard function point method is used to count the function points.
[0011] Furthermore, we obtain benchmark data through historical project data, and use the overall function points to estimate the software workload through the benchmark data and estimation model, including:
[0012] Obtain benchmark data from historical project data, obtain the average time consumption rate of software function points through the benchmark data, and estimate the software workload based on the average time consumption rate.
[0013] Furthermore, adjustment factors are introduced to adjust the estimated value of workload, including:
[0014] The adjustment factor takes project factors into account. According to the amount of data that the project needs to process, the estimated value of the workload is adjusted through the adjustment factor. The adjustment factor is the scale range change factor.
[0015] A software functional requirement evaluation system based on function points includes: a function point estimation module, which decomposes the software to be evaluated into multiple function points according to the estimated functions to estimate the overall function points of the software; a workload estimation module, which obtains benchmark data through historical project data, estimates the workload of the software by using the overall function points through the benchmark data and the estimation model, and introduces an adjustment factor to adjust the estimated value of the workload; a software progress and quality evaluation module, which determines the cost estimate through the estimated value of the workload, formulates an accurate software project plan based on the cost estimate and the estimated value of the workload, and monitors the progress and quality of the project through the measurement of function points.
[0016] Furthermore, the software to be evaluated is decomposed into multiple functional points according to the estimated functions, including:
[0017] In the early stages of the project, a preliminary estimate of the software size is made to obtain the estimated function points;
[0018] Clarify the project requirements based on the estimated functional points, and decompose the software into multiple functional points based on the requirements.
[0019] A computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions, which, when executed by a computing device, cause the computing device to perform any of the above methods.
[0020] A computing device comprises: one or more processors, a memory and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for executing any of the above methods.
[0021] The present invention adopts the above technical solution, which has the following advantages:
[0022] The present invention can improve the efficiency and accuracy of software function and cost evaluation and audit. The application of the function point method optimizes the operation and decision-making process, and also promotes the modernization of technology and management of the entire industry. Through the comprehensive application of the function point method, the software cost measurement standard is unified, the software cost evaluation and audit process is standardized, and the artificial intelligence-assisted software cost estimation and audit are realized with the help of advanced technology, ensuring that the software cost measurement results are standardized, accurate and consistent under the premise of complying with national / industry standards. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Figure 1 It is a flow chart of a method for evaluating software functional requirements based on function points in an embodiment of the present invention. DETAILED DESCRIPTION
[0024] At present, software development is no longer a simple technical activity, but an indispensable part of corporate strategy. The depth and breadth of software development are directly related to the level of intelligent operation of the enterprise. It can make the internal processes of the enterprise more efficient, reduce resource waste, improve the accuracy of decision-making and the speed of responding to the market. In addition, software development plays a vital role in improving user experience. Through user data analysis and human-computer interaction design, software can provide more personalized and intuitive services, enhance user satisfaction and loyalty. This user-centric design concept not only enhances the value of the product, but also provides a platform for continuous interaction and value creation for the enterprise.
[0025] Therefore, in order to solve the problem that the evaluation of existing software functions and costs is relatively difficult, the present invention provides a method, system, medium and device for evaluating software function requirements based on function points, which decompose the software to be evaluated into multiple function points according to the estimated functions to estimate the overall function points of the software; obtain benchmark data through historical project data, estimate the workload of the software with the overall function points through the benchmark data and the estimation model, and introduce adjustment factors to adjust the estimated value of the workload; determine the cost estimate through the estimated value of the workload, formulate an accurate software project plan based on the cost estimate and the estimated value of the workload, and monitor the progress and quality of the project through the measurement of function points. Therefore, the present invention can effectively improve the accuracy of the estimation.
[0026] In order to make the purpose, technical solution and advantages of the embodiment of the present invention clearer, the technical solution of the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings of the embodiment of the present invention. Obviously, the described embodiment is a part of the embodiment of the present invention, not all of the embodiments. Based on the described embodiment of the present invention, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of the present invention.
[0027] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit exemplary embodiments according to the present invention. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprising" and / or "including" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.
[0028] In one embodiment of the present invention, a method for evaluating software functional requirements based on function points is provided to identify and quantify functional requirements in a software system through function point analysis. Figure 1 As shown, the method comprises the following steps:
[0029] 1) Decompose the software to be evaluated into multiple function points according to the estimated functions to estimate the overall function points of the software;
[0030] 2) Obtain benchmark data through historical project data, estimate the software workload by using the overall function points through the benchmark data and estimation model, and introduce adjustment factors to adjust the estimated value of the workload;
[0031] 3) Determine the cost estimate through the workload estimate, develop an accurate software project plan based on the cost estimate and workload estimate, and monitor the progress and quality of the project through the measurement of function points.
[0032] The function point analysis method used in this embodiment is a method for measuring and evaluating the functional requirements of software users. It quantifies the functional requirements of software through the unit of measurement of function points (FP), which is similar to square meters or kilograms in the physical world. The advantage of this measurement method is that when different people count the function points of the same software requirement, they can get highly consistent results, and the error is usually controlled within ±5%.
[0033] Function point analysis is a basic measurement and evaluation unit that makes it possible to quantitatively evaluate the scale, performance and quality of software. By establishing a measurement and evaluation system based on functional scale, it is possible to carry out estimation work quantitatively and track changes in requirements, completion progress and quality during the development life cycle. This method realizes a closed loop of project management that is predictable beforehand, controllable during the process and improveable afterward.
[0034] In the above step 1), the software to be evaluated is decomposed into multiple function points according to the estimated functions, including the following steps:
[0035] 1.1) In the early stages of the project, a preliminary estimate of the software size is made to obtain the estimated function points;
[0036] 1.2) Clarify the project requirements based on the estimated function points, and decompose the software into multiple function points based on the requirements.
[0037] In this embodiment, the measurement of function points is based on multiple common measurement elements, including: data groups, data items, external inputs, external outputs, external queries, and external reports; these measurement elements are counted and weighted to estimate the overall function points of the software.
[0038] After the function point count is completed, the workload of software development can be estimated through some benchmark data and estimation models. These benchmark data are usually derived from historical project data, which can provide the average time consumption rate of different types of software function points. For example, the function point of an internal logic file may require a certain number of man-hours to implement, and this time consumption rate will vary depending on the complexity of the file.
[0039] In this embodiment, the international standard function point method is used to count the function points.
[0040] In the above step 2), the benchmark data is obtained through historical project data, and the overall function points are used to estimate the software workload through the benchmark data and the estimation model, specifically:
[0041] Obtain benchmark data from historical project data, obtain the average time consumption rate of software function points through the benchmark data, and estimate the software workload based on the average time consumption rate.
[0042] In the above step 2), an adjustment factor is introduced to adjust the estimated value of the workload, specifically:
[0043] The adjustment factor takes project factors into account. According to the amount of data that the project needs to process, the estimated value of the workload is adjusted through the adjustment factor. The adjustment factor is the scale range change factor.
[0044] In this embodiment, in order to improve the accuracy of the estimate, the function point analysis method also introduces a series of adjustment factors. These adjustment factors take into account project-specific factors, such as the scale of the project, the experience of the development team, the quality requirements of the software, etc. For example, if a project needs to process a large amount of data, it may be necessary to introduce a scale range variation factor to adjust the workload estimate. Similarly, if the development team has rich experience, the development efficiency may be higher, which will affect the workload estimate.
[0045] The application of function point analysis is not limited to workload and cost estimation. It can also help project managers develop more accurate project plans and monitor project progress and quality through the measurement of function points. In addition, function point analysis can also be used for software maintenance and upgrades to evaluate the evolution of software by tracking changes in function points.
[0046] In addition to being used for cost assessment, function point size is also a very basic metric evaluation element, which is the basis for quantitative evaluation of scale, efficiency, and quality. By establishing a metric evaluation system based on functional size, it is possible to carry out estimation work quantitatively and track changes in requirements, completion progress, quality status, etc. throughout the development life cycle, and ultimately achieve a management closed loop that is predictable beforehand, controllable during the process, and improveable afterward.
[0047] In this embodiment, three application scenarios of the standard function point method are provided to adapt to software development projects at different stages and different levels of detail of requirements, including:
[0048] (1) Estimated function points: The estimated function point method is particularly important in the early stages of a project when the team needs to quickly make a preliminary estimate of the software scale in order to formulate a budget or participate in a bidding process. This method is particularly suitable for situations where the project details are not yet fully understood. It uses a simplified calculation formula to quickly provide a rough estimate. For example, when the project team only has limited information, such as the number of internal logic files and external interface files, this formula can be used to quickly calculate the number of function points in order to gain a preliminary understanding of the project scale. This not only improves the efficiency of the estimate, but also provides basic data support for subsequent project planning and decision-making.
[0049] (2) Estimating function points: As the project develops and requirements become clearer, the project team often needs a more accurate function point estimate than the initial estimate. At this time, a more comprehensive method for estimating function points becomes a more appropriate choice. This method not only considers internal logic and external interfaces, but also covers multiple components such as external input, external output, and external query. By using slightly more complex calculation formulas—although these formulas are still based on assumptions of medium complexity—it can provide medium-precision estimates. This method is particularly suitable for situations where the requirements are relatively clear but the project team is unwilling to invest a lot of time and resources in detailed analysis, ensuring that the accuracy of the estimate is improved while maintaining efficiency.
[0050] (3) Detailed Function Points: During the detailed design or development phase of a project, the requirements have become very clear and the project team needs to make accurate cost and time estimates. The detailed function point method is particularly critical. This method requires an in-depth analysis of the complexity of all basic functional components and accurately allocates function points based on the actual complexity of each component. This method is particularly suitable for large-scale or extremely complex projects, where the success of the project is extremely dependent on accurate estimation results. Through the detailed function point method, the project team can make a detailed assessment of the complexity of each component and calculate a very accurate total number of function points. This not only provides solid data support for project cost and time management, but also ensures the scientific nature of resource allocation and the reliability of project plans, greatly improving the sophistication and success rate of project management.
[0051] In summary, when the present invention is used, it can evaluate the workload and cost of software development, standardize the software cost measurement process, and quantify the evaluation results. With the continuous expansion and deepening of the function point method in practical applications, cost estimation has been achieved in new projects and continuous improvement projects using the function point method, achieving compliance, scientificity, standardization and traceability of compliant, scientific, standardized and traceable software cost evaluation.
[0052] Among them, compliance is to add a cost assessment sub-process to the existing process and clarify the responsibilities and division of labor of each role in the process. Second, clarify the specific method of assessment. Formulate relevant requirements to clarify the assessment methods of different types of projects, the assessment information transmission process, the assessment report template, submission, confirmation, review and release process, etc. Third, clarify the process of indicator data release, adjustment and modification. Scientificity, first, the international standard function point method (NESMA) can be used to count the main functions of common systems; second, for some special scenarios, the function point counting rules can be adjusted and optimized based on the function point methodology framework, combined with data analysis and verification, to ensure its scientificity and applicability. Standardize the assessment process and clarify the setting principles of the assessment model and adjustment factors. The assessment of all projects is carried out in accordance with established principles and models to calculate the workload and costs. Traceability is mainly reflected in the formation of important organizational process assets. Such as assessment results (drafts, assessment reports) and demand documents as input, function point rule adjustment and optimization query manuals, indicator data and usage guidelines, etc.
[0053] The present invention significantly improves the efficiency and accuracy of software function and cost evaluation and audit, and improves the management and utilization efficiency of data assets. The application of the function point method not only optimizes the operation and decision-making process, but also promotes the modernization of technology and management of the entire industry. By comprehensively applying the function point method, unifying software cost measurement standards, standardizing software cost evaluation and audit processes, and using advanced technology to achieve artificial intelligence-assisted software cost estimation and auditing, it ensures that the software cost measurement results are standardized, accurate and consistent under the premise of complying with national / industry standards, and improves the management capabilities of the entire group's software R&D costs.
[0054] Furthermore, through the function point method and artificial intelligence-assisted software cost estimation and auditing tools, daily software cost measurement work can be implemented to achieve online software cost evaluation and audit. Evaluators and auditors do not need to manually switch offline and compare multiple documents of software requirements and evaluation results one by one. At the same time, the intelligent auxiliary model supports the rapid provision of intelligent results, which provides important reference for manual evaluation and audit, greatly improving the quality and efficiency of cost measurement, facilitating rapid consensus on software costs and reducing communication costs.
[0055] Furthermore, the utilization rate of software cost measurement and evaluation data assets can be improved. Through platform-based management of software cost measurement and evaluation data, a closed loop of information-based software cost measurement data management can be formed, making it possible to further utilize and analyze the data in the software cost measurement and evaluation link and the audit link, thus realizing the continuous accumulation and use of data assets.
[0056] In one embodiment of the present invention, a software function requirement evaluation system based on function points is provided, which includes:
[0057] Function point estimation module, which decomposes the software to be evaluated into multiple function points according to the estimated functions, so as to estimate the overall function points of the software;
[0058] The workload estimation module obtains benchmark data through historical project data, estimates the workload of the software by using the overall function points through the benchmark data and the estimation model, and introduces adjustment factors to adjust the estimated value of the workload;
[0059] The software progress and quality assessment module determines the cost estimate through the workload estimate, formulates an accurate software project plan based on the cost estimate and workload estimate, and monitors the project progress and quality through the measurement of function points.
[0060] In the above embodiment, the software to be evaluated is decomposed into multiple functional points according to the estimated functions, including:
[0061] In the early stages of the project, a preliminary estimate of the software size is made to obtain the estimated function points;
[0062] Clarify the project requirements based on the estimated functional points, and decompose the software into multiple functional points based on the requirements.
[0063] In this embodiment, the measurement of function points is based on multiple common measurement elements, including: data groups, data items, external inputs, external outputs, external queries, and external reports;
[0064] These metric elements are counted and weighted to estimate the overall function points of the software.
[0065] In this embodiment, the international standard function point method is used to count the function points.
[0066] In the above embodiment, the benchmark data is obtained through historical project data, and the overall function points are used to estimate the workload of the software through the benchmark data and the estimation model, including:
[0067] Obtain benchmark data from historical project data, obtain the average time consumption rate of software function points through the benchmark data, and estimate the software workload based on the average time consumption rate.
[0068] In the above embodiment, an adjustment factor is introduced to adjust the estimated value of the workload, including:
[0069] The adjustment factor takes project factors into account. According to the amount of data that the project needs to process, the estimated value of the workload is adjusted through the adjustment factor. The adjustment factor is the scale range change factor.
[0070] The system provided in this embodiment is used to execute the above-mentioned method embodiments. Please refer to the above-mentioned embodiments for specific processes and detailed contents, which will not be repeated here.
[0071] A computing device provided in one embodiment of the present invention may be a terminal, which may include: a processor, a communications interface, a memory, a display screen, and an input device. The processor, the communications interface, and the memory communicate with each other through a communication bus. The processor is used to provide computing and control capabilities. The memory includes a non-volatile storage medium and an internal memory, wherein the non-volatile storage medium stores an operating system and a computer program, and the computer program is executed by the processor to implement the methods in the above embodiments; the internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner may be implemented through WIFI, a management network, NFC (near field communication) or other technologies. The display screen may be a liquid crystal display screen or an electronic ink display screen, and the input device may be a touch layer covered on the display screen, or a key, trackball or touchpad provided on the housing of the computing device, or an external keyboard, touchpad or mouse, etc. The processor may call the logic instructions in the memory.
[0072] In addition, the logic instructions in the above-mentioned memory can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0073] In one embodiment of the present invention, a computer program product is provided, wherein the computer program product includes a computer program stored on a non-transitory computer-readable storage medium, wherein the computer program includes program instructions. When the program instructions are executed by a computer, the computer can execute the methods provided by the above-mentioned method embodiments.
[0074] In one embodiment of the present invention, a non-transitory computer-readable storage medium is provided, wherein the non-transitory computer-readable storage medium stores server instructions, and the computer instructions enable a computer to execute the methods provided in the above embodiments.
[0075] The above embodiment provides a computer-readable storage medium, whose implementation principle and technical effect are similar to those of the above method embodiment, and will not be repeated here.
[0076] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0077] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0078] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0079] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A software functional requirement evaluation method based on function points, characterized in that: include: Decompose the software to be evaluated into multiple function points according to the estimated functions to estimate the overall function points of the software; Obtain benchmark data through historical project data, estimate the software workload by using the overall function points through the benchmark data and estimation model, and introduce adjustment factors to adjust the estimated value of the workload; Determine the cost estimate through the workload estimate, develop an accurate software project plan based on the cost estimate and workload estimate, and monitor the progress and quality of the project through the measurement of function points.
2. The software functional requirement evaluation method based on function points as claimed in claim 1, characterized in that: Decompose the software to be evaluated into multiple functional points according to the estimated functions, including: In the early stages of the project, a preliminary estimate of the software size is made to obtain the estimated function points; Clarify the project requirements based on the estimated functional points, and decompose the software into multiple functional points based on the requirements.
3. The software functional requirement evaluation method based on function points as claimed in claim 2, characterized in that: Function point measurement is based on multiple common measurement elements, including: data groups, data items, external inputs, external outputs, external queries, and external reports; These metric elements are counted and weighted to estimate the overall function points of the software.
4. The software functional requirement evaluation method based on function points as claimed in claim 2, characterized in that: The international standard function point method is used to count function points.
5. The software functional requirement evaluation method based on function points as claimed in claim 1, characterized in that: Obtain benchmark data from historical project data, and use the overall function points to estimate the software workload through the benchmark data and estimation model, including: Obtain benchmark data from historical project data, obtain the average time consumption rate of software function points through the benchmark data, and estimate the software workload based on the average time consumption rate.
6. The software functional requirement evaluation method based on function points as claimed in claim 1, characterized in that: Adjustment factors are introduced to adjust the effort estimates, including: The adjustment factor takes project factors into account. According to the amount of data that the project needs to process, the estimated value of the workload is adjusted through the adjustment factor. The adjustment factor is the scale range change factor.
7. A software functional requirement evaluation system based on function points, characterized in that: include: Function point estimation module, which decomposes the software to be evaluated into multiple function points according to the estimated functions, so as to estimate the overall function points of the software; The workload estimation module obtains benchmark data through historical project data, estimates the workload of the software by using the overall function points through the benchmark data and the estimation model, and introduces adjustment factors to adjust the estimated value of the workload; The software progress and quality assessment module determines the cost estimate through the workload estimate, formulates an accurate software project plan based on the cost estimate and workload estimate, and monitors the progress and quality of the project through the measurement of function points.
8. The software function requirement evaluation system based on function points as claimed in claim 7, characterized in that: Decompose the software to be evaluated into multiple functional points according to the estimated functions, including: In the early stages of the project, a preliminary estimate of the software size is made to obtain the estimated function points; Clarify the project requirements based on the estimated functional points, and decompose the software into multiple functional points based on the requirements.
9. A computer-readable storage medium storing one or more programs, characterized in that: The one or more programs include instructions, which, when executed by a computing device, cause the computing device to perform any one of the methods of claims 1 to 6.
10. A computing device, characterized in that include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for executing any one of the methods described in claims 1 to 6.
Citation Information
Cited By
Software credential creation adaptation workload evaluation method, system, equipment and medium
CN121705194A