This deliverable applies database design patterns that we leaned in class (transactions and objects, category, and
intersection tables) in creating and querying the database schema for your process. The following 4 items are needed:
1. A data/relationship diagram showing tables, attributes, primary keys, and foreign key relationships.
2. At least one category table and at least one intersection table.
3. The number of object and transaction tables will vary depending upon the complexity of your process.
4. A data design explanation section.
o For each object, transaction, category and intersection table that you include in the data diagram, include 1 paragraph explaining the purpose served by the table and the logic for including the attributes. Clearly identify the primary key and foreign key(s) (if applicable) for each table. Also specify the purpose served by each foreign key.
o For each intersection table, ALSO copy this paragraph filling in the parameters as appropriate: – The A_B_Intersection_Table_Name intersection table supports a many-to-many relationship between the
Table_One table and the Table_Two table. The intersection table, itself, is not a list of individual events or objects of interest, rather its purpose is to record an association between items in the other tables. It has its own primary key and has two foreign key attributes Att_A which points to the primary key of Table_One and Att_B which points to the primary key of Table_Two.
o Example data from ALL the tables in your Access database. Include enough data to demonstrate how the table works, e.g., category tables include at least 2 different categories and intersection tables show M:M relationships in action. A minimum of 2 rows for a category table, a minimum of 5 rows for object and transaction tables, and a minimum of 10 rows for intersection tables.
