<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>A Socio-Technical Modeling Framework for Designing Enterprise Capabilities</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mohmmad Hossein Danesh</string-name>
          <email>danesh@cs.toronto.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science, University of Toronto</institution>
          ,
          <addr-line>Toronto</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <fpage>31</fpage>
      <lpage>46</lpage>
      <abstract>
        <p>The need for flexible and adaptive IT is ever more pressing as enterprises compete in global digital economies and ecosystems. To enable flexibility and adaptability of IT, one requires tools and techniques that enable co-design of IT and business. Hence, this research builds on the strategic management literature, particularly the research on dynamic capabilities, to propose a socio-technical modeling framework for designing enterprise capabilities. An agent-oriented modeling framework for understanding social and technical requirements when designing enterprise capabilities is proposed by building on conceptual modeling practices and techniques. An overview of the research design consisting of objectives, questions, and methodology is presented in this paper.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        The challenge of dynamic and evolving requirements faced by enterprise IT is twofold,
the need for (1) adaptable and reconfigurable software services/systems that can adjust
to changes [1], and (2) a flexible organization that can develop, support and leverage
such systems/services [
        <xref ref-type="bibr" rid="ref3 ref4">2–4</xref>
        ]. Understanding and analyzing the complexities and
behaviors of interdependent enterprise actors, systems, processes, and structures are required
to overcome the design hurdles [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. In this process methods and constructs that enable
co-design of IT and the business organization is key [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        This research started with the question of “how to architect flexible IT to enable
adaptive enterprises”. The first step in answering the question was to understand what
kinds of flexibilities are needed to design adaptive enterprises, i.e., answer the question
of “flexibility towards what”. An investigation into the literature revealed that enabling
business and enterprise evolution in response to environment dynamism is the primary
concern of flexibility [
        <xref ref-type="bibr" rid="ref13 ref5">5, 13</xref>
        ].
      </p>
      <p>The above answer provoked an investigation into the strategic management
literature. The flexibility aspect of the research motivation narrows down the scope of the
investigation to inside-out views in strategic management which directed us to the
Dynamic Capability View (DCV) of the firm.</p>
      <p>
        Capabilities in DCV are defined as an organization’s ability to appropriately
assemble, adapt, integrate, reconfigure and deploy valued resources, usually, in
combination or co-presence [
        <xref ref-type="bibr" rid="ref14 ref15">14, 15</xref>
        ]. They are created through collaborative learning
processes that individual agents participate in, and are supported by the norms and culture
Copyright 2018 for this paper by its authors. Copying permitted
for private and academic purposes.
of the organization [
        <xref ref-type="bibr" rid="ref16">2, 16</xref>
        ]. Enterprises succeed by nurturing the ability to continuously
create valuable and difficult-to-replicate capabilities, often referred to as “dynamic
capabilities” [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
      </p>
      <p>Fig. 1 depicts the described journey from the initial motivating research question
around IT flexibility to the refined question that enterprises are dealing with on a day
to day basis. Therefore, the research objective is defined as enabling enterprises,
particularly managers and architects within enterprises, to answer the question of “How
to design for social and technical flexibility that enables creation, management and
evolution of Enterprise Capabilities?”.</p>
      <p>
        Conceptual modelers and IS designers have raised the abstraction level of the
design artifacts to better understand enterprise context and design higher quality
information systems [1]. For example, concepts such as value [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], goals [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], actors [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], and
business processes [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] have been used as abstractions to design information systems.
Similar to our quest into the strategic management literature, other practitioners and
researchers have also used the notion of capability to identify requirements and infer
strategic direction when designing information systems [
        <xref ref-type="bibr" rid="ref11 ref12">1, 11, 12</xref>
        ].
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Research Objectives and Questions</title>
      <p>To enable the design of flexible enterprise capabilities, the ability to perform analysis
and answer the questions presented in Table 1, is necessary. In this research, a
conceptual modeling approach is adopted to develop a framework consisting of modeling
constructs, methods, and tools that intend to answer the analysis questions of Table 1.</p>
      <p>
        The choice of using conceptual modeling practices is supported by the success of the
IS community in a) developing conduits that can represent and analyze technical,
business and organizational context [
        <xref ref-type="bibr" rid="ref18 ref19">18, 19</xref>
        ], b) guiding and enabling socio-technical design
and requirements engineering [
        <xref ref-type="bibr" rid="ref20 ref21">20, 21</xref>
        ], and c) allowing reuse of design artifacts in terms
