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 | Android app that establishes Bluetooth connections with Smart TV, computer of tablet | Must | ✓ | Hugh, Ulk, Robbie |
| 2 | Bluetooth connection should not require additional software | Must | ✓ | Hugh, Ulk, Robbie |
| 3 | Mouse controller | Must | ✓ | Hugh |
| 4 | Keyboard controller | Must | ✓ | Ulk |
| 5 | Gamepad controller | Must | ✓ | Robbie |
| 6 | MotionInput support and integration for Face, Hands and Eyegaze | Must | ✓ | Hugh + Ulk + Masters Team's |
| 7 | Settings pages | Must | ✓ | Hugh, Robbie |
| 8 | Dark and light Mode | Should | ✓ | Hugh |
| 9 | Speech input to control app navigation | Should | ✓ | Hugh + Masters Teams's |
| 10 | Speech controlled keyboard over Bluetooth | Should | ✓ | Ulk + Masters Team's |
| 11 | Auto Bluetooth reconnect setting | Could | ✓ | Hugh |
| 12 | Make the device discoverable to connect from other devices | Could | ✗ | N/A |
| 13 | Ability to add and remove key-binds for MotionInput mode in settings | Could | ✗ | N/A |
| 14 | Profiles to retain settings and presets for each user | Wont | ✗ | N/A |
Known Bug List
Our team used the GitHub issues page as the main way of tracking and fixing known bugs within our app. Over the development process we identified 21 different bugs and issues which were all succinctly reported and tracked on GitHub. We are pleased to say that as of finishing the project we issued fixes for all known bugs and the only outstanding issue is for extending support to older versions of Android.
| ID | Known Bug | Priority |
|---|---|---|
| 1 | No support for Android versions 10 and below. #16 | Low |
Induvidual Contributions
| Work Packages | Hugh | Robbie | Ulk |
|---|---|---|---|
| Project Partner Liaison | 95% | 0% | 5% |
| Other Teams Liaison | 75% | 0% | 25% |
| Requirement Analysis | 20% | 20% | 60% |
| HCI | 33% | 33% | 34% |
| Research & Experiments | 33% | 33% | 34% |
| UI Design | 25% | 50% | 25% |
| Coding | 50% | 15% | 35% |
| Testing | 75% | 0% | 25% |
| Project Website | 43% | 42% | 15% |
| Presentation Planning | 0% | 100% | 0% |
| Video Editing | 5% | 90% | 5% |
| Overall | 36% | 31% | 33% |
| Main Roles | Client Liaison, Programmer, Tester | Report Editor, UI Designer, Researcher | Programmer, UI Designer, Tester |
*Note: Each task is not weighted equally, and as such the overall contribution numbers may not add up to the exact overall values.
Critical Evaulation
- User Interface & Experience
- Functionality
- Stability
- Efficiency
- Compatability
- Maintainability
- Project management
During the project we always ensured our project would meet the requirements of the end user. We frequently tested in lab sessions with a broad range of different users to measure the success of our requirements. We adopted a similar UI design to many mobile applications, using a single navigaton bar at the bottom of the screen in order to move between pages. We found that this gave familiarity to what users have experienced before, therefore, they were fast in learning the apps flow.
Lots of work was undertaken to ensure the UI was responsive to users interactions. All buttons have custom press animations, the trackpad uses a dynamic finger tracker that follows the users movement on the screen and error messages are display in an informative and descriptive manner that is useful for users.
The colour theme used is also clean, consistient and well balanced so that it is easy on the users eyes, assessible and visually appealing for users.
Overall, we rate ourselves great in this section.
Our app provides full functionality for three seperate input types: Mouse, Keyboard and Gamepad. These modes deliver the same functionality as a standard mouse and keyboard for each of these input modes while also providing usful preset settings and modifiable key presets for each.
The Bluetooth functionality is capable of discovering all nearby Bluetooth devices, making connections and sending user input over Bluetooth.
Overall, we think we did a great job on implementing the expected functionalities.
Throughout the project, our team executed a comprehensive testing protocol encompassing both automated and manual procedures. Our automated testing framework evaluated the stability of individual classes in real-time on an Android device through instrumented tests. We also generated a comprehensive code coverage report, indicative a high level of test coverage.
Furthermore, substantial time was spent undertaking user testing conducted by both our team and potential end-users, ensuring the app's usability and stability. We are pleased to confirm that all significant bugs identified during testing have been addressed, instilling confidence in the stability of our application for deployment and release.
Overall, we think we did a good job on stability.
Efficiency is a critical aspect of any user application, as any inefficiencies can deter users from adopting the product. Our team conducted performance testing on the final build of the app using Android Studio's profiler, and we're pleased to says that we identified no bottlenecks while measuring both CPU and memory usage during a sustained usage test. Additionally, we have implemented the utilization of multiple threads, particularly in the Bluetooth transmission code, to enhance the efficiency of our application.
Overall, we thing we did good on efficiency.
During development we considered backwards compatibility to make sure our application can run on as many devices as possible. Due to the ever evolving Android frameworks for different Android versions that proved to be hard in places but we are happy to say our app is compatible with Android versions 11.0 and above. This coveres the majoriy of current Android devices in use today. Although, we would have hoped to extend support even further back we still consider this as a success.
We had also intended to extend support to Chromebooks. However, due to a difficulty with access to Bluetooth HID profiles when running ChromeOS this was not possible. After a discussion with our project partner, Dean, we all agreed it was best to focus on the Android app support.
Overall, we think we did an good job on compatability.
Throughout the project lifecycle, we maintained a commitment to adhering to best practices and producing clean, well-structured code. Every method and class is documented with JavaDoc comments, providing comprehensive explanations of parameters and functionality. Our directory structure is clearly organised, facilitating clarity and ease of navigation, with all components arranged in a logical and intuitive manner.
Each class is dedicated to a distinct process, following encapsulation principles, enhancing modularity and maintainability. This concerted effort results in a codebase that is highly readable and accessible, allowing new developers to contribute to the project.
Overall, we think we did a great job on maintainability.
The project was effectively coordinated through weekly lab sessions where tasks were organized and distributed among team members. GitHub's integrated tools were employed for issue tracking and ensuring that only functional code was merged into the main branch via pull requests. A Gantt chart was utilized to establish a project timeline and meet deadlines, facilitating successful completion. Additionally, weekly meetings were held with our project partner to communicate progress and gather feedback.
Overall, we thing we did a great job on project management.
Future Work / Plan
If we had more time we would extend the project in the following ways:
-
The first thing on the future development plan for this project would be to optimise the application and improve performance. Enhancing the application's performance would ensure better operation across a wider range of devices, particularly those with lower specifications. This would involve further optimization through threading and simplification of certain components to reduce complexity, ultimately aiming for smoother functionality across all device levels.
-
The second improvement we would make would be to implement user profiles. Currently, users have to setup the app manually every time the app is shutdown, and this is a problem for our target user base who are disabled or injured. They have to get a helper to set up the app or spend a significantly long period of time struggling to get it all working. User profiles which store settings would improve the user experience significantly. This would also enable multiple individuals to utilize the same device with personalized settings and presets. By saving configurations to individual profiles rather than the app itself, users can effortlessly switch between preferences, ensuring a better experience for each user.
-
The third thing on the list of things to do would be making the app discoverable to other devices to expand the supported set of ways users can pair with target devices. Currently, our app can not be made discoverable to other devices to connect. This means that connection is only one directional, from the app to another device. However, Bluetooth supports handshakes from both directions, regardless of which device is the controller and which is the reciever. Since some devices can only pair via this method, it will make the app accessible to larger amount of potential devices.
-
The lowest priority next step would be to extend layout configurations to support landscape mode, thereby improving the user experience, especially on Android tablets. This would involve creating dedicated layout pages for landscape orientation, ensuring optimal usability across different device types.