| [2] | 1 | REQUIREMENTS
|
|---|
| 2 |
|
|---|
| 3 | updated 2008-03-19 by EM
|
|---|
| 4 |
|
|---|
| 5 | * Problem
|
|---|
| 6 |
|
|---|
| 7 | The CNS device will help drivers by guiding them to their destination.
|
|---|
| 8 |
|
|---|
| 9 | * Background information / Domain analysis
|
|---|
| 10 |
|
|---|
| 11 | The CNS will be used in cars which can very in type. All types of roads have to be considered. Several companies will offer the CNS. CNS is using the GPS Satellite system to get it's location, which means that big buildings, bad weather and tunnels can impact the performance of the device.
|
|---|
| 12 |
|
|---|
| 13 | * Environment / system model
|
|---|
| 14 |
|
|---|
| 15 | The device must be able to receive and use information from GPS (Global Positioning System) and RDS (Radio Data System). The GPS is used to get the location.
|
|---|
| 16 | The device must be able to receive and use information from RDS (Radio Data System). RDS is used to get data about traffic jams and other traffic conditions.
|
|---|
| 17 | The dimensions should be 12 x 12 x 6 cm (width x height x depth), with no greater deviation than 1 cm in each direction.
|
|---|
| 18 | The screen dimensions must be at least 10 x 10 cm (width x height).
|
|---|
| 19 | The screen must be touch sensitive (touch input).
|
|---|
| 20 | The weight should stay below 200 gram.
|
|---|
| 21 | Energy usage must be kept low, less than 5 Watt.
|
|---|
| 22 | Buttons:
|
|---|
| 23 | - power on/off
|
|---|
| 24 | - select between views (discussed below)
|
|---|
| 25 | - select
|
|---|
| 26 | - "+" (zoom in)
|
|---|
| 27 | - "-" (zoom out)
|
|---|
| 28 |
|
|---|
| 29 | * Functional requirements
|
|---|
| 30 |
|
|---|
| 31 | The device has two views (screens):
|
|---|
| 32 | - main screen (default view on powering up)
|
|---|
| 33 | - target selecting screen
|
|---|
| 34 |
|
|---|
| 35 | Main screen:
|
|---|
| 36 |
|
|---|
| 37 | The device must show a map on screen which shows:
|
|---|
| 38 | - the car, marked by a green triangle pointed to the current driving direction (or the last driving direction when standing still), centered when no target is selected, and 2 cm from a border directing the opposite direction when driving to a selected target, updated each 1 seconds.
|
|---|
| 39 | - the environment (choose map based on current location), updated each 5 seconds.
|
|---|
| 40 | - the route / way to be taken, marked by small (3 mm) dots, updated each 60 seconds.
|
|---|
| 41 | - if possible, the target, marked by a red circle (a dot of 6 mm), updated each 60 seconds.
|
|---|
| 42 | - if existent, traffic jams or other problems, marked by a gray shade, updated each 60 seconds.
|
|---|
| 43 | - current speed (bottom centered), updated each 1 seconds.
|
|---|
| 44 | - current time (upper left), updated each 1 seconds.
|
|---|
| 45 | - ETA (estimated time of arrival) (upper right), updated each 15 seconds.
|
|---|
| 46 | - driving directions (arrows), updated each 3 seconds.
|
|---|
| 47 |
|
|---|
| 48 | Tapping with a finger on the screen should set a new waypoint to which the driver should be taken first, before the final target is reached.
|
|---|
| 49 |
|
|---|
| 50 | Target selecting screen:
|
|---|
| 51 | The device must show a list on screen which shows:
|
|---|
| 52 | - current target and waypoints, ordered on current distance, and tapping on one of those should select it. Pressing the "-" should delete the selected target / waypoint.
|
|---|
| 53 | - nearby points of interest and important roads (highways) (first half of the screen), which can be added with "+" as waypoint or with "select" as destination (target).
|
|---|
| 54 | - a touchscreen virtual keyboard input to specify a target, which can be added with "+" as waypoint or with "select" as destination (target). If the target is not recognized, then it should be shown in red, and not be added as waypoint or destination. If it is recognized, it should be shown in blue. A list of three suggested targets based on the current input should be shown below the text input.
|
|---|
| 55 |
|
|---|
| 56 | * Usability
|
|---|
| 57 |
|
|---|
| 58 | The usability is guaranteed by using only a few buttons and where possible the touch screen input. Users instantly see their current position and current map. The usability is further improved by fast updating important information and not showing too much information and arcane options.
|
|---|
| 59 |
|
|---|
| 60 | * Performance
|
|---|
| 61 |
|
|---|
| 62 | A performance minimum for updating driving directions, current location and so forth is given in the requirements for the main screen. The performance should allow the driver to act quickly on changing directions and to have a relevant and actual view on his/her environment.
|
|---|
| 63 |
|
|---|
| 64 | * Accuracy
|
|---|
| 65 |
|
|---|
| 66 | Here, maximum errors / deviations are given:
|
|---|
| 67 | - current speed: max 10%
|
|---|
| 68 | - current location: max 25 meters while driving (less is difficult with current GPS technology) max 12 meters while standing still
|
|---|
| 69 | - current time: max 2 min.
|
|---|
| 70 | - ETA: this is a guess, so up to 20% of the time to travel may be wrong 95% of time
|
|---|
| 71 | - traffic jams: this depends on RDS data, so accuracy cannot be guaranteed by the CNS
|
|---|
| 72 |
|
|---|
| 73 | * Quality
|
|---|
| 74 |
|
|---|
| 75 | The device must withstand small drops of water (like when raining), sunshine behind glass, operating temperatures from -20 up to 80 degreed Celsius, drops from table-level heights, and firm finger presses on the touch screen.
|
|---|
| 76 |
|
|---|
| 77 | The GPS and RDS modules must be replaceable with newer modules.
|
|---|
| 78 |
|
|---|
| 79 | The internal map must be stored on a removable storage, so make updating possible.
|
|---|
| 80 |
|
|---|
| 81 | The software should be programmed using the object oriented paradigm.
|
|---|
