Re equireme ents Cove erage Ana alysis

6 Re equireme ents Cove erage Ana alysis

In this s section, we d discuss vario ous requirem ments for th he design of the intent‐a aware user interface which ha ave original b been defined d in D1.1. Gi ven these re equirements, , we perform m a detailed coverage analysis to validate t the design a nd purpose of the intent t ‐aware user r interface sy ystem. As pa art of the analysis, , we discuss the concrete e design con cepts and m mechanisms w we are propo osing to addr ress each of the re equirements for our syste em.

6.1 In ntent ‐rela ated Requ uirements s

ID UI_005

Descript tion The user interface pe erforms proa active recom mendations on trips.

Type Function al and data r requirement ts Priority High

UI_005: This require ement has be een covered through the design of co oncepts for p proactive tra vel

guidance e in Section 3 3. The user‐i nterface is in nherently pr oactive in th hat it recomm mends trip an nd transit in nformation w which are rel evant to the e individual t ravel behavi our and inte ent. In contra ast, reactive travel recom mmenders re equire this kn nowledge to be given as explicit by th he user.

ID UI_008 Descript tion The perso onal user int terfaces supp port the visu alization of p possible rout tes. Type Function al and data r requirement ts Priority High

UI_008: Our user‐int terface mode el spans diffe erent layers which deal w with the visu ualization of r route informat tion as discu ssed in Secti ion 3. The tra ansit layer in ntroduced in Section 3.1 visualizes th e routes and stru cture of the transport ne etwork using g basic data a about the tra ansport syste em. Addition nally, we enrich th he visualizati ion of routes s with crowd d information n and predict tions of trave el habits.

ID UI_011 Descript tion The user interface co omponent m ust recomme end persona alised transpo ort routes. Type Function al and data r requirement ts Priority High

UI_011: Personalizat tion concept ts of the user r interface ha ave been tho oroughly cov vered in Sect tion 3.2. In this se ection, we ha ave develope ed the interf face concept t of cognitive e maps to rec commend an nd highlight t travel infor rmation whic ch are most r relevant to p peoples’ trav vel patterns a and mobility needs.

ID UI_012

Descript tion The user interface co omponent m ust provide p personalised d information n

related to o user intent t. Type Function al and data r requirement ts Priority High

UI_012: This require ement has be een covered in Section 5. .2 by an algo orithmic appr roach to extr ract user intents a and mobility profiles from m histories o of past travel behaviour. T This informa ation describ bes the most po pular routes s of a travelle er across a w week as a bas sis for the ge neration of c cognitive ma aps with which us sers can inte eract.

ID UI_013 Descript tion The user interface co omponent sh ould enable users to bec come aware of friend's t ravel behavi iour.

Type Function al and data r requirement ts Priority High

UI_013: This require ement has be een covered in Section 3. .3, where we e have propo osed a user i nterface concept based on th e notion of s social transp port maps. A social transp port maps su ummarizes h ow the

user’s so ocial network k has been u sing a public c transport s ystem. ID UI_014

Descript tion The user interface sh ould anticipa ate user info ormation nee eds and be d esigned to minim ize user inpu ut. Type Function al and data r requirement ts Priority Medium

UI_014: We have cov vered this re equirement i n Section 5 b by proposing g a specificat tion of variou us user

interface e algorithms . The algorit hms are des igned to extr ract user inte ents so that user input is s

minimize ed or not ne cessary at al l. For this pu urpose, perso onal and soc ial mobility p patterns are derived from pas st travel hist ories.

ID UI_015 Descript tion The user interface sh ould be desi igned to imp rove user's f feeling abou t public transport t. Type Function al and data r requirement ts Priority Medium

UI_015: The design of our user i interface sys stem is cove red in Sectio on 3 and em mphasizes con ncepts to discover r and repres ent various kind of trav vel informati ion (crowd w warnings, pe ersonal route es, social transpor rt usage), wh hich are inte ended to im prove user’s s feelings ab bout public t transportatio on. While

the focu us of this del iverable is to o introduce a consistent t framework for the imp lementation of these concepts s, a report a about users’ reactions w will

be given n in the follo owing delive erables based d on real world us ser studies.

6.2 P rivacy ‐re elated Req quiremen nts

ID UI_006 Descript tion The user interface en nables the us ser to manua ally override and limit

automate ed collection n and sharing g of data. Type Mandate ed constraint ts Priority High

4.1.6, w where the p rivacy comp ponent of th he intent‐ aware u ser ‐interface e system is d discussed. Th he user inte rface interac cts with the privacy pres servation framewo ork to set t the desired privacy set ttings. The c changes are e then enfo orced by the e privacy preserva ation framew work accordi ng to the giv ven privacy p preferences.

UI_006: This require ement is cov vered in Sec ction

ID UI_007 Descript tion The priva acy setting sh hould indicat te a distincti on between on device a nd on the serve er. Type Function al and data r requirement ts Priority High

4.1.6, the user interfa ces allows f or inspectin ng and modi fying the privacy c configuratio n. This inclu des the poli icy rules for the chosen level of stor ring data (“R Remote”, “Device” ”, “Detect On nly”), which indicates wh here sensitive e user data i s stored in th he network.

UI_007: As discusse ed in Section n

ID UI_010 Descript tion The user interface co omponent m ust enable u sers to selec ct privacy preferen ces. Type Function al and data r requirement ts Priority High

UI_010: The user in terface inter racts with th he privacy p reservation framework t to exchange e privacy‐ related control sett tings. This h has been di scussed in Section

4. T The user int terface will visualize

different t choices for the sensing, , storage and d sharing of sensitive con ntext data. ID UI_009

Descript tion It should be possible to manually configure th he policy. Type Function al and data r requirement ts Priority High

UI_009: As discusse ed in Sectio n

4, the use er interface will allow the user to o change the e various relations s which are part of the p privacy polic cy language. The modific cation of the e policy lang uage will

be repor rted back to the privacy preservation n framework k which take s care of the e enforceme ent of the privacy s settings for t the execution n of the appl lication.