Summary TermProject.docx INFO321 PROJECT PAPER American Public University INFO321 1. We can see that the table presents a one to many relationships because a pilot can only work for one airline while the airline can have many pilots also, this can t be the

INFO321
PROJECT PAPER American

Public University INFO321




1. We can see that the table presents a one to many relationships because a pilot can only

work for one airline while the airline can have many pilots also, this can’t be the other

way around. In fact, the pilot entity represents the attributes of PilotID, FName, LName,

JobTitle, Salary and AirlineID. A A pilot can have any PilotID as long as the ID does

not replicate itself. The PilotID is the primary key. The Airlines entity, on the other

hand, represent the AirlineID, NPLanes, NRoutes, NPilots. The Airlines entity is

dependent on the Pilot entity hence the AirlineID appears as a foreign key (FK) on the

Pilot entity.



2. Functional dependency is a constraint between two sets of attributes in a table from a

database. It mainly includes a primary key (PK) and any other non-key attributes in the

table. From the report, the PilotID attribute is a functional decency which uniquely

identifies the FName, LName, JobTitle and Salary since with just the pilot ID one can

obtain the first name, last name, job tittle and salary of a pilot.



3. From the table PilotID is only represented by one AirlineID, meanwhile more than one

AirlineID represent more than one PilotID. So, the relationship between the pilot and the

Airline entity is a one-to-many relationship because a pilot can only work for a single

airline, but an airline can have several pilots.