of patterns and architectural decisions [
        <xref ref-type="bibr" rid="ref22">1, 22</xref>
        ].
How to design for social What Alternatives (including architectural patterns) are there
and technical flexibility available for the evolution/creation of an enterprise capability?
that enables creation, How to identify possible inflexibilities that inhibit
evolution/cremanagement and evolu- ation of enterprise capabilities?
tion of Enterprise Capa- What is the impact of choosing one alternative over the other and
bilities? what is the tradeoff?
      </p>
      <p>The above questions that elaborate the research objectives trigger the following
research questions as presented in Table 2.</p>
      <sec id="sec-2-1">
        <title>What would be an appropriate representation</title>
        <p>of enterprise capabilities for modeling and
analyzing competitiveness?
How does the concept relate to other concepts
within the enterprise such as services,
processes and resources?
How can one represent and analyze the
formation of enterprise capabilities to enable
answering the questions of Table 1?</p>
      </sec>
      <sec id="sec-2-2">
        <title>What are the different kinds of choices?</title>
      </sec>
      <sec id="sec-2-3">
        <title>How does one evaluate capabilities?</title>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Research Methodology</title>
      <p>
        Design Science Research (DSR) has become a prominent research method in both IS
engineering and IS management communities [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. Different steps of a typical design
cycle of the DSR methodology is presented in Fig. 2. The approach recommends
multiple cycles of the process to refine and enhance designed solution(s) through evaluation
and feedbacks.
      </p>
      <p>This thesis has adopted the DSR methodology. Throughout the research, a few
rounds of DSR design cycles with feedback received from both academia and industry
case studies are conducted. As an example, feedback from academia suggested the need
for a holistic understanding of the notion of capability and how it is related to other
modeling constructs and concepts. This feedback triggered a new design cycle. In the
interest of space more in depth discussion of the design cycles are not presented in this
paper, instead, we focus on elaborating the outcomes of the design iterations.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Overview of the Framework and its Components</title>
      <p>A modeling framework consisting of ten components as laid out in Fig. 3 is proposed
in response to discussed research questions. The first component is the conceptual
foundation serving as the main theoretical contribution of the thesis. It builds on an in-depth
review of concepts from literature and proposes an integrated meta-model for enterprise
capability and its relationships. The second component of the framework focuses on
the i* based instantiation of the meta-model. The third and fourth components are
practical guidelines for using and instantiating the modeling framework in the context of an
enterprise. Each component is developed as part of a case study.</p>
      <p>The next five components of the framework are analysis techniques that help
decision makers investigate and answer what-if questions. The last component as depicted
at the top of Fig. 3 is an overarching view and categorization of all decisions that must
be made throughout the lifecycle of a capability.</p>
      <p>In Table 3, the components are described with a specification of their purpose and
contributions to answering the research questions. The last column of Table 3 focuses
on the feedbacks or triggers that initiated the development of the component. The order
of the components presented in the table do not describe the sequence in which they
were developed.</p>
      <sec id="sec-4-1">
        <title>Trigger/</title>
      </sec>
      <sec id="sec-4-2">
        <title>Feedback</title>
        <sec id="sec-4-2-1">
          <title>Why are there many approaches?</title>
        </sec>
        <sec id="sec-4-2-2">
          <title>What are Enter</title>
          <p>prise
Capabilities &amp; how are
they different?
A
socio-technical approach
that enables
reasoning on
capability formation
is needed
4
5
8
9</p>
          <p>Alternative
Kinds &amp;
Reasoning
Guidelines</p>
        </sec>
        <sec id="sec-4-2-3">
          <title>Identifying Inflexibilities</title>
        </sec>
        <sec id="sec-4-2-4">
          <title>Cause &amp; 6 Effects of NFRs</title>
        </sec>
        <sec id="sec-4-2-5">
          <title>Boundary 7 Reconfiguration</title>
        </sec>
        <sec id="sec-4-2-6">
          <title>Top-Down</title>
          <p>Modeling
Approach
Bottom-Up
Modeling
Approach
Constructs
Methods
Constructs
Method</p>
        </sec>
        <sec id="sec-4-2-7">
          <title>Design Theory Method</title>
        </sec>
        <sec id="sec-4-2-8">
          <title>Method</title>
        </sec>
        <sec id="sec-4-2-9">
          <title>Method Method</title>
          <p>Instantiations in DSR are used to demonstrate the usage of an approach and validate
the contribution of the research. In Table 4, the series of instantiations, their purpose,
and publication venues are presented. The final item in the table refers to an ongoing
case study in evaluating the usage of the framework.</p>
        </sec>
        <sec id="sec-4-2-10">
          <title>Used to draft the first version of the framework</title>
        </sec>
        <sec id="sec-4-2-11">
          <title>Used in practice to guide the delivery of IS artifacts</title>
        </sec>
        <sec id="sec-4-2-12">
          <title>Used as the case study for Causal modeling of NFRs</title>
        </sec>
        <sec id="sec-4-2-13">
          <title>Used as a publicly available reference capability model to demonstrate capability alternatives</title>
        </sec>
        <sec id="sec-4-2-14">
          <title>Understand the concept of capability and its relationships in a second case study Instantiate &amp; validate the meta-model</title>
        </sec>
        <sec id="sec-4-2-15">
          <title>Used to describe the future state (visionary) capabilities</title>
        </sec>
        <sec id="sec-4-2-16">
          <title>Explicate collaboration requirements &amp; responsibilities with the intention to onboard all stakeholders Serve as a roadmap to define &amp; prescribe solutions</title>
        </sec>
        <sec id="sec-4-2-17">
          <title>Serve as a roadmap to define &amp; prescribe KPIs</title>
        </sec>
        <sec id="sec-4-2-18">
          <title>Used to develop bottom-up guidelines and methodology</title>
        </sec>
        <sec id="sec-4-2-19">
          <title>Model a vendor proposal to evaluate</title>
          <p>o</p>
          <p>satisfaction of persona requirements
o identification of tool and platform bias
o identify and propose alternatives for shortcomings</p>
        </sec>
        <sec id="sec-4-2-20">
          <title>Used to develop top-down guidelines and methodology TBD</title>
          <p>d
e
h
s
i
l
b
u</p>
          <p>
            P
[
            <xref ref-type="bibr" rid="ref24">24</xref>
            ]
[
            <xref ref-type="bibr" rid="ref25">25</xref>
            ]
[
            <xref ref-type="bibr" rid="ref26">26</xref>
            ]
No
No
          </p>
          <p>In the remainder of this section a brief overview of the components of the framework
is presented.
4.1</p>
        </sec>
      </sec>
      <sec id="sec-4-3">
        <title>Conceptual Foundation</title>
        <p>The integrated meta-model for the modeling framework is based on different
conceptual viewpoints coordinated through the notion of enterprise capabilities as outlined
in Fig. 4. The views enable describing what forms a capability, how it relates to other
enterprise concepts and how one can determine the value of the capability in the
ecosystem. Enterprise capabilities (EC) are defined as intentional combination of
firmspecific assets, organizational routines (business processes), and human knowledge
(skillset/know-how) that take advantage of complementary relations and are created
and evolved overtime through social collaboration and learning.
Examples of enterprise capabilities we have investigated as part of our instantiations
are “Enterprise IT Risk Management”, “Customer Interaction Management”, “Business
Process Management”, “Social Media Analytics”, and “Integrated Information
Provisioning”.</p>
        <p>The proposed meta-model represents the confluence of the results from two domains
of strategic management and information systems engineering. It serves as the keystone
of a socio-technical approach for developing information systems and has been
validated in more than three case studies. Because of such validations, the meta-model has
been extended particularly in the social view as presented later in Fig. 9.
4.2</p>
      </sec>
      <sec id="sec-4-4">
        <title>Maturity Stages &amp; Their Requirements</title>
        <p>Building on the variety of research efforts on using capabilities, a capability modeling
practice is proposed consisting of six maturity stages as presented in Fig. 5. The initial
stage is to use capabilities as blueprints for communicating investment priorities. At
stages two and three the focus is on enabling representation of capability formation and
its alternative evolution paths. At stages four and five, the capability concept is used to
reorganize the enterprise and enable design for flexibility, while exploring different
configurations of roles and responsibilities. At stage six in response to demands of
ecosystems, the capability concept is used to enable re-design and re-alignment of the
enterprise and its service propositions.</p>
        <p>For each of the stages, a set of questions are identified that will guide a) researchers
