Image module

Software size measurement according to specifications

The size of the software to be developed is the most important element to consider to determine the price of software development.

Thanks to software sizing, you can implement performance indicators such as:

  • Productivity: amount of software produced in time,
  • Quality: number of defects per unit of software,
  • Maintenance costs: maintenance costs according to the size of the application.

Software sizing also enables to improve productivity, objectify costs and compare with others.

Thanks to artificial intelligence and Machine Learning, Estimancy can automatically determine the size of the software according to specifications in natural language.

What is software sizing?

Software sizing answers the following question: what is the amount of software to be developed in accordance with specifications?

 

That amount varies depending on the technology if the size is expressed in technical components (lines of code, widgets, screens, processing, batch, software package configuration, etc.).

Functional measures (IFPUG, COSMIC, …) enable to avoid using technologies measuring the size of the request of the user but they do not allow to measure what is not functional (e.g., application migration).

A company must have different systems able to determine the size corresponding to different project types.

Image module

Software size

Estimancy automatically calculates the size of software to be developed according to specifications in natural language.

The size of the software may lean on technical or functional components.

Our solution enables to:

  • Avoid the intervention of experts in function points (after the learning phase),
  • Save time,
  • Answer quote requests faster,
  • Get more reliable and replicable function point sizing.

Technical size is the developer portfolio

  • Determines the technical size of the request
  • Depends on the technology
  • Non-standard

Functional size is the user portfolio

  • Determines the functional size of the request
  • Does not depend on technology
  • International norms exist
taille technique
Cocomo

Gain 10% of productivity 

 

Experience shows that simply setting up a productivity measurement system increases productivity by 10%.

Teams are more attentive, more engaged, and understand that productivity is a key goal for business success.

The measurement of productivity must imperatively be accompanied by an analysis process, and never concern individuals.

 

The history of the meter

IT is still a recent science and software is intangible.

When we take a closer look at the history of sizing, we realize that the trade of software encounters the same issues as any other trades did before the French revolution.

Until the 18th century, the measuring systems were disparate. Despite the attempts of Charlemagne, and many other of his successors, to reduce the number of units used at that time, France was one the most creative and disorderly countries in that field. In 1795, France counted more than 700 units.

Many of them derived from human morphology and were named after it: inch, palm, foot, cubit, step, fathom or toise. Those units were not fixed, they would vary from one city to another or according to the nature of the objects to be measured. For instance, the surface of floors and carpets would be expressed in different units.

Source

Image module