Systems Analysis and Design ith

(1)

Syst e m s An a lysis a n d

Alan Dennis Barbara Wixom and David

Alan Dennis, Barbara Wixom , and David

Tegarden

(2)

Copyright © 2005

J h Wil

& S

I

John Wiley & Sons, I nc.

All right s reserved. Reproduct ion or t ranslat ion of t his

work beyond t hat perm it t ed in Sect ion 117 of t he 1976

Unit ed St at es Copyright Act wit hout t he express writ t en

perm ission of t he copyright owner is unlawful.

p

py g

Request for furt her inform at ion should be addressed t o

t he Perm issions Depart m ent , John Wiley & Sons, I nc.

The purchaser m ay m ake back- up copies for his/ her own

The purchaser m ay m ake back up copies for his/ her own

use only and not for redist ribut ion or resale.

The Publisher assum es no responsibilit y for errors,

om issions, or dam ages, caused by t he use of t hese

(3)

Pr oj e ct M a n a ge m e n t

(4)

Obj

t i

Obj e ct ive s

■

Become familiar with estimation

■

Become familiar with estimation.

■

Be able to create a project workplan.

■

Understand why project teams use

■

Understand why project teams use

timeboxing.

■

Become familiar with how to staff a project.

p j

■

Understand how computer-aided software

engineering,

improve the efficiency of a project.

(5)

K

D fi it i

Ke y D e fin it ion s

Proj ect m anagem ent

is t he process

Proj ect m anagem ent

is t he process

of planning and cont rolling t he

developm ent of a syst em w it hin a

(6)

Est im a t in g a Pr oj e ct Ba se d

Applic a tio ns

Tim e

Re q uire d

4 5 33

9 33

8 Re q uire d

4

5.33

9.33

8 in Pe rso n

(7)

F

t i

P i t

input s, out put s, queries, files, and

program int erfaces

Est im a t e e ffor t r e qu ir e d

Person Mont hs

(8)

Tim e Est im a t ion Usin g a

M

C

l

A

h

(9)

Ge t t in g t h e Righ t

N u m be r s for Est im a t ion

Prior proj ect s

Past experience

I ndust ry st andards

(10)

Est im a t ion Tr a de - offs

Est im a t ion Tr a de offs

Size

Funct ion point s

Li

f d

Lines of code

Effort

Person- m ont hs

People available

p

(11)

C l

l t F

t i

P i t

Ca lcu la t e Fu n ct ion Poin t s

List m aj or elem ent s of syst em

Det erm ine t ot al num ber of each

l

t

elem ent

Specify com plexit y index of

each com ponent ( low, m ed.,

high)

g )

(12)

Fu n ct ion Poin t Est im a t ion

St

O

- -

St e p On e

C

l

i

Complexity

Description

Low

Medium

High

Total

I

3

4

6

(13)

(14)

Adj u st e d Pr oce ssin g

C

l

i

S

2

(15)

Fu n ct ion Poin t s Est im a t ion

St

F

- -

St e p Fou r

Adjusted Project Complexity

065 (0 01 * P j

t C

l

it )

=

.065 + (0.01 * Project Complexity)

Total Adjusted Function Points

j

=

(16)

Fu n ct ion Poin t Est im a t ion

Processing Com plexit y ( PC) : 7____

( From St ep 2)

Adj ust ed Processing

Com plexit y ( PCA) =

0.65 + ( 0.001 *

7 )

Com plexit y ( PCA)

0.65 + ( 0.001 __7_ )

Tot al Adj ust ed

Funct ion Point s:

0 72 * 338

243 Funct ion Point s:

_0.72 * _338_ = 243

(17)

Con ve r t in g Fu n ct ion

Poin t s t o Lin e s of Code

Language

LOC/ Funct ion Code Point

Language

LOC/ Funct ion Code Point

(18)

Fi

l St

Fin a l St e p

Mult iply funct ion point s

Approxim at e lines of code per

(19)

Est im a t in g Effor t

(20)

COCOM O Est im a t ion

C l

l t i

Ca lcu la t ion

Effort =

1.4 *

