Filter by keyword, subject, or both. Updates live as new model answers are added to our portal.
3,000 words
ParkaLot Enterprise Parking Garage Management System: Software Analysis, Design and Prototype Development
This enterprise software engineering project requires students to analyse, design and prototype a centralised parking garage management system for ParkaLot Group, a UK operator of multi-storey parking facilities. The existing organisation relies heavily on manual processes, local spreadsheets and simple barrier-based vehicle counts, resulting in limited real-time occupancy information, inconsistent reservation arrangements, decentralised billing and reduced ability to optimise parking capacity and revenue. COMP1471 CW 2526 (1) The proposed system supports ParkaLot’s wider digital transformation by integrating customer registration, reservations, parking-space allocation, occupancy monitoring, contracts and billing. Customers can check availability and reserve parking through an online portal, while frequent and corporate users can establish recurring arrangements or block reservations. License-plate recognition and individual parking-space sensors enable automated access control and real-time occupancy tracking. COMP1471 CW 2526 (1) Additional functionality includes centralised electronic billing, dynamic pricing, promotional schemes and predictive decision-making for controlled overbooking. Historical usage data may be analysed to estimate no-shows, early departures and overstays, while operational dashboards support staffing, pricing and capacity-management decisions across the garage network. COMP1471 CW 2526 (1) Development is undertaken in two phases. The first uses structured analysis and design, requiring an Entity Relationship Diagram, Data Flow Diagram including a context diagram, and implementation of a prototype database. The second expands the solution using object-oriented analysis and UML, with emphasis on adaptable and reusable software design. COMP1471 CW 2526 (1) The final report covers the software-engineering **5 Ps—Problem, Process, Project, Product and People—**alongside ERD and DFD models, UML use cases, at least three sequence diagrams, a detailed class diagram and application of design patterns such as GRASP. Students must also submit prototype evidence, source code, personal reflection, peer assessment and work-contribution documentation. COMP1471 CW 2526 (1) Overall, the assessment integrates requirements engineering, structured modelling, object-oriented design, database development, design patterns, software project management, implementation and acceptance testing within a realistic enterprise-system case study. Overview word count: approximately 360 words. AI-use note: the brief permits Levels 1–4 of generative-AI use, including research and exploration at Level 4, but all final submitted text, code, diagrams and designs must be the students’ own work. Level 4 use requires disclosure, an appendix of prompts/outputs and reflective commentary. COMP1471 CW 2526 (1)
Read Model Answer →
Software Engineering / Enterprise Systems Development
3,000 words
Enterprise Software Engineering Development: ParkaLot Parking Management System Analysis, Design and Prototype
This Enterprise Software Engineering Development assessment is based on the ParkaLot Group, a fictional operator of multi-storey parking garages across major UK cities. The organisation currently relies on fragmented manual processes, basic barrier-based vehicle counting, local spreadsheets, on-site payment and inconsistent customer access arrangements. Students act as software engineering consultants and are required to analyse these operational weaknesses and design a centralised enterprise parking management system capable of supporting reservations, customer accounts, vehicle identification, billing, real-time occupancy monitoring, dynamic pricing and management reporting. COMP1471 CW 2526 The proposed ParkaLot platform is intended to integrate customers, parking spaces, reservations and billing across the garage network. Planned functionality includes online registration and reservation, recurring and corporate parking arrangements, licence-plate recognition, automated space allocation, sensor-based occupancy tracking, centralised monthly billing, electronic payments, promotional pricing and predictive overbooking. The system must also provide dashboards and historical reporting to assist management with capacity planning, staffing, pricing and operational decision-making. COMP1471 CW 2526 The coursework is completed in two main development phases. Phase 1 – Structured Analysis and Design requires an Entity Relationship Diagram representing the logical data model, a Data Flow Diagram including a Level 0 context diagram, and implementation of a prototype database. Phase 2 – Object-Oriented Development extends the system using object-oriented analysis, design principles and UML, with substantial business and user-interface functionality implemented using suitable OO technologies. COMP1471 CW 2526 The final report contains analysis of the 5 Ps of software engineering: Problem, Process, Project, Product and People. Students discuss the business problem and commercial risks, justify the development methodology followed, define resources and budget, document project artefacts and requirements, and identify the main stakeholders involved in the project. The technical design section includes the ERD, DFD, UML use-case model, at least three sequence diagrams, a detailed class diagram and discussion of design patterns. COMP1471 CW 2526 Students must additionally submit a functioning prototype that reflects the design and participate in acceptance testing and a live demonstration. Individual students are questioned on both theoretical and technical aspects of the submitted system. The assessment also evaluates group contribution, peer and self-assessment, personal reflection, research quality, communication and professional teamwork. COMP1471 CW 2526 The weighting places substantial emphasis on technical design and implementation: the UML design is worth 24 marks, the software prototype 15 marks, design patterns 6 marks, and acceptance testing/demonstration 25 marks. This makes the coursework strongly focused on demonstrating the relationship between requirements analysis, software architecture, UML modelling, implementation quality and working enterprise-system functionality. COMP1471 CW 2526
Read Model Answer →
Data Science / Data Management / Professional Practice
4,500 words
Tesla Data Science Professional Case Study: Data Management, Leadership, Entrepreneurship and Ethics
This composite case-study assessment for The Data Science Professional module requires students to critically analyse Tesla from several interconnected professional perspectives, including data management, artificial intelligence ethics, leadership, organisational development, entrepreneurship and business risk. The coursework is designed to combine technical data-science capability with strategic, ethical and managerial decision-making. a82a1aa6a2e7a3268ad021c4f5b3d44… Part A – Database Design and Distributed Frameworks focuses on data management. Students design an Entity-Relationship model and relational schema for a Tesla-related vehicle-hire business, identifying entities, relationships, cardinalities, identifiers, primary keys and foreign keys. The accompanying guidance specifies entities relating to vehicles, employees, outlets, clients, hire agreements, insurance, faults and employment records. a82a1aa6a2e7a3268ad021c4f5b3d44… 39cdc24cc46a13ddf444b8e7af838eb… The SQL component uses an Online Music database to examine Tesla customer preferences. Students create relational tables using Oracle standard SQL and write queries involving users, music, publishers, categories and download records. Evidence of implementation and query results must be provided using Oracle Live SQL. 39cdc24cc46a13ddf444b8e7af838eb… Part A also requires a critical assessment of the security, privacy and ethical implications of Tesla’s Full Self-Driving technology, connecting technical development with responsible data and AI practice. a82a1aa6a2e7a3268ad021c4f5b3d44… Part B – Leadership and Developing People requires critical evaluation of Tesla’s leadership model, organisational culture and their effects on employees and organisational performance. Students must propose a leadership and people-development strategy capable of supporting the organisation as it expands. a82a1aa6a2e7a3268ad021c4f5b3d44… Part C – Entrepreneurial Practice and Managing Risk examines a proposed Tesla spin-out venture developing innovative low-cost green hydrogen production systems. Students critically assess management support for the venture, propose an evidence-based approach to entrepreneurial risk, develop an entrepreneurial leadership role descriptor, and evaluate how GDPR and AI/data ethics may support or constrain entrepreneurial practice. a82a1aa6a2e7a3268ad021c4f5b3d44… Overall, the assessment integrates technical database design, SQL, data ethics, organisational leadership, entrepreneurship, sustainability and professional decision-making within a single Tesla-focused case study. Overview word count: approximately 360 words. Important: the assessment brief itself explicitly states that it must not be passed to third parties or posted on any website. So for a public Reference Library, use the metadata and your own finished work where permitted, but do not upload the assessment brief/guidance PDFs themselves publicly. a82a1aa6a2e7a3268ad021c4f5b3d44… The AI status is Amber: generative AI may be used for limited inspiring/planning purposes, but usage must be acknowledged with the tool, prompts and relevant evidence; the brief also specifically prohibits using LLMs to generate the Part A(3) essay. a82a1aa6a2e7a3268ad021c4f5b3d44… a82a1aa6a2e7a3268ad021c4f5b3d44…
Read Model Answer →
Data Management / Business Analytics
2,500 words
Data Design Management (BS514) — Data Strategy Consultancy: Relational Database Design, SQL Implementation and Pipeline Transformation
This Level 7 assessment places the writer in the role of a Data Strategy and Analytics Consultant appointed by an organisation operating in a realistic industry sector. The brief is entirely simulated, so the work sets out a defensible set of assumptions about the organisation's data environment before any design begins, and populates the resulting database with synthetic but realistic records. The deliverable is a slide deck carrying full explanatory notes, submitted as a single PDF, and weighted across three connected tasks. Task one establishes the business case. It describes how the chosen organisation currently collects, stores and uses data across customer interactions, sales transactions, operational processes and digital channels, and identifies where that fragmented picture costs the business in efficiency, resource use, retention and decision quality. A SWOT analysis benchmarks the organisation against a named real-world competitor in the same sector, drawing on publicly available market information rather than assertion. The section closes with a critical evaluation of modern relational database advancements — cloud-hosted SQL services, distributed architectures and data warehousing — assessed not in the abstract but against what each would actually change about this organisation's business model. Task two carries the heaviest weighting and is the technical core. Key business entities are identified from the scenario, a current-state data flow diagram traces how data moves from collection points through to storage and reporting with the existing ETL approach made explicit, and a future-state ER diagram is then built with full attributes, primary and foreign keys, relationships and cardinality. The design is normalised to third normal form with the decomposition reasoning shown. Implementation follows in SQL: tables created with appropriate integrity constraints, at least ten realistic sample records inserted per table, and five business questions answered through working queries — highest-performing product or campaign, average conversion by category, workload distribution across staff, accounts with overdue or pending items, and most effective service channel. Outputs accompany every script. A transformation demonstrating query optimisation is included with before-and-after samples so the improvement is evidenced rather than claimed. Task three steps back to the technology decision. Two widely used data processing platforms are compared in tabular form across integration, cleaning, transformation and automation capability, judged specifically against this organisation's constraints, with a reasoned justification for the tool finally selected. The transformed dataset is then used to answer two management-level questions — where investment should be prioritised and how retention might be improved from observed behavioural patterns — each interpreted briefly and tied back to a concrete recommendation. Slide structure follows the prescribed layout, SQL scripts sit in the notes section, and the complete script file is reproduced in the appendix.
Read Model Answer →