from use cases to users perspectives
TRANSCRIPT
From use cases to users perspectives
A process towards the definition of a tool for IoT urban service design
Mario Chiesa – ISMB; Cristina Barbero, Simona Ricaldone – Concept Reply
Context and motivationdesign and prototyping in the real world of an
innovative technological platform– hardware– system architecture– middleware– applications
to implement future horizontal services within the Internet of Things (IoT) paradigm
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Context and motivationAs an example of future “horizontal” implementations
of IoT technologies and services, we chose a mall with:– A parking area– Shops– Other typical services– Associated touchpoints
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Context and motivation
“How does and how can IoT services impact and change the way people experience their city?”
“How to create an IoT ecosystem that creates mutual benefit for both service contributors as well as service consumers in order to encourage active participation and long term sustainable growth of the city platform?”
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
IoT value drivers• infrastructural values
1. simplified manual proximity trigger
2. automatic proximity trigger
3. automatic sensor triggering
4. automatic product security
• motivational values5. simple and direct user feedback
6. extensive user feedback
7. mind-changing feedback
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
“Simplified and automatic extensive feedbacks”
IoT in public urban areas• Diffused and horizontal solutions
• Loose definition of goals
• Users with very different skills
• Multiple services at the same time, with different timescales
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
“very different from vertical professional environment“
The design challenge• How different users will perceive their
interactions with IoT services?
• Why they will decide to use andinteract with many of them?
• How their daily life will benefit from them?
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
“Multiple levels for motivational aspects and feedbacks“
The design challenge
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
“How can we answer to those crucial questions?“
“How can we communicate those motivations?“
Limits of classic design tools – 1/3Scenarios, use cases, tasks descriptions:
are linear and homogeneous ways of developing and describing stories. They usually need to ground their narration on a set of pre-assumptions (technological or motivational), develop it through a sequence of actions and events, and end with a finite set of possible conclusions.
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Limits of classic design tools – 2/3As a linear narration they find difficult:
• to describe multiple forks along the process• to highlight the richness in the offering of services• to describe the generation of complex services• to describe simultaneous situations and conditions,
and their evolution
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Limits of classic design tools – 3/3As an homogeneous narration they find difficult:
• to satisfy the need of describing and representing the same event or sequence of events towards different communities
• to allow the addition of future services, implementations into the same narration
• to describe the same events with different eyes, according to the different involved stakeholders
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Inspirations – 1/4Scenario based system design
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Inspirations – 2/4
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Isometric projections
Inspirations – 3/4
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Storytelling
Inspirations – 4/4
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Toys
Plain text microstories
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Microstories can:• break a scenario in its basic units• describe a use case from more viewpoints• leave room to side descriptions and situations
that typically would be lost
Plain text microstories
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Microstories can:• enhance the added value perceived by users– when they get in touch with the system (as a
single experience)– during their usage of the system (again as a single
experience)– in the long period, as an overall perception of the
system as it impacts in their lives (as a global experience)
Microstories from existing user stories
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
developing microstories means to break apart each use case into several microstories, in order to create:
• at least one single experience microstory for each step in the use case
• at least one global experience microstory for each use case or usage scenario
Microstories from investigation phase
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
developing microstories means to translate into its narrative form the results of a clustering session, in order to create:
• at least one single experience microstory for each item of a cluster
• at least one global experience microstory for each cluster
Microstories, time perspectives and roles
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Final users Providers
Global experience
Personal achievements, global considerations
Business goals, overall evaluations
Single experience
Single actions, local advantages
Single actions, local advantages
User perspectives
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Instant perspectives
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
“The next step in the visual representation of the microstories is their visualization in the real use context“
Instant perspectives – work in progress
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Instant perspectives – work in progress
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
A glimpse of other project’s activities
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
XMPP• Ad-hoc commands• Publish-subscribe• Data forms
IoT Middleware
A glimpse of other project’s activities
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
From use cases to users perspectivesA process towards the definition of a tool for IoT urban service design
Mario Chiesa
Istituto Superiore Mario Boella
Cristina Barbero, Simona Ricaldone
Concept Reply
{cr.barbero, s.ricaldone}@reply.it
Thank you!