C MB Uk T I 10

s MN g ; k mμv iF I
(Application Architecture)

eKalbMN génemeron
eRkaybBa©b ;e meronenH Gñknwg sikSa H
 Planning the Architecture
 Client/Server Architecture and Processing Methods
 Modelling application architecture
 System Management and Support
 System Design Completion

9-1
 enHKWC aCMBUkcug eRkaykñúg cMe N am 3 CMBUkenAkñúg systems design phase eday
eyIg Bic arN aeTAelI application architecture EdleFVIkarbMElg logical model
énRbB½n §Bt’maneTACa physical model. enAeBleyIg begáIt physical model eyIg sikSa
GMBI servers, clients, processing methods, networks nig bBaðaepSgeTotEdlBak;B½n §.
Tis edAcMe BaHcMn uc enHenAkñúg SDLC KWe FVIkarkMn t; application architecture TaMg Rsug
EdlGacRTRTg;tMrUvkarBt’manénCMn Yj .
RbB½n §Bt’maneKGacehAfa application ehIyvaRtUvkar hardware, software,
data, procedures, and people edIm,Ib Me BjsMn uMmux gar)ankMn t;rbs;Rkumh‘un . RbB½n §p þl ;
lT§pll¥ edayRc)ac;s masPaKTaMg enaHbBa©Úl KñaeTACa architecture or design
EdlGacbt;Ebn)an (flexible)/ cMN aymanRbsiT§PaB (cost-effective)/ manlkçN H
bec©keTs (technically sound) nig mansmtßPaBRTRTg;tMrUvkarBt’manénCMn Yj .
Application architecture bMElg logical design énRbB½n §B t’maneTACa physical
structure edayrYmbBa©Úl hardware, software, network support, and processing
methods. End product én systems design phase KWC akarerobcM system design
specification documentation ehIyRbsin ebIe Kyl;RBmcMe BaHÉksarenaH eyIg nwg
dMe N IrkarCMh anbnþe TotKW systems implementation phase.
1. Planning the Architecture
RKb;RbB½n §Bt’manEtgEtBak;B½n §C amYy functions CacMb gcMn Yn 3 KW viFIe RbIR)as;
nig rkSaTukTin ñn ½y (data storage and access methods)/ application programs
edaHRsay processing logic nig interface EdlGnuBaØatie GayGñkeRbIR)as;Tak;TgeTAvij
eTAmkCamYyRbB½n §. Functions CacMb gTaMg 3 GacdMe N IrkarenAelI server rW client
GaRs½yeTAelI architecture eRbIR)as;. enAeBlerobEpnkarcMe BaH system design eyIg
RtUvEtkMn t;kEnøg sMrab;e Gay functions TaMg enaHdMe N Irkar RBmTaMg KuN RbeyaCn_
nig KuN vib tþc Me BaHCMe rIs ksagnImYy² ehIyEpñkenHnwg erobrab;BI server and client
characteristics nig faetIC Me rIs ksagnImYy² (each design alternative) edaHRsay
system functions edayrebobN a.

9-2
1. 1. Servers
Server KWC akMuB üÚT½rpÁt;p Ág ;Tin ñn ½y/ processing services
rWkarRTRTg;e pSgeToteTA
kan;kMuBüÚT½rmYy rWe RcIn EdleKeGayeQμaHfa clients. System design Edl server
dMe N Irkarral; processing TaMg Gs;e KehAfa mainframe architecture ehIycMe BaH
server RTRTg;c Mn Yn clients CaeRcIn enATIkEnøg epSg²Kña eKehAfa centralized system.
eTaHbIC a server BitR)akdmin caM)ac;C a mainframe k¾e day k¾Bakü mainframe
architecture nig centralized system CaTUe TABiB N ’n aGMB ImCÆdæa nGñkeRbIR)as;C aeRcIn
(multi-user environment) Edl server eRcIn Etmanel,ÓndMe N Irkarx<s ;C ag clients.
GñkviPaKRbB½n §KYrEtdwg BIRbvtþ mainframe architecture edIm,Iyl;BItYn aTIrbs; server
enAkñúg modern system design.
Background
Mainframe architecture ekIteLIg kñúg kMLúg qñaM 1960 ehIyvaKWC a system
design EtmYyKt;n aeBlenaH. EfmBIe lI centralized data processing RbB½n §kalBImun
dMe N Irkarral; data input and output enAÉTItaMg kN þalmYyEdlCaerOy²eKeGayeQμaH
fa data processing center. Physical data RtUvbBa¢Ún kñúg TMrg;C aeRcIn eTAkan; data
processing center EdlCaTIkEnøg sMrab;b Ba©Úl vaeTAkan;RbB½n §. GñkeRbIR)as;e nAkñúg
Rkumh‘un KμansmtßPaBGacbBa©Úl nig emIl output eT elIkElgEt printed reports
Etb:ue N ÑaH.
Server-based Processing
Network technology ecHEtrIklUtlas;e TAmux nig Gacrkluyéllk)an.
Rkumh‘un CaeRcIn cab;e pþImtMe LIg terminals enATItaMg q¶ay² dUe cñHGñkeRbIR)as;GacbBa©Úl
nig eRbIR)as;Tin ñn ½yBITIkEnøg N ak¾)anenAkñúg Rkumh‘un edaymin xVl ;f a centralized
computer sßitenATIkEnøg N aeT.
cMe BaH centralized design karvay rWc uc tYGkSrelI keyboard enAÉTItaMg q¶ayRtUv
bBa¢Ún eTAkan; mainframe EdlCakEnøg dMe N IrkarsMe N IrenaH nig eqøIbtbeTAvij tamryH
bBa¢Ún screen output Rtlb;e TAkan; screen terminal rbs;GñkeRbIR)as;vij .
KuN RbeyaCn_C acMb gcMe BaH server-based processing KWf aeyIg GacP¢ab; terminals
CaeRcIn RbePTeGayTak;TgCamYy mainframe nig karksagenHmin kMn t;e TAelI hardware
platform Cak;l ak;N amYyeT. KuN vib tþc Me BaH server-based processing vij KWf a

