<!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>A Preliminary Investigation of the Utility of Goal Model Construction</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Naomi Cebula</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lily Diao</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alicia M. Grubb</string-name>
          <email>amgrubbg@smith.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science Smith College</institution>
          ,
          <addr-line>Northampton, MA</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <fpage>67</fpage>
      <lpage>72</lpage>
      <abstract>
        <p>Goal models have long been used in the literature to model and reason about stakeholders' intentions. Prior work proposed several studies aimed at investigating what utility stakeholders derive from constructing and analyzing goal models. We designed and conducted an initial empirical study that explores the construction stage of goal modeling, asking whether stakeholders bene t from manually drawing their own model. We recruited eight quali ed participants and asked each to create a goal model for a decision they were considering while talking out loud. Half of the participants in this study used BloomingLeaf, while the remaining participants drew goal models by hand. Using information gathered through an online pre-study questionnaire, we constructed a goal model for each participant. Participants' compared our generated models with their manually created ones. We used open coding to nd themes and categories for qualitative responses. Analysis was mixed on whether participants preferred their own model to the researcher generated one. The results of which have implications for future studies, as well as goal model adoption and automation.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        In early project planning, goal-oriented requirements engineering (GORE)
approaches have been advocated to help stakeholders make trade-o decisions.
While there have been many GORE languages [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], they all encapsulate the
representation of functional and non-functional requirements into a central artifact,
called a goal model. These techniques have been extended and applied to research
projects downstream in software development [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], yet they have not achieved
broad industrial adoption [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. In prior work, Grubb described basic assumptions
made as part of the GORE process, including the assumption that modelers
can construct goal models [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Using these assumptions, Grubb proposed several
studies aimed at investigating what utility stakeholders derive from
constructing and analyzing goal models, where utility was de ned as ` tness for some
desirable purpose or valuable end' [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        Our aim is to investigate the construction stage of goal modeling. This study
is a rst attempt at exploring the questions proposed by Grubb [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. We ask to
what extent do participants gain value in manually drawing goal models (in a
tool or on paper)? Utility can be more speci cally seen as whether stakeholders
Copyright © 2020 for this paper by its authors. Use permitted under
Creative Commons License Attribution 4.0 International (CC BY 4.0).
have gained any new insights, changed any decisions, or developed new values
through modeling. Our null hypothesis in this work is that there is no utility in
the goal model construction process (i.e., drawing models on paper or in a tool).
Contributions. In this paper, we present an exploratory study of the utility
of goal model construction. We recruited, trained, and observed eight novice
Tropos [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] modelers as they modeled a scenario of their choosing. Participants
used either BloomingLeaf [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] or pencil and paper to construct their own model
(called USER) and reviewed a second model of the same scenario (called AUTO).
Adapting the OZ Paradigm [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], participants were told the AUTO model was
automatically generated from their pre-study survey, but it was created by the
authors of this paper. In this study, we consider four research questions: (RQ1)
Were novice participants able to understand and use goal model constructs?
If so, what di culties were experienced by novices when being introduced to
goal modeling and Tropos? (RQ2) To what extent were participants able to
understand the AUTO model? (RQ3) Did participants choose to extend the USER
or AUTO model? (RQ4) What utility (if any) was described by participants or
observed by researchers?
      </p>
      <p>The remainder of this paper is organized as follows. Section 2 introduces the
methodology of our study. Section 3 describes and interprets our study
observations. We discuss implications and future work in Sect. 4.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Methodology</title>
      <p>This study was reviewed by the Smith College Institutional Review Board
(Protocol: 18-110), see supplemental information online1 for the study protocol.
Study Design. Participants were asked to complete a pre-session
questionnaire, a single in-person modeling session, and a brief post-study questionnaire.
Throughout the study, participants were asked to explore one of three
motivating scenarios that was currently relevant to their life: choosing between majors,
planing for after graduation, and deciding between study abroad options.</p>
      <p>In the pre-study survey, participants were asked who, what, and why
questions to elicit scenario information, which allowed us to create goal models of
their trade-o decisions, known as the AUTO model. Four participants each were
randomly assigned to either the Paper or Tool group.</p>
      <p>
        In the in-person modeling session, participants were trained on the syntax
and semantics of Tropos goal models (either on paper or in BloomingLeaf).
To demonstrate Tropos language constructs, we used a modernized version of
the Trusted Computing example [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. After completing the training videos, we
asked participants questions to ensure that they achieved an adequate level of
understanding of Tropos. Participants were then given time to develop a goal
model for their chosen scenario (i.e., the USER model). We asked the participants
a list of questions to encourage them to expand and re ne the USER model. Once
participants felt they were nished with the USER model, we showed them the
1 https://github.com/amgrubb/gore-study
AUTO model and asked them to extend it. After the participants nished, they
were asked to compare the USER and AUTO model and choose between them,
explaining their choice. Finally, the participants were given another opportunity
to improve their chosen model and were asked followup questions.
      </p>
      <p>In the optional post-study questionnaire, participants were asked if their
decisions changed after the in-person session or if they had any further thoughts
about the scenario they investigated.</p>
      <p>Recruitment and Remuneration. We recruited eight participants in the
summer of 2019. Participants were required to be pro cient in English, without any
formal training in goal modeling, and registered undergraduate students at Smith
College in the 2019 school year. Each participant was paid $15.00 upon
completion of the in-person session. The participants' information was kept anonymous
and demographic information was not collected.</p>
      <p>
        Data Analysis. With participants' consent, in-person modeling sessions were
recorded and transcribed. Two of the authors independently used open-coding on
the transcripts to explore themes [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. In a group meeting, all authors discussed
and converged on relevant themes. A second pass was then performed on the
transcripts to ensure consistency in coding.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Results</title>
      <sec id="sec-3-1">
        <title>In this section, we describe and interpret our study observations.</title>
        <p>Understanding Tropos (and BloomingLeaf ). We begin by answering RQ1:
Were novice participants able to understand and use goal model constructs? If
so, what di culties were experienced by novices when being introduced to goal
modeling and Tropos? After watching the tutorial videos, participants were able
to identify actors, decomposition links, and contribution links. Some
participants were confused about the di erence between the speci c types of
contribution links. For example, one participant asked, \What's the di erence between
++ and ++S?", while another asked \Why do some [links] have two negatives
and others have one negative?". We were able to clarify participants' questions
about model semantics prior to continuing; thus, we believe we can compare
observations between participants.</p>
        <p>Participants were encouraged to continue asking questions throughout the
session for additional clari cation. We observed two additional patterns over
the remainder of the modeling. First, participants asked clarifying questions
about model elements, including intentions. For example, a participant asked
if \soft goals are things that don't have cut-o s?". These questions were most
likely to occur at the beginning of the modeling process when participants had
not yet fully transferred concepts from the Trusted Computing example. Second,
participants asked how factors in their scenario could be added to the model. This
style of question was most common once participants identi ed the main goals
of their scenario. For example, participants asked, \Is my interest a resource or a
task?" and \Should this link be and?". Overall, we found that novice participants
were able to understand and use goal modeling constructs with assistance.
Model Understanding. Next, we consider RQ2: To what extent were
participants able to understand the AUTO model? After each participant constructed
the USER model, the researcher showed them the AUTO model and asked
questions to understand how well it t the participant's own scenario. None of the
participants removed any nodes or connections from the AUTO model. Four
participants proposed new connections between existing intentions and new
intentions to be added. Two participants proposed how an intention could be further
decomposed. After reviewing the AUTO model, all of the participants were able
to present a clear cut answer about the major trade-o s and decisions in their
own scenario, which were not clearly indicated in their pre-study questionnaire;
thus, all participants were able to understand the AUTO model. This provides
additional evidence that participants understood the goal model constructs.
Comparing Auto Model with Self-created Model. Following from the
previous question, we look at RQ3: Did participants choose to extend the USER
or AUTO model? Five participants chose the AUTO model (3 Paper &amp; 2 Tool),
while three chose the USER model (1 Paper &amp; 2 Tool). For participants who chose
the AUTO model, their reasoning was that the AUTO model was more organized
or had more information, sample responses included, \I think auto is more clear
and the arrows make more sense" and \...there are more direct connections
between all of the components that go into my goals...". For participants who
chose the USER model, they found it contains more detailed information, for
example, \I'll extend the one I just made, it has a lot of links I don't want to
recreate on auto". In reviewing the participants' rationale, we became concerned
that participants may have chosen the AUTO model because it was more visually
appealing than their own model, which is addressed in our future work.
Utility Evaluation. Finally and most importantly, we looked at RQ4: What
utility (if any) was described by participants or observed by researchers? To
evaluate what utility participants gain from constructing the model, we coded
the responses to the post-study questionnaire and the transcripts of the in-person
sessions, including the results to the question, \what did you learn from each
model?". We observed four aspects of utility in the model construction activities
in this study.</p>
        <p>(1) Elicit Underlying Assumptions &amp; Motivations. When talking out loud,
participants discussed their motivation behind achieving a certain goal while
putting that goal on the canvas. Thinking in the context of goal modeling helped
participants to explore tacit information, though most of this information does
not appear in the nal model. Two comments included in this category were,
\probably it is also a goal [to become pre-dental], 'cause after coming to Smith, I
nd that I really want to take a lot of chemistry courses and want to eventually
make it a major", and \one of the goals of neuroscience is to achieve a deep
understanding in one of the hard sciences, a task would be taking a bunch of
upper-level classes".</p>
        <p>(2) Explicitly Consider Structural Relationships. Study participants responded
that they learned how to break down a bigger goal into smaller tasks and
considered how to weigh di erent factors in the process. This lead to new insights
about how they could structurally think about the ultimate goal of their
scenario. One participant said that she learned \...a di erent way to weigh things,
compare things that are required vs possibilities. A new way to put thoughts
down". Another participant said that this made her \...look at things as smaller
steps, which is really valuable. It very much so set into stark terms the decisions.
I'll have to make in the future, which I've been putting o ".</p>
        <p>(3) Learned Something New. Participants responded that after modeling their
goals, some of the factors or goals were presented and linked within the model
which they had not seriously considered before. This forced them to reconsider
a perspective or factor that they had previously ignored. Two sample responses
were, \I wasn't thinking a lot about how di erent perspectives would contribute
to my decision-making, especially [my] pre-health advisor...but in this model it
represents that.", and \I think one of the biggest conclusions is that industry
job would satisfy less of my personal goals than teaching or research".</p>
        <p>(4) Update Conclusions. Finally, participants responded that their personal
preference was further reinforced or changed after the modeling experience. Some
said that the idea of \soft goals" helped them to see the broader picture of the
scenario, which in uenced their decisions. For example, one participant said,
\I think my preference is towards the french major now. It shifted more in
that direction.", while another reinforced their concerns, saying, \I guess I was
thinking a lot about money issues, but when you draw [out the model] it feels
real and pressing."
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Discussion</title>
      <sec id="sec-4-1">
        <title>In this section, we discuss our observations and propose future studies.</title>
        <p>
          Threats to Validity. The observations made in this study may be erroneous
due to threats to validity, speci cally construct validity. Subjects may have
gained utility from discussing their scenarios. We did not separate the utility
in talking through a problem from the utility of modeling the problem. Future
studies will isolate this factor and compare them with the results of Kwan and
Yu [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. Since our participants asked clarifying questions while modeling, the
researchers' answers may have biased the participants in some way. Our training
videos can be improved by contrasting contribution links, providing more
examples, and considering the work of Liaskos et al. [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. Future studies should recruit
participants already familiar with goal modeling and Tropos. Participants may
have been apprehensive towards evaluation and wanted to perform well for our
study. They may also have been biased by their own assessments due to
hypothesis guessing. Finally, bias may exist in our analysis as a result of experimenter
expectancies.
        </p>
        <p>Discussion of Utility. In Sect. 3 we found evidence of utility; thus, we reject
the null hypothesis as stated, but this is insu cient to answer our study question:
To what extent do participants gain value in manually drawing goal models (in a
tool or on paper)? Since this was an exploratory study, none of the observations
were conclusive but instead inform our future work.
Future Work. We expect to re ne our protocol and make the changes described
above to address our threats to validity. We will repeat this study as a series of
controlled experiments with larger numbers of participants over longer periods
of observation, isolating each variable in this study. In future work, we intend to
explore participants rationale for choosing the AUTO or USER model.</p>
        <p>To investigate the e ects of `talking out loud', we will compare the use of
goal modeling to other methods of choosing between trade-o s (e.g., pro and
con lists). For each of these studies we should consider novice users (representing
stakeholders), trained modelers, and stakeholders not involved in the modeling
process. Finally, we hope to partner with software organizations to study goal
model construction in an industrial context.</p>
        <p>Summary In this paper, we presented an exploratory study of the utility of
goal model construction. We found that participants understood and were able
to use model constructs and found utility in both the USER and AUTO models.
Participants gained insights into their assumptions, goals, and the structural
nature of their scenarios with some participants changing their decision. Future
work will repeat our study with trained modelers and address the issues noted
in our discussion above.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>J.</given-names>
            <surname>Horko</surname>
          </string-name>
          and
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          , \
          <article-title>Comparison and Evaluation of Goal-Oriented Satisfaction Analysis Techniques,"</article-title>
          <source>Requirements Engineering</source>
          , vol.
          <volume>18</volume>
          , no.
          <issue>3</issue>
          , pp.
          <volume>199</volume>
          {
          <issue>222</issue>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>J.</given-names>
            <surname>Horko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.-L.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Salnitri</surname>
          </string-name>
          , E. Cardoso,
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Pimentel</surname>
          </string-name>
          , \
          <article-title>Taking goal models downstream: A systematic roadmap,"</article-title>
          <source>in Proc. of RCIS'14</source>
          ,
          <year>2014</year>
          , pp.
          <volume>1</volume>
          {
          <fpage>12</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>A.</given-names>
            <surname>Mavin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Wilkinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Teu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Femmer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Eckhardt</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Mund</surname>
          </string-name>
          , \
          <article-title>Does Goal-Oriented Requirements Engineering Achieve Its Goal?"</article-title>
          <source>in Proc. of RE'17</source>
          ,
          <year>September 2017</year>
          , pp.
          <volume>174</volume>
          {
          <fpage>183</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>A. M. Grubb</surname>
          </string-name>
          , \
          <article-title>Re ection on Evolutionary Decision Making with Goal Modeling via Empirical Studies,"</article-title>
          <source>in Proc. of RE'18</source>
          ,
          <year>2018</year>
          , pp.
          <volume>376</volume>
          {
          <fpage>381</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>OED</given-names>
            <surname>Online</surname>
          </string-name>
          , \utility,
          <source>n."</source>
          , Oxford University Press,
          <year>2018</year>
          , www.oed.com/view/Entry/220771. Accessed:
          <fpage>2018</fpage>
          -03-13.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>A.</given-names>
            <surname>Fuxman</surname>
          </string-name>
          , L. Liu,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Pistore</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Roveri</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Traverso</surname>
          </string-name>
          , \
          <article-title>Specifying and Analyzing Early Requirements in Tropos,"</article-title>
          <source>Requirements Engineering</source>
          , vol.
          <volume>9</volume>
          , no.
          <issue>2</issue>
          , pp.
          <volume>132</volume>
          {
          <issue>150</issue>
          , May
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>A. M.</given-names>
            <surname>Grubb</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Chechik</surname>
          </string-name>
          , \
          <article-title>BloomingLeaf: A Formal Tool for Requirements Evolution over Time,"</article-title>
          <source>in Proc. of RE'18: Tool Demos</source>
          ,
          <year>2018</year>
          , pp.
          <volume>490</volume>
          {
          <fpage>491</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>J. F.</given-names>
            <surname>Kelley</surname>
          </string-name>
          , \
          <article-title>An Empirical Methodology for Writing User-Friendly Natural Language Computer Applications,"</article-title>
          <source>in Proc. of CHI'83</source>
          ,
          <year>1983</year>
          , pp.
          <volume>193</volume>
          {
          <fpage>196</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>J.</given-names>
            <surname>Horko</surname>
          </string-name>
          and
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          , \
          <article-title>A Qualitative, Interactive Evaluation Procedure for Goaland Agent-oriented Models,"</article-title>
          <source>in Proc. of CAiSE'09</source>
          ,
          <year>2009</year>
          , pp.
          <volume>19</volume>
          {
          <fpage>24</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>A.</given-names>
            <surname>Strauss</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Corbin</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Corbin</surname>
          </string-name>
          ,
          <article-title>Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory</article-title>
          .
          <source>SAGE Publications</source>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>A.</given-names>
            <surname>Kwan</surname>
          </string-name>
          and
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          , \
          <article-title>Goal Modeling without Stress: An Empirical Study of User Engagement,"</article-title>
          <source>in Proc. of iStar'17</source>
          ,
          <year>2017</year>
          , pp.
          <volume>85</volume>
          {
          <fpage>90</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>S.</given-names>
            <surname>Liaskos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Alothman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ronse</surname>
          </string-name>
          , and W. Tambosi, \
          <article-title>On the Meaning</article-title>
          and
          <article-title>Use of Contribution Links,"</article-title>
          <source>in Proc. of iStar'19</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>