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 →