Using the functional dependency notation used in Examples 14.4, 14.5, list the functional dependencies that exist in the below table attached figure. All attributes should be included at least once.

EXAMPLE 14.4 Example of a transitive functional dependency

Consider the following functional dependencies within the StaffBranch

staffNo ? sName, position, salary, branchNo, bAddress

branchNo ? bAddress

The transitive dependency branchNo ? bAddress exists on staffNo via branchNo. In other words, the staffNo attribute functionally determines the bAddress via the branchNo attribute and neither branchNo nor bAddress functionally determines staffNo.

EXAMPLE 14.5 Identifying a set of functional dependencies for the StaffBranch relation

We begin by examining the semantics of the attributes in the StaffBranch relation. For the purposes of discussion, we assume that the position held and the branch determine a member of staff's salary. We identify the functional dependencies based on our understanding of the attributes in the relation as:

staffNo ? sName, position, salary, branchNo, bAddress

branchNo ? bAddress

bAddress ? branchNo branchNo, position ? salary

bAddress, position ? salary

We identify five functional dependencies in the StaffBranch relation with staffNo, branchNo, bAddress, (branchNo, position), and (bAddress, position) as determinants. For each functional dependency, we ensure that all the attributes on the right-hand side are functionally dependent on the determinant on the left-hand side.

Figure - Cars Sold CustID, Fname and Lname refer to the person who purchased the car CarVin# Year Manufacturer SalesPrice CustID Fname Lname 12345 2014 Ford 27,000 100 John Smith 67890 2015 Honda 20,000 200 Jane Doe 10293 2012 Ford 18,000 300 Sam Jones 54322 2010 GM 15,000 400 Sarah Jackson 98989 2013 Hyundai 18,500 100 John Smith 76766 2009 Toyota 10,000 500 John Smith 88999 2012 Toyota 18,500 600 Sam Jones