9-3
GñkeRbIR)as;C aTUe TAeRbIR)as; character-based terminals. ral; data storage, access,
and application programs sßitenAelI mainframe cMe BaH server-based system.
sBVéf¶e nHeKenAeRbI mainframe architecture cMe BaHRkumh‘un N aEdlRtUvkar
large amount of data processing EdlGacdMe N IkarCaRkumenATItaMg kN þa l.
]TahrN _³ credit card company EdldMe N Irkar monthly statement CaRkum
rWk¾FnaKarEdleRbIR)as; mainframe server edIm,IEkERb customer balances erogral;
yb;.
Terminal technology mankarEkERbKYrP£a k;e p¥Il ya:g xøa Mg enAeBlEdl server
technology manPaBrIkcMe rIn ]TahrN _³ Rkumh‘un GaceRbIR)as; mix of PCs nig ]bkrN _
Bie ssd¾éTepSgeTot EdlGnuBaØatie GayGñkeRbIR)as;GacTak;TgeTAvij eTAmkCamYy
centralized server. enAkñúg Rkumh‘un PaKeRcIn workstations eRbIR)as; powerful GUIs
CMn Ys eGay character-based terminals.
1. 2. Clients
enAeBl PC technology ekItmanenAkñúg kMLúg Bak;kN þalqñaM 1980 ehIyman
skþanuBlya:g xøaMg min yUrb:un μanGñkeRbIR)as;yl;e XIj fa BYkeKGacdMe N Irkar word
processing, spreadsheet, and database application edayxøÜn Égedaymin caM) ac;C Mn Yy
BI IT group eTenAkñúg TMrg;mYyeKehAfa stand-alone computing. eRkaymkeTot
Rkumh‘un PaKeRcIn tP¢ab; stand-alone computers cUl KñaCa networks EdlGaceFVIe Gay
clients GacmanlT§PaBpøa s;b þÚr Tin ñn ½yeTAvij eTAmk nig dMe N Ir kar processing enAelI
kMuBüÚT½rpÞal;x øÜn .
Stand-alone Computing
enAeBlGñkeRbIR)as;n ImYy²eFVIkarkñúg TMrg; stand-alone mode enaH wrokstation
dMe N Irkarral; functions of server TaMg Gs;e dayrkSaTuk/ eRbIR)as; nig dMe N IrkarTin ñn ½y
(storing, accessing, and processing data) RBmTaMg pþl ; user interface. eTaHbIC a
PCs begáIn plitPaB nig GnuB aØa tie GayGñkeRbIR)as;d Me N Ikarkic ©karEdlkalBImun RtUvkar
CMn YyBI IT department k¾e day k¾ stand-alone computing min )anpþl ;pll¥

9-4
(inefficient)/ éfø nig bgáe GaymankþIkgVl ;ya:g xøaMg eTAelI data security, integrity, and
consistency.
Local and Wide Area Networks
Rkumh‘un PaKeRcIn edaHRsaybBaðacMe BaH stand-alone computing edaytP¢ab;
clients CaeRcIn bBa©Úl Kña eTACa local area network (LAN) EdlGnuB aØa tiB YkeKEckcay
nig eRbIR)as;Tin ñn ½y RBmTaMg hardware resources dUc rUb xageRkam elIs BIe nHeTot
LANs mYy rWe RcIn tP¢a b;b Ba©Úl Kña nig GacTMn ak;TMn gCamYy centralized server. PaBrIk
cMe rIn xag data communication technology GaceFVIe GaymanlT§PaBbegáIt powerful
networks edayeRbIR)as; satellite link, high-speed fiber-optic lines rW Internet
edIm,IEckcay nig eRbIR)as;Tin ñn ½y.

(rUb 9.1)
cMe BaH wide area network (WAN) GacBRgIkcMg aykan;Etq¶ay nig GaceGay
GñkeRbIR)as;TMn ak;TMn gKñaqøg TVIb . Network )anlak;kM)aMg (transparent) cMe BaH
GñkeRbIR)as;d Me N IrkarTin ñn ½yenAelI LAN or WAN BIe RBaHGñkeRbIR)as;RKan;EteXIj
Tin ñn ½ydUc CavarkSaTukenAelI workstation pÞal;xøÜn BYkeK.

9-5
Client-based Processing
Clients Eckcay nig eRbIR)as;Tin ñn ½yrkSaTukenAelI local server edIm,IRTRTg;
RkumGñkeRbIR)as; rW department enAkñúg LAN TUe TA. enAeBl LAN kan;EtmanRbCaRbiy
LAN configuration CaTUe TAPaKeRcIn KW file server design. LAN client
nImYy²cMe BaH file server design rWe KGacehAfa file sharing architecture
pÞúkc,ab;c Ml g application program b:uEnþmin )anpÞúkTin ñn ½yeT edayTin ñn ½yenaHRtUv
rkSaTukenAelI server. Client esñIs Muc ,ab;c Ml g data file ehIy server eqøIytbvij
edaybBa¢Ún entire file eTAkan; client vij bnÞab;BIkic ©d Me N Irkar processing enAelI
client rYc ehIy client bBa¢Ún data file Rtlb;e TAkan; server vij . File sharing
designs manRbsiT§PaBkñúg krN IEdlcMn Yn networked users tic nig file sizes
RtUvbBa¢Ún manTMh MtUc . File sharing design TamTar network resources CadMukMPYn
BIe RBaHRtUvbBa¢Ún entire data file eTAkan; clients.
2. Client/Server Architecture
eTaHbIC aKμan standard definition ekItmank¾e day k¾Bakü client/server
architecture CaTUe TAsMe dAeTAelIRbB½n §EdlEbgEck processing rvag networked
clients mYy rWe RcIn nig central server. enAkñúg client/server system Fmμta client
dMe N Irkar entire user interface rYmbBa©Úl TaMg data entry, data query, and screen
presentation logic ehIy server rkSaTin ñn ½y nig data access RBmTaMg database
management functions nig cug eRkay application logic RtUvEbgEckkñúg TMrg;
CaeRcIn rvag client nig server. cMe BaHGnþrkmμe nAkñúg client/server system vij KWf a
client bBa¢Ún sMe N IrsMuB t’maneTAkan; server EdlCaTIkEnøg dMe N Ir karskmμPaB nig eqøIy
tbeTAkan; client vij . dUc bgðajenAkñúg rUb xageRkam eyIg eXIj fa data file min )anbBa¢Ún
BI server eTAkan; client eT manEtsMe N Ir nig lT§plRtUv)anbBa¢Ún qøg kat;b N þaj
network. edIm,Ib Me BjsMe N IrbBa¢Ún BI client, server RbEhlCaTak;TgCamYy servers
epSgeTotedIm,Is uM data or processing support b:uEnþ processing enaHlak;kM)aMg BI
client.

