Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.1 © 2006 Pearson/Prentice Hall 3.1 Tracking Progress : Gantt Chart Activities shown.

Slides:

Advertisements

Similar presentations

ISBN Prentice-Hall, 2006 Chapter 2 Modeling the Process and Life Cycle Copyright 2006 Pearson/Prentice Hall. All rights reserved.

Advertisements

CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.

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

ISBN Prentice-Hall, 2006 Chapter 3 Planning and Managing the Project Copyright 2006 Pearson/Prentice Hall. All rights reserved.

Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.

Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.

1 Calibrating Function Points Using Neuro-Fuzzy Technique Vivian Xia NFA Estimation Inc. London, Ontario, Canada Danny Ho IT Department.

Lecturer: Dr. AJ Bieszczad Chapter 33-1 Planning and managing the project Tracking project progress Project personnel and organization Effort and schedule.

SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.

Chapter 3 Planning and Managing the Project Shari L. Pfleeger Joanne M. Atlee 4th Edition.

Computer Engineering 203 R Smith Project Scheduling 12/ Scheduling Now we know how much work there is to do, when can it be done? What kind of schedule.

Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.

Project Management Software Tools Cheryl A. Wilhelmsen Lee Ostrom.

Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.

University of Toronto Department of Computer Science © 2001, Steve Easterbrook CSC444 Lec22 1 Lecture 22: Software Measurement Basics of software measurement.

© The McGraw-Hill Companies, Software Project Management 4th Edition Software effort estimation Chapter 5.

Chapter 3 Planning and Managing the Project. Pfleeger and Atlee, Software Engineering: Theory and PracticeChapter 3.2 Important Dates 09/09/2010 HW: Page.

ISBN Prentice-Hall, 2006 Chapter 10 Delivering the System Copyright 2006 Pearson/Prentice Hall. All rights reserved.

Four P’s People – software engineers People – software engineers Product – software to be produced Product – software to be produced Process – framework.

Schedule & effort.

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 4.1 © 2006 Pearson/Prentice Hall Sidebar 4.1 Why Are Requirements Important? Top factors.

Risk evaluation Risk evaluation is meant to decide whether to proceed with the project or not, and whether the project is meeting its objectives. Risk.

Building (stage 2) for Dept. of Computer Science & Computer Unit  Total Cost Estimate :291 Million  Physical Progress: 80%  Financial Progress:60% University.

Using Scientific Measurements. Uncertainty in Measurements All measurements have uncertainty. 1.Measurements involve estimation by the person making the.

By K Gopal Reddy.  Metrics in software are of two types.direct and indirect.  Function points as indirect metrics.  Function points are used to measure.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.

Project Management Formal Methods. How do you monitor a project?

Chapter 3 Project Management Details Tracking Project Progress Project Estimation Project Risk Analysis Project Organization RUP Project Management Workflow.

1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.

Introduction to Software Engineering ECSE-321 Unit 4 – Project Management 10/19/2015Introduction to Software Engineering – ECSE321Unit 4 – Project Management/1.

Cost Estimation What is estimated? –resources (humans, components, tools) –cost (person-months) –schedule (months) Why? –Personnel allocation –Contract.

Measurement (II)1 Measurement - Productivity, Estimation, Effort Advanced Software Engineering COM360 University of Sunderland © 1998.

Project Management Cross lifecycle Activity

Chapter 3 Planning and Managing the Project Shari L. Pfleeger Joanne M. Atlee 4 th Edition.

Estimation using COCOMO

1. What do you understand by software engineering? Discuss the role of engineering software development. 2. What do you understand by software requirement.

Project Management. Introduction  Project management process goes alongside the system development process Process management process made up of three.

Schedule & effort.

ISBN Prentice-Hall, 2006 Chapter 8 Testing the Programs Copyright 2006 Pearson/Prentice Hall. All rights reserved.

University of Southern California Center for Systems and Software Engineering Reducing Estimation Uncertainty with Continuous Assessment: Tracking the.

Smi COCOMO II Calibration Status USC-CSE Annual Research Review March 2004.

2.02 Utilize project-management skills to improve workflow and minimize costs.

SOFTWARE PROCESS MODELING Benjamin Dixon U

PROJECT PLANNING & MANAGEMENT Brittany Hamilton. PROGRESS TRACKING Do we understand customer’s needs? Can we design a system to solve customer’s problems.

PLANNING AND MANAGING THE PROJECT CODY STANISH. 3.1 TRACKING PROGRESS Do you understand the customer’s needs? Can you design a system to solve customer’s.

Local Calibration: How Many Data Points are Best? Presented by Barry Boehm on behalf of Vu Nguyen, Thuy Huynh University of Science Vietnam National University.

(6) Estimating Computer’s efficiency Software Estimation The objective of Software Estimation is to provide the skills needed to accurately predict the.

The Software Engineering Process Discussion Slides.

Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.

By Manish Shrotriya CSE MS Software Estimation Effort Estimation: how much effort is required to complete an activity. (How to define efforts: Line.

2.02 Utilize project-management skills to improve workflow and minimize costs.

Software Project Planning. Software Engineering Estimation Estimation The SPM begins with a set of activities that are collectively called Project planning.

Software cost and effort estimation will never be an exact science. Estimation is very difficult to do, but is often needed Too many variables can affect.

Z26 Project Management Metrics appropriate metrics for iterative projects Lecture 4a Graham Collins, UCL

Software Development Process includes: all major process activities all major process activities resources used, subject to set of constraints (such as.

Project Cost Management

Software Project Sizing and Cost Estimation

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,

Chapter 3 Planning and Managing the Project Shari L. Pfleeger

COCOMO Model Basic.

The Software Engineering Process

Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.

The role of Planning in the Software Development Process

Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,

Why Do We Measure? assess the status of an ongoing project

PPT3: Project planning and management

Copyright 2006 Pearson/Prentice Hall. All rights reserved.

Software Effort Estimation

Chapter 26 Estimation for Software Projects.

Presentation transcript:

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.1 © 2006 Pearson/Prentice Hall 3.1 Tracking Progress : Gantt Chart Activities shown in parallel

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.2 © 2006 Pearson/Prentice Hall 3.1 Tracking Progress Phases, Steps, and Activities in Building a House

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.3 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation Estimation Should be Done Repeatedly Uncertainty affects the accuracy of cost and size estimations

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.4 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation Watson and Felix Model Productivity Factors

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.5 © 2006 Pearson/Prentice Hall Three Stages of COCOMO II

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.6 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation COCOMO II: Estimate Application Points To compute application points count the number of screens, reports, and programming language used, and determine the complexity level 8 +mediumdifficult 4 +mediumdifficult

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.7 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation Complexity Weights for Application Points Object typeSimpleMediumDifficult Screen 123 Report 258 3GL component -- 10

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.8 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation Productivity Estimate Calculation

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.9 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation - Evaluating Models No model captures cost for all types of development PRED(25%) within 25% of actual cost MMRE - mean magnitude of relative error (small is good)

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.10 © 2006 Pearson/Prentice Hall Risk

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.11 © 2006 Pearson/Prentice Hall 3.4 Risk Management Risk Management Activities (continued) Example of risk exposure calculation