Chapter 9 Database Design

Chapter 9
Database Design
Discussion Focus
What is the relationship between a database and an information system, and how does this
relationship have a bearing on database design?
An information system performs three sets of services:
It provides for data collection, storage, and retrieval.
It facilitates the transformation of data into information.
It provides the tools and conditions to manage both data and information.
Basically, a database is a fact (data) repository that serves an information system. If the database is
designed poorly, one can hardly expect that the data/information transformation will be successful, nor is
it reasonable to expect efficient and capable management of data and information.
The transformation of data into information is accomplished through application programs. It is
impossible to produce good information from poor data; and, no matter how sophisticated the
application programs are, it is impossible to use good application programs to overcome the effects of
bad database design. In short: Good database design is the foundation of a successful information
system.
Database design must yield a database that:
Does not fall prey to uncontrolled data duplication, thus preventing data anomalies and the
attendant lack of data integrity.
Is efficient in its provision of data access.
Serves the needs of the information system.
The last point deserves emphasis: even the best-designed database lacks value if it fails to meet
information system objectives. In short, good database designers must pay close attention to the
information system requirements.
Systems design and database design are usually tightly intertwined and are often performed in parallel.
Therefore, database and systems designers must cooperate and coordinate to yield the best possible
information system.
What is the relationship between the SDLC and the DBLC?
The SDLC traces the history (life cycle) of an information system. The DBLC traces the history (life
cycle) of a database system. Since we know that the database serves the information system, it is not
surprising that the two life cycles conform to the same basic phases.
Suggestion: Use Figure 9.13 as the basis for a discussion of the parallel activities.

41

Chapter 9 Database Design

What basic database design strategies exist, and how are such strategies executed?
Suggestion: Use Figure 9.14 as the basis for this discussion.
There are two basic approaches to database design: top-down and bottom-up.
Top-down design begins by identifying the different entity types and the definition of each entity's
attributes. In other words, top-down design:
starts by defining the required data sets and then
defines the data elements for each of those data sets.
Bottom-up design:
first defines the required attributes and then
groups the attributes to form entities.
Although the two methodologies tend to be complementary, database designers who deal with small
databases with relatively few entities, attributes, and transactions tend to emphasize the bottom-up
approach. Database designers who deal with large, complex databases usually find that a primarily
top-down design approach is more appropriate.
In spite of the frequent arguments concerning the best design approach, perhaps the top -down vs.
bottom-up distinction is quite artificial. The text's note is worth repeating:

NOTE
Even if a generally top-down approach is selected, the normalization process that revises
existing table structures is (inevitably) a bottom-up technique. E-R models constitute a topdown process even if the selection of attributes and entities may be described as bottom-up.
Since both the E-R model and normalization techniques form the basis for most designs, the
top-down vs. bottom-up debate may be based on a distinction without a difference.

42

Chapter 9 Database Design

Answers to Review Questions

1. What is an information system? What is its purpose?
An information system is a system that
provides the conditions for data collection, storage, and retrieval
facilitates the transformation of data into information
provides management of both data and information.
An information system is composed of hardware, software (DBMS and applications), the database(s),
procedures, and people.
Good decisions are generally based on good information. Ultimately, the purpose of an information
system is to facilitate good decision making by making relevant and timely information available to
the decision makers.
2. How do systems analysis and systems development fit into a discussion about information
systems?
Both systems analysis and systems development constitute part of the Systems Development Life
Cycle, or SDLC. Systems analysis, phase II of the SDLC, establishes the need for and the extent of an
information system by
Establishing end-user requirements.
Evaluating the existing system.
Developing a logical systems design.
Systems development, based on the detailed systems design found in phase III of the SDLC, yields
the information system. The detailed system specifications are established during the systems design
phase, in which the designer completes the design of all required system processes.
3. What does the acronym SDLC mean, and what does an SDLC portray?
SDLC is the acronym that is used to label the System Development Life Cycle. The SDLC traces the
history of a information system from its inception to its obsolescence. The SDLC is composed of six
phases: planning, analysis, detailed system, design, implementation and maintenance.
4. What does the acronym DBLC mean, and what does a DBLC portray?
DBLC is the acronym that is used to label the Database Life Cycle. The DBLC traces the history of a
database system from its inception to its obsolescence. Since the database constitutes the core of an
information system, the DBLC is concurrent to the SDLC. The DBLC is composed of six phases:
initial study, design, implementation and loading, testing and evaluation, operation, and maintenance
and evolution.