in developing methods and techniques for reasoning and decision making, and b)
practitioners in selecting appropriate methods and performing required analysis for
capability design.</p>
        <p>This component consists of three parts a) justification of applying an agent-oriented
modeling paradigm, b) guidelines to model and reason on different aspects of capability
formation, and c) the formal specification that enables instantiating the meta-model
using the i* framework. Without these key components, the analysis techniques that help
decision makers and designers will not be applicable.</p>
      </sec>
      <sec id="sec-4-5">
        <title>Adopting an Agent Oriented Modeling Paradigm.</title>
        <p>
          There are five characteristics evident in the definition of EC as reviewed in section 4.1.
(1) ECs are intentionally built and evolved in accordance with enterprise strategy while
striving for survival and relevance at enterprise scale [
          <xref ref-type="bibr" rid="ref14 ref27">14, 27</xref>
          ]. (2) ECs achieve their
objectives by intelligently coupling enterprise-specific resources and processes [
          <xref ref-type="bibr" rid="ref14 ref27">2, 14,
27</xref>
          ]. (3) ECs often create value in complementary settings forming a network of
interdependent capabilities [
          <xref ref-type="bibr" rid="ref15 ref27">15, 27</xref>
          ]. (4) ECs are built in the social setting of the enterprise
i.e., they are influenced by the social capital, reputation, and relationships of the
responsible managers and teams [
          <xref ref-type="bibr" rid="ref28">2, 28</xref>
          ]. (5) ECs are continuously evolving through
