Kendall Sad9 Pp 1

7/24/2019 Kendall Sad9 Pp 1

1/51

Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice all 1!1

1

"yste#s, $oles, and

%eelop#ent'ethodologies


2/51

Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prenticeall 1!2

Intended (earning

)utco#es* +nderstand the need or syste#s

analysis and design in organi-ations.

* $eali-e hat the #any roles o thesyste#s analyst are.

* Co#prehend the unda#entals o threedeelop#ent #ethodologies/

* "%(C*he agile approach

* )bect!oriented syste#s analysis and design


3/51

eaching and (earning

ctiities* %iscussion

* Proble#!based Presentation

1!3


4/51

ssess#ent ass

* Case "tudy

* $ecitation

1!4


5/51

1!5

opics

* 6unda#entals o di7erent inds oinor#ation syste#s

* $oles o syste#s analysts

* Phases in the syste#s deelop#entlie cycle as they relate to u#an!

Co#puter Interaction 8CI9 actors* C"E tools

* )pen "ource "otare


6/51

1!:

;eed or "yste#s nalysis

and %esign* Installing a syste# ithout proper planning

leads to great user dissatisaction and

re


7/511!=

$oles o the "yste#s

nalyst*he analyst #ust be able to or

ith people o all descriptions and

be e>perienced in oring ithco#puters

*hree pri#ary roles/

* Consultant* "upporting e>pert

* gent o change


8/511!?

@ualities o the "yste#s

nalyst* Proble# soler

* Co##unicator

* "trong personal and proessionalethics

* "el!disciplined and sel!#otiated


9/511!A

"yste#s %eelop#ent (ie

Cycle 8"%(C9*he syste#s deelop#ent lie cycle

is a phased approach to soling

business proble#s* %eeloped through the use o a

speciBc cycle o analyst and user

actiities* Each phase has uni


10/511!10

he "een Phases o the"yste#s %eelop#ent (ie Cycle86igure 1.19


11/511!11

Incorporating u#an!

Co#puter Interaction 8CI9Considerations*he de#and or analysts ho are

capable o incorporating CI into the

syste#s deelop#ent process eepsincreasing, as co#panies begin toreali-e that the


12/511!12

Identiying Proble#s,

)pportunities, and )becties* ctiity/

* Interieing user #anage#ent

* "u##ari-ing the noledge obtained

* Esti#ating the scope o the proect

* %ocu#enting the results


13/511!13

Identiying Proble#s,

)pportunities, and )becties* )utput/

* 6easibility report containing proble#

deBnition and obectie su##ariesro# hich #anage#ent can #ae adecision on hether to proceed iththe proposed proect


14/511!14

%eter#ining u#an

Inor#ation $e


15/51

1!15

%eter#ining u#an

Inor#ation $e


16/51

1!1:

naly-ing "yste# ;eeds

* ctiity/

* Create data Fo, actiity, or se


17/51

1!1=

%esigning the $eco##ended

"yste#* ctiity/

* %esign procedures or data entry

* %esign the hu#an!co#puter interace* %esign syste# controls

* %esign database andGor Bles

* %esign bacup procedures* )utput

* 'odel o the actual syste#


18/51

1!1?

%eeloping and %ocu#enting

"otare* ctiity/

* "yste# analyst ors ith progra##ers

to deelop any original sotare* Hors ith users to deelop e7ectie

docu#entation

* Progra##ers design, code, and re#oe

syntactical errors ro# co#puter progra#s* %ocu#ent sotare ith help Bles,procedure #anuals, and Heb sites ith6re


19/51

1!1A

%eeloping and %ocu#enting

"otare*)utput/

* Co#puter progra#s

* "yste# docu#entation


20/51

1!20

esting and 'aintaining the

"yste#* ctiity/

*est the inor#ation syste#

* "yste# #aintenance* 'aintenance docu#entation

* )utput/

* Proble#s, i any* +pdated progra#s

* %ocu#entation


21/51

1!21

I#ple#enting and Ealuatingthe "yste#

