Choose a database application with which you are familiar. Design a schema
and show a sample database for that application, using the notation of Fig-
ures 1.2 and 2.1. What types of additional information and constraints
would you like to represent in the schema? Think of several users of your
database, and design a view for each.
Think of different users for the database shown in Figure 1.2. What types of
applications would each user need? To which user category would each
belong, and what type of interface would each need?
If you were designing a Web-based system to make airline reservations and se
airline tickets, which DBMS architecture would you choose from Section 2.5
Why? Why would the other architectures not be a good choice?
Consider Figure 2.1. In addition to constraints relating the values of col-
umns in one table to columns in another table, there are also constraints that
impose restrictions on values in a column or a combination of columns
within a table. One such constraint dictates that a column or a group of col-
umns must be unique across all rows in the table. For example, in the
STUDENT table, the Student number column must be unique (to prevent two
different students from having the same Student number). Identify the col-
umn or the group of columns in the other tables that must be unique across
all rows in the table.