A model for estimating the cost of a software development project

The estimation method of the commonly used software cost estimation model proposes a new cost estimation model for web system software development projects, the man-day evaluation model, which is put aside. In the actual development process, software development projects are divided into core and non-core parts. The core part is mainly the business model that changes greatly with the projectRecommend caj** ...

The Delphi method (expert) or the international function point estimation method can be used. If you use the Delphi method, the approximate steps are as follows: 1. First estimate the workload according to WBS (work task decomposition) (man-days) 2. Then use the workload * cost per person per day to get the personnel cost 3. Use the personnel cost + other costs (rent, water and electricity allocation, transportation costs, ** fees, etc.) If you use the international function point estimation method, the approximate steps are as follows::

1. Calculate the scale of the software first (that is, the number of function points) 2. Use the function points * productivity workload (man-days) 3. Then use the workload * the cost per person per day to get the personnel cost 4, the cost of personnel + other costs (rent, water and electricity, transportation, ** fee, etc.).

Today, we will analyze this problem in detail, please read on.

When estimating the development cost of a software project, it should include the sum of the resources spent from the inception of the project to the end of the project's R&D activities, and can be estimated or measured by phase.

The process of software cost estimation can be divided into four processes: estimating the scale, estimating the workload, estimating the duration and estimating the cost, and finally determine the software cost. Among them, the cost estimation needs to estimate the direct labor cost, indirect labor cost, indirect non-labor cost and direct non-labor cost separately.

1. Estimate the scale.

Typically, an estimate of software sizing is the starting point of the software cost estimation process. Estimating the size is the main basis for the subsequent calculation of the workload, cost and schedule of the software project, and is the key to project scope management.

When estimating, the project requirements and system boundaries should be clarified based on the feasibility study report or similar documents. The choice of estimation method is based on the characteristics of the project and the level of detail of the requirements.

If the requirements of the current project are uncertain, you can skip this part and move on to the next step.

2. Estimate the workload.

Software project workload estimation can be based on equations, analogies, and analogies.

Analogy: When the software project requirements are extremely vague or uncertain, if there are highly similar historical projects, this method can be used to use historical project data to roughly estimate the workload.

Analogy: When the requirements of a software project are extremely vague or uncertain, if there is a set of benchmark data that is similar to some of the attributes of the project, the analogy method can be used to use the benchmark data to roughly estimate the workload.

Equation method: For projects that have been sized, the equation method can be used to determine the workload of the project to be estimated through various parameters.

Both estimation methods should be used to cross-validate the estimation results in order to pursue the accuracy of the estimation. The estimate of the effort is a range, not a single value.

3. Estimate the construction period.

The estimation of the duration of a software project can also be based on analogy, analogy and equations.

4. Estimate the cost.

Analogy and analogy are equally applicable to cost estimation when the demand period is ambiguous or uncertain.

Cost estimates are typically a range.

After obtaining the workload and duration, the scientific method is used to estimate the cost. As an authorized partner of Beijing Software Cost Evaluation Technology Innovation Alliance, CEUNION adopts the rapid function point method for cost estimation when estimating software costs.

Developers' salaries, servers, domain names, a lot.

Developers' salaries, servers, domain names, whatever.

The cost of a software development project is calculated from the following four aspects:

1. Developer's salary: The basis of the outsourcing project is the developer's salary, which is determined by the working years, experience and level. Developers include product managers, UI designers, front-end engineers, server-side engineers, client engineers, etc., and different outsourcing projects require different developers.

2. Time cost: In the process of software development, the output of deliverables mainly depends on programmers, and programmers consume the highest cost. The longer a programmer writes **, the higher the cost, and software costs are often estimated on a daily basis.

3. Identify activities and decompose work costs: After the software is started and developed, conduct requirements analysis, write requirements specifications, requirements review, testing and other activities. In the early stage of the project, it is necessary to identify the relevant activity items of software development and perform a work breakdown to determine the dependencies of each activity item.

4. Estimate the role and number of personnel: After the activity items are determined, evaluate the resources required for the implementation of the activity items one by one, evaluate the required personnel according to the deliverables, and develop the corresponding software. Each software requires different skills, roles and levels.

There are several ways to estimate the cost of a software project:

1.Expert judgment method: Experienced technicians or managers estimate the project cost through subjective judgment based on past experience in dismantling and similar projects, combined with demand analysis, technical solutions, etc.

2.Function point estimation method: The success and loss of the project are calculated by quantitatively estimating the function points implemented in the software project, including the complexity of the function points, the difficulty of implementation, and the workload.

3.Parametric model method: decompose the cost of a software project into multiple parameters, such as the number of lines, development workload, test workload, etc., and then estimate it based on historical data and statistical models.

4.Analogue estimation method: Estimate according to the cost data and project characteristics of similar projects that have been completed, and obtain a more accurate cost estimate through comparison and adjustment.

It should be noted that different estimation methods are suitable for different types of software projects, and the estimation of sales also needs to take into account the influence of other factors, such as personnel quality, technical difficulty, schedule management, etc. Questions related to corporate value or company asset valuation can be answered as a nod to the question.

When estimating the cost of a software project, in addition to using the common formula of cost estimation, we should also understand the composition and meaning of software cost, which is more helpful for us to systematically understand the content and process of software cost estimation.

Software costs include both direct and indirect costs. According to the characteristics of the software industry, direct costs are divided into direct labor costs and direct non-labor costs, while indirect costs are divided into indirect labor costs and indirect non-labor costs.

The so-called direct costs are the costs that occur when the project exists, and the costs that no longer occur when the project is canceled. For example, the human resources cost (direct labor cost) of the project members, the travel (direct non-labor cost) and training (non-labor cost of direct dispatch) incurred due to the needs of the project.

Indirect costs, on the other hand, are the joint costs of servicing all R&D projects of the Organization, i.e. they will be incurred whenever there are R&D activities, and the costs will not be incurred if all R&D activities are cancelled. For example, the cost sharing of R&D management personnel (indirect labor costs) and the cost sharing of R&D equipment sites (indirect non-labor costs).

The direct labor cost is calculated based on the workload estimation results (usually per person-month) and the average labor cost rate (i.e., how much per person per month), and the labor cost rate can refer to the benchmark data of China's software industry released by the Beijing Software Cost Evaluation Technology Innovation Alliance; Indirect costs are usually apportioned according to the number and duration of the project team, and are therefore also related to the workload; Direct non-labor costs usually account for a small proportion of software projects, and this part has nothing to do with the workload, and can be estimated by referring to the detailed division of direct non-labor costs in the "Specification" (including office expenses, travel expenses, training expenses, operating expenses, procurement costs and other six items).

Therefore, when estimating the cost of a software project, our commonly used software cost estimation formula is: software cost = workload average labor cost rate (including direct labor cost and indirect cost) + direct non-labor cost. This formula basically contains the content and process of software cost estimation.