COCOMO II Demo and ARS Example
|
|
|
- Austen Bryan
- 6 years ago
- Views:
Transcription
1 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
2 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
3 USC COCOMO II Demo 6/23/2008 LUMS 3
4 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
5 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
6 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
7 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
8 Prototype Size and Effort Component Size (Application Points) Estimated Reuse New Application Points (NAP) Radar Unit Control % 8.8 Radar Item Processing % 45.5 Radar Database 23 0 % 23 Display Manager 42 0 % 42 Display Console 17 0 % 17 Built In Test 0 0 % 0 TOTAL 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
9 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
10 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
11 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 Ada 95 Reused Ada 95 New Ada 95 Translate 0 d Radar Database 6272 Ada 95 New Ada 95 Modified Display Manager Ada 95, C New Ada 95, C Reused C COTS Display Console 5400 C, microcode 2876 C, microcode Built In Test 4200 Ada 95, assembler New COTS New TOTAL /23/2008 LUMS 11
12 Early Design Estimate for Breadboard 6/23/2008 LUMS 12
13 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
14 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 Ada modified Ada reused Radar Item Processing Ada new Ada modified Ada translated* Radar Database Ada new Ada reused Display Manager Ada, C new Ada, C reused C COTS Display Console C new C modified C, microccots Built In Test Ada, assenew Ada, assereused totals /23/2008 LUMS 14
15 Post-Architecture Estimate for IOC (Top-level) 6/23/2008 LUMS 15
16 Post-Architecture Estimate for IOC (Detailed) 6/23/2008 LUMS 16
17 Sample Incremental Estimate 6/23/2008 LUMS 17
18 Incremental COCOMO Costar (commercial tool) provides comprehensive implementation 6/23/2008 LUMS 18
19 Increment Phasing 6/23/2008 LUMS 19
20 Increment Summary 6/23/2008 LUMS 20
21 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
22 References Raymond J. Madachy, EC-6 COCOMO II: Airborne Radar System Example, CS 510 Lecture, Barry W. Boehm et al., Software Cost Estimation with COCOMO II, Prentice Hall PTR, /23/2008 LUMS 22
C S E USC. University of Southern California Center for Software Engineering
COCOMO II: Airborne Radar System Example Dr. Ray Madachy C-bridge Internet Solutions Center for Software Engineering 15th International Forum on COCOMO and Software Cost Modeling October 24, 2000 C S E
COCOMO II Model. Brad Clark CSE Research Associate 15th COCOMO/SCM Forum October 22, 1998 C S E USC
COCOMO II Model Brad Clark CSE Research Associate 15th COCOMO/SCM Forum October 22, 1998 Brad@Software-Metrics.com COCOMO II Model Overview COCOMO II Overview Sizing the Application Estimating Effort Estimating
You document these in a spreadsheet, estimate them individually and compute the total effort required.
Experience-based approaches Experience-based techniques rely on judgments based on experience of past projects and the effort expended in these projects on software development activities. Typically, you
SENG380:Software Process and Management. Software Size and Effort Estimation Part2
SENG380:Software Process and Management Software Size and Effort Estimation Part2 1 IFPUG File Type Complexity Table 1 External user type External input types External output types Low Average High 3 4
A Comparative study of Traditional and Component based software engineering approach using models
A Comparative study of Traditional and Component based software engineering approach using models Anshula Verma 1, Dr. Gundeep Tanwar 2 1, 2 Department of Computer Science BRCM college of Engineering and
Software Project Management. Software effort
Software Project Management Chapter Five Software effort estimation 1 Objectives The lecture discusses: why estimating is problematic (or challenging ) the main generic approaches to estimating, including:
COCOMO Summary. USC-CSE COCOMO Team
K. Appendix 1. COCOMO II Summary COCOMO Summary Constructive Cost Model(COCOMO) is USC-CSE COCOMO Team Abstract 1-1 Table of Contents 1 Introduction...3 2 Overall Model Definition...3 2.1 COCOMO II Models
COSYSMO: Constructive Systems Engineering Cost Model
COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual Research Review February 6, 2001 Outline Background Scope Proposed Approach Strawman Model Size & complexity Cost & schedule
3. December seminar cost estimation W 2002/2003. Constructive cost model Department of Information Technology University of Zurich
I 3. December 2002 seminar cost estimation W 2002/2003 COCOMO Constructive cost model Department of Information Technology University of Zurich Nancy Merlo-Schett Nancy Merlo-Schett, Department of Information
COCOMO II.2003 Calibration Status USC-CSE 1
COCOMO II.2003 Calibration Status 2003-3-19 USC-CSE 1 Outline Introduction to COCOMO II COCOMO II.2003 Calibration Conclusion 2003-3-19 USC-CSE 2 COCOMO II Model Usage COCOMO II Estimation Endpoints I
MTAT Software Economics. Session 6: Software Cost Estimation
MTAT.03.244 Software Economics Session 6: Software Cost Estimation Marlon Dumas marlon.dumas ät ut. ee Outline Estimating Software Size Estimating Effort Estimating Duration 2 For Discussion It is hopeless
COCOMO III. Brad Clark, PhD USC Center for Systems and Software Engineering 2017 Annual Research Review April 4, 2017
COCOMO III Brad Clark, PhD USC 2017 Annual Research Review April 4, 2017 The COCOMO III Project COCOMO (COnstructure COst MOdel) is the most widely used, free, open source software cost estimation model
CORADMO and COSSEMO Driver Value Determination Worksheet
1. COCOMO Stage Schedule and Effort MODEL (COSSEMO) COSSEMO is based on the lifecycle anchoring concepts discussed by Boehm 3. The anchor points are defined as Life Cycle Objectives (LCO), Life Cycle Architecture
Chapter 1: Introduction
1.1 What is COCOMO? COCOMO (COnstructive COst MOdel) is a screen-oriented, interactive software package that assists in budgetary planning and schedule estimation of a software development project. Through
Software Engineering Economics (CS656)
Software Engineering Economics (CS656) Software Cost Estimation w/ COCOMO II Jongmoon Baik Software Cost Estimation 2 You can not control what you can not see - Tom Demarco - 3 Why Estimate Software? 30%
A Process for Mapping COCOMO Input Parameters to True S Input Parameters
A Process for Mapping Input s to Input s Agenda > Overview > Rosetta Stone II > Analysis > Summary 2 Overview > Initial Comparison and Assessment was Completed by USC Center for Systems & Software Engineering
Software cost estimation
Software cost estimation Joseph Bonello (based on slides by Ian Sommerville) Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for software productivity
Systems Cost Modeling
Systems Cost Modeling Affiliate Breakout Group Topic Gary Thomas, Raytheon 0 1900 USC Center for Software Engineering Sy~C~stModelingBreakoutTopicVisual-v0-1 vl.o - 10/27/00 University of Southern California
DRAFT. Effort = A * Size B * EM. (1) Effort in person-months A - calibrated constant B - scale factor EM - effort multiplier from cost factors
1.1. Cost Estimation Models Parametric cost models used in avionics, space, ground, and shipboard platforms by the services are generally based on the common effort formula shown in Equation 1. Size of
SOFTWARE EFFORT AND SCHEDULE ESTIMATION USING THE CONSTRUCTIVE COST MODEL: COCOMO II
SOFTWARE EFFORT AND SCHEDULE ESTIMATION USING THE CONSTRUCTIVE COST MODEL: COCOMO II Introduction Jongmoon Baik, Sunita Chulani, Ellis Horowitz University of Southern California - Center for Software Engineering
COCOMO II Bayesian Analysis
COCOMO II Bayesian Analysis Sunita Chulani (sdevnani@sunset.usc.edu) Center for Software Engineering University of Southern California Annual Research Review March 9, 1998 Outline Motivation Research Approach
Software cost estimation
Software cost estimation Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for software productivity assessment To explain why different techniques should
COCOMO II Model Definition Manual
COCOMO II Model Definition Manual Version 2.0 Table of Contents Acknowledgements...ii Copyright Notice...iii Warranty...iii 1. Introduction... 1 1.1 Overview... 1 1.2 Nominal-Schedule Estimation Equations...
Cost Model Comparison Report
Cost Model Comparison Report October 31, 2006 Update Version Prepared for: NASA Ames Prepared by: University of Southern California Center for Software Engineering 941 West 37 th Place Los Angeles, CA
RESULTS OF DELPHI FOR THE DEFECT INTRODUCTION MODEL
RESULTS OF DELPHI FOR THE DEFECT INTRODUCTION MODEL (SUB-MODEL OF THE COST/QUALITY MODEL EXTENSION TO COCOMO II) Sunita Devnani-Chulani USC-CSE Abstract In software estimation, it is important to recognize
Software Engineering
Software Engineering (CS550) Estimation w/ COCOMOII Jongmoon Baik WHO SANG COCOMO? The Beach Boys [1988] KoKoMo Aruba, Jamaica,ooo I wanna take you To Bermuda, Bahama,come on, pretty mama Key Largo, Montego,
Software User Manual Version 3.0. COCOMOII & COCOTS Application. User Manual. Maysinee Nakmanee. Created by Maysinee Nakmanee 2:07 PM 9/26/02 1
COCOMOII & COCOTS Application User Manual Maysinee Nakmanee Created by Maysinee Nakmanee 2:07 PM 9/26/02 1 Created by Maysinee Nakmanee 2:07 PM 9/26/02 2 Contents INTRODUCTION... 4 MODEL OVERVIEW... 5
COCOMO I1 Status and Plans
- A University of Southern California c I S IE I Center for Software Engineering COCOMO I1 Status and Plans Brad Clark, Barry Boehm USC-CSE Annual Research Review March 10, 1997 University of Southern
An Empirical Study of the Efficacy of COCOMO II Cost Drivers in Predicting a Project s Elaboration Profile
An Empirical Study of the Efficacy of COCOMO II Cost Drivers in Predicting a Project s Elaboration Profile Ali Afzal Malik, Barry W. Boehm Center for Systems and Software Engineering University of Southern
Fundamental estimation questions. Software cost estimation. Costing and pricing. Software cost components. Software pricing factors
Fundamental estimation questions Software cost estimation How much effort is required to complete an activity? How much calendar time is needed to complete an activity? What is the total cost of an activity?
CSCI 510 Midterm 1, Fall 2017
CSCI 510 Midterm 1, Fall 2017 Monday, September 25, 2017 3 questions, 100 points If registered DEN student, please circle: Yes Last Name: First Name: USC ID: Question 1 (30) Question 2 (40) Question 3
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) Women at Work Team No: 14 Sr no Name Role 1 Srikant Madhava Project Manager 2 Sanath Bhandary Operational Concept Engineer 3 Rohit Kudva Feasibility Analyst 4 Varma Maryala Life Cycle
Software Cost Metrics Manual
MOTIVATION Software Cost Metrics Manual Mr. Wilson Rosa Dr. Barry Boehm Mr. Don Reifer Dr. Brad Clark Dr. Ray Madachy 21 st Systems & Software Technology Conference April 22, 2009 DOD desires more credible
COCOMO II Based Project Cost Estimation and Control
3rd International Conference on Education, Management, Arts, Economics and Social Science (ICEMAESS 2015) COCOMO II Based Project Cost Estimation and Control Aihua Ren1, a, Yun Chen1, b 1 School of Computer
CHAPTER 6 AN ANALYSIS OF EXISTING SOFTWARE ESTIMATION TECHNIQUES
54 CHAPTER 6 AN ANALYSIS OF EXISTING SOFTWARE ESTIMATION TECHNIQUES This chapter describes the series of techniques that are implemented in the hybrid tool. Several programs, with Graphic User Interfaces
Determining How Much Software Assurance Is Enough?
Determining How Much Software Assurance Is Enough? Tanvir Khan Concordia Institute of Information Systems Engineering Ta_k@encs.concordia.ca Abstract It has always been an interesting problem for the software
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) City of Los Angeles Public Safety Applicant Resource Center Team No. 09 Team members and roles: Vaibhav Mathur Project Manager Preethi Ramesh Feasibility Analyst Arijit Dey Requirements
Vrije Universiteit Amsterdam Faculty of Exact Sciences. Exam: Software Project Management Version A. Dr. Nelly Condori-Fernandez. Date: May 27, 2015
Vrije Universiteit Amsterdam Faculty of Exact Sciences Exam: Software Project Management Version A Code: Coordinator: X_401093 Dr. Nelly Condori-Fernandez Date: May 27, 2015 Duration: Calculator allowed:
Project Plan: MSE Portfolio Project Construction Phase
Project Plan: MSE Portfolio Project Construction Phase Plans are nothing; planning is everything. Dwight D. Eisenhower September 17, 2010 Prepared by Doug Smith Version 2.0 1 of 7 09/26/2010 8:42 PM Table
COCOMO 1 II and COQUALMO 2 Data Collection Questionnaire
COCOMO 1 II and COQUALMO 2 Data Collection Questionnaire 1. Introduction The Center for Software Engineering at the University of Southern California is conducting research to update the software development
CSCI 510 Final Exam, Fall 2017 v10 of solution & rubric Monday, December 11, questions, 300 points
CSCI 510 Final Exam, Fall 2017 v10 of solution & rubric Monday, December 11, 2017 4 questions, 300 points If registered DEN student, please circle: Yes Last Name: First Name: USC ID: Question 1 (48) Question
Lecture 7 Project planning part 2 Effort and time estimation
1 Lecture 7 Project planning part 2 Effort and time estimation 22.2.2015 Lecture schedule 12.01 Introduction to the course and software engineering 19.01 Life-cycle/process models Project planning (part
SOFTWARE ENGINEERING. Topics covered 1/20/2015. Chapter 3 - Project Management. Risk management Managing people Project cost Project plan & schedule
SOFTWARE ENGINEERING Chapter 3 - Project Management Sep 2013 Chapter 2. Project Management 2 Topics covered Risk management Managing people Project cost Project plan & schedule 1 Sep 2013 Chapter 2. Project
Chapter 5 Estimate Influences
Dilbert Scott Adams Dilbert Scott Adams Chapter 5 Estimate Influences How much is 68 + 73? ENGINEER: It s 141. Short and sweet. MATHEMATICIAN: 68 + 73 = 73 + 68 by the commutative law of addition. True,
Communication Model for Cooperative Robotics Simulator. Project Plan. Version 1.0
Communication Model for Cooperative Robotics Simulator Project Plan Version 1.0 1 Introduction This document provides an overview of project plan for Communication Model for Cooperative Robotics Simulator
The Rosetta Stone: Making COCOMO 81 Files Work With COCOMO II
The Rosetta Stone: Making COCOMO 81 Files Work With COCOMO II Donald J. Reifer, Reifer Consultants, Inc. Barry W. Boehm, University of Southern California Sunita Chulani, University of Southern California
IFCnSSCM-23. Realistic Software Cost Estimation for F6 Fractionated Space Systems. A. Winsor Brown, Ramin Moazeni {AWBrown,
IFCnSSCM-23 Realistic Software Cost Estimation for F6 Fractionated Space Systems A. Winsor Brown, Ramin Moazeni {AWBrown, Moazeni}@CSSE.USC.edu & A W Brown BES/MSEE & USC CSE EC19b=PrsntRealisticSwCEforF6v2.doc
The software process
Software Processes The software process A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. A software process model is an abstract representation
Calibrating the COCOMO II Post-Architecture Model
Calibrating the COCOMO II Post-Architecture Model Sunita Devnani-Chulani Bradford Clark Barry Boehm Center for Software Engineering Computer Science Department University of Southern California Los Angeles,
Software Estimation Experiences at Xerox
15th International Forum on COCOMO and Software Cost Modeling Software Estimation Experiences at Xerox Dr. Peter Hantos Office Systems Group, Xerox 1 Theme Is making bad estimates a crime? No, but it is
II. Software Life Cycle. Laurea Triennale in Informatica Corso di Ingegneria del Software I A.A. 2006/2007 Andrea Polini
II. Software Life Cycle Laurea Triennale in Informatica Corso di Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process
Software Reuse Economics
Software Reuse Economics Barry Boehm DARPA Workshop January 14, 1997 http://sunset.usc.edu Barry Boehm - 1 Outline Motivation Software Reuse Economics Framework Return on Investment Elements Investments
COCOMO II Status and Extensions. Barry Boehm, USC COCOMO / SCM Forum #13 October 7,1998. Outline
COCOMO II Status and Extensions Barry Boehm, USC COCOMO / SCM Forum #13 October 7,1998 1 Mt98 WSCCSE 1 Outline COCOMO 11.1 998 Status and Plans Overview of Extensions COTS Integration (COCOTS) Quality:
Elaboration Cost Drivers Workshop. 18 th COCOMO / SCE Forum October 2003
Elaboration Cost Drivers Workshop 18 th COCOMO / SCE Forum October 200 Attendees Brad Clark (moderator) Mauricio Aguiar Michael Douglas Samuel Eiferman Stuart Garrett Dan Ligett Vicki Love Karen Lum Karen
Objectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
Life Cycle Plan (LCP)
LCP_FCP_F14a_T07_V2.0 Version 2.0 Life Cycle Plan (LCP) Mission Science irobots Team 07 Ashwini Ramesha Chen Li Farica Mascarenhas Jiashuo Li Ritika Khurana Siddhesh Rumde Sowmya Sampath Yun Shao OCE,
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) Mission Science Information and Data Management System 3.0 Team 03 Fei Yu: Project Manager, Life Cycle Planner Yinlin Zhou: Prototyper, Operational Concept Engineer Yunpeng Chen:
User Manual. COCOMO II.2000 Post-Architecture Model Spreadsheet Implementation (Microsoft Excel 1997)
User Manual COCOMO II.2000 Post-Architecture Model Spreadsheet Implementation (Microsoft Excel 1997) Center for Software Engineering University of Southern California 2000 USC C enter for Software Engineering
Software Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
USC COCOMOII Reference Manual. University of Southern California
USC COCOMOII.1997 Reference Manual University of Southern California This manual is compatible with USC-COCOMOII.1997 version 0. Copyright Notice This document is copyrighted, and all rights are reserved
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) LINGGGO 3 Chicheng Ren Software Architect Dahai Li Quality Focal Point Dashun Wen Life Cycle Planner Kraingkrai Bumroungruksa Prototyper
SENG Software Reliability and Software Quality Project Assignments
The University of Calgary Department of Electrical and Computer Engineering SENG 521 - Software Reliability and Software Quality Project Assignments Behrouz Far Fall 2012 (Revision 1.01) 1 Assignment no.
Factors Influencing System-of-Systems Architecting and Integration Costs
Paper # (unknown) Factors Influencing System-of-Systems Architecting and Integration Costs Jo Ann Lane University of Southern California Center for Software Engineering 941 W. 37th Place, SAL Room 328
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) City of Los Angeles Public Safety Applicant Resource Center Team No. 09 Team members and roles: Vaibhav Mathur Project Manager Preethi Ramesh Feasibility Analyst Arijit Dey Requirements
Lecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
Software Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
Topics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
A Cost Model for Ontology Engineering
A Cost Model for Ontology Engineering Elena Paslaru Bontas, Malgorzata Mochol AG Netzbasierte Informationssysteme paslaru@inf.fu-berlin.de mochol@inf.fu-berlin.de August 3, 2005 Technical Report B-05-03
Software Engineering Economics: Cost-Effectiveness Analysis
Software Engineering Economics: Cost-Effectiveness Analysis CS 566 Software Management and Economics Lecture 13 (Chapters 10 12, Boehm 1981; Boehm 2005) Ali Afzal Malik Software Decision Analysis Techniques
RT 6 Software Intensive Systems Data Quality and Estimation Research in Support of Future Defense Cost Analysis
RT 6 Software Intensive Systems Data Quality and Estimation Research in Support of Future Defense Cost Analysis A013 - Annual and Final Scientific Technical Report SERC 2012-TR-032 March 13, 2012 Dr. Barry
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) Yanomamo Interactive DVD/Online Team No. 6 Reetika Rastogi - Project Manager, Life Cycle Planner Rohit Mani - Requirements Engineer, Life Cycle Planner Sanjay Kutty - Feasibility
CORADMO Constructive Rapid Application Development Model. Cyrus Fakharzadeh
Constructive Rapid Application Development Model Cyrus Fakharzadeh fakharza@sunset.usc.edu 1999 USC 1 v1.2 11/03/0099 Outline Background Model Overview Schedule Drivers, Rating Scales 1999 USC 2 v1.2 11/03/0099
Synthesis of Existing Cost Models to Meet System of Systems Needs
Paper #128 Synthesis of Existing Cost Models to Meet System of Systems Needs Jo Ann Lane University of Southern California Center for Software Engineering 941 W. 37th Place, SAL Room 328 Los Angeles, CA
LADOT SCANNING. Team 8. Team members Primary Role Secondary Role. Aditya Kumar Feasibility Analyst Project Manager
Life Cycle Plan (LCP) LADOT SCANNING Team 8 Team members Role Role Aditya Kumar Feasibility Analyst Project Manager Anirudh Govil Project Manager Lifecycle Planner Corey Painter IIV&V Shaper Jeffrey Colvin
A Value-Based Orthogonal Framework for Improving Life-Cycle Affordability
A Value-Based Orthogonal Framework for Improving Life-Cycle Affordability Barry Boehm, Jo Ann Lane, Sue Koolmanojwong http://csse.usc.edu NDIA Systems Engineering Conference October 25, 2012 Outline Affordability
Headquarters U.S. Air Force
Headquarters U.S. Air Force Software Sizing Lines of Code and Beyond Air Force Cost Analysis Agency Corinne Wallshein June 2009 1 Presentation Overview About software sizing Meaning Sources Importance
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) Mental Math Team - 7 Isha Agarwal Prototyper, Life Cycle Planner, JingXing Cheng Kajal Taneja Operational Concept Engineer, UML Modeler, Kiranmai Ponakala, Life Cycle Planner, IIV
Component-Based Software Engineering. ECE493-Topic 5 Winter Lecture 27 Component Based Development Process (Part A)
Component-Based Software Engineering ECE493-Topic 5 Winter 2007 Lecture 27 Component Based Development Process (Part A) Ladan Tahvildari Assistant Professor Dept. of Elect. & Comp. Eng. University of Waterloo
Technology Impact Analysis Tool. A. Winsor Brown
O. Appendix 5. Technology Impact Analysis Tool Technology Impact Analysis Tool A. Winsor Brown Abstract The COCOMO RAD MODEL (CORADMO) is currently implemented in two parts: a front end staged 5-1 Table
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) Scriptonomics Team No - 7 Team Member USC Email Id Role Role Aditya Holikatti holikatt@usc.edu Feasibility Engineer Software Developer Alex Miller milleram@usc.edu IIV &V Website
Addressing New Technologies
c S I E 1 a COCOMO 2.0: Addressing New Technologies Barry Boehm I I th COCOMOISCM Forum October 10,1996 Barry Boehm - 1 C I S I E I Outline + Candidate Software Silver Bullets + Likely Future Software
CORADMO: A Software Cost Estimation Model for RAD Projects
CORADMO: A Software Cost Estimation Model for RAD Projects Cyrus Fakharzadeh fakharza@usc.edu and Barry Boehm ISPA/SCEA 2001 Presentation 1 Introduction RAD (Rapid Application Development) an application
COSYSMO: A Systems Engineering Cost Model
COSYSMO: A Systems Engineering Cost Model Ricardo Valerdi and Barry W. Boehm Abstract: Building on the synergy between Systems engineering and Software Engineering, we have developed a parametric model
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) Version 1.0 Life Cycle Plan (LCP) Software Quality Analysis as a Service (SQAaaS) Team No.1 Kavneet Kaur Requirement Engineer George Llames IIV & V Aleksandr Chernousov Life Cycle
Modeling Software Defect Introduction
Modeling Software Defect Introduction Sunita Devnani-Chulani (sdevnani@sunset.usc.edu) California Software Symposium November 7, 1997 OMO IISunita Devnani-Chulani chart 1 Presentation Outline Motivation
Cost Estimation for Secure Software & Systems Workshop Introduction
Cost Estimation for Secure Software & Systems Workshop Introduction Edward Colbert, Sr. Research Associate Dr. Barry Boehm, Director Center for System & Software Engineering {ecolbert, boehm}@csse.usc.edu
Evaluation of Calibration Techniques to Build Software Cost Estimation Models
ISSN:2320-0790 Evaluation of Calibration Techniques to Build Software Cost Estimation Models Safia Yasmeen 1, Prof.Dr.G.Manoj Someswar 2 1. Research Scholar, Mahatma Gandhi Kashi Vidyapith, Varnasi, U.P.,
Life Cycle Plan (LCP)
Cash Doctor 3.0 Team 12 Steven Helferich: Project Manager Kenneth Anguka: IIV&V Xichao Wang: Operational Concept Engineer Alisha Parvez: Life Cycle Planner Ekasit Jarussinvichai: Requirements Engineer
COCOTS: a COTS software integration cost model - model overview and preliminary data findings
COCOTS: a COTS software integration cost model - model overview and preliminary data findings Chris Abts, Barry W. Boehm, and Elizabeth Bailey Clark Abstract As the use of commercial-of-the-shelf (COTS)
Software Technology Conference
30 April 2003 Costing COTS Integration Software Technology Conference Salt Lake City Linda Brooks 1 Objective Provide a roadmap for doing an estimate for a Commercial Off-the-Shelf (COTS) software intensive
Question Paper Solution (75:25), April 2015 Subject : Software Project Management
Question Paper Solution (75:25), April 2015 Subject : Software Project Management Ques1. (a) Discuss the significance, of reducing the product size, on ROI (returns on investment). Explain, briefly, how
ETSF01: Software Engineering Process Economy and Quality. Chapter Five. Software effort estimation. Software Project Management
Software Project Management ETSF01: Software Engineering Process Economy and Quality Dietmar Pfahl Lund University Chapter Five Software effort estimation What makes a successful project? Cost/Schedule
Application Examples
4762ch03.qxd_tb 5/30/00 1:49 PM Page 83 3 Application Examples 3.1 INTRODUCTION This chapter provides a set of examples designed to show you how to use the COCOMO II model to develop estimates, perform
CS SOFTWARE ENGINEERING QUESTION BANK
CS6403 - SOFTWARE ENGINEERING QUESTION BANK UNIT I- SOFTWARE PRODUCT AND PROCESS Part - A (2 M ARKS) 1. What is the prime objective of software engineering? 2. Define software engineering paradigm. 3.
Life Cycle Plan (LCP)
Using Social Media/Mobile Devices to Bridge the Achievement Gap Team 2 Ying Yang, Project Manager/Life Cycle Planner Tianyin Zhou, Life Cycle Planner/Prototyper Ying Li, Operational Concept Engineer/Requirement
Ilities Tradespace and Affordability Program (itap)
Ilities Tradespace and Affordability Program (itap) By Barry Boehm, USC Russell Peak, GTRI 6 th Annual SERC Sponsor Research Review December 4, 2014 Georgetown University School of Continuing Studies 640
Life Cycle Plan (LCP)
Life Cycle Plan (LCP) < LEMA Pilot School Integrated Family Accountability System> PROJECT TITLE LEMA FAMILY ACCOUNTABILITY SYSTEM TEAM NO #04 TEAM MEMBERS & ROLES NAME ROLES Teawon Han Project Manager
Software Estimation Is the problem solved? Sanathanan Rajagopal CAAS
Software Estimation Is the problem solved? Sanathanan Rajagopal CAAS Content Difference between Software and Hardware estimation Why we think it is difficult to estimate software cost (Myths, Perception,
Life Cycle Plan (LCP) PicShare. Team 02
Life Cycle Plan (LCP) PicShare Team 02 Team Members Sultan Alsarra Adil cem Albayrak Julapat Julnual Charles Reitz Mohammad Almunea Aref Shafaeibejestan Andrea Brown Travis Weaver 12/7/15 Version History
Software Economics Homework I
Software Economics Homework I Function Point Analysis and Effort Estimation Martin Vels Raido Seene Rauno Kiss Tartu 2012 2 Table of Contents TABLE OF CONTENTS... 3 OVERVIEW... 5 SCOPE... 5 DOMAIN MODEL...