OBJECTIVE: Get some firsthand experience with the implications of a chain of relationships.

INTRODUCTION: Jo Annes Fabrics and Crafts has stores all across the country. Each store has a name that is unique within that stores district. Each district has a name that is unique within that districts region. Each region has a name that is unique within that regions state. Assume for this exercise that Jo Annes only operates within the United States.

Each store has a store manager. Each district has a district manager, and so on up the line. A given manager manages one and only one store, district, region, and state. Each manager is an employee of Jo Annes. Each employee in Jo Annes has a surrogate key: EmployeeID. Their Employee ID uniquely identifies them across all of Jo Annes.

PROCEDURE: For each state, we want to know the manager in charge of that state. For each region, we want to know the manager. Similarly for the district and the individual store. For each store, we want to know the city within the state where the store is located. One city could have more than one Jo Annes stores in it. A given store can come in large or small format and we want to know that as well.

Create a UML class model of the above information. Then create the corresponding relation scheme diagram.

There are two basic ways to go about the key structure of this model: one using a surrogate key in each case, and the other that uses no surrogate keys. Use both approaches and compare and contrast the results.

WHAT TO TURN IN:

The UML class model for each approach to the key structure in either a .dia or draw.io model.

The relation scheme diagram for each approach to the key structure in either in a .dia or draw.io model.