metalevel learning processes that codify and extend enterprise knowledge base [
          <xref ref-type="bibr" rid="ref16">2, 16</xref>
          ].
        </p>
        <p>An agent-oriented modeling approach is adopted to model and represent enterprise
capabilities and its characteristics. To this end, in this research ECs are represented as
specialized i* actors. The ability of the i* framework to represent goals, means-ends,
quality attributes, contributions, and tradeoffs are beneficial in capturing the
intentionality and internal structure of capabilities. The i* dependencies and actor associations
empower understanding of the social and complementary aspects of ECs. An example
of a capability represented with the i* language is presented in Fig. 6. This figure
illustrates how goals, resource, business processes, capabilities, and their relationships
are instantiated using i*.</p>
        <p>Fig. 7 demonstrates the social context in which a capability is built in. The figure
focuses on instantiating the relationships among social actors and capabilities while
capturing different desires and norms of teams within the organization.</p>
      </sec>
      <sec id="sec-4-6">
        <title>Modeling &amp; Reasoning on Formation of Enterprise Capabilities</title>
        <p>This part of the component focuses on guidelines for modeling and reasoning on the
formation of capabilities that will empower understanding of (1) why a capability is
needed, (2) how it is achieved, (3) how it fits within the organizational and social setting
of the enterprise, and (4) what relationships are required for its success. Addressing
these requirements satisfy the second maturity stage presented in Fig. 5.</p>
        <p>The guidelines enable a) explication of choices for coupling enterprise-specific
resources and processes that differentiate emerging quality attributes, b) expression of the
social and organizational setting to empower analyzing the influences and interests of
multiple stakeholders, and c) representation of interdependent networks of capabilities
to enable orchestration of design choices among capabilities, information systems and
organizational structure(s). In Fig. 8, an example of complementary relationships
among capabilities and their impact on alternative are presented.</p>
      </sec>
      <sec id="sec-4-7">
        <title>Formal Description of Framework</title>
        <p>The third part of this component focuses on a formal description of the extended i*
language. A set of guidelines accompany the meta-model presented in Fig. 9 to enable
instantiating ECs. The details of the guidelines to perform the instantiation are left for
future publications.
4.4</p>
      </sec>
      <sec id="sec-4-8">
        <title>Analysis Techniques</title>
        <p>
          Supporting analysis techniques are required to understand consequences of decisions
