A SEMINAR ON COCOMO Presentation by, Kongkon Mahanta MCA 4 th sem Roll no- 8.

Slides:



Advertisements
Similar presentations
Software Cost Estimation
Advertisements

COST ESTIMATION TECHNIQUES AND COCOMO. Cost Estimation Techniques 1-)Algorithmic cost modelling 2-)Expert judgement 3-)Estimation by analogy 4)-Parkinsons.
Lial/Hungerford/Holcomb/Mullins: Mathematics with Applications 11e Finite Mathematics with Applications 11e Copyright ©2015 Pearson Education, Inc. All.
Estimation using COCOMO More Science, Less Art. COCOMO History COCOMO History Constructive Cost Model Dr. Barry Boehm TRW in 1970s COCOMO
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
Project Risks and Feasibility Assessment Advanced Systems Analysis and Design.
Ch8: Management of Software Engineering. 1 Management of software engineering  Traditional engineering practice is to define a project around the product.
1 COST ESTIMATION Basics, COCOMO, FP. 2 What is estimated? TIME MONEY TIME: –duration, chronological weeks, months, years –effort, person-month (man-month)
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
Chapter 23 – Project planning Part 2. Estimation techniques  Organizations need to make software effort and cost estimates. There are two types of technique.
Software Project Management
1 Cost Estimation CIS 375 Bruce R. Maxim UM-Dearborn.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
Information System Economics Software Project Cost Estimation.
University of Toronto Department of Computer Science © 2001, Steve Easterbrook CSC444 Lec22 1 Lecture 22: Software Measurement Basics of software measurement.
© The McGraw-Hill Companies, Software Project Management 4th Edition Software effort estimation Chapter 5.
Cost22 1 Question of the day u If you were the boss, what would you do for cost estimation?
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Lecture 22 Instructor Paulo Alencar.
COCOMO Models Ognian Kabranov SEG3300 A&B W2004 R.L. Probert.
After Lesson 6 next is Lesson 13 to fit topic on Software Development SOFTWARE PROJECT MANAGEMENT.
Project Management Estimation. LOC and FP Estimation –Lines of code and function points were described as basic data from which productivity metrics can.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 23Slide 1 Chapter 23 Software Cost Estimation.
By K Gopal Reddy.  Metrics in software are of two types.direct and indirect.  Function points as indirect metrics.  Function points are used to measure.
CS /39 Illinois Institute of Technology CS487 Software Engineering David A. Lash.
A Brief Introduction to COCOMO Hossein Saiedian EECS810: Software Engineering.
Group Members: Ayush Newatia, Barry Foye, Billy Felton, Kevin Anderson, Shahnaz Begum and Adam Jasinski Constructive Cost Model is a technique used to.
Quality Assurance vs. Quality Control Quality Assurance An overall management plan to guarantee the integrity of data (The “system”) Quality Control A.
Software cost estimation Predicting the resources required for a software development process 1.
Cost13 1 Cost Estimation Estimates based on LOC. cost13 2 Boehm's COCOMO u Software Engineering Economics u Prentice-Hall c1981 u type COCOMO in a search.
T. E. Potok - University of Tennessee CS 594 Software Engineering Lecture 3 Dr. Thomas E. Potok
Student Curriculum Planning System MSE Project Presentation I Kevin Sung.
10/27/20151Ian Sommerville.  Fundamentals of software measurement, costing and pricing  Software productivity assessment  The principles of the COCOMO.
Cost Estimation. Problem Our ability to realistically plan and schedule projects depends on our ability to estimate project costs and development efforts.
Cost Estimation What is estimated? –resources (humans, components, tools) –cost (person-months) –schedule (months) Why? –Personnel allocation –Contract.
Project Estimation Model By Deepika Chaudhary. Factors for estimation Initial estimates may have to be made on the basis of a high level user requirements.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.
Project Estimation techniques Estimation of various project parameters is a basic project planning activity. The important project parameters that are.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 26Slide 1 Software cost estimation l Predicting the resources required for a software development.
SFWR ENG 3KO4 Slide 1 Management of Software Engineering Chapter 8: Fundamentals of Software Engineering C. Ghezzi, M. Jazayeri, D. Mandrioli.
Software Project Estimation IMRAN ASHRAF
Cost9a 1 Software Estimating Technology: A Survey Richard Stutzke Crosstalk, May96 text pp
Effort Estimation Has been an “art” for a long time because
Copyright , Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M18 - Version 9.01 SMU CSE 7315 Planning and Managing a Software Project.
©Ian Sommerville, adapted by Werner Wild 2004Project Management Slide 1 Software cost estimation u Predicting the resources required for a software development.
Estimation using COCOMO
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Effort Estimation In WBS,one can estimate effort (micro-level) but needed to know: –Size of the deliverable –Productivity of resource in producing that.
The COCOMO model An empirical model based on project experience. Well-documented, ‘independent’ model which is not tied to a specific software vendor.
Rating Very Very Extra Cost Drivers Low Low Nominal High High High Product Attributes Required software reliability Database size.
CSE SW Project Management / Module 18 - Introduction to Effort Estimating Models Copyright © , Dennis J. Frailey, All Rights Reserved CSE7315M18.
Project Estimation. Planning Prerequisites The planning process requires the following inputs: –Required human effort (man-months) –Project duration (months)
بشرا رجائی برآورد هزینه نرم افزار.
Software Project Management (Lecture 9)
Project Cost Management
Software Estimating Technology: A Survey
Software Project Management
Software Project Management
Software Project Management
Software Planning
Constructive Cost Model
COCOMO Model Basic.
Activities During SPP Size Estimation
More on Estimation In general, effort estimation is based on several parameters and the model ( E= a + b*S**c ): Personnel Environment Quality Size or.
COCOMO Models.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
COCOMO 2 COCOMO 81 was developed with the assumption that a waterfall process would be used and that all software would be developed from scratch. Since.
Software Cost Estimation
COnstructive COst MOdel
COCOMO MODEL.
Presentation transcript:

A SEMINAR ON COCOMO Presentation by, Kongkon Mahanta MCA 4 th sem Roll no- 8

PROJECT ESTIMATION TECHNIQUES The important project parameters that are estimated include Project size Effort required to develop the software Project duration Cost Three broad categories of estimation techniques: Emipirical estimation techniques: EXPERT JUDGEMENT & DELPHI ESTIMATION Analytical estimation techniques: HALSTEADS SOFTWARE SCIENCE Heuristic technique: COCOMO

COCOMO( CO nstructive CO st estimation MO del) Boehms definition of different kinds of software are as follows : Organic Developmental team is small Team members are experienced in developing similar types of project Semidetached Developmental team consist of experienced and inexperienced staff Team members have limited experience on related system

COCOMO( CO nstructive CO st estimation MO del) Embedded Developmental project is of embedded type Software being developed is strongly coupled to complex hardware According to boehm,software cost estimation should be done through three stages: Basic COCOMO Intermediate COCOMO Complete COCOMO

BASIC COCOMO model The basic COCOMO model is given by the following expression: Effort= a 1 x (KLOC) a2 PM Tdev= b 1 x (Effort) b2 months Where o KLOC=Estimated size of software product expressed in Kilo lines of code o a 1,a 2,b 1,b 2 are constants for each category of software products o Tdev is the estimated time to develop the software expressed in months o Effort is the total effort required to develop the software product, expressed in person month(PMs)

BASIC COCOMO model Estimation of development effort ORGANIC: Effort = 2.4 x (KLOC) 1.05 PM SEMIDETACHED: Effort = 3.0 x (KLOC) 1.12 PM EMBEDDED : Effort = 3.6 x (KLOC) 1.20 PM Estimation of development time ORGANIC: Tdev = 2.5 x (Effort) 0.38 months SEMIDETACHED: Tdev = 2.5 x (Effort) 0.35 months EMBEDDED : Tdev = 2.5 x (Effort) 0.32 months

AN EXAMPLE P ROBLEM : Assume that the size of an organic type software product has been estimated to be 32,000 lines of source code. Assume that the average salary of software developers is Rs 15,000 per month. Determine the effort required to develop the software product, the development time, and the cost to develop the product SOLUTION : Effort = 2.4 x (32) 1.05 = 91 PM Nominal developmental time = 2.5 x (91) 0.38 =14 months Cost required to develop the software = 91 X 15,000 = Rs 1,465,000

INTERMEDIATE COCOMO MODEL After determining the initial estimate, some other factors are incorporated to get the final estimate. It uses a 15 different cost drivers based on various attributes of software development. Each cost driver has a rating scale, and for each rating, a multiplying factor is provided. Cost drivers can be classified as being attributes of: 1. Product 2.Computer 3.Personnel 4.Development environment

EFFORT MULTIPLIERS FOR COST DRIVER Product attributes Very lowlownominalhighVery high Requires reliability Database size Product complexity Computer attributes Very low lownominalhighvery high Execution time Main storage Virtual machine Turnaround time Personnel attributes Very low lownominalHighVery high Analyst capability Application experience Programmer capabilty Virtual machine exp Programming language exp Project atttibutes Very low lownominalHighVery high Modern programming Use of s/w tools Developmental schedule

EXAMPLE TO USE THE EFFORT MULTIPLIERS FOR COST DRIVER(Product and Computer) Product attributes Very lowlownominalhighVery high Requires reliability Database size Product complexity Let the database size is high and the turnaround time is low Then effort adjustment factor(EAF)= 1.08 * 0.87= From earlier example, the effort for the project is, E = 2.4 x (32) 1.05 = 91 pm Using the EAF,the adjusted effort estimate is E(f)=91* = 85.5 PM Computer attributes Very low low nominalhighvery high Execution time Main storage Virtual machine Turnaround time

COMPLETE COCOMO Large systems are break down into several small subsystem Subsystems may have different characteristics. Maybe organic,semidetached and embedded The cost of the each subsystem is estimated separately ans summed up to give the overall cost of the system

LIMITATION OF COCOMO COCOMO is not a perfect realistic model. Assumptions made at the beginning may vary as time progresses in developing the project. When need arises to revise the cost of the project. A new estimate may show over budget or under budget for the project. Thus any changes in the requirements are not accommodated for calculation of cost of the project.