9-6
 File Server Design

Client requests data file

Server transmits entire data file

(rUb 9.2)

Client/Server Design

Client submits data

query to server
Server transmits only the
results of the client query

(rUb 9.3)
rUb xageRkambgðajBIPaBxus EbøkKñaCacMb grvag client/server and traditional
mainframe system. Client/server system kalBImun PaKeRcIn min )anbegáItkarsnSM
R)ak;d Uc karrMBwg TukeT BIe RBaHvamanEt standards mYycMn Yn tUc ekItman nig development
cost mantMéléføC agkarsμa nTukCamun . Implementation mantMéléføB Ie RBaH clients
RtUvkar powerful hardware and software edIm,Ie daHRsay sharing processing
tasks.
Rkumh‘un CaeRcIn vin ie yaKeTAelI client/server system edIm,Is Me rc changing
business operation ehIy client/server concept GacbnþB RgIkedayrab;b Ba©Úl clients
and severs enAxageRkARkumh‘un pgEdr. sBVéf¶e nH client/server architecture
køayeTACaTMrg;mYyEdleKeRbIR)as;e lIs lub cMe BaH system design edayeRbIR)as;
Internet protocols and traditional network models.

Characteristics of Client/Server versus Mainframe Systems

Characteristics Client/Server Mainframe
Basic architecture Very flexible Very rigid
Application Flexible High structured
development Fast Slow
Object-Oriented Traditional

9-7
 User environment PC-based Uses terminals
GUI Text interface
Empowers the users Constraints the user
Improves productivity Limited options
Security and control Decentralized Centralized
features Difficult to control Easier to control
Processing options Can be shared and Can not be modified
configured in any form
desired
Data storage options Can be distributed to place All data is stored centrally
data closer to users
Hardware/software Very flexible Very rigid
integration Multivendor model Single proprietary vendor
(rUb 9.4)

2. 1. Types of Clients: Fat and Thin

Client/server design manmUl dæa neTAelI fat or thin clients. Fat client
design eKk¾e hAfa thick client design pÞúk application processing logic PaKeRcIn
rWTaMg Gs;e nAelI client rIÉ thin client design vij pÞúk application processing logic
PaKeRcIn rITaMg Gs;e nAelI server. etIkarksagnImYy²manKuN RbeyaCn_ nig KuN vib tþ
GVIx øH? IT expert PaKeRcIn yl;Rsbfa thin client design pþl ;e l,ÓndMe N Irkarkan;Et
RbesIreLIg (better performance) BIe RBaH program code sßitenAelI server
enACitTin ñn ½y pÞúyeTAvij fat client dMe N Irkar processing eRcIn Cag RBmTaMg RtUvEtEkERb
nig eRbIR)as;Tin ñn ½yCaerOy². Fat client EtgEtcMN ayeRcIn CageRBaHEt initial
hardware and software requirements nig cMN aykMB ug ekItmaneLIg edIm,IRTRTg;
RBmTaMg EkERb remote client computers. eTaHbIC aya:g N ak¾e day k¾ fat client
design manlkçN HFmμta nig tMélefakCagedIm,IGPivDÆn_ BIe RBaH architecture rbs;va
RsedogeTAnwg file server design.
Characteristics Fat Client Thin Client
Network traffic Higher, because the fat client Lower, because most
must communicate more interaction between code and
often with the server to access data takes place at the server
data and update processing
results
Performance Slower, because more Faster, because less network
network traffic is required traffic is required
Initial cost Higher – more powerful Lower – workstation
hardware is required hardware requirement are not
as stringent

9-8
 Maintenance cost Higher, because more Lower, because most
program code resides on the program code resides on the
client central server
Ease of development Easier, because systems More difficult, because
resemble traditional file- developers must optimize the
server designs where all division of processing logic
processing was performed at
the client
(rUb 9.5)
2. 2. Client/Server Tiers
Client/server designs kalBImun eKehAfa two-tier designs. enAkñúg two-tier
design, user interface dMe N IrkarenAelI client/ ral;Tin ñn ½yTaMg Gs;rkSaTukenAelI
server nig application logic GacdMe N IrkarenAelI server rW client rWGacpÞúkenAelI
server xøHenAelI client xøH .
enAeBlfμIe nHmanTrg;f μImYyeTotelceLIg eKeGayeQμaHfa three-tier design
kMBug EtmanRbCaRbiyPaB. enAkñúg three-tier design, user interface dMe N IrkarenAelI
client/ ral;Tin ñn ½yTaMg Gs;rkSTukenAelI server dUc eTAnwg two-tier design Edr b:uEnþ
three-tier design man middle layer mYyeTotenAcenøa Hrvag client nig server eday
dMe N IrkarsMe N IrBI client ehIybkERbvaeTACa data access commands Edl server
yl; nig GacdMe N IrkarbBa¢aenaH)andUc rUb xageRkam. eyIg ehA middle layer fa
application server BIe RBaHpþl ; application logic or business logic EdlRbB½n §
RtUvkar. Three-tier designs eKk¾GacehAfa n-tier designs edIm,Ib Ba¢ak;BIkarksagmYy
cMn Yn EdleRbIR)as; intermediate layer elIs BImYy.

Two-tier

Three-tier

(rUb 9.6)

9-9
 KuN RbeyaCn_én application logic layer KWf a three-tier design eFVIe Gay
