The second week of work-estimating the software workload

Evaluation factors affecting software workload

There are many factors involved in the evaluation of software workloads. According to my understanding, there are methods or tools used, familiarity of the developer, and (inter-departmental) interest, the understanding of the project to assess the personality of the person. The final workload assessment based on various factors will have a big difference.

1. Method of Use (tool)

For a project, if a is done on the existing module, and B is restarted. Then their assessment of the project's workload is naturally different. Now suppose that a project consists of a set of front and back two parts, the party will think that they need to deal with the background part, the workload is the time required in the background, but party B may think that their workload is the front and back two parts of the and, this is the completion of the whole project.

2. How familiar the developer is

This is easy to understand, if the general language or technical mastery of unfamiliar people, spend time and rework time, communication time will naturally be a little longer.

3. (inter-departmental) interest relations

Outsourcing projects between companies tend to be a bit longer, taking into account the assumption that there will be some change in user demand or the desire to make more money from it. The company's departments are similar, and the marketing department always wants the sooner the better, but the development department always thinks that the marketing department didn't ask for the demand earlier, and so on.

4. Understanding the project or assessing the personality of the person

Similarly, if you have 1000 users and 10 million users, there will be a very big difference in practice.

Evaluation method of software workload

Here, we analyze several common methods of workload evaluation:

First, the software scale is evaluated by the function point. This method is often prominent in the actual work of the magic weapon, with a large number of followers, but because of its original definition is abstract, the actual workload and function points between the functional relationship is not obvious, often also subject to technical choice. For example, for the statistics of the current use of the system users of this requirement, the use of B/s method is very straightforward, and the traditional C/s seems to take some effort, the workload of the two are obviously different. Another example, C/s pop out a modal form is very simple, but for B/s seems to have to think more.

Second, the commonly used assessment methods are analogy and expert law. Because of the lack of historical data, analogy and expert law are also difficult to work, not to mention that many enterprises also lack the use of this assessment method of experience and data.

How to measure the software scale This problem has been the focus of this field since the birth of computer engineering. The functional scale of a software product or project is a key indicator of the cost of software development and transaction, the forecast of Project resource investment, the budget of Project maintenance cost, the requirement of project quality management, and the time of product launch. Therefore, it is particularly important to measure the functional scale of software products. At present, experts in software field at home and abroad have carried out very fruitful research on the measurement of software function scale, and put forward various industry standards.

ISO/IEC has published 4 criteria for measuring methods of functional scale, which are:

--iso/iec 19761 (COSMIC-FFP method);
--iso/iec 20926 (Ifpug method);
--iso/iec 20968 (Mkⅱ method);
--iso/iec 24750 (Nesma method).

Among them, the COSMIC-FFP method declaration can be applied to the Management Information System (MIS) and real-time type two kinds of software, such as the control system in home appliances, aircraft ticketing system and so on, but this method is not suitable for complex algorithm system and processing continuous variable system, such as: Expert system, simulation system, self-learning system, Weather forecasting systems, sound and image processing systems, etc. The Ifpug method declaration is available for all types of software, and the Mkⅱ method declaration can be used for any type of software that a logical transaction can be determined, and the Nesma method is very similar to the Ifpug method and can be used for all software types. As far as I know the COSMIC-FFP method, the process of the method mainly has two stages, the first stage is the mapping phase, the purpose of the mapping phase is to decompose the functional requirements of the software into functional processing, data groups, data properties, the second stage is the measurement phase, The purpose of the measurement phase is to decompose the functional processing into data movement and calculate the function size.

The second week of work-estimating the software workload