CN117075851A - Software demand workload assessment method, device, computer equipment and storage medium - Google Patents
Software demand workload assessment method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN117075851A CN117075851A CN202310909836.2A CN202310909836A CN117075851A CN 117075851 A CN117075851 A CN 117075851A CN 202310909836 A CN202310909836 A CN 202310909836A CN 117075851 A CN117075851 A CN 117075851A
- Authority
- CN
- China
- Prior art keywords
- software
- target software
- type
- workload
- target
- 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 128
- 238000003860 storage Methods 0.000 title claims abstract description 9
- 238000013209 evaluation strategy Methods 0.000 claims abstract description 35
- 230000006870 function Effects 0.000 claims description 73
- 238000011156 evaluation Methods 0.000 claims description 51
- 230000008569 process Effects 0.000 claims description 51
- 238000011161 development Methods 0.000 claims description 32
- 238000006243 chemical reaction Methods 0.000 claims description 25
- 238000013075 data extraction Methods 0.000 claims description 13
- 238000012552 review Methods 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 3
- 238000013461 design Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000013515 script Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004088 simulation Methods 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000003058 natural language processing Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Physics & Mathematics (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Strategic Management (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Game Theory and Decision Science (AREA)
- Software Systems (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a software demand workload assessment method, a device, computer equipment and a storage medium, wherein the method comprises the following steps: identifying the demand category of the target software to determine the demand type corresponding to the target software; determining a target evaluation strategy corresponding to the requirement type of the target software according to the corresponding relation between the software requirement type and the evaluation strategy; and evaluating the workload of the target software by utilizing the target evaluation strategy. Therefore, the demand type corresponding to the target software is determined by identifying the demand type of the target software, and a proper evaluation strategy is selected for the demand type corresponding to the target software according to the corresponding relation between the software demand type and the evaluation strategy, so that the accuracy of the software demand workload can be improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and apparatus for evaluating software requirement workload, a computer device, and a storage medium.
Background
Software often requires an estimate of the size of the software at a pre-development stage. The size of the software directly influences the setting and management of the software development project, the size of the target software to be developed is estimated correctly, the workload is estimated according to the size of the software, and then a proper development project is formulated for the software.
In the related art, after classifying the functional points, the development amount and the workload of the functional points are calculated, and the manual intervention is required, so that the influence of artificial uncertain factors on the evaluation value can be generated, and the accuracy cannot be ensured.
Disclosure of Invention
The application provides a software demand workload assessment method, a software demand workload assessment device, computer equipment and a storage medium. The specific scheme is as follows:
in one aspect, an embodiment of the present application provides a method for evaluating software demand workload, including:
identifying the demand category of the target software to determine the demand type corresponding to the target software;
determining a target evaluation strategy corresponding to the requirement type of the target software according to the corresponding relation between the software requirement type and the evaluation strategy;
and evaluating the workload of the target software by utilizing the target evaluation strategy.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a software development class requirement type, and the workload of the target software is evaluated by using a target evaluation policy, including:
determining an execution process corresponding to a user function of the target software, and determining a function point corresponding to the execution process;
and converting the function points corresponding to the execution process to obtain the development type demand workload of the target software.
In one possible implementation manner of the embodiment of the present application, determining a function point corresponding to an execution process includes;
decomposing the execution process to obtain a plurality of sub-processes;
identifying each sub-process to determine the data movement corresponding to each sub-process;
determining a function point corresponding to each sub-process according to the data movement corresponding to each sub-process;
and determining the function points corresponding to the execution process according to the function points corresponding to the sub-processes.
In one possible implementation manner of the embodiment of the present application, converting a function point corresponding to an execution process to obtain development class requirement workload of target software includes:
obtaining the value of each conversion parameter corresponding to the target software;
and converting the function points corresponding to the execution process according to the values of the conversion parameters to obtain the development type demand workload of the target software.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a configuration class requirement type or a data extraction class requirement type, and the workload of the target software is evaluated by using a target evaluation policy, including:
and evaluating the workload of the target software by a function point method.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a user interface UI/user experience UE class requirement type, and the workload of the target software is evaluated by using a target evaluation policy, including:
and under the condition that the review operation of the target object on the UI/UE class requirement workload of the target software is detected, acquiring the UI/UE class requirement workload of the target software.
Another embodiment of the present application provides a software requirement workload assessment device, including:
the identification module is used for identifying the demand type of the target software so as to determine the corresponding demand type of the target software;
the determining module is used for determining a target evaluation strategy corresponding to the requirement type of the target software according to the corresponding relation between the software requirement type and the evaluation strategy;
and the evaluation module is used for evaluating the workload of the target software by utilizing the target evaluation strategy.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a software development type requirement type, and the evaluation module is configured to:
determining an execution process corresponding to a user function of the target software, and determining a function point corresponding to the execution process;
and converting the function points corresponding to the execution process to obtain the development type demand workload of the target software.
In one possible implementation manner of the embodiment of the present application, the evaluation module is configured to:
decomposing the execution process to obtain a plurality of sub-processes;
identifying each sub-process to determine the data movement corresponding to each sub-process;
determining a function point corresponding to each sub-process according to the data movement corresponding to each sub-process;
and determining the function points corresponding to the execution process according to the function points corresponding to the sub-processes.
In one possible implementation manner of the embodiment of the present application, the evaluation module is configured to:
obtaining the value of each conversion parameter corresponding to the target software;
and converting the function points corresponding to the execution process according to the values of the conversion parameters to obtain the development type demand workload of the target software.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a configuration type requirement type or a data extraction type requirement type, and the evaluation module is configured to:
and evaluating the workload of the target software by a function point method.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a user interface UI/user experience UE class requirement type, and the evaluation module is configured to:
and under the condition that the review operation of the target object on the UI/UE class requirement workload of the target software is detected, acquiring the UI/UE class requirement workload of the target software.
Another embodiment of the present application provides a computer device, including a processor and a memory;
wherein the processor executes a program corresponding to the executable program code by reading the executable program code stored in the memory, for implementing the software requirement workload assessment method according to the embodiment of the above aspect.
Another embodiment of the present application proposes a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the software requirement workload assessment method according to the embodiment of the above aspect.
Additional aspects and advantages of the application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the application.
Drawings
The foregoing and/or additional aspects and advantages of the application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a schematic flow chart of a software workload demand assessment method according to an embodiment of the present application;
FIG. 2 is a flowchart of another method for evaluating software workload demand according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a software workload assessment device according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative and intended to explain the present application and should not be construed as limiting the application.
The software requirement workload assessment method, apparatus, computer device and storage medium of the embodiments of the present application are described below with reference to the accompanying drawings.
Fig. 1 is a flowchart of a software requirement workload evaluation method according to an embodiment of the present application. As shown in fig. 1, the software requirement workload assessment method includes:
step 101, identifying the demand category of the target software to determine the corresponding demand type of the target software.
In the application, the software requirement can be a software development type requirement, a configuration type requirement, a data extraction type requirement, a User Interface (UI)/User body (UE) type requirement and the like. That is, the software requirement types may include, but are not limited to, a software development class requirement type, a configuration class requirement type, a data extraction class requirement type, a UI/UE class requirement type.
According to the method and the device, the demand type of the target software can be identified according to the characteristics of different demand types, and the software demand type corresponding to the target software is determined.
Optionally, a software requirement category input interface may be provided, where, when an input operation of a user software requirement type is detected, a requirement type corresponding to the target software is obtained.
In the application, the type of the requirement corresponding to the target software can be one or more, and the application is not limited to the type.
Step 102, determining a target evaluation strategy corresponding to the requirement type of the target software according to the corresponding relation between the software requirement type and the evaluation strategy.
In the application, different evaluation strategies can be adopted for different software requirement types. For example, in the software development type requirement, the user function requirement can be decomposed into a plurality of function points, and the function points can be converted into development workload. As another example, for configuration class requirement types and data extraction class requirement types, evaluation can be performed by a function point method. For another example, for the UI/UE class requirement type, the evaluation may be performed by the target object, and the evaluation result may be obtained.
According to the method and the device, the target evaluation strategy corresponding to the target software can be determined according to the requirement type corresponding to the target software and the corresponding relation between the software requirement type and the evaluation strategy.
Alternatively, if the demand type corresponding to the target software includes a plurality of demand types, a target evaluation policy corresponding to each demand type may be determined.
Optionally, if the requirements of the target software are relatively large, the related functional scale is relatively large, the requirements can be split, and each split sub-requirement is evaluated by adopting a target evaluation strategy, so that the unused evaluation requirements can be met, and the application range is wide.
And step 103, evaluating the workload of the target software by utilizing a target evaluation strategy.
After determining the target evaluation policy corresponding to the requirement type of the target software, the target evaluation policy may be adopted to evaluate the workload of the target software, so as to obtain the workload corresponding to the requirement type.
If the demand type of the target software comprises a plurality of demand types, the demand type is evaluated by adopting a corresponding evaluation strategy for each demand type.
Therefore, one or more evaluation strategies can be selected for evaluation according to different types of requirements, so that the influence of artificial uncertain factors on evaluation can be avoided, the evaluation can be more conveniently and rapidly performed, and the evaluation range of the type of the requirements is enlarged.
In the embodiment of the application, the demand type corresponding to the target software is determined by identifying the demand type of the target software, and the proper evaluation strategy is selected for the demand type corresponding to the target software according to the corresponding relation between the software demand type and the evaluation strategy, so that the accuracy of the software demand workload can be improved.
FIG. 2 is a flowchart illustrating another method for evaluating software workload demand according to an embodiment of the present application. As shown in fig. 2, the software requirement workload assessment method includes:
step 201, identifying a requirement type of the target software, and determining that a requirement type corresponding to the target software is a software development type requirement type.
In the present application, step 201 is similar to the method for determining the type of requirement corresponding to the target software described in the above embodiment, and thus will not be described herein.
In the application, the demand type of the target software is identified, and the demand type corresponding to the target software is determined to be the software development type demand type.
Step 202, determining a target evaluation strategy corresponding to the software development type demand according to the corresponding relation between the software demand type and the evaluation strategy.
In the present application, according to the software development type requirement and the correspondence between the software requirement type and the evaluation policy, it can be determined that the objective evaluation policy corresponding to the software development type requirement is a manner of decomposing the user function requirement into a plurality of function points and converting the function points into development workload, and the specific process is as follows in steps 203 to 204.
Step 203, determining an execution process corresponding to the user function of the target software, and determining a function point corresponding to the execution process.
In the application, the user function requirement of the target software can be analyzed, the execution process of the user function of the target software is determined, the execution process is analyzed, and the function point corresponding to the execution process is determined.
As an implementation manner, the executing process may be decomposed to obtain a plurality of sub-processes, and each sub-process is identified to determine data movement corresponding to each sub-process, and according to the data movement corresponding to each sub-process, determine a function point corresponding to each sub-process, and then determine a sum of the function points corresponding to the plurality of sub-processes as a function point corresponding to the executing process.
Wherein the data movement type may include, but is not limited to, input, output, read, write, etc., and a data movement may be denoted as a function point.
And 204, converting the function points corresponding to the execution process to obtain the development type demand workload of the target software.
In the application, the function points corresponding to the execution process can be converted into the workload according to the conversion relation between the function points and the workload, and the workload is the workload required by the development class of the target software.
As an implementation manner, the conversion relation between the function point and the workload may include conversion parameters, and the values of the conversion parameters corresponding to different software may be different. Therefore, the values of the conversion parameters corresponding to the target software can be obtained, and the functional points corresponding to the execution process are converted according to the values of the conversion parameters, so that the development type demand workload of the target software is obtained.
For example, the conversion relation between the function points and the workload can be expressed by a conversion formula, and the values of the conversion parameters corresponding to the target software and the function points corresponding to the execution process can be substituted into the conversion formula to calculate, so that the development type demand workload of the target software can be obtained.
In the present application, the conversion parameters may include, but are not limited to: application type parameters, quality and characteristic parameters, development language parameters, development team background parameters, software scale change factor parameters and integrity level adjustment factor parameters.
Wherein the application type parameters include:
and (3) business processing: business management and business processing software such as OA, official document, personnel, accounting, company, sales and the like;
science and technology, application integration: scientific computing, simulation, blank form program, statistics, CAE (computer aided engineering) and other enterprise service buses, application integration and the like;
multimedia: icons, images, sounds, etc., multimedia application fields, geographic information systems, educational and entertainment applications, etc.;
intelligent information: natural language processing, artificial intelligence, expert systems, etc.;
the system comprises: operating systems, database systems, integrated development environments, automated development/design tools, etc.;
communication control: communication protocols, simulations, switch software, global positioning systems, etc.;
and (3) flow control: production management, instrument control, robot control, real-time control, embedded software, etc.
The quality and characteristic parameters may include:
performance efficiency criterion: there is no explicit requirement for performance efficiency; to meet performance efficiency requirements, the design phase is required to begin performance efficiency analysis, or analysis tools are used in the design and development phases.
Compatibility judgment criteria: there is no explicit requirement for compatibility; the operational requirements of different hardware or software environments at different sites need to be considered during the design phase.
Reliability judgment criteria: there is no explicit requirement for reliability; causing economic loss or life hazard when faults occur.
Portability criterion: there is no explicit requirement for portability; when conditions change, the program can run without much modification.
Development team background parameters may include:
similar projects were developed for this line;
similar software has been developed for other industries, or different but related software has been developed for the industry;
there is no background of the same kind of items.
The software scale change factor parameters include: rectifying, approximating, budgeting and settling.
The integrity level adjustment factor parameters include: four risk classes, class a to class D, where class a is highest and class D is smallest.
When each parameter of the target software is obtained, the value of each conversion parameter can be determined according to the information related to the development of the target software. For example, different application types have corresponding application type parameter values, and the application type parameter values corresponding to the target application types can be determined according to the target application types to which the target software belongs.
In the present application, the values of the conversion parameters may be adjusted as needed.
In order to further improve accuracy of development type demand workload of the target software, multiple review experts can evaluate the development type demand workload obtained through conversion, weight is carried out according to evaluation results of the multiple review experts, and a weighted result is used as final development type demand workload of the target software.
In the embodiment of the application, the demand type of the target software is identified, the demand type corresponding to the target software is determined to be the software development type demand type, the target evaluation strategy corresponding to the software development type demand type is determined according to the corresponding relation between the software demand type and the evaluation strategy, the execution process corresponding to the user function of the target software is determined, the functional point corresponding to the execution process is determined, and the functional point corresponding to the execution process is converted to obtain the development type demand workload of the target software. Therefore, when the requirement type corresponding to the target software is the software development type requirement type, the user function of the target software can be decomposed into function points, and the function points are converted into workload.
In one embodiment of the application, the demand type of the target software is identified, the demand type corresponding to the target software is determined, and if the demand type corresponding to the target software is a configuration type demand type or a data extraction type demand type, the workload of the target software can be evaluated by a function point method.
By way of example, the configuration class requirements may include configuration requirements of the host, configuration requirements of the database, script review requirements, and the like.
Taking script review requirements as an example, scripts are usually multi-line, different line number ranges have corresponding workload, different interval ranges have corresponding workload, and for example, workload below 10 lines is a simple requirement
In addition, for a workflow, the workload of the workflow can be determined according to how many nodes and how many branches the workflow has.
In the application, the data extraction type requirements can comprise the extraction requirements of the precisely-divided ETL data, the grade difficulty can be divided for the data extraction type requirements, the different grade difficulty has corresponding workload, and the workload of the target software can be determined according to the grade of the data extraction type requirements. The ETL may refer to a process of loading data of the service system into the data warehouse after extraction and cleaning conversion.
In one embodiment of the application, the demand category of the target software is identified, the demand type corresponding to the target software is determined, if the demand type corresponding to the target software is the UI/UE class demand type, the target object can evaluate the UI/UE class demand workload of the target software, and when the evaluation operation of the target object on the UI/UE class demand workload of the target software is detected, the UI/UE class demand workload of the target software can be obtained. For example, when the requirement type of the target software is the UI/UE class requirement type, the review expert may review the UI/UE class requirement workload of the target software to obtain the workload of the UI/UE class requirement.
In the application, the software requirements can be divided into four types of software development type requirements, configuration type requirements, data extraction type requirements and UI/UE type requirements, and the problems that different types of requirements need to be independently evaluated by adopting different evaluation methods and cannot be completed by a model can be solved by adopting the combination of a general software measurement international alliance (Common Software Measurement International Consortium, COSIC) method, a function point method and an expert evaluation method and selecting the best one or more of the methods according to different types of requirements. Therefore, the influence of artificial uncertain factors on the evaluation can be avoided, the evaluation can be more conveniently and rapidly performed, and the evaluation range of the demand type is enlarged.
The software demand workload assessment method can assess the workload of various demands in the software development process, and by identifying the type of the software demand, the corresponding appropriate assessment method is selected, so that the accuracy of the software demand workload is improved, the assessed workload is adapted to be optimal, thereby reducing complicated working assessment steps, and the method is used for quantifying the functional points of the software, finally obtaining the numerical value representing the size of the software, and the method is suitable for any stage of the software development.
In order to achieve the above embodiment, the embodiment of the present application further provides a software requirement workload assessment device. Fig. 3 is a schematic structural diagram of a software workload assessment device according to an embodiment of the present application.
As shown in fig. 3, the software demand workload assessment apparatus 300 includes:
the identifying module 310 is configured to identify a requirement type of the target software, so as to determine a requirement type corresponding to the target software;
a determining module 320, configured to determine a target evaluation policy corresponding to the requirement type of the target software according to a correspondence between the requirement type of the software and the evaluation policy;
and the evaluation module 330 is used for evaluating the workload of the target software by utilizing the target evaluation strategy.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a software development type requirement type, and the evaluation module 330 is configured to:
determining an execution process corresponding to a user function of the target software, and determining a function point corresponding to the execution process;
and converting the function points corresponding to the execution process to obtain the development type demand workload of the target software.
In one possible implementation manner of the embodiment of the present application, the evaluation module 330 is configured to:
decomposing the execution process to obtain a plurality of sub-processes;
identifying each sub-process to determine the data movement corresponding to each sub-process;
determining a function point corresponding to each sub-process according to the data movement corresponding to each sub-process;
and determining the function points corresponding to the execution process according to the function points corresponding to the sub-processes.
In one possible implementation manner of the embodiment of the present application, the evaluation module 330 is configured to:
obtaining the value of each conversion parameter corresponding to the target software;
and converting the function points corresponding to the execution process according to the values of the conversion parameters to obtain the development type demand workload of the target software.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a configuration class requirement type or a data extraction class requirement type, and the evaluation module 330 is configured to:
and evaluating the workload of the target software by a function point method.
In one possible implementation manner of the embodiment of the present application, the requirement type corresponding to the target software is a user interface UI/user experience UE class requirement type, and the evaluation module 330 is configured to:
and under the condition that the review operation of the target object on the UI/UE class requirement workload of the target software is detected, acquiring the UI/UE class requirement workload of the target software.
It should be noted that the explanation of the embodiment of the software requirement workload evaluation method is also applicable to the software requirement workload evaluation device of the embodiment, so that the explanation is omitted here.
In the embodiment of the application, the demand type corresponding to the target software is determined by identifying the demand type of the target software, and the proper evaluation strategy is selected for the demand type corresponding to the target software according to the corresponding relation between the software demand type and the evaluation strategy, so that the accuracy of the software demand workload can be improved.
In order to implement the above embodiments, the embodiments of the present application further provide a computer device, including a processor and a memory;
wherein the processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, for implementing the software requirement workload evaluation method as described in the above embodiment.
In order to implement the above-described embodiments, the embodiments of the present application also provide a non-transitory computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the software requirement workload assessment method as described in the above-described embodiments.
In the description of this specification, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "plurality" means at least two, for example, two, three, etc., unless specifically defined otherwise.
While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.
Claims (14)
1. A software demand workload assessment method, comprising:
identifying the demand category of the target software to determine the demand type corresponding to the target software;
determining a target evaluation strategy corresponding to the requirement type of the target software according to the corresponding relation between the software requirement type and the evaluation strategy;
and evaluating the workload of the target software by utilizing the target evaluation strategy.
2. The method of claim 1, wherein the type of requirement corresponding to the target software is a software development class requirement type, and the evaluating the workload of the target software using the target evaluation policy comprises:
determining an execution process corresponding to a user function of the target software, and determining a function point corresponding to the execution process;
and converting the function points corresponding to the execution process to obtain the development type demand workload of the target software.
3. The method of claim 2, wherein the determining the function point corresponding to the execution process includes;
decomposing the execution process to obtain a plurality of sub-processes;
identifying each sub-process to determine the data movement corresponding to each sub-process;
determining a function point corresponding to each sub-process according to the data movement corresponding to each sub-process;
and determining the function points corresponding to the execution process according to the function points corresponding to the sub-processes respectively.
4. The method of claim 2, wherein the converting the function point corresponding to the execution process to obtain the development class requirement workload of the target software includes:
obtaining the value of each conversion parameter corresponding to the target software;
and converting the function points corresponding to the execution process according to the values of the conversion parameters to obtain the development type demand workload of the target software.
5. The method of claim 1, wherein the requirement type corresponding to the target software is a configuration class requirement type or a data extraction class requirement type, and the evaluating the workload of the target software using the target evaluation policy comprises:
and evaluating the workload of the target software by a function point method.
6. The method of claim 1, wherein the type of requirement corresponding to the target software is a user interface UI/user experience UE class requirement type, and wherein the evaluating the workload of the target software using the target evaluation policy comprises:
and under the condition that the review operation of the target object on the UI/UE class requirement workload of the target software is detected, acquiring the UI/UE class requirement workload of the target software.
7. A software demand workload assessment apparatus, comprising:
the identification module is used for identifying the demand type of the target software so as to determine the demand type corresponding to the target software;
the determining module is used for determining a target evaluation strategy corresponding to the requirement type of the target software according to the corresponding relation between the software requirement type and the evaluation strategy;
and the evaluation module is used for evaluating the workload of the target software by utilizing the target evaluation strategy.
8. The apparatus of claim 7, wherein the requirement type corresponding to the target software is a software development class requirement type, and the evaluation module is configured to:
determining an execution process corresponding to a user function of the target software, and determining a function point corresponding to the execution process;
and converting the function points corresponding to the execution process to obtain the development type demand workload of the target software.
9. The apparatus of claim 8, wherein the evaluation module is to:
decomposing the execution process to obtain a plurality of sub-processes;
identifying each sub-process to determine the data movement corresponding to each sub-process;
determining a function point corresponding to each sub-process according to the data movement corresponding to each sub-process;
and determining the function points corresponding to the execution process according to the function points corresponding to the sub-processes respectively.
10. The apparatus of claim 8, wherein the evaluation module is to:
obtaining the value of each conversion parameter corresponding to the target software;
and converting the function points corresponding to the execution process according to the values of the conversion parameters to obtain the development type demand workload of the target software.
11. The apparatus of claim 7, wherein the requirement type corresponding to the target software is a configuration class requirement type or a data extraction class requirement type, and the evaluation module is configured to:
and evaluating the workload of the target software by a function point method.
12. The apparatus of claim 7, wherein the type of requirement corresponding to the target software is a user interface UI/user experience UE class requirement type, and the evaluation module is configured to:
and under the condition that the review operation of the target object on the UI/UE class requirement workload of the target software is detected, acquiring the UI/UE class requirement workload of the target software.
13. A computer device comprising a processor and a memory;
wherein the processor runs a program corresponding to executable program code stored in the memory by reading the executable program code for implementing the method according to any one of claims 1-6.
14. A non-transitory computer readable storage medium, on which a computer program is stored, characterized in that the program, when executed by a processor, implements the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310909836.2A CN117075851A (en) | 2023-07-20 | 2023-07-20 | Software demand workload assessment method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310909836.2A CN117075851A (en) | 2023-07-20 | 2023-07-20 | Software demand workload assessment method, device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117075851A true CN117075851A (en) | 2023-11-17 |
Family
ID=88708837
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310909836.2A Pending CN117075851A (en) | 2023-07-20 | 2023-07-20 | Software demand workload assessment method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117075851A (en) |
-
2023
- 2023-07-20 CN CN202310909836.2A patent/CN117075851A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8479165B1 (en) | System for testing operation of software | |
| CN110554958B (en) | Graph database testing method, system, device and storage medium | |
| JPWO2003069466A1 (en) | Software component importance assessment system | |
| CN113537797A (en) | Method and device for intelligent test workload assessment based on historical data analysis, terminal equipment and storage medium | |
| CN115600891B (en) | Big data analysis method and system applied to production monitoring of aqueous acrylic resin | |
| Zhang et al. | A generic data analytics system for manufacturing production | |
| Westermann et al. | Efficient experiment selection in automated software performance evaluations | |
| CN111159241A (en) | Click conversion estimation method and device | |
| CN112860736A (en) | Big data query optimization method and device and readable storage medium | |
| CN112433942A (en) | Software automation testing method, device and system based on artificial intelligence model | |
| CN117075851A (en) | Software demand workload assessment method, device, computer equipment and storage medium | |
| CN115359203A (en) | Three-dimensional high-precision map generation method and system and cloud platform | |
| CN114493317A (en) | Intelligent acquisition and evaluation method and system based on enterprise environment | |
| US20200409817A1 (en) | Method and apparatus for evaluating and selecting signal comparison metrics | |
| CN114626545A (en) | Data preparation for artificial intelligence models | |
| CN114020642A (en) | Big data task testing method and device, storage medium and electronic equipment | |
| Bause et al. | ProFiDo–a toolkit for fitting input models | |
| CN112527631A (en) | bug positioning method, system, electronic equipment and storage medium | |
| CN113590458A (en) | Method and device for checking a technical system | |
| Polter et al. | A generic workflow engine for iterative, simulation-based non-linear system identifications | |
| JP6707215B1 (en) | Engineering tools, learning devices, and data acquisition systems | |
| Galyean | Orthogonal PSF taxonomy for human reliability analysis | |
| EP4345610A1 (en) | A method for estimating a potential replacement of at least one hand-coded function in a program code with a machine learning algorithm, computer program product, computer-readable storage medium as well as an electronic computing device | |
| Gustafsson et al. | A Strategy for Cross-Project Defect Prediction Models in Industry | |
| CN117971679A (en) | Intelligent contract test data generation method, device, equipment and storage medium |
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 |