building a plan

8/9/2019 building a plan

1/41

CSE Senior Design ICSE Senior Design I

Building a PlanBuilding a Plan

Instructor: Mike ODellInstructor: Mike ODell

Several of the slides in this module are a modification and amplification of slides preparedSeveral of the slides in this module are a modification and amplification of slides preparedby Mr. Tom Rethard for use in a prior Senior Desin !lass. They "ere oriinally for useby Mr. Tom Rethard for use in a prior Senior Desin !lass. They "ere oriinally for use"ith"ith # Discipline for Soft"are $nineerin# Discipline for Soft"are $nineerin%&atts S. 'umphrey() sponsored by the *.S.%&atts S. 'umphrey() sponsored by the *.S.

Department of Defense. Oriinal slides are copyriht S$I+ modifications are !opyriht ,Department of Defense. Oriinal slides are copyriht S$I+ modifications are !opyriht ,

--) T. Rethard. /urther modifications by Mike ODell. #ll Rihts Reserved.--) T. Rethard. /urther modifications by Mike ODell. #ll Rihts Reserved.


2/41

2

CSE 4316 2

Why Plan?Why Plan?

A plan helps you focusfocuson the goal Begin with the end in mind!"

A plan let#s you estimateestimate$o% completion

A plan helps you trac& progresstrac& progressA plan gi'es you milestonesmilestonesthat pro'ide a

sense of accomplishmentsense of accomplishment along the way

A plan helps you identify pro%lemsidentify pro%lems earlyA plan esta%lishes commitmentsesta%lishes commitments for the

team and each indi'idual on it1Stephen R. Covey, The Seven Habits of Highly Effective People


3/41

2

CSE 4316 3

(he Planning Process) Simplified(he Planning Process) Simplified

0lanthe wor& ) then "orkthe plan

Refine* refine* refine)


4/41

2

CSE 4316 4

What is a Plan?What is a Plan?

An agreementagreement %y the team on the cost andschedule for a specified $o%

A structurestructurefor organi+ing the wor&

A framewor&framewor&for o%taining the re,uiredresources -people* funds* etc.

A recordrecordof what was initially assumed andcommittedIt#s a C/0(1AC(C/0(1AC(2


5/41

2

CSE 4316 5

Components of a PlanComponents of a Plan

