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

Slides:



Advertisements
Similar presentations
Estimation for Software Projects
Advertisements

PERENCANAAN PROYEK PERANGKAT LUNAK Nur Cahyo Wibowo, S.Kom, M.Kom.
Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.
Metrics. A Good Manager Measures measurement What do we use as a basis? size? size? function? function? project metrics process metrics process product.
Chapter 26 Estimation for Software Projects
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
Chapter 5 Software Project Planning
Developed by Reneta Barneva, SUNY Fredonia Software Project Planning.
Ch8: Management of Software Engineering. 1 Management of software engineering  Traditional engineering practice is to define a project around the product.
Software Project Planning CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 12, 2002.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
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.
SOFTWARE PROJECT PLANNING
Software Project Planning Infsy 570 Dr. R. Ocker.
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.
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
COCOMO Models Ognian Kabranov SEG3300 A&B W2004 R.L. Probert.
Software Project Management
Project Management Estimation. LOC and FP Estimation –Lines of code and function points were described as basic data from which productivity metrics can.
CS /39 Illinois Institute of Technology CS487 Software Engineering David A. Lash.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
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.
Introduction to Software Engineering ECSE-321 Unit 4 – Project Management 10/19/2015Introduction to Software Engineering – ECSE321Unit 4 – Project Management/1.
T. E. Potok - University of Tennessee CS 594 Software Engineering Lecture 3 Dr. Thomas E. Potok
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 Chapter 5 Software Project Planning. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling,
Developed by Reneta Barneva, SUNY Fredonia Software Project Planning.
Cost Estimation What is estimated? –resources (humans, components, tools) –cost (person-months) –schedule (months) Why? –Personnel allocation –Contract.
Software Engineering Software Project Planning. Objectives 1.To introduce project planning. 2.To examine the stages of project planning: scoping, estimation,
Software Engineering Lecture 5 Software Project Planning 1.
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.
Software Project Estimation IMRAN ASHRAF
Estimation for Software Projects 1. Software Project Planning 2 The overall goal of project planning is to establish a pragmatic strategy for controlling,
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.
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
Software Engineering (CSI 321) Project Planning & Estimation 1.
Software Engineering Lecture 5: Project Planning.
Intro to Estimating Part Art, Part Science. Importance of Good Estimates Time (Realistic Deadlines) most software projects are late because the time was.
Software Project Management
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.
Software Cost Estimation By Deepika Chaudhary. In project planning process a project is split into a number of activities which are performed in parallel.
SPM UNIT 2 - Prof S. S. Deshmukh. Software measurements  Measurement gives us the insight by providing mechanism for evaluation.  There are four reasons.
INFSY 570 DR. R. OCKER Software 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.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
Chapter-7 ESTIMATION FOR SOFTWARE PROJECTS
Chapter 33 Estimation for Software Projects
For University Use Only
Estimation for Software Projects
Software Engineering (CSI 321)
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,
Software Project Estimation
REKAYASA PERANGKAT LUNAK
Software Project Planning &
Constructive Cost Model
Software Cost estimation
COCOMO Model Basic.
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,
COnstructive COst MOdel
Chapter 26 Estimation for Software Projects.
SOFTWARE ESTIMATION 1. Estimation for Software Projects -Project planning -Scope and feasibility -Project resources -Estimation of project cost and effort.
COCOMO MODEL.
Presentation transcript:

Software Project Planning

Software Engineering Estimation Estimation The SPM begins with a set of activities that are collectively called Project planning The SPM begins with a set of activities that are collectively called Project planning Whenever estimates are are made we look into future concern and so there is some degree of uncertainty in estimation Whenever estimates are are made we look into future concern and so there is some degree of uncertainty in estimation

Software Engineering Observation on Estimation Observation on Estimation PM manager must have the ability to estimate PM manager must have the ability to estimate PM with the ability to know what will go wrong before it actually does PM with the ability to know what will go wrong before it actually does Estimation of resources, cost and schedule for a software requires experience of past projects and access to historical data Estimation of resources, cost and schedule for a software requires experience of past projects and access to historical data

Software Engineering Project complexity has a strong effect on uncertainty that is inherent in planning. Project complexity has a strong effect on uncertainty that is inherent in planning. Complexity is affected by familiarity with past efforts Complexity is affected by familiarity with past efforts Real time projects are always complex Real time projects are always complex Project size also effect the accuracy of the estimates Project size also effect the accuracy of the estimates

Software Engineering If the requirements have been solidified estimation is easy but if the requirement are keep on changing estimation is affects If the requirements have been solidified estimation is easy but if the requirement are keep on changing estimation is affects

Software Engineering Project Planning objectives Project Planning objectives The objectives of software project planning is to provides the reasonable estimates of cost, effort and schedule The objectives of software project planning is to provides the reasonable estimates of cost, effort and schedule These estimates are made at the beginning of the project and must be updated wit the passage of time. These estimates are made at the beginning of the project and must be updated wit the passage of time.

Software Engineering Software Scope Software Scope Estimation of scope Estimation of scope Functional, non functional requirements. Constraints Functional, non functional requirements. Constraints

Software Engineering Obtaining information necessary for scope Obtaining information necessary for scope Things are always hazy at the start of the project Things are always hazy at the start of the project There must be some meeting between customer and analyst for obtaining the scope of project There must be some meeting between customer and analyst for obtaining the scope of project

Software Engineering 1 st meeting question 1 st meeting question 2 nd meeting question 2 nd meeting question 3 rd meeting question and so on 3 rd meeting question and so on

Software Engineering Resources Resources The 2 nd task of software planning is the estimation of resources required to accomplish the software development effort The 2 nd task of software planning is the estimation of resources required to accomplish the software development effort Pyramid Pyramid The development environment-----Hardware and software tools, Reusable components and people The development environment-----Hardware and software tools, Reusable components and people

Software Engineering Human Resource: Human Resource: The no. of people required for a software project can be determined only after an estimate of development effort. Reusable Software component Reusable Software component Off the shelf components Full experience components Partial experience components New components

Software Engineering Guidelines Guidelines

Software Engineering Software Sizing Software Sizing Fuzzy logic sizing Function point sizing Standard component sizing

Software Engineering Problem based estimation Problem based estimation EV is calculated as EV= (S opt +4S m +S pess )/6 There is a very small probability that the actual size result will fall outside the EV

Software Engineering Example Example

Software Engineering COCOMO Model COCOMO Model Constructive Cost model Three model Model 1 Model 2 Mode3

Software Engineering Model 1 is called Basic COCOMO Model 1 is called Basic COCOMO It has three level It has three levelOrganicSemi-detachedEmbedded

Software Engineering E= a b KLOC bb E= a b KLOC bb D= c b E dd D= c b E dd N= E/D N= E/D Where E is the development effort in PM and D is the development effort time in months and N is the no of people

Software Engineering Make Buy decision: Make Buy decision: The software managers are often faced with the problem of make buy decision. In some cases it is cost effective to acquire rather than internal development