el,ÓndMe N IrkarRbB½n §TaMg mUl kan;EtRbesIreLIg (enhance overall performance) eday
kat;b nßy server’s workload. karbMEbk application logic layer dac;BIKñak¾s Mral
bnÞúk complex processing tasks enAelI client pgEdr ehIy layer GacdMe N Irkar
enAelIkMuBüÚT½rEdlmansmtßPaBx<s ;C ag client workstation Fmμta.
Application User
Architecture Data
Logic Interface
Central data processing Server X X X
center Client
Central server with remote Server X X
terminals Client X
Stand-alone client Server
Client X X X
Two-tier client/server Server X X
Client X X
Three-tier client/server Data server X
Application server X
Client X
(rUb 9.7)
rUb xagelIbgðajBITIkEnøg pÞúk data, application logic, and user interface
cMe BaH architectures CaeRcIn RbePT.
2. 3. Cost-Benefit Issues
edIm,IRTRTg; business requirements RbB½n §Bt’manRtUvEtGacBRgIkBRgYm)an
(scalable)/ manGMN ac (powerful) nig pøa s;b þÚr eTAtamkalHeTsH (flexible)
]TahrN _³ client/server system cMe BaHRkumh‘un PaKeRcIn pþl ;n Uv features CaeRcIn bBa©Úl
KñaedIm,IRTRTg;tMrUvkar dUe cñHenAeBlEdlCMn Yj manPaBrIkcMe rIn rWf ycuH client/server
system manlT§PaBsMr beTAtammCÄdæa nCMn Yj ya:g qab;r h½s )an. enAeBlTMh MC Mn Yj ERb
RbYl vagayRsYl EktMrUvcMn Yn clients and processing functions BYkeKdMe N IrkarCaCag
EktMrUvsmtßPaBrbs; large-scale central server.
Client/server computing GaceFVIe GayRkumh‘un bBa¢Ún applications dMe N Irkar
enAelI expensive mainframe eTAkan; client platform mantMélefakCagvij elIs BI
enHeTot clients and servers GacTMn ak;TMn gKñaqøg kat; platforms CaeRcIn edayeRbIR)as;
bBa¢a SQL.

9-10
 Cacug bBa©b ; client/server systems kat;b nßy network load and response
times dUe cñHGñkeRbIR)as;GaceRbIR)as;Tin ñn ½ykñúg el,ÓnelOnCagmun . ]TahrN _³
cUrBic arN aeTAelIGñkeRbIR)as;e nAkñúg Rkumh‘un cg;)anBt’mancMe BaHtMéllk;s rub RbB½n §RtUv
bBa¢Ún sale transaction files 3 dac;e dayELkBIKñaBITItaMg kariyal½yepSgKñaedIm,Ipþl ;
Tin ñn ½yGaceGay clients KN nacMe BaH file server design b:uEnþc Me BaH client/server
system vij server EsVg rkTin ñn ½y/ dMe N Irkar processing N acaM) ac; nig eqøIytbya:g
elOneTAkan;s Me N Irrbs; client. Data retrieval and processing functions )anlak;
kM)aMg BI client BIe RBaHBYkvadMe N IrkarenAelI server min EmnenAelI client eT.
3. Processing Methods
enAkñúg kareRCIs erIs application architecture GñkeRbIR)as;RbB½n §RtUvkMn t;f aetI
RbB½n §C a online system, batch system rWRbB½n §TaMg 2 bBa©Úl Kña.

3. 1. Online versus Batch Processing

RbB½n §kMuBüÚT½rkalBImun Bwg Ep¥kCacMbgeTAelI batch processing b:uEnþRbB½n §PaKeRcIn
elIs lubsBVéf¶e RbIR)as; online processing. Online system edaHRsayral;
transactions TaMg Gs;e nAeBlTTYl )an nig pþl ; output pÞa l;e TAkan;GñkeRbIR)as; ehIyva
)anksagsMvaTya:g rwg maMrvagRbB½n § nig GñkeRbIR)as; edaysarEtlkçN Hskmμrbs;va.
]TahrN _³ RbB½n §e KeRbIR)as;e dIm,IRKb;RKgkarkk;s Mb uRtynþe haHeQμaHfa airline
reservation system eRbIR)as; online processing edayenAeBleyIg Bin itüemIl eCIg
ynþe haH eyIg RKan;EtbBa©Úl eyIg eFVId Me N IrBITIkEnøg N aeTAkan;kEnøg N a RBmTaMg
kalbrie cäT nig eBlevla eBlenaHRbB½n §n wg eFVIkarEsVg rkBt’manecjBI database rbs;
xøÜn ehIyeqøIytbedaybgðajBt’manenAelI screen dUc Ca available flights, times,
and prices. Rbsin ebIGtif iC ncg;kk;e dayRKan;EtbBa©Úl eQμa H/ Gas½ydæa n/ credit card
information nig Bt’manmYycMn Yn eTot enaHRbB½n §n wg kk;kEnøg RBmTaMg elxekAGIGgÁúy
nig eFVIEkERb database Pøam²pgEdr. Online processing systems manlkçN HTUe TATaMg
4 dUc xageRkamenH³
1. RbB½n §d Me N Irkar transactions TaMg Rsug enAeBlBYkvaekIteLIg .
2. GñkeRbIR)as;TMn ak;TMn gedaypÞa l;C amYyRbB½n §B t’man.

9-11
 3. GñkeRbIR)as;GaceRbIR)as;Tin ñn ½yRBav².
4. RbB½n §Bt’manRtUvEtdMe N Irkarral;e BlcaM)ac;e dIm,IRTRTg; business functions.
3. 2. Batch Processing
eKRbmUl pþúMTin ñn ½y nig dMe N IrkarBYkvaCaRkumcMe BaH batch processing system.
eTaHbIC aeKeRbIR)as; online processing cMe BaH interactive business system EdlTam
TareGaybBa©Úl input nig beBa©j output Pøam²k¾e day k¾ batch processing Gac
dMe N IrkarTTYl )anlT§p lRbesIrCagkñúg sßankarmYycMn Yn . ]TahrN _³ batch
processing CaTUe TARtUv)aneKeRbIR)as;e TAelIc Mn Yn Tin ñn ½yd¾e RcIn EdlRtUvdMe N IrkarcMe BaH
eBlevlakMn t;C ak;l ak;N amYy dUc CakarKN naR)ak;ExbuKÁl ikerogral;c ug Ex. enAkñúg
batch processing eKRtUvpþMú input transactions eTACa file mYyehIydMe N IrkarCamYyKña
]TahrN _³ dMe N IrkarKN nacMN at;f ñak;s is Ssalaerogral;Ex edayRtUvRbmUl Bin Þúmux viC ¢a
nImYy²rYc ehIybBa©Úl enAcug Ex. Batch processing systems pþl ;l kçN HmYycMn Yn
dUc Ca³ RbmUl / pþúM nig dMe N Irkar transactions enAkMLúg eBlCak;l ak;N amYy dUe cñH IT
operation group GacdMe N Irkar batch programs kñúg eBlkMn t;C ak;l ak;N amYyeday
min caMBak;B½n §C amYyGñkeRbIR)as;e T eyIg GaceFVIvakñúg ema:g eFVIkarFmμta rWc ug s)þah_.
3. 3. Combined Online and Batch Processing
KYrkt;s MKal;Edrfa online system GaceRbIR)as; batch processing edIm,Id Me N Ir
kic ©kardEdlCak;l ak;N amYy. ]TahrN _³ Rkumh‘un lk;TMn ij mYyeRbIR)as; online and
batch methods TaMg BI edayRbB½n §e RbI online processing edIm,Ie daHRsay data entry
and inventory updates xN H reports dMe N IrkarCaRkum. kMLúg eBlema:g eFVIkarFmμta
salesperson bBa©Úl karlk;e dayeRbIR)as; barcode scanner EdlCaEpñkmYyén
RbB½n §Bt’mansMrab;d Me N Irkar sale transaction RbcaMéf¶ nig EfrkSa online inventory
file. enAeBl salesperson bBa©Úl transaction eBlenaH online processing ekIteLIg
bnÞab;mkRbB½n §KN natMélluy/ EkERb inventory file nig beBa©j output enAelI screen
and printed receipt. enAeBlbiThag RbB½n §e RbIR)as; sale transactions edIm,Ib egáIt
sales report RbcaMéf¶e dayeRbIR)as; batch processing eyIg eXIj fa kñúg krN Ie nH
skmμPaBekIteLIg Etmþg Kt;e rogral;éf¶ nig CaTUe TAenAeBlbiThag.

