You have signed on as a member of the Sustainability Taskforce, which sponsors ecologically oriented community projects of various kinds (such as building and distributing composters or constructing energy-efficient low-income housing). You have volunteered to start building a relational database to replace the hodgepodge of spreadsheets currently being used to track membership and projects. Assume you have access to a zip code table and plan to include it in the database.

First, you want to keep track of all the taskforces members. For each member, you want to store the following information: first name, middle name, last name, date of birth, address information (street address, city, state, and zip code), phone number, Email address and date of joining the organization. Furthermore, most members have a mentor, who is another member of the taskforce.

For each project, you want to store a name, worksite address (street address, city, state, and zip code), description, date started, and date ended (blank if the project is still ongoing). Furthermore, you want the database to remember which members are involved in each project: a project can involve as few as 1 member and in some cases as many as 25. A small number of the members involved in each project are designated project leaders; usually there is just one leader per project, but for some larger projects there may be two or three.

1. Create a high-level ERD which shows only the cardinality and modality between the main entities.
2. Write out the tables including the primary keys and the foreign keys.
3. Complete a full ERD with all tables, cardinalities and modalities.