43

Chapter 9 Database Design

5. Discuss the distinction between centralized and decentralized conceptual database design.
Centralized and decentralized design constitute variations on the bottom-up and top-down
approaches we discussed in the third question presented in the discussion focus. Basically, the
centralized approach is best suited to relatively small and simple databases that lend themselves well
to a bird's-eye view of the entire database. Such databases may be designed by a single person or by a
small and informally constituted design team. The company operations and the scope of its problems
are sufficiently limited to enable the designer(s) to perform all of the necessary database design tasks:
1. Define the problem(s).
2. Create the conceptual design.
3. Verify the conceptual design with all user views.
4. Define all system processes and data constraints.
5. Assure that the database design will comply with all achievable end user requirements.
The centralized design procedure thus yields the design summary shown in Figure Q9.5A.

Figure Q9.5A The Centralized Design Procedure

D
A
T
A

Conceptual Model

Conceptual Model Verification

User
Views

System
Processes

Data
Constraints

44

D
I
C
T
I
O
N
A
R
Y

Chapter 9 Database Design

Note that the centralized design approach requires the completion and validation of a single
conceptual design.

NOTE
Use the texts Figures 9.15 and 9.16 to contrast the two design approaches, then use Figure
9.6 to show the procedure flows; demonstrate that such procedure flows are independent of
the degree of centralization.
In contrast, when company operations are spread across multiple operational sites or when the
database has multiple entities that are subject to complex relations, the best approach is often based
on the decentralized design.
Typically, a decentralized design requires that the design task be divided into multiple modules, each
one of which is assigned to a design team. The design team activities are coordinated by the lead
designer, who must aggregate the design teams' efforts.
Since each team focuses on modeling a subset of the system, the definition of boundaries and the
interrelation between data subsets must be very precise. Each team creates a conceptual data model
corresponding to the subset being modeled. Each conceptual model is then verified individually
against the user views, processes, and constraints for each of the modules. After the verification
process has been completed, all modules are integrated in one conceptual model.
Since the data dictionary describes the characteristics of all the objects within the conceptual data
model, it plays a vital role in the integration process. Naturally, after the subsets have been aggregated
into a larger conceptual model, the lead designer must verify that the combined conceptual model is
still able to support all the required transactions. Thus the decentralized design activities may be
summarized as shown in Figure Q8.6B.

45

Chapter 9 Database Design

Figure Q9.6B The Decentralized Design Procedure

DATA COMPONENT

Conceptual
Models

Verification

Subset A

Subset B

Subset C

Views,
Processes,
Constraints

Views,
Processes,
Constraints

Views,
Processes,
Constraints

Aggregation

FINAL CONCEPTUAL MODEL

D
A
T
A
D
I
C
T
I
O
N
A
R
Y

Keep in mind that the aggregation process requires the lead designer to assemble a single model in
which various aggregation problems must be addressed:
synonyms and homonyms. Different departments may know the same object by different names
(synonyms), or they may use the same name to address different objects (homonyms.) The
object may be an entity, an attribute, or a relationship.
entity and entity subclasses. An entity subset may be viewed as a separate entity by one or more
departments. The designer must integrate such subclasses into a higher-level entity.
Conflicting object definitions. Attributes may be recorded as different types (character,
numeric), or different domains may be defined for the same attribute. Constraint definitions, too,
may vary. The designer must remove such conflicts from the model.
6. What is the minimal data rule in conceptual design? Why is it important?
The minimal data rule specifies that all the data defined in the data model are actually required to fit
present and expected future data requirements. This rule may be phrased as All that is needed is

