2. We want to design an entity-relation model of a system that stores civil court cases with the following assumptions: Each court case should have an ID, a filing date, and a complaint. Each court case involves a plaintiff and a defendant. Note that a plaintiff in one case could be the defendant in another case. (Ignore modeling constraints such as a person cannot file a case against themselves, or conflicts of interest.) Each plaintiff/defendant in a case must be represented by someone. However, note that a person can be represented by different individuals in different cases. Each individual should be modeled using their their ID, name, date of birth, and address.

(a) Draw an ER diagram that completely models all the assumptions discussed above. Mark the primary keys of the entity sets. [20pt.]

(b) Convert the ER model to a relational database schema with only two relations. For each table, discuss the conversion process, starting from the ER sets and resulting in the particular table schema. List the primary keys, not-null, and foreign key constraints. [20pt.]