A 3ifecycle3ifecyclePlanning 4odel5 (he 4asterPlan for the Pro$ect /rder and criteria for &ey e'ents

Correct model for the $o%?Wor& Estimate 6ow %ig is the $o% -si+e and effort.?

6ow long will it ta&e* when will we finish?Schedule and Wor& Brea&down When do we e7pect to ha'e things done?

What are we committing to?


6/41

2

CSE 4316 7

1epresentati'e 3ifecycle 4odels1epresentati'e 3ifecycle 4odels

Pure Waterfall -the old granddaddy.Code8and89i7 -and plan to fail.Spiral -new age sophistication.

4odified Waterfalls -ma&ing the %est of an oldstand%y.

E'olutionary:1apid Prototyping -design as you go.

Staged 4odels -show as you go. Design to schedule

6y%rids ; some com%inationcom%inationof a%o'e


7/41

2

CSE 4316 8

Pure WaterfallPure Waterfall

Phased deli'era%lesDocument8dri'enDiscontinuous* infle7i%le phases

All planning is done up front


8/41

2

CSE 4316 9

Pure WaterfallPure Waterfall

Requirements

Analysis

Concept

& Planning

Architectural

Design

Detailed

Design

mplementation

& De!ugging

System

"alidation

Pass

9ail

Pass

Pass

Pass

Pass

9ail

9ail

9ail

9ail


9/41

2

CSE 4316 10

Build -Code.8and89i7Build -Code.8and89i7

In general* don#t do it2 Process5 Specify it* code8and8fi7 it* ship it-?.Ad'antages5

3ow:no o'erhead -no planning* documentation*standards* etc.

>ou can start (/DA>2 1e,uires little other than technical e7pertise

Disad'antages5 0o means of assessing progress* pro%lems Dangerous2 for other than tiny pro$ects


10/41

2

CSE 4316 11

SpiralSpiral

1is&8oriented* layered approach Process5

Brea& pro$ect into mini8pro$ects* each addressingma$or ris&s* eg 1is& of poor specifications 1is& of poorly understood architecture

Iterate until ris&s are eliminated Si7 steps in each iteration

Ad'antages5 (ime and money can reduce ris&

Disad'antages Comple7


11/41

2

CSE 4316 12

SpiralSpiral

(Diagram from Spiral Development: Experience, Principles and Refinements, workshop paper by Barry Boehm)

Start


12/41

2

CSE 4316 13

4odified Waterfalls4odified Waterfalls

Waterfall with /'erlapping Phases-Sashimi. 3i&e pure waterfall* %ut phases can o'erlap

Concept

& Planning

Requirements

Analysis

Architectural

Design

DetailedDesign

mplementation

& De!ugging

System

"alidation


13/41

2

CSE 4316 14


Waterfall with Su%pro$ects Begin detailed design on

su%pro$ects %efore o'erallarchitectural design is completeRequirements

Analysis

Concept

& Planning

Architectural

Design

Detailed

Design

mplementation

& De!ugging

Su!System

"alidationSystem

"alidation

Detailed

Design

mplementation

& De!ugging

Su!System

"alidation

Detailed

Design

mplementation

& De!ugging

Su!System

"alidation

Detailed

Design

mplementation

& De!ugging

Su!System

"alidation


14/41

2

CSE 4316 15


Waterfall with 1is& 1eduction Spiral for re,uirements and

architectural design phasesRequirements

Analysis

Concept

& Planning

Architectural

Design

Detailed

Design

mplementation

& De!ugging

System

"alidation


15/41

2

CSE 4316 16

E'olutionary -or 1apid. PrototypingE'olutionary -or 1apid. Prototyping

Especially useful when re,uirements are changingre,uirements are changingrapidly* or cannot %e committed

Process5

Design initial prototype of e7ternal:prominent aspects 1e'iew with customer Iterate and refine until good enough"

Ad'antages

eeps customer in'ol'ed in process3ow o'erhead

Disad'antagesImpossi%le to pro$ect schedule:%udgetCan e'ol'e to code8and8fi7


16/41


17/41

2

CSE 4316 18

Agile 4ethodologiesAgile 4ethodologies

Iterati'e and incremental de'elopment

Adapti'e planning %ased on customer andmar&et changes

Plan milestones are fle7i%le and su%$ect tochange rolling wa'e" progression

(imeBo7 de'elopment Staged -potentially shippa%le increments. Scrum


18/41

2

CSE 4316 19

6y%rid Staged Deli'ery 4odel6y%rid Staged Deli'ery 4odel

Requirements

Analysis

Concept

& Planning

Architectural

Design

#edium $igh Priority% Detailed design implement and test

#edium Priority% Detailed design implement and test

$igh Priority% Detailed design implement and test

#edium 'o( Priority% Detailed design implement and test

'o( Priority% Detailed design implement and test

Run out o) time

and money

Release

Design8to8ScheduleDesign8to8Schedulewith ris& reductionwith ris& reduction--our modelour model* appro7.* appro7.


19/41

2

CSE 4316 20

Choosing the 1ight 4odelChoosing the 1ight 4odel

Strengths and wea&nesses analysis Discussion5 (a%le @8!

Case Study @85 Effecti'e 3ifecycle4odel Selection Pro$ect characteristics Why was the model the right one?

What was the outcome?
http://top%20level%20lifecycle%20process%20model.jpg/


20/41

2

CSE 4316 21

(ools:(echni,ues to 6elp >ou(ools:(echni,ues to 6elp >ou

PE1( and CP4 (ools Program -or Pro$ect. E'aluation and 1e'iew

(echni,ue

Critical Path 4ethod -from Dupont. Account for tas& dependencies


21/41

2

CSE 4316 22


-PE1( Chart.-PE1( Chart.


22/41

2

CSE 4316 23


CoCo4o -Constructi'e Cost 4odel. Estimating tool created %y Barry Boehm

-Software Engineering Economics* !C!.

Based on si+e* comple7ity* en'ironment* teamcomposition* language* tools* etc

4ethod is %ased on a large study of 'arying

si+e significant pro$ects


23/41

2

CSE 4316 24

Wor& Brea&down StructureWor& Brea&down Structure

Brea&s down the wor& to %e done into specific*product8oriented managea%le units

Allows de'elopment of a detailed plan

Basis for pro$ect cost and scheduleEna%les assignment of responsi%ility Pro'ides %asis for accounta%ility of indi'iduals

Defines independentwor& units ; minimum

interfacing with or dependency on other wor&unitsAllows measurement of progress


24/41

2

CSE 4316 25

Wor& Brea&down StructureWor& Brea&down Structure

WBS5 Building aWBS5 Building aBicycleBicycle


25/41

2

CSE 4316 26

4ilestone (rac&ing 8


26/41

2

CSE 4316 27

6igh =uality Plans6igh =uality Plans

Characteristics* as stated in the SEI te7t Complete 1eadily accessi%le* e'en %y the customer

Clear Specific Precise

Accurate0ot in the SEI te7t* %ut necessary 4EAS1AB3E


27/41

2

CSE 4316 28

What#s ma&es aWhat#s ma&es a


28/41


29/41

2

CSE 4316 30

Product SpecificationsProduct Specifications

Pro'ide the details of whatwhatwill %e done*and howhowit will %e done5 1e,uirements Specification -S1S ; whatwhat.

Architecture Design -ADS ; %ridge%ridgewhat tohow.

Detailed Design Documentation -DDS 8 ho"ho".

(hese pro'ide the %asis for system'erification and acceptance


30/41

2

CSE 4316 31

Statement of Wor&Statement of Wor&

A narrati'e descriptionof the wor& that isto %e done5 Details of hardware and software components

Description of deli'era%les Estimate of start and stop dates for &ey

phases of process

Acceptance criteria


31/41

2

CSE 4316 32

4ilestones4ilestones

Dri'en %y the lifecycle modelyou use Esta%lishes start and stop dates for all &ey phases of

pro$ect 1einforced %y your detailed schedules

se PE1(:


32/41

2

CSE 4316 33

Processes:ProceduresProcesses:Procedures

Defines howhowthings will get done Pro'ides the %asis for esta%lishing critical

milestones and deli'era%les

Esta%lishes entry and e7it criteria for criticalphases

Esta%lishes the standards that will %e used

Defines the tools that are re,uired tocomplete the wor&


33/41

2

CSE 4316 34

Sta&eholdersSta&eholders

Any person or organi+ation that has a'ested interestin the success of youpro$ect

>our customer or sponsor >our company >our company#s owners:stoc&holders

>our management


34/41

2

CSE 4316 35

Plan Documentation and (rac&ingPlan Documentation and (rac&ing

System 1e,uirements Specification W6A(you plan to create

Pro$ect Charter

6/Wyou will go a%out the process of creatingthe W6A(

Includes 1IS 4A0A


35/41

2

CSE 4316 36

Characteristics of a


36/41

2

CSE 4316 37

Characteristics of a


37/41

2

CSE 4316 38

(ips for Successful 1e,uirement(ips for Successful 1e,uirementDeterminationDetermination

Start %y esta%lishing what the team thin&sthe features:functionsfeatures:functionsof the systemshould %e

Brainstorm as team and write e'erything down eep a simple list -such as the re,uirements

wor&sheet on the we%site.

4eet with your sponsorsponsorto re'iew:modifyyour list and discuss alternati'es Add any features:functions that the sponsor

%elie'es are re,uired


38/41

2

CSE 4316 39


Consider and add ancillary re,uirementsancillary re,uirements Eg* performance* pac&aging* loo& and feel

Discuss and add as necessary any non8non8functional" re,uirementsfunctional" re,uirements Eg* standards that you must adhere to*

maintenance and support* safety

Discuss and analy+e the feasi%ilityanaly+e the feasi%ility ofmeeting or e7ceeding each re,uirementwithin the %udget* time and s&ills allowed


39/41

2

CSE 4316 40


D/ 0/(D/ 0/( collect re,uirements %y attemptingto fill out the S1S


40/41

2

CSE 4316 41

What is a System 1e,uirementsWhat is a System 1e,uirementsSpecification -S1S.?Specification -S1S.?

A detailed descriptiondetailed description of the features andfunctions of a product* incorporating5 End8user and sponsor input

De'eloper input 4anagement input Standards and processes

>our documented commitmentcommitmentto deli'er

>our contractcontractwith your sta&eholders thatidentifies W6A( you will create

(See SRSs from prior teams on #lass website.)


41/41

building a plan

Documents