there, and all that is there is needed.

46

Chapter 9 Database Design

7. Discuss the distinction between top-down and bottom-up approaches to database design.
We have addressed this question in detail in the discussion focus segment.
8. What are business rules? Why are they important to a database designer?
Business rules are narrative descriptions of the business policies, procedures, or principles that are
derived from a detailed description of operations. Business rules are particularly valuable to database
designers, because they help define:
Entities
Attributes
Relationships (1:1, 1:M, M:N, expressed through connectivities and cardinalities)
Constraints
To develop an accurate data model, the database designer must have a thorough and complete
understanding of the organization's data requirements. The business rules are very important to the
designer because they enable the designer to fully understand how the business works and what role is
played by data within company operations.

NOTE
Do keep in mind that an ERD cannot always include all the applicable business rules. For
example, although constraints are often crucial, it is often not possible to model them. For
instance, there is no way to model a constraint such as no pilot may be assigned to flight
duties more than ten hours during any 24-hour period.
It is also worth emphasizing that the description of (company) operations must be done in
almost excruciating detail and it must be verified and re-verified. An inaccurate description
of operations yields inaccurate business rules that lead to database designs that are destined
to fail.
9. What is the data dictionary's function in database design?
A good data dictionary provides a precise description of the characteristics of all the entities and
attributes found within the database. The data dictionary thus makes it easier to check for the
existence of synonyms and homonyms, to check whether all attributes exist to support required
reports, to verify appropriate relationship representations, and so on. The data dictionary's contents
are both developed and used during the six DBLC phases:
DATABASE INITIAL STUDY
The basic data dictionary components are developed as the entities and attributes are defined during
this phase.
DATABASE DESIGN
The data dictionary contents are used to verify the database design components: entities, attributes,
and their relationships. The designer also uses the data dictionary to check the database design for
homonyms and synonyms and verifies that the entities and attributes will support all required query
47

Chapter 9 Database Design

and report requirements.
IMPLEMENTATION AND LOADING
The DBMS's data dictionary helps to resolve any remaining attribute definition inconsistencies.
TESTING AND EVALUATION
If problems develop during this phase, the data dictionary contents may be used to help restructure
the basic design components to make sure that they support all required operations.
OPERATION
If the database design still yields (the almost inevitable) operational glitches, the data dictionary may
be used as a quality control device to ensure that operational modifications to the database do not
conflict with existing components.
MAINTENANCE AND EVOLUTION
As users face inevitable changes in information needs, the database may be modified to support those
needs. Perhaps entities, attributes, and relationships must be added, or relationships must be changed.
If new database components are fit into the design, their introduction may produce conflict with
existing components. The data dictionary turns out to be a very useful tool to check whether a
suggested change invites conflicts within the database design and, if so, how such conflicts may be
resolved.
10. What steps are required in the development of an ER diagram? (Hint: See Table 9.1.)
Table 9.1 is reproduced for your convenience.
TABLE 9.1 Developing the Conceptual Model, Using ER Diagrams
STEP
1
2
3
4
5
6
7
8

ACTIVITY
Identify, analyze, and refine the business rules.
Identify the main entities, using the results of Step 1.
Define the relationships among the entities, using the results of Steps 1 and 2.
Define the attributes, primary keys, and foreign keys for each of the entities.
Normalize the entities. (Remember that entities are implemented as tables in an RDBMS.)
Complete the initial ER diagram.
Have the main end users verify the model in Step 6 against the data, information, and
processing requirements.
Modify the ER diagram, using the results of Step 7.

Point out that some of the steps listed in Table 9.1 take place concurrently. And some, such as the
normalization process, can generate a demand for additional entities and/or attributes, thereby causing
the designer to revise the ER model. For example, while identifying two main entities, the designer
might also identify the composite bridge entity that represents the many-to-many relationship between
those two main entities.
11. List and briefly explain the activities involved in the verification of an ER model.

