The biggest risk to the project is still all of the logistics that come with mounting our system to the glasses. We need to ensure that everything is mounted securely while still keeping a minimal footprint with all of our wiring, and ensuring that our LCD will be readable. This risk is being managed mainly with our being ahead of schedule leaving us plenty of time to work out any difficulties that come with mounting. We are also continuing to keep in mind the suggestion of pivoting to a handheld system as a last resort.
No changes have been made to the design or our schedule.
Both our verification and validation will be described following, because our subsystems basically fully integrated and so all of our forms of testing will be collaborative within in the team in some way.
In terms of verification, the main metrics we need to test are end-to-end accuracy and latency, as well as connection angle and distance. Based on some initial testing, we don’t believe angle and distance will have a significant impact on accuracy and latency, it appears to be an all or nothing connection, so our tests for those will be separate.
For our accuracy and latency, we will be using around 5-10 spoken and computer generated passages of vary accents and speeds to measure both metrics. Each passage will be repeated around 3 times with averages of different wpm and overall averages taken for our reporting. During this, we will also perform stress tests involving disrupting the line of sight to ensure full functionality. These reported metrics will map directly back to the matching use case and design requirements.
For our angle and distance, we will be transmitting simpler passages compared to above to simply check for a connection. We will do this ranging from 3-15 ft and a 40 degree range and constructing a graph of where connection is possible. This will allow us to provide a visual representation of where our system is usable.
For validation we will be utilizing our friends and hopefully volunteers who are hard of hearing or deaf to provide feedback on the usability of our system. We will be creating a survey that captures our more qualitative requirements, such as how it feels to wear and how obstructive it is.