Evaluation
MoSCoW List Evaluation
Functional Requirements
We are pleased that our product completes 100% of the MUST and SHOULD and some of the COULD MoSCoW requirements. The full achievement table is shown below:
| ID | Requirement | Priority | Completed | Contributors |
|---|---|---|---|---|
| 1 | Users authentication (login/signup) | Must | ✓ | Ibrahim, Mouid |
| 2 | Content Management tools | Must | ✓ | All |
| 3 | Use of Gen-AI for enhanced user experience and content generation tools | Must | ✓ | All |
| 4 | Interactive map displaying reported issues and events | Must | ✓ | Mouid, Nayeem |
| 5 | Reporting system (creation, editing, status updates) | Must | ✓ | Ibrahim |
| 6 | Differentiation between content manager and user account types | Should | ✓ | Mouid |
| 7 | Mobile Responsiveness | Should | ✓ | All |
| 8 | Detailed event information pages | Should | ✓ | Mohamad |
| 9 | Enhanced content creation for content managers | Should | ✓ | Mohamad, Mouid, Nayeem |
| 10 | Settings customisation (logo, business info, limit boundaries of the community etc.) | Should | ✓ | Ibrahim |
| 11 | Reported issues discussions and upvoting | Should | ✓ | Ibrahim |
| 12 | Extraction of content from PDF/ICS files to automatically create events/articles | Could | ✓ | Nayeem |
| 13 | Semantic search for events/articles | Could | ✓ | Mohamad |
| 13 | Personalised content recommendations of events/articles | Could | N/A | |
| 14 | Community sentiment analysis and automatic issue prioritisation | Won't | N/A | |
| 15 | Automatic report classification/forwarding | Won't | N/A |
Known Bug List
We have used the GitHub issue tracker to keep track of all the bugs that have been identified during the development process. Over the development process we identified 20 bugs in total, 17 of which have been fixed. The outstanding bugs are show below:
| ID | Description | Severity |
|---|---|---|
| 1 | On startup, the home page map displays boundaries in Los Angeles even when set boundaries are elsewhere | Low |
| 2 | On the reporting page, a gray rectangle can appear when interacting with and closing the sidebar | Low |
| 3 | Uploading ICS file encounters a 500 error in certain circumstances | Medium |
Individual Contributions
| Work Packages | Ibrahim | Mohamad | Mouid | Nayeem |
|---|---|---|---|---|
| Project Partner Liaison | 40% | 40% | 10% | 10% |
| Requirement Analysis | 25% | 25% | 25% | 25% |
| HCI | 30% | 30% | 20% | 20% |
| Research & Experiments | 20% | 20% | 30% | 30% |
| UI Design | 25% | 25% | 25% | 25% |
| Coding | 25% | 25% | 25% | 25% |
| Testing | 70% | 10% | 10% | 10% |
| Report Website | 25% | 25% | 25% | 25% |
| Presentation | 20% | 60% | 10% | 10% |
| Video Editing | 10% | 10% | 40% | 40% |
| Overall Contribution (average) | 29% | 27% | 22% | 22% |
*Note: Each task is not weighted equally, and the number of tasks completed does not necessarily reflect the amount of work done by each team member.
Critical Evaluation
User interface / user experience
We've created a clean, cohesive look across all our frontend pages with custom styling on each component and error feedback on every form. Through design iterations, user testing, and client feedback, we've refined the user experience into something that's both fun and easy to navigate. While we didn’t include animations, the design has been well-received, especially for its smooth, mobile-friendly experience.
Overall, we would rate ourselves very good in this category.
Functionality
Our platform is powered by complex, well-documented, and highly efficient algorithms. From the detailed reporting page to the semantic search and local large language model (LLM) integration, we've pushed the boundaries of what's possible in creating an engaging and innovative community impact report portal.
Feedback has shown that users are particularly impressed with the AI-driven features, which allow for a more personalized and efficient experience. The ability to differentiate between businesses and customers was highlighted as a standout feature, enabling more tailored interactions and enhancing the platform's overall usability.
We would rate ourselves very good in this category.
Stability
Our platform’s stability is backed by thorough integration testing, which ensures smooth performance and minimizes disruptions. This has helped us fix many bugs, making the system more reliable. However, there’s still room for improvement by adding more frontend tests to cover all pages, ensuring consistent performance across different scenarios and devices, and further boosting the user experience.
We would rate ourselves very good in this category.
Efficiency
Our platform delivers strong efficiency, with fast rendering times and minimal slowdown. Users experience smooth performance, with only slight stutters during AI model loading—an expected delay due to its complexity. Pages with heavy styling and many components, like the reporting page, maintain consistent speed without noticeable lag. Our backend semantic searches are also highly efficient, even when running live on Azure, providing quick, accurate results without sacrificing performance.
Overall, we would rate ourselves very good in delivering an efficient platform.
Compatibility
We tested every major platform (Windows, Mac and Linux) to ensure our frontend and backend worked perfectly. Our application runs on modern web browsers, but LLMs are disabled on mobile, due to performance.
We would rate ourselves good in this category.
Maintainability
We’ve focused on maintaining high cohesion and low coupling in both frontend and backend components. While some pages, like the reporting page, could be refactored for better maintainability, the backend is well-commented for easier understanding and upkeep.
We would rate ourselves good on this section.
Project management
We used GitHub for version control and collaboration throughout the project, documenting over 50 pull requests and tracking more than 40 issues. This kept the development process organized and transparent. Team members reviewed each other’s changes, which helped everyone stay aligned and understand the project as a whole. GitHub comments were crucial for communication, allowing us to provide thoughtful feedback and maintain a steady workflow without relying on instant messaging.
We followed strict GitHub workflows, never committing directly to the main branch and ensuring pull requests focused on specific changes. This helped us keep the code clean and allowed us to add extra features beyond our initial priorities. The MoSCoW prioritization method helped assign tasks, focusing on the most critical features first. Weekly meetings kept us aligned, with regular reviews of functionality, pitches, demos, and other materials, all contributing to the project’s success.
We would rate ourselves very good in this category.
Future Work and Improvements
If we were to continue working on this project, there are several areas we would focus on to improve the application further:
-
The first thing we would like to add is the Personalised Content Recommendations feature. This would allow users to receive content suggestions based on their preferences and behaviour on the platform. It would also enhance the user experience and engagement on the platform. This was one of our Could Have features on the requirements list.
-
The second improvement we would like to make is to implement an Automatic Report Classification/Forwarding feature. This would involve implementing a system to automatically classify and forward reports to relevant authorities based on the type of issue reported. This would streamline the process of handling reports and ensure that they are directed to the appropriate authorities promptly. This was one of our Won't Have features on the requirements list, as we did not have the time to implement it during the project timeline, but we believe it would be a valuable addition to the platform.
-
When receiving user testing feedback, one suggestion made by Sam (See the User Acceptance Testing section) was that a potential client of our web app could also be building managers, not just local councils. The structure is currently designed for local councils to manage their community, but this could be expanded to include building managers who want to manage their building community. There would need to be tweaks such as changing the interactive maps to show the building layout and adding features such as booking the gym or having a services section to include a list of repairmen that can be contacted. This would be a significant change to the platform and would require further research and development to implement effectively.
-
Another improvement could be AI to optimise the site dynamically adjusting its layout and content to align with prompts given to it, such as "Sustainability Week." It could analyse existing content and prioritise relevant articles, events, products, and initiatives based on the theme.