<!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 a Framework for Analytics-driven Domain-speci c Mashup Environments</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Michael Aram</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gustaf Neumann</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Vienna University of Economics and Business Institute for Information Systems and New Media Welthandelsplatz 1</institution>
          ,
          <addr-line>Building D2, 1020 Vienna</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Mashup environments enable end users to directly engage in the design process of the information system. Traditional mashup technology o ers users generic components and therefore targets technically skilled people. Recent research investigates domain-speci c mashup platforms with the aim to be easier to understand and use. We present a proposal for research towards a generic framework that supports the design of domain-speci c mashup environments through native analytics.</p>
      </abstract>
      <kwd-group>
        <kwd>Evolutionary Information Systems</kwd>
        <kwd>Secondary Design</kwd>
        <kwd>Mashups</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        In this paper, we conceive of an information system as consisting of human
beings and/or machines that are interconnected via communication relationships
and that produce and/or use information [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Accordingly, we interpret an
educational information system as a sub-part of a computer-based organizational
information system where educational processes are at the center of attention.
Core processes include learning, coaching, assessment and delivery of learning
content [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]; supporting processes are e.g. authoring of learning material,
development of learning applications or administration processes.
      </p>
      <p>
        The traditional mindset considers the technological part of an information
system as being designed by software developers and used by end-users. The
concept of secondary design, however, interprets end-users as \designers in their
own right", who are actively engaged in the design and modi cation of the
information system within the context of use [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. This is particularly desirable
because organizations, and therefore their processes, are necessarily constantly
evolving due to an ever-changing environment. This in turn demands for highly
tailorable technology [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] that can be continuously and substantially adapted by
its stakeholders, particularly by domain experts. In line with [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], we use the term
Evolutionary Educational Information System (EEIS)1 to refer to this class of
educational information systems.
1 \Evolutionary Information Systems" should be understood as an emerging research
eld that is currently developed and explored at our institute in a joint research
e ort of several researchers (see also [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]). The hereby proposed research into mashup
environments by the author is embedded within this conceptual frame.
      </p>
    </sec>
    <sec id="sec-2">
      <title>Problem Areas and State of the Art</title>
      <p>
        In [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], we have tried to identify three highly relevant dimensions within the
research eld around evolutionary systems, thus providing the overall directions for
further investigation { and the broader frame for the hereby proposed research:
D1 { Systematic discovery of improvement potentials within the system.
D2 { Incremental application of corresponding modi cations into the system.
      </p>
      <p>
        D3 { Inclusion of stakeholders into the continuous design process of the system.
With respect to these objectives the emerging mashup paradigm [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] promises a
possible solution space. In line with our notion of EEISs, a mashup environment
comprises a mashup platform plus organizational structures and actors [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. A
mashup platform is a tailorable technology [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] that allows end users to create,
use, modify and exchange mashups. Mashups are personalized, situational
applications created by end users by dynamically combining web resources to address
the current needs of a person or community [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. An enterprise mashup stack
comprises three central technological concepts, i.e. web-based resources, which are
virtualized into widgets and nally combined on demand into mashups [
        <xref ref-type="bibr" rid="ref7 ref8">7, 8</xref>
        ]. In
general, mashup platforms contribute to the area of D2 by providing a means to
adapt a system's behavior. In providing a means for end user programming [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ],
mashup environments tackle problem area D3. Furthermore, being frequently
used for situational reporting and analytics, mashup platforms can generally
contribute to research direction D1, thus enabling a \business intelligence for
the masses" concept [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>
        Recent e orts investigate Domain-speci c Mashup Platforms, hence aim to
apply the concept of domain-speci c languages [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] to the mashup paradigm (see
e.g. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]). Here, the main goal remains to make the mashup experience as simple
as possible for the end user. This is attempted by providing easy-to-understand
domain-speci c components instead of domain-agnostic generic components. For
example, \ResEval Mash" [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] represents a domain-speci c mashup platform for
conducting research evaluation.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Research Questions and Challenges</title>
      <p>
        As we position this research within the eld of Evolutionary Information
Systems, we ultimately aim at enabling secondary design within an EEISs in a
uni ed approach. We strive to integrate techniques from the broad elds of
analytics [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], domain-speci c languages and mashup technologies in a
comprehensive framework. Within the mindset we have sketched so far, we formulate both
a high-level research question and an incomplete set of derived sub-questions.
How should a framework be designed that supports domain experts in their
secondary design of Domain-speci c Mashup Environments through analytics within
the context of an Evolutionary Educational Information System?
tu
We are going to search for an answer to this question by investigating the related
phenomena within the Technology Enhanced Learning (TEL) domain.
Therefore, we consider relevant educational stakeholders (e.g. developers of learning
resources, e-learning assistants, teachers) as the domain experts, and the systems
that we have direct access to2 as the EEISs. Within an abductive re ection
process, several more concrete subquestions arise. Note, however, that this tentative
set is expected to be extended and amended in the course of our design-oriented
research e ort.
      </p>
      <p>
        { What should be designed in the primary design process, and what should be
intentionally left to the secondary design of the domain experts?
{ How can we enable secondary design of the Domain-speci c Mashup
Environments (DSMEs) and still preserve control of the system functions?
{ How should one account for and deal with \transitive secondary design",
i.e. when the secondary design process of domain experts actually acts as
primary design for the secondary design of other end-user groups?
{ What is a suitable \gentle slope" [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] deployment process for the incremental,
evolutionary establishment of such mashup environments within an EEIS?
{ How can we incorporate analytics to facilitate the emergence and sustainable
integration of a DSMEs within an EEIS?
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>A Framework for Analytics-driven Domain-speci c</title>
    </sec>
    <sec id="sec-5">
      <title>Mashup Environments</title>
      <p>
        We aim to tackle the identi ed problems by means of a design-oriented research
approach [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. In this section, we sketch a tentative solution suggestion. In a
nutshell, the proposed solution shall be manifested in the form of a highly tailorable
framework that empowers domain experts to design and maintain DSMEs based
on analytics. Our domain-aware and design-oriented research approach
implicitly requires us to construct and deploy working software within an EEIS, which
implies technological and organizational opportunities and constraints. The
actual implementation is particularly important, as its continuous introspection
within the EEISs is essential for developing and evaluating it. The intention is
to develop software within the technological framework that runs our real world
learning platforms. In particular, this stack comprises the dotLRN learning
management system that is based on the OpenACS community framework, which in
turn relies on NaviServer, PostgreSQL and the Next Scripting Framework3.
4.1
      </p>
      <sec id="sec-5-1">
        <title>Objectives of the Solution</title>
        <p>The overall goal of e orts in the eld of EEISs is to make progress with respect to
the three research directions (D1{D3). In addition to that, we present here a list
2 These are Learn@WU (see https://learn.wu.ac.at) and LMS.at (see https://lms.at),
large learning platforms of the WU Vienna and for Austrian schools, respectively.
3 Please refer to the respective web sites: http://dotlrn.org, http://openacs.org,
http://naviserver.sourceforge.net, http://postgresql.org, http://next-scripting.org.
of relevant high-level objectives of this concrete research e ort. For brevity,
typical requirements known from the eld of software engineering (e.g. performance,
scalability, usability, etc.) and from research projects (e.g. rigorous architectural
design decisions, openness, etc.) are not mentioned explicitly.</p>
        <p>
          High Tailorability for Enabling Secondary Design of DSMEs. Our main objective
is to design, develop, and deploy a framework that allows diverse stakeholders
within an EEIS to collaboratively construct mashup environments speci cally
tailored to their respective domains and needs. Thus, the design decisions made
in the course of the construction of the framework shall account for the concept
of secondary design. Firstly, this includes a generic infrastructure that allows
technical experts to develop and integrate internal or external resources and
make them available for the domain experts in the form of \virtualized
components" (widgets) [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Secondly, it requires means for the domain experts to
derive or introduce domain-speci c components. Thirdly, end users within the
organization should be enabled to e ciently nd, evaluate, and use these tailored
domain-speci c components (widgets, mashups, and resources).
        </p>
        <p>
          Native Analytics. The need for analytics is especially true for Evolutionary
Information Systems (EISs), which strive to enable secondary design and
therefore require means for investigating and interpreting the system's behavior in a
quanti able manner. Firstly, as a basis, data generated by (instantiations of) the
framework shall follow clear semantics (e.g. via collaboratively de ned
ontologies) in order to facilitate data mining techniques [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. Secondly, the framework
shall facilitate domain-relevant analytics, e.g. via collaboratively-annotated
situational analytics mashups. This is intended to support a continuous evaluation
of the mashup environment and its underlying processes for all its stakeholders,
ultimately contributing to D1.
        </p>
        <p>
          Incremental Applicability. We state the applicability and deployability of the
framework within an existing EEIS as an important objective (see D2), both from
a technological and an organizational perspective. The latter demands a \gentle
slope" system [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] that can be incrementally learned by the domain experts.
Therefore, means for the inclusion or transformation of (legacy) components
and artifacts from the existing system shall be considered.
4.2
        </p>
      </sec>
      <sec id="sec-5-2">
        <title>Contributions</title>
        <p>
          The hereby proposed research e ort is intended to contribute to the eld of
information systems research and to relevant reference disciplines and sub-areas
such as TEL, domain-speci c software engineering and learning analytics. The
contributions, i.e. additions to the knowledge base, are going to be artifacts [
          <xref ref-type="bibr" rid="ref14 ref16">14,
16</xref>
          ], and in particular open source software. The artifacts, which embody the
new knowledge, are going to comprise (i) design principles for the construction
of DSMEs within EEISs; (ii) concrete models describing the constructed
environments and abstract models that generalize from these; (iii) experiences from
and methods for constructing such environments.
        </p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>A Pluralistic Design-oriented Research Con guration</title>
      <p>
        In general, research is \an activity that contributes to the understanding of a
phenomenon" [
        <xref ref-type="bibr" rid="ref14 ref17">14, 17</xref>
        ]. In design-oriented research, these phenomena are partly
created by the researcher [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. The construction process is supposed to reveal
design principles that can be applied to a class of similar systems [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. Numerous
process models can be found in the literature, from \micro-scale" cognitive
models [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] over \project-scale" [
        <xref ref-type="bibr" rid="ref20 ref21">20, 21</xref>
        ] to \macro-scale" aggregate models
applicable to e orts of multiple research communities [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. However, a common scheme
among these process models remains. After some form of problem awareness or
trigger, the researcher iteratively switches between constructive and evaluative
activities. The construction allows for creativity, nevertheless design decisions
must be grounded in the knowledge base and be made explicit [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ].
      </p>
      <p>
        A range of di erent qualitative and quantitative evaluation approaches [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]
seems appropriate for the various parts of this research. Ultimately, the created
artifacts are going to be evaluated against the de ned goals and objectives.
For example, while the architecture of the system will be evaluated by means
of expert reviews, interviews or con rmatory focus groups [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] with domain
experts will be considered for evaluating the appropriateness of the system for
the business environment. As our intention is to natively incorporate analytics,
we expect to be able to directly gain useful quantitative usage data.
6
      </p>
    </sec>
    <sec id="sec-7">
      <title>Conclusion and Outlook</title>
      <p>
        We have presented our intention to succeed with research into DSMEs. We
believe that incorporating analytics into these systems has the potential to make
them even more useful and e ective and can help to tackle some of the problems
that arise within EEISs. We conclude this paper with a research agenda.
M1 { Tentative Design. A crucial rst step is to further elaborate the solution
suggestion to result in a tentative design [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. We expect this to include
design principles, high level architectural models, and user interface mockups.
M2 { Mashup Platform Prototype. As a basis for further developments, we
plan to implement a prototype of a exible mashup platform based on and
integrated with our existing EEISs.
      </p>
      <p>M3 { DSMEs Prototype. This iteration of the prototype development shall
actually enable domain experts to design DSMEs.</p>
      <p>M4 { Analytics-based DSMEs Prototype. In this phase we are going to enhance
the process of designing DSMEs by using analytics.</p>
      <p>M5 { Evaluation. While various evaluation activities will have already
happened at this stage, we will nally evaluate the prototype within its
environment for its appropriateness to tackle the overall problem areas and de ned
objectives (see Sections 2 and 4). To this end, a framework for continuous
evaluation is intended to be designed and included from the beginning.
The activities preceding each milestone are expected to take us about two
months, and we plan at least one publication as a result.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Hansen</surname>
            ,
            <given-names>H.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Neumann</surname>
          </string-name>
          , G.:
          <article-title>Wirtschaftsinformatik 1</article-title>
          . UTB,
          <string-name>
            <surname>Stuttgart</surname>
          </string-name>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Tyler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          et al.:
          <volume>1484</volume>
          .1
          <article-title>- IEEE Standard for Learning Technology - Learning Technology Systems Architecture (LTSA)</article-title>
          .
          <source>IEEE Computer Society</source>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Germonprez</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hovorka</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gal</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Secondary Design: A Case of Behavioral Design Science Research</article-title>
          .
          <source>Journal of the Association for Information Systems</source>
          .
          <volume>12</volume>
          ,
          <issue>10</issue>
          , 662{
          <fpage>683</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Germonprez</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hovorka</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Collopy</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>A Theory of Tailorable Technology Design</article-title>
          .
          <source>Journal of the Association for Information Systems</source>
          .
          <volume>8</volume>
          ,
          <issue>6</issue>
          , 351{
          <fpage>367</fpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Neumann</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aram</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sobernig</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>Evolutionary Business Information Systems. [forthcoming]</source>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Hoyer</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fischer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Market Overview of Enterprise Mashup Tools</article-title>
          . In: Bouguettaya,
          <string-name>
            <given-names>A.</given-names>
            et al. (eds.)
            <surname>Service-Oriented Computing</surname>
          </string-name>
          <string-name>
            <surname>ICSOC</surname>
          </string-name>
          <year>2008</year>
          . pp. 708721 Springer Berlin Heidelberg (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Pahlke</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wolf</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>Enterprise Mashup Systems as Platform for Situational Applications - Bene ts and Challenges in the Business Domain</article-title>
          .
          <source>Business &amp; Information Systems Engineering. 2</source>
          ,
          <issue>5</issue>
          , 305{
          <fpage>315</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Hoyer</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stanoesvka-Slabeva</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janner</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schroth</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          : Enterprise Mashups:
          <article-title>Design Principles towards the Long Tail of User Needs</article-title>
          .
          <source>In: Proceedings of the 2008 IEEE International Conference on Services Computing (SCC</source>
          <year>2008</year>
          ),
          <volume>601</volume>
          {
          <fpage>602</fpage>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Cypher</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          et al.:
          <article-title>No Code Required: Giving Users Tools to Transform the Web</article-title>
          . Morgan Kaufmann (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Fowler</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Domain-Speci c Languages</surname>
          </string-name>
          .
          <string-name>
            <surname>Addison-Wesley Professional</surname>
          </string-name>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Soi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Domain Speci c Mashup Platforms as a Service</article-title>
          .
          <source>PhD Dissertation</source>
          . DISI - University of Trento (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Long</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Siemens</surname>
          </string-name>
          , G.:
          <article-title>Penetrating the Fog: Analytics in Learning and Education</article-title>
          .
          <source>Educause Review 09/10</source>
          <year>2011</year>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>MacLean</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carter</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lvstrand</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moran</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>User-tailorable systems: pressing the issues with buttons</article-title>
          .
          <source>In: Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</source>
          (
          <year>1990</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Vaishnavi</surname>
            ,
            <given-names>V.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuechler</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          : Design Science Research Methods and Patterns. Auerbach
          <string-name>
            <surname>Publications</surname>
          </string-name>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Van der Aalst</surname>
            ,
            <given-names>W. M. P.</given-names>
          </string-name>
          : Process Mining. Springer, Berlin Heidelberg (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>March</surname>
          </string-name>
          , S.T.,
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>G.F.</given-names>
          </string-name>
          :
          <article-title>Design and natural science research on information technology</article-title>
          .
          <source>Decision Support Systems</source>
          .
          <volume>15</volume>
          ,
          <issue>4</issue>
          , 251{
          <fpage>266</fpage>
          (
          <year>1995</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chatterjee</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>Design Research in Information Systems: Theory and Practice</source>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Sein</surname>
            ,
            <given-names>M.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Henfridsson</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Purao</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rossi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lindgren</surname>
          </string-name>
          , R..
          <source>: Action Design Research. MIS Quarterly</source>
          .
          <volume>35</volume>
          ,
          <issue>1</issue>
          , 37{
          <fpage>56</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Takeda</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Veerkamp</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tomiyama</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yoshikawa</surname>
          </string-name>
          , H.:
          <article-title>Modeling Design Processes</article-title>
          .
          <source>AI Mag</source>
          .
          <volume>11</volume>
          ,
          <issue>4</issue>
          , 37{
          <fpage>48</fpage>
          (
          <year>1990</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20. Pe ers,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Tuunanen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Rothenberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.A.</given-names>
            ,
            <surname>Chatterjee</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.</surname>
          </string-name>
          :
          <source>A Design Science Research Methodology for Information Systems Research. Journal of Management Information Systems</source>
          .
          <volume>24</volume>
          ,
          <issue>3</issue>
          , 45{
          <fpage>77</fpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Nunamaker</surname>
            ,
            <given-names>J.F.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          :
          <article-title>Systems development in information systems research</article-title>
          .
          <source>Proceedings of the 23rd Annual HICSS</source>
          ,
          <year>1990</year>
          . pp.
          <volume>631</volume>
          {640 vol.
          <volume>3</volume>
          (
          <year>1990</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Schermann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gehlert</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krcmar</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pohl</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Justifying design decisions with theory-based design principles</article-title>
          .
          <source>In: ECIS 2009 Proceedings</source>
          .
          <article-title>(</article-title>
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>