Database Systems Design Implementation And
Management 12th Edition By Coronel Chapter 1-16
SOLUTION MANUAL
TABLES OF CONTENTS
Ch 1: Database Systems
1
,Ch 2: Data Models
Ch 3: The Relational Database Model
Ch 5: Advanced Data Modeling
Ch 6: Normalization of Database Tables
Ch 7: Introduction to Structured Query Language (SQL)
Ch 8: Advanced SQL
Ch 9: Database Design
Ch 10: Transaction Management and Concurrency Control
Ch 11: Database Performance Tuning and Query Optimization
Ch 12: Distributed Database Management Systems
Ch 13: Business Intelligence and Data Warehouses
Ch 14: Big Data Analytics and NoSQL
Ch 15: Database Connectivity and Web Technologies
Ch 16: Database Administration and Security
Discussion Focus
How is a database design verified, and why is such verification necessary?
2
,Use our deTailed answer To quesTion 1 To focus class discussion on
daTabase design verificaTion. STress ThaT The verificaTion process
uses The iniTial ER ṃodel as a coṃṃunicaTion Tool.
The designer ṃay begin The verificaTion process by describing The
organizaTion's operaTions To iTs end users, basing The deTailed
descripTion on The iniTial ER ṃodel. NexT, explain how The operaTions
will be supporTed by The daTabase design. STress ThaT The design ṃusT
supporT The end-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
ṃusT be correcTed?
• Does The ṃodel supporT The end-user requireṃenTs? If noT,
whaT aspecTs of The end-user requireṃenTs have noT been
addressed or have been addressed inadequaTely?
Keep in ṃind ThaT even a ṃodel ThaT perfecTly addresses all iniTially
deTerṃined end user requireṃenTs is likely To need adjusTṃenTs as Those
end users begin To undersTand The raṃificaTions of The daTabase
design's capabiliTies. In ṃany cases, The end users ṃay learn whaT The
organizaTion's processes and procedures acTually are, Thus leading To
new requireṃenTs and The percepTion of new opporTuniTies. The daTabase
designer ṃusT keep such likely developṃenTs in ṃind, especially if
(s)he works as a daTabase design consulTanT. (AnTicipaTion of such
developṃenTs ṃusT be facTored inTo The conTracT negoTiaTions for
consulTing fees.)
Discuss The role of The sysTeṃ ṃodules.
3
, The use of sysTeṃ ṃodules can hardly be overeṃphasized in a daTabase
design environṃenT. STress These ṃodule characTerisTics and feaTures:
• Ṃodules represenT subseTs of The daTabase ṃodel: Sṃaller
"pieces" are ṃore easily undersTood.
• Ṃodules are self-conTained and accoṃplish a specific sysTeṃ
funcTion; if such a sysTeṃ funcTion ṃusT be ṃodified, oTher
funcTions reṃain unaffecTed.
• Ṃodules fiT inTo a ṃodular daTabase design, which is ṃore
easily ṃodified and adapTed To new circuṃsTances. Because
ṃodificaTion efforTs are focused on a daTabase subseT,
producTiviTy of boTh designers and applicaTion developers is
likely To be enhanced.
Ṃodule inTerfaces ṃusT be clear if The ṃodules are expecTed To work well wiThin
The overall sysTeṃ.
4
Management 12th Edition By Coronel Chapter 1-16
SOLUTION MANUAL
TABLES OF CONTENTS
Ch 1: Database Systems
1
,Ch 2: Data Models
Ch 3: The Relational Database Model
Ch 5: Advanced Data Modeling
Ch 6: Normalization of Database Tables
Ch 7: Introduction to Structured Query Language (SQL)
Ch 8: Advanced SQL
Ch 9: Database Design
Ch 10: Transaction Management and Concurrency Control
Ch 11: Database Performance Tuning and Query Optimization
Ch 12: Distributed Database Management Systems
Ch 13: Business Intelligence and Data Warehouses
Ch 14: Big Data Analytics and NoSQL
Ch 15: Database Connectivity and Web Technologies
Ch 16: Database Administration and Security
Discussion Focus
How is a database design verified, and why is such verification necessary?
2
,Use our deTailed answer To quesTion 1 To focus class discussion on
daTabase design verificaTion. STress ThaT The verificaTion process
uses The iniTial ER ṃodel as a coṃṃunicaTion Tool.
The designer ṃay begin The verificaTion process by describing The
organizaTion's operaTions To iTs end users, basing The deTailed
descripTion on The iniTial ER ṃodel. NexT, explain how The operaTions
will be supporTed by The daTabase design. STress ThaT The design ṃusT
supporT The end-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
ṃusT be correcTed?
• Does The ṃodel supporT The end-user requireṃenTs? If noT,
whaT aspecTs of The end-user requireṃenTs have noT been
addressed or have been addressed inadequaTely?
Keep in ṃind ThaT even a ṃodel ThaT perfecTly addresses all iniTially
deTerṃined end user requireṃenTs is likely To need adjusTṃenTs as Those
end users begin To undersTand The raṃificaTions of The daTabase
design's capabiliTies. In ṃany cases, The end users ṃay learn whaT The
organizaTion's processes and procedures acTually are, Thus leading To
new requireṃenTs and The percepTion of new opporTuniTies. The daTabase
designer ṃusT keep such likely developṃenTs in ṃind, especially if
(s)he works as a daTabase design consulTanT. (AnTicipaTion of such
developṃenTs ṃusT be facTored inTo The conTracT negoTiaTions for
consulTing fees.)
Discuss The role of The sysTeṃ ṃodules.
3
, The use of sysTeṃ ṃodules can hardly be overeṃphasized in a daTabase
design environṃenT. STress These ṃodule characTerisTics and feaTures:
• Ṃodules represenT subseTs of The daTabase ṃodel: Sṃaller
"pieces" are ṃore easily undersTood.
• Ṃodules are self-conTained and accoṃplish a specific sysTeṃ
funcTion; if such a sysTeṃ funcTion ṃusT be ṃodified, oTher
funcTions reṃain unaffecTed.
• Ṃodules fiT inTo a ṃodular daTabase design, which is ṃore
easily ṃodified and adapTed To new circuṃsTances. Because
ṃodificaTion efforTs are focused on a daTabase subseT,
producTiviTy of boTh designers and applicaTion developers is
likely To be enhanced.
Ṃodule inTerfaces ṃusT be clear if The ṃodules are expecTed To work well wiThin
The overall sysTeṃ.
4
