Solutions Manual for Database Systems: Design, Implementation, and Management (12th Edition) by Carlos Coronel – Complete Answers for Chapters 1–16

Appendix+|C+|The+|UniversiTy+|Lab:
ConcepTual+|Design+|VerificaTion,+|Logical+|Design,+|and+|ImplemenTa
Tion
Appendix C +|




Solutions Manual for Database Systems: Design, Implementa
+| +| +| +| +| +|




ion, and Management (12th Edition) by Carlos Coronel –
+| +| +| +| +| +| +| +|




Complete Answers for Chapters 1–16
+| +| +| +| +|




The University Lab: Conceptual Design, Verification,L
+| +| +| +| +| +
|




ogical Design, and Implementation +| +| +|




Discussion Focus +|




How+|is+|a+|database+|design+|verified,+|and+|why+|is+|such+|verification+|necessary?



Use+|our+|deTailed+|answer+|To+|quesTion+|1+|To+|focus+|class+|discussion+|on+|daTabase+|design+|verificaTion.
+|STress+|ThaT+|The+|verificaTion+|process+|uses+|The+|iniTial+|ER+|model+|as+|a+|communicaTion+|Tool.




The+|designer+|may+|begin+|The+|verificaTion+|process+|by+|describing+|The+|organizaTion's+|operaTions+|To+|i
Ts+|end+|users,+|basing+|The+|deTailed+|descripTion+|on+|The+|iniTial+|ER+|model.+|NexT,+|explain+|how+|The+|op
eraTions+|will+|be+|supporTed+|by+|The+|daTabase+|design.+|STress+|ThaT+|The+|design+|musT+|supporT+|The+|e
nd-
user+|applicaTion+|views,+|ouTpuTs,+|and+|inpuTs.+|PoinTs+|To+|be+|addressed+|include+|such+|quesTions+|as:

• Is+|The+|descripTion+|accuraTe?+|If+|noT,+|whaT+|aspecTs+|of+|The+|descripTion+|musT+|be+|correcTed?
• Does+ | The+ | model+ | supporT+ | The+ | end-
user+ | requiremenTs?+ | If+ | noT,+ | whaT+ | aspecTs+ | of+ | The+ | end-
user+r| equiremenTs+|have+|noT+|been+|addressed+|or+|have+|been+|addressed+|inadequaTely?+|f
or+|any+|assistance+|email+|at+|+|


Keep+| in+| mind+| ThaT+| even+| a+| model+| ThaT+| perfecTly+| addresses+| all+| iniTially+| deTermined+| end+| user+| re
quiremenTs+i| s+|likely+|To+|need+|adjusTmenTs+|as+|Those+|end+|users+|begin+|To+|undersTand+|The+|ramificaTi
ons+|of+|The+|daTabase+|design's+|capabiliTies.+|In+|many+|cases,+|The+|end+|users+|may+|learn+|whaT+|The+|org
anizaTion's+|processes+|and+|procedures+|acTually+|are,+|Thus+|leading+|To+|new+|requiremenTs+|and+|The+|p
1

, Appendix+|C+|The+|UniversiTy+|Lab:
ConcepTual+|Design+|VerificaTion,+|Logical+|Design,+|and+|ImplemenTa
ercepTion+|of+|new+|opporTuniTies.+|Thed
| aTabase+|Tion
+ designer+|musT+|keep+|such+|likely+|developmenTs+|in+|
mind,+|especially+|if+|(s)he+|works+|as+|a+|daTabase+|design+|consulTanT.+|(AnTicipaTion+|of+|such+|developm
enTs+|musT+|be+|facTored+|inTo+|The+|conTracT+|negoTiaTions+|for+|consulTing+|fees.)



Discuss+|The+|role+|of+|The+|sysTem+|modules.




2

, Appendix+|C+|The+|UniversiTy+|Lab:
ConcepTual+|Design+|VerificaTion,+|Logical+|Design,+|and+|ImplemenTa
Tion

The+ | use+ | of+ | sysTem+ | modules+ | can+ | hardly+ | be+ | overemphasized+ | in+ | a+ | daTabase+ | design+ | environ
menT.+ | STress+T| hese+|module+|characTerisTics+|and+|feaTures:

