How to price software development?

How to calculate the working hours of software development, how to quote, the calculation method of quotation for customized development of software system, and the standard of working hours and expenses of software development.

1. software development to do software ((call. Hebei L58 l58-ll33-4744)) Price estimation method

The price of software development is related to workload, business cost, national tax and enterprise profit. In order to facilitate the calculation, the calculation formula is given:

Software development price = development workload × development cost/person/month

1. 1 develop software ((call. Ji L58 l58-ll33-4744)) Workload

The workload of software development is related to the empirical value of estimated workload, risk coefficient and reuse coefficient:

Software development workload = expected workload experience value × risk coefficient × reuse coefficient

1. 1. 1 empirical value of estimated workload (denoted by a)

Some people propose to calculate the workload of software development by the number of lines of source code or function points, but these methods are difficult to realize. At present, the international calculation is still based on past experience, and domestic software companies also use experience to estimate workload.

In order to standardize the estimation method better, it is suggested that the workload can be calculated according to the activities in the software development process specified in the national standard GB/T 8566-200 1 Software Life Cycle Process.

The calculation of workload is based on the workload that a developer can complete in one month (calendar month, including national holidays), which is commonly called "person month".

In particular, the process of software development includes not only the usual software development, but also various software testing activities.

1. 1.2 risk coefficient (expressed in σ)

Estimating the empirical value of workload is also very risky, and there are many factors that cause software crisis, which is also a factor. Especially when software enterprises are unfamiliar with the business fields of information engineering projects, and users can't or can't fully express their real needs, software enterprises need to constantly improve the requirements acquisition and modify the design. Therefore:

L ≤ Risk coefficient ≤ 1.5

According to our understanding of software enterprises, it is unacceptable to exceed half of the estimated workload experience value, so we determine "1.5" as the limit value. Of course, this depends on both the ability of the enterprise and the acceptance of users.

1. 1.3 multiplexing coefficient (expressed in τ)

The empirical value of estimating workload is estimated by the software enterprise undertaking the general project, but if the software enterprise adopts the "component-based development method"

, and established a reusable component library (core asset library), or some existing software products, only secondary development, thus reducing the workload of software development. Therefore:

0.25 ≤ Multiplexing coefficient ≤ 1

According to the empirical data of domestic and foreign software enterprises in implementing component-based development method (software product line), the work efficiency is improved to 25% (the highest value).

1.2 development cost/person/month

Business cost, national tax, enterprise profit, management cost and quality cost of software enterprises. Can be distributed to all software developers.

Development cost/person/month =(P+Q+R)× S× τ

1.2. 1 P (head fee)

Headcount expenses mainly include employees' salaries, bonuses and various expenses calculated by people as stipulated by the state. Its total business cost in software enterprises accounts for 70%-80%.

P = B × 1.476

7% national provident fund, 12% medical insurance, 22% pension and unemployment benefits.

2% (that is, the so-called four funds), in addition to 0.5% work injury deposit, 0.5% maternity deposit, 1.6% disability fund, 2% trade union fund, totaling 47.6%.

B is the average wage, that is, the sum of wages, bonuses and material rewards paid by enterprises to employees, divided by the number of employees in enterprises, and apportioned to each month.

1.2.2 Q (office expenses)

Office expenses include office rental fees, property management fees, communication fees, office consumables, water, electricity and air conditioning fees, equipment depreciation fees, travel expenses, and expenses paid by enterprises for on-the-job training of employees. The total business expenses in software enterprises account for 20%-30%.

Q = B/3

The office expenses here are calculated at 25% of the business expenses.

1.2.3 R (national tax and corporate profits)

Because the state implements the preferential policies for developing the software industry, the calculation is not listed separately, but software enterprises still have the obligation to pay state taxes, which can be considered together with enterprise profits.

In addition, it is impossible for employees of software enterprises to work at full capacity all year round. Even if they work twelve months a year, they still need to take time out for on-the-job training and pre-job training for promotion. As far as we know, employees of software enterprises can spend 10 months a year.

1 1 month is also normal.

R = B/3

The following are our suggestions, and each software enterprise can make changes according to the situation.

1.2.4 S (management coefficient)

Usually every organization will have a certain proportion of managers. Referring to the practice of some organizations, there are two managers for every ten software personnel, that is, management fees:

1 ≤ S ≤ 1.2

1.2.5 T (quality coefficient)

To improve software quality, there must be some expenses, that is, quality cost, which is different for different software enterprises.

Software enterprises, like other enterprises, also have many factors, such as honesty and brand, which increase their expenses.

At present, we can determine it according to ISO9000 quality system certification and CMM or CMMI certification, and the values are 1.05, 1. 1. 1.2 respectively.

In the future, it is suggested that the qualification of software enterprises should be divided into four levels. It is determined by the software industry association according to various factors such as CMMI certification, brand and integrity. The construction of this system needs further exploration.

Accordingly, we synthesize the above points:

Development cost/person/month = (b×1.476+b/3+b/3) × l.2× t.

= B×( 1.476+2/3)× 1.2×T

= B × 2 .575 × T

= B × λ

When T= 1.05, λ=2.7.

When T= 1.2, λ=3.09.

Therefore, 2.7 ≤ λ ≤ 3.09.

For undertaking foreign software outsourcing business, on the one hand, employees' wages are high, on the other hand, it is difficult to work at full capacity, so this proposal is R=B/2. therefore

