Activities During SPP Size Estimation

Slides:



Advertisements
Similar presentations
Estimation using COCOMO More Science, Less Art. COCOMO History COCOMO History Constructive Cost Model Dr. Barry Boehm TRW in 1970s COCOMO
Advertisements

Early Effort Estimation of Business Data-processing Enhancements CS 689 November 30, 2000 By Kurt Detamore.
Project Estimation: Metrics and Measurement
Metrics. A Good Manager Measures measurement What do we use as a basis? size? size? function? function? project metrics process metrics process product.
Software project management (intro)
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)
CSC 395 – Software Engineering
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
1 Cost Estimation CIS 375 Bruce R. Maxim UM-Dearborn.
Information System Economics Software Project Cost Estimation.
Cost22 1 Question of the day u If you were the boss, what would you do for cost estimation?
ECE 355: Software Engineering
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.
Chapter 6 : Software Metrics
Project Management Estimation. LOC and FP Estimation –Lines of code and function points were described as basic data from which productivity metrics can.
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.
Quality Assurance vs. Quality Control Quality Assurance An overall management plan to guarantee the integrity of data (The “system”) Quality Control A.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Engineering SM ? 1. Outline of this presentation What is SM The Need for SM Type of SM Size Oriented Metric Function Oriented Metric 218/10/2015.
Cost13 1 Cost Estimation Estimates based on LOC. cost13 2 Boehm's COCOMO u Software Engineering Economics u Prentice-Hall c1981 u type COCOMO in a search.
T. E. Potok - University of Tennessee CS 594 Software Engineering Lecture 3 Dr. Thomas E. Potok
Lecture 4 Software Metrics
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.
Software Project Planning Part II. Troutman's Postulates Profanity is the one language understood by all programmers. Not until a program has been in.
SEG3300 A&B W2004R.L. Probert1 COCOMO Models Ognian Kabranov.
SFWR ENG 3KO4 Slide 1 Management of Software Engineering Chapter 8: Fundamentals of Software Engineering C. Ghezzi, M. Jazayeri, D. Mandrioli.
Software Project Estimation IMRAN ASHRAF
Cost9a 1 Software Estimating Technology: A Survey Richard Stutzke Crosstalk, May96 text pp
©Ian Sommerville, adapted by Werner Wild 2004Project Management Slide 1 Software cost estimation u Predicting the resources required for a software development.
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.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
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.
540f07cost12oct41 Reviews Postmortem u Surprises? u Use white background on slides u Do not zip files on CD u Team leader should introduce team members.
Intro to Estimating Part Art, Part Science. Importance of Good Estimates Time (Realistic Deadlines) most software projects are late because the time was.
بشرا رجائی برآورد هزینه نرم افزار.
Cost9b 1 Living with Function Points Bernstein and Lubashevsky Text pp
Cost Estimation Software Quality Assurance and Testing.
Estimation Questions How do you estimate? What are you going to estimate? Where do you start?
Cost23 1 Question of the Day u Which of the following things measure the “size” of the project in terms of the functionality that has to be provided in.
Chapter-7 ESTIMATION FOR SOFTWARE PROJECTS
Chapter 33 Estimation for Software Projects
Software Engineering.
Software Estimating Technology: A Survey
For University Use Only
Why Do We Measure? assess the status of an ongoing project
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Software Project Estimation
Software Planning
Software Engineering.
Chapter 26 Estimation for Software Projects
COCOMO Model Basic.
Function Point.
Chapter 5: Software effort estimation- part 2
Software Metrics “How do we measure the software?”
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.
Why Do We Measure? assess the status of an ongoing project
COCOMO Models.
Chapter 33 Estimation for Software Projects
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Software Cost Estimation
Why Do We Measure? assess the status of an ongoing project
COnstructive COst MOdel
Why Do We Measure? assess the status of an ongoing project
Chapter 26 Estimation for Software Projects.
COCOMO MODEL.
Presentation transcript:

Activities During SPP Size Estimation Critical & Difficult area of the project planning Conventional Methods (LOC/FP Approach) compute LOC/FP using estimates of information domain values use historical effort for the project

LOC Example

LOC cont.. Include all lines When comments and blank lines are ignored Executable statements 13 (5-17)