thousands-of-(in Person-

lines-of-code

(

f

Months)

E

l

Example:

If LOC = 2000 Then...

f

(21)

Est im a t in g Sch e du le Tim e

Rule of t hum b for est im at ion

Schedule Time (months)

=

3 0 * p s n m nths

1/3

(22)

St ffi

At t ib t

St a ffin g At t r ibu t e s

St affing levels will change over

a proj ect ’s lifet im e

Adding st aff m ay add m ore

(23)

I n cr e a sin g Com ple x it y

it h L

T

(24)

(25)

D

l

i

W

k Pl

D e ve lopin g a W or k Pla n

I dent ify t asks in t he proj ect

Est im at e t ask lengt h

Det erm ine t ask dependencies

Specify t o whom t ask will be

assigned

(26)

A W

k l

E

l

A W or k pla n Ex a m ple

Work Plan I nform at ion

Exam ple

Work Plan I nform at ion

Exam ple

Nam e of t ask

Perform econom ic feasibilit y

Nam e of t ask

Perform econom ic feasibilit y

St art dat e

`

Jan 05, 2001

Com plet ion dat e

Jan 19, 2001

Person assigned

g

Mary Sm it h, sponsor

y

, p

Deliverable( s)

Cost- benefit analysis

Com plet ion st at us

Open

Priorit y

High

Resources needed

Spreadsheet

Est im at ed t im e

16 hours

(27)

I de n t ifyin g Ta sk s

Top- dow n approach

I dent ify highest level t asks as

phases in t he proj ect

Break t hem int o increasingly

sm aller unit s

Met hodology

(28)

Top D ow n Ta sk

I d

t ifi

t i

I de n t ifica t ion

Phases

_{high level steps}

Phases with

Wo rk Pla n

De live ra b le s

Estima te d

Assig ne d

ho urs

To

(29)

W

k B

k d

S

W or k Br e a k dow n St r u ct u r e

Specify high level t asks

Break down each st ep int o

sm aller t asks and num ber t hem

in a hierarchical fashion

WBS can be done in t wo ways

SDLC h

(30)

(31)

E

l t i

W BS

Evolu t ion a r y W BS

organize in a st andard m anner across all

proj ect s

(32)

P

j

t W

k Pl

(33)

(34)

K

D fi it i

Ke y D e fin it ion s

The

st affing plan

describes t he kinds

The

st affing plan

describes t he kinds

of people working on t he proj ect

The

proj ect chart er

describes t he

The

proj ect chart er

describes t he

proj ect ’s obj ect ives and rules

A

funct ional lead

m anages a group of

A

funct ional lead

m anages a group of

analyst s

A

t

h i

l l

d

f

(35)

M t i

t i

M ot iva t ion

Use m onet ary rew ards caut iously

Use int rinsic rewards

(36)

Con flict Avoida n ce

St

t

i

St r a t e gie s

Clearly define roles and proj ect plans

Hold individuals account able

Proj ect chart er list ing norm s and

groundrules

Develop schedule com m it m ent s ahead of

t im e

(37)

P

ibl

R

i

S

(38)

CON TROLLI N G AN D

D I RECTI N G TH E

(39)

(40)

M a r gin s of Er r or in

Cost a n d Tim e Est im a t e s

Typ ic a l ma rg ins o f Erro r fo r

We ll-d o ne Estima te s

Pha se

De live ra b le

C o st (%)

time (%)

Pla nning

Syste m Re q ue st

400

60 Pro je c t Pla n

100

25 Ana lysis

Syste m Pro p o sa l

50

15 D

i

S t

S

ifi

ti

25

10

(41)

(42)

PERT Ch

t

PERT Ch a r t s

Proj ect Evaluat ion and Review

Technique ( PERT)

Pessim ist ic, P

(43)

(44)

CASE Tools

Initiation Analysis Design Implementation

Upper CASE

Lower CASE

Upper SE

Lower SE

(45)

CASE C

t

Diagram s

Screen

CASE Com pon e n t s

Diagram s

Screen

Designs

CASE Reposit ory

P

d

l

M t d t

Procedural

Met adat a

(46)

St a n da r ds

Exam ples

Form al rules for nam ing files

Form s indicat ing goals reached

Program m ing guidelines

(47)

D ocu m e n t a t ion

Proj ect binder

(48)

M

i

S

M a n a gin g Scope

Scope creep

a m aj or cause of

Scope creep - - a m aj or cause of

developm ent problem s

JAD and prot ot yping

(49)

Tim e box in g

Fixed deadline

Make deadline possible

Set by developm ent group

Reduced funct ionalit y if

Reduced funct ionalit y, if

necessary

(50)

Ti

b

i

St

Tim e box in g St e ps

1 Set the date for system delivery

1. Set the date for system delivery.

2. Prioritize the functionality that needs to be

included in the system.

y

3. Build the core of the system (the functionality

ranked as most important).

4. Postpone functionality that cannot be provided

within the time frame.

5 Deliver the system with core functionality

5. Deliver the system with core functionality.

6. Repeat steps 3 through 5, to add refinements

and enhancements.

(51)

M a n a gin g Risk

Risk assessm ent

(52)

Cl

i M i t k

Cla ssic M ist a k e s

Overly opt im ist ic schedule

Failing t o m onit or schedule

Failing t o updat e schedule

(53)

S

Su m m a r y

Proj ect m anagem ent is crit ical

t o successful developm ent of

new syst em s

Proj ect m anagem ent involves

planning, cont rolling and

(54)

E

di

t h

D

i

inform at ion syst em s:

www pm i org

www .pm i.org