SE 29 Nov 2011

W SysLems analysls and deslgn Lhe process of
deslgnlng bulldlng and malnLalnlng

lnformaLlon sysLems
SysLems analysL
W 8lendlng Lechnlcal and managerlal experLlse
SLeps lnvolved ln Analysls and ueslgn
18equlremenLs ueLermlnaLlons
28equlremenLs SpeclflcaLlons
3leaslblllLy Analysls
4llnal SpeclflcaLlons
3Pardware SLudy
6SysLem ueslgn
7SysLem lmplemenLaLlon
8SysLem LvaluaLlon
9SysLem ModlflcaLlon
Step 1 kequ|rements
Determ|nat|on
W 9rlorlLles among appllcaLlons deLermlned
W 9lck hlgh prlorlLy appllcaLlons
W Arrlved aL by a consensus among managers
W Step 2 kequ|rements Spec|f|cat|on
W DndersLand Lhe exlsLlng SysLem
W AppllcaLlons where a sysLem ls requlred are llsLed
W Arrlve aL Lhe speclflcaLlons of Lhe users 8equlremenLs
W afLer dlscusslons wlLh Lhe user
W A sysLem may encompass several appllcaLlons
W known as SysLem 8equlremenLs SpeclflcaLlon (S8S)
W Step 3 Ieas|b|||ty Ana|ys|s
W lormulaLe Coals of Lhe sysLem and quanLlfy goals
W llnd alLernaLlve meLhods of meeLlng Lhe goals
W lor each alLernaLlve assess resources needed
Puman 8esources
1lme and Money
LqulpmenL needed
Assess cosL of each alLernaLlve
W rrllnd Lhe besL alLernaLlve meLhod sub[ecL Lo resource
consLralnLs
Step 4 I|na| Spec|f|cat|ons
W Spec|f|cat|ons wou|d state what the system wou|d
ach|eve
W Spec|f|cat|on drawn up are |mproved for
|mp|ementat|on
W SkS wr|tteng|ven to user and agreement reached
LIIL
W Step S nardware Study
W ueLermlne 8esponse Llme volume of daLa Lo
be processed lrequency of reporLs eLc Lhen
W plck Lhe hardware
W ueLermlne Pardware and SofLware requlred Lo
execuLe Lhe appllcaLlon
Step 6 System Des|gn
W 1esL 9lan
W lmplemenLaLlon 9lan urawn up
W uaLabase ueslgned
W Cb[ecLs ldenLlfled
W 9rogram SpeclflcaLlon drawn up
W Loglcal ueslgn of Lhe SysLem
Step 7 System Imp|ementat|on
W 1esL and AccepL
W uocumenL SysLem
W CreaLe uaLabase
W 1rlal run of Lhe sysLem
W 1raln Dsers
W WrlLe 9rograms
Step 8 System eva|uat|on
W I|nd out from Users whether the System meets
spec|f|ed requ|rements
W L|st areas of d|ssat|sfact|on and f|nd reasons
Suggest |f there has to be any |mprovements to
the system
Step 9 System Mod|f|cat|on
W rrAdd/ueleLe feaLures as requlred by users
W rrllx errorsrrConLlnuously monlLor sysLem and
assessperformancerr1une Lhe SysLem
kCLL CI SS1LMS ANALS1
1) Def|n|ng kequ|rementsInvo|ves
Interv|ew|ng Users
2) r|or|t|z|ng kequ|rementsCbta|n Users
Consensus
3) Iact Gather|ngData Iacts Cp|n|ons of
Managers Lower |eve| Users shou|d be
consu|ted
4) Ana|ys|s and eva|uat|onArr|ve at
appropr|ate system
S) So|v|ng prob|ems
nazy requ|rements converted |nto spec|f|c
requ|rements
Suggest many a|ternat|ve so|ut|ons uant|fy
6) Draw|ng up spec|f|cat|ons
IUNC1ICNAL SLCIIICA1ICNS
Understood by users and programmers
Accepted by users
rec|se and deta||ed
Account for poss|b|e changes17
7) SS1LM DLSIGN
Log|ca| des|gn of system
Cb[ects |dent|f|cat|on
Norma||z|ng database
1est p|an
Des|gn must be modu|ar to accommodate change
8) Lva|uat|ng Systems
Lva|uat|on after use for somet|me
|an per|od|c|ty for eva|uat|on
Mod|fy as needed
A11kI8U1LSCI A SS1LMS ANALS1
1) kNCWLLDGL CI CkGANISA1ICNknowlng user's
[argon pracLlcesknow ManagemenL funcLlons
2) kNCWLLDGL CI CCMU1LkS AND SCI1WAkL
knowledge of sysLem deslgn Lools
keep abreasL of modern developmenLs
3) GCCD IN1LkLkSCNNAL kLLA1ICNS
need Lo work as Leam member
Lead smaller Leams
lnLerface wlLh programmers Dsers
MoLlvaLor
4) A8ILI1 1C CCMMUNICA1L
Cral 9resenLaLlon
S) 8kLAD1n CI kNCWLLDGL
8road Llberal knowledge
varleLy of [obs Lo be Lackled ln dlverse
organlzaLlons
6) ANAL1ICAL MIND
9roblem solvlng aLLlLudeAblllLy Lo assess Lrade offs
Sound commonsenseCurloslLy Lo learn abouL
new organlzaLlonsrr
1CCLS USLD 8 SS1LMS ANALS1
W uaLa llow ulagram
W ueclslon 1ables
W Modellng Language such as DML
W normallzaLlon of uaLabases
W 1esLlng Lools
W lSC/CMM procedure manuals
WhaL ls SofLware?
SofLware ls a seL of lLems or ob[ecLs
LhaL form a conflguraLlon" LhaL
lncludes
- programs
- documenLs
- daLa
sofLware ls englneered
sofLware doesn'L wear ouL
sofLware ls complex
sofLware ls a 'dlfferenLlaLor'
sofLware ls llke an 'aglng facLory'
SofLware ls a seL of lLems or ob[ecLs
LhaL form a conflguraLlon" LhaL
lncludes
- programs
- documenLs
- daLa
sofLware ls englneered
sofLware doesn'L wear ouL
sofLware ls complex
sofLware ls a 'dlfferenLlaLor'
sofLware ls llke an 'aglng facLory'
SecLlon l
ueveloplng e8uslness SysLems
lnformaLlon SysLems uevelopmenL
W 1he sysLems approach Lo problem solvlng
applled Lo Lhe developmenL of lnformaLlon
sysLem soluLlons Lo buslness problems
W SelecL Lhe sysLem soluLlon LhaL besL meeLs your
requlremenLs
W ueslgn Lhe selecLed sysLem soluLlon
W lmplemenL and evaluaLe Lhe success of Lhe deslgned
sysLem
1he need for SLrucLured SysLems
uevelopmenL
W SysLems analysls and deslgn Lhe process of
deslgnlng bulldlng and malnLalnlng
lnformaLlon sysLems
SysLems analysL
W 8lendlng Lechnlcal and managerlal experLlse
1he need for SLrucLured SysLems
uevelopmenL
W CpLlons for CbLalnlng lnformaLlon SysLems
W 8ulld your own
W 8uy a prepackaged sysLem
W CuLsource developmenL Lo a 3rd parLy
W Lnd user developmenL
SLeps ln Lhe SysLems uevelopmenL

9rocess
Ma|ntenance
W 9hase 1 SysLem ldenLlflcaLlon SelecLlon and
9lannlng
DnderLake only Lhose pro[ecLs crlLlcal Lo mlsslon
goals and ob[ecLlves
SelecL a developmenL pro[ecL from all posslble
pro[ecLs LhaL could be performed
ulfferenL evaluaLlon crlLerla used Lo rank poLenLlal
pro[ecLs
SLeps ln Lhe SysLems
uevelopmenL 9rocess
1 Invest|gat|on 1 Invest|gat|on
SysLems uevelopmenL 9rocess
W SysLems lnvesLlgaLlon 9hase
leaslblllLy sLudles
W 9hase 1 SysLem ldenLlflcaLlon SelecLlon and
9lannlng
LvaluaLlon crlLerla
W SLraLeglc allgnmenL
W 9oLenLlal beneflLs
W 9oLenLlal cosLs and resource avallablllLy
W 9ro[ecL slze / duraLlon
W 1echnlcal dlfflculLy / rlsks
uevelopmenL 9rocess
W 9hase 2 SysLem Analysls
ueLermlnlng As ls and 1o 8e
Modellng CrganlzaLlonal uaLa
W LnLlLy 8elaLlonshlp ulagram (L8u)
Modellng CrganlzaLlonal 9rocesses and Loglc
W uaLa flows
W 9rocesslng loglc
uevelopmenL 9rocess
2 Ana|ys|s 2 Ana|ys|s
Soccer Camp Application Process
2

A
n
a
|
y
s
|
s
2

A
n
a
|
y
s
|
s
ulu example
2 Ana|ys|s 2 Ana|ys|s
SysLems ueslgn
W 9hase 3 SysLem ueslgn
Speclfles PCW Lhe sysLem wlll meeL Lhe lnformaLlon needs
of users
W locuses on Lhree ma[or producLs
Dser lnLerface deslgn
uaLa deslgn
W uaLabase sLrucLures
9rocess deslgn
W 9rocesslng and conLrol procedures
3 Des|gn 3 Des|gn
SysLems ueslgn (cLd)
W Dser lnLerface deslgn
locuses on supporLlng Lhe lnLeracLlons beLween
end users and Lhe compuLerbased appllcaLlons
W ulsplay screens
W lnLeracLlve user/compuLer dlalogues
W Audlo responses
W lorms documenLs and reporLs
3 Des|gn 3 Des|gn
SysLems ueslgn (cLd)
W SysLem speclflcaLlons
lormallzes Lhe deslgn of Lhe appllcaLlon's user
lnLerface meLhods producLs
lormallzes daLabase sLrucLures
lormallzes processlng and conLrol procedures
3 Des|gn 3 Des|gn
SecLlon ll
lmplemenLlng e8uslness SysLems
SysLem lmplemenLaLlon
W 9hase 4 1he acLual developmenL of lS
soluLlons
4 Imp|ementat|on 4 Imp|ementat|on
LvaluaLlng Pardware SofLware
Servlces
W May requlre suppllers Lo presenL blds and
proposals based on sysLem speclflcaLlons
W Mlnlmum accepLable physlcal performance
characLerlsLlcs for all hardware and sofLware
requlremenLs are esLabllshed
W Large buslnesses and governmenL agencles formallze
requlremenLs by llsLlng Lhem ln a 8equesL for 9roposal
(8l9) or a 8equesL for CuoLaLlon (8lC)
LvaluaLlng Pardware SofLware
Servlces(cLd)
W May use a scorlng sysLem for evaluaLlon
ueLermlne evaluaLlon facLors and asslgn polnLs
W 9erformance of hardware and sofLware musL
be demonsLraLed and evolooteJ evolooteJ
May use benchmark LesL programs
A sample evaluaLlon
W ln order Lo seL up qulckly and effecLlvely an
evaluaLlon process we suggesL Lo proceed wlLh Lhe
followlng sLeps
Crganlze an evaluaLlon model by dlvldlng lL lnLo
CCM9CnLn1S (LhaL are Lhe maln loglcal evaluaLlon unlL)
and u8lvL8S (LhaL are Lhe baslc loglcal unlL)
ueflne a speclflc welghL for each model componenL and
each componenL drlver
LvaluaLe Lhe speclflc drlvers for each candldaLe
Analyze Lhe sLandard reporLs generaLed
Make a recommendaLlon
W 9hase 4 SofLware uevelopmenL
SofLware programmlng
SofLware LesLlng
W uevelopmenLal
1esLlng Lhe correcLness of lndlvldual modules and
Lhe lnLegraLlon of mulLlple modules
W Alpha
1esLlng Lhe overall sysLem Lo see lf lL meeLs Lhe
deslgn requlremenLs
W 8eLa
1esLlng Lhe capablllLles of Lhe sysLem ln Lhe user
envlronmenL and wlLh acLual daLa
SysLems uevelopmenL
9rocess
W 9hase 4 SysLem lmplemenLaLlon
SysLem converslon
W 9arallel
W ulrecL
W 9hased
W 9lloL
SysLem documenLaLlon Lralnlng and supporL
W Dser and reference guldes
W 1ralnlng and LuLorlals
W lnsLallaLlon procedures and LroubleshooLlng guldes
SysLems uevelopmenL
9rocess
W 9hase 3 SysLem MalnLenance
MalnLenance process sLeps
W CbLaln malnLenance requesL
W 1ransform requesLs lnLo changes
W ueslgn changes
W lmplemenL changes
uevelopmenL 9rocess
S Ma|ntenance
W 9hase 3 SysLem MalnLenance
MalnLenance Lypes
W CorrecLlve malnLenance
W AdapLlve malnLenance
W 9erfecLlve malnLenance
W 9revenLlve malnLenance
uevelopmenL 9rocess
S Ma|ntenance
Prototyping Prototyping
Ident|fy 8as|c User
kequ|rements
kap|d|y Deve|op
rototype
Lnab|e Users to Work
w|th the rototype
Cbta|n User
Ieedback
"1hrowowoy" Prototypinq
erform further System
Deve|opment w|th a L|feCyc|e
8ased Methodo|ogy
(and d|scard the prototype)
"vo/utionory v/opmnt
Comp|ete and Document the
I|na| rototype and I|e|d It as
the Cperat|ona| System
Iterat|ve
Lnhancement
of the
rototype
Mod|fy the
rototype
SofLware 9roLoLyplng(Dse Lhls ulg)
SCl1WA8L 98C1C1?9lnC
W l 9urpose of appllcaLlon proLoLyplng
9roLoLype refers Lo a worklng model of an lnformaLlon
sysLem
uoes noL conLaln all Lhe feaLures or perform all of Lhe
funcLlons of Lhe flnal sysLem
lL lncludes only a sufflclenL number of elemenLs Lo
enable Lhe users Lo deLermlne whaL Lhey llke and whaL
Lhey do noL llke
9ermlLs Lhe user Lo be able Lo ldenLlfy feaLures LhaL
should be added or changed or deleLed
Maln characLerlsLlcs
W 1he proLoLype ls a llve worklng appllcaLlon
W 1he purpose ls Lo LesL ouL assumpLlons made by
analysLs and users abouL requlred sysLem feaLures
W 9roLoLypes are creaLed qulckly
W 9roLoLypes evolve Lhrough an lLeraLlve process
W 9roLoLypes are relaLlvely lnexpenslve Lo bulld
W A Dses of AppllcaLlon 9roLoLyplng
9rlmary uses
1 an effecLlve devlce for clarlfylng user
requlremenLs
2 Lo verlfy Lhe feaslblllLy of a sysLems deslgn
W an experlmenLal approach Lo evaluaLe user reacLlon
and response
W an analysls of menu or speclal keys or keywords or
bar code eLc
W 8 Why 9roLoLype?
1 Dser lnvolvemenL
2 LsLabllsh 8LAL Dser 8equlremenLs
3 SupporL for CrganlzaLlonal Change
Learnlng
W C 8aLlonal for AppllcaLlon 9roLoLyplng
An ouLgrowLh of Lhe need Lo deslgn and
develop lnformaLlon sysLems qulckly
efflclenLly and effecLlvely and Lo galn a
saLlsfled user
1 9roducLlvlLy aspecLs
9roducLlvlLy when applled Lo sysLems analysls means
carrylng ouL acLlvlLles ln Lhe mosL efflclenL manner
galnlng Lhe greaLesL lmpacL wlLh Lhe besL uLlllzaLlon of
resources
W Llme losL Lo lncorrecL developmenL ls mlnlmlzed
W deslgn errors are mlnlmlzed
W Lhe efforLs of analysLs have a hlgh payoff
W Dsers recelve Lhe appllcaLlons Lhey need wanL !
W uevelopmenL work does noL have Lo be redone
8emember 9roducLlvlLy ls lnpuLs/ouLpuLs
W L CandldaLe appllcaLlon (DnsLrucLured
slLuaLlons)
8equlremenLs are unknown
a new appllcaLlon new Lechnology new
people new Lask
very llLLle lnformaLlon ls avallable or known
8equlremenL need evaluaLlon
requlremenL are known effecLs on user are
unknown all of Lhe condlLlons can noL be
deLermlned Lherefore a plloL ls run Lo assess
approach and verlfy meLhods procedures
Lechnology eLc
Plgh cosL resources (human money maLerlals
machlnes) oLher appllcaLlon compeLlng for
same resources
Plgh rlsk CCM9L1l1lvL AuvAn1ACL
W lnaccuraLe assessmenL of slLuaLlon (volaLlle
slLuaLlons or markeL condlLlons) leadlng Lo an
lnaccuraLe evaluaLlon of requlremenLs places
organlzaLlon ln [eopardy
W (Dnknown parameLers) Lhe example ln book could
be LesLed vla slmulaLlon (also very cosLly))
new 1echnology
W a company may noL have experlence wlLh a new
Lechnology le CMC or Lul
8emember Dsers can polnL Lo feaLures Lhey
llke or dlsllke and Lhus lndlcaLe shorLcomlngs ln
an exlsLlng and worklng sysLems more easlly
Lhan Lhey can ldenLlfy Lhem ln a narraLlve or
graphlc descrlpLlon of a promlsed sysLem
W Sen 1able 31 page 220
8 uevelop Worklng Model (con'L)
W SLep 1 ldenLlfy known requlremenLs
W SLep 2 uevelop Worklng model
W SLep 3 Dse 9roLoLype
W SLep 4 8evlew 9roLoLype
W SLep 3 CompleLe?
W SLep 6 ueclslon abandon lmplemenL redevelop
begln new
SofLware 9roLoLyplng
W ll SLeps ln 9roLoLype MeLhod
A ldenLlfy known 8equlremenLs
W Pow? ConducLlng Lhe lnvesLlgaLlon
W 8evlewlng organlzaLlonal documenLs
W ConducLlng lnLervlews
W CbservaLlons
W CuesLlonnalres
W uo Lhe work
W LxperlmenL
W 9lanL slLe vlslLs
A ldenLlfy known 8equlremenLs (con'L)
W vendor demonsLraLlons
W Semlnar
W Conferences
W Workshops
W llLeraLure Lrade/academlc
W 9ersonal conLacLs
W kL? Learn DndersLand LlsLen lnLegraLe
Also
W deLermlne purpose
W scope of lLs capablllLles
8 uevelop Worklng Model
W SLep 0 SysLems analysLs descrlbes proLoLype
meLhod Lo users
whaL acLlvlLles ln whaL sequence
responslblllLles of Leam members (user analysLs manger
eLc)
presenL a general plan so everybody knows whaL Lo
expecL 1hls can be a pro[ecL plan uslng pro[ecL
managemenL Lechnlques (1lmeLlne 9ro[ecL Work 8ench
MlcrosofL 9ro[ecL Mgr eLc)
Llme Lable for sLarLup
[olnLly speclfy Lhe daLa requlred
lndlvldual reporLs and documenLs
a layouL of each
an esLlmaLe of cosLs
W ComponenLs of proLoLype
lnLerface beLween user and sysLem
command language dlalogue
conversaLlon
lnpuL screens formaL
LssenLlal processlng modules
sysLem ouLpuL
C Dser 9roLoLype
W l1 lS 1PL DSL8S 8LS9CnSl8lLl1? 1C WC8k Wl1P
1PL 98C1C1?9L Anu LvALDA1L l1S lLA1D8LS Anu
C9L8A1lCn
W Lxperlence wlLh Lhe sysLem ls requlred ln order Lo
develop and lmplemenL an effecLlve saLlsfylng and
efflclenL lnformaLlon sysLem
W Cnly Lhe user can deLermlne whaL changes are
needed whaL enhancemenLs are requlred now or
laLer whaL feaLures are lnadequaLe or undeslrable
eLc
W CLher lnformaLlon
CrganlzaLlonal daLa sLandards are Lo be followed
(AnalysLs)
Maklng l/C lnLerface feaLures represenLaLlve of Lhose ln
Lhe producLlon sysLem ls lmporLanL
As of 19841989 documenLaLlon or speclflcaLlons are
done aL Lhls Llme 1992 mosL orgs are dolng Lhese Lhlngs
ln parallel
LffecLlveness ls more lmporLanL Lhan efflclency
SaLlsfacLlon ls more lmporLanL Lhan effecLlveness
u 8evlew proLoLype
W uurlng evaluaLlon
W CollecL daLa
W 1he Leam should have dally weekly meeLlngs Lo
dlscuss sysLem problems dlrecLlon eLc
User AnaIysts
Problems Operational Statistics
Number of Sessions hours of
use, system down time
Likes Number of erros made
Dislikes Number of incorrect ?
New approaches Use, control, censensus,
attitude
New insights
L 8epeaL as needed
W 1he sysLems evolves ln an cycllc lLeraLlve manner
W 1he process ends when Lhe Leam agree LhaL Lhe
sysLem has evolved Lo lnclude Lhe necessary feaLure
or when lL ls evldenL LhaL Lhere ls no beneflL for
addlLlonal lLeraLlons
W lll Dse of 9roLoLypes
A Abandon AppllcaLlon
W uoes noL mean LhaL Lhe proLoLype process was a
mlsLake
W 8aLher Lhe lnformaLlon and experlence galned by
developlng and uslng Lhe proLoLype led Lo a
declslon
A Abandon AppllcaLlon (con'L)
W 8oLh Lhe analysLs and user have learned from Lhe
opporLunlLy
an alLernaLlve was dlscovered
Lhe approach was lnapproprlaLe
remember Lhe proLoLype saved Llme resource was used
under condlLlons of unsLrucLured declslon maklng or
problem solvlng (Coory ScoLLMorLon 1971)
8 lmplemenL 9roLoLype
W 1he proLoLype can become Lhe acLual sysLem
W Lhe proLoLype evolved Lo a compleLe appllcaLlon
conslsLlng of all Lhe feaLures capablllLles and
performance characLerlsLlcs
W Lhe appllcaLlon wlll be used only lnfrequenLly and
any speed or efflclency of operaLlon ls noL essenLlal
W 1he appllcaLlon does noL affecL or lnLeracL wlLh
oLher appllcaLlons or daLa ln Lhe organlzaLlon and
meeLs Lhe needs of lLs lmmedlaLe users
8 lmplemenL 9roLoLype (con'L)
W 1he proLoLype wlll do unLll
Lhe organlzaLlon needs change
prlorlLles change
W 1he currenL envlronmenLal condlLlons are
uncerLaln so
C 8edevelop AppllcaLlon
W 1he lnformaLlon collecLed durlng Lhe proLoLype can
be used Lo develop Lhe full appllcaLlon
more lnformed declslon can be made
Lhe requlred feaLured become known
Lhe user lnLerface becomes deflned
a close approxlmaLlon Lo Lhe Dser menLal model
durlng Lhe redevelopmenL process a greaLer emphasls ls
has been placed on Lhe use of sysLem resources
efflclency daLa sLorage Why? SaLlsfacLlon and
effecLlveness aspecLs have been fulfllled
C 8edevelop AppllcaLlon (con'L)
ln redeveloplng Lhe proLoLype lL can be maln sLreamed
lnLo Lhe SysLems uevelopmenL Llfe Cycle MeLhod
9rellmlnary lnvesLlgaLlon
ueLermlnaLlon of sysLem requlremenLs
ueslgn of sysLem
uevelopmenL of sofLware
SysLem LesLlng
lmplemenLaLlon evaluaLlon
W 1he proLoLype can be used as an alLernaLlve Lo Lhe
requlremenLs phase or deslgn phase
u 8egln new 9roLoLype
W A new approach ls someLlmes suggesLed leaLures
LhaL are enLlrely dlfferenL can be revealed
W noLe lf an analysLs can noL undersLand a users
general requlremenLs a proLoLype wlll noL help
1he Leam musL have some common frame of
reference from whlch Lo begln 1hls ls Lhe
lmporLance of Lhe ln1LLLlCLnCL 9PASLS
lnvesLlgaLlon deLermlnaLlon of sysLem
requlremenLs
W vl MlsconcepLlons abouL 9roLoLyplng
Many beneflLs buL noL used very much
used more on small sysLems or slmple
appllcaLlons
Lhe key ls user lnvolvemenL
Lhe appllcaLlon slze ls noL lmporLanL
proLoLyplng can work well for all slzes
W vll Summary
9roLoLyplng lnvolves Lhe creaLlon of a worklng
model
lL may only conLaln a small number of feaLures
lnvolves Lhe users
ls an lLeraLlve process
can be lncremenLal
W vll Summary (con'L)
can become Lhe full sysLem
used when Lhe requlremenLs can noL be
deLermlned
used when Lhe Leam wanLs Lhe user dlrecLly
lnvolved
used Lo speed up Lhe process
W vlll !olnL AppllcaLlon uevelopmenL
1eam approach
W operaLlonallze user lnvolvemenL
W operaLlonallze user parLlclpaLlon
W focus on faclllLaLed lnLeracLlons beLween users and deslgners
W group dynamlc Lechnlques are used
compleLe deslgn fasL
W acceleraLe Lhe deslgn of lS
W promoLe comprehenslveness
W hlgh quallLy resulLs
!Au
!Au orlglns
W l8M laLe 1970s
W has flourlshed ouLslde of Lhe academlc communlLy
(llke Case)
!Au
!Au 1echnlques
W laclllLaLlon
W Agenda seLLlngs/sLrucLure
W uocumenLaLlon
W Croup uynamlcs
W 8ralnsLormlng
W alrlng facLs
W rules of order
!Au
MeLhodology
W Dsers 9eople who wlll user or are effecLed by Lhe
sysLem
W LxecuLlve Sponsor
W laclllLaLor/MeeLlng Leader
W Scrlbe (Popefully uses elecLronlc equlpmenL)
W lS 9ro[ecL Leam
!Au
1he CeneraLlons of !Au
lrom Carnel LL Al (1993) CACM 36(4) 4048
%he Spiral Life Cycle Model
Sp|ra| Mode| Descr|pt|on
1he developmenL splral conslsLs of four quadranLs
CuadranL 1 ueLermlne ob[ecLlves alLernaLlves and consLralnLs
CuadranL 2 LvaluaLe alLernaLlves ldenLlfy resolve rlsks
CuadranL 3 uevelop verlfy nexLlevel producL
CuadranL 4 9lan nexL phases
CuadranL 1 ueLermlne ob[ecLlves alLernaLlves and
consLralnLs
ob[ecLlvesnamely performance funcLlonallLy and ablllLy Lo
accommodaLe change
lmplemenLaLlon alLernaLlvesnamely deslgn reuse procure
and procure/ modlfy
consLralnLs lmposed on Lhe alLernaLlvesnamely Lechnology
cosL schedule supporL and rlsk
CuadranL 2 LvaluaLe AlLernaLlves ldenLlfy 8esolve 8lsks
1he focus here ls on rlsk mlLlgaLlon
proLoLyplng slmulaLlon benchmarklng reference checklng
admlnlsLerlng user
quesLlonnalres analyLlc modellng or comblnaLlons of Lhese
and oLher rlsk resoluLlon Lechnlques
":adrant 3: DeveIop, Verify, Next-LeveI Prod:.t ":adrant 3: DeveIop, Verify, Next-LeveI Prod:.t
":adrant 3: DeveIop, Verify, Next-LeveI Prod:.t
8aslc waLerfall" approach may be employedmeanlng
concepL of operaLlons deslgn developmenL lnLegraLlon
and LesL of Lhe nexL sysLem or producL lLeraLlon lf
approprlaLe lncremenLal developmenL approaches may
also be appllcable
uadrant 4 |an Next hases
1echnlcal revlew LhaL assesses Lhe sLaLus progress
maLurlLy merlLs rlsk of developmenL efforLs Lo daLe
resolves crlLlcal operaLlonal and/or Lechnlcal lssues
(CCls/C1ls)
lmplemenLaLlon of lnformaLlon
SysLems
W C WhaL ls successful lmplemenLaLlon?
1 Plgh level of Dse LlllClLnC? DSA8lLl1?
W number of LransacLlons per unlL Llme
W 8esponse Llme
W ConnecL Llme less ldle Llme
W eLc
2 ApproprlaLe naLure of Dse (lnLended Dse)
DSA8lLl1?
W used as deslgned
W eLc (need More Lxamples)
SysLems
W C WhaL ls successful lmplemenLaLlon?
(con'L)
3 Plgh Level of Dser SaLlsfacLlon
SA1lSlAC1lCn
4 AccompllshmenL of ob[ecLlve
LllLC1lvLnLSS
3 lndlcaLlon of lnsLlLuLlonallzaLlon of SysLem
LllLC1lvLnLSS SA1lSlAC1lCn
SysLems
W u lacLors ln Successful lmplemenLaLlon
8easons for fallures
W 1 pollLlcal opposlLlon
W 2 resources dlverLed
W 3 developmenL cosL exceed esLlmaLe
W 4 developmenL Llme exceed esLlmaLe
W 3 lnLended use lgnored
W 6 process deslgned lncorrecLly
W 7 capaclLy noL deslgned correcLly
W 8 lnlLlal deslgn Leam reasslgned
W 9
SysLems
lacLors for Success/lallure
W 1 proper lmplemenLaLlon plannlng
W 2 enacLmenL of organlzaLlon
W 3 CrganlzaLlonal culLure
W 4 SLakeholder lnvolvemenL
SysLems
W llgure 1811 page 748
lmplemenLaLlon of lS
SysLem CuallLy (con'L)
W 9oor uaLa quallLy
no rellablllLy
poor accuracy
daLa noL Llmely
daLa unavallable
W 9oor quallLy of lnformaLlon
lnaccuraLe daLa
lrrelevanL lnformaLlon
lnformaLlon overload
lmplemenLaLlon of lS
SysLem CuallLy (con'L)
W CosL over runs
W CperaLlonal problems
response Llme
down Llme
crashes
repalr Llme
W DsablllLy
W luncLlonallLy
8apld AppllcaLlon uevelopmenL
W 1rendy Lerm for many of Lhese alLernaLlve
meLhods used ls some comblnaLlon
CASL
!Au
9roLoLyplng
1lme 8oxlng
1he 8Au Model
Business
Modeling
Data
Modeling
Process
Modeling
Application
Generation
Testing &
Turnover
Business
Modeling
Data
Modeling
Process
Modeling
Application
Generation
Testing &
Turnover
60 90 days
8Au Model
W 8uslness Modellng
WhaL lnfo urlves Lhe buslness process?
WhaL lnfo ls generaLed?
Who generaLes lL?
Where does Lhe lnfo go?
Who processes lL? LLc
W uaLa Modellng
8eflnemenL from buslness model lnLo daLa ob[ecLs
CharacLerlsLlcs of ob[ecL ldenLlfled and
relaLlonshlps beLween ob[ecLs are deflned
8Au Model
W 9rocess Modellng
uaLa ob[ecLs are Lransformed Lo achleve Lhe lnfo
flow
9rocess desc added for addlng modlfylng
deleLlng or reLrlevlng a daLa ob[ecL
W AppllcaLlon CeneraLlon
Dse of 4CL Lechnlques
AuLomaLed Lools use for consLrucLlon of S/W
W 1esLlng 1urnover
1esLlng Llme ls less bcoz of reusable componenLs
Cnly new componenLs LesLed and lnLerfaces
LlmlLaLlons of 8Au
W More human resources requlred Lo creaLed
rlghL Leams
W 1lme cruclallf commlLmenL lack8Au falls
W Modular sysLems lmplemenLable noL
approprlaLe for hlgh performance sysLems
whlch requlre rlgorous Lunlng of lnLerfaces
W noL approprlaLe where Lechnlcal rlsks are hlgh
le appllcaLlons maklng heavy use of new
Lech or new S/W requlre hlgh degree of
lnLeroperablllLy wlLh exlsLlng sysLems
Dec|s|on1ree
Steps in the Systems
Development Process
aintenan.e
1he Llnear Model
ana|ys|s
des|gn code test
8ystem||nformat|on
eng|neer|ng
Advantages of Waterfa|| L|fe Cyc|e
Mode|s
W Lasy Lo explaln Lo Lhe user
W SLages and acLlvlLles are well deflned
W Pelps Lo plan and schedule Lhe pro[ecL
W verlflcaLlon aL each sLage ensures early
deLecLlon of errors / mlsundersLandlng
LlmlLaLlons of Lhe WaLerfall Llfe Cycle
Model
W 8uL for absoluLely new sysLem deLermlnlng
Lhe requlremenLs ls dlfflculL
W A large pro[ecL mlghL Lake a few years Lo
compleLe sofLware wlll employ a hardware
Lechnology LhaL ls on Lhe verge of becomlng
obsoleLe
lLeraLlve Models
||sler
lo
cuslorer
ou||d/rev|se
roc|-up
cuslorer
lesl-dr|ves
roc|-up
-:s|ness
mode||ng
data
mode||ng
process
mode||ng
app||cat|on
generat|on
test|ng
&
t:rnover
-:s|ness
mode||ng
dat a
mode||ng
process
mode||ng
app|| cat |on
generat | on
test|ng
&
t:rnover
- :s|n ess
m ode | |n g
d at a
m od e| |n g
p r ocess
m od e| | ng
ap p| | cat| on
gen er at| on
test| ng
&
t: rn o ver
team #1
team #2
team #3
0 - 90 days
9roLoLyplng
8Au
$ystems Development LiIe Cycle
$ystems Development LiIe Cycle
Why do we need Life-Cycle-based Development?
Large systems take large amounts of time, resources, and can be seen by all: %hus they require CON%#OL
One way of reducing complexity (very unstructured) is to "break" the problem into smaller "less" complex sub-systems
v
Why do we need Life-Cycle-based Development?
Large systems take large amounts of time, resources, and can be seen by all: %hus they require CON%#OL
One way of reducing complexity (very unstructured) is to "break" the problem into smaller "less" complex sub-systems
v
easibiIity
St:dy
Tasks Tasks
Systems
AnaIysis
Systems
Design
Programming
(Constr:.tion)
InstaIIation
(System
Operation
and
aintenan.e)
Req:irements
AnaIysis
Logi.aI
Design
Physi.aI
Design
Coding and
Testing
Conversion
PostimpIemen-
tation Review
Re.ommendation to Pro.eed and
System ProposaI or
Re.ommendation to Abandon
Development Stages Development Stages Deliverables Deliverables
Req:irements Spe.ifi.ations
Con.ept:aI Design
or Programs and Databases
DetaiIed Design of System
od:Ies and Databases
Spe.ifi.ation of System
Hardware and Software
A..epted System with
CompIete Do.:mentation
InstaIIed OperationaI System
Re.om. for Enhan.ement of the
System and of the Dev. ethod
Re.om. for Org. Adj:stment
1he lncremenLal Model
ana|ys|s des|gn code test
8ystem||nformat| on
eng|neer|ng
ana|ys|s des|gn code t est
|ncrement 2
|ncrement 3
|ncrement 4
|ncrement 1
de||very of
1st |ncrement
de||very of
2nd |ncrement
de||very of
3rd |ncrement
de||very of
4th |ncrement
ca|endar t|me
An LvoluLlonary (Splral) Model
Customer
Communication
Planning
Construction & #elease
Customer
Evaluation
Engineering
#isk nalysis
9roLoLyplng sofLware uevelopmenL
model
W Lhe cllenL can geL an acLual feel of Lhe
sysLem
W bullLlLLwlce approach
W sysLem wlLh overall funcLlonallLy
8equlremenLs CaLherlng
acilitated pplication Specification %echniques acilitated pplication Specification %echniques
SofLware SofLware
Lnglneerlng Lnglneerlng
Croup Croup
CusLomer CusLomer
Croup Croup
S?S1LMS AnAL?SlS uLSlCn
!$
SYS%EMS NLYSS
ueLermlnlng 8equlremenLs
SuLC 9hases
9hase 2 SysLems Analysls
Cb[ecLlves
Learn how Lhe currenL sysLem works
ueLermlne and documenL fully how Lhe sysLem
could work beLLer
uevelop a loglcal model of Lhe new sysLem
Make recommendaLlons Lo managemenL
ChapLer
ueLermlnlng 8equlremenLs
Cb[ecLlves
W Lxplaln how sysLems analysls relaLes Lo
buslness needs problems and opporLunlLles
W LlsL and descrlbe Lhe Lypes of sysLem
requlremenLs LhaL musL be ldenLlfled durlng
sysLems analysls
W uescrlbe how Lo conducL a successful
lnLervlew
Cb[ecLlves
W Lxplaln when and how Lo use facLflndlng
Lechnlques lncludlng lnLervlews
documenLaLlon revlew observaLlon
quesLlonnalres sampllng and research
W SeL up effecLlve documenLaLlon meLhods Lo
use durlng sysLems developmenL
W Cvervlew of sysLems analysls phase
W lacLflndlng Lechnlques
lnLervlewlng
uocumenLaLlon revlew
CbservaLlon
CuesLlonnalres
Sampllng
8esearch
W MeLhods used Lo record resulLs
lnLroducLlon
Cvervlew of Lhe SysLems Analysls
9hase
W SysLems analysls phase Lasks
CaLher and record facLs abouL Lhe currenL sysLem
and whaL ls requlred Lo supporL buslness needs
W 1hreesLep approach Lo declslonmaklng
ueLermlne Lhe facLs
Analyze Lhe facLs
Make a declslon
W 1wo sLeps ln Lhe sysLems analysls phase
8equlremenLs deLermlnaLlon (facLflndlng)
8equlremenLs analysls
Package
Cllck Lo see llgure 31
1he Challenge of SysLems Analysls
W Large sysLems are especlally challenglng
W 8uslness sysLems musL change rapldly
W SysLems analysLs use varlous skllls
8everse englneerlng
CrlLlcalLhlnklng skllls
lnLerpersonal skllls
W 8equlremenLs deLermlnaLlon quesLlons
Who does lL?
WhaL ls done?
Where ls lL done?
When ls lL done
Pow ls lL done
W AnoLher lmporLanL quesLlon
Why?
Package
W 8equlremenLs analysls quesLlons
Who should do lL?
WhaL should be done?
Where should lL be done?
When should lL be done?
Pow should lL be done?
lnLervlews
W ueLermlne Lhe people Lo lnLervlew
W LsLabllsh ob[ecLlves for Lhe lnLervlew
W 9repare for Lhe lnLervlew
W ConducL Lhe lnLervlew
W uocumenL Lhe lnLervlew
W LvaluaLe Lhe lnLervlew
W Dnsuccessful lnLervlews
lnLervlews
W ueLermlne Lhe people Lo lnLervlew
SelecL Lhe rlghL people
Conslder lnformal sLrucLures
Package
lnLervlews
W LsLabllsh ob[ecLlves for Lhe lnLervlew
ueLermlne Lhe areas Lo be dlscussed
LlsL Lhe facLs you wanL Lo gaLher
SollclL ldeas suggesLlons and oplnlons
keep quesLlons conslsLenL
lnLervlews
Schedule a speclflc day and Llme
9lace a remlnder call
Send a memo Lo managers
Package
lnLervlews
Schedule a speclflc day and Llme
9lace a remlnder call
Send a memo Lo managers
CreaLe a llsL of quesLlons
Dse a varleLy of quesLlons
W Cpenended quesLlons
W Closedended quesLlons
W 8ange of responses quesLlons
Send conflrmaLlon memo Lo lnLervlewee
Package
lnLervlews
W ConducL Lhe lnLervlew
lnLroduce yourself
uescrlbe Lhe pro[ecL
Lxplaln your ob[ecLlves
Ask quesLlons ln order
Summarlze Lhe maln polnLs
Lxplaln Lhe nexL course of acLlon
LlsLen carefully pracLlce engaged llsLenlng
18AuLCll
W WhaL ls Lhe besL locaLlon for Lhe lnLervlew?
lnLervlewee's offlce
W Makes Lhe lnLervlewee more comforLable
W Lasler access Lo supporLlng maLerlal
neuLral locaLlon
W lewer lnLerrupLlons
W Advlse lnLervlewee Lo brlng necessary lLems
A kL? CDLS1lCn
W uoes organlzaLlon level affecL lnLervlews?
W AL lasL9ak !esse Lvans runs lnLo a problem
W Calls and vlslLors cause many lnLerrupLlons
W lnLervlew process ls Llmeconsumlng
W Manager unwllllng Lo reschedule meeLlng
W WhaL should !esse do ln Lhls slLuaLlon?
lnLervlews
W uocumenL Lhe lnLervlew
keep noLeLaklng Lo a mlnlmum
8ecord Lhe lnformaLlon qulckly
Allow Llme beLween lnLervlews
1hank Lhe lnLervlewee wlLh a memo
W noLe Lhe daLe Llme locaLlon and purpose
W 8evlew Lhe maln polnLs dlscussed
lnLervlews
W LvaluaLe Lhe lnLervlew
ldenLlfy posslble blases
ueLermlne wheLher lnLervlewees have necessary
experlence
18AuLCll
W 1ape recorders pros and cons
Can be an effecLlve Lool
lf people feel LhreaLened
W ulscuss ln advance
W 8eassure Lhe lnLervlewee
W 1urn off Lape when lndlcaLed
MusL use Lhls Lechnlque carefully
?ou mlghL rely Loo much on Lhe recorder
LxLra Llme needed Lo llsLen Lo Laped maLerlal
A kL? CDLS1lCn
W Should an analysL lnLervlew several people aL
Lhe same Llme?
W !esse's problem ln Lhe lasL9ak lnLervlew
Cne person domlnaLed Lhe conversaLlon
MeeLlng wlLh Lwo lnLervlewees creaLed a
problem noL an opporLunlLy
W WhaL should !esse have done?
lnLervlews
W Dnsuccessful lnLervlews
noL all lnLervlews are successful
llnd a way Lo conclude an unsuccessful meeLlng
Conslder alLernaLlves
CLher lacLllndlng 1echnlques
W uocumenL revlew
W CbservaLlon
W CuesLlonnalres
W Sampllng work and work producLs
W Craphlcs
W 8esearch
W uocumenL revlew
8evlew exlsLlng sysLem documenLaLlon
CbLaln coples of acLual forms and documenLs
8evlew blank coples of forms
8evlew samples of compleLed forms
8evlew sofLware documenLaLlon
W CbservaLlon
Ask quesLlons abouL presenL sysLem operaLlon
Cbserve all sLeps ln Lhe processlng cycle
Lxamlne each form record and reporL
Conslder each person worklng wlLh Lhe sysLem
1alk Lo people who recelve currenL reporLs
Conslder Lhe PawLhorne LffecL
Package
W CuesLlonnalres
8rlef and userfrlendly
Clear lnsLrucLlons
CuesLlons ln loglcal order
Slmple wordlng Lo avold mlsundersLandlng
Avold leadlng quesLlons
Cpenendlng quesLlons are dlfflculL Lo LabulaLe
LlmlL quesLlons ralslng concern/negaLlve lssues
SecLlon for general commenLs
1esL Lhe quesLlonnalre ln advance
Package
W Sampllng work and work producLs
CollecL examples of acLual documenLs
Sampllng Lechnlques
W SysLemaLlc sample
W SLraLlfled sample
W 8andom sample
W Craphlcs
ulsplay facLflndlng resulLs graphlcally
Craphlcal formaL can hlghllghL quallLy conLrol
problems/causes
PlsLogram ls common Lool Lo dlsplay
quesLlonnalre or sampllng resulLs
Package
Package
W 8esearch
!ournals perlodlcals books
lnLerneL slLes
W Pardware and sofLware vendors
W lndependenL flrms LhaL provlde lnformaLlon
W newsgroups
9rofesslonal meeLlngs semlnars dlscusslons
SlLe vlslLs Lo observe a sysLem ln use
Package
Cllck Lo see llgure 310b
Package
Cllck Lo see llgure 310a
18AuLCll
W lnLervlews
Work besL wlLh small number of people
More personal and famlllar Lhan quesLlonnalres
9eople Lalk more freely ln person
lnLervlewers can reacL lmmedlaLely
9arLlclpaLlon can be a human relaLlons plus
CosLly and Llmeconsumlng
18AuLCll
W CuesLlonnalres
Work besL wlLh large groups
Many people have opporLunlLy for lnpuL
More convenlenL for reclplenLs
Anonymous responses mlghL be more candld
CuesLlons musL be deslgned carefully
Some reclplenLs vlew quesLlonnalres as lnLruslve
Llmeconsumlng and lmpersonal
A kL? CDLS1lCn
W ConducL lnLervlews or send quesLlonnalres?
W CybersLuff background
Several Lhousand sales LransacLlons per week
1hreeshlfL operaLlon
30 fullLlme and 123 parLLlme employees
W Ann's ob[ecLlve lnformaLlon Lo analyze and
resolve recenL bllllng complalnL problems
W WhaL are pros and cons of each Lechnlque?
W WhaL ls Lhe besL way Lo selecL parLlclpanLs?
8ecordlng Lhe lacLs
W 1he need for recordlng Lhe facLs
keeplng accuraLe records ls essenLlal
8aslc rule te t Jo
Culdellnes for good documenLaLlon
W 8ecord lnformaLlon as soon as posslble
W Dse Lhe slmplesL recordlng meLhod
W Lnsure LhaL your work ls undersLandable
W Crganlze your documenLaLlon maLerlal
Conslder a narraLlve llsL wlLh slmple sLaLemenLs
8ecordlng Lhe lacLs
W SofLware Lools
Word processlng
SpreadsheeLs
uaLabase
9resenLaLlon graphlcs
9ersonal or deskLop lnformaLlon managers
CLher SysLems uevelopmenL
1echnlques
W lnLroducLlon
SLrucLured analysls and deslgn ls Lhe mosL
common meLhod
CLher Lechnlques are avallable
W !olnL appllcaLlon developmenL (!Au)
W 8apld appllcaLlon developmenL (8Au)
W Cb[ecLorlenLed (CC) sysLems developmenL
1echnlques
W !olnL appllcaLlon developmenL (!Au)
1ask force of users managers and lS sLaff
Cb[ecLlves
W CaLher lnformaLlon
W ulscuss buslness needs
W ueflne Lhe new sysLem requlremenLs
MeLhods
W 1eam usually meeLs aL speclflc locaLlon
W 1eam has pro[ecL leader and recorder(s)
W key users parLlclpaLe ln lnLense developmenL efforL
!Au can be cosLly buL hlghly effecLlve
Package
1echnlques
W 8apld appllcaLlon developmenL (8Au)
1eam meLhod slmllar Lo !Au buL goes furLher
8Au phases resemble a mlnlSuLC
W 8equlremenLs plannlng user deslgn consLrucLlon and
cuLover
8Au lnvolves a conLlnuous deslgn process
W 1eam can reacL qulckly
W llnal ob[ecLlve ls a funcLlonlng sysLem
8Au can be fasLer and less cosLly buL sLresses
sysLem mechanlcs raLher Lhan sLraLeglc needs
1echnlques
W Cb[ecLorlenLed (CC) sysLems developmenL
Cb[ecLbased model
Cb[ecLs and Lhelr aLLrlbuLes are absLracL enLlLles
Classes and subclasses
9revlew of 8equlremenLs Analysls
9hase
W 8equlremenLs analysls ls Lhe second ma[or
sLage of Lhe sysLems analysls phase
W 8equlremenLs analysls ob[ecLlves
uevelop a loglcal deslgn of Lhe sysLem
CreaLe a sysLem requlremenLs documenL
uellver a formal presenLaLlon Lo managemenL
SCl1WLA8 LlMl1Lu
W SWL has compleLed a prellmlnary lnvesLlgaLlon
W Several problems were revealed
lnpuL errors
CverLlme Lo correcL errors and produce reporLs
W 1he lS Leam recommended furLher analysls
Mr !eremy approved Lhe recommendaLlon
1he sysLems analysls phase now ls underway
SCl1WLA8 LlMl1Lu
W Puman resources deparLmenL lnLervlew
8evlew of organlzaLlon charLs
Package
Package
SCl1WLA8 LlMl1Lu
lnLervlew wlLh MeredlLh 8lder
W 9reparaLlon
Package
Package
SCl1WLA8 LlMl1Lu
W 9reparaLlon
W lorms
Package
Package
Package
Package
Package
SCl1WLA8 LlMl1Lu
W 9reparaLlon
W lorms
LxplanaLory memo Lo Mlke lelner
ConflrmaLlon memo Lo MeredlLh
lollowup memo Lo MeredlLh afLer lnLervlew
Package
Package
SCl1WLA8 LlMl1Lu
W 9ayroll deparLmenL lnLervlew
lnLervlew wlLh nelson WhlLe lead payroll clerk
8evlew of SWL's SysLems and 9rocedures Manual
Package
SCl1WLA8 LlMl1Lu
W 9ayroll deparLmenL lnLervlew
lnLervlew wlLh nelson WhlLe lead payroll clerk
8evlew of SWL's SysLems and 9rocedures Manual
8evlew of sample payroll deducLlon reglsLers
Package
SCl1WLA8 LlMl1Lu
W 8uslness lnformaLlon servlces lnLervlew
lnLervlew wlLh Llnda ueMarco cusLomer
relaLlons manager for 8lS
new program called CPl9S
ueLermlnaLlon LhaL CPl9S wlll noL handle SWL's
needs
SCl1WLA8 LlMl1Lu
W new plans and developmenLs
Dpcomlng changes aL 8lS presenL problems
no obvlous soluLlon Lo sLock purchase deducLlon
processlng
LlmlLed resulLs expecLed unless Lhe payroll pro[ecL
scope ls expanded
AnnouncemenL LhaL SWL wlll move forward wlLh
new Lmployee Savlngs and lnvesLmenL 9lan (LSl9)
LSl9 LargeL daLe of Aprll 1 1999
SCl1WLA8 LlMl1Lu
W 1he revlsed pro[ecL
Cb[ecLlve Lo deLermlne requlremenLs for Lhe
overall payroll sysLem
Carla Moore Lo work wlLh 8lck Wllllams
ConducL addlLlonal lnLervlews and followup
lnLervlews
8evlew of payroll reporL samples
W 9ayroll 8eglsLer
Package
SCl1WLA8 LlMl1Lu
lnLervlews
W 9ayroll 8eglsLer
W Lmployee CompensaLlon 8ecord
Package
SCl1WLA8 LlMl1Lu
lnLervlews
W 9ayroll 8eglsLer
W Lmployee CompensaLlon 8ecord
W SWL employee paycheck and sLub
Package

SE 29 Nov 2011

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

SE 29 Nov 2011

Cargado por

Copyright:

Formatos disponibles

W SysLems analysls and deslgn Lhe process of

deslgnlng bulldlng and malnLalnlng

SLeps ln Lhe SysLems uevelopmenL

También podría gustarte