Intertribal Friendship House

1. Intertribal Friendship House Presented by Group 1 Patrick Briaud Yang Liu Milad Odabaei Maria Rodriguez Fernando Siu David Uniman Jennifer Wu John Guo

2. Background of Intertribal Friendship House • Non-profit organization • Founded in 1955 • Located in Oakland • Center for Bay Area’s Native Americans • Conducts various classes open to the public for free • Hosts various community events

3. Current Situation of IFH • Inefficient data management • No electronic database Consequences = problems in: • Human resources • Cash flow • Activity planning • Expansion plan

4. Issues with Human Resources • Failure to database members • Difficulty communicating with members • Lack of formal scheduling system

5. Issues with Cash Flow • No formal accounting system • Highly variable cash inflows • Organization near bankruptcy

6. Issues with Activity Planning • Lack of official scheduling systems • Difficulty coordinating among facilities

7. Project Objectives • Provide a useful organization of IFH’s data • Improve the ability to coordinate activities • Improve the ability to manage resources • Increase efficiency in order to allow sustainability and growth

9. Database requirements Person Entity: • For every person, we store PID, name, phone numbers, email addresses • Each person can be either an employee, volunteer, customer, participant, donor, or any combination of the above Product entity: • For each product, we keep track of PrID, name, selling price Inventory item entity: • For each inventory item, we keep track of IID, name, expiration date, acquisition price

10. Activity Entity: • For each activity, we keep track of the AID, name, type, organizer Facility Entity: • For each facility, we keep track of the FID, name, dimension, floor, room number Time Slot Entity: • For each time slot, we keep track of the date, hour blocks

11. Transaction Entity: • For each transaction, we keep track of date, amount • Each transaction is either a payment or an income • Each payment is either a utility cost, product cost, maintenance cost, employee cost • Income comes from either a rental, donation or sale.

12. Relationships: • Employees and volunteers can work in zero or multiple time slots. Multiple people can work in a time slot. • Volunteer can be available for zero or multiple time slots, and a time slot can have multiple volunteers available. • A customer can be included in at least one sale. A sale is made by one customer only.

13. Relationships: • A donor must make more than one donation. A donation is made by a single donor. • A participant must participate in at least one activity. An activity can have multiple participants. • An activity must take place in at least one time slot. A time slot can have up to many activities. • An activity must take place in at least one facility. A facility can hold multiple activities.

14. Relationships • An employee must be associated with at least one cost. An employee cost is only associated with one employee. • An activity can generate one rental income. A rental must be associated with one activity. • A product can be a component of multiple products. A product can have multiple components. • An inventory item must be one type of product. There can be many inventory items of a product.

15. Relationships: • A sale must include at least one inventory item. An inventory item can be included in one sale. • An inventory item must cost one product cost. A product cost must have one inventory item.

17. Project Schedule • 10/24: Begin revising the EER diagram and Relational Design • 10/28: Revisit the center to collect additional data • Verify the usefulness and accuracy of proposed database design with board members • Ask for query requests from the board members • 11/5: Finalize EER diagram and improve on the Relational Design • Develop multiple queries to address the center’s needs