Estimation using COCOMO More Science, Less Art. COCOMO History COCOMO History Constructive Cost Model Dr. Barry Boehm TRW in 1970s 1981 - COCOMO81 1996.

Slides:

Advertisements

Similar presentations

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

Advertisements

Software Cost Estimation Main issues:  What factors determine cost/effort?  How to relate effort to development time?

Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.

LOC, COCOMO I & COCOMO II Subject: Software Engineering Coordinator: Mr Anoj Kumar Presented By: Kamal Kishore (2012ca34) Jyoti Shrivastava (2012ca52)

Project Risks and Feasibility Assessment Advanced Systems Analysis and Design.

Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation.

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)

COCOMO II 資管研一張永昌. Agenda Overall Model Definition COCOMO II Models for the Software Marketplace Sectors COCOMO II Model Rationale and Elaboration Development.

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.

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.

Software Engineering: A Practitioner’s Approach

SOFTWARE COST ESTIMATION

Cost22 1 Question of the day u If you were the boss, what would you do for cost estimation?

ECE 355: Software Engineering

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.

Software Project Management

Dr. M. Shamim HossainSWE 211 Effort, Duration and Cost Lec 3 1.

Project Management Estimation. LOC and FP Estimation –Lines of code and function points were described as basic data from which productivity metrics can.

CS /39 Illinois Institute of Technology CS487 Software Engineering David A. Lash.

A Brief Introduction to COCOMO Hossein Saiedian EECS810: Software Engineering.

1 Software Cost Estimation. Outline  Introduction  Inputs and Outputs  Methods of Estimation  COCOMO  Conclusion 2.

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.

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

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.

Estimating Software Projects & Activity Scheduling in the Dynamic, Multi-Project Setting: Choosing Heuristics Through Deterministic Simulation.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.

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

©Ian Sommerville, adapted by Werner Wild 2004Project Management Slide 1 Software cost estimation u Predicting the resources required for a software development.

Estimation for Software Projects 1. Software Project Planning 2 The overall goal of project planning is to establish a pragmatic strategy for controlling,

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.

Software cost estimation. Objectives To introduce the fundamentals of software costing and pricing To introduce the fundamentals of software costing and.

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.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation.

Project Estimation. Planning Prerequisites The planning process requires the following inputs: –Required human effort (man-months) –Project duration (months)

بشرا رجائی برآورد هزینه نرم افزار.

COCOMO Software Cost Estimating Model Lab 4 Demonstrator : Bandar Al Khalil.

Cost Estimation Software Quality Assurance and Testing.

THE FAMU-CIS ALUMNI SYSTEM

Software Engineering.

Software Estimating Technology: A Survey

SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION

Software Project Management

Constructive Cost Model

Software Engineering.

SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION

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 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

Presentation transcript:

Estimation using COCOMO More Science, Less Art

COCOMO History COCOMO History Constructive Cost Model Dr. Barry Boehm TRW in 1970s COCOMO COCOMOII

Modes Modes (project types) Organic Organic Relatively small software teams develop software in a highly familiar, in-house environment Semi-detached Semi-detached between organic and embedded Embedded Embedded Needs to operate within tight constraints. The product must operate within (is embedded in) a strongly coupled complex of hardware, software, regulations, and operational procedures.

Levels Levels (sophistication of estimate) Basic Basic for rough estimates Intermediate Intermediate several more input variables Detailed Detailed phase-sensitive effort

Basic's Effort Formula E = a × Size b E = person-months Size = KLOC OrganicSemiEmbedded a b

Estimation Type = Basic Organic Semi-detached Embedded

Basic's Duration Formula TDEV = 2.5 × E b TDEV = development time in months Organic SemiEmbedded b

Intermediate Effort Formula E = a × Size b × C E = person-months Size = KLOC C = 15 Cost Drivers OrganicSemiEmbedded a b

Cost Drivers Cost Drivers very low extra high Product attributes Required software reliability Size of application database Complexity of the product Hardware attributes Run-time performance constraints Memory constraints Virtual machine environment volatility Required turnaround time

Cost Drivers Cost Drivers very low extra high Personnel attributes Analyst capability Software engineer capability Applications experience Virtual machine experience Programming language experience Project attributes Use of software tools Application of SwEng methods Required development schedule

Example of Intermediate /cocomo81_pgm/cocomo81.htmlsunset.usc.edu/research/COCOMOII /cocomo81_pgm/cocomo81.html

Detailed Detailed Broken into system, subsystem, and module Cost Drivers applied to each module

Why COCOMO II Why COCOMO II Changes in development less waterfall more reuse more design time more real-time, less mainframe COCOMO81 based on SLOC not FPs COCOMOII supports FP, Object Points, and SLOC

COCOMO II COCOMO II The Application Composition Model used early for rough estimate based on Object Points The Early Design Model used once requirements are stable uses a small set of new Cost Drivers, new estimating equations based on Unadjusted Function Points or KSLOC The Post-Architecture Model used after development of overall architecture new cost drivers, new line counting rules, new equations

Application Composition Model Object Points used for sizing, not LOC Based on number and complexity of screens number and complexity of reports amount of code reuse experience of developers

Object Points Object point complexity levels for screens and reports Number of data tables views Total <4Total <8Total 8+ <3simplesimplemedium 3-7simplemediumdifficult 8+mediumdifficultdifficult

Object Complexity Weight Object typeSimpleMediumDifficult Screen Report GL component

COCOMOII Rough Estimate of Effort NOP = (object points) x (100 – r) / 100 NOP = new object points r = % of code reuse E = NOP / PROD PROD = productivity based on experience Developer Experience very low low nominal high very high

Next… Exam One