1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern.

Slides:



Advertisements
Similar presentations
COST ESTIMATION TECHNIQUES AND COCOMO. Cost Estimation Techniques 1-)Algorithmic cost modelling 2-)Expert judgement 3-)Estimation by analogy 4)-Parkinsons.
Advertisements

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.
Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6, 6.5.
COCOMO II Calibration Brad Clark Software Metrics Inc. Don Reifer Reifer Consultants Inc. 22nd International Forum on COCOMO and Systems / Software Cost.
University of Southern California Center for Software Engineering CSE USC ©USC-CSE 10/23/01 1 COSYSMO Portion The COCOMO II Suite of Software Cost Estimation.
University of Southern California Center for Systems and Software Engineering 1 © USC-CSSE Unified CodeCounter (UCC) with Differencing Functionality Marilyn.
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)
1 CORADMO in 2001: A RAD Odyssey Cyrus Fakharzadeh 16th International Forum on COCOMO and Software Cost Modeling University of Southern.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
Estimating System of Systems Engineering (SoSE) Effort Jo Ann Lane, USC Symposium on Complex Systems Engineering January 11-12, 2007.
COCOMO II Database Brad Clark Center for Software Engineering Annual Research Review March 11, 2002.
SE is not like other projects. l The project is intangible. l There is no standardized solution process. l New projects may have little or no relationship.
University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.
Chapter 23 – Project planning Part 2. Estimation techniques  Organizations need to make software effort and cost estimates. There are two types of technique.
Information System Economics Software Project Cost Estimation.
COCOMO-SCORM: Cost Estimation for SCORM Course Development
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Lecture 22 Instructor Paulo Alencar.
Feasibility Study.
Group Members: Ayush Newatia, Barry Foye, Billy Felton, Kevin Anderson, Shahnaz Begum and Adam Jasinski Constructive Cost Model is a technique used to.
University of Southern California Center for Systems and Software Engineering Cost Estimation with COCOMO II Barry Boehm CS 510, Fall 2015 v3: Slide 10.
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.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6 Barry.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6 Barry.
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.
University of Southern California Center for Systems and Software Engineering Vu Nguyen, Barry Boehm USC-CSSE ARR, May 1, 2014 COCOMO II Cost Driver Trends.
Expert System Job Offer Evaluation Software May Abstract The project’s focus is to decide what criteria should be used to determine which job offer.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.
CSE 403, Spring 2008, Alverson Estimation What to say when asked for an estimate “I’ll get back to you” Pragmatic Programmer Deadly sins material adapted.
Overview of COCOMO Reporter:Hui Zhang
Effort Estimation Has been an “art” for a long time because
University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 1 Trends in Productivity and COCOMO Cost Drivers over the.
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.
CSE 403, Spring 2007, Alverson Estimation What to say when asked for an estimate “I’ll get back to you” Pragmatic Programmer Deadly sins material adapted.
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.
University of Southern California Center for Systems and Software Engineering Reducing Estimation Uncertainty with Continuous Assessment: Tracking the.
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.
Project Manager:PATS Project Manager Estimator:Peter Project Manager Start Date:1/1/2010 PATS Software PATS Project Team.
University of Southern California Center for Systems and Software Engineering 1 © USC-CSSE Integrating Case-Based, Analogy-Based, and Parameter-Based Estimation.
بشرا رجائی برآورد هزینه نرم افزار.
COCOMO Software Cost Estimating Model Lab 4 Demonstrator : Bandar Al Khalil.
THE FAMU-CIS ALUMNI SYSTEM
Project Cost Management
Estimate Testing Size and Effort Using Test Case Point Analysis
Appendix B Agile Methodologies
Globey's World Abstract End-Product Description Technical Approach
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
Metrics and Terms SLOC (source lines of code)
Cost Estimation with COCOMO II
Tutorial: Software Cost Estimation Tools – COCOMO II and COCOTS
Pongtip Aroonvatanaporn CSCI 577b Spring 2011 March 25, 2011
Cost Estimation with COCOMO II
End-Product Description
Software Systems Cost 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.
Cost Estimation with COCOMO II
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.
Cost Estimation with COCOMO II
Proposed Approach and Considerations
COCOMO MODEL.
Presentation transcript:

1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern California Center for Software Engineering CSE USC

2 Outline Introduction Background Motivation Implementation Applications Conclusions University of Southern California Center for Software Engineering CSE USC

