April 27, 2004CS 562 - WPI1 CS 562 Advanced SW Engineering Lecture #3 Tuesday, April 27, 2004.

Slides:



Advertisements
Similar presentations
Software Cost Estimation
Advertisements

COST ESTIMATION TECHNIQUES AND COCOMO. Cost Estimation Techniques 1-)Algorithmic cost modelling 2-)Expert judgement 3-)Estimation by analogy 4)-Parkinsons.
Estimation using COCOMO More Science, Less Art. COCOMO History COCOMO History Constructive Cost Model Dr. Barry Boehm TRW in 1970s COCOMO
SW Economics & COCOMO II November 25, 2005 Jongmoon Baik, Ph.D. School of Engineering Information and Communications University.
On Representing Uncertainty In Some COCOMO Model Family Parameters October 27, 2004 John Gaffney Fellow, Software & Systems.
May 18, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #6 Tuesday, May 18, 2004.
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)
CSCI COCOMO Tutorial1 CS “Tutorial” Presentation: Software Cost Estimation Tools – COCOMO II and COCOTS A Winsor Brown and Ye.
Applying COCOMO II Effort Multipliers to Simulation Models 16th International Forum on COCOMO and Software Cost Modeling Jongmoon Baik and Nancy Eickelmann.
May 11, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #5 Tuesday, May 11, 2004.
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
April 13, 2004CS WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 – 7 pm Instructor: Diane Kramer.
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.
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.
COCOMO Models Ognian Kabranov SEG3300 A&B W2004 R.L. Probert.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Effort estimation.
University of Southern California Center for Systems and Software Engineering Cost Estimation with COCOMO II Barry Boehm CS 510, Fall 2015 v3: Slide 10.
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.
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.
Software Project Planning Part II. Troutman's Postulates Profanity is the one language understood by all programmers. Not until a program has been in.
1 Advanced Information Systems Development (SD3043) Project Management: Effort and Cost Estimation.
©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.
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.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
The COCOMO model An empirical model based on project experience. Well-documented, ‘independent’ model which is not tied to a specific software vendor.
1 COCOMO II Estimation Example: Transaction Processing System (TPS) II Based on Chapter 3 of COCOMO II book Used for new microeconomics examples –Replaces.
Cost Estimation Cost Estimation “The most unsuccessful three years in the education of cost estimators appears to be fifth-grade arithmetic. »Norman.
COCOMO Software Cost Estimating Model Lab 4 Demonstrator : Bandar Al Khalil.
THE FAMU-CIS ALUMNI SYSTEM
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION
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
COCOMO II Overview CSCI 510 Fall 2013 (c) USC CSSE.
COCOMO II Overview Barry Boehm CSCI 510 Fall 2011 (c) USC CSSE
COCOMO II Overview Barry Boehm CSCI (c) USC CSSE 2018/9/19.
Constructive Cost Model
Pongtip Aroonvatanaporn CSCI 577b Spring 2011 March 25, 2011
COCOMO II Overview Ray Madachy CSCI 510
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION
CMPUT Project Estimation
Cost Estimation with COCOMO II
Software Systems Cost Estimation
COCOMO Model Basic.
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
Cost Estimation with COCOMO II
Cost Estimation with COCOMO II
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 Models.
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.
COCOMO II Overview LiGuo Huang Computer Science and Engineering
Chapter 23 Software Cost Estimation
Cost Estimation with COCOMO II
Cost Estimation with COCOMO II
COnstructive COst MOdel
COCOMO MODEL.
Presentation transcript:

April 27, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #3 Tuesday, April 27, 2004

April 27, 2004CS WPI2 Class Format for Today Turn in Paper #1 Questions Lecture #3: Chapter 2 – Model Definition Exercise?

April 27, 2004CS WPI3 Questions? From last week’s class From the reading About the papers/project? Anything else? Everyone has books, all set with reading?

April 27, 2004CS WPI4 COCOMO II Model Definition Boehm, et al Chapter 2

April 27, 2004CS WPI5 Overview Model Types Post-Architecture Model Early Design Model How are these models defined? Review Estimation Equations on page 13: Amount of effort in Person-Months (Eq. 2.1) Amount of calendar time (Eq. 2.2) Review average-sized project example, p. 14

