Database design

As a database developer, you have been asked to design a new database the operation of the new project within the Liverpool John Moores University (LJMU). LJMU is planning to deliver a number of professional training courses in Al. Each course is delivered by one member of staff at LJMU's Training Centre; each staff is allocated a staff number. The policy of LJMU is to record the start working date of each staff, the first and last name, the date of birth, home address, telephone number for (home and mobile email, type of contracts (permanent, sessional), sex, National Insurance Number and the specified salary. There are different training courses offered by LJMU. The fees vary for each course and on the number of delegates a company sends. For example if a company sends one delegate, the charge may be 2500. If the company sends two people, the first may be charged 2500, but the second may be charged 2000 The Al professional courses can be attended by a number of delegates, subject to a limit for each course (Maximum 10 for each of the planned professional courses). A start and end date is assigned for each course with the start and end time. An invoice is sent to the delegate's company. The invoice clarifies to the client orland the company the date that the fee is paid, method of payment (one full payment, or a deposit then completing the payment) (a) Identify the main entities (list all attributes of these entities) for the above proposed database. Determine primary key, Candidate keys and foreign keys attributes b) Create a single Entity-Relationship (ER) diagram to represent the data requirements of the database (Conceptual Database Design). To simplify the diagram, only show entities, relationships, primary and foreign key attributes. State any assumptions (if necessary) to support your design. (c) Identify the main relationships between entities described in part (a); represent each relationship in your ER diagram, clearly labelling each relationship. State the degree of each of the relationships described in part (b). Decompose any many to many relationships, replacing them with new entity types and relationships