about ECs. An in-depth review of each of the analysis techniques is beyond the scope
of this paper, but a brief overview of each one is discussed:
1. Base i* Qualitative Evaluations: Uses i*to analyze and infer the degree of which
intentions are satisfied within and beyond the boundary of an actor.
2. Reasoning on Alternatives [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ]: The analysis technique focuses on demonstrating
different kinds of choices about ECs. The first class of choices are Development
alternatives that focus on (a) options for acquiring/building resources and processes,
and (b) alternative couplings of resources and processes. The second class of choices
refer to options for Deployment Configuration of capabilities both from a technical
and organizational perspective. Finally, the third class of choices refer to
Orchestration alternatives which entail a) coordination among development and deployment
alternatives, b) coordination of choices available for interdependent capabilities, and
c) tradeoffs in employing information systems.
3. Boundary Reconfiguration [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ]: The analysis supports answering what-if questions
about the division of roles and responsibilities among i* actors. The analysis
approach is supported by a series of guiding questions. The intention is to identify
potential reconfigurations in actor boundaries leading to better satisfaction of
intentions, particularly softgoals.
4. Identifying Inflexibilities [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ]: The proposal focuses on identifying critical
relationships among capabilities, information systems, and organizational actors by
analyzing their propagation effects.
5. Causal Relations among NFRs: The analysis technique consists of a set of
guidelines that build on the dependency propagations to identify causal relations among
quality goals. The causalities are modeled using the Causal Loop Diagrams (CLD)
[
          <xref ref-type="bibr" rid="ref30">30</xref>
          ] and enable asking what-if questions regarding short-term and long-term impacts
of alternatives.
5
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Outstanding Research Activities and Future Work</title>
      <p>Ongoing activities to finalize the proposed framework are outlined as follows:
• Organizing findings from case studies into playbooks that serve as “Top-Down
Guidelines &amp; Methods” and “Bottom-Up Guidelines &amp; Methods” to facilitate the
modeling activity.
• Finalizing an ongoing case study which demonstrates the ability of the framework
to appropriately navigate from high-level capabilities and drill down into the
analysis as necessary.
• Applying minor changes and updates received from feedbacks of the DSR design
cycle for the causal modeling technique.</p>
      <p>The following components are planned for future iterations of the framework beyond
