Agile Modeling and Prototyping.pptx

7/26/2019 Agile Modeling and Prototyping.pptx

1/42

AGILE MODELING AND

PROTOTYPING


2/42

Major Topics

Prototyping RAD(Rapid Application Development) Extreme Programming(XP)


3/42

SDLC

Software is created on a wellplanned pattern.

Ecient as planned. Everyting will !e as written. "oc#ses on developers$ not #sers.

%arder to &A'ER.


4/42

SDLC

PLANNING

CONSULTATION

CREATION

TESTING

LAUNCHING

DOCUMENTATION


5/42

Prototyping

*ot !ased on planning. +ne after anoter #ntil te perfect one is

formed.

,ser can test and improve-


6/42

Prototyping

Prototyping is an informationgateringtecni/#e.

0n many programming lang#ages$

a function prototypeis te declaration ofa f#nction.

Prototypes are #sef#l in see2ing #serreactions$ s#ggestions$ innovation$ and

revision plans. Prototyping may !e #sed as an alternative

to te systems development life cycle.


7/42

For !in"s o# Prototyp$s

e fo#r conceptions of prototypes are 3

Patced#p prototype.

*onoperational scale model.

"irstofaseries.

Selected "eat#res Prototype


8/42

Patc%$"&p Prototyp$

Enco#rages cooperation of di4erentdevelopers.

Everyone plays is part. A fast development model. no need to overlap in a speci5c

f#nction of wor2. needs a strong pro6ect manager. 7anager controls te wor2 8ow.


9/42

Non&Op$rationa' Prototyp$

,sed wen only a certain part of te programso#ld !e #pdated.

Speci5c part will wor2 and co#ld !e tested.

7ain prototype is not e4ected !y te&d#mmy.

0mplemented wen certain pro!lems in a

speci5c part of te program arises. Alteration and maintenance is important. smart way of creating software.


10/42

First o# a S$ri$s Prototyp$

9nown as a !eta version. Ecient if la#nced properly. P#!lic gets a cance to test. Aim is to receive feed!ac2s. :est to test 5rewall and sec#rity. 0t co#ld !e ac2ed$ !ac25re and

destroyed.


11/42

S$'$ct$" F$atr$sPrototyp$

"#ll version software !#t &'070ED. 0s applied to a !igger s#ite of programs. 0ndependent of s#ite. o test independent feat#res.


12/42

Typ$s o# Prototyping


13/42

Prototyp$ Mo"$' Disa"(antag$s

7odels presented in te early stage arenot complete.

,s#ally tey lac2 8aws.

Doc#mentation is a nigtmare.


14/42

Prototyp$ Mo"$'A"(antag$s

7ore e4ort is placed in creating teact#al software.

Red#cing man o#rs in creating a

software. Software is created #sing lots of #ser

feed!ac2s.

&+ver Design co#ld also !e avoided. %as great advantage over oter SD';

models.


15/42

Rapi" App'ication

D$($'op)$nt *RAD+


16/42

Rapi" App'ication

D$($'op)$nt*RAD+

Software is not a pysical tool tat can !e lostonce it gets developed.

'ittle canges are made in te interface tomeet te re/#irement of te client.

ools as code generators are in te mar2et.

RAD an o!6ectoriented approac to systemsdevelopment.

"oc#ses more on te vis#al instead of tecoding.


17/42

Ho, RAD is "i-$r$nt #ro) ot%$r

SDLC syst$)s.


18/42

RAD P%as$s

e tree !road pases to RAD are 3 Re/#irements planning.

RAD design wor2sop.

0mplementation.


19/42

R$/ir$)$nts P'anningP%as$ ,sers and analysts meet to identify

o!6ectives of te application or system +riented toward solving !#siness

pro!lems


20/42

RAD D$sign 0or1s%op

Design and re5ne pase.

Programmers and analysts can !#ild and sowvis#al representations of te designs andwor28ow to #sers.

Analysts re5ne designed mod#les !ased on#ser responses.


21/42

I)p'$)$ntation P%as$

As te systems are !#ilt and re5ned$ tenew systems or partial systems aretested and introd#ced to te

organi


22/42

RAD P%as$s


23/42

RAD an" t%$ SDLC

RAD tools are #sed to generate screensand exi!it te overall 8ow of teapplication.

,sers approve te design and sign o4 onte vis#al model. 0mplementation is less stressf#l !eca#se

#sers elp to design te !#siness aspects

of te system.


24/42

0%$n to Us$ RAD

RAD is #sed wen3e team incl#des programmers and analysts

wo are experienced wit it.ere are ard pressing reasons for speeding

#p application development.e pro6ect involves a *ovel ecommerce

application and needs /#ic2 res#lts. ,sers are sopisticated and igly engaged

wit te goals of te company.


25/42

Disa"(antag$s o# RAD

is re/#ires igly s2illed developers. Re/#ires longer percentage of time of

sta2eolders and #sers tan oter

approaces.


26/42

E2tr$)$ Progra))ing *3P+