• Modules+|represenT+|subseTs+|of+|The+|daTabase+|model:+|Smaller+|"pieces"+|are+|more+|eas
ily+u
| ndersTood.


• Modules+|are+|self-
conTained+|and+|accomplish+|a+|specific+|sysTem+|funcTion;+|if+|such+|a+|sysTem+|funcTion+|m
usT+|be+|modified,+|oTher+|funcTions+|remain+|unaffecTed.
• Modules+|fiT+|inTo+|a+|modular+|daTabase+|design,+|which+|is+|more+|easily+|modified+|and+|ad
apTed+|To+n| ew+|circumsTances.+|Because+|modificaTion+|efforTs+|are+|focused+|on+|a+|daTab

ase+|subseT,+|producTiviTy+|of+|boTh+|designers+|and+|applicaTion+|developers+|is+|likely+|To+|
be+|enhanced.


Module+|inTerfaces+|musT+|be+|clear+|if+|The+|modules+|are+|expecTed+|To+|work+|well+|wiThin+|The+|overall+|sysTem.




3

, Appendix+|C+|The+|UniversiTy+|Lab:
ConcepTual+|Design+|VerificaTion,+|Logical+|Design,+|and+|ImplemenTa
Tion
Answers To Review QuesTions
+| +| +|




1. Why+|musT+|a+|concepTual+|model+|be+|verified?+|WhaT+|sTeps+|are+|involved+|in+|The+|verificaTion+|process?


The+|verificaTion+|of+|a+|concepTual+|model+|is+|crucial+|To+|a+|successful+|daTabase+|design.+|The+|verific
aTion+|process+|allows+|The+|designer+|To+|check+|The+|accuracy+|of+|The+|daTabase+|design+|by:

• Re-examining+|daTa+|and+|daTa+|TransformaTions.
• Enabling+ | The+ | designer+ | To+ | evaluaTe+ | The+ | design+ | efficiency+ | relaTive+ | To+ | The+ | end
+ | user's+ | and+
s| ysTem's+|design+|goals.


Keep+|in+|mind+|ThaT,+|To+|a+|large+|exTenT,+|The+|besT+|design+|is+|The+|one+|ThaT+|serves+|The+ | end-
user+|requiremenTs+|besT.+|For+|example,+|a+|design+|ThaT+|works+|well+|for+|a+|manufacTuring+|firm+|ma
y+|noT+|fiT+|The+|needs+|of+|a+|markeTing+|research+|firm,+|and+|vice+|versa.



The+|verificaTion+|process+|helps+|The+|designer+|To+|avoid+|implemenTaTion+|problems+|laTer+|by:

• ValidaTing+|The+|model's+|enTiTies.+|(Remember+|The+|minimal+|daTa+|rule.)
• Confirming+|enTiTy+|relaTionships+|and+|eliminaTing+|duplicaTe,+|unnecessary,+|or+|imp
roperly+d
| efined+|relaTionships.


• EliminaTing+|daTa+|redundancies.
• Improving+|The+|model's+|semanTic+|precision+|To+|beTTer+|represenT+|real-world+|operaTions.
• Confirming+|ThaT+|all+|user+|requiremenTs+|(processing,+|performance,+|or+|securiTy)+|are+|meT.


VerificaTion+|is+|a+|conTinuous+|acTiviTy+|in+|any+|daTabase+|design.+|The+|daTabase+|design+|process+|is+|
evoluTionary+|in+|naTure:+|IT+|requires+|The+|conTinuous+|evaluaTion+|of+|The+|developing+|model+|by+|ex
amining+|The+|effecT+|of+|adding+|new+|enTiTies+|and+|by+|confirming+|ThaT+|any+|design+|changes+|enha
nce+|The+|model's+|accuracy.



The+|verificaTion+|process+|requires+|The+|following+|sTeps:



1. IdenTify+|The+|daTabase's+|cenTral+|enTiTy.


The+ | cenTral+ | enTiTy+ | is+ | The+ | mosT+ | imporTanT+ | enTiTy+ | in+ | our+ | daTabase,+ | and+ | mos
T+ | of+ | The+ | oThere
| nTiTies+|depend+|on+|iT.
+




4