<!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>Fostering an Enterprise Architecture's Value Proposition Using Dedicated Presentation Strategies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Christian Kluge</string-name>
          <email>c.kluge@qut.edu.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andreas Dietzsch</string-name>
          <email>andreas.dietzsch@mobi.ch</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Rosemann</string-name>
          <email>m.rosemann@qut.edu.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Queensland University of Technology, Faculty of Information Technology Brisbane Qld 4000</institution>
          ,
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Swiss Mobiliar Bundesgasse 35</institution>
          ,
          <addr-line>3001, Bern</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
      </contrib-group>
      <fpage>240</fpage>
      <lpage>243</lpage>
      <abstract>
        <p>Enterprise Architectures as Means in Business - IT Alignment As exclusively technology-focused solutions do not provide any strategic competitive advantages nowadays ([1]), IT service provision needs to focus on business requirements. Consequently, adequately aligned IT services need to combine a good efficiency-/effectiveness ratio and adequate innovation power with regard to a business' overall strategic objectives ([2]). According to Henderson and Venkatraman's model of strategic Business - IT alignment ([3]), the necessary comprehensive change coordination and management approach needs to comprise business strategy, organisational structure and processes as well as IT strategy, IT related processes and infrastructure. In addition, Aier ([4]) shows that sustainable changes within an organisation demand an active participation of all affected persons (strategy of participation). At the same time, the affected systems need to be fully compatible or to be separated completely (strategy of consistency)1. Taking into account requirements of aligned and sustainable changes in an organisation, a common information and communication base is required to foster coordination between the involved stakeholders. As recent surveys by e.g. Infosys ([5]) and the Institute for Enterprise Architecture Developments (IEAD, [6]) show, Enterprise Architectures (EA) are widely expected to provide the common foundation, an integrated management of organisational capabilities, applications and IT infrastructure, can be build upon. Though recent EA developments revealed a growing maturity in this area (see e.g. Hafner and Winter's article indicating a set of standard EA layers and a standard EA development process model, [7]), evidences from the field show, that an EA's value proposition cannot be released easily. In particular, as our</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1 Here we apply a rather broad notion of the term system, not only including
information systems, but also organisational structures within an organisation.
case studies with an Australian utility company and a Swiss insurer as well as
the aforementioned EA surveys show, an EA’s perceived value to non IT-related
stakeholders remains a major issue currently.
2</p>
      <p>
        Why Haven’t Enterprise Architectures Delivered Yet?
As outlined by a Gartner report in 1995 ([
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]) architecture should not be limited
to documents and models only, but also be considered as an ongoing and
iterative (political) process. Consequently, in the context of this paper we will apply
a comprehensive definition of EA, as given by Schoenherr and Aier,
considering EA as the “joint action of technological, organisational, and psycho-social
measures during development and operation of enterprise information systems”
(see [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], p. 3). Given Henderson and Venkatraman’s work it does not focus on
IS solely, since (sustainable) changes within IT must inevitably be accompanied
by appropriate business changes and vice versa. In the light of our definition an
EA needs to satisfy two major requirements consequently:
– Meet EA stakeholders’ concerns, i.e. capture the right information
– Offer EA content to stakeholders in a satisfactory way in terms of:
• Architecture effectiveness (doing the right things)
• Architecture efficiency (doing the things right)
      </p>
      <p>
        Investigating recent surveys ([
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ]) in more detail, it can easily be noticed
that although most EA applicants intend to solve questions from various areas,
only a few actually address issues from non-IT areas. In addition, it is worth
noticing that the majority of the enterprise architects are associated with their
organisation’s IT departments primarily.
      </p>
      <p>
        Proper et al. ([
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]) investigated the principles underlying a modelling
concept’s utility in more detail. Thereby they found, that a model’s value to a
viewer is determined by three major components: appropriate consideration of
the model user’s concerns, the applied meta-model (i.e. the concepts used by
a viewer when observing the domain) and the modelling outcomes’
representation. Consequently, the lacking value proposition for business stakeholders might
partly be explained by different concerns applied by the model creator (usually
predominantly IT-related) and the future model users (business related).
      </p>
      <p>
        This is due to the second component of Proper’s findings, the underlying
meta-models in the modelling process. Proper et al. arguably presume that
model users are able to express their viewpoints. Yet, it would not ensure a
full understanding necessarily as it will require the use of language. Given their
differing meta-models, model user and creator are subject to all sorts of
(implicit and unintended) misunderstandings by using the same words (symbols)
for different concepts (thoughts) and vice versa (see concept of the semiological
triangle, [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]).
Using Presentation Strategies to Foster an Enterprise
Architecture’s Value Proposition
Although a full alignment of the meta-models by model user and creator might
not be achievable (see section 2), a better alignment leading to an enhanced EA
value proposition remains desirable. Assuming an appropriate coverage of the
relevant domain, we propose the introduction of a dedicated presentation
strategy implemented by a presentation layer to foster the intended harmonisation.
In doing so, the presentation strategy assures an adequate level of the provided
EA services, whereby the presentation layer enables the modelling outcomes’
presentation according to stakeholders’ needs and skills.
      </p>
      <p>By integrating a presentation layer, we also avoid the need to establish
different architectural descriptions for distinct stakeholder groups. Instead, Enterprise
Architects will be enabled to take advantage of current (IT-related) modelling
methodologies ensuring consistency and integrity of large models, while at the
same time presenting the required information in an appropriate and
meaningful manner to stakeholders from non-IT related areas. Nevertheless, such a
layer implementation will face three major challenges: the determination of the
right information for the targeted stakeholders, the establishment of appropriate
presentation techniques and adequate value communication as an issue in EA
management.</p>
      <p>Apart from issues surrounding different universe perceptions, EA
information requirements engineering will also suffer from the current lack of EA value
awareness by the targeted audience. Therefore we propose the application of
an EA Reference Query Set targeting a common set of information needs by
non-IT related stakeholders. In doing so, the query set will not only foster an
early value perception but also support the targeted stakeholders in
determining potential future applications of the captured information. As an approach
towards appropriate presentation techniques, we currently investigate the use
of Business Information Sheets providing condensed and preprocessed readily
applicable decision-relevant information on a single page which can be detailed
upon request.</p>
      <p>Though, as already highlighted briefly above, a presentation layer’s services
need to be reevaluated and revised constantly. Therefore, it must be
accompanied by an overarching presentation strategy assuring not only an adequate
stakeholder involvement but also well-defined feedback and revaluation cycles.</p>
      <p>
        The approach described in this position paper is part of our investigation
concerning the value proposition of an EA on a corporate level. In course of
our research and our case studies we developed a comprehensive EA value
realisation model based on the model of IS success by DeLone and McLean (see
[
        <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
        ]). Thereby, the presented presentation strategy and layer approach forms
the first stage of our value realisation model, ensuring a sufficient stakeholder
value perception and awareness. The latter will be turned into realised EA value
subsequently using appropriate EA governance strategies.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Carr</surname>
            ,
            <given-names>N.G.: IT</given-names>
          </string-name>
          <string-name>
            <surname>Doesn't Matter</surname>
          </string-name>
          .
          <source>Harvard Business Review</source>
          <volume>81</volume>
          (
          <issue>5</issue>
          ) (
          <year>2003</year>
          )
          <fpage>41</fpage>
          -
          <lpage>49</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Mieze</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Beyond Carr - und sie bewegt sich doch</article-title>
          .
          <source>HMD - Praxis der Wirtschaftsinformatik (239)</source>
          (
          <year>2004</year>
          )
          <fpage>18</fpage>
          -
          <lpage>27</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Henderson</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Venkatraman</surname>
          </string-name>
          , N.:
          <article-title>Strategic alignment: Leveraging information technology for transforming organizations</article-title>
          .
          <source>IBM Systems Journal</source>
          <volume>32</volume>
          (
          <issue>1</issue>
          ) (
          <year>1993</year>
          )
          <fpage>4</fpage>
          -
          <lpage>16</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Aier</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Sustainability of Enterprise Architecture and EAI</article-title>
          . In Soliman, K.S., ed.:
          <source>Information Technology and Organizations in the 21st Century: Challenges &amp; Solutions. Proceedings of the 2004 International Business Information Management Conference</source>
          , Amman, Jordan,
          <source>International Business Information Management Association (IBIMA)</source>
          (
          <year>2004</year>
          )
          <fpage>182</fpage>
          -
          <lpage>189</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. Infosys:
          <article-title>Enterprise Architecture Survey 2005</article-title>
          .
          <source>Technical report, Infosys</source>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Schekkerman</surname>
          </string-name>
          , J.:
          <source>Trends in Enterprise Architecture</source>
          <year>2005</year>
          :
          <article-title>How are Organizations Progressing? Web-based survey, Institute for Enterprise Architecture Developments (</article-title>
          <year>2005</year>
          ) Download:
          <fpage>16</fpage>
          .
          <fpage>01</fpage>
          .
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hafner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Winter</surname>
          </string-name>
          , R.:
          <article-title>Vorgehensmodell fu¨r das Management der unternehmensweiten Applikationsarchitektur</article-title>
          . In
          <string-name>
            <surname>Ferstl</surname>
            ,
            <given-names>O.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sinz</surname>
            ,
            <given-names>E.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Eckert</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Isselhorst</surname>
          </string-name>
          , T., eds.: Wirtschaftsinformatik, Physica-Verlag (
          <year>2005</year>
          )
          <fpage>627</fpage>
          -
          <lpage>646</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Magrassi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Raphaelian</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>Architecture: A dialogue, not a document</article-title>
          .
          <source>Research Note TU-430-087</source>
          , Gartner Research (
          <year>1995</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Schoenherr</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aier</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Sustainable Enterprise Architecture - Central (EAI) vs. Decentral (SOA) Approaches to Define and Establish Flexible Architectures</article-title>
          .
          <source>In: Proceedings of the VIIth SAM/IFSAM World Congress</source>
          . (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Proper</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Verrijn-Stuart</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoppenbrouwers</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>On Utility-based Selection of Architecture-Modelling Concepts</article-title>
          . In Hartmann, S.,
          <string-name>
            <surname>Stumptner</surname>
          </string-name>
          , M., eds.: Second Asia-Pacific
          <source>Conference on Conceptual Modelling (APCCM)</source>
          .
          <article-title>Volume 43 of CRPIT</article-title>
          .,
          <source>Australian Computer Society</source>
          (
          <year>2005</year>
          )
          <fpage>25</fpage>
          -
          <lpage>34</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Ogden</surname>
            ,
            <given-names>C.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Richards</surname>
            ,
            <given-names>I.A.</given-names>
          </string-name>
          :
          <article-title>The Meaning of Meaning. A Study of The influence of Language upon Thought and of The Science of Symbolism</article-title>
          . Harcourt, Brace &amp; Company, New York (
          <year>1923</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>DeLone</surname>
          </string-name>
          , W.H.,
          <string-name>
            <surname>McLean</surname>
            ,
            <given-names>E.R.</given-names>
          </string-name>
          :
          <source>Information Systems Success: The Quest for the Dependent Variable. Information Systems Research</source>
          <volume>3</volume>
          (
          <issue>1</issue>
          ) (
          <year>1992</year>
          )
          <fpage>60</fpage>
          -
          <lpage>95</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>DeLone</surname>
          </string-name>
          , W.H.,
          <string-name>
            <surname>McLean</surname>
            ,
            <given-names>E.R.</given-names>
          </string-name>
          :
          <article-title>The DeLone and McLean model of information systems success: A ten-year update</article-title>
          .
          <source>Journal of Management Information Systems</source>
          <volume>19</volume>
          (
          <issue>4</issue>
          ) (
          <year>2003</year>
          )
          <fpage>9</fpage>
          -
          <lpage>30</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>