Chapter 14 Methodology –
Conceptual Database Design
14.1 Describe the purpose of a design
methodology.
14.2 Describe the main phases involved
database design.
14.3 Identify important factors in the
success of logical database design.
14.4 Discuss the important role played by
users in the process of database design.
14.5 Describe the main objective of
conceptual database design.
14.6 Identify the main steps associated
with conceptual database design.
14.7 How would you identify entity and
relationship types from a user’s requirements specification?
14.8 How would you identify attributes
from a user’s requirements specification and then associate the attributes with
entity or relationship types?
14.9 Describe the purpose of
specialization/generalization of entity types, and discuss why this is an
optional step in conceptual database design.
14.10 How would you check a data model for
redundancy? Give an example to illustrate your answer.
14.11 Discuss why you would want to validate a
conceptual data model and describe two approaches to validating a conceptual
model.
14.12 Identify and describe the purpose of the
documentation generated during conceptual database design.
14.13 Create a local conceptual data model for
the Branch view of DreamHome documented in Appendix A. Compare your ER diagram
with Figure 12.8 and justify any differences found.
14.14 Show that all the query transactions for
the Branch view of DreamHome listed in Appendix A are supported by your local
conceptual data model.
14.15 Provide a user’s requirements
specification for the University Accommodation Office case study documented in
Appendix B.1.
14.16 Create a local conceptual data model for
the one user view. State any assumptions necessary to support your design.
Check that the local conceptual data model supports the required transactions.
14.17 Provide a user’s requirements
specification for the EasyDrive School of Motoring case study documented in
Appendix B.2.
14.18 Create a local conceptual data model for
the one user view. State any assumptions necessary to support your design.
Check that the local conceptual data model supports the required transactions.
14.19 Identify user views for the Medical
Director and Charge Nurse in the Wellmeadows Hospital case study described in
Appendix B.3.
14.20 Provide a user’s requirements
specification for each of these user views.
14.21 Create local conceptual data models for
each of the user views. State any assumptions necessary to support your design.
Chapter 15 Methodology – Logical
Database Design for Relational Model
15.1 Discuss the purpose of logical
database design.
15.2 Describe the types of structures that
are known not to be compatible with the relational model and describe how they
could be removed from a conceptual data model. Give examples to illustrate your
answer.
15.3 Describe the rules for deriving
relations that represent:
(a) strong entity types;
(b) weak entity types;
(c) one-to-many (1:*) binary
relationship types;
(d) one-to-one (1:1) binary
relationship types;
(e) one-to-one (1:1) recursive
relationship types;
(f) superclass/subclass relationship
types;
(g) many-to-many (*:*) binary
relationship types;
(h) complex relationship types;
(i) multi-valued attributes.
15.4 Discuss how the technique of
normalization can be used to validate the logical data model and the relations
derived from the model.
15.5 Discuss two approaches that can be
used to validate that the logical data model is capable of supporting the
transactions required by the user’s view.
15.6 Describe the purpose of integrity
constraints and identify the five main types of constraints.
15.7 Describe the alternative strategies
that can be applied if there exists a child occurrence referencing a parent
occurrence that we wish to delete.
15.8 Identify the tasks typically
associated with merging local logical data models into a global logical model.
15.9 Derive relations for the following
conceptual data model:
The DreamHome case study
15.10 Create a relational schema for the
Branch view of DreamHome based on the conceptual data model produced in Exercise
14.13 and compare your schema with the relations listed in Figure 15.9. Justify
any differences found.
The University Accommodation
Office case study
15.11 Create and validate a local logical data
model from the local conceptual data model for the University Accommodation
Office case study created in Exercise 14.16.
The EasyDrive School of Motoring
case study
15.12 Create and validate a local logical data
model from the local conceptual data model for the EasyDrive School of Motoring
case study created in Exercise 14.18.
The Wellmeadows Hospital case
study
15.13 Create and validate the local logical
data models for each of the local conceptual data models of the Wellmeadows
Hospital case study identified in Exercise 14.21.
15.14 Merge the local data models to create a
global logical data model of the Wellmeadows Hospital case study. State any
assumptions necessary to support your design.
The DreamHome case study
15.10 Create a relational schema for the
Branch view of DreamHome based on the conceptual data model produced in
Exercise 14.13 and compare your schema with the relations listed in Figure
15.9. Justify any differences found.
The University Accommodation
Office case study
15.11 Create and validate a local logical data
model from the local conceptual data model for the University Accommodation
Office case study created in Exercise 14.16.
The EasyDrive School of Motoring
case study
15.12 Create and validate a local logical data
model from the local conceptual data model for the EasyDrive School of Motoring
case study created in Exercise 14.18.
The Wellmeadows Hospital case
study
15.13 Create and validate the local logical
data models for each of the local conceptual data models of the Wellmeadows
Hospital case study identified in Exercise 14.21.
15.14 Merge the local data models to create a
global logical data model of the Wellmeadows Hospital case study. State any
assumptions necessary to support your design.
15.15 Create or update the supporting
documentation for the global logical data model of the Wellmeadows Hospital
case study.
Chapter 16 Methodology –
Physical Database Design for Relational
Databases
16.1 Explain the difference between
conceptual, logical, and physical database design. Why might these tasks be
carried out by different people?
16.2 Describe the inputs and outputs of
physical database design.
16.3 Describe the purpose of the main
steps in the physical design methodology presented in this chapter.
16.4 “One of the main objectives of
physical database design is to store data in an efficient way.” How might
we measure efficiency in this context?
The DreamHome case study
16.5 In Step 5.3, we chose the indexes to
create in Microsoft Access for the query transactions listed in Appendix A for
the Staff view of DreamHome. Choose indexes to create in Microsoft Access for
the query transactions listed in Appendix A for the Branch view of DreamHome.
16.6 Repeat Exercise 16.5 using Oracle as
the target DBMS.
Using the interactions created
above and using the guidelines provided in Section Step 5.3, the student should
propose and justify a number of indexes.
16.7 Create a physical database design for
the logical design of the DreamHome case study (described in Chapter 15) based
on the DBMS that you have access to.
16.8 Implement this physical design for
DreamHome created in 16.7.
The University Accommodation
Office case study
16.9 Based on the logical data model
developed in Exercise 15.11, create a physical database design for the
University Accommodation Office case study (described in Appendix B.1) based on
the DBMS that you have access to.
16.10 Implement the University Accommodation
Office database using the physical design created in 16.9.
The EasyDrive School of Motoring
case study
16.11 Based on the logical data model
developed in Exercise 15.12, create a physical database design for the
EasyDrive School of Motoring case study (described in Appendix B.2) based on
the DBMS that you have access to.
16.12 Implement the EasyDrive School of
Motoring database using the physical design created in 16.11.
The Wellmeadows Hospital case
study
16.13 Based on the global logical data model
developed in Exercise 15.14, create a physical database design for the
Wellmeadows Hospital case study (described in Appendix B.3) based on the DBMS
that you have access to.
16.14 Implement the Wellmeadows Hospital
database using the physical design created in 16.13.
Chapter 17 Methodology – Monitoring and Tuning the Operational System
17.1 Describe the purpose of the main
steps in the physical design methodology presented in this chapter.
17.2 Under what circumstances would you
want to denormalize a logical data model? Use examples to illustrate your
answer.
17.3 Investigate whether your DBMS can
accommodate the two new requirements for the DreamHome case study given in Step
9 of this chapter. If feasible, produce a design for the two requirements and
implement them in your target DBMS.
ScholarMatic: Explanation & Answer
Your ready answer from a verified tutor is just a click away for as little as $14.99
Click Order Now to get 100% Original Answer Customized to your instructions!
