Create ER diagram from the following requirements. In UML ERD notation using cardinality and participation constraints. Write down any assumptions you make that are not specified.

We are going to create a database to keep track of our congressman in the House of Representatives. Each representative will have a name, state, a political party (Republican, Democrat, Independent), multiple phone numbers and an office location. We will also keep track of each of the bills that come to congress to be voted on and how each representative votes. Each Bill has a bill number, a name, a status, total votes for, total votes against, total votes abstained. A representative votes on a Bill. For each vote, the vote (for, against, abstain), the exact time the vote was submitted, and multiple comments the representative may have about this vote are stored.

We are also going to keep track of committees that Representatives are members of. For each committee, we need to maintain its name, they type of committee (voting or advisory), the chairman of the committee, the office number and the total number of members (this is to be stored for faster data retrieval). Representatives may be on many committees and committees can have many members.

Note: We will want to be able to sort our representatives by their last names. To maintain the integrity of the database and to save space, the total votes data fields for each bill will not be stored with the bill information. A representative may only vote on a bill once but over time will vote on many.