Software Costing

Optimize the success rate of your projects thanks to more reliable estimations

Knowing the size of the software to be developed, we can calculate the effort of development by taking into account other parameters as the experience of the teams or the technology.

Estimancy allows you to have simpler, faster, more reliable estimations.

Thanks to Software Costing, you can:

Decrease the number of abandoned or failing projects to guarantee a return on investment mastering project ADM (Development application and Maintenance) costs. Estimancy can answer all your estimation needs, depending on technology, Sizing, or activities. You will then be able to improve your forecasts over time.

What is Software Costing?

Software Costing consists in answering the following questions:

How much is it going to cost and how long will it last, according to the hypotheses of estimation?

Effort can depend on numerous parameters. Some models identify up to 200 parameters! In most cases, for a given company, parameters can be reduced to the number of 5.

The construction of a cost model is based on a statistical approach, and is therefore uncertain.

Estimancy allows to:

Produce estimations in all the stages of a project

Calculate the effort according to standard or specific calculation methods

Industrialize the process of calculation (workflow – safety – access rights)

Assure the traceability from the request to the detail of the calculation

What is a cost model?

A cost model allows to calculate an effort, according to input parameters such as:

  • The size of the software (cf. Software Sizing)
  • The technology
  • The experience of the teams (developers, architects)
  • Constraints on the project (multi-sites, process)
  • Constraints on the product (quality, platforms) etc…

Generally, we calculate a development effort (unitary tests), then, by ratios, the efforts of the other activities of development. The activities depend on the methodology (Waterfall, Agile, Cycle in V)

The duration is deducted with an equation and the possible adjustment of the schedule.

Finally, the costs are calculated according to the costs of every profiles or an average cost.

Building a cost model

The simplest method consists in establishing a correlation function between the size and the effort. We lean on previous projects, drawing up the balance sheet size – effort. For it is necessary to have a well defined size and statements of time.

Another approach consists in leaning on “standard” models. There are many works which were led on the correlation size-effort, and gave rise to heaps of models, as CoCoMo, CoSysMo, CoQualmo, etc.

The best practice is to separate size, calculation of basic effort, activities, and calculation of deadline / Staffing.

Estimancy suggests models which are ready to use, but you can also easily implement your own models.

So the user can have a model for small projects, SAP projects, big Java projects, etc.