Consider the general architecture of a DBMS.
Where are the key functions of a DBMS implemented in this architecture?
Build a relational model for a church database that includes people, each with a title, name, gender/sex and membership status, and families, each with a (full) address. Individuals can have a “roles” within their family (e.g., parent, child).
Try to ensure the appropriate integrity constraints.
As time allows, add the following to the model in the previous exercise.
Teams — The church maintains a set of leadership teams, e.g., elders, music, etc. People are assigned to potentially many teams and play a particular role on each of them for a particular time period.
Homegroups — The church maintains a set of homegroups, e.g., Bible studies, with names and topics. People have at most one homegroup.
Requests — Households, not individuals, are allowed to submit requests to the leadership, e.g., prayer requests, at a particular time. Each request is assigned to an individual person for followup action and a single-character access code.
Mentors — Any person can have a mentor.