Development cost/person/month = b (1.476+1/3+1/2) ×1.2× t.

= B × 2.767 × T

= B × λ

When T= 1.05, λ=2.906.

When T= 1.2, λ=3.32.

Therefore, 2.9 ≤ λ ≤ 3.32.

Conclusion:

Software development price = A × σ × τ × B × λ

Answer: Estimate the empirical value of workload.

B: Average salary of software enterprises/person/month.

Q: risk coefficient l ≤ Q ≤ 1.5.

T: the multiplexing coefficient is 0.25 ≤ τ ≤ 1.

λ: the comprehensive coefficient is 2.7 ≤ λ ≤ 3.09.

2. Software (system) maintenance cost price estimation method

Within one year after the confidence engineering system integration and application software development are completed and delivered to users for formal operation, the software (system) will provide free maintenance service for one year.

After one year of official operation, software enterprises should sign software (system) maintenance contracts with users. This contract is a technology transfer contract or a technology development contract.

According to different user needs, software (system) maintenance can be divided into four levels.

2. 1 A level

Software companies send technicians to resident users to solve problems in daily operations.

2. 1. 1 U (system construction investment)

Users need the system maintained by software enterprises and the investment amount of system construction. If the user only needs the software enterprise to maintain its developed application software, U is the development fee of the application software; If users need software companies to maintain the whole system, including computer hardware, software, network and application software, then U is the total investment of information engineering projects.

2. 1.2 N (number of technicians)

Software companies send n technicians, who are permanent users, so:

Software (system) maintenance fee/year = U × 15% or b×××× n×12.

B and λ refer to 1.

Level 2.2

Software enterprises respond 24 hours (7×24 hours) seven days a week, go to the site for 2 hours, and send technicians to the site to debug the software (system) performance every day to make it run well.

Software (system) maintenance fee/year = U × 10%

2.3 degrees Celsius level

The software company responded in 7×24 hours and arrived at the scene in 2 hours.

Software (system) maintenance fee/year =U × 5%

2.4 D level

If the user's information engineering system or application software has problems, the original software enterprise will send someone to maintain it.

2.4. 1 B '

This maintenance method requires the software company to keep all technical documents, and also requires the software company to take out special personnel to be familiar with and fully grasp the technical details of the software (system). Therefore, this expenditure of software enterprises is bound to be rewarded in the maintenance fee income.

Take b in section 1. 1.3 as the parameter, and change the unit of person-month to person-day, which is represented by b'.

2.4.2 τ'

If software enterprises adopt component-based development methods and establish component libraries, the efficiency of software maintenance will be greatly improved. In addition, if there are many users running similar systems, the efficiency can also be improved.

τ in section 1. 1.3 is taken as a parameter, which is expressed as τ'. Therefore:

Software (system) maintenance fee/time =B' × τ'× n

This time n represents the number of people and days needed. The value of τ' is 0.2 ≤ τ'≤ 1.

3. Estimation method of system integration price

The equipment, software and network involved in the whole system can be integrated and run normally, and the running result can reach the goal of establishing the system by users. This is the meaning of system integration. Therefore, it can be understood that simple equipment procurement and supply does not involve system integration, and simple application software development does not involve system integration.

The cost of system integration should be related to the scale and complexity of the whole system.

System scale is often closely related to system construction cost. In order to simplify the calculation, the system construction cost (expressed by U) is taken as the reference coordinate. Complexity (denoted by α) can be divided into four levels.

System integration fee = u××××××α× t

See section 1.2.5.

3. 1 A level

The whole system involves computer hardware, software and LAN, and its architecture is below three layers (including three layers).

5% ≤ α ≤ 8%

Level 3.2

The whole system involves computer hardware, software, local area network and internet, and its architecture is above three layers (including three layers).

7% ≤ α ≤ 10%

3.3 degrees Celsius level

The whole system involves computer hardware, software, LAN, Internet and various network interfaces.

8% ≤ α ≤ 12%

3.4 D level

The whole system involves the interface of computer hardware, software, network, communication and various data acquisition devices or the interface with the main system.

10% ≤ α ≤ 15%

4. System solution cost estimation method

According to the initial requirements put forward by users and previous experience, software companies provide the whole system construction scheme, including the general idea of computer hardware, software, network equipment and application software to be purchased, cost estimation, preliminary schedule, planning of some rules and regulations involved in informatization, and sometimes the construction of information center. This is what the system solution should do.

At present, the domestic market has not fully realized that the system solution is the result of intellectual labor, and most domestic bidding companies are not familiar with information technology, which makes it more difficult to charge for the system solution. Therefore, the current fees are in a transitional stage.

The cost of system solution is related to the scale and complexity of the whole system.

The scale of the system is often closely related to the cost of system construction. In order to simplify the calculation, the total investment of system construction (expressed in U) is taken as the reference coordinate.

Complexity is related to the user's function, the complexity of performance requirements, the type and number of information interfaces, and is expressed by β.

Solution cost =U × β × T

See section 1.2.5.

Regarding β, we refer to the levels listed in Section 3.

Grade A: 0.7% ≤ β ≤ 1.2%

Grade b: 1% ≤ β ≤ 1.8%

Grade c: 1.5% ≤ β ≤ 2.2%

Grade D: 2% ≤ β ≤ 3%