Solutions manual for database systems design implementation and management 12th edition by coronel All Chapters 1-16

Appendix gC gThe gUniversity gLab:
Conceptual gDesign gVerification, gLogical gDesign, gand
gImplementation

Appendix C g




The University Lab: Conceptual Design,
g g g g



gVerification,Logical Design, and Implementation
g g g g




Discussion gFocus


How gis ga gdatabase gdesign gverified, gand gwhy gis gsuch gverification gnecessary?



Use gour gdetailed ganswer gto gquestion g1 gto gfocus gclass gdiscussion gon gdatabase gdesign gverification.
gStress gthat gthe gverification gprocess guses gthe ginitial gER gmodel gas ga gcommunication gtool.




The gdesigner gmay gbegin gthe gverification gprocess gby gdescribing gthe gorganization's goperations gto gits
gend gusers, gbasing gthe gdetailed gdescription gon gthe ginitial gER gmodel. gNext, gexplain ghow gthe

goperations gwill gbe gsupported gby gthe gdatabase gdesign. gStress gthat gthe gdesign gmust gsupport gthe gend-

user gapplication gviews, goutputs, gand ginputs. gPoints gto gbe gaddressed ginclude gsuch gquestions gas:

 Is gthe gdescription gaccurate? gIf gnot, gwhat gaspects gof gthe gdescription gmust gbe gcorrected?
 Does g the g model g support g the g end-user g requirements? g If g not, g what g aspects g of g the
g end-usergrequirements ghave gnot gbeen gaddressed gor ghave gbeen gaddressed ginadequately?




Keep g in g mind g that g even g a g model g that g perfectly g addresses g all g initially g determined g end g user
g requirements gis glikely gto gneed gadjustments gas gthose gend gusers gbegin gto gunderstand gthe

gramifications gof gthe gdatabase gdesign's gcapabilities. gIn gmany gcases, gthe gend gusers gmay glearn gwhat

gthe gorganization's gprocesses gand gprocedures gactually gare, gthus gleading gto gnew grequirements gand

gthe gperception gof gnew gopportunities. gThe gdatabase gdesigner gmust gkeep gsuch glikely gdevelopments gin

gmind, gespecially gif g(s)he gworks gas ga gdatabase gdesign gconsultant. g(Anticipation gof gsuch gdevelopments

gmust gbe gfactored ginto gthe gcontract gnegotiations gfor gconsulting gfees.)




Discuss gthe grole gof gthe gsystem gmodules.



1

, Appendix gC gThe gUniversity gLab:
Conceptual gDesign gVerification, gLogical gDesign, gand
gImplementation




The g use g of g system g modules g can g hardly g be g overemphasized g in g a g database g design
g environment. g Stressgthese gmodule gcharacteristics gand gfeatures:



 Modules grepresent gsubsets gof gthe gdatabase gmodel: gSmaller g"pieces" gare gmore geasily
gunderstood.

 Modules gare gself-contained gand gaccomplish ga gspecific gsystem gfunction; gif gsuch ga
gsystem gfunction gmust gbe gmodified, gother gfunctions gremain gunaffected.

 Modules gfit ginto ga gmodular gdatabase gdesign, gwhich gis gmore geasily gmodified gand
gadapted gto gnew gcircumstances. gBecause gmodification gefforts gare gfocused gon ga gdatabase

gsubset, gproductivity gof gboth gdesigners gand gapplication gdevelopers gis glikely gto gbe

genhanced.




Module ginterfaces gmust gbe gclear gif gthe gmodules gare gexpected gto gwork gwell gwithin gthe goverall gsystem.




2

, Appendix gC gThe gUniversity gLab:
Conceptual gDesign gVerification, gLogical gDesign, gand
gImplementation
Answers gto gReview gQuestions


1. Why gmust ga gconceptual gmodel gbe gverified? gWhat gsteps gare ginvolved gin gthe gverification gprocess?


The gverification gof ga gconceptual gmodel gis gcrucial gto ga gsuccessful gdatabase gdesign. gThe
gverification gprocess gallows gthe gdesigner gto gcheck gthe gaccuracy gof gthe gdatabase gdesign gby:



 Re-examining gdata gand gdata gtransformations.
 Enabling g the g designer g to g evaluate g the g design g efficiency g relative g to g the g end
g user's g andgs ystem's gdesign ggoals.




Keep gin gmind gthat, gto ga glarge gextent, gthe gbest gdesign gis gthe gone gthat gserves gthe g end-user
grequirements gbest. gFor gexample, ga gdesign gthat gworks gwell gfor ga gmanufacturing gfirm gmay gnot gfit

gthe gneeds gof ga gmarketing gresearch gfirm, gand gvice gversa.




The gverification gprocess ghelps gthe gdesigner gto gavoid gimplementation gproblems glater gby:

 Validating gthe gmodel's gentities. g(Remember gthe gminimal gdata grule.)
 Confirming gentity grelationships gand geliminating gduplicate, gunnecessary, gor
gimproperlygdefined grelationships.

 Eliminating gdata gredundancies.
 Improving gthe gmodel's gsemantic gprecision gto gbetter grepresent greal-world goperations.
 Confirming gthat gall guser grequirements g(processing, gperformance, gor gsecurity) gare gmet.


Verification gis ga gcontinuous gactivity gin gany gdatabase gdesign. gThe gdatabase gdesign gprocess gis
gevolutionary gin gnature: gIt grequires gthe gcontinuous gevaluation gof gthe gdeveloping gmodel gby

gexamining gthe geffect gof gadding gnew gentities gand gby gconfirming gthat gany gdesign gchanges

genhance gthe gmodel's gaccuracy.




The gverification gprocess grequires gthe gfollowing gsteps:



1. Identify gthe gdatabase's gcentral gentity.


The g central g entity g is g the g most g important g entity g in g our g database, g and g most g of
g the g othergentities gdepend gon git.




3

, Appendix gC gThe gUniversity gLab:
Conceptual gDesign gVerification, gLogical gDesign, gand
gImplementation




2. Identify gand gdefine geach gmodule gand gits gcomponents.


The g designer g divides g the g database g model g into g smaller g sets g that g reflect g the g data
g needs g ofgparticular gsystems gmodules gsuch gas ginventory, gorders, gpayroll, getc.




3. Identify gand gdefine geach gof gthe gmodule's gprocesses.


Specifically, g this g step g requires g the g identification g and g definition g of g the g database g transactions
that grepresent gthe gmodule's greal-world goperations.




4