Practical Assignment Example | Topics and Well Written Essays - 2500 words

Practical - Assignment Example First, it is vital to note that these concerts bear naming scheme and their duration may only be within 2, 3, 4, or 5 hours. The concerts have to fall in three broad categories too. These categories are classical, rock, or pop and all of them have a minimum ticket cost varying from  £25 and  £450. These are scenarios recorded for purposes of having a consistency in data. The consistency that arose from the definitions laid bare by the anticipation of data to be collected here is what leads to the springing up of tables. Secondly, to keep the data collected in check, both in complexity and in quantity, the aspect of the concerts being scheduled and are in a repeated run makes it much easier in the database logic streamline. The events are in a variety of venues but the way that they are set up eases the schematics of the database due the recurring nature of the tables needed. The opportunities in reusing the tables and the design schemas made the work easier and the time saved was key in coming up with the best solution possible for the Concert Office database. In the analysis, stage we figured out that â€Å"REUNION† concert was one that could run in a multiple venues. This type of a scenario often anticipated a lot in the future hence the schema had to accommodate this scenario. After the design accommodating the scenario in the logic, then at least data has to be analysed to ensure maintenance in consistency. The runs that catered for here are what the team at The Concert Office term as events. The dates associated by each of the event and the venues around the UK have to be recorded. Recording is dependent on a proper datasheet and well-foreseen data collection. This scenario demands that customer’s book onto the events. The company will then need to capture the details of these customers. Still, on the requirements analysis stage, the anticipation was