48

Chapter 9 Database Design

Section 9.3.2, Database Design, includes a discussion on verification. In addition, Appendix C,
The University Lab: Conceptual Design Verification, Logical Design, and Implementation, covers
the verification process in detail. The verification process is detailed in the texts Table 9.3,
reproduced here for your convenience.
TABLE 9.3 The ER Model Verification Process
STEP
1
2
3
4
5
6

ACTIVITY
Identify the ER models central entity.
Identify each module and its components.
Identify each modules transaction requirements:
Internal: Updates/Inserts/Deletes/Queries/Reports
External: Module interfaces
Verify all processes against the ER model.
Make all necessary changes suggested in Step 4.
Repeat Steps 25 for all modules.

Keep in mind that the verification process requires the continuous verification of business transactions
as well as system and user requirements. The verification sequence must be repeated for each of the
systems modules.
12. What factors are important in a DBMS software selection?
The selection of DBMS software is critical to the information systems smooth operation.
Consequently, the advantages and disadvantages of the proposed DBMS software should be carefully
studied. To avoid false expectations, the end user must be made aware of the limitations of both the
DBMS and the database.
Although the factors affecting the purchasing decision vary from company to company, some of the
most common are:
Cost. Purchase, maintenance, operational, license, installation, training, and conversion costs.
DBMS features and tools. Some database software includes a variety of tools that facilitate
the application development task. For example, the availability of query by example (QBE),
screen painters, report generators, application generators, data dictionaries, and so on, helps
to create a more pleasant work environment for both the end user and the application
programmer. Database administrator facilities, query facilities, ease of use, performance,
security, concurrency control, transaction processing, and third-party support also influence
DBMS software selection.
Underlying model. Hierarchical, network, relational, object/relational, or object.
Portability. Across platforms, systems, and languages.
DBMS hardware requirements. Processor(s), RAM, disk space, and so on.

Problem Solutions

49

Chapter 9 Database Design

1. The ABC Car Service & Repair Centers are owned by the SILENT car dealer; ABC services
and repairs only SILENT cars. Three ABC Car Service & Repair Centers provide service and
repair for the entire state.
Each of the three centers is independently managed and operated by a shop manager, a
receptionist, and at least eight mechanics. Each center maintains a fully stocked parts
inventory.
Each center also maintains a manual file system in which each cars maintenance history is
kept: repairs made, parts used, costs, service dates, owner, and so on. Files are also kept to
track inventory, purchasing, billing, employees hours, and payroll.
You have been contacted by the manager of one of the centers to design and implement a
computerized system. Given the preceding information, do the following:
a. Indicate the most appropriate sequence of activities by labeling each of the following steps
in the correct order. (For example, if you think that Load the database. is the appropriate
first step, label it 1.)
____
____
____
____
____
____
____
____
____
____
____

Normalize the conceptual model.

Obtain a general description of company operations.
Load the database.
Create a description of each system process.
Test the system.
Draw a data flow diagram and system flowcharts.
Create a conceptual model, using ER diagrams.
Create the application programs.
Interview the mechanics.
Create the file (table) structures.
Interview the shop manager.

The answer to this question may vary slightly from one designer to the next, depending on the
selected design methodology and even on personal designer preferences. Yet, in spite of such
differences, it is possible to develop a common design methodology to permit the development of a
basic decision-making process and the analysis required in designing an information system.
Whatever the design philosophy, a good designer uses a specific and ordered set of steps through
which the database design problem is approached. The steps are generally based on three phases:
analysis, design, and implementation. These phases yield the following activities:
ANALYSIS
1. Interview the shop manager
2. Interview the mechanics
3. Obtain a general description of company operations
4. Create a description of each system process
DESIGN
5. Create a conceptual model, using E-R diagrams
6. 8. Draw a data flow diagram and system flow charts
50

