Table 1.
Exemplar user requirements mapped to system requirements (RIM—Relation and Identity Manager; MPD—Mobility Pattern Detector; PMS—Personal Mobility Store; INM—Infrastructure Network Manager; MPD—Mobility Pattern Detector).
| Scenario ID | User Requirements | System Component & Requirements | Priority |
|---|---|---|---|
| US2 | Social Network Reuse | RIM.1 (identify and authenticate user), RIM.3 (link Social Network user ID to tripzoom user ID), RIM.5 (import social network links into tripzoom) | High |
| US4 | Improved Mobility Pattern Analysis | MPD.1 (create mobility patterns for persons, places & vehicles), MPD.4 (provide overviews of mobility choices of users & consequences of choices, e.g., time, money, emissions, delay), PMS.2 (pre-filter sensor data), INM.4 (Get mapping of location trace to a list of infrastructure segments); INM.5 (reverse geo-coding and mobility-related Point of interest lookup). | High |
| US8 | Planned Real-time Trip Info & Recommender | MPD.3 (classify context-aware mobility patterns where context can be weather condition, or user-event driven, e.g., shopping) | High |
| US9 | Real-time Trip Info. | MPD.1 (as above) | Medium |
| US13 | Trip Change Incentives | PMS.8 (pre-filtered sensor data exchange), IMP.4 (offer context-aware, incentives e.g., in space and time, to targeted users) | High |
| US14 | Ad hoc Location-specific Mobility Offers | IMP.4 (as above) | Medium |