COCOMO II Database Brad Clark Center for Software Engineering Annual Research Review March 11, 2002.

Slides:



Advertisements
Similar presentations
Making the Case for Metadata at SRS-NSF National Science Foundation Division of Science Resources Statistics Jeri Mulrow, Geetha Srinivasarao, and John.
Advertisements

Use of Estimation Methods on finished projects. Comparative Evaluation between the theorical estimation and the real time of development. Alejandro Fernández.
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
COSYSMO 2.0 Workshop Summary (held Monday, March 17 th 2008) USC CSSE Annual Research Review March 18, 2008 Jared Fortune.
USC 21 st International Forum on Systems, Software, and COCOMO Cost Modeling Nov 2006 University of Southern California Center for Software Engineering.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
Integration of Software Cost Estimates Across COCOMO, SEER- SEM, and PRICE-S models Tom Harwick, Engineering Specialist Northrop Grumman Corporation Integrated.
University of Southern California Center for Systems and Software Engineering Productivity Data Analysis and Issues Brad Clark, Thomas Tan USC CSSE 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.
COSOSIMO* Workshop 13 March 2006 Jo Ann Lane University of Southern California Center for Software Engineering CSE Annual.
COCOMO II Calibration Brad Clark Software Metrics Inc. Don Reifer Reifer Consultants Inc. 22nd International Forum on COCOMO and Systems / Software Cost.
Smi COCOMO II Calibration Status COCOMO Forum October 2004.
Affiliate Feedback and Discussion 1. Future Research: COSYSMO Updated data collection effort Quantifying the effect of schedule Harmonizing across software.
Database PowerPoint Guy Wade Comm 165 Guy Wade Comm 165.
Ch8: Management of Software Engineering. 1 Management of software engineering  Traditional engineering practice is to define a project around the product.
Constructive COTS Model (COCOTS) Status Chris Abts USC Center for Software Engineering Annual Research Review Annual Research Review.
University of Southern California Center for Systems and Software Engineering Building Cost Estimating Relationships for Acquisition Decision Support Brad.
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
1 CORADMO in 2001: A RAD Odyssey Cyrus Fakharzadeh 16th International Forum on COCOMO and Software Cost Modeling University of Southern.
University of Southern California Center for Software Engineering CSE USC USC-CSE Annual Research Review COQUALMO Update John D. Powell March 11, 2002.
USC 21 st International Forum on Systems, Software, and COCOMO Cost Modeling Nov 2006 University of Southern California Center for Software Engineering.
Costar & SystemStar Estimation Tools Dan Ligett Softstar Systems (603)
University of Southern California Center for Systems and Software Engineering Software Cost Estimation Metrics Manual 26 th International Forum on COCOMO.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 Reuse and Maintenance Estimation Vu Nguyen March 17, 2009.
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 AFCAA Database and Metrics Manual Ray Madachy, Brad Clark, Barry Boehm, Thomas.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy USC Center for Systems and Software Engineering
USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering USC Affiliates Code Counter News USC Annual Research.
April 27, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #3 Tuesday, April 27, 2004.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.
The Art and Science of Estimating Software Development Cost Glenn Briskin Partner, Sierra Systems Group A. Nicklas Malik Technical Architect Certified.
Information System Economics Software Project Cost Estimation.
COCOMO-SCORM: Cost Estimation for SCORM Course Development
1 Beyond California Water Plan Update 2005 California Water and Environmental Modeling Forum Annual Meeting, March 3 rd, 2005.
Project Management Estimation. LOC and FP Estimation –Lines of code and function points were described as basic data from which productivity metrics can.
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.
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.
Database A database program is a piece of software to organize and sort information. It creates an electronic list of information that can be sorted very.
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.
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.
Group 6. What is data redundancy? Data redundancy occurs in database systems which have a field that is repeated in two or more tables... Data redundancy.
Software Project Planning Part II. Troutman's Postulates Profanity is the one language understood by all programmers. Not until a program has been in.
Database Management Systems.  Database management system (DBMS)  Store large collections of data  Organize the data  Becomes a data storage system.
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.
Unit 5—HS 305 Research Methods in Health Science
SOFTWARE PROCESS AND PROJECT METRICS. Topic Covered  Metrics in the process and project domains  Process, project and measurement  Process Metrics.
Overview of COCOMO Reporter:Hui Zhang
Copyright , Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M18 - Version 9.01 SMU CSE 7315 Planning and Managing a Software Project.
University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 1 Trends in Productivity and COCOMO Cost Drivers over the.
Empirical Estimation Models Based upon historic data Basic Structure E = A + B * (ev) C where A, B, c are empirical constants ‘ev’ is the effort in terms.
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
CISB113 Fundamentals of Information Systems IS Development.
Smi COCOMO II Calibration Status USC-CSE Annual Research Review March 2004.
11/04/091 Some Topics Concerning The COSYSMOR Model/Tool John E. Gaffney, Jr Center For Process Improvement Excellence.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
University of Southern California Center for Systems and Software Engineering Reducing Estimation Uncertainty with Continuous Assessment Framework Pongtip.
COCOMO Software Cost Estimating Model Lab 4 Demonstrator : Bandar Al Khalil.
1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern.
Project Cost Management
COCOMO III Workshop Summary
Productivity Data Analysis and Issues
Metrics and Terms SLOC (source lines of code)
2006 Annual Research Review & Executive Forum
COCOMO II Security Extension Workshop Report
SLOC and Size Reporting
COSYSMO: Constructive Systems Engineering Cost Model
Software Sizing and Costing
COnstructive COst MOdel
Center for Software and Systems Engineering,
Presentation transcript:

