Scribd
Upload
6 views

week 3- SE-COST ESTIMATION (2)

Uploaded by

nausheen1614
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views

week 3- SE-COST ESTIMATION (2)

Uploaded by

nausheen1614
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

LAB-3

COST ESTIMATION

INVENTORY MANAGEMENT SYSTEM

Estimation in Software Engineering

Estimation in the context of inventory management system project involves forecasting the
effort, time, resources, and costs necessary for building the system. The goal of estimation is
to enable effective planning, budgeting, and allocation of resources. Common factors
considered during estimation include:

 Size of the software (e.g., lines of code or function points)

 Complexity of the project

 Team skill level

 Project risks

 Available resources (e.g., hardware, personnel)

 Time constraints

Several techniques are used for estimation:

1. Expert Judgment: This technique relies on the insights and experience of seasoned
software developers or project managers to make informed predictions about the time,
effort, and resources needed to complete a project. These experts draw on their past
experiences and knowledge of similar projects to estimate project requirements.

2. Analogy-based Estimation: In this approach, the current project is compared to past


projects that had similar characteristics. The estimation is based on how those projects
performed in terms of effort, time, and cost, making it easier to forecast the likely
demands of the new project.
3. Decomposition Techniques: This method involves breaking down a complex project
into smaller, manageable tasks. Each task is then individually estimated, and the sum
of these estimates gives the total project effort and cost. An example of this approach
is the Work Breakdown Structure (WBS), where tasks are hierarchically structured

4. Parametric Models: These are mathematical models that predict effort and cost
based on certain input parameters, such as project size, complexity, and developer
productivity. One well-known model is COCOMO (Constructive Cost Model),
which estimates the effort required to complete a project by considering factors like
the size of the codebase and the development environment.

COCOMO (Constructive Cost Model)

COCOMO is a well-known parametric estimation model developed by Barry W. Boehm in


1981. It is used to estimate the cost, effort, and schedule of a software project based on its
size, expressed in terms of "thousands of lines of code" (KLOC). The COCOMO model
comes in three levels:

1. Basic COCOMO: A simple model that estimates effort and development time using
basic project size.

2. Intermediate COCOMO: This model extends the basic COCOMO by considering


additional cost drivers such as product complexity, required reliability, team
experience, and tools used.

3. Detailed COCOMO: The most comprehensive version, where the project is broken
down into smaller components, and each component's effort is estimated separately
based on the factors considered in the intermediate model.
The comparison of three COCOMO modes

Basic COCOMO coefficients

Let us assume that the project size is 40 KLOC (organic)

Effort (𝐸) = 𝑎𝑏(𝐾𝐿𝑂𝐶)𝑏𝑏

E = 115.444 PM
𝐷𝑒𝑣𝑒𝑙𝑜𝑝𝑚𝑒𝑛𝑡 𝑡𝑖𝑚𝑒 𝑜𝑣𝑒𝑟 𝑚𝑜𝑛𝑡ℎ𝑠 (𝐷) = 𝑐𝑏(𝐸)𝑑𝑏

D = 15.1929 PM

𝐸
𝐴𝑣𝑒𝑟𝑎𝑔𝑒 𝑆𝑡𝑎𝑓𝑓 𝑆𝑖𝑧𝑒 (𝑆𝑆) = 𝑃𝑒𝑟𝑠𝑜𝑛𝑠 𝐷

SS = 7.5985 Persons

𝐾𝐿𝑂𝐶
𝑃𝑟𝑜𝑑𝑢𝑐𝑡𝑖𝑣𝑖𝑡𝑦 (𝑃) = 𝐾𝐿𝑂𝐶/𝑃𝑀 𝐸

P = 0.3465 KLOC/ PM

You might also like