The business problem
First National Bank's old data model treats every customer the same — but individuals and businesses behave very differently, and shoehorning them into one entity creates years of downstream pain. Use Enhanced ER modeling (specialization, inheritance, weak entities) to design a schema that respects the differences while still giving the bank one unified view.
This case is the cleanest exercise in the course for practicing EER constructs: when you genuinely need them, and how to translate them into a relational schema once you do.
Case kit
The brief & deliverable
- First National Bank — EER Student HandoutRead the scenario; produce the EER and the relational mapping.
Reference materials
- Example EER Diagram (PDF)Reference visual of EER notation.
- Database Design Principles — Handout
Topics you'll be applying
- Decision 3 — Database Design · EER and inheritance
- Decision 4 — Business Rules · constraints to enforce the inheritance