Software Production Cost Estimation Models

Software Production Cost Estimation Models

Technology is best when it brings people together

Oscar Mauricio Garcia Chavez Systems And Computation Engineering

CONTENT

5. COCOMO I and II Model

Introduction

1. Basic Estimation Model

Video

Conclusions

2. Basic MLDC Model

Technology is best when it brings people together

3. Delphi Method

Bibliography

Thank You

4. Function Point Based Model

INTRODUCTION

Software production cost estimation is a crucial task in the development of software engineering projects. An effective and accurate estimation model can help companies make informed decisions, allocate appropriate resources and plan their projects efficiently. In this presentation, we will explore various software production cost estimation models and their application in the industry. Software production cost estimation provides a solid foundation for planning, decision making, financial control and risk management in software development projects. It is an essential tool for ensuring the success and profitability of projects, as well as for establishing solid business relationships with customers and suppliers.

Technology is best when it brings people togethert

What Is Cost Estimation?

Technology is best when it brings people together

Cost estimation is the calculation of the cost/budget of services and assets you will needfor your business. It is a necessary thing to do as it will allow you to commit a certainfinancial amount to the estimate that was made and manage the rest of your budget forother resources. One of the prominent needs in your business is IT Services such assetting up hardware, installation of programs, and maintaining the computer systems.Once you have figured out the cost estimation for them, you will be able to know whatyou want, and how much you are willing to spend on it.

+INFO

Basic Estimation Model

01

The basic software production cost estimation model is an initial, simple approach used to estimate the costs involved in the development of a software project. This model is based on previous experience and intuition of experts in the field. Some of the key components considered in this model are:

• Project requirements: functional and non-functional requirements of the software to be developed are evaluated. These requirements are used as the basis for estimating the scope of the project and, therefore, the associated costs.
• Effort and time: The amount of effort and time that will be required to complete the project is estimated. This includes time spent on analysis, design, programming, testing, documentation and project management.
• Resources: This takes into account the resources required to carry out the project, such as personnel, equipment, specialized software and hardware.

The basic estimating model is relatively quick and simple to apply, but may have limitations in terms of accuracy, especially for more complex or large-scale projects.

Basic MLDC Model

02

The basic MLDC model (Lines of Code Model) is another common approach used to estimate software production costs. This model is based on the number of lines of code expected to be developed in the project. Some relevant aspects of the MLDC model are:

• Project size: The total number of lines of code that will be required to be developed is estimated. This can be based on requirements analysis, preliminary designs or other estimation approaches.
• Team productivity: The average productivity of the software development team is considered. This productivity is expressed in lines of code developed per unit of time (e.g., lines of code per hour or per day).
• Effort and time: Using the estimated project size and team productivity, the effort and time required to complete the project is calculated. This involves determining how many hours or days of work will be required to develop the estimated lines of code.

The MLDC model has the advantage of being easy to understand and apply, and provides a quick initial estimate. However, it is important to keep in mind that the number of lines of code is not always an accurate indicator of the complexity or actual effort required in software development.

Delphi Method

03

The Delphi method is an estimation technique that uses the opinion of a group of experts in the field of software engineering to establish a conceptual software cost estimation model. This method is based on a series of rounds of questions and answers, with the objective of reaching a consensus on the estimates. Some key points of the Delphi method are:- Selection of experts: A group of experts in the field of software cost estimation is selected. These experts can come from different areas, such as project managers, experienced developers and cost analysts.- Question and answer rounds: Questionnaires are sent to the experts, requesting their individual estimates on different aspects of the project, such as scope, effort required and resources needed. The responses are then compiled and submitted anonymously to the experts for review and discussion.- Iterations and consensus: The question and answer process is repeated several times, with the objective of reaching a gradual consensus among the experts. In each round, the experts have the opportunity to review and adjust their estimates based on the responses of the other participants.The Delphi method helps reduce individual bias and promotes decision making based on the collective knowledge of experts in the field. However, it may require more time and effort compared to other estimation approaches.

Function Point Based Mode

04

The Function Point (FP) based model is a software cost estimation method that focuses on the functionality delivered by the system and its relationship to the effort required. In this model, points are assigned to different software functions, such as inputs, outputs, queries and files. Some key aspects of the Function Point based model are:

• Function identification: Different software functions are identified and classified according to the interaction with users and the system. These functions are grouped into categories, such as internal functions (e.g., data processing) and external functions (e.g., user interaction).
• Assignment of points: A numerical value is assigned to each function, based on its complexity and relative size. These points are summed to obtain the total Function Points for the project.
• Calculation of effort and time: Using the estimated Function Points, experience-based conversion factors are applied to determine the effort and time required. These factors may vary depending on the context of the project, such as the experience of the development team and the technological complexity.

The Function Point-based model is widely used because of its focus on delivered functionality and its ability to adapt to different projects and technologies. However, its accuracy depends on a correct identification and classification of software functions.

COCOMO I and II Model

05

The COCOMO model (COnstructive COst MOdel) is a set of models used for software production cost estimation developed by Barry W. Boehm. There are two main versions of the model: COCOMO I and COCOMO II. Some relevant aspects of these models are:COCOMO I: This model is based on a sequential approach and focuses mainly on waterfall software development projects. It estimates costs based on factors such as program size, staff experience, product complexity and development team characteristics.COCOMO II: This version of the COCOMO model is more flexible and adaptable to different development approaches, such as agile methods. It considers a wider range of cost factors, such as development process maturity, database size and hardware performance.Both COCOMO models provide estimates based on mathematical formulas and adjustment factors. However, it is important to keep in mind that these models are approximations and require precise and detailed information to obtain more accurate estimates.

Technology is best when it brings people together

+INFO

Estimate Software Development Costs.

Conclusions

• In this presentation, we have explored several software production cost estimation models. Each model has its own advantages and limitations, and it is important to select the right model based on the needs and characteristics of the project.
• It is essential to select the most appropriate model for the project and adjust it according to the particular circumstances.
• These models can be valuable tools to help companies make informed decisions and efficiently plan their software projects.

Technology is best when it brings people together

BIBLIOGRAPHY

https://en.wikipedia.org/wiki/Delphi_method#Introduction https://en.wikipedia.org/wiki/COCOMO http://www.pmoinformatica.com/2015/04/estimacion-puntos-funcion-introduccion.html https://www.evaluandosoftware.com/software-a-medida/costo-sistema-a-medida/ https://es.smartsheet.com/ultimate-guide-project-cost-estimating https://www.toptal.com/agile/estimacion-de-costos-de-software-en-gestion-de-proyectos-agiles

Technology is best when it brings people together

¡Thank You!