Collect use cases for vehicle interface
Description
Purpose
In order to develop a scalable and cohesive vehicle interface, we must determine the use cases the vehicle interface must satisfy.
To do this, we should collect use cases such as:
- What platforms the vehicle interface might support (i.e. open street drone, prius, forklift, etc...)
- What DBW/CAN interfaces the interface might support (SocketCAN, Kvaser, proprietary etc...)
- What inputs this might support (i.e. speed, and curvature; throttle and steer angle, etc...)
- What behaviors this might support at different levels (i.e. state machine, steering/speed control, reporting vehicle parameters etc...)
Definition of Done
-
A collection of use cases has been defined, accepted as valid use cases
Edited by Joshua Whitley