Draw a logical ERD in crows foot notation for the case described below. Make sure to indicate all relevant entity sets, attributes, primary keys, foreign keys, relationships, and cardinalities. If you need to make any assumptions, state them clearly in your answer. Software Architecture Association of New Zealand (SAANZ) The Software Architecture Association of New Zealand (SAANZ) wishes to manage its membership using a database. After the interviewing of the SAANZ committee members the following requirements were identified: Member: the information to be stored about a member is: membership number, first name, last name, email address, telephone number. Only persons with an email address may join the association as all communication is carried out via email. Only current email addresses are stored. Membership Type: there are several types of membership such as: student, associate member, full member and fellow. The information to be stored about membership type is: membership type code, membership type description. Over time a member's membership type may change. Membership: it is necessary to store the details about when a member joins the association, her/his membership type, and when s/he changes her/his membership type or leaves the association. Membership fees will be constant for one calendar year but may change from year to year. Currently the membership fee differs for each membership type. To retain an upgraded membership type with the association, a member must accumulate a certain number of 'professional development' points during a calendar year. These points are awarded for attending the association's events during one calendar year. The minimum number of points that a member must accumulate depends upon the member's type of membership. For example: student members and associate members do not have to accumulate any points, a full member must accumulate at least ten points, and fellows must accumulate fifteen points. The number of points to be accumulated per membership type may change over time - but will only change at the beginning of a calendar year. If insufficient points are accumulated, the member will be demoted to a lower membership type. If a member changes his/her membership type part way through a calendar year, the most recent membership type dictates the minimum number of points the member should accumulate. As points are awarded for attending the association's events it is important to store the details of which association events the members attend. Event: the details to be stored about an association event are: eventID, event name, event description, date of event, start time and duration, and number of points per membership type awarded for attending the event. Committee: At each Annual General Meeting (AGM) for the Association, a committee is elected. It is

important to retain in the database the details as to which members were elected each year. The AGM is a special event of the association and points are awarded to members for attending. As well as the usual event information, it is necessary to store, for the AGM, the excess (or otherwise) of income over expenditure for the year. Committee role: Persons elected to the committee may be elected as: chairperson, secretary, treasurer, or ordinary committee member. Payments: it is necessary to store the information about payments made by members towards their annual fees. Sometimes part payments are received; sometimes a member may end up in credit. The information to be stored about a payment is: date of payment, method of payment, payment amount.