9-12
 enAkñúg RbB½n §]TahrN _x agelI online processing pþl ;KuN RbeyaCn_mkCab;
CamYy BIe RBaHenAeBlbBa©Úl nig RtYtBin itüPaBRtwmRtUvTin ñn ½yrYc ehIy Tin ñn ½yGaceRbIR)as;
)an nig up-to-date eTotbnÞab;BIe K)anEkERbsþúkrYc ehIyedayRbB½n §. eTaHbIC aya:g N a
k¾e day online processing mantMéléfø ehIy\T§iBleTAelI system downtime or
slowdown b:H Bal;x øa Mg Cag batch processing. elIs BIe nH online processing
TamTareGayman backup Cajwkjab;.
4. Network Models
Network GaceGayeyIg Eckcay nig eRbIR)as; hardware, software, and data
resources edIm,Ikat;b nßycMN ay nig pþl ;l T§PaBbEnßmeToteTAeGayGñkeRbIR)as;.
enAeBlerobcMEpnkarcMe BaH network design eyIg RtUvEtBic arN aeTAelI network
topology, protocols, and licensing issues Edlnwg erobrab;l MGitkñúg cMn uc enH
ehIyeyIg k¾RtUvEtKitcMe BaH system performance, security, and interruption issues
pgEdr.
4. 1. Network Topology
viFIe dIm,I configure network eKehAfa network topology. TaMg LAN and
WAN networks CaTUe TAtMe robkñúg KMr UTaMg 3 KW bus, star, and ring. Concept CaTUe TA
dUc Kñaedaymin KitBITMh M network b:uEnþ physical implementation xus KñacMe BaH
large-scale WAN EdlBRgIkBaseBj business enterprise CamYy LAN tUc mYy
enAkñúg department EtmYyKt;. Topology EckCa 3 KW bus, star, and ring.
Bus Network
enAkñúg bus network manEt communication path EtmYyKt;EdlP¢ab;
mainframe computers, servers, workstations, and peripheral devices. Bt’man
RtUvbBa¢Ún tamTis edABIe qVg eTAsþaM rWBIs þaMe TAeqVg BI workstation N amYyeTAkan;
workstation epSgeTot. KuN RbeyaCn_c Me BaH bus network KWf aeyIg Gacbnßy rWb Enßm
devices N amYyBI network Rtg;c Mn uc N amYyedayKμa nb:H Bal;e TAdl; network TaMg mUl
elIs BIe nHeTot failures cMe BaH workstation N amYyenAelI network min )anb:HBal;
caM)ac;e TAdl; workstations epSgeToteT.

9-13
 Star Network
Star network man central computer rYmCamYy workstation mYy rWe RcIn TMn ak;
TMn gCamYyKñaedIm,Ib egáItTMrg; star. Central computer pÞúkral;Tin ñn ½yTaMg Gs;EdlRtUvkar
dMe N Irkar input BI workstation elIs BIe nHeTot vamin caM)ac;e dIrtYC a primary data
storage point eT vaGacedIrtYn aTIC a network coordinator sMr ab;e FVIe Gay devices
epSgeTotGacbBa¢Ún nig TTYl Tin ñn ½yBIKñaeTAvij eTAmk. Star network pþl ; efficiency
and close control eTAelITin ñn ½ydMe N Ir karenAelI network ÉKuN vib tþvij KWf a network
TaMg mUl RtUvBwg Bak;e TAelI central computer.
Ring Network
Ring network erobcMkMuBüÚT½rdak;d Uc eTAnwg ragrgVg ;mUl EdlGaceGayvaTak;Tg
CamYyKñaeTAvij eTAmk. CaerOyeKeRbIR)as;va enAeBl processing dMe N IrkarenAÉ local
sites CaCag central location.

4. 2. Network Protocols
enARKb;krN ITaMg Gs; network RtUveRbIR)as; protocols EdlKWC asMn uM standards
sMrab;RKb;RKg network data transmission. Network protocol manRbCaRbiyCageK
KW TCP/IP (Transmission Control Protocol/Internet Protocol) EdlGPivDÆn_e LIg
eday U.S Department of Defense edIm,IGnuBaØatie GaykMuBüÚT½renATItaMg epSgKñaGacTak;
TgKña)an elIs BIe nHeTotsBVéf¶e KGaceRbIvaedIm,Ie RbIR)as; Internet )anpgEdr. man
network protocols epSgeTotdUc Ca³ NetBIOS Ca protocol manRbCaRbiycMe BaH LAN
nig IPX/SPX Ca protocol eRbIe day Novell Corporation.
4. 3. Licensing Issues
vamansarHsMxan;kñúg karBic arN aeTAelI software licensing restrictions
enAeBlKitcMe BaH network design. Software vendors pþl ;n Uv software license
kñúg TMrg;C aeRcIn RbePT edayPaKeRcIn kMn t;e TAelIc Mn Yn GñkeRbIR)as; rWc Mn Yn kMuBüÚT½rEdl
eRbIR)as;kmμviFIkñúg eBlEtmYy. eyIg k¾RtUvEtesIubGegáteGay)anRbug Rby½tñe lIs mtßPaB
network software pgEdredIm,IGHGagfa vaBitCaGacedaH system traffic rMB wg Tuk)an.