3 Outline Introduction Background Motivation Implementation Applications Conclusions University of Southern California Center for Software Engineering CSE USC

4 Introduction Common to estimate software cost and schedule by analogy to a previous project –Including projects that use Agile methods Certain key cost factors may change for next project Want a simple method of software cost estimation Goal: build a simple tool to achieve this objective University of Southern California Center for Software Engineering CSE USC

5 Outline Introduction Background Motivation Implementation Applications Conclusions University of Southern California Center for Software Engineering CSE USC

6 Agile Methods Typical approaches –Adaptive Software Development, Crystal methods, Extreme Programming, Feature Driven Development, and Scrum Definition of agile (Merriam-Webster) –Marked by the ready ability to move with quick easy grace Agile COCOMO II is marked by the ready ability to move quickly in giving estimates with easy grace University of Southern California Center for Software Engineering CSE USC

7 COCOMO II Cost Drivers University of Southern California Center for Software Engineering CSE USC ProductRequired Software Reliability Database Size Product Complexity Developed for Reusability Documentation Match to Life-Cycle Needs PlatformExecution Time Constraint Main Storage Constraint Platform Volatility PersonnelAnalyst Capability Programmer Capability Personnel Continuity Application Experience Platform Experience Language and Tool Experience ProjectUse of Software Tools Multisite Development Schedule

8 COCOMO II Scale Factors Precedentedness Development Flexibility Architecture/Risk Resolution Team Cohesion Process Maturity University of Southern California Center for Software Engineering CSE USC

9 Outline Introduction Background Motivation Implementation Applications Conclusions University of Southern California Center for Software Engineering CSE USC

10 COCOMO II Model Enter –Size (SLOC – source lines of code) –Cost Drivers –Scale Factors Produces –Effort (Person-Months) –Schedule (Months) –Staff (People) Problem: Most people don’t want to figure out the other parameters Solution: Focus on one or 2 parameters and not the others University of Southern California Center for Software Engineering CSE USC

11 (USC) COCOMO II Shortcomings Better suited for software cost experts Does not easily support cost estimation by analogy More knowledge is required to use Requires specification of many parameters Time-consuming to use User interface is more complicated Platform-dependent University of Southern California Center for Software Engineering CSE USC

12 Outline Introduction Background Motivation Implementation Applications Conclusions University of Southern California Center for Software Engineering CSE USC

13 Requirements Browser Compatibility –Internet Explorer 6.0+ –Netscape 6.2+ Supported Platforms –PC –Macintosh –Linux –UNIX University of Southern California Center for Software Engineering CSE USC

14 Initialization University of Southern California Center for Software Engineering CSE USC

15 Analogy Parameters Total Cost in Dollars Total Effort in Person-Months Productivity in Dollars / (Function Point) Productivity in Dollars / (Lines of Code) Productivity in (Function Points) / Person-Month Productivity in (Lines of Code) / Person-Month University of Southern California Center for Software Engineering CSE USC

16 Define the Cost Driver Adjustments University of Southern California Center for Software Engineering CSE USC

17 Define the Changes to Scale Factors University of Southern California Center for Software Engineering CSE USC

18 Compute Next Project’s Cost University of Southern California Center for Software Engineering CSE USC

19 Options 1. Change a Difference Cost Driver/Scale Factor 2. Change an Additional Cost Driver/Scale Factor 3. Go Back to the Initial Estimate 4. View Report 5. Estimate Another Project University of Southern California Center for Software Engineering CSE USC

20 Report University of Southern California Center for Software Engineering CSE USC

21 Online Help University of Southern California Center for Software Engineering CSE USC

22 Outline Introduction Background Motivation Implementation Applications Conclusions University of Southern California Center for Software Engineering CSE USC

23 Applications Example software applications –Business –Defense –Energy –Environmental –Space –Transportation Tradeoff analysis –Compare options with difference scenarios to compare the resulting cost University of Southern California Center for Software Engineering CSE USC

24 Outline Introduction Background Motivation Implementation Applications Conclusions University of Southern California Center for Software Engineering CSE USC

25 Conclusions Limitations –No file system capability for this tool –Report may be printed/saved, but no way to load/save values from a session using the tool –Need to use USC COCOMO II for such features Being beta-tested by CSE Affiliates to be released later Browser-independent Platform-independent University of Southern California Center for Software Engineering CSE USC