Scribd
Upload
157 views6 pages

7th Assessment

The document contains three questions regarding database design and entity-relationship modeling. Question One asks to extract requirements and constraints from an ER diagram of an airline reservations system. Question Two asks to specify all entity types and relationships that could describe a general database system and environment. Question Three asks to design an ER schema to track information about votes in the U.S. House of Representatives.

Uploaded by

muhrathani4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
157 views6 pages

7th Assessment

The document contains three questions regarding database design and entity-relationship modeling. Question One asks to extract requirements and constraints from an ER diagram of an airline reservations system. Question Two asks to specify all entity types and relationships that could describe a general database system and environment. Question Three asks to design an ER schema to track information about votes in the U.S. House of Representatives.

Uploaded by

muhrathani4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

7th Week Assessment

Advanced Database
Question One: 5 marks (ILOs 2.1,2.2)
Consider the ER diagram in Figure 3.21, which shows a simplified schema for an airline
reservations system. Extract from the ER diagram the requirements and constraints that
produced this schema. Try to be as precise as possible in your requirements and
constraints specification.

Page 1 of 6
Question Two: 5 marks (ILO 1.2)
In Chapters 1 and 2, we discussed the database environment and database users. We
can consider many entity types to describe such an environment, such as DBMS, stored
database, DBA, and catalog/data dictionary. Try to specify all the entity types that can
fully describe a database system and its environment; then specify the relationship
types among them, and draw an ER diagram to describe such a general database
environment.
Question Three: 5 marks (ILO 3.1)
Design an ER schema for keeping track of information about votes taken in the U.S.
House of Representatives during the current two-year congressional session. The
database needs to keep track of each U.S. STATE’s Name (e.g., ‘Texas’, ‘New York’,
‘California’) and include the Region of the state (whose domain is {‘Northeast’, ‘Midwest’,
‘Southeast’, ‘Southwest’, ‘West’}). Each CONGRESS_PERSON in the House of
Representatives is described by his or her Name, plus the District represented, the
Start_date when the congressperson was first elected, and the political Party to which he
or she belongs (whose domain is {‘Republican’, ‘Democrat’, ‘Independent’, ‘Other’}). The
database keeps track of each BILL (i.e., proposed law), including the Bill_name, the
Date_of_vote on the bill, whether the bill Passed_or_failed (whose domain is {‘Yes’,
‘No’}), and the Sponsor (the congressperson(s) who sponsored—that is, proposed—the
bill). The database also keeps track of how each congressperson voted on each bill
(domain of Vote attribute is {‘Yes’, ‘No’, ‘Abstain’, ‘Absent’}). Draw an ER schema
diagram for this application. State clearly any assumptions you make.

Page 2 of 6
Question One:

3.19 Consider the ER diagram of Figure 3.20, which shows a simplified schema for an

airline reservations system. Extract from the ER diagram the requirements and

constraints that resulted in this schema. Try to be as precise as possible in your

requirements and constraints specification.

Answer:

(1) The database represents each AIRPORT, keeping its unique AirportCode, the

AIRPORT Name, and the City and State in which the AIRPORT is located.

(2) Each airline FLIGHT has a unique number, the Airline for the FLIGHT, and the

Weekdays on which the FLIGHT is scheduled (for example, every day of the week

except Sunday can be coded as X7).

(3) A FLIGHT is composed of one or more FLIGHT LEGs (for example, flight number

CO1223 from New York to Los Angeles may have two FLIGHT LEGs: leg 1 from New

York to Houston and leg 2 from Houston to Los Angeles). Each FLIGHT LEG has a

DEPARTURE AIRPORT and Scheduled Departure Time, and an ARRIVAL


AIRPORT and

Scheduled Arrival Time.

4) A LEG INSTANCE is an instance of a FLIGHT LEG on a specific Date (for


example,

CO1223 leg 1 on July 30, 1989). The actual Departure and Arrival AIRPORTs
and

Times are recorded for each flight leg after the flight leg has been concluded. The

Page 3 of 6
Number of available seats and the AIRPLANE used in the LEG INSTANCE are
also

kept.

5) The customer RESERVATIONs on each LEG INSTANCE include the


Customer Name,

Phone, and Seat Number(s) for each reservation.

(6) Information on AIRPLANEs and AIRPLANE TYPEs are also kept. For each
AIRPLANE

TYPE (for example, DC-10), the TypeName, manufacturing Company, and

Maximum Number of Seats are kept. The AIRPORTs in which planes of this
type

CAN LAND are kept in the database. For each AIRPLANE, the AirplaneId, Total

number of seats, and TYPE are kept.

Page 4 of 6
Question Two:

Page 5 of 6
Question Three:

Page 6 of 6

You might also like