9-14
5. Modeling Application Architecture
eyIg )ansikSaBImun mkehIyfa eKGaceRbIR)as; CASE tools BaseBj systems
development process ehIyelIs BIe nHeTot multipurpose drawing tools mantMél
CaBie ssenAeBleyIg begáIt rWksag application architecture. Tool mYykñúg cMe N am
tools CaeRcIn manRbCaRbiyKW Microsoft Visio Edlpþl ; drawing types, styles,
templates, and shapes CaeRcIn RbePT. ]TahrN _³ Visio pþl ; templates cMe BaH basic
network design.

6. System Management and Support

Information system RtUvEtbBa©Úl rbs;RtUvkarcMe BaH system
design
management and support tools edIm,IRtYtRta system performance, maintain
system security nig edaHRsay system interruption BI fault management to
disaster recovery.

6. 1. Performance Management
eKksag performance management tools edIm,ITTYl ykBt’mancMe BaH system
resources and activity levels. Performance management tools GacRtYtBin itü
system usage, capacity, and trends. Performance management GacbBa©Úl karEk
ERbbnþic bnþÜc eTAelI network configuration or software setting edIm,ITTYl )an
performance kan;EtRbesIreLIg .

6. 2. System Security
kic ©EfrkSa system security Bak;B½n §C amYykic ©karcMn Yn 2 KWTImYy RtUvEtman
kareRtomlkçN HCamun cMe BaHkarkMn t; nig RtYtBin itü user IDs, passwords, and data
access levels. TIB I security system tools RtUvEtGacedaHRsay virus protection
nig EsVg rkeGayeXIj karcUl eRbIR)as;N aeTAkan;RbB½n §EdlKμankarGnuBaØati edayrYmbBa©Úl
TaMg intruders pgEdr. bEnßmeTAelI built-in controls and security software
Rkumh‘un Gaccat;viFankarepSgeTotedIm,Ie FVIe Gay system security kan;EtRbesIreLIg
dUc Ca³ user training/ kic ©karBarcMe BaH physical security of hardware and software,

9-15
security audits, and strong security policies EdleKyl;ya:g c,as; nig BRgwg Bas
eBjRkumh‘un .
6. 3. Fault Management, Backup, and Disaster Recovery
eTaHbIC aeyIg xMe FVIkarksagvaedayl¥ya:g N ak¾e day k¾RKb;RbB½n §n wg CYb RbTHCa
bTBie saFn_c Me BaHbBaðamYycMn Yn Camin xan dUc Ca³ hardware failures, software errors,
user mistakes, and power outages (power outages KWkMLúg eBlEdl power
supply min dMe N Ir kar ) elIs BIe nHeToteyIg k¾K YrBic arN aeTAelIkarKMramkMEhgfμI²BIB Yk
hackers pgEdr. eyIg RtUvEtsμa nTukCamun cMe BaHbBaða TaMg enaH nig erobcMEpnkarsMrab;
edaHRsaybBaðaTaMg enaH edaycat;TukvaCaEpñkN amYyén systems design.
yuT§s aRsþl ¥b Mp utKWraraMg bBaðamun eBlvaekIteLIg EdleFVIe Gayb:HBal;e TAelIRbB½n §
]TahrN _³ eyIg )ansikSarYc mkehIykalBImun cMe BaH data validation, audit trail files,
security measures, and other control features eRbIR)as;s Mr ab;C YyeFVIe GayR)akdfa
Tin ñn ½ybBa©Úl nig dMe N IrkaredayRtwmRtUv. eTaHbIC aya:g N ak¾e day eyIg k¾RtUvpþl ;
meFüa)aybEnßmeTotedIm,Ie daHRsay system faults and interruptions.
Fault Management
kþIkgVl ;C acMb grbs; system administrator KWEsVg rkeGayeXIj nig edaHRsay
operational problems eGay)anelOntamEtGaceFVIe TA)an. eKCaerOy²ehAkic ©karenaH
fa fault management edayrab;b Ba©Úl TaMg RtYtBin itüelIRbB½n §e dIm,IEsVg rksBaØabBaða/
kt;Rta system failures/ diagnosing problem nig pþl ;s kmμPaBEktMrUv. RbB½n §kan;Et
sμúKsμaj vakan;EtlM)akviPaKeraKvin ic ä½y nig EbgEckbuBVe htue Gaydac;e cjBIKña.
Backup and Disaster Recovery
RKb; system design RtUvEtkareRtómlkçN HcMe BaH data backup and recovery.
Backup sMe dAeTAelId Me N IrkarcMl gTin ñn ½ybnþ\ tdac; rIÉ recovery procedures Bak;
B½n § restoring data nig eFVIe GayRbB½n §d Me N IrkardUc kalBIRbB½n §mun manbBaða. Overall
backup and recovery plan CaerOy²eKehAfa disaster recovery plan.
viFIe daHRsaycMe BaH online system backup KWe RbIR)as; file mYyeKeGayeQμaHfa
log file or journal file EdlpÞúkc,ab;c Ml g record nImYy²enAmun eBl rWe RkayeBl
EkERb. Rbsin ebITin ñn ½yxUc xat eyIg GaceRbIR)as; most recent backup edIm,I recover

9-16
or restore data file bnÞab;d Me N IrkareTAelI log file edIm,In aMTin ñn ½yeTAkan;l kçN Hmun
eBlxUc xat. vaeRbIR)as; recovery time srub yUrcMe BaH large-scale databases
EdlmancMn Yn records and transactions eRcIn . Logging functions bBa©Úl EtenAkñúg
large-scale DBMSs.
eRkABI backup and recovery procedures caM)ac;e dIm,IRTRTg; business
operations eKRtUvEteRbIR)as; file retention laws and regulations eTAelI company
data pgEdr. Rbsin ebI government rule kMn t;f a records cMe BaHkarbg;l uyeGay
Rkumh‘un RtUvrkSaTuksMrab;ryHeBl 3 qñaM dUe cñHkarksagRtUvEtGacRTRTg;e TAtamryHeBl
Edl)ankMn t;.
7. Systems Design Completion
Software design Bak;B½n §C amYydMN ak;kal 2 epSg²Kña ³ dMN ak;kalTImYy)an
cab;e pþImkMLúg eBl systems analysis phase enAeBlEdlral; functional primitives
TaMg Gs;RtUv)ankMn t; nig kt;RtaCaÉksarCamYy process descriptions. Tis edAKWe dIm,I
kMn t;e Gay)an system’s functions nig kMn t;GVIEdl logical module nImYy²dMe N Irkar.
dMN ak;kalTIBIe nAkñúg software design KWd Me N IrkarkMLúg eBl systems
implementation phase enAeBlEdl programmers kMn t;e Gay)anR)akdetI program
nImYy²nwg bMe bjTis edArbs;vaedayrebobN a ehIydMe N IrkarenHnwg erobrab;e nAkñúg CMBUkTI
10 EdlBiB N ’n aetIRtUvGPivDÆn_/ sakl,g nig kt;RtaCaÉksarcMe BaH applications eday
rebobN a.
skmμPaBcug bBa©b ;e nAkñúg systems design phase KWe RtómlkçN HerobcM system
design specification/ TTYl karyl;RBmBIGñkeRbIR)as; nig bBa¢Ún presentation CUn eTA
management.

