Evaluation
Summary of Achievements
MoSCoW Table
Contributors
PG - Parth Gandhi, RB - Rasul Bakhodirov, DL - Declan Loo, RGG - Roshan Gani Ganithi
| ID | Description | Priority | State | Contributor |
|---|---|---|---|---|
| 1 | The website/application must be able to fetch and display reports dynamically from the server. | Must | ✔ | DL,RGG |
| 2 | Users must be able to add new reports with geolocation data and optional images. | Must | ✔ | RB,RGG |
| 3 | Users must be able to interact with the chatbot by typing queries and receiving responses. | Must | ✔ | PG |
| 4 | The chatbot must update its interface dynamically with user and bot messages. | Must | ✔ | PG |
| 5 | The chatbot must use geolocation data to enhance its responses. | Must | ✔ | PG,DL |
| 6 | The header on the website must provide a navigation menu with links to all major pages (Home, Reports, Chatbot, About Us, Socials). | Must | ✔ | RGG |
| 7 | The website must include a mobile-friendly toggle menu for smaller screens. | Must | ✔ | RGG |
| 8 | Users must be able to view reports on the reports page. | Must | ✔ | RB,RGG |
| 9 | The reports page must display a list of reports with details such as name, category, latitude, longitude, and description. | Must | ✔ | RGG |
| 10 | If an image exists for a given report, the user must be able to view this image when viewing the report. | Must | ✔ | RGG,DL |
| 11 | The website must display markers for reports on the map, including additional details when the user clicks on the marker. | Must | ✔ | RGG |
| 12 | Allow the user to use augmented reality to view the location of a report on their camera. | Must | ✔ | PG |
| 13 | The user must be able to see the AR pin get larger and smaller as they move closer and further from the location of the report. | Must | ✔ | DL |
| 14 | Users should be able to upload images with reports. | Should | ✔ | RB,RGG |
| 15 | Users should be able to view the report details on the home screen of the app, for a given AR pin. | Should | ✔ | PG |
| 16 | An AI summary of the report description should be shown alongside the report. | Should | ✔ | PG |
| 17 | The website should display clickable logos for social media platforms on the Socials page. | Should | ✔ | RGG |
| 18 | Users could be able to search for reports by name, category, or description on the Reports page. | Could | ✔ | RGG, RB |
| 19 | Users could be able to filter reports by category on the Reports page. | Could | ✔ | RGG |
| 20 | Users could be able to sort reports by name, category, or date on the Reports page. | Could | ✖ | NA |
| 21 | The website could display a group picture and detailed descriptions of each team member on the About Us page. | Could | ✔ | RGG |
| 22 | The website won't function offline. | Won't | ✔ | NA |
| 23 | The website won't provide a chat function for users to talk to each other about their community. | Won't | ✔ | NA |
| 24 | The application won't be available on platforms aside from Android. | Won't | ✔ | NA |
Known Bugs
| Bug | Description | Severity | Proposed Fix |
|---|---|---|---|
| 1 | When there are many reports within a few metres of one another, the AR pins start to stutter. | Medium | Implement clustering for AR pins to reduce overlap and stuttering. |
| 2 | Occasionally, the images on the website and application are rotated 90 degrees. | Low | Check and correct the image orientation metadata before displaying the images. |
| 3 | When the app is open for prolonged periods of time, it will unexpectedly close. | High | Investigate memory leaks and optimize resource usage to prevent crashes. |
| 4 | The chatbot on the website does not read the history of the conversation when generating responses. | Medium | Store and pass the conversation history to the chatbot's backend for context-aware responses. |
Individual Contribution
| Work Packages | Parth | Roshan | Rasul | Declan |
|---|---|---|---|---|
| Project Partners Liaison | 80% | 5% | 5% | 10% |
| Requirement analysis | 25% | 25% | 25% | 25% |
| Research and Experiments | 40% | 20% | 20% | 20% |
| UI Design | 10% | 10% | 40% | 40% |
| System Design | 20% | 30% | 20% | 30% |
| Coding | 25% | 25% | 25% | 25% |
| Testing | 20% | 0% | 80% | 0% |
| Report Website | 10% | 25% | 25% | 40% |
| Videos & Scripts | 10% | 90% | 0% | 0% |
| Overall Contribution | 25% | 25% | 25% | 25% |
Critical Evaluation
User Interface / User Experience (UI/UX):
The user interface is clean and intuitive, making it easy for users to navigate through the application. However,
some users reported that the AR pins could be overwhelming in dense areas, which affects the overall experience.
Improvements in clustering and better visual cues could enhance the usability.
Functionality:
The application meets most of the functional requirements, including dynamic report fetching, chatbot interaction,
and geolocation-based features. However, occasional issues like image rotation and chatbot context limitations
indicate areas for improvement.
Stability:
The application is generally stable, but prolonged usage can lead to unexpected crashes, particularly on older
devices. This highlights the need for better memory management and resource optimization.
Efficiency:
The application performs well under normal conditions, but efficiency drops when handling a large number of reports
or AR pins. Optimizing algorithms for AR rendering and data processing could significantly improve performance.
Compatibility:
The application is compatible with Android devices and modern web browsers. However, expanding support to iOS and
other platforms would make it more accessible to a broader audience.
Maintainability:
The codebase is modular and well-documented, making it relatively easy to maintain and extend. Future integration of
new features or APIs should be straightforward, given the current architecture.
Project Management:
The project was well-organized, with clear task distribution and regular progress updates. However, some delays were
encountered due to unforeseen technical challenges, which could be mitigated with more robust risk management
strategies in future projects.
Future Work
The project could be extended in the following ways if more time and resources were available:
- Implement advanced clustering algorithms for AR pins to handle dense areas more efficiently.
- Enhance the chatbot's capabilities by integrating natural language processing (NLP) models for better context-aware responses.
- Develop offline functionality for the application to allow users to access reports and features without an active internet connection.
- Introduce additional accessibility features, such as screen reader support and high-contrast modes, to improve usability for users with disabilities.
- Expand the application to support multiple platforms, including iOS and web-based AR experiences.
- Integrate real-time collaboration features, allowing users to share and discuss reports within the application.
- Incorporate machine learning models to provide predictive insights and trends based on report data.
- Improve the application's performance and stability by optimizing resource usage and addressing known bugs.
- Enhance the UI/UX design with more intuitive navigation and interactive elements.
- Develop a comprehensive analytics dashboard for administrators to monitor and manage reports effectively.