<!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>Downsizing EPMcreate to Lighter Creativity Techniques for Requirements Elicitation *</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Department of Industrial Engineering</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>University of Trento</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy luisa.mich@unitn.it</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Cheriton School of Computer Science, University of Waterloo</institution>
          ,
          <addr-line>Waterloo</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>EPMcreate is a creativity technique for requirements elicitation based on a 16-step process. These steps suggest focusing on requirements related to every combination of two different target users or viewpoints. A series of experiments confirmed its feasibility; its applicability, both as individual and group technique; and its greater effectiveness than brainstorming. However, analysts involved in some of the experiments highlighted the large number of steps as a limitation of the technique. Recent experiments tested a variant of the EPMcreate, named Power-Only EPMcreate, based on 4 of the 16 steps. The experiments showed that it works better than EPMcreate for at least website requirements. Nevertheless, the question of whether any other combination of the steps of the original technique could work is still open. This paper illustrates a number of criteria for generating lighter creativity techniques, each based on a subset of the 16 steps of EPMcreate.</p>
      </abstract>
      <kwd-group>
        <kwd>Requirements elicitation • Creativity process • Creativity step •</kwd>
        <kwd>Target user • Viewpoint</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The Elementary Pragmatic Model (EPM) creativity technique, EPMcreate, was
