From the case study below answer Tasks 1-3

Whenever a customer makes a booking on the web page, they must enter their customer details. A new customer will automatically be assigned an account number, or a returning customer can register using their original account number and password. It is not necessary for you to model the password. The customer must supply details of their name (rst name, last name for a person, or organisation name if not an individual person]. If the customer is a person, a contact phone number and email address must be supplied. For an organisation their contact person's details must be stored (rst name, last name, phone number, email address}. A contact person for an organisation may change over time. For each new gustomer the billing address must be supplied {street address, suburb, city, postcode, country}. Once the photography session is completed, the digitized photographs will be stored in a database table, identied by the session date and start time, and each photo's unique number for that session. Once stored, the customer will be emailed with details of how to access the photos online. Saba Orange sometimes extracts sections of her photographs and assigns them individual numbers and stores them_i_r_1_t_h_e_i_r__o_w_n__r_ig_l'_1t_. In the database it will be necessary to be able to relate the extracted photographs to the original photograph from which they were sourced. Customers wiil order their printed photographs on the webpage. Each order will automatically receive a unique order number, and the dateftime of the order acceptance. Customers will be able to view their photos at the time of ordering and select each required photo by clicking on its thumbnail photo. For each selected photo the customer must choose a photo colour {% black and white, sepia, coiour gig}, size, whether the photos are to have a glossy or matte nish, and specify the number of copies required. it is possible that the same photos will be selected in differing combinations of colour, size, and nish, and that different quantities may be ordered for each combination. Each photo combination of colour, size and finish may have its own price, which may change over time. The orderer must also indicate whether the finished photographs will be collected from APU's studio or be couriered. If the order is to be couriered, a destination postal address must be entered if it differs from the billing address. The destination for the order may be a person or an organisation with details as described previously for customers. For each destination country, APU charges a xed postage amount. The postal charge set for each country must be stored in the database. The postal charge may change over time. The total cost of the order, including the cost of the prints and postal charge, if any, will be calculated by the system, displayed on the webpage, and the customer must pay before the order is accepted. Thus, any booking or order will be paid at the time of recording on the webpage. The handling of the payment will be carried out by a third party so payment details will not be stored in the database. However, a booking or order will only be validated if the third party approves the payment. Thus, only paid bookings and orders will be stored in the database. Case Study: APU Photography Database for Online Booking and Ordering System You have been invited to join the project team that will be involved in developing a computerized booking and ordering system for APU Photography Limited. Your job will be to model the data to be stored in the database that will be created for the new system. APU invited the project team to a meeting to discuss their requirements. Saba Orange, the founder of APU, and outstanding photographer, started the company in 2015 and has slowly achieved the reputation of being Auckland's leading portrait photographer. Her profile is such that appointments for her photography sessions must be made at least two months in advance. Saba now employs three office staff, an accountant, and three assistants. The increase in business has forced Saba and her staffto consider implementing an online system to manage the photography session bookings, the ordering of photographs by customers, and the dissemination of digital proofs to the customers. It is planned to develop an APU web site where bookings for photo sessions and orders for photo prints can be entered. Both bookings and orders will have to be paid at the time of their entry on the webpage in order to be accepted. Delivery of the ordered prints is promised within two weeks of ordering. The method of collection of the ordered photographs, whether picked up from the studio, or couriered, will be chosen by the people who place the orders on the website. Through a series of questions from the team, the following information was obtained about the data that should be stored in the system: To book a photography session on the web page, the customer will select an available date and session time from charts displayed. Session times currently last 75 minutes, with 15 minutes break between sessions. For each weekday the session times are as follows: 8.30 am 9.45 10.00 am 11.15 pm; 11.30 am 12.45 pm; 1.30 2.45 pm; 5.30 pm 6.45 pm. However, session times may change in the future. Photography sessions are carried out in the APU studio, or on a location of the customer's choice, where location can be at a local beach, park, cafe, home etc., Currently a customer is charged $250.00 fora daytime session and $275.00 for an early evening session in the studio, or $400.00 on a location. it is possible that this charge could also change in the future, with individual sessions all having individual charges. Assume that session times will always be constant for all days in the week. The web page must prompt the customer as to the reason for the photographic session: graduation, wedding, baby etc. The customer may enter a different reason if their purpose is not included in the webpage list. If customers cannot attend their booking, they must cancel on the web page at least three days in advance in order to receive a refund. Part A Entity Relationship Modelling and Logical Database Design Task 1 identify Entities 8: Develop Business Rules Identify all entities and relationships in the case study and develop a set of business rules. You should follow the syntax given below. Each relationship must be described by two rules, one in each direction. Eacth/An ENTIT_1 May/Must Relationship Verb Phrase number ENTITY_2 Task 2 Construct a logical Entity Relationship Diagram (ERD) Based on the business rules developed in Task 1, construct a logical ERD for the case study using the Visual Paradigm tool. 0 Identify all attributes in each entity including all primary and foreign keys (any composite and multivalued attributes must be transformed according to the rules of the relational model}. 0 All relationships must be named (L; Verb phrases must be shown for all relationships} 0 If superfsubtypes are used, indicate whether the supersubtype relationships are disjoint or overlapping, and fully or partially specialised (com plete or incomplete}. 0 Identify the Ca rdinality and Participation for each relationship. - Resolve all E relationships. 0 Describe any assumptions you have made in a text note in the diagram. Task 3 Use Normalisation to validate your ER {a} Use the technique of normalisation to validate your logical ERDI data model . Demonstrate that each of your relations is in third normal form (3NF) by displaying (a list of dependencies} the functional dependencies between attributes in each relation. Note, if any of your relations are not in 3NF, this may indicate that your ER model is structuraliy incorrect or that you have introduced errors in the process of deriving relations from your model