COCOMO II Database Brad Clark Center for Software Engineering Annual Research Review March 11, 2002

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review2 COCOMO II 2002 Calibration Quality of data impacts the quality of the model - and good data is hard to come by Collected data has challenges –Level of detail –Consistency (project size, scope, units, ratings) –Known relationships 100 data points being evaluated –Not all of these data can be used –Need more data

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review3 Data Collection and Storage Data Collection –Paper collection form (most desirable because of detail) –From the USC COCOMO software tool estimation files Historical - whole project New data entered into a separate database from calibration data and evaluated. Data storage –Data is labeled with generic identifier –Stored in locked room –Access limited to 3 researchers Affiliate Organizations provide majority of data.

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review4 Level of Detail More detail permits normalization of data –In addition to effort, request effort by phase and labor categories included in data –In addition to duration, request number of phases covered and lifecycle description –In addition to size, request types of languages, type of SLOC count, modified code characteristics –Intermediate values of scale / cost driver ratings

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review5 Consistency of Data Project Size Effort Breadth and Depth Duration Breadth Process Maturity Rating(SF 5 ) Scale Driver Ratings (SF 1 -SF 4 ) Cost Driver Ratings (EM 1 -EM 17 ) COCOMO II Database

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review6 Checking for Known Relationships ?

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review7 Data Representation 111 Data fields across 5 tables –Additional data stored with effort, duration, size, scale and cost driver ratings Scale and Cost driver data stored symbolically –RELY value = H –RELY offset = 0.75

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review8 Data Flow for Producing a Calibration Symbolic Data Symbol Values Uncalibrated Numeric Data Calibration Process Calibration Process New COCOMO II Values New COCOMO II Values Adjustment Coefficients COCOMO II Database Accuracy Evaluation Accuracy Evaluation Calibrated Numeric Data

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review Calibration Data Status Currently screening data for incorporation into calibration database More project data needed –If you calibrate the COCOMO II model locally - would you consider letting us use your data to calibrate the scale / cost drivers? –If you have recently completed projects, would you consider filling out one of our data questionnaires? We can conduct a data collection interview over the phone. We plan to release calibration results by next COCOMO II forum (Fall 2002).

University of Southern California Center for Software Engineering CSE USC March 2002Annual Research Review10 For More Information Website – –Software for COCOMO II and COCOMO 81 models –Data collection form –Upcoming COCOMO events (Forum in Oct 2002) Book: –Software Cost Estimation with COCOMO II, 2000 Affiliates' Private Area