Scribd
Upload
49 views6 pages

Software Project Planning

The document discusses key steps for planning a software project, including scoping the work, estimating time and costs, assessing risks, creating a schedule, and controlling quality. It provides examples of estimating project effort using lines of code and function points. It also discusses reasons why projects fall behind schedule and principles for effective scheduling like compartmentalizing tasks, defining dependencies and outcomes, and establishing milestones.

Uploaded by

mirage07
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
49 views6 pages

Software Project Planning

The document discusses key steps for planning a software project, including scoping the work, estimating time and costs, assessing risks, creating a schedule, and controlling quality. It provides examples of estimating project effort using lines of code and function points. It also discusses reasons why projects fall behind schedule and principles for effective scheduling like compartmentalizing tasks, defining dependencies and outcomes, and establishing milestones.

Uploaded by

mirage07
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling, tracking, and

monitoring a complex technical project. Why? So the end result gets done on time, with quality! The Steps t Scopingunderstand the problem and the work that must be done t Estimationhow much effort? how much time? t Riskwhat can go wrong? how can we avoid it? what can we do about it? t Schedulehow do we allocate resources along the timeline? what are the milestones? t Control strategyhow do we control quality? how do we control change? Write it Down Documentation

To Understand Scope ... t Understand the customers needs t understand the business context t understand the project boundaries t understand the customers motivation t understand the likely paths for change Cost Estimation Project Scope must be explicitly defined Task and/or functional decomposition is necessary

historical measures are very helpful atleast two different techniques should be used remember that uncertainty is inherent

Estimation Techniques t past (similar) project experience t conventional estimation techniques task breakdown and effort estimates size (e.g., FP) estimates

t tools (e.g., Checkpoint) 1. Conventional Methods: LOC/FP Approach t compute LOC/FP using estimates of information domain values t use historical effort for the project Example: LOC Approach
Functions UICF 2DGA 3DGA DSM CGDF PCF DAM Totals estimated LOC 2340 5380 6800 3350 4950 2140 8400 33,360 LOC/pm 315 220 220 240 200 140 300 $/LOC 14 20 20 18 22 28 18 Cost 32,000 107,000 136,000 60,000 109,000 60,000 151,000 655,000 Effort (months) 7.4 24.4 30.9 13.9 24.7 15.2 28.0 145.0

Example: FP Approach

measurement parameter number of user inputs number of user outputs number of user inquiries number of files number of ext.interfaces algorithms count-total complexity multiplier feature points

count 40 25 12 4 4 60 x x x x x x

weight 4 5 4 7 7 3 = = = = = = 160 125 48 28 28 180

0.25 p-m / FP = 120 p-m

569 .84 478

2. Tool-Based Estimation 3. Empirical Estimation Models General Estimation Guidelines estimate using at least two techniques get estimates from independent sources avoid over-optimism, assume difficulties you've arrived at an estimate, sleep on it adjust for the people who'll be doing the jobthey have the highest impact Project Scheduling and Tracking Why Are Projects Late? t an unrealistic deadline established by someone outside the software development group t changing customer requirements that are not reflected in schedule changes; t an honest underestimate of the amount of effort and/or the number of resources that will be required to do the job; t predictable and/or unpredictable risks that were not considered when the project commenced; t technical difficulties that could not have been foreseen in advance;

t human difficulties that could not have been foreseen in advance; t miscommunication among project staff that results in delays; t a failure by project management to recognize that the project is falling behind schedule and a lack of action to correct the problem Scheduling Principles t compartmentalizationdefine distinct tasks t interdependencyindicate task interrelationshipsffort validationbe sure resources are available t defined responsibilitiespeople must be assigned t defined outcomeseach task must have an output t defined milestonesreview for quality Defining Task Sets t determine type of project t assess the degree of rigor required identify adaptation criteria compute task set selector (TSS) value interpret TSS to determine degree of rigor t select appropriate software engineering tasks

Define a Task Network


I.3a Tech. Risk Assessment I.5a Concept Implement.

I.1 Concept scoping

I.2 Concept planning

I.3b Tech. Risk Assessment

I.4 Proof of Concept

I.5b Concept Implement.

Integrate a, b, c

I.6 Customer Reaction

I.3c Tech. Risk Assessment

I.5c Concept Implement.

Three I.3 tasks are applied in parallel to 3 different concept functions

Three I.3 tasks are applied in parallel to 3 different concept functions

Effort Allocation t front end activities customer communication analysis design review and modification

t construction activities coding or code generation

t testing and installation unit, integration white-box, black box regression

Use Automated Tools to Derive a Timeline Chart

You might also like