The document discusses challenges with user-centered design (UCD) for large, collaborative infrastructure projects like SPICE. It summarizes the SPICE project goals of creating an extendable architecture to support new service creation across networks. Focus groups provided feedback on initial SPICE scenarios, identifying benefits but also privacy, profiling and organizational concerns. Recommendations focused on addressing these issues in revised scenarios and requirements. The document concludes by noting UCD for infrastructures requires an iterative, collaborative approach where methodology is a flexible conversation.

1. Crafting infrastructures. Requirements, scenarios and evaluation in the SPICE project Mobile IST Summit User Centricity Workshop Budapest, 5° July 2007 L.Galli-Neos

2. UCD challenges in R&D, collaborative, infrastructure projects UCD @ R&D stage Collaborative projects INFRASTRUCTURE

3. Infrastructure-orientation generates indirectness in evaluations “ Stuck in the middle?” Source: W.K. Edwards, V. Bellotti, A.K. Dey, M.W. Newman, Stuck in the Middle: the Challenges of User-Centered Design and Evaluation for Infrastructure, 2003

4. Can I have UCD – but XL? Source: E.Kurvinen et al., User-Centered Design in the Context of Large and Distributed Projects, 2006 abstraction critical mass* * NOT the one regarding bikes!  compartmentalization

6. SPICE scenarios The tourists’ potential interest in particular activities or items is inferred from their behaviour and is followed by a service push. So when they stop around for a couple of hours at a nice village in the countryside the system advances a proposal suitable to the moment of the day (“do you want suggestions for a light meal nearby?”). Depending on the user’s reply, additional audio/visual information is provided to get them on the suggested spot. Once they have enjoyed the break, they go back to their car … A multidisciplinary team of managerial, marketing and technical people associated with the promoting organization of “Sunrise Inc.” and its technology partners meet to evaluate all the possibilities offered by the SPICE PF components repository. Some services will be created by simply reusing existing elements (e.g. basic components, composite components), while others will be realized as an investment from the involved third parties. Ad hoc contractual and operational models are provided ….

7. Proposal Project lifetime 3 short textual narratives - I-Portal - e-Tourism - e-Emergency 4 rich textual & visual narratives scenarios - I-Portal - e-Tourism - e-Emergency - Service Creation (NEW!) 4 fully REVISED and slightly EXPANDED scenarios based on FOCUS GROUPS RESULTS & other inputs - I-Portal - e-Tourism - e-Emergency - Service Creation divergence convergence 1 newly revised COMMON SCENARIO, consistent set of characters & situations, unified view, re-ordered against SPICE main features Initial requirements Revised requirements Technical design and development (including architectural work and intermediate demos) 1° EVALUATION ROUND (focus groups) 2° EVALUATION ROUND Demos Final prototypes Kick-off Conclusion Exploitation Take-up Business modelling & legal issues Vision Objectives Workplan Step 1 Step 2 Step 3 Step 4

12. Mapping users’ input into “scenes’ requirements”

13. Enhanced scenarios it is impossible that the service makes use of users’ sensitive information in a malicious way since the local SPICE Operator guarantees that user’s personal data (e.g. name, address, mail, telephone…) are never matched with his context information (e.g. position, mood, availability). Before the service can use sensitive information, the user’s consent must always be given.

15. Craft & “traditional methods”

16. Methodology should not be a fixed track to a fixed destination but a conversation about everything that could be made of happen J.C. Jones, Design Methods (1972-1990) Methodology as conversation

17. Q&A Thank you for your attention Luca Galli [email_address]