<!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>Towards an Evaluation Visualization with Color</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Megan H. Varnum</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kate M. B. Spencer</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>79</fpage>
      <lpage>84</lpage>
      <abstract>
        <p>Goal models help stakeholders understand project scenarios and make decisions. In prior work, we used Tropos evaluation semantics to allow for automated analysis over time; however, formal evaluation labels (e.g., (F; ?)) are di cult for users to interpret across a large model. In this paper, we present our work towards understanding the extent to which using colors in goal modeling a ects users' ability to make decisions. Speci cally, we are interested in studying if coloring intentions with evaluation information allows for better comparisons of initial states and simulations of future paths. To address this question, we developed a color visualization extension to BloomingLeaf, a goal model analysis tool, where the color of each node is changed based on either the initial evaluations or the resulting analysis over time. This then allows us to explore if and how color visualization assists the user with decision making. We present our implementation and initial evaluation of this extension.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Goal modeling allows stakeholders to model and visualize their domain and
analyze trade-o s [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Recent work extends goal modeling and analysis to allow
for project scenarios with changing evaluations [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Users can run simulations
to examine relationships over time, with tooling and analysis provided for both
iStar [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and Tropos [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. We believe these tools have potential for problem-solving
among teams of stakeholders. However, the reality of working with large models
is that it is challenging to view trends and make decisions because of the large
volume of data and technical nature of analysis results.
      </p>
      <p>
        In our work, we aim to improve the interpretability of model evaluations
and analysis. We investigate the use of color to convey information about the
ful llment of evaluations, both statically and as they change over time. Previous
work in the iStar community looks at improving clarity of goal models through
visualizations and making them more user-friendly [
        <xref ref-type="bibr" rid="ref10 ref3">3, 10</xref>
        ]. We present our work
in the context of BloomingLeaf, which uses Tropos semantics, but the lessons
learned have similar implications for the iStar language.
      </p>
      <p>
        Running Example: Social Distancing Dinner. In the midst of the
COVID19 pandemic [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], Emma must decide how to acquire dinner for the week. She
constructs a goal model to evaluate the trade-o s between picking up takeout
or cooking her dinner at home (see Fig. 1(i)). She runs simulations for various
scenarios on BloomingLeaf, one where minimize economic impact is prioritized (i.e.,
Copyright © 2020 for this paper by its authors. Use permitted under
Creative Commons License Attribution 4.0 International (CC BY 4.0).
(?; F)
(F; P)
(F; F)
      </p>
      <p>(P; P)
(P; F)
(P; ?)
(?; P)
(?; ?)
(i) Running Example: Social
Distancing Dinner
(ii) A lattice of evidence pairs in</p>
      <p>Tropos with colored labels.
satis ed over time) and another where minimize spread of COVID-19 is prioritized.
For each scenario, BloomingLeaf returns evaluation labels for all timepoints in
a week, and Emma is unsure how to proceed. How can she easily know whether
cook at home or order takeout is satis ed more often? What about the proportion
of time that practice social distancing is partially denied or fully denied? While
traversing the simulation path, Emma is unsure how to interpret the data and
unclear about the optimal course of action.</p>
      <p>Contributions. In this paper, we explore our research question: To what extent
does applying colors to individual intentions in models and simulation paths
improve model understanding and allow for better decision making? We present
Evaluation Visualization Overlay (EVO), an extension to BloomingLeaf which
colors the initial satisfaction values (i.e., evidence pairs) of each intention in a
goal model and, after running analysis, overlays the proportion of time points
that each intention holds each evaluation. With EVO, users can better
visualize future states of their model, make comparisons between intentions, and
understand trends in ful llment over time.</p>
      <p>The remainder of this paper is organized as follows. Sect. 2 introduces relevant
background about evaluation labels and BloomingLeaf. Sect. 3 explores our
visualization approach. Sect. 4 discusses our preliminary evaluation and compares
our work with prior visualizations. We conclude in Sect. 5.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Background</title>
      <p>
        BloomingLeaf is an online tool used to construct and analyze goal models using
the Tropos language [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Goal models consist of actors and intentions (i.e., goals,
soft goals, tasks, and resources). For example, in Fig. 1(i), Emma is an actor, have
dinner is a goal, practice social distancing is a soft goal, and cook at home is a task.
In BloomingLeaf, when EVO is not enabled, elements are solely colored based
on their intention type. For instance, fresh groceries in Fig. 1(i) is colored light
blue because it is a resource. These colors, combined with di erent shapes, allow
users to distinguish intention types. In Tropos, each intention can be assigned
a qualitative evaluation label (i.e., evidence pair ), which is a pair (s; d) where
s 2 fF; P; ?g is the level of evidence for and d 2 fF; P; ?g is the level of evidence
against the ful llment of an intention g [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. F [resp. P] means there is full [resp.
partial] evidence for or against the ful llment of g, while ? represents null
evidence. Fig. 1(ii) gives a lattice of evidence pairs, with all possible combinations of
evidence for and against. Initially, an intention can have one of ve evaluation
labels: (Fully) Satis ed (F; ?), Partially Satis ed (P; ?), Partially Denied (?; P),
(Fully) Denied (?; F), and None (?; ?). Propagation-based analysis techniques
may result in intentions being assigned one of four con icting evaluation labels:
(F; F), (F; P), (P; F), and (P; P).
      </p>
      <p>
        Interactions between intentions are expressed through links. Contribution
links (e.g., +, -, ++, {) indicate an element's in uence on another. For example,
in Fig. 1(i), in order for cook at home to be satis ed, fresh groceries must also be
satis ed, indicated by a ++, while cook at home helps practice social distancing,
indicated by a +. Decomposition links (and /or ) decompose an intention into child
goals. An intention with an and [resp. or ] decomposition requires all [resp. only
one] of its children to be satis ed. Functions indicate an intention's evolution.
For example, Fig. 1(i) assigns fresh groceries a Monotonic Negative function
(MN) because Emma's groceries will expire throughout the week. After creating
a model of intentions, links, initial values, and functions, users can analyze their
model over time by simulating single paths (not shown). These are sequences of
states consisting of evidence pairs for each element in the model over an ordered
set of time points [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Users can step through these time points to see the
changing evidence pairs of each intention, based on its assigned function. Unassigned
intentions receive evidence pairs via propagation and the Stochastic function.
In Fig. 1(i), simulating a single path helps Emma see how the satisfaction of
fresh groceries impacts the evaluation of not get or transmit COVID-19 (not shown).
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Results</title>
      <p>The goal of Evaluation Visualization Overlay (EVO) is to visualize both the
initial state and path analysis of a model over time. Each evidence pair is assigned
a color, with bluer shades closer to satis ed and redder shades closer to denied,
as illustrated in the background of Fig. 1(ii). Thus, (F; ?) and (P; ?) are shades
of blue and (?; F) and (?; P) are shades of red. Con icting evaluations with
evidence for both satisfaction and denial are shades of purple, with (F; P) [resp.
(P; F)] assigned shades of purple closer to blue [resp. red]. These colors are used
both in modeling and analysis mode when EVO is enabled.</p>
      <p>Implementation. Working within the architecture of BloomingLeaf, we
implemented EVO as an on-o toggle option in the top toolbar, with its mechanics
implemented in the JavaScript front-end. For the visualization of a single path
in analysis mode, BloomingLeaf's back-end provides the necessary data, which
is then stored in an encapsulating object. This object contains an array that
corresponds to the evidence pairs of each intention at each time point.
EVO while Modeling. Activating EVO in the modeling mode changes the
color of each intention to correspond to its user-set initial satisfaction value.
This provides an overall visualization of the model's initial state, allowing users
to understand the color scheme and initial evaluations.</p>
      <p>In our running example, Emma rst prioritizes minimize spread of COVID-19,
assigning it as (F; ?) with a Constant function. Knowing her groceries deplete
over time, she sets the resource fresh groceries to (F; ?) with a Monotonic
Negative function. Interested in the initial state of the model, she activates EVO.
She sees the two intentions above are blue (not shown), while the rest remain
their original color. Because the majority of her model doesn't change, Emma
knows she cannot answer her dinner question with only the model's initial state.
EVO while Analyzing the Resulting Model. After running a single-path
simulation in analysis mode, activating EVO displays colored stripes on each
element. The width of each colored stripe corresponds to the percentage of the
path that the intention is assigned a given evidence pair, ordered left to right from
most to least satis ed. Thus, the user can gauge the evaluations of intentions
over time without needing to walk through the simulation state by state.</p>
      <p>In our example, Emma, simulates a path in analysis mode and sees the
evidence pairs in the corners of the intentions while stepping through time points.
However, she is unable to remember data from each previous time point and so
nds it impossible to make sense of the evidence pairs at once. She then turns
on EVO to see how prioritizing the satisfaction of minimize spread of COVID-19
impacts her dinner decision (see Fig. 2). While there are variations in the
evaluations, Emma sees that cook at home is more satis ed than order takeout, and that
it is never denied. This indicates that to minimize the transmission of COVID-19
in her life she should choose to cook at home. Emma also observes that not get
or transmit COVID-19 and practice social distancing are mostly satis ed, but notices
that minimize economic impact has the majority of evidence towards denied.</p>
      <p>In a second scenario, Emma wants to reduce job loss and is concerned about
her local economy. She clears the model and sets minimize economic impact to
fully satis ed with a Constant function. Starting with EVO o , she is able to
discern that while order takeout is fully satis ed, minimize spread is denied for
several time points. However, toggling EVO reveals the whole picture of her results
(see Fig. 2). While order takeout and have dinner are overwhelmingly satis ed, the
other intentions have mixed results, and many are denied. Given this
information, Emma understands the consequences of interacting with others and decides
to cook at home to keep her and others the most safe.</p>
      <p>EVO helps Emma understand trends in the model and answer her trade-o
question: Which dinner option is fully or partially satis ed for the greatest
proportion of time points under her chosen constraints? She can also draw
conclusions about the unpredictability of her scenario with EVO by seeing discrepancies
among multiple single paths.
To explore EVO's versatility, we took nine models ranging in size from 14 to 121
intentions, some more deterministic and others more stochastic, and analyzed
them with EVO enabled. For each model, we considered what information was
clear before activating EVO and what we could not understand without it. We
consolidated our observations into bene ts of EVO and areas of improvement.
Bene ts. The toggle operation makes the user interface easy to use. In the
modeling mode, EVO shows initial evaluations to visualize the initial state of
the model. The colors are intuitive, with bluer shades equating to more satis ed
and redder shades to more denied. In analysis mode, EVO provides the user with
the \big picture" of their model by visualizing the proportion of time points the
intentions hold each evaluation. Since the order of colors is consistent, it's easy to
compare evaluation proportions across di erent intentions and simulation paths.
Improvements. The chosen color palette is not optimal for colorblind users.
EVO can be improved by enabling a colorblind mode. An intention that starts
(F; ?) and evolves to (?; F) has the same visualization as the reverse, because
the colors are always in the same order. An additional view showing changes in
order would di erentiate these two cases. EVO can also be improved to visualize
any partial point of interest after simulating a single path. EVO is limited in the
modeling view; it's only useful for select models with well-de ned initial states.
Plan for Validation. We have con dence EVO bene ts users in drawing
conclusions from goal models, given the distinct di erences observed between using
it and not; however, we only provide an initial evaluation. To quantify and
validate the functionality of EVO, we must test it among a broader range of users.</p>
      <p>
        We plan to conduct a study comparing BloomingLeaf's usability in decision
making with and without EVO by providing di erent models to two randomized
groups of students trained in goal modeling. One group's tool will have EVO
enabled, while the other group will only use the simulated path. The students
will then answer questions about optimal decisions and evaluations over time.
Related Work. Aprajita proposed using heatmaps to depict overall satisfaction
(see Fig. 11 of the associated thesis [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]). In both Aprajita's work and this paper,
we address the di culty of allowing the user to visualize trends in time-based
goal models [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Our research di ers in that Aprajita's heatmaps are separate
from the goal model, whereas our work integrates the color visualization and the
model, allowing users to see both at the same time. Aprajita's system of red to
green (for quantitative evaluations) does not apply in our work; thus, we develop
our two axis color scheme (see Fig. 1(ii)).
5
      </p>
    </sec>
    <sec id="sec-4">
      <title>Summary and Future Work</title>
      <p>
        EVO visualizes evaluation trends in single-path simulations as well as models'
initial states, which allows for easy comparison across intentions within models.
This work could have implications for decision making in other iStar tools [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>Before drawing conclusions to our research question, a more thorough
analysis across a broad range of potential users is required. Additionally, future work
ensures our color palette is appropriately clear for all users. We are also
developing a variation of EVO that visualizes the evaluations at every time point over
a single path. This variation allows users to see changes of intentions over time
instead of their unordered overall evaluation.</p>
      <p>Acknowledgments. Varnum was supported by a Smith College STRIDE Scholarship.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>D.</given-names>
            <surname>Amyot</surname>
          </string-name>
          et al.
          <article-title>Evaluating Goal Models Within the Goal-Oriented Requirement Language</article-title>
          .
          <source>International Journal of Intelligent Systems</source>
          ,
          <volume>25</volume>
          (
          <issue>8</issue>
          ):
          <volume>841</volume>
          {
          <fpage>877</fpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. Aprajita. TimedGRL:
          <article-title>Specifying Goal Models Over Time</article-title>
          .
          <source>Master's thesis</source>
          , McGill University,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>R. F. de Oliveira</surname>
          </string-name>
          et al.
          <article-title>A Critical View Over iStar Visual Constructs</article-title>
          .
          <source>In Proc. of iStar'19</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          , E. Nicchiarelli, and
          <string-name>
            <given-names>R.</given-names>
            <surname>Sebastiani</surname>
          </string-name>
          .
          <article-title>Formal Reasoning Techniques for Goal Models</article-title>
          .
          <source>Journal on Data Semantics</source>
          ,
          <volume>1</volume>
          :1{
          <fpage>20</fpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>A. M.</given-names>
            <surname>Grubb</surname>
          </string-name>
          . Evolving Intentions:
          <article-title>Support for Modeling and Reasoning about Requirements that Change over Time</article-title>
          .
          <source>PhD thesis</source>
          , University of Toronto,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <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 Posters &amp; Tool Demos</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>A. M. Grubb</surname>
            , G. Song, and
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Chechik. GrowingLeaf: Supporting Requirements</surname>
          </string-name>
          <article-title>Evolution over Time</article-title>
          .
          <source>In Proc. of iStar'16</source>
          , pages
          <fpage>31</fpage>
          {
          <fpage>36</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>T.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. M.</given-names>
            <surname>Grubb</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Horko</surname>
          </string-name>
          <article-title>:. Understanding Challenges and Tradeo s in iStar Tool Development</article-title>
          .
          <source>In Proc. of iStar'16</source>
          , pages
          <fpage>49</fpage>
          {
          <fpage>54</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. WHO.
          <article-title>WHO Statement regarding cluster of pneumonia cases in Wuhan, China</article-title>
          . https://www.who.int/china/news/detail/09-01-2020-who
          <article-title>-statement-regardingcluster-of-pneumonia-cases-in-wuhan-</article-title>
          <string-name>
            <surname>china</surname>
          </string-name>
          ,
          <source>Jan. 9</source>
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>A.</given-names>
            <surname>Yasin</surname>
          </string-name>
          and
          <string-name>
            <given-names>L.</given-names>
            <surname>Liu</surname>
          </string-name>
          .
          <source>Recent Studies on i*: A Survey</source>
          .
          <source>In Proc. of iStar'17</source>
          , pages
          <fpage>79</fpage>
          {
          <fpage>84</fpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>