7. 1. System Design Specification

System design specification eKk¾GacehAfa technical design
specification rW detailed design specification EdlKWC a documentation bgða jBI
karksageBlelj (complete design) cMe BaHRbB½n §Bt’manfμIC amYycMN aylMGit/

9-17
buKÁl ik nig tarageBlevlasMrab;d Me N Irkar SDLC phase bnÞab;e TotKW systems
implementation.
System design specification KWRKan;EtCaÉksarmanGkSre)aHBum< rWs resrenABI
elIs Mrab;e Gay operational system vas;Evg. vaxus BI system requirement
documentation Edlkt;Rtakñúg TMr g;mYyGaceGayGñkeRbIR)as;e mIl yl; b:uEnþ system
design specification manTis edAeq<a HeTAkan; programmers EdlCaGñknwg eRbIvaedIm,I
begáItkmμviFIc aM)ac;. EpñkmYycMn Yn enAkñúg system requirement documentation RbEhl
CaGacbgðajmþg eTotenAkñúg system design specification dUc Ca³ process
descriptions, data dictionary entries, and data flow diagrams.
System design specification xus Kña eTAtamRbEvg dUe cñH eyIg RtUvEtcat;Ecg
erobcMvaeGay)anRbug Rby½tñ nig dak;e lxerogRKb;TMB½rtamlMd ab;. eyIg KYrEtbBa©Úl cover
page/ taragmatikarerOglMGit nig lib iRkm (index) ehIymatikarerOgén system design
specification GaRs½yeTAtamsþg ;d arRkumh‘un nig PaBsμúK sμa jrbs;RbB½n §. System
design specification CaTUe TAeRbIR)as;rcnasm<½n §RsedogKña edayEckCa 5 EpñkKW
Management summary, System components details, Environmental
requirement, Implementation requirements, Time and cost estimates, and
Appendices (Rbsin ebIRtUvkar).
1. Management Summary. Management summary pþl ;n UvTsSnHsegçb
(overview) énKMe ragcMe BaH company managers. vabgða jkic ©Rbwg ERbgGPivDÆn_C acMn uc
sMx an;²mkdl;s BVéf¶e nH/ pþl ;n Uv current status report/ segçb cMN ayKMe ragbc©úb ,nñ
nig cMN aycMe BaHdMN ak;kalenAsl;/ RtYtBin itüeLIg vij cMe BaHKuN RbeyaCn_TaMg mUl én
RbB½n §f μI/ bgðaj system development phase schedule nig elIkeLIg cMn uc sMx an;²cMe BaH
bBaðaN aEdl management RtUvkarniyay.
2. System Components Details. EpñkenHpÞúknUvkarksagTaMg Rsug (complete
design) cMe BaHRbB½n §f μIe dayrYmbBa©Úl ³ user interface, outputs, inputs, files,
databases, and network specifications. eyIg KYr EtbBa©Úl source documents,
report and screen layouts, O-O diagrams, and documentation Tak;TgepSgeTot.
eyIg KYrEtbBa©Úl GVI²tMrUveGaymancMe BaH support processing dUc Ca backup and

