Draw an Entity-Relationship (ER) Diagram to represent the data requirements of the following scenario:

You are setting up your own business by developing an Electronic Auction website for the staff, students, and faculty of your University. You would like to build a database to support the operations of this auction web site. To run your business, you need to keep track of the transactions, specifically, the items that are offered to be auctioned, the person offered the item, and bids and ask prices. In order for any customer (a buyer or a seller) to be able to conduct business on your website, he/she must set up an account with payment methods and personal information (name, email, phone, gender, birthday, address, etc). After the account is established, he/she can offer items or buy items.

However, everyone can offer bids along with his/her name, phone #, and email without creating an account. For each auction item, you want to keep certain information such as ask price, the bids, the final sale price, and the categories that it belongs to. The seller must assign each offered item to at least one category and up to 5 categories.