Travel Jabs Clinic Centralised Database

Замовник: AI | Опубліковано: 16.12.2025

Assignment Description: Travel Jabs Clinic Database System This assignment involves designing and building a small but complete database system for a fictional company called Travel Jabs, which provides private travel vaccinations through clinics across the UK. The goal is to create a centralised database that improves how information is stored, shared, and managed across multiple clinics. You are required to take the system description provided and translate it into a well-structured relational database, documenting both the design and implementation clearly in a report. What the system must support The database must store and manage information about: • Clinics (location, contact details, manager, staff) • Staff (personal details, job role, salary, clinic association) • Patients (personal details and contact information) • Vaccines (types, descriptions, and fixed prices) • Appointments (date, time, vaccines required, duration) • Invoices and payments (vaccines given, costs, payment date and method) Although invoices do not display which staff member administered vaccines, this information must still be stored in the database. Required tasks and deliverables 1. Entity-Relationship (ER) Diagram (UML notation) • Show all entities, attributes, relationships • Include cardinality and participation constraints • Clearly state any assumptions made 2. Data Dictionary • Define every table and attribute • Include data types, keys, and constraints 3. Database Implementation (Oracle SQL) • Write CREATE TABLE statements for all tables • Include these statements in the report 4. Data Population • Insert realistic sample data into the tables • Provide screenshots showing populated tables 5. Constraints Discussion • Explain entity, referential, and column constraints • Justify why each constraint was used and how it ensures data integrity 6. SQL Queries • Write three meaningful SQL queries that demonstrate the database meets system requirements • Queries must use a range of SQL features (not simple SELECT *) • Include screenshots of query results