Estimating Size and Effort

Save this PDF as:

Size: px
Start display at page:

Transcription

1 Estimating Size and Effort Dr. James A. Bednar Dr. David Robertson SAPM Spring 2007: Estimation 1

2 Estimating SW Size and Effort Most methods for estimating the total effort required for a software project (to decide on schedule, staffing, and feasibility) depend on the size of the software project. Unfortunately, it is difficult to measure size meaningfully, it is difficult to estimate size in advance, and it is difficult to extrapolate from size to what we are really interested in. We will first look at methods for estimating size, then at how size can be used to estimate effort (e.g. using COCOMO). SAPM Spring 2007: Estimation 2

3 Three-Point Estimates If you just ask someone for an estimate of how long a task will take, the answers you get will vary enormously, depending on how they interpret the question. Worst case? Best case? Etc. Instead, estimates are typically done using three points: o = Optimistic estimate (best 2.5%) m = Most likely estimate p = Pessimistic estimate (worst 2.5%) SAPM Spring 2007: Estimation 3

4 Using Three-Point Estimates A single estimate can be computed from a three-point estimate as: E = o + 4m + p 6 SD = p o 6 These calculations are from the PERT method (discussed later), assuming that the actual values will have a Gaussian distribution. People still underestimate the pessimistic case (Vose 1996), but the results are more repeatable than simply asking for a single number at the start. (1) (2) SAPM Spring 2007: Estimation 4

5 Approaches to Estimating Size Through expert consensus (Wideband-Delphi) From historical population data (Fuzzy logic) From standard components (Component estimating) From a model of function (Function points) See Humphrey (2002) for more information on these methods and other more complicated ones. SAPM Spring 2007: Estimation 5

6 Wideband-Delphi Estimating 1. Group of experts: [E 1,..., E i,..., E n ] 2. All E i meet to discuss project 3. Each anonymously estimates size: [X 1,..., X i,..., X n ] 4. Each E i gets to see all X j (anonymously) 5. Stop if the estimates are sufficiently close together 6. Otherwise, back to step 2 Helps get a group of engineers committed to a particular schedule. SAPM Spring 2007: Estimation 6

7 Fuzzy-Logic Estimating Break previous products into categories by size: Range Nominal KLOC KLOC range included V Small Small Medium Large V Large Then look at the previous projects in each category and decide which category contains projects similar to this one. Problem: Only a very rough estimate, yet requires several relevant historical datapoints in each range (rare) SAPM Spring 2007: Estimation 7

8 Standard Component Estimating Gather historical data on types and sizes of key components For each type (i), guess how many you will need (M i ) Also guess largest (L i ) and smallest (S i ) extremes Estimated number (E i ) is a function of M i, L i and S i, e.g.: E i = (S i + 4M i + L i )/6 Total size calculated from estimated number and average size (X i ) of each type: X = i E ix i Helps break down a large project into more-easily guessable chunks. SAPM Spring 2007: Estimation 8

9 Function Point Estimating (1) Popular method based on a weighted count of common functions of software. The five basic functions are: Inputs : Sets of data supplied by users or other programs Outputs : Sets of data produced for users or other programs Inquiries : Means for users to interrogate the system Data files : Collections of records which the system modifies Interfaces : Files/databases shared with other systems SAPM Spring 2007: Estimation 9

10 Function Point Estimating (2) Function Count Weight Total Inputs Outputs Inquiries Data files Interfaces Total 135 May adjust function point total using influence factors. SAPM Spring 2007: Estimation 10

11 Estimating Total Effort Once we have the size estimate, we can try to estimate the total effort involved, e.g. in person-months, e.g. to decide on staffing levels. Unfortunately, the total amount of effort required depends on the staffing levels cf. The Mythical Man-Month (Brooks 1995). So it is easy to get stuck in circular reasoning. Still, with some big assumptions, it is possible to try to use historical experience with similarly sized projects. SAPM Spring 2007: Estimation 11

