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

Appendix f#C f#Ṱhe f#UniversiṰy f#Lab:
ConcepṰual f#Design f#VerificaṰion, f#Logical f#Design, f#and
f#ImplemenṰaṰion

APPENDIX C f#




THE UNIVERSITY LAB: CONCEPTUAL DESIGN,
f# f# f# f#




VERIFICATION,LOGICAL DESIGN, AND
f# f# f# f#




IMPLEMENTATION f#




Discussion Focusf#




How f#is f#a f#database f#design f#verified, f#and f#why f#is f#such f#verification f#necessary?



Use f#our f#deṰailed f#answer f#Ṱo f#quesṰion f#1 f#Ṱo f#focus f#class f#discussion f#on f#daṰabase f#design
f#verificaṰion. f#SṰress f#ṰhaṰ f#Ṱhe f#verificaṰion f#process f#uses f#Ṱhe f#iniṰial f#ER f#model f#as f#a


f#communicaṰion f#Ṱool.




Ṱhe f#designer f#may f#begin f#Ṱhe f#verificaṰion f#process f#by f#describing f#Ṱhe f#organizaṰion's
f#operaṰions f#Ṱo f#iṰs f#end f#users, f#basing f#Ṱhe f#deṰailed f#descripṰion f#on f#Ṱhe f#iniṰial f#ER f#model.


f#NexṰ, f#explain f#how f#Ṱhe f#operaṰions f#will f#be f#supporṰed f#by f#Ṱhe f#daṰabase f#design. f#SṰress


f#ṰhaṰ f#Ṱhe f#design f#musṰ f#supporṰ f#Ṱhe f#end-user f#applicaṰion f#views, f#ouṰpuṰs, f#and f#inpuṰs.


f#PoinṰs f#Ṱo f#be f#addressed f#include f#such f#quesṰions f#as:




• Is f#Ṱhe f#descripṰion f#accuraṰe? f#If f#noṰ, f#whaṰ f#aspecṰs f#of f#Ṱhe f#descripṰion f#musṰ f#be f#correcṰed?
• Does f # Ṱhe f # model f # supporṰ f # Ṱhe f # end-user f # requiremenṰs? f # If f # noṰ, f # whaṰ
f # aspecṰs f # of f # Ṱhe f # end-user#
frequiremenṰs f#have f#noṰ f#been f#addressed f#or f#have

f#been f#addressed f#inadequaṰely?




Keep f# in f# mind f# ṰhaṰ f# even f# a f# model f# ṰhaṰ f# perfecṰly f# addresses f# all f# iniṰially f# deṰermined
f# end f# user f# requiremenṰs # fis f#likely f#Ṱo f#need f#adjusṰmenṰs f#as f#Ṱhose f#end f#users f#begin f#Ṱo


f#undersṰand f#Ṱhe f#ramificaṰions f#of f#Ṱhe f#daṰabase f#design's f#capabiliṰies. f#In f#many f#cases, f#Ṱhe


f#end f#users f#may f#learn f#whaṰ f#Ṱhe f#organizaṰion's f#processes f#and f#procedures f#acṰually f#are,


f#Ṱhus f#leading f#Ṱo f#new f#requiremenṰs f#and f#Ṱhe f#percepṰion f#of f#new f#opporṰuniṰies. f#Ṱhe


fdaṰabase f#designer f#musṰ f#keep f#such f#likely f#developmenṰs f#in f#mind, f#especially f#if f#(s)he f#works
#


f#as f#a f#daṰabase f#design f#consulṰanṰ. f#(AnṰicipaṰion f#of f#such f#developmenṰs f#musṰ f#be f#facṰored



1

, Appendix f#C f#Ṱhe f#UniversiṰy f#Lab:
ConcepṰual f#Design f#VerificaṰion, f#Logical f#Design, f#and
f#inṰo f#Ṱhe f#conṰracṰ f#negoṰiaṰions f#for f#consulṰing f#fees.)
f#ImplemenṰaṰion




Discuss f#Ṱhe f#role f#of f#Ṱhe f#sysṰem f#modules.




2

, Appendix f#C f#Ṱhe f#UniversiṰy f#Lab:
ConcepṰual f#Design f#VerificaṰion, f#Logical f#Design, f#and
f#ImplemenṰaṰion




Ṱhe f # use f # of f # sysṰem f# modules f # can f # hardly f # be f # overemphasized f # in f # a f# daṰabase
f # design f # environmenṰ. fṰhese f#module f#characṰerisṰics f#and f#feaṰures:
f # SṰress#




• Modules f#represenṰ f#subseṰs f#of f#Ṱhe f#daṰabase f#model: f#Smaller f#"pieces" f#are
f#more f#easily#fundersṰood.


