COCOMO II Demo and ARS Example

Similar documents
C S E USC. University of Southern California Center for Software Engineering

COCOMO II Model. Brad Clark CSE Research Associate 15th COCOMO/SCM Forum October 22, 1998 C S E USC

You document these in a spreadsheet, estimate them individually and compute the total effort required.

SENG380:Software Process and Management. Software Size and Effort Estimation Part2

A Comparative study of Traditional and Component based software engineering approach using models

Software Project Management. Software effort

COCOMO Summary. USC-CSE COCOMO Team

COSYSMO: Constructive Systems Engineering Cost Model

3. December seminar cost estimation W 2002/2003. Constructive cost model Department of Information Technology University of Zurich

COCOMO II.2003 Calibration Status USC-CSE 1

MTAT Software Economics. Session 6: Software Cost Estimation

COCOMO III. Brad Clark, PhD USC Center for Systems and Software Engineering 2017 Annual Research Review April 4, 2017

CORADMO and COSSEMO Driver Value Determination Worksheet

Chapter 1: Introduction

Software Engineering Economics (CS656)

A Process for Mapping COCOMO Input Parameters to True S Input Parameters

Software cost estimation

Systems Cost Modeling

DRAFT. Effort = A * Size B * EM. (1) Effort in person-months A - calibrated constant B - scale factor EM - effort multiplier from cost factors

SOFTWARE EFFORT AND SCHEDULE ESTIMATION USING THE CONSTRUCTIVE COST MODEL: COCOMO II

COCOMO II Bayesian Analysis

Software cost estimation

COCOMO II Model Definition Manual

Cost Model Comparison Report

RESULTS OF DELPHI FOR THE DEFECT INTRODUCTION MODEL

Software Engineering

Software User Manual Version 3.0. COCOMOII & COCOTS Application. User Manual. Maysinee Nakmanee. Created by Maysinee Nakmanee 2:07 PM 9/26/02 1

COCOMO I1 Status and Plans

An Empirical Study of the Efficacy of COCOMO II Cost Drivers in Predicting a Project s Elaboration Profile

Fundamental estimation questions. Software cost estimation. Costing and pricing. Software cost components. Software pricing factors

CSCI 510 Midterm 1, Fall 2017

Life Cycle Plan (LCP)

Software Cost Metrics Manual

COCOMO II Based Project Cost Estimation and Control

CHAPTER 6 AN ANALYSIS OF EXISTING SOFTWARE ESTIMATION TECHNIQUES

Determining How Much Software Assurance Is Enough?

Life Cycle Plan (LCP)

Vrije Universiteit Amsterdam Faculty of Exact Sciences. Exam: Software Project Management Version A. Dr. Nelly Condori-Fernandez. Date: May 27, 2015

Project Plan: MSE Portfolio Project Construction Phase

COCOMO 1 II and COQUALMO 2 Data Collection Questionnaire

CSCI 510 Final Exam, Fall 2017 v10 of solution & rubric Monday, December 11, questions, 300 points

Lecture 7 Project planning part 2 Effort and time estimation

SOFTWARE ENGINEERING. Topics covered 1/20/2015. Chapter 3 - Project Management. Risk management Managing people Project cost Project plan & schedule

Chapter 5 Estimate Influences

Communication Model for Cooperative Robotics Simulator. Project Plan. Version 1.0

The Rosetta Stone: Making COCOMO 81 Files Work With COCOMO II

