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.

Slides:



Advertisements
Similar presentations
Project Estimation: Metrics and Measurement
Advertisements

Metrics for Process and Projects
Metrics for Process and Projects
Chapter 26 Estimation for Software Projects
Chapter 5 Software Project Planning
Project Estimation فرشاد آقابزرگی. Software Project Estimation.
Software Engineering II - Topic: Software Process Metrics and Project Metrics Instructor: Dr. Jerry Gao San Jose State University
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
A Good Manager Measures
Chapter 23 – Project planning Part 2. Estimation techniques  Organizations need to make software effort and cost estimates. There are two types of technique.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Project Planning CIS 375 Bruce R. Maxim UM-Dearborn.
1 Cost Estimation CIS 375 Bruce R. Maxim UM-Dearborn.
Project Planning Instructor: Dr. Jerry Gao. Project Planning Jerry Gao, Ph.D. Jan Software Scope - Obtaining Information Necessary for Scope -
Software Engineering: A Practitioner’s Approach
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.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Effort estimation.
1 Lecture 17: Chapter 26 Estimation for Software Projects Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman.
1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
10/27/20151Ian Sommerville.  Fundamentals of software measurement, costing and pricing  Software productivity assessment  The principles of the COCOMO.
1 Chapter 5 Software Project Planning. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling,
Managing Software Projects. The Project Reel J.S “Critical success factors in Software Projects”, IEEE Software, May 1999 Reel’s five step approach for.
Software Engineering Lecture 5 Software Project Planning 1.
Chapter 14: Maintenance Effort Models Omar Meqdadi SE 3860 Lecture 14 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Estimation - Software Metrics Managers frequently have to measure the productivity of software engineers.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Project Estimation techniques Estimation of various project parameters is a basic project planning activity. The important project parameters that are.
SOFTWARE PROCESS AND PROJECT METRICS. Topic Covered  Metrics in the process and project domains  Process, project and measurement  Process Metrics.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Estimation for Software Projects 1. Software Project Planning 2 The overall goal of project planning is to establish a pragmatic strategy for controlling,
CSC 480 Software Engineering Lecture 6 September 11, 2002.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Chapter 11: Alternative Approach - Purchasing Systems.
Software Project Management Lecture # 6. Outline Recap Remaining Topics of Chapter 23 Project Scheduling (Chapter 24)
Software Engineering (CSI 321) Project Planning & Estimation 1.
Advanced Software Engineering Lecture 4: Process & Project Metrics.
Intro to Estimating Part Art, Part Science. Importance of Good Estimates Time (Realistic Deadlines) most software projects are late because the time was.
CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
Chapter 5: Software effort estimation
Software Project Planning. Software Engineering Estimation Estimation The SPM begins with a set of activities that are collectively called Project planning.
THE FAMU-CIS ALUMNI SYSTEM
Software Project Management
Chapter 33 Estimation for Software Projects
Environment Assessment
Software Engineering Lecture #41
Software Engineering (CSI 321)
Software Project Sizing and Cost Estimation
Why Do We Measure? assess the status of an ongoing project
Software Engineering Lecture #2
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Software Engineering Lecture #39
Software Engineering Lecture #45
Software Metrics “How do we measure the software?”
Why Do We Measure? assess the status of an ongoing project
Software Engineering Lecture #26
Program Restructuring
Error Tracking Defect removal efficiency DRE = E / (E+D)
Defects yet to be fixed Defects Time Total reported defects
The Project Reel’s five step approach for successful projects
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
Why Do We Measure? assess the status of an ongoing project
Chapter 26 Estimation for Software Projects.
Software Engineering Lecture #28
Presentation transcript:

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 of lines of code or FP ‘E’ is the effort in terms of person months COCOMO - COnstructive COst MOdel E = 3.2 (KLOC) 1.05

Software Engineering II Lecture 17 Fakhar Lodhi

Recap

Software Project Estimation Project adjustment components –Problem complexity –Staff experience –Development environment and tools Factors – human, technical, environmental, political Estimation is difficult – not an exact science

Summary of Today’s Lecture

The Software Equation It’s a Dynamic Multivariable Estimation Model Assumes a specific distribution of effort over the life of the software development project Derived from productivity data collected for over 4000 projects

E = [LOC x B0.333/P]3 x (1/t4) E – effort in person months or person years t – project duration in months or years B – special skill factor –Increases slowly as the need for integration, testing, QA, documentation, management skills grow P – productivity parameter –Overall process maturity and management practices –The extent to which good SE practices are used –The level of programming language used –The state of the software environment –The skills and experience of the software team –The complexity of the application

Buy versus build Develop specification for function and performance of the desired software. Define measurable characteristics whenever possible Estimate internal cost and time to develop Select 3-4 candidate applications that best meet your specifications Select reusable software components that will assist in constructing the required application

Buy versus build Develop comparison matrix that presents a head-to- head comparison of key function. Alternatively, conduct benchmark tests to compare candidate software Evaluate each software package or component based on past product quality, vendor support, product direction, reputation, etc Contact other users of the software and ask for opinion

Buy versus build Delivery date Development Cost –Acquisition + customization Maintenance Cost