* ctiity/*rain users

* nalyst plans s#ooth conersion ro#old syste# to ne syste#

* $eie and ealuate syste#

* )utput/*rained personnel

* Installed syste#


22/51

1!22

"o#e $esearchers Esti#ate that the #ount o i#e"pent on "yste#s 'aintenance 'ay De as 'uch as :0Percent o the otal i#e "pent on "yste#s Proects

86igure 1.29


23/51

1!23

he I#pact o 'aintenance

* 'aintenance is peror#ed or toreasons/

* $e#oing sotare errors* Enhancing e>isting sotare

* )er ti#e the cost o continued#aintenance ill be greater than that

o creating an entirely ne syste#. tthat point it beco#es #ore easibleto peror# a ne syste#s study.


24/51

1!24

$esource Consu#ption oer the"yste# (ie 86igure 1.39


25/51

1!25

pproaches to "tructured nalysis and%esign and to the "yste#s %eelop#ent

(ie Cycle

*raditional syste#sdeelop#ent lie cycle

*C"E syste#s deelop#entlie cycle

*)bect!oriented syste#sanalysis and design


26/51

1!2:

Case ools

* C"E tools are productiitytools or syste#s analysts that

hae been created e>plicitly toi#proe their routine orthrough the use o auto#ated

support


27/51

1!2=

$easons or +sing Case

ools* $easons or using C"E tools

* Increasing analyst productiity

* I#proing analyst!userco##unication

* Integrating lie cycle actiities


28/51

1!2?


29/51

1!2A

he gile pproach

* Dased on/

* alues

* Principles

* Core practices


30/51

1!30

gile alues

* Co##unication

* "i#plicity

* 6eedbac

* Courage


31/51

1!31

6our gile $esources

* $esources are adusted to ensuresuccessul proect co#pletion

*i#e

* Cost

* @uality

* "cope


32/51

1!32

6ie "tages o gile%eelop#ent

* E>ploration

* Planning

* Iterations to the Brst release

* Productioni-ing

* 'aintenance


33/51

1!33

gile Proect %eelop#entProcess 86igure 1.59


34/51

1!34

)bect!)riented 8)!)9 "yste#snalysis and %esign

* lternate approach to the structuredapproach o the "%(C that is intended

to acilitate the deelop#ent osyste#s that change rapidly inresponse to dyna#ic businesseniron#ents

* nalysis is peror#ed on a s#all part othe syste# olloed by design andi#ple#entation


35/51

1!35

)bect!)riented 8)!)9 "yste#snalysis and %esign

*he cycle repeats ith analysis,design, and i#ple#entation o

the ne>t part and this repeatsuntil the proect is co#plete

* E>a#ines the obects o asyste#


36/51

1!3:

+niBed 'odeling (anguage8+'(9 Phases

* %eBne the use case #odel/

* +se case diagra#

* +se case scenarios* Create +'( diagra#s

* %eelop class diagra#s

* %ra statechart diagra#s* 'odiy the +'( diagra#s

* %eelop and docu#ent the syste#


37/51

1!3=


38/51

1!3?

Choosing a 'ethod

* Choose either/

* "%(C

* gile

* )bect!oriented #ethodologies


39/51

1!3A

Hhen to +se "%(C

* "yste#s hae been deeloped anddocu#ented using "(%C

* It is i#portant to docu#ent each step* +pper leel #anage#ent eels #ore

co#ortable or sae using "%(C

*here are ade


40/51

1!40

Hhen to +se gile

* here is a proect cha#pion o agile #ethodsin the organi-ation

* pplications need to be deeloped ecuties and analysts agree ith the

principles o agile #ethodologies


41/51

1!41

Hhen to +se )bect!

)riented*he proble#s #odeled lend the#seles to

classes

* n organi-ation supports the +'( learning

* "yste#s can be added gradually, onesubsyste# at a ti#e

* $euse o preiously ritten sotare is a

possibility* It is acceptable to tacle the diJcultproble#s Brst


42/51

1!42

)pen "ource "otare

* n alternatie o traditional sotaredeelop#ent here proprietary code ishidden ro# the users

* )pen source sotare is ree to distribute,share, and #odiy

* Characteri-ed as a philosophy rather thansi#ply the process o creating nesotare

* E>a#ples/ (inu> )perating "yste#,pache Heb "erer, 'o-illa 6ireo>


43/51

1!43

6our ypes o )pen "ourceCo##unities/

* d hoc

* "tandardi-ed

* )rgani-ed

* Co##ercial


44/51

1!44

"i> Key %i#ensions that%i7erentiate )pen "ource

Co##unities* eneral structure

* Eniron#ent

* oals

* 'ethods

*+ser co##unity

* (icensing


45/51

1!45

$easons or Participating in)pen "ource Co##unities

* $apidity ith hich ne sotarecan be deeloped and tested

* 6aster to hae a co##itted group oe>perts deelop, test, and debugcode

*his osters creatiity* ae #any good #inds or ith

innoatie applications


46/51

1!4:

$easons or Participating in)pen "ource Co##unities

* Potential to reduce deelop#entcosts

* Dolster their sel!i#age

* Contribute so#ething orthhileto the sotare deelop#ent

co##unity


47/51

1!4=

)pen "ource Contribution and%i7erentiation

* Contributions to the openco##unity and di7erentiation

ro# the open co##unity are orthe olloing reasons/* Cost

* 'anaging resources

*i#e it taes to bring a ne productto the #aret


48/51

1!4?

$easons or nalystParticipation in the )pen"ource Co##unity* Curiosity about sotare beneBts

* chiee collectie design

* Incorporate open source sotaredesign into/

* Proprietary products

* Processes* Knoledge

* I artiacts


49/51

1!4A

Collectie %esign

*hrough a process o collectiedesign the I artiact is i#bued

ith* Co##unity and organi-ational

structures

* Knoledge* Practices


50/51

1!50

"u##ary

* Inor#ation is a ey resource

* Integration o traditional syste#s ith netechnologies

* $oles and


51/51

Copyright 2014 Pearson Education, Inc.Copyright 2014 Pearson Education, Inc.

Publishing as Prentice allPublishing as Prentice all

Kendall Sad9 Pp 1

Documents

Transcript of Kendall Sad9 Pp 1