IFCnSSCM-23. Realistic Software Cost Estimation for F6 Fractionated Space Systems. A. Winsor Brown, Ramin Moazeni {AWBrown,

The software process

Calibrating the COCOMO II Post-Architecture Model

Software Estimation Experiences at Xerox

II. Software Life Cycle. Laurea Triennale in Informatica Corso di Ingegneria del Software I A.A. 2006/2007 Andrea Polini

Software Reuse Economics

COCOMO II Status and Extensions. Barry Boehm, USC COCOMO / SCM Forum #13 October 7,1998. Outline

Elaboration Cost Drivers Workshop. 18 th COCOMO / SCE Forum October 2003

Objectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes

Life Cycle Plan (LCP)

Life Cycle Plan (LCP)

User Manual. COCOMO II.2000 Post-Architecture Model Spreadsheet Implementation (Microsoft Excel 1997)

Software Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1

USC COCOMOII Reference Manual. University of Southern California

Life Cycle Plan (LCP)

SENG Software Reliability and Software Quality Project Assignments

Factors Influencing System-of-Systems Architecting and Integration Costs

Life Cycle Plan (LCP)

Lecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation

Software Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models

Topics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering

A Cost Model for Ontology Engineering

Software Engineering Economics: Cost-Effectiveness Analysis

RT 6 Software Intensive Systems Data Quality and Estimation Research in Support of Future Defense Cost Analysis

Life Cycle Plan (LCP)

CORADMO Constructive Rapid Application Development Model. Cyrus Fakharzadeh

Synthesis of Existing Cost Models to Meet System of Systems Needs

LADOT SCANNING. Team 8. Team members Primary Role Secondary Role. Aditya Kumar Feasibility Analyst Project Manager

A Value-Based Orthogonal Framework for Improving Life-Cycle Affordability

Headquarters U.S. Air Force

Life Cycle Plan (LCP)

Component-Based Software Engineering. ECE493-Topic 5 Winter Lecture 27 Component Based Development Process (Part A)

Technology Impact Analysis Tool. A. Winsor Brown

Life Cycle Plan (LCP)

Addressing New Technologies

CORADMO: A Software Cost Estimation Model for RAD Projects

COSYSMO: A Systems Engineering Cost Model

Life Cycle Plan (LCP)

Modeling Software Defect Introduction

Cost Estimation for Secure Software & Systems Workshop Introduction

Evaluation of Calibration Techniques to Build Software Cost Estimation Models

Life Cycle Plan (LCP)

COCOTS: a COTS software integration cost model - model overview and preliminary data findings

Software Technology Conference

Question Paper Solution (75:25), April 2015 Subject : Software Project Management

ETSF01: Software Engineering Process Economy and Quality. Chapter Five. Software effort estimation. Software Project Management

Application Examples

CS SOFTWARE ENGINEERING QUESTION BANK

Life Cycle Plan (LCP)

Ilities Tradespace and Affordability Program (itap)

Life Cycle Plan (LCP)

Software Estimation Is the problem solved? Sanathanan Rajagopal CAAS

Life Cycle Plan (LCP) PicShare. Team 02

Software Economics Homework I

Transcription:

COCOMO II Demo and ARS Example CS 566 Software Management and Economics Lecture 5 (Madachy 2005; Chapter 3, Boehm et al. 2000) Ali Afzal Malik

Outline USC COCOMO II tool demo Overview of Airborne Radar System (ARS) Usage of different COCOMO sub-models within an evolutionary spiral development process Estimation of reuse, modification, COTS, and automated translation Refinement of (aggregate) estimates Iterative development Summary References 6/23/2008 LUMS 2

USC COCOMO II Demo 6/23/2008 LUMS 3

ARS Estimation Use Applications Composition, Early Design and Post-Architecture submodels Two Post-Architecture estimates are demonstrated: top-level and detailed scale drivers apply to overall system in both estimates cost drivers are rated for the aggregate system in the top-level estimate (17 ratings) cost drivers are refined for each individual software component in the detailed estimate (17*6 components=102 ratings) 6/23/2008 LUMS 4

ARS System Overview display workstation and console user input graphics commands central computer radar control commands received radar data radar unit computer radar other user commands other sensor data 6/23/2008 LUMS 5

Software Components Radar Unit Control controls radar hardware Radar Item Processing extracts information returned from radar to identify objects Radar Database maintains radar object tracking data Display Manager high level displays management Display Console user input device interface and primitive graphic processing Built In Test hardware monitoring and fault localization 6/23/2008 LUMS 6

COCOMO Coverage in Evolutionary Lifecycle Process Development Phase ARS Product Milestone COCOMO Sub-model Inception Prototype Applications Composition Elaboration Breadboard Early Design Construction Initial Operating Capability (IOC) * both top-level and detailed estimates shown Post- Architecture* 6/23/2008 LUMS 7

Prototype Size and Effort Component Size (Application Points) Estimated Reuse New Application Points (NAP) Radar Unit Control 11 20 % 8.8 Radar Item Processing 65 30 % 45.5 Radar Database 23 0 % 23 Display Manager 42 0 % 42 Display Console 17 0 % 17 Built In Test 0 0 % 0 TOTAL 136.3 Productivity is high at 25 NAP/PM Effort = NAP/ Productivity = 136.3/25 = 5.45 PM (or 23.6 person-weeks) Personnel = 23.6 person-weeks/6 weeks ~ 4 full-time personnel 6/23/2008 LUMS 8

Scale Factors for Breadboard Factor Precedentedness (PREC) Development Flexibility (FLEX) Architecture/Risk Resolution (RESL) Team Cohesion (TEAM) Process Maturity (PMAT) Rating Nominal Low High Nominal Nominal 6/23/2008 LUMS 9

Early Design Cost Drivers for Breadboard Factor Product Reliability and Complexity (RCPX) Required Reuse (RUSE) Platform Difficulty (PDIF) Personnel Capability (PERS) Personnel Experience (PREX) Facilities (FCIL) Schedule (SCED) Rating High Very High High High Nominal Nominal Nominal 6/23/2008 LUMS 10

Breadboard System Size Calculations Component Size (SLOC) Language Type REVL (%) DM CM IM AA SU UNFM AAM Equivalent Size (SLOC) Radar Unit Control Radar Item Processing 4500 Ada 95 New 10 - - - - - - - 4950 1238 Ada 95 Reused 10 0 0 30 1 - - 10 136 19110 Ada 95 New 20 - - - - - - - 22932 25450 Ada 95 Translate 0 d Radar Database 6272 Ada 95 New 12 - - - - - - 0 7025 3222 Ada 95 Modified 12 15 20 50 2 15.1 29.81 1076 Display Manager 12480 Ada 95, C New 9 - - - - - - - 13603 18960 Ada 95, C Reused 9 0 0 25 2 - - 9.5 1963 24566 C COTS 9 0 0 20 0-6 1607 Display Console 5400 C, microcode 2876 C, microcode Built In Test 4200 Ada 95, assembler New 7 - - - - - - - 5778 COTS 7 0 0 20 0 - - 6 185 New 15 - - - - - - - 4830 TOTAL 64084 6/23/2008 LUMS 11

Early Design Estimate for Breadboard 6/23/2008 LUMS 12

ARS Full Development for IOC Use Post-Architecture estimation model same general techniques as the Early Design model for the Breadboard system, except for elaborated cost drivers Two estimates are demonstrated: top-level and detailed scale drivers apply to overall system in both estimates cost drivers are rated for the aggregate system in the top- level estimate (17 ratings) cost drivers are refined for each individual software component in the detailed estimate (17*6 components=102 ratings) 6/23/2008 LUMS 13

ARS Top-Level Size Calculations Component Size (SLOLanguageType REVL (%DM (%) CM (%) IM (%) AA SU UNFM AAF (%) AAM (%)eq size Radar Unit Control 3215 Ada new 2 0 0 0 0 0 0 0 0 3279 500 Ada modified 2 30 30 40 6 33 0.4 33 47.712 243 5738 Ada reused 2 0 0 40 0 0 0 12 12 702 Radar Item Processing 13715 Ada new 15 0 0 0 0 0 0 0 0 15772 11500 Ada modified 15 5 14 40 2 30 0.4 18.2 24.568 3249 58320 Ada translated* 0 0 0 Radar Database 12200 Ada new 6 0 0 0 0 0 0 0 0 12932 9494 Ada reused 6 40 0 0 0 12 12 1208 Display Manager 15400 Ada, C new 4 0 0 0 0 0 0 0 0 16016 31440 Ada, C reused 4 0 0 40 0 0 0 12 12 3924 24566 C COTS 4 0 0 40 0 0 0 12 12 3066 Display Console 13200 C new 4 0 0 0 0 0 0 0 0 13728 1800 C modified 4 20 20 40 2 30 0.4 26 34.24 641 2876 C, microccots 4 0 0 40 0 0 0 12 12 359 Built In Test 16000 Ada, assenew 10 0 0 0 0 0 0 0 0 17600 4200 Ada, assereused 10 0 0 40 0 0 0 12 12 554 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 totals 224164 93274 6/23/2008 LUMS 14

Post-Architecture Estimate for IOC (Top-level) 6/23/2008 LUMS 15

Post-Architecture Estimate for IOC (Detailed) 6/23/2008 LUMS 16

Sample Incremental Estimate 6/23/2008 LUMS 17

Incremental COCOMO Costar (commercial tool) provides comprehensive implementation 6/23/2008 LUMS 18

Increment Phasing 6/23/2008 LUMS 19

Increment Summary 6/23/2008 LUMS 20

Summary Learned the basics of USC COCOMO II ARS example Use of COCOMO sub-models for differing lifecycle phases and levels of detail Incremental development 6/23/2008 LUMS 21

References Raymond J. Madachy, EC-6 COCOMO II: Airborne Radar System Example, CS 510 Lecture, 2005. Barry W. Boehm et al., Software Cost Estimation with COCOMO II, Prentice Hall PTR, 2000. 6/23/2008 LUMS 22