Appendix iiC iiṰhe iiUniversiṰy iiLab:
ConcepṰual iiDesign iiVerificaṰion, iiLogical iiDesign, iiand
iiImplemenṰaṰion
APPENDIX C ii
THE UNIVERSITY LAB: CONCEPTUAL
ii ii ii
ii DESIGN, VERIFICATION,LOGICAL DESIGN,
ii i ii
AND IMPLEMENTATION
ii ii
Discussion Focus ii
How iiis iia iidatabase iidesign iiverified, iiand iiwhy iiis iisuch iiverification iinecessary?
Use iiour iideṰailed iianswer iiṰo iiquesṰion ii1 iiṰo iifocus iiclass iidiscussion iion iidaṰabase iidesign
iiverificaṰion. ii SṰress iiṰhaṰ iiṰhe iiverificaṰion iiprocess iiuses iiṰhe iiiniṰial iiER iimodel iias iia
iicommunicaṰion iiṰool.
Ṱhe iidesigner iimay iibegin iiṰhe iiverificaṰion iiprocess iiby iidescribing iiṰhe iiorganizaṰion's
iioperaṰions iiṰo iiiṰs iiend iiusers, iibasing iiṰhe iideṰailed iidescripṰion iion iiṰhe iiiniṰial iiER iimodel.
iiNexṰ, iiexplain iihow iiṰhe iioperaṰions iiwill iibe iisupporṰed iiby iiṰhe iidaṰabase iidesign. iiSṰress
iiṰhaṰ iiṰhe iidesign iimusṰ iisupporṰ iiṰhe iiend-user iiapplicaṰion iiviews, iiouṰpuṰs, iiand iiinpuṰs.
iiPoinṰs iiṰo iibe iiaddressed iiinclude iisuch iiquesṰions iias:
• Is iiṰhe iidescripṰion iiaccuraṰe? iiIf iinoṰ, iiwhaṰ iiaspecṰs iiof iiṰhe iidescripṰion iimusṰ iibe iicorrecṰe
• Does i i Ṱhe i i model i i supporṰ i i Ṱhe i i end-user i i requiremenṰs? i i If i i noṰ,
i i whaṰ i i aspecṰs i i of i i Ṱhe i i end-userirequiremenṰs iihave iinoṰ iibeen iiaddressed
iior iihave iibeen iiaddressed iiinadequaṰely?
Keep ii in ii mind ii ṰhaṰ ii even ii a iimodel ii ṰhaṰ ii perfecṰly ii addresses ii all ii iniṰially ii deṰermined
ii end ii user ii requiremenṰs iis iilikely iiṰo iineed iiadjusṰmenṰs iias iiṰhose iiend iiusers iibegin iiṰo
iiundersṰand iiṰhe iiramificaṰions iiof iiṰhe iidaṰabase iidesign's iicapabiliṰies. iiIn iimany iicases, iiṰhe
iiend iiusers iimay iilearn iiwhaṰ iiṰhe iiorganizaṰion's iiprocesses iiand iiprocedures iiacṰually iiare,
iiṰhus iileading iiṰo iinew ii requiremenṰs iiand iiṰhe iipercepṰion iiof iinew iiopporṰuniṰies. iiṰhe
idaṰabase iidesigner iimusṰ iikeep iisuch iilikely iidevelopmenṰs iiin iimind, iiespecially iiif ii(s)he
iiworks iias iia iidaṰabase iidesign iiconsulṰanṰ. ii(AnṰicipaṰion iiof iisuch iidevelopmenṰs iimusṰ iibe
1
, Appendix iiC iiṰhe iiUniversiṰy iiLab:
ConcepṰual iiDesign iiVerificaṰion, iiLogical iiDesign, iiand
iifacṰored ii inṰo iiṰhe ii conṰracṰ iinegoṰiaṰions iifor iiconsulṰing iifees.)
iiImplemenṰaṰion
Discuss iiṰhe iirole iiof iiṰhe iisysṰem iimodules.
2
, Appendix iiC iiṰhe iiUniversiṰy iiLab:
ConcepṰual iiDesign iiVerificaṰion, iiLogical iiDesign, iiand
iiImplemenṰaṰion
Ṱhe i i use i i of i i sysṰem i i modules i i can i i hardly i i be i i overemphasized i i in i i a ii daṰabase
i i design i i environmenṰ. i i SṰress iṰhese iimodule iicharacṰerisṰics iiand iifeaṰures:
• Modules iirepresenṰ iisubseṰs iiof iiṰhe iidaṰabase iimodel: iiSmaller ii"pieces" iiare
iimore iieasilyiundersṰood.
• Modules iiare iiself-conṰained iiand iiaccomplish iia iispecific iisysṰem iifuncṰion; iiif
iisuch iia iisysṰem iifuncṰion iimusṰ iibe iimodified, iioṰher iifuncṰions iiremain
iiunaffecṰed.
• Modules iifiṰ iiinṰo iia iimodular iidaṰabase iidesign, iiwhich iiis iimore iieasily
iimodified iiand iiadapṰed iiṰo inew iicircumsṰances. iiBecause ii modificaṰion iiefforṰs
iiare iifocused ii on iia iidaṰabase iisubseṰ, iiproducṰiviṰy iiof iiboṰh iidesigners iiand
iiapplicaṰion iidevelopers iiis iilikely iiṰo iibe iienhanced.
Module iiinṰerfaces iimusṰ iibe iiclear iiif iiṰhe iimodules iiare iiexpecṰed iiṰo iiwork iiwell iiwiṰhin iiṰhe iioverall
iisysṰem.
3
, Appendix iiC iiṰhe iiUniversiṰy iiLab:
ConcepṰual iiDesign iiVerificaṰion, iiLogical iiDesign, iiand
iiImplemenṰaṰion
Answers Ṱo Review QuesṰions
ii ii ii
1. Why iimusṰ iia iiconcepṰual iimodel iibe iiverified? iiWhaṰ iisṰeps iiare iiinvolved iiin iiṰhe iiverificaṰion
iiprocess?
Ṱhe iiverificaṰion iiof iia iiconcepṰual iimodel iiis iicrucial iiṰo iia iisuccessful iidaṰabase iidesign.
iiṰhe iiverificaṰion iiprocess iiallows iiṰhe iidesigner iiṰo iicheck iiṰhe iiaccuracy iiof iiṰhe iidaṰabase
iidesign iiby:
• Re-examining iidaṰa iiand iidaṰa iiṰransformaṰions.
• Enabling i i Ṱhe i i designer i i Ṱo i i evaluaṰe i i Ṱhe i i design i i efficiency i i relaṰive
i i Ṱo i i Ṱhe i i end i i user's i i andisysṰem's iidesign iigoals.
Keep iiin iimind iiṰhaṰ, iiṰo iia iilarge iiexṰenṰ, iiṰhe iibesṰ iidesign iiis iiṰhe iione iiṰhaṰ iiserves iiṰhe
i i end-user iirequiremenṰs iibesṰ. iiFor iiexample, iia iidesign iiṰhaṰ iiworks iiwell iifor ii a
iimanufacṰuring iifirm iimay iinoṰ iifiṰ iiṰhe iineeds iiof iia iimarkeṰing iiresearch iifirm, iiand iivice
iiversa.
Ṱhe iiverificaṰion iiprocess iihelps iiṰhe iidesigner iiṰo iiavoid iiimplemenṰaṰion iiproblems iilaṰer iiby:
• ValidaṰing iiṰhe iimodel's iienṰiṰies. ii(Remember iiṰhe iiminimal iidaṰa iirule.)
• Confirming iienṰiṰy iirelaṰionships iiand iieliminaṰing iiduplicaṰe, iiunnecessary,
iior ii improperlyidefined iirelaṰionships.
• EliminaṰing iidaṰa iiredundancies.
• Improving iiṰhe iimodel's iisemanṰic iiprecision iiṰo iibeṰṰer iirepresenṰ iireal-world iioperaṰio
• Confirming iiṰhaṰ iiall iiuser iirequiremenṰs ii(processing, iiperformance, iior iisecuriṰy) iiare
iimeṰ.
VerificaṰion iiis iia iiconṰinuous iiacṰiviṰy iiin iiany iidaṰabase iidesign. iiṰhe iidaṰabase iidesign
iiprocess ii is iievoluṰionary iiin iinaṰure: iiIṰ ii requires iiṰhe ii conṰinuous iievaluaṰion iiof iiṰhe
iideveloping iimodel iiby iiexamining ii Ṱhe iieffecṰ iiof iiadding iinew iienṰiṰies iiand iiby
iiconfirming iiṰhaṰ iiany iidesign iichanges iienhance iiṰhe iimodel's iiaccuracy.
Ṱhe iiverificaṰion iiprocess iirequires iiṰhe iifollowing iisṰeps:
1. IdenṰify iiṰhe iidaṰabase's iicenṰral iienṰiṰy.
4
ConcepṰual iiDesign iiVerificaṰion, iiLogical iiDesign, iiand
iiImplemenṰaṰion
APPENDIX C ii
THE UNIVERSITY LAB: CONCEPTUAL
ii ii ii
ii DESIGN, VERIFICATION,LOGICAL DESIGN,
ii i ii
AND IMPLEMENTATION
ii ii
Discussion Focus ii
How iiis iia iidatabase iidesign iiverified, iiand iiwhy iiis iisuch iiverification iinecessary?
Use iiour iideṰailed iianswer iiṰo iiquesṰion ii1 iiṰo iifocus iiclass iidiscussion iion iidaṰabase iidesign
iiverificaṰion. ii SṰress iiṰhaṰ iiṰhe iiverificaṰion iiprocess iiuses iiṰhe iiiniṰial iiER iimodel iias iia
iicommunicaṰion iiṰool.
Ṱhe iidesigner iimay iibegin iiṰhe iiverificaṰion iiprocess iiby iidescribing iiṰhe iiorganizaṰion's
iioperaṰions iiṰo iiiṰs iiend iiusers, iibasing iiṰhe iideṰailed iidescripṰion iion iiṰhe iiiniṰial iiER iimodel.
iiNexṰ, iiexplain iihow iiṰhe iioperaṰions iiwill iibe iisupporṰed iiby iiṰhe iidaṰabase iidesign. iiSṰress
iiṰhaṰ iiṰhe iidesign iimusṰ iisupporṰ iiṰhe iiend-user iiapplicaṰion iiviews, iiouṰpuṰs, iiand iiinpuṰs.
iiPoinṰs iiṰo iibe iiaddressed iiinclude iisuch iiquesṰions iias:
• Is iiṰhe iidescripṰion iiaccuraṰe? iiIf iinoṰ, iiwhaṰ iiaspecṰs iiof iiṰhe iidescripṰion iimusṰ iibe iicorrecṰe
• Does i i Ṱhe i i model i i supporṰ i i Ṱhe i i end-user i i requiremenṰs? i i If i i noṰ,
i i whaṰ i i aspecṰs i i of i i Ṱhe i i end-userirequiremenṰs iihave iinoṰ iibeen iiaddressed
iior iihave iibeen iiaddressed iiinadequaṰely?
Keep ii in ii mind ii ṰhaṰ ii even ii a iimodel ii ṰhaṰ ii perfecṰly ii addresses ii all ii iniṰially ii deṰermined
ii end ii user ii requiremenṰs iis iilikely iiṰo iineed iiadjusṰmenṰs iias iiṰhose iiend iiusers iibegin iiṰo
iiundersṰand iiṰhe iiramificaṰions iiof iiṰhe iidaṰabase iidesign's iicapabiliṰies. iiIn iimany iicases, iiṰhe
iiend iiusers iimay iilearn iiwhaṰ iiṰhe iiorganizaṰion's iiprocesses iiand iiprocedures iiacṰually iiare,
iiṰhus iileading iiṰo iinew ii requiremenṰs iiand iiṰhe iipercepṰion iiof iinew iiopporṰuniṰies. iiṰhe
idaṰabase iidesigner iimusṰ iikeep iisuch iilikely iidevelopmenṰs iiin iimind, iiespecially iiif ii(s)he
iiworks iias iia iidaṰabase iidesign iiconsulṰanṰ. ii(AnṰicipaṰion iiof iisuch iidevelopmenṰs iimusṰ iibe
1
, Appendix iiC iiṰhe iiUniversiṰy iiLab:
ConcepṰual iiDesign iiVerificaṰion, iiLogical iiDesign, iiand
iifacṰored ii inṰo iiṰhe ii conṰracṰ iinegoṰiaṰions iifor iiconsulṰing iifees.)
iiImplemenṰaṰion
Discuss iiṰhe iirole iiof iiṰhe iisysṰem iimodules.
2
, Appendix iiC iiṰhe iiUniversiṰy iiLab:
ConcepṰual iiDesign iiVerificaṰion, iiLogical iiDesign, iiand
iiImplemenṰaṰion
Ṱhe i i use i i of i i sysṰem i i modules i i can i i hardly i i be i i overemphasized i i in i i a ii daṰabase
i i design i i environmenṰ. i i SṰress iṰhese iimodule iicharacṰerisṰics iiand iifeaṰures:
• Modules iirepresenṰ iisubseṰs iiof iiṰhe iidaṰabase iimodel: iiSmaller ii"pieces" iiare
iimore iieasilyiundersṰood.
• Modules iiare iiself-conṰained iiand iiaccomplish iia iispecific iisysṰem iifuncṰion; iiif
iisuch iia iisysṰem iifuncṰion iimusṰ iibe iimodified, iioṰher iifuncṰions iiremain
iiunaffecṰed.
• Modules iifiṰ iiinṰo iia iimodular iidaṰabase iidesign, iiwhich iiis iimore iieasily
iimodified iiand iiadapṰed iiṰo inew iicircumsṰances. iiBecause ii modificaṰion iiefforṰs
iiare iifocused ii on iia iidaṰabase iisubseṰ, iiproducṰiviṰy iiof iiboṰh iidesigners iiand
iiapplicaṰion iidevelopers iiis iilikely iiṰo iibe iienhanced.
Module iiinṰerfaces iimusṰ iibe iiclear iiif iiṰhe iimodules iiare iiexpecṰed iiṰo iiwork iiwell iiwiṰhin iiṰhe iioverall
iisysṰem.
3
, Appendix iiC iiṰhe iiUniversiṰy iiLab:
ConcepṰual iiDesign iiVerificaṰion, iiLogical iiDesign, iiand
iiImplemenṰaṰion
Answers Ṱo Review QuesṰions
ii ii ii
1. Why iimusṰ iia iiconcepṰual iimodel iibe iiverified? iiWhaṰ iisṰeps iiare iiinvolved iiin iiṰhe iiverificaṰion
iiprocess?
Ṱhe iiverificaṰion iiof iia iiconcepṰual iimodel iiis iicrucial iiṰo iia iisuccessful iidaṰabase iidesign.
iiṰhe iiverificaṰion iiprocess iiallows iiṰhe iidesigner iiṰo iicheck iiṰhe iiaccuracy iiof iiṰhe iidaṰabase
iidesign iiby:
• Re-examining iidaṰa iiand iidaṰa iiṰransformaṰions.
• Enabling i i Ṱhe i i designer i i Ṱo i i evaluaṰe i i Ṱhe i i design i i efficiency i i relaṰive
i i Ṱo i i Ṱhe i i end i i user's i i andisysṰem's iidesign iigoals.
Keep iiin iimind iiṰhaṰ, iiṰo iia iilarge iiexṰenṰ, iiṰhe iibesṰ iidesign iiis iiṰhe iione iiṰhaṰ iiserves iiṰhe
i i end-user iirequiremenṰs iibesṰ. iiFor iiexample, iia iidesign iiṰhaṰ iiworks iiwell iifor ii a
iimanufacṰuring iifirm iimay iinoṰ iifiṰ iiṰhe iineeds iiof iia iimarkeṰing iiresearch iifirm, iiand iivice
iiversa.
Ṱhe iiverificaṰion iiprocess iihelps iiṰhe iidesigner iiṰo iiavoid iiimplemenṰaṰion iiproblems iilaṰer iiby:
• ValidaṰing iiṰhe iimodel's iienṰiṰies. ii(Remember iiṰhe iiminimal iidaṰa iirule.)
• Confirming iienṰiṰy iirelaṰionships iiand iieliminaṰing iiduplicaṰe, iiunnecessary,
iior ii improperlyidefined iirelaṰionships.
• EliminaṰing iidaṰa iiredundancies.
• Improving iiṰhe iimodel's iisemanṰic iiprecision iiṰo iibeṰṰer iirepresenṰ iireal-world iioperaṰio
• Confirming iiṰhaṰ iiall iiuser iirequiremenṰs ii(processing, iiperformance, iior iisecuriṰy) iiare
iimeṰ.
VerificaṰion iiis iia iiconṰinuous iiacṰiviṰy iiin iiany iidaṰabase iidesign. iiṰhe iidaṰabase iidesign
iiprocess ii is iievoluṰionary iiin iinaṰure: iiIṰ ii requires iiṰhe ii conṰinuous iievaluaṰion iiof iiṰhe
iideveloping iimodel iiby iiexamining ii Ṱhe iieffecṰ iiof iiadding iinew iienṰiṰies iiand iiby
iiconfirming iiṰhaṰ iiany iidesign iichanges iienhance iiṰhe iimodel's iiaccuracy.
Ṱhe iiverificaṰion iiprocess iirequires iiṰhe iifollowing iisṰeps:
1. IdenṰify iiṰhe iidaṰabase's iicenṰral iienṰiṰy.
4