defined in 2004. EPMcreate operationalized a creativity technique for problem
solving [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], adapting it to requirements elicitation. That problem-solving technique
was in turn based on a model of the pragmatics of communication, the EPM [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        The role of creativity in software development has been addressed in two main
ways. Some authors recognized the creativity as relevant for designing software
systems (see for example, [
        <xref ref-type="bibr" rid="ref3 ref4">3–4</xref>
        ]). Others worried about its impact on the software
development process and described it as a factor to be controlled (among them [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]).
These two approaches do reflect the dual nature of creativity that needs to be both
enhanced and methodically applied [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], as confirmed by the large number of existing
methods for creativity enhancement.
      </p>
      <p>
        The 16-step process characterizes EPMcreate as a requirements elicitation
technique nicely satisfying these two goals. Since its introduction, EPMcreate has
* Copyright 2017 for this paper by its authors. Copying permitted for private and academic
purposes.
been applied in a number of experiments. The first experiments tested its applicability
in real projects [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and involved groups of analysts; results of these experiments also
showed that EPMcreate performs better than the well-known and widely applied
brainstorming. Another experiment, run in 2007, investigated the applicability of
EPMcreate as an individual creativity technique [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] by junior analysts and also by
domain experts. Then a series of experiments was designed to start addressing a
specific question: “Could a creative process implementing a subset of the EPMcreate
steps be as effective as the full 16-step process of EPMcreate?” A technique, named
Power-Only EPMcreate, or POEPMcreate, based on 4 of the 16 steps was defined.
Experiments with POEPMcreate showed that for at least websites, it works better than
EPMcreate [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. This paper proposes some criteria to define other lighter variants of
EPMcreate, based on different subsets of its 16 steps.
      </p>
      <p>In the rest of the paper, Section 2 introduces the EPM to give a conceptual
framework to downsize EPMcreate. Section 3 illustrates the possible criteria to
generating creativity techniques based on processes with fewer steps than the 16
needed for EPMcreate. Conclusions are drawn in Section 4, highlighting some of the
open questions to be addressed in future work, on both theoretical and empirical
grounds.
2</p>
    </sec>
    <sec id="sec-2">
      <title>The Elementary Pragmatic Model and EPMcreate</title>
      <p>
        The Elementary Pragmatic Model (EPM) is based on the relational theories of the
Palo Alto School [
        <xref ref-type="bibr" rid="ref10 ref11">10–11</xref>
        ]. It formalizes the interactions between two subjects in terms
of elementary messages whose pragmatic content is interpreted using a two-value
logic. A sequence of messages is then represented by a sequence of 0 and 1 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], and
analyzed using the 16 Boolean functions of two variables [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. These 16 functions
can be illustrated by a Hasse diagram shown in Figure 1 and by the well-known truth
tables shown in Table 1. EPMcreate takes advantage of the 16 functions, f0, ..., f15, of
the EPM, suggesting a structured creative process for requirements elicitation [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
Each step of the process corresponds to one of the sixteen Boolean functions,
combining in a systematic way the viewpoints of two target users, U1, U2, of the
software system to be designed.
Step 0, the first step, f0, requires the analyst to empty her mind. In Step 1, f1, she
identifies requirements shared by the viewpoints of U1 and U2; in Step 2, f2, she
identifies requirements for the viewpoint of U1 not shared by the viewpoint of U2; in
Step 3, f3, she identifies requirements for the viewpoint of U1 independent of the
viewpoint of U2; ...; and in Step 15, f15, she identifies requirements for both
viewpoints, including those coming from external issues.
      </p>
      <p>
        Many of the steps of EPMcreate can be connected to other creativity techniques.
First of all, Step 0, corresponding to f0, encapsulates the Creative Pause Technique
[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Step 15, corresponding to f15, encapsulates the withhold-criticism principle of
brainstorming, because it says that each requirement has to be accepted. Another
interesting step is that corresponding to f8, which in EPM, describes behaviours giving
unexpected results as in the comic strip in Figure 3. Step 8 suggests that the analyst
empty her mind and think of requirements not related to either viewpoint adopted for
the requirements elicitation session. Also, Step 8 is similar to the Synapsis technique
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], whose turning point suggests deviating from the real context, suspending logical
thinking, in order to find uncommon ideas; many other techniques suggest the same
using different words. Being paradoxical by definition, Step 8 forces looking for new
issues, looking at the problem in a new way, represented by the external area in the
Venn diagram in Figure 2. Each step following Step 8 in EPMcreate includes that
external area, and for this reason, in EPM, functions from f8 onwards are called
“antifunctions”.
      </p>
    </sec>
    <sec id="sec-3">
      <title>Downsizing EPMcreate</title>
      <p>EPMcreate foresees a requirements elicitation process in 16 steps, more steps than
any of the existing creativity techniques include in its idea generation phase†. On one
hand, the systematic covering of the combinations of the target users' viewpoints is
the core of EPMcreate and forces an analyst to discover any user's requirements by
thinking in Steps 8 through 15, also of unexpected and external requirements. On the
other hand, in some of our experiments, analysts said that the large number of steps of
the technique is a limitation and complained about their repetitive nature. To reduce
the number of steps, POEPMcreate was defined. It includes the 4 steps corresponding
to the atoms of the Boolean algebra for 2 variables, that is, the steps for f1, f2, f4, and f8,
in the first row of nodes up from the bottom in Figure 1. In terms of a Venn diagram
as in Figure 2, these steps cover exactly the four regions of the viewpoint space. But
the question of whether other subsets of the steps of EPMcreate could work is still
open. The problem is that there is a huge number of combinations of the 16 steps:
according to the combinatorial calculus, even assuming that we are not repeating any
step and that order matters, there are 16!⁄(k! ×(16−k)!) steps for each subset with k of
the 16 steps. The goal of this paper is to propose criteria that could be applied to
choose from among so many combinations.</p>
      <p>First of all, if no information were available, even the criteria of choosing a random
set of functions could be applied, but this hypothesis can be discharged thanks to the
theoretical basis of the EPMcreate.</p>
      <p>General criteria to choose the number of steps and the steps of EPMcreate with
which to generate a lighter creativity technique are:
• time constraints: According to the experiments, a minimum time of 6 minutes
per step should be given. In the experiments run so far, when the time for each
step was from 15 to 30 minutes, no one complained about not having enough
time. Data about the number of requirement ideas generated per unit of time
could be used for more precise suggestions.
• requirements to be gathered vs. viewpoint: If one of the target users is more
important, steps producing more requirements for that viewpoint could be
chosen. Another possible approach could be to include only the steps that
generate requirements for a given viewpoint. That is, for U1, all steps would be
used except for Steps 0, 4, 8, and 12.
• number of sessions: To maintain the 16 steps of EPMcreate, an EPMcreate
session could be split into two or more sessions that partition the 16 steps, i.e.,
that share no steps with each other, but that collectively cover all 16 steps.</p>
      <p>Two other factors that can be taken into account for choosing the steps are the size
of the project and the type of the requirements (e.g., high-level vs. usability, or
functional vs. non-functional).</p>
      <p>
        A three-viewpoint variant of EPMcreate could be applied to take into account of
three different targets [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], but that would require experiments to test how analysts
could manage to think in three different viewpoints at the same time.
† EMPcreate covers only the first idea generation phase of a creative process. Many a creativity
method suggests including other, follow-on phases, such as idea evaluation and pruning.
      </p>
      <p>
        An exhaustive analysis of the combinations of steps starting from 1-step technique
and finishing with 16-step ones could be useful, but too complex. Applying a criterion
similar to that used to define POEPMcreate, in this paper we will start considering
techniques with 1, 2, 4, and 8 of the EPMcreate steps.
1-step techniques. As explained in Section 2, three of EPMcreate steps correspond to
existing creativity techniques, and applying any one of these existing techniques is
equivalent to a reduction of EPMcreate to the technique. In particular, Step 0 is
similar to the Creative Pause Technique [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]; Step 8 is similar to Synapsis [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], and,
in a sense, Step 15 is similar to brainstorming [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. In Boolean algebra, f0 and f15
correspond respectively to the null and the universal subsets. Both Step 0 and Step 15
are relevant from a theoretical point of view, as they are basic elements of any
algebra.
2-step techniques. There are 120 two-step techniques. A first reasonable assumption
is that Step 0, a good first step with which to start any creative requirements
elicitation process, should always be included. This step is always implicitly run
whenever mind blanking is required to allow concentration for the upcoming session.
Adding Step 15 to Step 0 yields the basic process of many a creativity technique:
Blank your mind and then start to say anything that comes to your mind. According to
the criterion of combining two steps to cover all the areas of the Venn diagrams, there
are 7 pairs of steps that could be used, that is Steps 1 and 14, Steps 2 and 13, etc. In
each of these pairs, the sum of the step numbers is 15. Combining Step 3 and Step 5
corresponds to the classical looking for the requirements for the two target users, U1
and U2.
4-step techniques. These techniques include POEPMcreate, that for at least websites,
works better than EPMcreate. Another 4-step technique, based on Step 0, Step 3, Step
5, and Step 15 corresponds to a requirements elicitation session in which after a
mindblanking step, Step 0, requirements for targeted users U1 and U2 are gathered with
Steps 3 and 5, finishing with a catch-all requirements check with Step 15.
8-step techniques. The definition of the EPMcreate steps according to the EPM
suggests that the steps from Step 8 onward, corresponding to the anti-functions,
should be more creative. More information is needed to suggest other combinations
with 8 steps.
      </p>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>This paper illustrates that EPMcreate can be used to generate lighter creativity
techniques based on subsets of its 16 steps. It offers a preliminary description of the
criteria that could be applied to choose among the large number of subsets of the
original 16-step technique. The effectiveness of variants of EPMcreate based on one
or more of these criteria need to be tested by experiments. To test all the possible
combinations of the steps in a significant way is very demanding. Therefore,
theoretical insights are valuable to point the way to promising subsets of steps. A
research strategy for future work should be defined to tackle the variety of issues and
questions raised in the paper. First of all, future work can use the results of past
experiments in a meta-analysis to obtain data to support selection of the variants of
EPMcreate. The list of open questions includes a systematic comparison of the steps
of EPMcreate with other creativity techniques, the ways in which to test a given
combination of steps against another combination, an analysis of the factors to be
taken into account for choosing a given subset of steps (as for example, the type of
software projects, time constraints, analysts expertise).</p>
      <p>Acknowledgements. Daniel Berry’s work was supported in part by a Canadian
NSERC grant NSERC-RGPIN227055-00.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>De Giacomo P.: Mente</surname>
          </string-name>
          e Creatività:
          <article-title>Il Modello Pragmatico Elementare quale strumento per sviluppare la creatività in campo medico, psicologico e manageriale</article-title>
          .
          <source>Franco Angeli</source>
          , Milano, IT (in Italian) (
          <year>1995</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Silvestri</surname>
          </string-name>
          . A.,
          <string-name>
            <surname>De Giacomo</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pierri</surname>
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lefons</surname>
            ,
            <given-names>E</given-names>
          </string-name>
          , Pazienza,
          <string-name>
            <surname>M.T.</surname>
          </string-name>
          , Tangorra F.:
          <article-title>A basic model of interacting subjects</article-title>
          .
          <source>Cybern Syst International Journal</source>
          <volume>11</volume>
          ,
          <fpage>115</fpage>
          -
          <lpage>129</lpage>
          (
          <year>1980</year>
          ).
          <source>doi:10.1080/01969728008960230</source>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Glass</surname>
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Software creativity</article-title>
          . Prentice Hall, Englewood
          <string-name>
            <surname>Cliffs</surname>
          </string-name>
          (
          <year>1995</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Robertson</surname>
            <given-names>J.</given-names>
          </string-name>
          :
          <source>Eureka! Why Analysts Should Invent Requirements, IEEE Software 19(4)</source>
          , pp.
          <fpage>20</fpage>
          -
          <lpage>22</lpage>
          , (
          <year>2002</year>
          ). doi:
          <volume>10</volume>
          .1109/MS.
          <year>2002</year>
          .1020281
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carroll</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Swatman</surname>
            ,
            <given-names>P.A.</given-names>
          </string-name>
          :
          <article-title>Supporting and monitoring the creativity of IS personnel during the requirements engineering process</article-title>
          ,
          <source>33rd Hawaii Int. Conf. on System Sciences (Vol. 7)</source>
          , January 4-
          <issue>7</issue>
          , 2000 Maui, Hawaii (
          <year>2000</year>
          ). doi:
          <volume>10</volume>
          .1109/HICSS.
          <year>2000</year>
          .926899
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>De Pisapia</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bacci</surname>
            <given-names>F</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parrott</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Melcher</surname>
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Brain networks for visual creativity: a functional connectivity study of planning a visual artwork</article-title>
          .
          <source>Scientific Reports</source>
          <volume>6</volume>
          :
          <fpage>39185</fpage>
          (
          <year>2016</year>
          ). doi:
          <volume>10</volume>
          .1038/srep39185
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Mich</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Anesi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berry</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          :
          <article-title>Applying a pragmatics-based creativity-fostering technique to requirements elicitation</article-title>
          .
          <source>Requirements Engineering</source>
          ,
          <volume>10</volume>
          (
          <issue>4</issue>
          ), pp.
          <fpage>262</fpage>
          -
          <lpage>275</lpage>
          (
          <year>2005</year>
          ).
          <source>doi:10.1007/s00766-005-0008-3</source>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Mich</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berry</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alzetta</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Individual and end-user application of the EPMcreate creativity enhancement technique to website requirements elicitation</article-title>
          .
          <source>In 1st Work. on Creativity in Requirements Engineering (CreaRE) at REFSQ</source>
          <year>2010</year>
          , pp.
          <fpage>22</fpage>
          -
          <lpage>31</lpage>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Sakhnini</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mich</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berry</surname>
            ,
            <given-names>D.M.:</given-names>
          </string-name>
          <article-title>The effectiveness of an optimized EPMcreate as a creativity enhancement technique for Web site requirements elicitation</article-title>
          .
          <source>Requirements Engineering</source>
          ,
          <volume>17</volume>
          (
          <issue>3</issue>
          ), pp.
          <fpage>171</fpage>
          -
          <lpage>186</lpage>
          (
          <year>2012</year>
          ).
          <source>doi:10.1007/s00766-011-0133-0</source>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Watzlawick</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Behavin</surname>
            ,
            <given-names>J.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jackson</surname>
            ,
            <given-names>D.D.</given-names>
          </string-name>
          :
          <article-title>Pragmatics of human communication</article-title>
          .
          <source>Norton</source>
          , New York (
          <year>1967</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Bateson</surname>
          </string-name>
          , G.:
          <article-title>Steps to an ecology of mind</article-title>
          , New York, Ballantine (
          <year>1972</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Preparata</surname>
            ,
            <given-names>F.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yeh</surname>
          </string-name>
          , R.T.Y.:
          <article-title>Introduction to discrete structures for Computer Science</article-title>
          and Engineering.
          <string-name>
            <surname>Addison-Wesley</surname>
            <given-names>Longman</given-names>
          </string-name>
          , Boston, MA, USA (
          <year>1973</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>De Bono</surname>
          </string-name>
          , E.:
          <article-title>Lateral thinking: creativity step by step</article-title>
          . New York; Harper &amp; Row; (
          <year>1970</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. Aznar G.:
          <article-title>la Creativité dans l'enterprise. Organisation pratique et technique d'animation</article-title>
          , Paris, Les Editions d'organisation (
          <year>1971</year>
          ).
          <source>doi:10.7202/1003695</source>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Osborn</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Applied imagination</article-title>
          . Charles Scribner's, New York (
          <year>1935</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Sakhnini</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mich</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berry</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          (
          <year>2017</year>
          ):
          <article-title>Group versus individual use of Power-Only EPMcreate as a creativity enhancement technique for requirements elicitation</article-title>
          .
          <article-title>Accepted to Empirical Soft Eng (</article-title>
          <year>2017</year>
          ). doi:
          <volume>10</volume>
          .1007/s10664-016-9475-z
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Sakhnini</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mich</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berry</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          :
          <article-title>Group Versus Individual Use of an Optimized and the Full EPMcreate as Creativity Enhancement Techniques for Web Site Requirements Elicitation</article-title>
          .
          <source>Technical Report</source>
          , University of Waterloo (
          <year>2016</year>
          ). https://cs.uwaterloo.ca/~dberry/FTP_SITE/tech.reports/SakhniniMichBerryTR.pdf
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>