Effort Effort=LOC/ Productivity =18/50 =0.36pm Suppose productivity of your Organization is 50 LOC/pm Labor rate is 8000Rs/pm Calculate Effort and Total cost of this increment Effort=LOC/ Productivity =18/50 =0.36pm Total cost=Rate * pm(Effort) =8000*0.36 =2880Rs. Cost per LOC=Total cost/LOC 2880/18=160Rs.

COCOMO Model Basic

The Constructive Cost Model (COCOMO) COCOMO is one of the most widely used software estimation models in the world It was developed by Barry Boehm in 1981 COCOMO predicts the effort and schedule for a software product development based on inputs relating to the size of the software and a number of cost drivers that affect productivity

COCOMO Models COCOMO has three different models that reflect the complexity: the Basic Model the Intermediate Model and the Detailed Model

Basic Model Applicable to small to medium sized software projects Use for a quick and rough estimates Three modes of software development are considered Organic Semi-detached Embedded

Organic Mode A small team of experienced programmers develop software in a very familiar environment Require little Innovation Size range ( 0-50 KLOC)

Semi-detached mode An intermediate mode between the organic mode and embedded mode Depending on the problem at hand, the team include the mixture of experienced and less experienced people Require medium Innovation Development environment is medium Size range ( 50 - 300 KLOC)

Embedded mode Project has tight constraints Hard to find experienced persons Require significant Innovation Development environment is complex Size range ( over 300 KLOC)

COCOMO: Some Assumptions Primary cost driver is the number of Delivered Source Instructions (DSI) / Delivered Line Of Code developed by the project COCOMO estimates assume that the project will enjoy good management by both the developer and the customer

Basic COCOMO Model: Formula The basic COCOMO equation E= ab (KLOC or KDSI) bb D= cb (E) db P=E/D where E is the effort applied in person-months, D is the development time in months, KLOC / KDSI is the estimated number of delivered lines of code for the project (expressed in thousands) P is the number of people required and ab, bb, cb and db are coefficients given in next slide.

Contd… Software project ab bb cb db Organic 2.4 1.05 2.5 0.38 Semi-detached 3.0 1.12 2.5 0.35 Embedded 3.6 1.20 2.5 0.32

Basic COCOMO Model: Equation

Basic COCOMO Model: Example E.g. 2: We have determined our project fits the characteristics of Semi-Detached mode We estimate our project will have 32,000 Delivered Source Instructions. Using the formulas, we can estimate: Effort = 3.0*(32) 1.12 = 146 man-months Schedule = 2.5*(146) 0.35 = 14 months Productivity = 32,000 DSI / 146 MM = 219 DSI/MM Average Staffing = 146 MM /14 months = 10 FSP

Basic COCOMO Model: Example E.g.1: Suppose that a project was estimated to be 400 KLOC. Calculate the effort and development time for each of the three modes I.e., organic, semidetached and embedded The basic COCOMO equation take the form: E = ab(KLOC) bb D = cb(E) db

FP based Estimation For above mentioned system Student can be registered Courses can be added/updated. Student can view courses Student can inquire his/her registration status

FP based Estimation Count Simple Average Complex External Inp 3 * 3 4 6 = 9 External Out 4 * 4 5 7 =16 External Inq 1 * 3 4 6 = 3 Internal Files 4 * 7 10 15 =28 External Files 0 * 5 7 10 = 0 Count Total= =56

Calculation of sum(Fi) Total of 0-5 rating of following 14 questions: Does the system require reliable back-up/recovery? 3 Are specialized data communications required? 2 Are there distributed processing functions? 0 Is performance critical? 2 Will run in heavily utilized operating environment? 1 On-line data entry required? 4 For on-line data entry, will it require multiple screens? 5 Are ILF’s updated on-line? 5 Are input, output, files, or inquiries complex? 2 Is the internal processing complex? 3 Is the code designed to be reusable? 0 Are conversion and installation included? 1 Is the system designed for installation in different organizations? 0 Is the application designed to facilitate change and ease of use? 1 20

The estimated number of FP is derived: FPestimated = count-total X [0.65 + 0.01 X Sum (Fi)] FPestimated = 56 * (0.65+.01*29) =52.64 or 53 If organizational average productivity = 5 FP/pm. Effort=FP/Productivity =53/5=10.6 person-months labor rate = 8000Rs. per month, Total Cost = labor rate * Person Month(Effort) =8000*10.6=84800Rs. Cost per FP=Total Cost/FP =84800/53=1600Rs.

Reference Pressman 15, 22,23 Section: 15.2.1,15.3, 22.2,23.6