Currently, the most significant risk that could jeopardize the success of the project is the selection of which BLE tags we choose to purchase. Certain tags require more work to be programmed, and we need to keep in mind both our budget and the scope and requirements of our project when purchasing tags. We’re currently managing this risk by creating a pro/con list of possible tag purchases and keeping room in our budget for multiple tag purchases, should some of them not meet our needs.
One change we made to the existing design of the system was choosing to include the phone’s camera to streamline easier item registration using computer vision. This change was necessary because the user burden of initial item registration was brought up as a concern by our project advisor, Professor Kim, and we agreed that having to manually register each tagged item might prove too big a burden for most users (particularly if they have many items). The costs that this change would incur include placing a larger performance burden on the user’s phone and adding much more complexity and risk to our project. We hope to mitigate these costs by finding relevant work related to item recognition and are prepared to default to manual item registration, should this aspect of our project not succeed.
Our current schedule can be found here (slack time and tasks are currently not finalized).