Academic Model Answers
Library for UK Postgraduates

Browse tutor-verified model answers across MBA, Law, Finance, Research Methods and more. Use as study references for your own work.

247 model answers 30+ subjects covered 50+ UK universities
Find your assignment

Search the Library

Filter by keyword, subject, or both. Updates live as new model answers are added to our portal.

Filtering by “Database Systems” Clear filters

Available Model Answers (2)

Real-time Database Sync
Databases and Business Intelligence

Databases and Business Intelligence – KAP Speciality Chocolates Database Coursewor

This individual coursework for the Databases and Business Intelligence module provides practical experience of database systems through the realistic KAP Speciality Chocolates case study. Students are required to design and implement a relational database solution that supports the management of products, stock, suppliers and purchase orders for KAP Speciality Chocolates Ltd. The case study describes a growing chocolate business with a shop and a storeroom that requires a database system to reduce operational errors and improve stock control. The first task requires students to analyse the case study and identify appropriate entities, attributes, relationships, primary keys, foreign keys and dependencies. Students must produce an extended Entity Relationship Diagram showing how the identified elements should be related. The diagram must include participation and cardinality constraints, and students must clearly document the assumptions made and the notation used. A range of modelling notations and software tools may be used, provided that the required database elements are clearly represented. The second task requires students to translate the ER design into a relational database implementation by writing SQL Data Definition Language statements. The SQL must define suitable tables, attributes, data types, primary and foreign keys and relevant constraints. The chosen data types should be appropriate and foreign-key data types must correspond correctly to their related primary keys. The third task focuses on SQL Data Manipulation Language and requires students to create queries addressing a range of business information needs. These include producing a product price list, identifying purchase orders due for delivery on a specified day, generating shop re-stocking lists, changing product cost and selling prices, identifying products with outstanding purchase-order deliveries, producing a re-order list for products below their minimum warehouse stock level, and identifying suppliers that provide multiple cartons. Students must populate their tables with sufficient suitable data to demonstrate that the SQL works and provide evidence of testing through screen captures of SQL statements and results. The fourth task requires students to demonstrate that the database design is normalised to Third Normal Form (3NF). The normalisation process must begin with unnormalised data and show the stages through First Normal Form (1NF), Second Normal Form (2NF) and Third Normal Form (3NF), explaining the changes and reasons at each stage. The final normalised solution must remain consistent with the ER diagram, assumptions and entity and attribute names used in the database implementation. The final submission must combine all tasks into one report written in English, using Arial 12-point font and single spacing. The report must contain the extended ER diagram and assumptions, SQL table definitions, SQL queries with explanations and testing evidence, and a written explanation of the normalisation process. The completed report must be submitted as a single PDF through SurreyLearn by the specified deadline.

Read Model Answer →
Computer Science / Database Systems 4,000 words

Advanced Databases (KL7011) — NORTHERNTOURS Coach Travel Database: EER Design, Oracle Implementation, Object-Relational and NoSQL Extensions

This piece of work addresses a four-part Masters-level assessment in Advanced Databases built around NORTHERNTOURS, a fictitious coach travel operator running services across cities, towns and tourist sites in the North East of England. The company sells tickets through a network of independent travel agents, each currently working from a paper-based sales book, while NORTHERNTOURS itself maintains separate paper records for routes, schedules, seat availability, vehicles and drivers. The brief asks for a single computer-based system capable of replacing both, tracking every agent transaction while giving the company control over ticket issue and seat allocation. Part one covers the conceptual and logical design. An enhanced entity-relationship model was produced covering agents, agent employees, customers, tickets, routes, stops, schedules, vehicles, drivers and the meal provision recorded at each stop, with key attributes, primary keys and full structural constraints shown. Because the scenario does not name identifiers for most entity types, appropriate surrogate and natural keys were devised and justified. The diagram was then mapped to a logical relational schema, normalised to third normal form, with a documented naming convention applied consistently across relations, attributes and keys, and every element recorded in a text-based data dictionary giving names, data types, descriptions and constraints. Part two moves to implementation in Oracle. A full DDL script creates the relations with primary and foreign keys and a substantial set of check constraints — key format patterns, positive seat counts and fare values, date ordering on schedules. Sample data populates the relevant tables, and two retrieval problems are answered twice over, once in relational algebra and once in SQL: schedules between Newcastle and Berwick-upon-Tweed with seven or more seats free in the coming fortnight, and the agent with the highest ticket sales across a defined month. Spooled session output evidences each script running. Part three revisits the conceptual design to argue where object-relational features earn their place — nested route-and-stop structures and composite address and contact types being the clearest candidates — implemented using Oracle object types, VARRAYs and nested tables, and demonstrated through two multi-join aggregate queries. A parallel discussion identifies the schedule and availability workload as a fit for document-oriented NoSQL storage, with representative code and a reasoned account of the denormalisation trade-offs involved. Part four is a report to the managing director covering sustainability, professional, legal, ethical and security obligations, alongside diversity, inclusion, cultural and environmental matters, commercial risk evaluation and mitigation, supported throughout by current literature and published standards.

Read Model Answer →