[Devel] Updated geolocation and navigation design document
Barkowski Andre (CM-CI1/PRM1)
Andre.Barkowski at de.bosch.com
Mon Nov 16 17:20:26 GMT 2015
thx for the updated document.
After having read the document and before I start providing deeper feedback, I was wondering about the UseCases covered in that document. We have used the pattern (from Usecases to Requirements, reflection of existing solutions and coming to a proposed approach) already multiple times, but this time I was really wondering, when do we pick up a use-case to be mentioned ?
One of my primary intentions is to define the SDK-API. So from that point of view I reflect, what kind of use-case exists for a "non-navigation app" to deal with location based information (e.g. Weather, Hotels, etc). That’s an App-Developer point of view.
Another set of use-cases comes from flexibility in system setups, that’s influencing things behind the scene and is more a System Integrator point of view.
Maybe there are more.
What is your motivation ?
In contrast, I do _not_ take into account what an developer of a navigation App would like to do. That’s all internal stuff, without dependency to the SDK.
I do have the feeling, there are uses cases included only relevant for Navigation internal implementation. Lets call them Navi-features. But I am not sure. Things like "Deviating off a navigation route", "Resuming a navigation route" or "cancelling a navigation route", aren't they full App-Internal ? Its seems to me like we would discuss that a phone call needs to have the capability to be canceled. That for sure right, but I miss why its important for our context.
Or the description is misleading, e.g. an App would like to subscribe for a new route (for example caused by deviating off a navigation route, but also caused by other reasons like a new (intermediate) destination has been set). In that case the description / and the use case would more focus on consuming the new-route information and to generate some great service from it instead of "that the calculated route must be radically different", and "recalculation should happen within a short time period".
Hope you get what I mean.
Von: Devel [mailto:devel-bounces at lists.apertis.org] Im Auftrag von Philip Withnall
Gesendet: Donnerstag, 12. November 2015 17:40
An: devel at lists.apertis.org
Betreff: [Devel] Updated geolocation and navigation design document
Please find attached version 0.2.1 of the geolocation and navigation
design document. This version incorporates feedback about swappable
backends and the ability to back any of the APIs by an implementation
in the automotive domain.
I have uploaded this version to the wiki as a draft. Further feedback
is welcome and will be incorporated as normal.
More information about the Devel