Filter by keyword, subject, or both. Updates live as new model answers are added to our portal.
Web Applications / Artificial Intelligence / Software Development
Smart Clinic Appointment and Patient Management System with AI-Based Demand Prediction
This Web Applications and AI coursework requires students to design, implement and evaluate a Smart Clinic Appointment & Patient Management System for a small healthcare clinic. The application combines conventional web-development functionality with an artificial-intelligence component for predicting appointment demand. The system is expected to use Java EE technologies, including Java Servlets, JSP, Web Services and JDBC, together with a relational database such as MySQL or PostgreSQL. f3855340dabd17407efd386c38cfdc3… The patient-facing side of the application should allow users to browse and search clinic services by department or specialty, price, availability and duration. Patients must be able to view detailed service information, select a clinician where appropriate, choose an available date and time, enter their details and confirm an appointment. The system should also provide a booking reference and basic appointment-history functionality. f3855340dabd17407efd386c38cfdc3… The administrative interface focuses on operational management. Staff should be able to add, update and remove services, configure consultation duration and pricing, manage clinician working hours and appointment-slot availability, and generate basic reports. f3855340dabd17407efd386c38cfdc3… A separate machine-learning component requires students to implement appointment-demand prediction using WEKA regression embedded in Java. The provided sample dataset contains Year, Month, Promotions Cost and Booking Requests. Students must expand this dataset to at least 60 realistic rows, including seasonal changes and plausible variation in marketing expenditure and demand. A regression model is then trained to predict booking requests for the following year based on promotional spending, including estimation of future demand if promotions expenditure increases by 10%. f3855340dabd17407efd386c38cfdc3… The assessment also requires evidence of professional software-development practice. Students must provide application-design artefacts such as design patterns, ER diagrams, wireframes and sketches, document the development process, demonstrate correct use of JSP, Servlets, Web Services and JDBC, and provide evidence of implementation through code, database content and screenshots. Regular GitHub commits are required to demonstrate ongoing development. f3855340dabd17407efd386c38cfdc3… f3855340dabd17407efd386c38cfdc3… The final submission includes a DOCX or PDF report containing system-design and implementation information, links to a private GitHub repository and a demonstration video of no more than five minutes. The assessment is classified as Green for AI use, meaning AI tools may support tasks such as generating example datasets, suggesting code snippets and brainstorming features or tests, provided their use is clearly declared in the report. f3855340dabd17407efd386c38cfdc3… Overall, the coursework integrates full-stack Java web development, relational database design, web services, software engineering and machine-learning regression within a healthcare appointment-management scenario. Important: the uploaded brief states that it is for Coventry University Group students' own use and must not be passed to third parties or posted publicly. f3855340dabd17407efd386c38cfdc3… So for a public Reference Library, use an original summary like the one above rather than publishing the original brief itself.
Read Model Answer →
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 →
Computer Science / Research Methods / Specialist Research
2,800 words
Research Specialism Report: Critical Review of Open Research Questions in Computer Science
This Advanced Research Topics in Computer Science assessment requires students to critically examine a research paper associated with their chosen MSc specialism and demonstrate an understanding of how established research techniques are used to create and extend knowledge in computer science. Eligible specialisms include Artificial Intelligence, Networking, Cyber Security, Software Engineering and Data Science. The assessment is intended to prepare students for deeper independent research as part of their Master's project. 7COM1084+Research+specialism+re… Students begin by providing a clear introduction to their selected research specialism and explaining the broader research area in a way that is accessible to readers with general computer-science knowledge. The report then identifies the open research question presented in the relevant 7COM1084 specialist lecture paper, explains the problem in detail and evaluates why it is scientifically significant or relevant to a real-world application. 7COM1084+Research+specialism+re… A substantial literature-review section requires students to examine existing and related research beyond the specialist lecture paper. The aim is to identify what previous work has achieved, explain why existing approaches do not fully solve the research problem and identify further unresolved questions. 7COM1084+Research+specialism+re… The research-methods section focuses on the approaches used in the selected specialist paper. Students are expected to describe and critically evaluate those methods, considering both their strengths and limitations. They must then propose an alternative or extended research approach that could build on the published work and investigate related open problems, drawing on principles of experimental design and theoretical or practical research. 7COM1084+Research+specialism+re… The final reflective component asks students to explain their personal investment in the research area, including why the selected question interests them and how their own strengths and prior experience would support future research in that domain. 7COM1084+Research+specialism+re… The report must not exceed 2,800 words ±10%, must use the Harvard referencing system, and must include at least 20 references, one of which must be the relevant 7COM1084 specialist paper. 7COM1084+Research+specialism+re… 7COM1084+Research+specialism+re… 7COM1084+Research+specialism+re… Overall, the assessment integrates research specialism knowledge, literature review, open-problem identification, methodological critique, research design, future-work development and scholarly communication within a Level 7 computer-science research context.
Read Model Answer →
Software Engineering / Software Measurement and Process Models
2,000 words
Software Measurement, Goal–Question–Metric Analysis and Process Model Evaluation for DETO
This Measures and Models in Software Engineering coursework uses the Doolan Executive Taxi Service Online (DETO) case study to assess the application of software measurement techniques, Goal–Question–Metric analysis and software process modelling. The assignment requires students to connect quantitative software-engineering measures with practical organisational objectives and to critically evaluate suitable development-process approaches for a safety- and reliability-sensitive software system. 7COM1024_MMSE_ Def_CW_Brief 202… Task 1 focuses on software measurement using Unadjusted Function Points. Students analyse part of the DETO web-based email attachment system and identify relevant functional elements, including user inputs, reports to users, prompts and responses, interfaces to external systems or files, and internal logical files. Appropriate weights must then be selected to calculate the unadjusted functional-point value. 7COM1024_MMSE_ Def_CW_Brief 202… Task 2 requires application of the Goal–Question–Metric (GQM) approach to evaluate the effectiveness of the DETO website. Students identify the object under measurement and define the purpose, quality focus, viewpoint and context. They then develop two measurable organisational goals, formulate relevant questions for each goal and identify metrics that could be collected to evaluate website performance and support the company's priority of attracting new customers. 7COM1024_MMSE_ Def_CW_Brief 202… Task 3 moves from software measurement to software process models. DETO is considering a sophisticated on-board navigation system for its next generation of vehicles, where fast development, high quality, reliability and integration with the existing website are strategically important. Students select two software process models and critically evaluate their suitability for the project. The discussion should compare their distinguishing characteristics against alternative approaches, identify development challenges, evaluate project risks and pitfalls, and propose appropriate risk-mitigation strategies. 7COM1024_MMSE_ Def_CW_Brief 202… The main discussion for Task 3 is limited to 2,000 words ±10% and must use the Harvard referencing system, with at least 10 sources expected. The brief specifically requires original prose and prohibits bullet points, lecture materials and diagrams for this section. 7COM1024_MMSE_ Def_CW_Brief 202… Overall, the assessment integrates functional software measurement, GQM-based metrics, process-model evaluation, software quality, reliability, systems integration and project risk management within a realistic software-engineering business scenario.
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 →
Software Engineering / Object-Oriented Programming / Java Development
Java Group Exercise Booking and Management System for Furzefield Leisure Centre
This software-development coursework requires students to design and implement a Java-based booking and management system for Furzefield Leisure Centre (FLC). The proposed system manages member bookings for group exercise lessons delivered on Saturdays and Sundays. Exercise types can include Yoga, Zumba, Aquacise, Box Fit and Body Blitz, with each lesson accommodating a maximum of four members and carrying an exercise-specific price. 7COM1025 Coursework Explanation… The application must enable members to search the lesson timetable either by day or exercise type and make bookings subject to capacity constraints. Members may book multiple lessons, but duplicate bookings for the same lesson are prohibited. Existing bookings can be changed when capacity is available in the replacement lesson or cancelled before attendance. Successful changes must retain the existing booking ID while releasing the place held in the original lesson. 7COM1025 Coursework Explanation… 7COM1025 Coursework Explanation… After attending a lesson, members can provide a written review and a numerical rating from 1 to 5. Booking statuses should distinguish booked, changed, attended and cancelled reservations. The system must also generate management reports showing attendance and average lesson ratings and identify the exercise type producing the highest income, while listing income generated by each exercise category. 7COM1025 Coursework Explanation… 7COM1025 Coursework Explanation… Students must design at least eight weekends of timetable data, equivalent to 48 lessons, covering at least four exercise types. The program should be self-contained and does not require an external database or security protocol. 7COM1025 Coursework Explanation… The software-engineering component requires a UML class diagram, Java implementation, JUnit testing, version-control evidence and consideration of design principles, design patterns and refactoring. Students submit a PDF report containing the UML diagram and repository evidence, a ZIP containing source code, tests and an executable JAR, and a screen-recording demonstrating the final system. 7COM1025 Coursework Explanation… 7COM1025 Coursework Explanation… Overall, the coursework assesses practical object-oriented software development through system modelling, implementation, validation and reflective documentation. The marking allocates 40 marks to system functionality, 30 to design and implementation, 10 to UML, 10 to JUnit testing, 5 to version control and 5 to report quality. 7COM1025 Coursework Explanation… Note: the uploaded material identifies the code 7COM1025 but does not state the formal module title. I would therefore keep Module name = Not specified rather than inventing one.
Read Model Answer →
Computer Science
2,800 words
Specialism Research Report
The Specialism Research Report is an individual assessment for the Advanced Research Topics in Computer Science module. The assignment provides students with an opportunity to develop a deeper understanding of a selected computer science research specialism and to investigate an open research question within that area. The available research specialisms are Artificial Intelligence, Networking, Cyber Security, Software Engineering and Data Science. Students are expected to examine the research specialism associated with their degree route and develop their understanding of current research challenges, established techniques and potential future research directions. The report requires students to provide an overview of the research paper presented in the relevant 7COM1084 Research Specialism Lecture. The report must identify and explain the research question addressed by the specialist paper, consider why the research problem is scientifically interesting or relevant to a real-world application, and investigate possible approaches for addressing the question. Students must also identify further research that could build upon the existing work and consider their own personal strengths, interests and experience in relation to the proposed research. The report is structured into five main sections. The first section, Introduction of Research Specialism, provides a general overview of the selected research area and is intended to be accessible to readers with broad computer science knowledge. The second section, Open Research Question, identifies and explains the research problem discussed in the specialist lecture paper and considers its scientific or practical significance. The third section, Existing and Related Work, provides a literature review of research beyond the specialist paper, identifies limitations in existing approaches and discusses related open research problems. The fourth section, Research Approach, examines the methods used in the specialist paper, evaluates their strengths and weaknesses, and proposes an approach for extending the research. The fifth section, Personal Investment, explains the student's interest in the research question and evaluates their personal strengths and experience relevant to conducting the proposed research. Students are expected to use module reading materials and secondary research to support their discussion. The report must use Harvard referencing and include at least 20 references, including the 7COM1084 specialist paper. The references are excluded from the word count. The submission must not exceed 2,800 words, with a permitted range of ±10%. The assessment develops students' ability to understand established research techniques, identify research problems from relevant literature, propose alternative solutions, critically evaluate research literature, develop approaches for future research and communicate research knowledge effectively in a scholarly manner.
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 →