Boat Control: Users

User Interviews

The users and their needs

In order to fully grasp what this app needs to do I first wanted to zero in on the target audience. In this case my target audience would be boat enthusiasts. once I had determined this I set out to compile a list of questions for my audience so that I can get their input on some of my designs, choices and problems that I have come across. The result of these interviews can be seen by clicking the image to the left.

After the interviews were done I made a requirements list with the client. This is the MoSCoW analysis that you see below.

MoSCoW Analysis

Must:

Be able to discover, pair and connect to bluetooth device
Be able to send data to bluetooth device
Be able to receive data from bluetooth device

Should:

Have a customisable UI
Be able to add your own buttons and functionality
Automatically connect to correct bluetooth device
Be able to read status of various sensors and features from bluetooth device
Be able to send alerts and alarms to the user for various sensors
Have encryption for any sent commands between the user and the bluetooth device

Could:

Also work over WiFi
Support multiple users at the same time
Have cross platform support

Won’t:

Upload any data to the internet / Have a connection to the internet
Be available outside of the local network
Drain a lot of battery on the bluetooth module side

Interview

Stakeholder interview

Interview Stakeholder Matthijs

Summary

The stakeholders expressed an interest in ease of use. Everything the app does can also be done in one way or another using already existing instruments on the boat. So the app needs to be faster in every scenario. It needs to also use very little power, that's why we chose for Bluetooth Low Energy. We thought about multiple ways to control the app, like voice commands or camera functions but the stakeholders wanted the app to be more consistent and reliable so we stuck with touch controls. They were happy with the concept design that were made and we devised a priority list (MoSCow) for the order in which functionality should be implemented.

Page updated

Google Sites

Report abuse