Chapter 9 Database Design

7. Normalize the conceptual model
IMPLEMENTATION
8. Create the table structures
9. Load the database
10. Create the application programs
11. Test the system.
This listing implies that, within each of the three phases, the steps are completed in a specific order.
For example, it would seem reasonable to argue that we must first complete the interviews if we are
to obtain a proper description of the company operations. Similarly, we may argue that a data flow
diagram precedes the creation of the E-R diagram. Nevertheless, the specific tasks and the order in
which they are addressed may vary. Such variations do not matter, as long as the designer bases the
selected procedures on an appropriate design philosophy, such as top-down vs. bottom-up.
Given this discussion, we may present problem 1's solution this way:
__7__ Normalize the conceptual model.
__3__ Obtain a general description of company operations.
__9__ Load the database.
__4__ Create a description of each system process.
_11__ Test the system.
__6__ Draw a data flow diagram and system flow charts.
__5__ Create a conceptual model, using E-R diagrams.
_10__ Create the application programs.
__2__ Interview the mechanics.
__8__ Create the file (table) structures.
__1__ Interview the shop manager.

51

Chapter 9 Database Design

b. Describe the various modules that you believe the system should include.
This question may be addressed in several ways. We suggest the following approach to develop a
system composed of four main modules: Inventory, Payroll, Work order, and Customer.
We have illustrated the Information System's main modules in Figure P9.1B.

Figure P9.1B The ABC Companys IS System Modules

The Inventory module will include the Parts and Purchasing sub-modules. The Payroll Module
will handle all employee and payroll information. The Work order module keeps track of the car
maintenance history and all work orders for maintenance done on a car. The Customer module
keeps track of the billing of the work orders to the customers and of the payments received from
those customers.
c. How will a data dictionary help you develop the system? Give examples.
We have addressed the role of the data dictionary within the DBLC in detail in the answer to
review question 10. Remember that the data dictionary makes it easier to check for the existence
of synonyms and homonyms, to check whether all attributes exist to support required reports, to
verify appropriate relationship representations, and so on. Therefore, the data dictionary's
contents will help us to provide consistency across modules and to evaluate the system's ability to
generate the required reports. In addition, the use of the data dictionary facilitates the creation of
system documentation.

52

Chapter 9 Database Design

d. What general (system) recommendations might you make to the shop manager? (For
example. if the system will be integrated, what modules will be integrated? What benefits
would be derived from such an integrated system? Include several general
recommendations.)
The designer's job is to provide solutions to the main problems found during the initial study.
Clearly, any system is subject to both internal and external constraints. For example, we can safely
assume that the owner of the ABC Car Service and Repair Center has a time frame in mind, not to
mention a spending limitation. As is true in all design work, the designer and the business owner
must prioritize the modules and develop those that yield the greatest benefit within the stated time
and development budget constraints.
Keep in mind that it is always useful to develop a modular system that provides for future
enhancement and expansion. Suppose, for example, that the ABC Car Service & Repair company
management decides to integrate all of its service stations in the state in order to provide better
statewide service. Such integration is likely to yield many benefits: The car history of each car will
be available to any station for cars that have been serviced in more than one location; the
inventory of parts will be on-line, thus allowing parts orders to be placed between service stations;
mechanics can better share tips concerning the solution to car maintenance problems, and so on.
e. What is the best approach to conceptual database design? Why?
Given the nature of this business, the best way to produce this conceptual database design would
be to use a centralized and top-down approach. Keep in mind that the designer must keep the
design sufficiently flexible to make sure that it can accommodate any future integration of this
system with the other service stations in the state.
f. Name and describe at least four reports the system should have. Explain their use. Who will
use those reports?
REPORT 1
Monthly Activity contains a summary of service categories by branch and by month. Such
reports may become the basis for forecasting personnel and stock requirements for each branch
and for each period.
REPORT 2
Mechanic Summary Sheet contains a summary of work hours clocked by each mechanic. This
report would be generated weekly and would be useful for payroll and maintenance personnel
scheduling purposes.
REPORT 3
Monthly Inventory contains a summary of parts in inventory, inventory draw-down, parts
reorder points, and information about the vendors who will provide the parts to be reordered.
This report will be especially useful for inventory management purposes.
REPORT 4
Customer Activity contains a breakdown of customers by location, maintenance activity, current
balances, available credit, and so on. This report would be useful to forecast various service
demand factors, to mail promotional materials, to send maintenance reminders, to keep track of