9-18
recovery, startup processing, and file retention. Rbsin ebIkarTij software
package CaEpñkmYyényuT§s aRsþ eyIg RtUvEtbBa©Úl interface information RtUvkarrvag
package nig RbB½n §e yIg kMB ug GPivDÆn_. Rbsin ebIe yIg eRbI CASE design tool eyIg Gac
e)aHBum< design diagrams nig documentation epSgeTotecjBI toolenaHedaypÞal;
Etmþg .
3. Environmental Requirements. EpñkenHerobrab;B I constraints or
conditions b:HBal;e TAelIRbB½n § edayrYmbBa©Úl TaMg GVI² tMrUveGaymanTaMg LayN aEdlBak;
B½n § operations, hardware, system software, or security. ]TahrN _c Me BaH
operational constraints rYmman transaction volumes EdlRbB½n §RtUvEtRTRTg;
eGay)an/ data storage requirements, processing schedules, reporting
deadlines, and online response times.
4. Implementation Requirements. enAkñúg EpñkenH eyIg eFVIkarkMn t; start-up
processing, karTTYl nig bBa©Úl Tin ñn ½yCaelIkdMb Ug (initial data entry or
acquisition), user training requirements, and software test plans.
5. Time and Cost Estimates. EpñkenHpþl ;n UvtarageBlevlalMGit/ cMN ay
sμanTuk nig staff requirements cMe BaH systems development phase nig karbEnßm
bnßyeTAelIEpñkenAsl;én SDLC. eyIg k¾bgðajBIc MN ayTaMg Gs;rhUtmkdl;e BlenH
cMe BaHKMe rag nig eRbobeFobCamYycMN ayEdleyIg )ansμanTukBImun mk.
6. Appendices. eyIg GacbBa©Úl sMParHbEnßm (supplemental material) eTAkan;
esckþIb Enßm (appendices) enAcMn uc cug bBa©b ;én system design specification. enAkñúg
EpñkenH eyIg GacbBa©Úl c,ab;c Ml gÉksartaMg BId MN ak;kalTaMg 3 dMe N IrkarCabnþb nÞab;
kalBImun Rbsin ebIBYkvaGacpþl ;C aÉksareyaggayRsYl (easy reference) cMe BaH
GñkGan.
7. 2. User Approval
GñkeRbIR)as;RtUvEtRtYtBin itüeLIg vij nig yl;RsbeTAelI interface design, report
and menu designs, data entry screens, source documents nig EpñkepSg²eTotén
RbB½n §EdlGacb:HBal;e TAdl;BYkeK. dMe N IrkarRtYtBin itüeLIg vij nig yl;RsbecHEteFVIkar
CabnþBaseBj systems design phase. enAeBleyIg bBa©b ;karksag reports
9-19
eyIg KYrEtCYb BiPakSaCamYyGñkeRbIR)as;e dIm,IRtYtBin itü prototype eLIj vij cMe BaH/ EktMrUv
karksagRbsin ebIc aM)ac; nig TTYl karyl;RsbCalaylkçN _GkSr.
karyl;e TAelIb BaðasuvtßiPaBBIGñkeRbIR)as;BaseBj design phase man
sarHsMx an;N as; edayviFIe daHRsayenHeFVIe GayR)akdfa eyIg min mankic ©karCacMb gedIm,I
RbmUl karyl;RsbenAcug bBa©b ;e T ehIyvaeFIVe GayGñkeRbIR)as;b nþaTMn ak;TMn gCamYy
system development nig pþl ; feedback faetIe yIg eFVIkarcMe KaledAEdrrWGt;. EpñkmYy
cMn Yn én system design phase RbEhlmin Tak;TajcitþGñkeRbIR)as;e T b:uEnþe yIg RtUv
EsVg rkkaryl;RsbeGaykan;Etqab;c Me BaHcMn uc N aEdlb:HBal;e TAelIGñkeRbIR)as;.
smaCik IT department epSgeTotk¾RtUvkarRtYtBin itüeLIg vij eTAelI system
design specification. IT management kgVl ;C amYybBaða buK Ál ik/ cMN ay/ hardware
and system software requirements/ network impact nig \T§iB lepSgeToteTAelI
operating environment enAeBlbBa©Úl RbB½n §. Operations group nwg cab;GarmμN _
CamYy processing support, report distribution, network loads, karrYmbBa©Úl Kña
CamYyRbB½n §e pSgeTot nig hardware or software issues TaMg LayN aEdlBYkeKRtUvkar
erobcM. eyIg RtUvEtCaGñkTMn ak;TMn gd¾l ¥ (communicator) edIm,Ie FVIe Gaymnus S
up-to-date/ TTYl yk input nig karEN naMrbs;B YkeK nig TTYl kic ©yl;RBmcaM) ac;.
enAeBlbBa©b ; system design specification eyIg EckcayÉksarenaHeTAkan;
RkumGñkeRbIR)as;/ IT department personnel, and company management cMe KaledA
elIs BIe nHeTot eyIg KYrEtEckcayÉksarenHya:g ehacN as;e Gay)anmYys)aþh _ mun nwg
dMe N Ir presentation edIm,Ie GayGñkTTYl (recipients) maneBlevlaemIl RKb;RKan;.
7. 3. Presentations
CaFmμtaeyIg nwg pþl ; presentations mYycMn Yn enAcMn uc cug bBa©b ;én systems
design phase ehIy presentations enHpþl ;»kaseGayeyIg GacBnül;B IRbB½n §/ eqøIytb
sMn Yr/ Bic arN aresckIþGtßaFib,ay (comments) nig pþl ;s uvtßiPaBcMe BaHkic ©s Me rccitþ
cug eRkay. Presentation dMb Ug eKKWe TAkan;GñkviPaKRbB½n §/ programmers and technical
support staff members EdlCaGñknwg Bak;B½n §C amYydMN ak;kalKMe ragbnþe Tot
rWkarRTRTg;Rbtib tþikarcMe BaHRbB½n §. edaysarGñkTTYl suT§EtmancMe N aHdwg xagEpñk IT
dUe cñH presentation GacmanlkçN HxiteTAxagbec©keTs.
9-20
 eyIg nwg pþl ; presentation CabnÞab;e ToteTAkan; department managers
nig GñkeRbIR)as;BI departments EdlBak;B½n §C amYyRbB½n §. dUc eTAnwg presentation elIkTI
mYyEdr Tis edACacMbgrbs;e yIg KWTTYl ykkic ©RTRTg; nig yl;RsbcMe BaH systems
design. vamin EmnCa technical presentation eTedayvamanbMN gbgáe GaymanGnþrkmμ
CamYyRbB½n § nig karcab;GarmμN _rbs; management eTAelIf vikar (budgets)/ tarageBl
evla/ buKÁl ik nig karb:HTgÁic eTAelI production environment.
Presentation cug eRkayKWe FVIe LIg eTAkan; company management. mun eBl
eyIg pþl ; presentation enH eyIg KYrEtTTYl kic ©yl;RsbTaMg Gs;c Me BaH presentation
BImun mkCamun sin . dUc eTAnwg management presentation enAcMn uc cug bBa©b ; systems
analysis phase, presentation enHk¾manTis edAsMx an;p gEdrKWTTYl karyl;Rsb
nig RTRTg;c Me BaHdMN ak;kalGPivDÆn_RbB½n §b nþe TotKW systems implementation edayrYm
bBa©Úl TaMg karpþac;j ar rWs nüacMe BaHhirBaØvtßú nig FnFanRtUvkarepSgeTot.
edaysMGageTAelI presentation nig Tin ñn ½yeyIg )anesñI management RbEhl
CaQaneTAkan;c Mn uc mYykñúg cMe N amkic ©s Me rccitþTaMg 3 KWdMe N Ir systems development
bnþe Tot/ dMe N IrkargarbEnßmeToteTAelI systems design phase rWbBa©b;KMe rag.
CMBUkeRjaynwg erobrab;BI systems implementation EdlCadMN ak;kalTIb Yn enAkñúg
systems development life cycle (SDLC).

Review Questions
1. cUrerobrab; nig Bnül;BI application architecture?
2. cUrerobrab;B I client/server architecture edayrYmbBa©Úl TaMg fat and thin
clients?
3. cUrBnül;B IPaBxus Kña rvag online processing and batch processing
RBmTaMg ]TahrN _mkbBa¢ak;pg?
4. cUrBnül; nig erobrab;B I fault management, backup, and disaster recovery?
5. cUrerobrab;B IEpñkenAkñúg system design specification RBmTaMg briyayBI
matikarerOgcMe BaHEpñknImYy²pg?
r r Ys s
9-21