Funky Festivals Specification
Funky Festivals organize a music festival that happens at various venues throughout the UK. A venue requires being booked before a Festival can take place. Each festival will comprise a range of artists who will each have their own time slot for performing at festival. Each Act has one and only one manager whose details are recorded as name, address, telephone number and email. Details of each Act include Act name, Manager, Music Genre, number of people in the Act.
Each act is designated either as a major act or a supporting act; an Acts designation may change with each Festival.
Each of the performers will necessitate accommodation and might have their own particular requirements provided for the performance. A festival will comprise at least one major act and up to 3 supporting acts. They require keeping track of what acts, what venues and confirming that accommodation has been booked for every of the acts. Information to be stored about each venue must consist of name, telephone number, address, contact person and capacity of the venue.
Funky Festivals need to know if their festivals have been booming or not so they need a record of how many tickets were sold, that acts they put on, whether there were any problems with any of the acts or venues, the cost of the venue and acts.
There will be a charge of £70 for adults, 12-16 year olds will be £34, 5-11s will be £24 and less than 5s is free. Parking will be £7 per vehicle and £4 camping charge.
Some festivals don’t allow teenager children so acceptable age ranges require to be identified for each festival at a particular venue.
Purchaser details require to be kept which include name, address, telephone number and email address
Milestone 1 Tasks
problem1. Design an Entity Relation Model (or ER) for the problem described above that shows: entities, attributes, keys, relationships, cardinalities, participation constraints, etc.
problem2. State clearly any assumptions that you have made and which justify your modeling choices. Please use the UML notation for your ER model, as used in the lectures.
problem3. Briefly describe your ER diagram.
problem4. Convert your ER in a relational schema. This must consist of primary and foreign keys.
problem5. Discover functional dependencies and normalize your relations to third normal form.