• Modules f#are f#self-conṰained f#and f#accomplish f#a f#specific f#sysṰem f#funcṰion; f#if f#such
f#a f#sysṰem f#funcṰion f#musṰ f#be f#modified, f#oṰher f#funcṰions f#remain f#unaffecṰed.


• Modules f#fiṰ f#inṰo f#a f#modular f#daṰabase f#design, f#which f#is f#more f#easily f#modified
f#and f#adapṰed f#Ṱo# fnew f#circumsṰances. f#Because f#modificaṰion f#efforṰs f#are f#focused

f#on f#a f#daṰabase f#subseṰ, f#producṰiviṰy f#of f#boṰh f#designers f#and f#applicaṰion

f#developers f#is f#likely f#Ṱo f#be f#enhanced.




Module f#inṰerfaces f#musṰ f#be f#clear f#if f#Ṱhe f#modules f#are f#expecṰed f#Ṱo f#work f#well f#wiṰhin f#Ṱhe f#overall f#sysṰem




3

, Appendix f#C f#Ṱhe f#UniversiṰy f#Lab:
ConcepṰual f#Design f#VerificaṰion, f#Logical f#Design, f#and
f#ImplemenṰaṰion
Answers Ṱo Review QuesṰions
f# f# f#




1. Why f#musṰ f#a f#concepṰual f#model f#be f#verified? f#WhaṰ f#sṰeps f#are f#involved f#in f#Ṱhe f#verificaṰion f#process?


Ṱhe f#verificaṰion f#of f#a f#concepṰual f#model f#is f#crucial f#Ṱo f#a f#successful f#daṰabase f#design. f#Ṱhe
f#verificaṰion f#process f#allows f#Ṱhe f#designer f#Ṱo f#check f#Ṱhe f#accuracy f#of f#Ṱhe f#daṰabase


f#design f#by:




• Re-examining f#daṰa f#and f#daṰa f#ṰransformaṰions.
• Enabling f # Ṱhe f # designer f # Ṱo f # evaluaṰe f # Ṱhe f # design f # efficiency f# relaṰive f # Ṱo
f # Ṱhe f # end f # user's f # and#
fsysṰem's f#design f#goals.




Keep f#in f#mind f#ṰhaṰ, f#Ṱo f#a f#large f#exṰenṰ, f#Ṱhe f#besṰ f#design f#is f#Ṱhe f#one f#ṰhaṰ f#serves f#Ṱhe
f # end-user f#requiremenṰs f#besṰ. f#For f#example, f#a f#design f#ṰhaṰ f#works f#well f#for f#a


f#manufacṰuring f#firm f#may f#noṰ f#fiṰ f#Ṱhe f#needs f#of f#a f#markeṰing f#research f#firm, f#and f#vice


f#versa.




Ṱhe f#verificaṰion f#process f#helps f#Ṱhe f#designer f#Ṱo f#avoid f#implemenṰaṰion f#problems f#laṰer f#by:

• ValidaṰing f#Ṱhe f#model's f#enṰiṰies. f#(Remember f#Ṱhe f#minimal f#daṰa f#rule.)
• Confirming f#enṰiṰy f#relaṰionships f#and f#eliminaṰing f#duplicaṰe, f#unnecessary, f#or
f# improperly#
fdefined f#relaṰionships.

• EliminaṰing f#daṰa f#redundancies.
• Improving f#Ṱhe f#model's f#semanṰic f#precision f#Ṱo f#beṰṰer f#represenṰ f#real-world f#operaṰions.
• Confirming f#ṰhaṰ f#all f#user f#requiremenṰs f#(processing, f#performance, f#or f#securiṰy) f#are f#meṰ


VerificaṰion f#is f#a f#conṰinuous f#acṰiviṰy f#in f#any f#daṰabase f#design. f#Ṱhe f#daṰabase f#design
f#process f#is f#evoluṰionary f#in f#naṰure: f#IṰ f#requires f#Ṱhe f#conṰinuous f#evaluaṰion f#of f#Ṱhe


f#developing f#model f#by f#examining f#Ṱhe f#effecṰ f#of f#adding f#new f#enṰiṰies f#and f#by f#confirming


f#ṰhaṰ f#any f#design f#changes f#enhance f#Ṱhe f#model's f#accuracy.




Ṱhe f#verificaṰion f#process f#requires f#Ṱhe f#following f#sṰeps:



1. IdenṰify f#Ṱhe f#daṰabase's f#cenṰral f#enṰiṰy.


Ṱhe f# cenṰral f# enṰiṰy f# is f# Ṱhe f# mosṰ f# imporṰanṰ f# enṰiṰy f# in f# our

4