April 27, 2004CS WPI6 Sizing Types of size data used by COCOMO II: New code Reused code Automatically translated code How are the types of data treated differently?

April 27, 2004CS WPI7 Counting Source Lines of Code Best source for estimating new lines of code is historical data. What other options are given when lacking historical data? Support software, such as test drivers: Include/exclude? When to estimate, why? Use of SEI definition checklist (p. 16)

April 27, 2004CS WPI8 Unadjusted Function Points How do function points measure a project? Review user function types – Table 2.1, p. 17 What other factors are considered? 4-step procedure for determining UFPs Steps listed on page 18 Complexity levels & weights – Tables 2.2, 2.3 Relating UFPs to SLOC Conversion ratios in Table 2.4, p. 20 What are USR slots used for?

April 27, 2004CS WPI9 Nonlinear Reuse Effects Review Figure 2.2 & Equation 2.3, p. 21, and Figure 2.3, p. 22: What are these about? How & why are the effects nonlinear? Discuss reuse penalties: Software understanding Module-interface checking

April 27, 2004CS WPI10 Reuse Model Estimate amount of software to be adapted using 3 degree-of-modification factors: Percentage of design modified Percentage of code modified Percentage of integration effort required Review Equation 2.4, page 22 How does this relate to Tables 2.5, 2.6, 2.7? Also see ranges of reuse factors, Table 2.8, p. 26

April 27, 2004CS WPI11 Req’s Evolution & Volatility Adjust effective size of product caused by requirements evolution & volatility What factors contribute to such volatility? REVL = % of code discarded due to requirements evolution Review example, bottom of p. 25 How is this factor used to calculate size? See Equation 2.5, p. 26

April 27, 2004CS WPI12 Automatically Translated Code Estimating costs of reengineering and conversion, using tools for restructuring How do the tools impact the estimate factors? Equation 2.6, p. 27, shows how auto translation affects estimated effort What is AT? What is ATPROD? How are these factors calculated/estimated?

April 27, 2004CS WPI13 Sizing Software Maintenance Scope of SW maintenance Includes adding new capabilities & fixing or adapting existing capabilities Excludes major product rebuilds and development of sizable interfacing systems Review Equations 2.7 – 2.10, page 28

April 27, 2004CS WPI14 Effort Estimation Expressed in terms of person-months How is PM defined? How does this relate to TDEV? Review Eq. 2.11, p. 29, and discuss inputs to this equation: A, Size, E, Em i How do cost drivers fit in – individual project components, vs. project as a whole?

April 27, 2004CS WPI15 Scale Factors Economy vs. diseconomy of scale What produces one or the other effect? How does this impact effort estimation? Review Eq. 2.12, p. 31, and Table 2.10, p. 32 What are these about? Discuss example on bottom of p. 31 Review various scale factors in Sections through

April 27, 2004CS WPI16 Effort Multipliers Used in Eq. 2.11, what are they? Post-Architecture vs. Early Design EM’s Post-Architecture: RELY, DATA, CPLX, RUSE, DOCU, TIME, STOR, PVOL, ACAP, PCAP, PCON, APEX, PLEX, LTEX, TOOL, SITE, SCED Pages 41 – 51 Early Design: RCPX, PDIF, PERS, PREX, FCIL Pages 51 – 55

April 27, 2004CS WPI17 Multiple Modules & Schedules 6 steps for estimating multiple module effort Why not just sum up individual module efforts? Review steps listed on pages 55 – 57 Schedule estimation – Eq. 2.14, p. 57 Review factors that go into this equation More info in Appendix A.

April 27, 2004CS WPI18 SW Maintenance & Decisions How is SW Maintenance defined? What assumptions are made? Review Eq & 2.16, p. 59 Section 2.6 presents an example for an auto- parts company named UST. Discuss Sections – 2.6.9, pgs. 60 – 68. More examples (in 2 weeks) in Chapter 3.

April 27, 2004CS WPI19 For Next Time Read Chapters 1-9 of Brooks Come prepared to discuss Proposal 1 for term project due