12 COCOMO Model The Constructive Cost Model (COCOMO; Boehm 1981) is popular for effort estimation. COCOMO is a mathematical equation that can be fit to measurements of effort for different-sized completed projects, providing estimates for future projects. COCOMO II (Boehm et al. 1995) is the current version (see but we will focus on the original simpler equation. All we are hoping to get is a rough (order of magnitude) estimate. SAPM Spring 2007: Estimation 12

13 Basic COCOMO Model In its simplest form COCOMO is: where: E = C P s M E is the estimated effort (e.g. in person-months) C is a complexity factor P is a measure of product size (e.g. KLOC) s is an exponent (usually close to 1) M is a multiplier to account for project stages SAPM Spring 2007: Estimation 13

14 Basic COCOMO Model Examples We ignore the multiplier, M, so E = C P s. Then we fit C and s to historical data from different types of projects: Simple (E = 2.4 P 1.05 ) : A well understood application developed by a small team. Intermediate (E = 3.0 P 1.12 ) : A more complex project for which team members have limited experience of related systems. Embedded (E = 3.6 P 1.20 ) : A complex project in which the software is part of a complex of hardware, software, regulations and operational constraints. SAPM Spring 2007: Estimation 14

15 Behavior of the Basic Examples 1000 Embedded Person months Intermediate Simple 0 0 K Lines of Source Code 120 SAPM Spring 2007: Estimation 15

16 Extending the COCOMO Model The basic examples didn t use the multiplier, M. M can be used to adjust the basic estimate by including expert knowledge of the specific attributes of this project. Potential attributes/constraints to consider: Product attributes (e.g. reliability) Computer attributes (e.g. memory constraints) Personnel attributes (e.g. programming language experience) Project attributes (e.g. project development schedule) SAPM Spring 2007: Estimation 16

17 COCOMO Multiplier Example 1 If the basic estimate is 1216 person-months, can add estimates of the effect of various constraints or attributes: Attribute Magnitude Multiplier Reliability V high 1.4 Complexity V high 1.3 Memory constraint High 1.2 Tool use Low 1.1 Schedule Accelerated 1.23 New E: = 3593 SAPM Spring 2007: Estimation 17

18 COCOMO Multiplier Example 2 Using the basic estimate of 1216 person-months, changing estimates of the constraints/attributes changes the result: Attribute Magnitude Multiplier Reliability V low 0.75 Complexity V low 0.7 Memory constraint None 1 Tool use High 0.9 Schedule Normal 1 New E: = 575 SAPM Spring 2007: Estimation 18

19 COCOMO Limitations 1 Like any mathematical model, COCOMO has two main potential types of error: model error and parameter error. Model error: Do projects really scale with KLOC as modeled? From the COCOMO II web site: The 1998 version of the model has been calibrated to 161 data points [projects]... Over those 161 data points, the 98 release demonstrates an accuracy of within 30% of actuals 75% of the time. Thus even looking retroactively, with accurate KLOC estimates, 25% of projects are more than 30% mis-estimated. SAPM Spring 2007: Estimation 19

20 COCOMO Limitations 2 Parameter estimation error: Can the various parameters be set meaningfully? E.g. result depends crucially on KLOC, which is difficult to estimate accurately. The other parameters can also be difficult to estimate for a new project, particularly at the beginning when scheduling and feasibility need to be decided. SAPM Spring 2007: Estimation 20

21 Estimation Limitations Model predictions can be sensitive to small changes in parameters, so be sure to perform a sensitivity analysis for different parameter estimates. In any case, early estimates are likely to be wrong, and should be revised once more data is available. Also, predictions can strongly affect the outcome: If estimate is too high, programmers may relax and work on side issues or exploring many alternatives If estimate is too low, quality may be sacrificed to meet the deadline SAPM Spring 2007: Estimation 21

22 Summary No size estimation method is foolproof or particularly accurate Even once size is available, hard to extrapolate to effort, cost, estimated schedule, etc. Estimates can be self-fulfilling or self-defeating Thus it is difficult to evaluate how well estimation is working, even retroactively Use an appropriate method for how much data you have if no data, then gut instinct estimation is reasonable Try to avoid depending on your estimates being accurate SAPM Spring 2007: Estimation 22

23 References Boehm, B. (1981). Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall. Boehm, B., Clark, B., Horowitz, E., Madachy, R., Shelby, R., & Westland, C. (1995). Cost models for future software life cycle processes: COCOMO 2.0. Annals of Software Engineering. Brooks, F. P., Jr. (1995). The Mythical Man-Month. Reading, MA: Addison-Wesley. Expanded reprint of 1975 edition. Humphrey, W. S. (2002). A Discipline for Software Engineering. Reading, MA: Addison-Wesley. SAPM Spring 2007: Estimation 22

24 Vose, D. (1996). Quantitative Risk Analysis: A Guide to Monte Carlo Simulation Modelling. John Wiley and Sons. SAPM Spring 2007: Estimation 22

Project Planning Objectives. Project Estimation. Resources. Software Project Estimation

Project Planning Objectives Project Estimation Providing a framework that allows managers to make responsible estimates of the resources and time required to build a software product. Determining the scope

Project Management. Week 4 Software Project Estimation & Metrics. Lecture Overview. Software Project Estimation

Project Management Week 4 Software Project Estimation & Metrics Lecture Overview The software estimation story Estimation process overview Size estimation Effort estimation Schedule estimation Ballpark

Cost Estimation Strategies COST ESTIMATION GUIDELINES

Cost Estimation Strategies Algorithmic models (Rayleigh curve Cost in week t = K a t exp(-a t 2 ) Expert judgment (9 step model presented later) Analogy (Use similar systems) Parkinson (Work expands to

Software Development: Tools and Processes. Lecture - 16: Estimation

Software Development: Tools and Processes Lecture - 16: Estimation Estimating methods analogy method direct estimating method Delphi technique PERT-type rolling window Constructivist Cost Model (CoCoMo)

Module 11. Software Project Planning. Version 2 CSE IIT, Kharagpur

Module 11 Software Project Planning Lesson 28 COCOMO Model Specific Instructional Objectives At the end of this lesson the student would be able to: Differentiate among organic, semidetached and embedded

Project Planning and Project Estimation Techniques. Naveen Aggarwal

Project Planning and Project Estimation Techniques Naveen Aggarwal Responsibilities of a software project manager The job responsibility of a project manager ranges from invisible activities like building

Finally, Article 4, Creating the Project Plan describes how to use your insight into project cost and schedule to create a complete project plan.

Project Cost Adjustments This article describes how to make adjustments to a cost estimate for environmental factors, schedule strategies and software reuse. Author: William Roetzheim Co-Founder, Cost

Lecture 14: Cost Estimation

Overview Project management activities Project costing Project scheduling and staffing Project monitoring and review General cost estimation rules Algorithmic Cost Modeling Function point model COCOMO

CS 458 - Homework 4 p. 1. CS 458 - Homework 4. To become more familiar with top-down effort estimation models, especially COCOMO 81 and COCOMO II.

CS 458 - Homework 4 p. 1 Deadline Due by 11:59 pm on Friday, October 31, 2014 How to submit CS 458 - Homework 4 Submit these homework files using ~st10/458submit on nrs-labs, with a homework number of

Chapter 23 Software Cost Estimation

Chapter 23 Software Cost Estimation Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 23 Slide 1 Software cost estimation Predicting the resources required for a software development process

Software cost estimation

Software cost estimation Sommerville Chapter 26 Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for software productivity assessment To explain why different

Article 3, Dealing with Reuse, explains how to quantify the impact of software reuse and commercial components/libraries on your estimate.

Estimating Software Costs This article describes the cost estimation lifecycle and a process to estimate project volume. Author: William Roetzheim Co-Founder, Cost Xpert Group, Inc. Estimating Software

Software cost estimation

Software cost estimation Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 26 Slide 1 Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for

A Comparison of Calibrated Equations for Software Development Effort Estimation

A Comparison of Calibrated Equations for Software Development Effort Estimation Cuauhtemoc Lopez Martin Edgardo Felipe Riveron Agustin Gutierrez Tornes 3,, 3 Center for Computing Research, National Polytechnic

An Empirical Approach for Estimation of the Software Development Effort

, pp. 97-110 http://dx.doi.org/10.14257/ijmue.2015.10.2.09 An Empirical Approach for Estimation of the Software Development Effort Amit Kumar Jakhar and Kumar Rajnish Department of Computer Science & Engineering,

Chapter 6 (part 1) Project Time Management. (Project Scheduling)

Chapter 6 (part 1) Project Time Management. (Project Scheduling) 1 Objectives Understand the process of project decomposition into activities Understand the level of details required for activities Understand

Module 11. Software Project Planning. Version 2 CSE IIT, Kharagpur

Module 11 Software Project Planning Lesson 29 Staffing Level Estimation and Scheduling Specific Instructional Objectives At the end of this lesson the student would be able to: Identify why careful planning

Software Engineering CSCI 4490. Lesson 9 Project Management Part 1- Planning & Estimating. February 23, 2015

Lesson 9 Project Management Part 1- Planning & Estimating February 23, 2015 Projects and Project Managers Project a [temporary] sequence of unique, complex, and connected activities having one goal or

Project Management for Scientists

Project Management for Scientists Cost & Schedule Estimates Christoph U. Keller, c.u.keller@uu.nl Sterrekundig Instituut Utrecht Utrecht University www.astro.uu.nl/~keller Outline Resource Assignments

Computer Science and Software Engineering University of Wisconsin - Platteville 3.Time Management

Computer Science and Software Engineering University of Wisconsin - Platteville 3.Time Management SE 2730 Lecture Notes Yan Shi Based on Introduction to the Personal Software Process by Watts Humphrey

CISC 322 Software Architecture

CISC 322 Software Architecture Lecture 20: Software Cost Estimation 2 Emad Shihab Slides adapted from Ian Sommerville and Ahmed E. Hassan Estimation Techniques There is no simple way to make accurate estimates

SoftwareCostEstimation. Spring,2012

SoftwareCostEstimation Spring,2012 Chapter 3 SOFTWARE COST ESTIMATION DB Liu Software Cost Estimation INTRODUCTION Estimating the cost of a software product is one of the most difficult and error-prone

Software cost estimation. Predicting the resources required for a software development process

Software cost estimation Predicting the resources required for a software development process Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 23 Slide 1 Objectives To introduce the fundamentals

Project Planning. COSC345 Lecture 3 Slides: Andrew Trotman Dramatic presentation: Richard O Keefe. Software Engineering 2013

Project Planning COSC345 Lecture 3 Slides: Andrew Trotman Dramatic presentation: Richard O Keefe Software Engineering 2013 Overview Assignment: The assignment sheet specifies a minimum Think about what

Contents. Today Project Management. Project Management. Last Time - Software Development Processes. What is Project Management?

Contents Introduction Software Development Processes Project Management Requirements Engineering Software Construction Group processes Quality Assurance Software Management and Evolution Last Time - Software

Safe and Simple Software Cost Analysis Barry Boehm, USC Everything should be as simple as possible, but no simpler.

Safe and Simple Software Cost Analysis Barry Boehm, USC Everything should be as simple as possible, but no simpler. -Albert Einstein Overview There are a number of simple software cost analysis methods,

MTAT.03.244 Software Economics. Lecture 5: Software Cost Estimation

MTAT.03.244 Software Economics Lecture 5: Software Cost Estimation Marlon Dumas marlon.dumas ät ut. ee Outline Estimating Software Size Estimating Effort Estimating Duration 2 For Discussion It is hopeless

SOFTWARE EFFORT ESTIMATION USING RADIAL BASIS FUNCTION NEURAL NETWORKS Ana Maria Bautista, Angel Castellanos, Tomas San Feliu

International Journal Information Theories and Applications, Vol. 21, Number 4, 2014 319 SOFTWARE EFFORT ESTIMATION USING RADIAL BASIS FUNCTION NEURAL NETWORKS Ana Maria Bautista, Angel Castellanos, Tomas

CSC 342 Software Engineering

CSC 342 Software Engineering Chapter 23: Software Cost Estimation Instructor: Dr. Ghazy Assassa Software Engineering CSC 342/Dr. Ghazy Assassa Sommerville, Ch 23 & Pressman, Ch 4, 5 Slide 1 Software cost

PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING

PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING 03-23-05 Christine Green, PMI PMBOK and Estimating EDS, Delivery

Software Requirements Metrics

Software Requirements Metrics Fairly primitive and predictive power limited. Function Points Count number of inputs and output, user interactions, external interfaces, files used. Assess each for complexity

WBS, Estimation and Scheduling. Adapted from slides by John Musser

WBS, Estimation and Scheduling Adapted from slides by John Musser 1 Today Work Breakdown Structures (WBS) Estimation Network Fundamentals PERT & CPM Techniques Gantt Charts 2 Estimation Predictions are

Knowledge-Based Systems Engineering Risk Assessment

Knowledge-Based Systems Engineering Risk Assessment Raymond Madachy, Ricardo Valerdi University of Southern California - Center for Systems and Software Engineering Massachusetts Institute of Technology

Extending Change Impact Analysis Approach for Change Effort Estimation in the Software Development Phase

Extending Change Impact Analysis Approach for Change Effort Estimation in the Software Development Phase NAZRI KAMA, MEHRAN HALIMI Advanced Informatics School Universiti Teknologi Malaysia 54100, Jalan

Risk management :Introduction, nature of risk, managing risk, risk identification, risk analysis

Risk management :Introduction, nature of risk, managing risk, risk identification, risk analysis Definition of Risk A risk is a potential problem it might happen and it might not Conceptual definition

Handbook for Software Cost Estimation

JPL D-26303, Rev. 0 Handbook for Software Cost Estimation Prepared by: Karen Lum Michael Bramble Jairus Hihn John Hackney Mori Khorrami Erik Monson Document Custodian: Jairus Hihn Approved by: Frank Kuykendall

Comparison of SDLC-2013 Model with Other SDLC Models by Using COCOMO

International Journal of Emerging Science and Engineering (IJESE) Comparison of SDLC-2013 Model with Other SDLC Models by Using COCOMO Naresh Kumar, Pinky Chandwal Abstract There exist a large number of

Software Architecture and Engineering Project Cost Management Peter Müller

Software Architecture and Engineering Project Cost Management Peter Müller Chair of Programming Methodology Spring Semester 2012 12. Project Cost Management Overview 2 12. Project Cost Management 12.1

ICS 121 Lecture Notes Spring Quarter 96

Software Management Cost Estimation Managing People Management Poor managment is the downfall of many software projects Ð Delivered software was late, unreliable, cost several times the original estimates

Session Objectives. Software Estimation. Why Estimate Software? Problem for Estimates. My Background. What are the consequences?

Session Objectives Software Estimation What you need to know Mel Rosso-Llopart rossollo@cmu.edu 1 Where is the software industry with estimation of project Why are we bad at estimating? What do we mean

Software cost estimation. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 26 Slide 1

Software cost estimation Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 26 Slide 1 Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for

Analyzing Software Development as a Noncooperative Game

Analyzing Software Development as a Noncooperative Game Mark Grechanik and Dewayne E. Perry The Center for Advanced Research In Software Engineering (ARISE) The University of Texas at Austin gmark@cs.utexas.edu,

Chapter 3 Managing the Information Systems (IS) Project

Content Chapter 3 Managing the Information Systems (IS) Project Process of managing IS projects Skills required to be an effective project manager Skills and activities of a project manager during project

Software Quality and Standards

Software Quality and Standards Dr. James A. Bednar jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar Dr. David Robertson dr@inf.ed.ac.uk http://www.inf.ed.ac.uk/ssp/members/dave.htm SEOC2 Spring

Deducing software process improvement areas from a COCOMO II-based productivity measurement

Deducing software process improvement areas from a COCOMO II-based productivity measurement Lotte De Rore, Monique Snoeck, Geert Poels, Guido Dedene Abstract At the SMEF2006 conference, we presented our

Effect of Schedule Compression on Project Effort

Effect of Schedule Compression on Project Effort Ye Yang, Zhihao Chen, Ricardo Valerdi, Barry Boehm Center for Software Engineering, University of Southern California (USC-CSE) Los Angeles, CA 90089-078,

The ROI of Systems Engineering: Some Quantitative Results

The ROI of Systems Engineering: Some Quantitative Results Barry Boehm Center for Systems and Software Engineering University of Southern California boehm@usc.edu Ricardo Valerdi Lean Aerospace Initiative,

CISC 322 Software Architecture. Example of COCOMO-II Ahmed E. Hassan

CISC 322 Software Architecture Example of COCOMO-II Ahmed E. Hassan Function Point Table Number of FPs External user type Complexity Low Average High External input type 3 4 6 External output type 4 5

Fuzzy Logic based framework for Software Development Effort Estimation

330 Fuzzy Logic based framework for Software Development Effort Estimation Sandeep Kad 1, Vinay Chopra 2 1 Department of Information Technology Amritsar College of Engg. & Technology, Amritsar, Punjab,

Integrated Modeling of Business Value and Software Processes

Integrated Modeling of Business Value and Software Processes Raymond Madachy, USC Center for Software Engineering Department of Computer Science, SAL 8 University of Southern California Los Angeles, CA

Systems Analysis and Design Life Cycle

Systems Analysis and Design Life Cycle 2.1 The major goal of requirement determination phase of information system development is a. determine whether information is needed by an organization b. determine

CSSE 372 Software Project Management: Software Estimation With COCOMO-II

CSSE 372 Software Project Management: Software Estimation With COCOMO-II Shawn Bohner Office: Moench Room F212 Phone: (812) 877-8685 Email: bohner@rose-hulman.edu Estimation Experience and Beware of the

An Approach to Find Maintenance Costs Using Cost Drivers of Cocomo Intermediate Model

An Approach to Find Maintenance Costs Using Cost Drivers of Cocomo Intermediate Model C.V.S.R SYAVASYA 1, M.Tech, GITAM UNIVERSITY Abstract: Maintenance of software under several cost drivers is as sort

CS/SWE 321 Sections -001 & -003. Software Project Management

CS/SWE 321 Sections -001 & -003 Software Project Management Copyright 2014 Hassan Gomaa All rights reserved. No part of this document may be reproduced in any form or by any means, without the prior written

An Evaluation of Neural Networks Approaches used for Software Effort Estimation

Proc. of Int. Conf. on Multimedia Processing, Communication and Info. Tech., MPCIT An Evaluation of Neural Networks Approaches used for Software Effort Estimation B.V. Ajay Prakash 1, D.V.Ashoka 2, V.N.

Fundamentals of Computer Architecture. 1. Introducing The Processor

Fundamentals of Computer Architecture 1. Introducing The Processor 1 Chapter Overview This chapter includes: The key aspects of a computer; A brief history of the computer and its place within our modern

Simulation for Business Value and Software Process/Product Tradeoff Decisions

Simulation for Business Value and Software Process/Product Tradeoff Decisions Raymond Madachy USC Center for Software Engineering Dept. of Computer Science, SAL 8 Los Angeles, CA 90089-078 740 570 madachy@usc.edu

PROJECT RISK MANAGEMENT

11 PROJECT RISK MANAGEMENT Project Risk Management includes the processes concerned with identifying, analyzing, and responding to project risk. It includes maximizing the results of positive events and

A DIFFERENT KIND OF PROJECT MANAGEMENT: AVOID SURPRISES

SEER for IT: Infrastructure, Services for Project & Operations SEER project estimation and management solutions improve success rates on IT Infrastructure and IT services projects and operations. Based

A DIFFERENT KIND OF PROJECT MANAGEMENT: AVOID SURPRISES

SEER for Software: Cost, Schedule, Risk, Reliability SEER project estimation and management solutions improve success rates on complex software projects. Based on sophisticated modeling technology and

A Case Study Research on Software Cost Estimation Using Experts Estimates, Wideband Delphi, and Planning Poker Technique

, pp. 173-182 http://dx.doi.org/10.14257/ijseia.2014.8.11.16 A Case Study Research on Software Cost Estimation Using Experts Estimates, Wideband Delphi, and Planning Poker Technique Taghi Javdani Gandomani

Cost Estimation Driven Software Development Process

Cost Estimation Driven Software Development Process Orsolya Dobán, András Pataricza Budapest University of Technology and Economics Department of Measurement and Information Systems Pázmány P sétány 1/D

Project Scheduling Techniques: Probabilistic and Deterministic

Project Scheduling Techniques: Probabilistic and Deterministic Contents Project scheduling and types of project schedule... 2 Overview... 2 Project scheduling techniques... 2 Deterministic Scheduling...

Feasibility of a Software Process Modeling Library based on MATLAB / Simulink

Feasibility of a Software Process Modeling Library based on MATLAB / Simulink T. Birkhoelzer University of Applied Sciences Konstanz, Braunegger Str. 55, 7846 Konstanz, Germany, birkhoelzer@fh-kontanz.de

Schedule Risk Analysis Simplified 1 by David T. Hulett, Ph.D.

Schedule Risk Analysis Simplified 1 by David T. Hulett, Ph.D. Critical Path Method Scheduling - Some Important Reservations The critical path method (CPM) of scheduling a project is a key tool for project

Software Project Estimation

Software Project Estimation Effective software project estimation is one of the most challenging and important activities in software development. Proper project planning and control is not possible without

Software Failures. Dr. James A. Bednar. jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar. Dr. David Robertson

Software Failures Dr. James A. Bednar jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar Dr. David Robertson dr@inf.ed.ac.uk http://www.inf.ed.ac.uk/ssp/members/dave.htm SAPM Spring 2012: Failures

Amajor benefit of Monte-Carlo schedule analysis is to

2005 AACE International Transactions RISK.10 The Benefits of Monte- Carlo Schedule Analysis Mr. Jason Verschoor, P.Eng. Amajor benefit of Monte-Carlo schedule analysis is to expose underlying risks to

SYSTEMS ANALYSIS AND DESIGN LIFE CYCLE

MODULE 2 SYSTEMS ANALYSIS AND DESIGN LIFE CYCLE OBJECTIVE QUESTIONS There are 4 alternative answers to each question. One of them is correct. Pick the correct answer. Do not guess. A key is given at the

Cost Estimation for Secure Software & Systems

Background Cost Estimation for Secure Software & Systems Ed Colbert Dr. Barry Boehm Center for Systems & Software Engineering, University of Southern California, 941 W. 37th Pl., Sal 328, Los Angeles,

risks in the software projects [10,52], discussion platform, and COCOMO

CHAPTER-1 INTRODUCTION TO PROJECT MANAGEMENT SOFTWARE AND SERVICE ORIENTED ARCHITECTURE 1.1 Overview of the system Service Oriented Architecture for Collaborative WBPMS is a Service based project management

Project management Project Management

Project management Project Management Dr. James A. Bednar jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar A project is a temporary endeavour to produce a unique product, service, or result (PMI

Project Management. Software Projects vs. Engineering Projects

Read Chapters (a) Project Management, (b) Project Scheduling and (c) Risk Management from Pressman for this lecture. Project Management Rahul Premraj + Andreas Zeller reliability of data questioned! Software

Improving Software Project Management Skills Using a Software Project Simulator

Improving Software Project Management Skills Using a Software Project Simulator Derek Merrill and James S. Collofello Department of Computer Science and Engineering Arizona State University Tempe, AZ 85287-5406

Estimation Tools. Seminar on Software Cost Estimation WS 02/03. Presented by Christian Seybold seybold@ifi.unizh.ch

Estimation Tools Seminar on Software Cost Estimation WS 02/03 Presented by Christian Seybold seybold@ifi.unizh.ch Requirements Engineering Research Group Department of Computer Science University of Zurich,

Summary of GAO Cost Estimate Development Best Practices and GAO Cost Estimate Audit Criteria

Characteristic Best Practice Estimate Package Component / GAO Audit Criteria Comprehensive Step 2: Develop the estimating plan Documented in BOE or Separate Appendix to BOE. An analytic approach to cost

Chapter 4: Planning Projects, Part I (Integration, Scope, Time, and Cost Management) Slide 2

Chapter 4: Planning Projects, Part I (Integration, Scope, Time, and Cost Management) Slide 2 Introduction to Project Management Project Time Management Planning Tasks Project time management involves the

SYSTEMS ANALYSIS WHAT, WHY AND HOW. Edward A. Beimborn College of Engineering and Applied Science University of Wisconsin--Milwaukee

SYSTEMS ANALYSIS WHAT, WHY AND HOW Edward A. Beimborn College of Engineering and Applied Science University of Wisconsin--Milwaukee The New Approach to Urban Revival essentially involves the application

A New Approach in Software Cost Estimation with Hybrid of Bee Colony and Chaos Optimizations Algorithms

A New Approach in Software Cost Estimation with Hybrid of Bee Colony and Chaos Optimizations Algorithms Farhad Soleimanian Gharehchopogh 1 and Zahra Asheghi Dizaji 2 1 Department of Computer Engineering,

Software Development Cost and Time Forecasting Using a High Performance Artificial Neural Network Model

Software Development Cost and Time Forecasting Using a High Performance Artificial Neural Network Model Iman Attarzadeh and Siew Hock Ow Department of Software Engineering Faculty of Computer Science &

Software Cost Estimation using Function Point with Non Algorithmic Approach

Global Journal of omputer Science and Technology Software & Data Engineering Volume 13 Issue 8 Version 1.0 Year 2013 Type: Double Blind Peer Reviewed International Research Journal Publisher: Global Journals

Impact of CMMI-Based Process Maturity Levels on Effort, Productivity and Diseconomy of Scale

352 The International Arab Journal of Information Technology, Vol. 9, No. 4, July 2012 Impact of -Based Process Maturity Levels on Effort, Productivity and Diseconomy of Scale Majed Alyahya, Rodina Ahmad,

11.1 What is Project Management? Object-Oriented Software Engineering Practical Software Development using UML and Java. What is Project Management?

11.1 What is Project Management? Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 11: Managing the Software Process Project management encompasses all the

E-COCOMO: The Extended COst Constructive MOdel for Cleanroom Software Engineering

Database Systems Journal vol. IV, no. 4/2013 3 E-COCOMO: The Extended COst Constructive MOdel for Cleanroom Software Engineering Hitesh KUMAR SHARMA University of Petroleum and Energy Studies, India hkshitesh@gmail.com

Project Management. Project Management Fundamentals: Estimation and Project Control. Sergio Cavaliere. IBM Global Business Services

Project Management Sergio Cavaliere IBM Global Business Services Agenda Estimating Basic Definitions Estimating Approaches an Techniques Project Estimating Project Control Overview Schedule and Cost Control

Software Project Management Matrics. Complied by Heng Sovannarith heng_sovannarith@yahoo.com

Software Project Management Matrics Complied by Heng Sovannarith heng_sovannarith@yahoo.com Introduction Hardware is declining while software is increasing. Software Crisis: Schedule and cost estimates

SOFTWARE ECONOMICS UNIT 15. Presented by. Stefano Street

SOFTWARE ECONOMICS UNIT 15 Presented by Stefano Street Objectives Software economics its importance and place in software systems Provide an empirical view of where money goes Why it is important to understand

Project Management Dr. James A. Bednar

Project Management Dr. James A. Bednar jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar SAPM Spring 2006: Project Management 1 Project Management A project is a temporary endeavour to produce

Training Software Development Project Managers with a Software Project Simulator

Master of Science Thesis Proposal Department of Computer Science and Engineering Arizona State University Training Software Development Project Managers with a Software Project Simulator Prepared by Derek

Project Management Process

Project Management Process Description... 1 STAGE/STEP/TASK SUMMARY LIST... 2 Project Initiation 2 Project Control 4 Project Closure 5 Project Initiation... 7 Step 01: Project Kick Off 10 Step 02: Project

Software Metrics. Lord Kelvin, a physicist. George Miller, a psychologist

Software Metrics 1. Lord Kelvin, a physicist 2. George Miller, a psychologist Software Metrics Product vs. process Most metrics are indirect: No way to measure property directly or Final product does not

Software Estimation Techniques - Common Test Estimation Techniques used in SDLC

Software Estimation Techniques - Common Test Estimation Techniques used in SDLC In order to successful software project & proper execution of task, the Estimation Techniques plays vital role in software

COCOMO-SCORM Interactive Courseware Project Cost Modeling

COCOMO-SCORM Interactive Courseware Project Cost Modeling Roger Smith & Lacey Edwards SPARTA Inc. 13501 Ingenuity Drive, Suite 132 Orlando, FL 32826 Roger.Smith, Lacey.Edwards @Sparta.com Copyright 2006

A DIFFERENT KIND OF PROJECT MANAGEMENT

SEER for Software SEER project estimation and management solutions improve success rates on complex software projects. Based on sophisticated modeling technology and extensive knowledge bases, SEER solutions

Topics. Project plan development. The theme. Planning documents. Sections in a typical project plan. Maciaszek, Liong - PSE Chapter 4

MACIASZEK, L.A. and LIONG, B.L. (2005): Practical Software Engineering. A Case Study Approach Addison Wesley, Harlow England, 864p. ISBN: 0 321 20465 4 Chapter 4 Software Project Planning and Tracking

Project Risk Management

PROJECT ADVISORY Project Risk Management Leadership Series 9 kpmg.com/nz About the Leadership Series KPMG s Leadership Series is targeted towards owners of major capital programmes, but its content is

Large Scale Systems Design G52LSS

G52LSS Lecture 5 Project Management Elements of Project Management Estimate Size of the Project Produce a Work-Plan Produce a Staffing Plan Coordinate Project Activities Learning outcomes: describe the