27/42

Extreme programming (XP) takesgood systems developmentpractices to the extreme.

It is denoted by XP.

E2tr$)$ Progra))ing *3P+


28/42

9endall > 9endall ? @B Pearson Prentice %all C@

For 4a'$s o# E2tr$)$Progra))ing

;omm#nication. Simplicity. "eed!ac2. ;o#rage.


29/42

9endall > 9endall ? @B Pearson Prentice %all C@

Fi($ 3P Princip'$s

Providing rapid feed!ac2. Ass#ming simplicity. ;anging incrementally. Em!racing cange. Enco#raging /#ality wor2.


30/42

9endall > 9endall ? @B Pearson Prentice %all CF

Fi($ 3P Princip'$s


31/42

9endall > 9endall ? @B Pearson Prentice %all CFG

For 5asic Acti(iti$s o# 3P

;oding. esting. 'istening$ to te programming partner

and c#stomer. Designing.


32/42

9endall > 9endall ? @B Pearson Prentice %all CF@

For 3P R$sorc$ Contro'4aria6'$s

ime. ;ost. Scope. H#ality.


33/42

9endall > 9endall ? @B Pearson Prentice %all CFF

For 3P Cor$ Practic$s

e fo#r XP core practices are3 Sort releases$ wor2 wit te most important

feat#res 5rst.

%aving a Io#r wor2 wee2. %aving an onsite c#stomer.

Pair programming wit anoter programmer.


34/42

9endall > 9endall ? @B Pearson Prentice %all CFI

3P R$'ations%ips


35/42

9endall > 9endall ? @B Pearson Prentice %all CFB

3P D$($'op)$nt Proc$ss

e pases of te XP development processare3 Exploration.

Planning. 0terations to te 5rst release.

Prod#ctioni


36/42

9endall > 9endall ? @B Pearson Prentice %all CFC

3P Stori$s

XP stories are a spo2en interaction!etween developers and #sers.

0t is not written comm#nication.

e goal is prevention ofmis#nderstanding or misinterpretationsof #ser re/#irements.


37/42

9endall > 9endall ? @B Pearson Prentice %all CFJ

3P L$ssons

e six lessons tat can !e drawn fromte XP development approac are3 Sort releases allow te system to evolve.

Pair programming enances overall /#ality. +nsite c#stomers are m#t#ally !ene5cial to

te !#siness and te XP team.


38/42


3P L$ssons

e six lessons tat can !e drawn fromte XP development approac(contin#ed)

e Io#r wor2 wee2 improves wor2ere4ectiveness. :alanced reso#rces and activities s#pport

pro6ect goals.

XP val#es are cr#cial to s#ccess.

3P L$ssons


39/42


3P L$ssons


40/42

9endall > 9endall ? @B Pearson Prentice %all CI

Agi'$ Mo"$'ing

Agile modeling is similar to XP. 0n addition to te val#es of

comm#nication$ simplicity$ feed!ac2 and

co#rage$ it as a 5ft val#e of #mility.


41/42

9endall > 9endall ? @B Pearson Prentice %all CIG

Agi'$ Mo"$'ing *Contin$"+

Agile modeling process is3 'isten to #ser stories.

Draw a logical wor28ow model.

;reate new #ser stories !ased on tewor28ow.

Develop some prototypes.

,se feed!ac2 from te prototypes and logical

wor28ow to create pysical model.


42/42

Scr)

Scr#m is an Agile approac tat as anempasis on teamwor2.

eam s#ccess is of primary importance.

0ndivid#al s#ccess is secondary. e team wor2s witin a strict time

frame. e pro6ect leader as some !#t not

m#c in8#ence on detail.

Date post:	02-Mar-2018
Category:	Documents
Upload:	ali-goher-shabir
View:	220 times
Download:	0 times

Agile Modeling and Prototyping.pptx

Documents