Evaluation
Summary of Achievements
MoSCoW Requirements
| Requirement Description | Type | Priority | State | Contributors |
|---|---|---|---|---|
| AI Chatbot to help and enhance the user's experience on the platform. | Functional | Must | ✔︎ | Emir |
| Voice input for AI chatbot and the Booking page. | Functional | Must | ✔︎ | Nicholas, Efe |
| Accessibility Features including Text-To-Speech, High Contrast Mode, Adjustable Font Size, Screen Reader and different fonts. | Functional | Must | ✔︎ | Nicholas, Efe |
| Booking Time Slots through a weekly grid with support for longer visits (Multiple timeslots). | Functional | Must | ✔︎ | Nicholas |
| Future Bookings with ability to navigate to future weeks and book in advance. | Functional | Must | ✔︎ | Nicholas |
| Email Confirmation for booking confirmations. | Functional | Must | ✔︎ | Efe |
| Display café menu items on a separate page to allow for browsing of items and preparing of their order in BSL. | Functional | Should | ✔︎ | Efe |
| Able to view how busy the café is for any given timeslot. | Functional | Should | ✔︎ | Nicholas |
| The frontend should have a responsive layout which adapts to various screen shapes and sizes. | Functional | Should | ✔︎ | Pratham, Nicholas |
| AI chatbot can go through the booking process if given the necessary information. | Functional | Could | ✔︎ | Nicholas, Emir |
| AI chatbot should have access to database information, e.g., booking availabilities. | Functional | Could | ✔︎ | Nicholas, Emir |
| Option to make booking public/private and see other public bookings. | Functional | Could | ✗ | N/A |
| Option to book certain locations in the cafe. | Functional | Could | ✗ | N/A |
| Able to amend booking information (CRUD). | Functional | Could | ✗ | N/A |
| Able to share booking on social media (Instagram, Facebook, etc.). | Functional | Could | ✗ | N/A |
| The system must be easy to use and navigate for all users. | Non-Functional | Must | ✔︎ | Pratham, Nicholas, Efe, Emir |
| The system must be easy to update and maintain, with well designed and documented code. | Non-Functional | Must | ✔︎ | Pratham, Nicholas, Efe, Emir |
| The AI chatbot must not be able to produce harmful or offensive content. | Non-Functional | Must | ✔︎ | Pratham, Nicholas, Efe, Emir |
| User data should be stored and transmitted securely. | Non-Functional | Should | ✔︎ | Pratham, Nicholas, Efe, Emir |
| The system should be able to scale to support additional users and features. | Non-Functional | Should | ✔︎ | Pratham, Nicholas, Efe, Emir |
| The system should be compatible with external accessibility tools such as screen readers. | Non-Functional | Should | ✔︎ | Pratham, Nicholas, Efe, Emir |
| The system could support multiple languages. | Non-Functional | Could | ✔︎ | Pratham, Nicholas, Efe, Emir |
| The system could be able to handle multiple users and load quickly. | Non-Functional | Could | ✔︎ | Pratham, Nicholas, Efe, Emir |
| The system won't support offline mode. | Non-Functional | Won't | ✗ | Pratham, Nicholas, Efe, Emir |
| The system won't support legacy browsers. | Non-Functional | Won't | ✔︎ | Pratham, Nicholas, Efe, Emir |
Individual Contributions
| Work Type | Pratham | Nicholas | Efe | Emir |
|---|---|---|---|---|
| Client Liaison | 15% | 10% | 10% | 65% |
| HCI | 25% | 25% | 25% | 25% |
| Requirement Analysis | 15% | 30% | 30% | 25% |
| Research | 25% | 25% | 25% | 25% |
| AI | 5% | 20% | 5% | 70% |
| Diagrams | 20% | 20% | 50% | 10% |
| Pitch Presentation | 70% | 10% | 10% | 10% |
| Deployment | 5% | 50% | 30% | 15% |
| Accessibility | 15% | 30% | 35% | 20% |
| Frontend | 10% | 40% | 40% | 10% |
| Backend | 5% | 40% | 20% | 35% |
| Testing | 10% | 60% | 25% | 5% |
| Development Blog | 70% | 20% | 5% | 5% |
| Website Editing | 35% | 25% | 30% | 10% |
| Video Editing | 70% | 10% | 10% | 10% |
| Overall Contribution | Equal | Equal | Equal | Equal |
| Roles | Team Leader, Programmer, Client Liaison, Report | Researcher, Programmer, Report Writer | Developer, Designer, Tester | Programmer, Client Liaison, Researcher |
Critical Evaluation
We conducted a comprehensive evaluation of our project across several key dimensions to assess its success and identify areas for improvement.
User Interface / Experience
The interface successfully prioritizes accessibility with features like high contrast mode and adjustable fonts. User testing showed positive feedback for navigation and readability, though some users initially found the AI chatbot interface challenging. Voice commands and BSL videos enhanced the overall user experience.
Functionality & Stability
Core features like booking management and AI assistance were successfully implemented with robust error handling. The system maintains stability under normal usage, though AI response generation shows occasional latency. Advanced features were properly prioritized using MoSCoW analysis.
Efficiency & Performance
Quick response times achieved for most operations, with booking confirmations processed within seconds. Database queries are optimized with proper indexing. The AI assistant responds within 2 seconds on average, though BSL video loading times could be further optimized.
Compatibility & Maintainability
The application demonstrates consistent performance across major browsers and devices with responsive design. The codebase follows clean architecture principles with comprehensive documentation and unit tests. Regular code reviews and consistent styling ensure maintainability, while clear version control facilitates updates.
Project Management
Agile methodology with weekly sprints and regular client meetings proved effective. Most deadlines were met, with some features requiring timeline adjustments. Communication was maintained through regular stand-ups and documentation sharing, though task distribution could be improved in future projects.
Future Work
With additional time and resources, the project could be extended in several ways to enhance its functionality and user experience.
Enhanced AI Capabilities
Implementation of more sophisticated natural language processing for complex queries, multilingual support for international users, and development of personalized user interaction patterns based on usage history.
Advanced Booking Features
Development of recurring booking system for regular visitors, waitlist functionality for popular time slots, and a comprehensive event management system for organizing community activities.
Administrative Tools
Creation of a full-featured admin dashboard for café staff, implementation of detailed analytics and reporting tools, and addition of staff scheduling and resource management features.
Enhanced Accessibility
Expansion of BSL video content for more menu items and common phrases, implementation of more sophisticated voice command features, and addition of support for additional assistive technologies.
Technical Improvements
Implementation of offline mode support for basic functionality, optimization of performance for faster load times, and enhancement of security features for better user data protection.