A bit of “Persona”, a bit of “Goal”, a bit of “Process” ... a recipe for Analyzing User Intensive Software Systems

Chiara Di Francescomarino, Chiara Leonardi, Alessandro Marchetto, Cu D. Nguyen, Nauman A. , g y ,

Qureshi, Luca Sabatucci, Anna Perini, Angelo Susi, Paolo Tonella, and Massimo Zancanaro

Fondazione Bruno Kessler – IRST CIT

MotivationsMotivations

Two projects Ambient Aware Assistance (Healthcare domain) Internet of Services (IoS)

Central role of the users in the design and evolution of “User intensive” (user-centric) systems

Motivating domain: Ambient Aware Assistance (ACube project)Assistance (ACube project) System for monitoring and acting on nursing homes

( )(Alzheimer patients and their caregivers) A very critical domain highly user-centric

f f / The system should follow each user also forecasting her/his behavior Reactive to events Ubiquitous in the life space of patients and operators Ubiquitous in the life space of patients and operators

[Leonardi et al. 2010]

Motivating domain: Internet of Services (Real services)(Real services)

• Real Services: a combination of actual services and software services that: (i) provide electronic access to an actual service; (ii) inform the user in real time about events that maybe crucial for her (e.g. flight cancellation)

Tailored to each specific user– Tailored to each specific user … user-centric

– asset-driven, user’s assets, such as time, money, social relations h f d lthat are fundamental in our

choices– Ubiquitous …

[Marchetto et al. 2010]

Envisaged solutionEnvisaged solution

An integrated methodology in which user-centered design goal-oriented representation and analysis (as mediating artifact) process modeling

May cooperate for a continuous communication between users, k h ld d drequirements engineers, stakeholders and designers

To go from user needs, to requirements, to process design

ACube / IoS: use of goals in the processACube / IoS: use of goals in the process

IoSACube

User requirements

SystemSystem requirements

System design

From user needs to requirements (through personas actors/goals)(through personas, actors/goals)

Coupling the engineering perspective with a creative perspective typical of User-Centred Design (persona, scenario) approaches:

Principles: early focus on users, their tasks and their environment the active involvement of users in the design process the incorporation of user-derived feedback into system design iterative design whereby a prototype is designed, tested and

d f dmodified.

The proposed process (and ingredients)p p p ( g )

And Tropos Actor/Goal Models

For the problems in the Tropos to visual Scenarios translation see Luca’s talk on Friday (Ahab’s leg)

From requirements to Real Services(through goals and processes)(through goals and processes)

Tropos: actors roles goalsSpecification &

design

Tropos: actors, roles, goals, softgoals, social dependencies

designBPMN: service modelingAnd also:

Validation through simulation

Ontologies: user assets, and domain entities

OCL constraints: effect of activities on user assets

Implementation

Concepts from goals to BPMNConcepts from goals to BPMN

Goal Model element BPMN Model element

Actor/User Role Pool

Goal/Sub-Goal/Plan Activities (i e Task/Subprocesses)Goal/Sub-Goal/Plan Activities (i.e. Task/Subprocesses)

OR decomposition Branch of activities (i.e. OR/XOR gateway and alternative flows)g y )

Resources inside actor/role boundary Data objects exchanged among activities in the same pool

Resources shared by actors Data objects exchanged among activities in different pool

Ongoing/future workOngoing/future work

Refining the UCD/GORE methodology better integrating goal orientation and user-centred design refining the way to communicate models to users

Methodology for modeling /specifying IoS extended modeling of quality requirements and preferences

ifi ti f it i f liti d f t d i specifications of monitoring for qualities and preferences to drive self-adaptation at run-time

ReferencesReferences Leonardi, C., Sabatucci, L., Susi, A., Zancanaro, M.: Ahab’s leg: Exploring

the issues of communicating semi-formal requirement to final users. In: g qProceedins of CAiSE 2010. (2010)

Marchetto, A., Nguyen, C.D., Francescomarino, C.D., Qureshi, N.A., Perini, A., Tonella, P.: A Design Methodology for Real Services. In: 2nd I i lW k h P i i l f E i i S i O i dInternational Workshop on Principles of Engineering Service-Oriented Systems, PESOS, May 2-8, 2010, Cape Town, South Africa. (2010)

Di Francescomarino, C., Ghidini, C., Rospocher, M., Serafini, L., Tonella, P.: Rea soning on semantically annotated processes In: InternationalRea- soning on semantically annotated processes. In: International Conference on Service-Oriented Computing. (2008)

I i i k Inspiring works: Sutcliffe, A., Maiden, N., Minocha, S., Manuel, D.: Supporting scenario-

based requirements engineering. IEEE Transactions on Software Engineering 24(12) (1998) 1072 1088Engineering 24(12) (1998) 1072–1088

Pistore, M., Traverso, P., Paolucci, M., Wagner, M.: From Software Services to a Future Internet of Services. In: Towards the Future Internet - A European Research Perspective IOS Press (2009) 183–192European Research Perspective. IOS Press (2009) 183 192

Process and guidelinesProcess and guidelines

user’s goals, preferences,

building the process view, preferences,

alternative solutions

from the goal model

capturing thecapturing the effect of the asset modifiers in the user assets

t l t d

assets

annotating the models concepts related

to user and system; user assets and

t difi

ode ssemantically by considering the asset modifiers

asset modifiers