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 →
Systems Analysis and Design
Systems Analysis and Design with UML – Individual Systems Design Assignment
This individual assignment forms Part 2 of the Systems Analysis and Design with UML assessment and contributes 50% of the overall module weighting. The uploaded guidance indicates that this component should continue directly from work completed in Part 1, meaning that the analysis and design developed previously should provide the foundation for the second-stage submission. The assignment is centred on the principles and practices of systems analysis and design using the Unified Modeling Language (UML). It is intended to demonstrate the application of structured analytical thinking and modelling techniques to the development or refinement of an information-system solution. Because Part 2 follows an earlier assessment component, continuity between the original problem definition, requirements and subsequent design work is likely to be an important aspect of the submission. Relevant areas may include requirements representation, system modelling, process and interaction analysis, object-oriented design and the use of appropriate UML artefacts to communicate system structure and behaviour. The work should therefore demonstrate how analytical findings are translated into coherent design decisions while maintaining alignment with the system requirements established during the earlier project stage. The assessment is individual and therefore should demonstrate independent understanding of the selected system, its requirements and the rationale underlying the proposed design. The uploaded summary confirms that this component is worth 50% of the module and has a submission deadline of 15 May 2026 at 17:00 GMT. Note: the actual detailed Part 2 brief is not contained in this uploaded summary, so specific UML diagrams, required sections, word count and marking criteria cannot be confirmed from this document alone. Entry 2 — Intelligent User Interfaces Part 1 Field Content to enter Title Smart Study Student Assistant: Intelligent User Interface Prototype University Not specified in the uploaded guideline Subject Intelligent User Interfaces / Human-Computer Interaction Module name Intelligent User Interfaces Academic level Not specified Academic year Not specified Assignment type Presentations and Academic Posters Reference style Not specified Word count Not applicable – maximum 10-minute pre-recorded prototype presentation Amount (₹) Enter your internal project amount Key topics Intelligent User Interfaces, Human-Computer Interaction, Smart Study Assistant, Student Productivity, Adaptive Interfaces, Personalised Learning, Study Planning, Question Generation, Low-Fidelity Prototyping, User-Centred Design, User Behaviour, Learning Progress, Educational Technology, UX Design, Personalisation Assignment overview This project prototype forms Part 1 of Intelligent User Interfaces and contributes 60% of the final module mark. The assessment requires a project prototype supported by a pre-recorded presentation of no more than ten minutes. The selected project concept is a Smart Study Student Assistant, positioned within education and student-productivity technology. The proposed system is an adaptive study-planning and note-based question-generation interface. Its purpose is to help students organise academic work by combining uploaded study notes, deadlines and information about user behaviour to generate personalised study plans and learning questions. The project addresses common problems including scattered study materials, missed deadlines, unclear schedules and the lack of personalised guidance on how and when students should study. The guidance specifically states that the solution should not be unnecessarily advanced. Instead, the design should focus on how the interface will be useful to different types of users. Low-fidelity material and supporting notes are also required, indicating that the project should demonstrate user-centred design thinking rather than focusing solely on technical sophistication. The intended goal is to provide personalised study plans, questions and guidance based on the student's notes and deadlines, supporting more consistent study habits and improved organisation. Tutor feedback describes the concept as relevant and well motivated but identifies one important weakness: the system's intelligent behaviour is currently under-specified. The tutor specifically recommends clarifying how study plans and question generation adapt according to user behaviour or learning progress. Accordingly, the prototype should communicate both the interface design and the adaptive logic that makes the system genuinely intelligent and user-centred. Entry 3 — Intelligent User Interfaces Part 2 Field Content to enter Title Intelligent User Interfaces – Individual Essay University Not specified in the uploaded guideline Subject Intelligent User Interfaces / Human-Computer Interaction Module name Intelligent User Interfaces Academic level Not specified Academic year Not specified Assignment type MS Essays Reference style Not specified Word count Not specified Amount (₹) Enter your internal project amount Key topics Intelligent User Interfaces, Human-Computer Interaction, Adaptive Interfaces, User-Centred Design, Intelligent Systems, Personalisation, User Experience, Educational Technology, Interaction Design, AI Interfaces Assignment overview This individual essay forms Part 2 of the Intelligent User Interfaces module and contributes 40% of the final module mark. The uploaded guidance identifies the submission deadline as 21 May 2026 at 16:00. The assessment belongs to the same Intelligent User Interfaces module as the Part 1 prototype project. The broader module context therefore concerns the design and evaluation of interfaces that use intelligent or adaptive behaviour to improve interaction between users and digital systems. Relevant considerations may include personalisation, adaptive interaction, usability, human-computer interaction, user behaviour and the responsible design of intelligent systems. However, the uploaded summary does not contain the actual Part 2 assessment brief, essay question, required word count, marking criteria or prescribed topic. It only confirms that the assessment is an individual essay worth 40% of the final mark. For that reason, the Reference Library overview should remain general rather than claiming that Part 2 specifically assesses the Smart Study Student Assistant. If the Part 2 essay is intended to continue or evaluate the Part 1 prototype, that relationship should only be added once the actual Part 2 assessment brief confirms it. The current document explicitly provides the Smart Study Student Assistant instructions under Subject 2, while no corresponding topic instructions are shown for Subject 3. So for Entry 3, I would keep the title and overview generic until the actual KV7005 Part 2 brief is uploaded.
Read Model Answer →