AlmostAnyNotForProfit.com You are the founder of AlmostAnyNotForProfit.com, an online website that connects donors, donations, and not-for-profit agencies. Your website is unique because it permits individuals to donate to different charities (not-for-profits) from one location. For example, before your ingenious website was invented an individual who wanted to donate to the Community Development fund, the Senior-Care Program, and the Human Fund had to go to each agencys website and make a donation. Now, using your site people can simply select (from a drop down list) which agencies they wish to give to. Brilliant.

In AIS class you heard Professor Tadesse talk about the importance of maintaining good database documentation. Thus, you have decided to create an ERD for AlmostAnyNotForProfit.com. Your companys database records and tracks three factors of interest: donors, donations, and agencies. Each factor has its own table.

Perhaps the most important table is the donor table. The donor table tracks each donors first name, last name, and phone number. Further, every donor is assigned a unique identifying number. Because you outsourced all payment operations, you do not track any of the donors payment-related information within your database. Although every donor can give to as many agencies as desired, each individual donation can go to only one agency. Thus, a donor who wishes to give to multiple agencies must complete several donation transactions.

The agency table records information about each agencys name, contact persons first and last name, the contacts phone number, and a way to uniquely identify each agency. Further, each agencys street address, city, state, and zip code are tracked within the agency table.

Finally, the donation table keeps track of all donations given by donors. Consequently, the donation table needs to track the donation value (amount), the agency the donation was given to, and the donation date. Also, the donation table needs to record who gave the donation. Further, each donation must have its own unique identifier. (This is the trickiest table to model!)

IDK what to do with this.