Filter by keyword, subject, or both. Updates live as new model answers are added to our portal.
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 →
Security of Emerging Connected Systems
2,000 words
Security Evaluation – Secure Design, Security Audit and IoT Security Recommendations
This individual coursework for the Security of Emerging Connected Systems module requires students to prepare a 2,000-word technical report evaluating secure design, security auditing and security recommendations for an organisation developing Internet of Things (IoT) devices and systems for home and workplace environments. The assessment is worth 10 credits and requires students to provide practical and evidence-based guidance to the client’s software development team. The report is assessed across secure design and development methodology, security audit methodology, security recommendations and overall report structure. The first major section addresses Secure Design and Development Methodology. The client wants to incorporate secure design principles into its software development workflow and therefore requires an overview of possible secure design processes relevant to IoT. Students must evaluate the strengths and weaknesses of different approaches and provide a justified recommendation for a process that would be appropriate for the client. The emphasis is on integrating security into the design and development of systems rather than treating security as a separate activity after development. The second section focuses on Security Audit Methodology. The client wants to complement its secure design process with a security audit of the final developed system. Students must provide a practical guide explaining how a security audit could be performed, including the overall testing methodology and the purpose of each stage. The brief identifies methodologies such as PTES and OWASP as examples. Students are also expected to discuss different approaches and evaluate their respective strengths and weaknesses. The third section concerns Security Recommendations and requires students to demonstrate the implications of strong secure design and auditing through an IoT security case study. Students must research a security vulnerability affecting an IoT device, explain the vulnerability and identify where the security flaw was introduced. The report must then examine which parts of the secure design and audit processes were not implemented correctly and evaluate the resulting impact on the security of the product. The report is intended for a technical audience, specifically the client's software development team. Students are expected to use an appropriate technical structure and language, support their arguments and analysis with references, and use APA referencing. The assessment also encourages appropriate diagrams to support the written content. The report structure component accounts for 10% of the assessment, while Secure Design and Development Methodology, Security Audit Methodology and Security Recommendations each account for 30%. The coursework assesses learning outcomes relating to defence-in-depth solutions for technical internet security vulnerabilities, secure private networks for IoT and BYOD, and current research and technological advances in network security. These outcomes connect the assignment to practical IoT security engineering, secure development, security auditing and emerging network-security practices.
Read Model Answer →
Secure Design and Development
2,000 words
Secure Design and Development – PixelForge Nexus (UITS)
This assessment for Coventry University’s Secure Design and Development module requires students to design and develop a functional secure online system with the aid of a Large Language Model (LLM). The assignment is based on a practical scenario involving Creative SkillZ LLC and its proposed “PixelForge Nexus” system. The submission combines a functional prototype, an individual 2,000-word report, source code hosted in the Coventry University GitHub environment, and a video report demonstrating the completed prototype. The PixelForge Nexus prototype is intended to provide secure project management and basic asset and resource management for a game-development environment. Core functionality includes adding and removing projects, viewing active projects, assigning developers to projects, allowing developers to view their assigned projects, uploading project documents, and allowing authorised users to access documents associated with their projects. The system must implement privilege separation between Admin, Project Lead and Developer roles. Security is a central requirement of the assignment. Administrators are responsible for managing projects and user accounts, Project Leads can assign developers and upload project documents, while Developers can view assigned projects and associated documents. The system must include a robust login mechanism with secure password hashing and storage, with Multi-Factor Authentication recommended as an additional security measure. Proposed pages include Sign In/Register, a role-based User Dashboard, Account Settings and a Project Details page. The practical assessment evaluates four major areas: System Design, Security Testing and Analysis, System Development, and Formal Methods. System design requires consideration of secure design principles and their application to the development lifecycle. Security testing requires critical evaluation of security techniques, identification of issues and proposed mitigation measures. System development requires a functional prototype that follows the proposed design and considers legal and ethical requirements. Formal methods require a behavioural model and appropriate verification techniques to establish whether the system meets its specification. The individual report must document the methods and techniques used to develop the prototype and discuss the stages of the development lifecycle, including specification, design and development. It must also explain the deployment and testing approach, limitations of the prototype, possible improvements, security techniques and the formal model used. The submission must include links to the Coventry University GitHub repository and Microsoft OneDrive video, while the required appendix contains the LLM prompt history and other resources used with APA-style referencing.
Read Model Answer →