53

Chapter 9 Database Design

special customer requirements, and so on.
2. Suppose you have been asked to create an information system for a manufacturing plant that
produces nuts and bolts of many shapes, sizes, and functions. What questions would you ask,
and how would the answers to those questions affect the database design?
Basically, all answers to all (relevant) questions help shape the database design. In fact, all information
collected during the initial study and all subsequent phases will have an impact on the database design.
Keep in mind that the information is collected to establish the entities, attributes, and the relationships
among the entities. Specifically, the relationships, connectivities, and cardinalities are shaped by the
business rules that are derived from the information collected by the designer.
Sample questions and their likely impact on the design might be:
Do you want to develop the database for all departments at once, or do you want to design
and implement the database for one department at a time?
How will the design approach affect the design process? (In other words, assess top-down vs.
bottom-up, centralized or decentralized, system scope and boundaries.)
Do you want to develop one module at a time, or do you want an integrated system?
(Inventory, production, shipping, billing, etc.)
Do you want to keep track of the nuts and bolts by lot number, production shift, type, and
department? Impact: conceptual and logical database design.
Do you want to keep track of the suppliers of each batch of raw material used in the
production of the nuts and bolts? Impact: conceptual and logical database design. E-R model.
Do you want to keep track of the customers who received the batches of nuts and bolts?
Impact: conceptual and logical database design. ER model.
What reports will you require, what will be the specific reporting requirements, and to whom
will these reports be distributed?
The answers to such questions affect the conceptual and logical database design, the databases
implementation, its testing, and its subsequent operation.
a. What do you envision the SDLC to be?
The SDLC is not a function of the information collected. Regardless of the extent of the design or
its specific implementation, the SDLC phases remain:

PLANNING
Initial assessment
Feasibility study

ANALYSIS
User requirements
Study of existing systems
Logical system design

DETAILED SYSTEMS DESIGN

Detailed system specifications
54

Chapter 9 Database Design

IMPLEMENTATION
Coding, testing, debugging
Installation, fine-tuning

MAINTENANCE
Evaluation
Maintenance
Enhancements
b. What do you envision the DBLC to be?
As is true for the SDLC, the DBLC is not a function of the kind and extent of the collected
information. Thus, the DBLC phases and their activities remain as shown:

DATABASE INITIAL STUDY

Analyze the company situation
Define problems and constraints
Define objectives
Define scope and boundaries

DATABASE DESIGN
Create the conceptual design
Create the logical design
create the physical design

IMPLEMENTATION AND LOADING

Install the DBMS
Create the database(s)
Load or convert the data

TESTING AND EVALUATION

Test the database
Fine-tune the database
Evaluate the database and its application programs

OPERATION
Produce the required information flow

MAINTENANCE AND EVOLUTION

Introduce changes
Make enhancements
3. Suppose you perform the same functions noted in Problem 2 for a larger warehousing
operation. How are the two sets of procedures similar? How and why are they different?
The development of an information system will differ in the approach and philosophy used. More
precisely, the designer team will probably be formed by a group of system analysts and may decide to
use a decentralized approach to database design.
55

Chapter 9 Database Design