this thesis as outlined in dark color and white text in Fig. 10. The two new components
on the right intend to enable integration of other researchers’ analysis techniques and
design patterns into the proposed modeling framework with tool support. The three
analysis techniques at the top focus on the external relationships of ECs and how one
should evaluate their value. The two components in the lower part of the figure focus
on conceptual and practical aspects of modeling enterprise structure. The added
component on the left focuses on decisions on bundling service propositions into platforms.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgements</title>
      <sec id="sec-6-1">
        <title>This thesis is supervised by professor Eric Yu.</title>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>Appendix A</title>
    </sec>
    <sec id="sec-8">
      <title>Appendix B</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <source>(eds.) The Practice of Enterprise Modeling</source>
          . pp.
          <fpage>117</fpage>
          -
          <lpage>131</lpage>
          . Springer Berlin Heidelberg (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Leonard-Barton</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Core capabilities and core rigidities: A paradox in managing new product development</article-title>
          .
          <source>Strategic Management Journal</source>
          .
          <volume>13</volume>
          ,
          <fpage>111</fpage>
          -
          <lpage>125</lpage>
          (
          <year>1992</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Combs</surname>
            ,
            <given-names>J.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ketchen</surname>
            , Jr,
            <given-names>D.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ireland</surname>
            ,
            <given-names>R.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Webb</surname>
            ,
            <given-names>J.W.</given-names>
          </string-name>
          :
          <article-title>The Role of Resource Flexibility in Leveraging Strategic Resources</article-title>
          .
          <source>Journal of Management Studies</source>
          .
          <volume>48</volume>
          ,
          <fpage>1098</fpage>
          -
          <lpage>1125</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Nevo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wade</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The Formation and Value of IT-Enabled Resources: Antecedents and Consequences</article-title>
          .
          <source>Management Information Systems Quarterly</source>
          .
          <volume>34</volume>
          ,
          <fpage>163</fpage>
          -
          <lpage>183</lpage>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Dreyfus</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Iyer</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Managing architectural emergence: A conceptual model and simulation</article-title>
          .
          <source>Decision Support Systems</source>
          .
          <volume>46</volume>
          ,
          <fpage>115</fpage>
          -
          <lpage>127</lpage>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Frank</surname>
          </string-name>
          , U.:
          <article-title>Multi-perspective enterprise modeling: foundational concepts, prospects and future research challenges</article-title>
          .
          <source>Software &amp; Systems Modeling</source>
          .
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Kort</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gordijn</surname>
          </string-name>
          , J.:
          <article-title>Modeling Strategic Partnerships Using the E3value Ontology: A Field Study in the Banking Industry. Handbook of ontologies for business interaction</article-title>
          . (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Lamsweerde</surname>
            ,
            <given-names>A. van:</given-names>
          </string-name>
          <article-title>Goal-oriented requirements engineering: a guided tour</article-title>
          .
          <source>In: Proceedings Fifth IEEE International Symposium on Requirements Engineering</source>
          . pp.
          <fpage>249</fpage>
          -
          <lpage>262</lpage>
          (
          <year>2001</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Agent orientation as a modelling paradigm</article-title>
          .
          <source>Wirtschaftsinformatik</source>
          .
          <volume>43</volume>
          ,
          <fpage>123</fpage>
          -
          <lpage>132</lpage>
          (
          <year>2001</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Allweyer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>BPMN 2.0</article-title>
          .
          <string-name>
            <surname>BoD</surname>
          </string-name>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Azevedo</surname>
            ,
            <given-names>C.L.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Iacob</surname>
          </string-name>
          , M.-E.,
          <string-name>
            <surname>Almeida</surname>
            ,
            <given-names>J.P.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sinderen</surname>
            , M. van, Pires,
            <given-names>L.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guizzardi</surname>
          </string-name>
          , G.:
          <article-title>Modeling resources and capabilities in enterprise architecture: A well-founded ontology-based proposal for ArchiMate</article-title>
          .
          <source>Information Systems</source>
          .
          <volume>54</volume>
          ,
          <fpage>235</fpage>
          -
          <lpage>262</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Ulrich</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosen</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The Business Capability Map: The" Rosetta Stone"</article-title>
          of Business/IT Alignment, (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Furukawa</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Minami</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A Study on the '</article-title>
          <source>Flexibility' of Information Systems (Part</source>
          <volume>1</volume>
          ): Why Do They Need to Be Flexible?
          <source>International Journal of Business and Management</source>
          .
          <volume>8</volume>
          ,
          <issue>p48</issue>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Helfat</surname>
            ,
            <given-names>C.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peteraf</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>The dynamic resource-based view: capability lifecycles</article-title>
          .
          <source>Strategic Management Journal</source>
          .
          <volume>24</volume>
          ,
          <fpage>997</fpage>
          -
          <lpage>1010</lpage>
          (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Teece</surname>
            ,
            <given-names>D.J.:</given-names>
          </string-name>
          <article-title>Explicating dynamic capabilities: the nature and microfoundations of (sustainable) enterprise performance</article-title>
          .
          <source>Strategic Management Journal</source>
          .
          <volume>28</volume>
          ,
          <fpage>1319</fpage>
          -
          <lpage>1350</lpage>
          (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Zollo</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Winter</surname>
            ,
            <given-names>S.G.</given-names>
          </string-name>
          :
          <article-title>Deliberate Learning and the Evolution of Dynamic Capabilities</article-title>
          . Organization Science.
          <volume>13</volume>
          ,
          <fpage>339</fpage>
          -
          <lpage>351</lpage>
          (
          <year>2002</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Jacobides</surname>
            ,
            <given-names>M.G.</given-names>
          </string-name>
          :
          <article-title>The architecture and design of organizational capabilities</article-title>
          .
          <source>Industrial and Corporate Change</source>
          .
          <volume>15</volume>
          ,
          <fpage>151</fpage>
          -
          <lpage>171</lpage>
          (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Davies</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Green</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Indulska</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gallo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>How do practitioners use conceptual modeling in practice? Data &amp; Knowledge Engineering</article-title>
          .
          <volume>58</volume>
          ,
          <fpage>358</fpage>
          -
          <lpage>380</lpage>
          (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. S. Robinson,
          <string-name>
            <given-names>G.</given-names>
            <surname>Arbez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. G.</given-names>
            <surname>Birta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Tolk</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <article-title>Wagner: Conceptual modeling: Definition, purpose and benefits</article-title>
          .
          <source>In: 2015 Winter Simulation Conference (WSC)</source>
          . pp.
          <fpage>2812</fpage>
          -
          <lpage>2826</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Daneva</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Damian</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marchetto</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pastor</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Empirical research methodologies and studies in Requirements Engineering: How far did we come?</article-title>
          <source>Journal of Systems and Software</source>
          .
          <volume>95</volume>
          ,
          <issue>1</issue>
          -
          <fpage>9</fpage>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Dalpiaz</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giorgini</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mylopoulos</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Adaptive socio-technical systems: a requirementsbased approach</article-title>
          .
          <source>Requirements Engineering</source>
          .
          <volume>18</volume>
          ,
          <fpage>1</fpage>
          -
          <lpage>24</lpage>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Chung</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cooper</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Developing adaptable software architectures using design patterns: an NFR approach</article-title>
          .
          <source>Computer Standards &amp; Interfaces</source>
          .
          <volume>25</volume>
          ,
          <fpage>253</fpage>
          -
          <lpage>260</lpage>
          (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Gregor</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A.R.</given-names>
          </string-name>
          :
          <article-title>Positioning and Presenting Design Science Research for Maximum Impact</article-title>
          .
          <source>MIS Quarterly</source>
          .
          <volume>37</volume>
          ,
          <fpage>337</fpage>
          -
          <lpage>355</lpage>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Danesh</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Analyzing IT Flexibility to Enable Dynamic Capabilities</article-title>
          . In: Persson,
          <string-name>
            <given-names>A.</given-names>
            and
            <surname>Stirna</surname>
          </string-name>
          ,
          <string-name>
            <surname>J</surname>
          </string-name>
          . (eds.)
          <source>Advanced Information Systems Engineering Workshops</source>
          . pp.
          <fpage>53</fpage>
          -
          <lpage>65</lpage>
          . Springer International Publishing (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Danesh</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Modeling Enterprise Capabilities with i*: Reasoning on Alternatives</article-title>
          . In: Iliadis,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Papazoglou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            , and
            <surname>Pohl</surname>
          </string-name>
          , K. (eds.)
          <source>Advanced Information Systems Engineering Workshops</source>
          . pp.
          <fpage>112</fpage>
          -
          <lpage>123</lpage>
          . Springer International Publishing (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Danesh</surname>
            ,
            <given-names>M.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Loucopoulos</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Dynamic Capabilities for Sustainable Enterprise IT - A Modeling Framework</article-title>
          . In: Johannesson,
          <string-name>
            <surname>P</surname>
          </string-name>
          . (ed.) Conceptual Modeling. pp.
          <fpage>1</fpage>
          -
          <lpage>9</lpage>
          . Springer International Publishing (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>McKelvie</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Davidsson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>From Resource Base to Dynamic Capabilities: an Investigation of New Firms</article-title>
          .
          <source>British Journal of Management</source>
          .
          <volume>20</volume>
          ,
          <fpage>S63</fpage>
          -
          <lpage>S80</lpage>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Adner</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Helfat</surname>
            ,
            <given-names>C.E.</given-names>
          </string-name>
          :
          <article-title>Corporate effects and dynamic managerial capabilities</article-title>
          .
          <source>Strategic Management Journal</source>
          .
          <volume>24</volume>
          ,
          <fpage>1011</fpage>
          -
          <lpage>1025</lpage>
          (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Mahlouji</surname>
          </string-name>
          , N.:
          <article-title>A Method for Modeling and Analyzing different Approaches to Agile BI</article-title>
          , (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Meadows</surname>
            ,
            <given-names>D.H.</given-names>
          </string-name>
          :
          <article-title>Thinking in systems: A primer</article-title>
          .
          <source>Chelsea Green Publishing</source>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>