Autonomous mobility scooter requirements: Difference between revisions
Line 18: | Line 18: | ||
== smart mobility == | == smart mobility == | ||
- the mobility scooter should have a display <br> | - the mobility scooter should have a display <br> | ||
- a user can set his destination with the display | - a user can set his destination with the display <br> | ||
- a user should not have to take more than 5 seconds to get in to the mobility scooter | - a user should not have to take more than 5 seconds to get in to the mobility scooter | ||
== physical == | == physical == |
Revision as of 14:20, 25 February 2018
in order to make a product or a model of the system, it must first be decided what the actual requirements and limitations of our model are. with these requirements we can see what our model should eventually do.
we have split the requirements in four different sections, to split main parts of the system.
navigation: these requirements concern everything to with the software and navigation, what it should, can, cannot or should not do.
safety: these requirements concern safety issues of a mobility scooter.
smart mobility: these requirements concern how to enhance the mobility scooter such that it responds to the requests of the user.
physical: these requirements concern the actual hardware that is needed for the mobility scooter.
- the mobility scooter is able to navigate through a shop
- the mobility scooter can use lifts
safety
- the mobility scooter should drive 5 km/h or less on a walking path
- the mobility scooter should not get closer than 10 centimetres to another person while driving.
- if the autonomous system detects a failure, it should notify the user
smart mobility
- the mobility scooter should have a display
- a user can set his destination with the display
- a user should not have to take more than 5 seconds to get in to the mobility scooter