Also, as is true for any organization, the system scope and constraints may be very different for
different systems. Therefore, designers may opt to use different techniques at different stages. For
example, the database initial study phase may include separate studies carried out by separate design
teams at several geographically distant locations. Each of the findings of the design teams will later be
integrated to identify the main problems, solutions, and opportunities that will guide the design and
development of the system.
4. Using the same procedures and concepts employed in Problem 1, how would you create an
information system for the Tiny College example in Chapter 4?
Tiny College is a medium-sized educational institution that uses many database-intensive operations,
such as student registration, academic administration, inventory management, and payroll. To create
an information system, first perform an initial database study to determine the information system's
objectives.
Next, study Tiny College's operations and processes (flow of data) to identify the main problems,
constraints, and opportunities. A precise definition of the main problems and constraints will enable
the designer to make sure that the design improves Tiny College's operational efficiency. An
improvement in operational efficiency is likely to create opportunities to provide new services that
will enhance Tiny College's competitive position.
After the initial database study is done and the alternative solutions are presented, the end users
ultimately decide which one of the probable solutions is most appropriate for Tiny College. Keep in
mind that the development of a system this size will probably involve people who have quite different
backgrounds. For example, it is likely that the designer must work with people who play a managerial
role in communications and local area networks, as well as with the "troops in the trenches" such as
programmers and system operators. The designer should, therefore, expect that there will be a wide
range of opinions concerning the proposed system's features. It is the designer's job to reconcile the
many (and often conflicting) views of the "ideal" system.
Once a proposed solution has been agreed upon, the designer(s) may determine the proposed system's
scope and boundaries. We are then able to begin the design phase. As the design phase begins, keep
in mind that Tiny College's information system is likely to be used by many users (20 to 40 minimum)
who are located on distant sites across campus. Therefore, the designer must consider a range of
communication issues involving the use of such technologies as local area networks. These
technologies must be considered as the database designer(s) begin to develop the structure of the
database to be implemented.
The remaining development work conforms to the SDLC and the DBLC phases. Special attention
must be given to the system design's implementation and testing to ensure that all the system modules
interface properly.
Finally, the designer(s) must provide all the appropriate system documentation and ensure that all
appropriate system maintenance procedures (periodic backups, security checks, etc.) are in place to
ensure the system's proper operation.
Keep in mind that two very important issues in a university-wide system are end-user training and
56

Chapter 9 Database Design

support. Therefore, the system designer(s) must make sure that all end users know the system and
know how it is to be used to enjoy its benefits. In other words, make sure that end-user support
programs are in place when the system becomes operational.
5. Write the proper sequence of activities in the design of a video rental database. (The initial
ERD was shown in Figure 9.7.) The design must support all rental activities, customer payment
tracking, and employee work schedules, as well as track which employees checked out the
videos to the customers. After you finish writing the design activity sequence, complete the ERD
to ensure that the database design can be successfully implemented. (Make sure that the design is
normalized properly and that it can support the required transactions.
Given its level of detail and (relative) complexity, this problem would make an excellent class project.
Use the chapters coverage of the database life cycle (DBLC) as the procedural template. The texts
Figure 9.3 is particularly useful as a procedural map for this problems solution and Figure 9.6
provides a more detailed view of the database designs procedural flow. Make sure that the students
review section 9.4.2, Database Design, before they attempt to produce the problem solution.
Appendix B, The University Lab: Conceptual Design, and Appendix C The University Lab:
Conceptual Design Verification, Logical Design, and Implementation show a very detailed example
of the procedures required to deliver a completed database. You will find a more detailed video rental
database problem description in Appendix B, problem 4. This problem requires the completion of the
initial database design. The solution is shown in this manuals Appendix B coverage. This design is
verified in Appendix C, Problem 2.
The Visio Professional files for the initial and verified designs are located on your instructors CD.
Select the FigB-P04a-The-Initial-Crows-Foot-ERD-for-the-Video-Rental-Store.vsd file to see the
initial design. Select the Fig-C-P02a-The-Revised-Video-Rental-Crows-Foot-ERD.vsd file to see
the verified design.

57