<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Bridging User-Centered Design and Requirements Engineering with GRL and Persona Cases</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Shamal Faily</string-name>
          <email>shamal.faily@cs.ox.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science, University of Oxford</institution>
          <addr-line>Wolfson Building, Parks Road, Oxford OX1 3QD</addr-line>
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2011</year>
      </pub-date>
      <fpage>114</fpage>
      <lpage>119</lpage>
      <abstract>
        <p>Despite the large body of i* research, there has been comparatively little work on how goal-modelling techniques can help identify usability concerns. Recent work has considered how goal models might better integrate with User-Centered Design. This paper takes an alternative perspective by examining how work in User-Centered Design, specifically Persona Cases, can be re-framed as goal models. We briefly describe an approach for doing this, and present some preliminary results from applying this approach using the Goal-oriented Requirements Language and existing tool support.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>i* and related agent-oriented requirements engineering techniques are useful for
modelling complex relationships between social agents and intentional concepts.
Surprisingly, however, there appears to be comparatively little work on the
usefulness of these techniques for eliciting concerns affecting the usability of systems
for its participating users.</p>
      <p>
        Previous work has considered how i* might be integrated with User-Centered
Design techniques to facilitate communication between requirements engineers,
stakeholders, and designers [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. This work argues that such an approach adds
a creative element to the engineering perspective associated with goal-oriented
techniques. Follow on work by Leonardi et al. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] proposes the use of visual
scenarios to contextualise Tropos models, and using personas [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] to fulfil the role
of actors. Personas are behavioural specifications of archetypical users which
embody their needs and goals; since their initial introduction by Cooper [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ],
personas have become a mainstay in User-Centered Design. Leonardi et al.
identify several issues associated with translating formal models to more engaging
artifacts like scenarios, but attention also needs to be paid to the validity of
the personas used. If personas are not carefully developed then criticisms about
their validity may also threaten the validity of any artifacts they influence [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        Persona Cases have recently been proposed as a technique for providing
independent validation of personas [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Persona cases are personas whose
characteristics are both grounded in, and traceable to, their originating source of
empirical data. As a validation tool, persona cases are built on the premise that
sense-making in qualitative data analysis is an argumentative activity, and the
elements of Grounded Theory [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] can be re-framed as an argument using
Toulmin’s model of argumentation [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Expressing persona data using i* can also
provide a means of validity by eliciting intentional relationships that support
or challenge aspects of a persona’s behaviour. However, aside from providing a
means for persona validation, there are three additional reasons why integrating
this work with i* and related goal-oriented approaches might be useful from a
design perspective.
      </p>
      <p>First, given the analogies that can be drawn between i* and other approaches
for design rationale, and Toulmin’s model being the basis upon which these
approaches are built, it seems reasonable to expect alignment between i* concepts
and persona cases. Alignment between concepts may allow qualitative models
to be re-framed as goal models in the same sense that they can currently be
re-framed as persona skeletons.</p>
      <p>Second, current efforts to support interchange between different i* modelling
tools also facilitate the generation of goal models by requirements management
tools that support aligning concepts.</p>
      <p>
        Third, because goal models provide an alternative way of contextualising
personas, an integrated approach benefits UX (User Experience) designers as
well as requirements analysts. When augmented with tasks that stakeholders
might carry out, designers may be more interested in using these models to
understand user activities in context [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] rather than as a vehicle for directly
eliciting requirements. Consequently, framing goal modelling as a UX design
technique may lead to an expanded audience for i* and related techniques, who
may identify hitherto unseen affordances in both goal models and goal modelling
techniques.
      </p>
      <p>In this short paper, we describe preliminary work bridging User-Centered
Design and Requirements Engineering by re-framing persona cases as goal
models. In section 2, we describe our research objectives and the research approach
adopted before describing our contributions to date in section 3. We summarise
these contributions in section 4, and describe on-going work in this area.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Objectives</title>
      <p>The objectives of this research are two-fold.</p>
      <p>
        First, we want to better understand how personas and associated concepts
align with i*. Unlike previous work, we wish to align concepts to i* rather than
the other way around; this is because we are considering i* as a tool to support
User-Centered Design, rather than vice-versa. Because personas are often
described using scenarios, we expanded the scope of analysis to include use cases
carried out by personas. Because previous work suggests that goal models align
with use cases [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], it is possible that the alignment relationship between goal
models and use cases is bi-directional.
Second, we want to understand how existing tool support can exploit these
relationships such that goal models can be automatically generated based on
pre-existing analysis. As a baseline for this research, we use the Goal-oriented
Requirements Language (GRL) as the goal-modelling language for aligning
concepts, and the jUCMNav [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] Eclipse plugin because of its support for importing
XML based GRL files. The CAIRIS tool [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] was used for managing persona case
and use case elements, and generating GRL files.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Contributions</title>
      <p>GRL
Relations</p>
      <p>Contribution
Relationship</p>
      <p>Intentional</p>
      <p>Relationship
Decomposition
Relationship</p>
      <p>Persona Case
Elements</p>
      <p>Persona
Characteristic</p>
      <p>Warrant</p>
      <p>Element
Grounds</p>
      <p>Element
Use Case
Elements</p>
      <p>Use Case step</p>
      <p>Objective</p>
      <p>GRL Nodes</p>
      <p>Intentional
Element</p>
      <p>Task
Softgoal
Goal
To date, we have made contributions to each of our research objectives.</p>
      <p>
        We identified several aligning relationships between persona case and use case
elements and GRL; these are summarised in figure 1. The elements in this model
align with concepts from the IRIS (Integrating Requirements and Information
Security) meta-model: a conceptual model aligning elements from Requirements
Engineering, HCI, and Information Security [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>Because the [long] names associated with persona characteristics and their
supporting elements are displayed on a goal model, a short synopsis was
associated with each; a similar synopsis was assigned to each associated use case
objective and step. As figure 1 shows, each stipulated persona case and use case
element was associated with a GRL intentional element. To date, our
preliminary research has considered only the sub-set of tasks, goals, and soft-goals as
candidate aligning elements.</p>
      <p>To support the bounding of elements associated with i* Strategic Rationale
models, persona characteristic synopses and supporting elements were
automatically bounded by persona name. Synopses associated with use case steps were
associated with either personas or concepts associated with the system being
designed.</p>
      <p>Associations between persona characteristics and their supporting
argumentation elements were aligned to GRL contribution relationships. Our initial work
indicates that GRL contribution relationships are semantically richer than the
relationships between persona characteristics and their supporting grounds and
warrants. For this reason, it was necessary to associate the navigability between
elements in the contribution relationship with each characteristic-grounds and
characteristic-warrant relationship, together with the strength of the
contribution. This strength is based on the qualitative contribution values associated with
GRL; these range from Make and SomePositive to SomeNegative and Break. At
present, the analyst is responsible for deciding both the navigability direction
and the strength of the qualitative contribution. This decision is based on the
use case’s impact on the persona, and activities related to both the persona and
the use case. Associated with each use case step is a decomposition relationship
between the intentional element associated with the use case objective and the
element associated with the step.
CAIRIS was updated to support the association of synopses with persona
case and use case elements, and the association of the requisite contribution link
attributes – contribution direction and strength – to each characteristic-grounds
and characteristic-warrant association. The tool was also updated to allow a
GRL model file to be generated for a selected persona and associated use case.
When models are imported into jUCMNav, additional contribution links were
added to elements associated with use case steps to indicate whether these help
or hinder persona goals or tasks. Such links are added at this late stage as these
may not be obvious until the initial goal model is displayed. Figure 3 illustrates
a complete GRL model generated by CAIRIS and imported into jUCMNav for
all of Helen’s characteristics and all steps of the Content sharing and storage use
case.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusion and Ongoing Work</title>
      <p>This paper presented an approach for generating goal models from persona cases
and their associated elements. We described how persona case and use case
elements align with complementary elements of GRL, and demonstrated how
existing tool support can take advantage of this alignment to generate GRL
models from pre-existing model data in CAIRIS.</p>
      <p>As part of the EU FP7 webinos project, we are currently using this approach
to model the impact of personas carrying out use cases which help or hinder
their personal or occupational goals. Insights gleaned from this and other goal
models are currently being used to develop scenarios illustrating the
unintentional impact of webinos to prospective users and their security and privacy
expectations.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgements</title>
      <p>The research described in this paper was funded by the EU FP7 webinos project
(FP7-ICT-2009-05 Objective 1.2). We are also grateful to Daniel Amyot and
Sepideh Ghanavati for their advice on using jUCMNav and GRL.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Francescomarino</surname>
            ,
            <given-names>C.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leonardi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marchetto</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>C.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Qureshi</surname>
            ,
            <given-names>N.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sabatucci</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Perini</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Susi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tonella</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zancanaro</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A bit of ”persona”, a bit of ”goal”, a bit of ”process” ... a receipe for analyzing user intensive software systems</article-title>
          . In Castro, J.,
          <string-name>
            <surname>Franch</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mylopoulos</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
          </string-name>
          , E., eds.
          <source>: Proceedings of the 4th International i* Workshop</source>
          . Volume 586. CEUR Workshop Proceedings (
          <year>2010</year>
          )
          <fpage>36</fpage>
          -
          <lpage>40</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Leonardi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sabatucci</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Susi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zancanaro</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Ahab's leg: exploring the issues of communicating semi-formal requirements to the final users</article-title>
          .
          <source>In: Proceedings of the 22nd international conference on Advanced information systems engineering. CAiSE'10</source>
          , Berlin, Heidelberg, Springer-Verlag (
          <year>2010</year>
          )
          <fpage>455</fpage>
          -
          <lpage>469</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Cooper</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity (2nd Edition)</article-title>
          .
          <source>Pearson Higher Education</source>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Chapman</surname>
            ,
            <given-names>C.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Milham</surname>
            ,
            <given-names>R.P.:</given-names>
          </string-name>
          <article-title>The persona's new clothes: Methodological and practical arguments against a popular method</article-title>
          .
          <source>Proceedings of the Human Factors and Ergonomics Society 50th Annual Meeting</source>
          . Available at http://cnchapman.files.wordpress.com/
          <year>2007</year>
          /03/chapman-milhampersonas-hfes2006-
          <fpage>0139</fpage>
          -0330.pdf (
          <year>2006</year>
          )
          <fpage>634</fpage>
          -
          <lpage>636</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Faily</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , Fl´echais, I.:
          <article-title>Persona cases: a technique for grounding personas</article-title>
          .
          <source>In: Proceedings of the 29th international conference on Human factors in computing systems</source>
          ,
          <source>ACM</source>
          (
          <year>2011</year>
          )
          <fpage>2267</fpage>
          -
          <lpage>2270</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Corbin</surname>
            ,
            <given-names>J.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Strauss</surname>
            ,
            <given-names>A.L.</given-names>
          </string-name>
          :
          <article-title>Basics of qualitative research : techniques and procedures for developing grounded theory</article-title>
          .
          <source>3rd edn. Sage Publications</source>
          , Inc. (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Toulmin</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>The uses of argument. updated edn</article-title>
          . Cambridge University Press (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Norman</surname>
            ,
            <given-names>D.A.</given-names>
          </string-name>
          :
          <article-title>Logic versus usage: the case for activity-centered design</article-title>
          .
          <source>Interactions</source>
          <volume>13</volume>
          (
          <issue>6</issue>
          ) (
          <year>2006</year>
          )
          <fpage>45</fpage>
          -
          <lpage>ff</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Castro</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alencar</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santander</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Silva</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Integration of i* and ObjectOriented Models</article-title>
          . In
          <string-name>
            <surname>Yu</surname>
          </string-name>
          , E.,
          <string-name>
            <surname>Giorgini</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maiden</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mylopoulos</surname>
          </string-name>
          , J., eds.:
          <article-title>Social Modeling for Requirements Engineering</article-title>
          . MIT Press (
          <year>2011</year>
          )
          <fpage>457</fpage>
          -
          <lpage>483</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Mussbacher</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Modeling and Analysis of URN Goals and Scenarios with jUCMNav</article-title>
          .
          <source>In: Proceedings of the 2009 17th IEEE International Requirements Engineering Conference</source>
          , RE. RE '09, Washington, DC, USA, IEEE Computer Society (
          <year>2009</year>
          )
          <fpage>383</fpage>
          -
          <lpage>384</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Faily</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , Fl´echais, I.:
          <article-title>Towards tool-support for Usable Secure Requirements Engineering with CAIRIS</article-title>
          .
          <source>International Journal of Secure Software Engineering</source>
          <volume>1</volume>
          (
          <issue>3</issue>
          )
          <article-title>(July-September</article-title>
          <year>2010</year>
          )
          <fpage>56</fpage>
          -
          <lpage>70</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Faily</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , Fl´echais, I.:
          <article-title>A Meta-Model for Usable Secure Requirements Engineering</article-title>
          .
          <source>In: Proceedings of the 6th International Workshop on Software Engineering for Secure Systems</source>
          , IEEE Computer Society (
          <year>2010</year>
          )
          <fpage>126</fpage>
          -
          <lpage>135</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>