<!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>
      <journal-title-group>
        <journal-title>Hammamet, Tunisia, pp.</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Using Goals to Model Strategy Map for Business IT Alignment</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Abdul Babar</string-name>
          <email>Abdul.Babar@uts.edu.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Didar Zowghi</string-name>
          <email>Didar.Zowghi@uts.edu.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Eng Chew</string-name>
          <email>Eng.chew@uts.edu.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Engineering and Information Technology, University of Technology Sydney</institution>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2010</year>
      </pub-date>
      <volume>1</volume>
      <fpage>6</fpage>
      <lpage>30</lpage>
      <abstract>
        <p>Strategy Map (SM) is one of the widely used methods to create business aligned IT strategy map providing valuable insights to business executives. However, problem with strategy map method is that it is not easy to use which can lend itself to various interpretations. This is because linkages between the strategic objectives in the four strategy map perspectives are not explicit which makes SM ambiguous. Goal modelling approaches from Requirements Engineering (RE) have proven rigorous in elicitation and representation of information system requirements. In an attempt to make explicit the causal relationships of SM linkages meaningful this research proposes the use of goal modelling approach i*.</p>
      </abstract>
      <kwd-group>
        <kwd>Business IT alignment</kwd>
        <kwd>strategy map</kwd>
        <kwd>goal modelling</kwd>
        <kwd>i*</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Business aligned IT strategy has been the top ranking concern of business executives
in the last two decades [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Due to strategic misalignment, firms often fail to accrue
the full business value from their IT investment [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. To address the alignment issue,
researchers and practitioners from Management Information Systems (MIS) have
proposed many types of methods for business executives providing insights about
different aspects of strategic alignment. Some methods focus on social aspect of
strategic alignment [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] in which the resulting causal model of resources (such as
knowledge sharing, trust and successful IT history as pre-requisite to communication
between business and IT executives and connection between business and IT
planning) to achieve alignment are presented. Others highlight the importance of
informal organisational structure for strategic alignment [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Several other models
describe alignment as planning process [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. There are also methods that identify
holistic view of alignment process such as Strategic Alignment Model (SAM) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and
strategy map (SM) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] in which several aspects of alignment process and relationships
among them are identified.
      </p>
      <p>
        Strategy map which evolved from balanced scorecard has been regarded as the
most widely used alignment method and more than 300 organisations have used to
create maps for their business aligned IT strategies [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Strategy map defines four
perspective map (Financial, Customer, Internal and Learning &amp; Growth (L&amp;G)) of an
organisation’s value creating strategy. It provides textual concepts that executives can
use to discuss the directions and priorities of their enterprise. Strategy map identifies
the cause-and-effect relationships among the objectives in the four perspectives of an
organisation’s strategy in which the desired outcomes are defined in terms of
objectives in financial and customer perspectives. Internal perspective identifies the
critical internal processes that an organisation must excel in so as to deliver the
strategic outcomes. L&amp;G perspective identifies the human and organisational capitals
along with technology assets necessary to support the value-creating internal
processes. Visual representation of the causal relationships in the four perspectives
provides greater insight to executives as to how the firm’s tangible and intangible
resources must be aligned to create value for the customers and the firm.
      </p>
      <p>
        However, researchers found that the SM method is not easy to use and the created
strategy map lends itself to various interpretations [
        <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
        ]. The major reason for these
problems is that the linkages created among objectives in four perspectives are not
explicit as shown in Figure 1. The lack of an explicit model of relationships
contributes to the difficulties in evaluating the relative importance of performance
objectives in SM [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. According to [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] an adequate causal model should help
members of organisations to understand how objectives can be achieved. However, a
recent study reported that the vagueness of SM guidelines results in three different
types of interpretations of the SM created by a firm [
        <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
        ]. The problem of implicit
model of relationships exists in most of business IT alignment models.
      </p>
      <p>
        Goal modelling approaches from RE have been considered rigorous and structured
in elicitation and representation of requirements [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Many goal modelling
approaches have been proposed and compared in terms of their requirements
modelling capabilities [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Among them, i* appeared semantically richer and that it
provides greater requirements analysis support than other modelling approaches [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
Therefore, we consider exploiting the constructs of i* approach to overcome the
above-mentioned weaknesses and make strategy map more structured.
      </p>
      <p>Thus, we set a research question to address the problem of strategy map:
How can we use i* to make strategy map more structured and unambiguous for
business executives?</p>
      <p>
        In this regard we use Consumer Bank exemplar (a case study conducted by [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and
its created strategy map is shown in Figure 1). Application of i* to the textual
description of Consumer Bank enables us to create an i* model of SM which we call
SMi* model. Using the knowledge of Consumer Bank exemplar to develop SMi*
model is advantageous in a way that we can effectively compare SMi* model with
conventional strategy map in terms of explicitness in linkages. The rest of the paper is
structured as follows. Section 2 compares and contrasts strategy map constructs with
i* constructs in a tabular form. Development process of SMi* model has been
presented in section 3. Section 4 presents lessons learned from the development
process of SMi* model. Conclusion and future work direction are presented in section
5.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2 Suitability Analysis of i* Constructs for Strategy Map</title>
      <p>
        Before we develop SMi* model we need to evaluate whether the constructs offered by
i* are suitable and adequate to conceptualise and represent SM constructs. In this
regard, we carefully analyse textual description of the exemplar and SM method used
to create strategy map from [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and identify constructs needed to be represented.
Similarly, we also evaluate i* constructs in an attempt to match them against strategy
map constructs. Evaluation of SM and i* constructs is described in Table 1.
      </p>
      <sec id="sec-2-1">
        <title>Modelling requirements (strategy map)</title>
        <p>Perspective refers to a firm’s strategic view in
terms of conceptual elements (e.g. goals and
resources) pertinent to a particular domain of
concern. Strategy map consisting of four
perspectives describes value creating strategy
in terms of objectives which provides basis
for executives to discuss the directions and
priorities of their enterprise.</p>
        <p>Contents of financial perspective present
i*constructs
i* does not offer any suitable construct
to represent the concept of perspective
of SM.
i* offers graphical notation Goal to
how an enterprise intends to create
sustainable growth in shareholder value.
Primarily in the financial perspective Firm’s
financial targets are established which are
precise in nature.</p>
        <sec id="sec-2-1-1">
          <title>Quality Goal</title>
          <p>
            Integrated Goal
offerings
Credibility of Soft goal
service
Help in Soft goal
planning &amp;
implementing
financial plans
Contents of internal perspective comprise of
three value creating core process types
(operations, customer and innovation
management core processes). A firm typically
defines the critical few (clusters of) strategic
processes known as strategic themes that
have the greatest impact on delivering the
espoused CVPs. A core process comprise of
many sub-processes. These sub-processes are
executed to achieve CVPs. A strategic theme
has clear performance targets (aligned with
the CVPs) which must be supported by
learning &amp; growth perspective.
represent objectives/targets which are
precise in nature. According to a
definition goal is a condition or a state
of affairs to be achieved [
            <xref ref-type="bibr" rid="ref15">15</xref>
            ]. Given
that the objectives in financial
perspective are precise in nature we use
goal construct (as shown below) to
represent financial objectives.
          </p>
          <p>
            CVPs can be classified into
precise/hard and qualitative/soft
objectives. Goal construct is suitable to
represent precise CVPs however we use
soft goal construct to represent
qualitative targets. Soft goal means it
does not have clear-cut satisfaction
criteria [
            <xref ref-type="bibr" rid="ref15">15</xref>
            ]. Soft goal is used to
represent qualitative target in terms of
satisfied sufficiently. Thus, goal and
soft goal constructs conceptually
qualify to represent quantitative and
qualitative types of requirements
potentially across SM four perspectives.
i* need to represent three types of
elements here for internal perspective –
(1) three clusters of core processes, (2)
core processes which are known as
strategic themes and (3) sub-processes
executed to achieve strategic themes. i*
does not offers any suitable construct to
represent three clusters of strategic
themes. Strategic themes have been
described in terms of precise value.
          </p>
          <p>
            Therefore goal construct qualifies to
represent strategic themes. To represent
sub-processes we use Task construct.
According to a definition task is a
course of action that is carried out in a
particular way typically to achieve
Contents of learning &amp; growth perspective
comprise of three capitals: (1) human capital,
(2) Information Capital (IC) and (3)
organisational capital (known as intangible
assets) each defined with precise objectives
and performance targets to support the
strategic themes. Human capital refers to
specialist roles required to execute activities
in internal perspective, organisational capital
refers to interaction among stakeholders and
IC refers to value creating computer
technologies necessary to support activities in
the strategic theme of internal perspective.
Technology infrastructure used to support
activities has been regarded as asset/resource
in the MIS literature [
            <xref ref-type="bibr" rid="ref16">16</xref>
            ]. Therefore, we need
to represent technology as asset/resource,
people as stakeholders for all four
perspectives and organisational issues as
relationships among the stakeholders.
some goal. For simplicity this concept
Of task can be used as an
approximation to equate the concept of
sub-process
Actor is an entity that carries out
actions to achieve goal by exercising its
know-how. In addition an actor can be
classified into specialised roles as
shown below. The concept of actor is
suitable and adequate to represent
human capital potentially across all four
perspectives.
          </p>
          <p>
            Fundamentally i* is an approach that is
used to express complex social and
organisational relationships through
dependency relationships among actor
[
            <xref ref-type="bibr" rid="ref15">15</xref>
            ]. i*’s inherent structure supports
representation of human and
organisational aspects. Thus for
simplicity, in this study we present the
human and organisational resources in
conjunction with related concepts in the
appropriate perspectives where they
make sense. This means the L&amp;G
perspective only needs to represent IT
resources which support the
subprocesses of the strategic themes.
          </p>
          <p>
            According to [
            <xref ref-type="bibr" rid="ref15">15</xref>
            ] Resource is a
provision of some entity either physical
or informational to achieve some goals
or to perform some tasks. This concept
of resource is equivalent to the concept
of IT resource which is used to execute
sub-processes of strategic themes.
Classification of objectives. The exemplar
describes objectives for all four perspectives.
However these objectives are of different
types of. For example Consumer Bank
describes shareholder value as
mission/aspiration and to achieve the mission
the bank establishes many productivity and
growth targets. In this case the firm’s
strategic aspiration is its strategic intent and
productivity and growth targets are objectives
defined to achieve the strategic intent. So, we
classify targets provided for all four
perspectives into intents and objectives
categories.
          </p>
          <p>
            Cause-and-effect relationships are
established among four perspectives by
showing that IT supports internal processes
which supports customer perspective and
which supports financial perspective (for
example, see Figure 1). Establishing
relationships among perspectives mean to
facilitate discussion among executives in
terms of linkages between objectives.
Relationship strengths, objectives in each
perspective which drive to achieve strategic
intent have various types of relationships and
these relationships have various degrees of
strengths. For example, the exemplar at many
stages in [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ] shows that the two
subobjectives/sub-processes support to achieve
an objective that means
sub-objectives/subprocesses have AND relationships, at some
stage the exemplar describes one
subobjective is sufficient to achieve an objective
then the relationship should be shown with
Means-Ends link. At another stage one
objective supports another objective but the
relationship strength in unknown for which
In i* intentionality is described in terms
of desires and wants of an actor from
another actor in Strategic Dependency
(SD) model [
            <xref ref-type="bibr" rid="ref15">15</xref>
            ]. To deliver a strategic
intent an actor establishes some targets
which are defined in Strategic Rationale
(SR) model of i*.
          </p>
          <p>To make distinction between the variety
of objectives and their strategic intents
i* uses the concept of a boundary as
shown below. This construct defines
boundary of objectives in terms of
goals, tasks and resources. i* describes
it as workability analysis which fits
well to represent that how
wellintegrated objectives support achieving
strategic intents which are represented
out side the boundary. Responsible
actor to achieve strategic intent through
targets inside the boundary appears an
equivalent concept to SM concept on
strategic intent and associated
objectives.</p>
          <p>Strategic Dependency (SD) relationship
concept allows representing
cause-andeffect relationships of SM through actor
dependency relationship as the
construct is shown below. With SR
model SM will be able to represent
explicit relationships among objectives
as well as actors and dependency
relationships among them for strategic
intents for all four perspectives.</p>
        </sec>
        <sec id="sec-2-1-2">
          <title>The use of following relationship constructs can bring clarity to the relationships among the objectives of SM four perspectives.</title>
          <p>AND/OR construct is used to indicate
that satisfying a goal can be
accomplished by satisfying all its
subgoals.</p>
        </sec>
        <sec id="sec-2-1-3">
          <title>Means -Ends is used to show if a sole goal is contributor to another goal. + construct represents that one goal positively influences the other goal. It is</title>
          <p>we use Plus contribution link.
used where strength is not sure.</p>
          <p>DECOMPOSITION construct
represents decomposition of a task into
more than one sub-tasks.
2.1 Extension to i*</p>
          <p>
            i* approach appears to be suitable representing most of the SM constructs
however, it lacks representing the concept of four different types of perspectives and
three types of clusters of core processes for internal perspective. Therefore we
propose new constructs presented in Table 2. We do not present theoretical
background of these new constructs in this article due to the space constraint however
in selecting appropriate visual constructs we take insights from [
            <xref ref-type="bibr" rid="ref17">17</xref>
            ].
          </p>
          <p>
            Visual constructs are more effective in understanding and solving problems than their
contents [
            <xref ref-type="bibr" rid="ref17">17</xref>
            ]. Visual representation in software engineering is pervasive but little
attention is paid to perceptual aspect when a visual construct is selected. Two
important principles should be addressed in selecting visual constructs: (1) symbols
could be discriminated accurately from each other. Symbols are different from each
other. The greater the visual distance between symbols the faster and more accurately
they will be recognised and (2) appearance of constructs should suggest their
meanings which means that the symbols are required to provide clues to their
meanings. Such representation provides accurate and speed up recognition of
constructs.
          </p>
        </sec>
        <sec id="sec-2-1-4">
          <title>We use three colours to represent three</title>
          <p>clusters of core processes. Red colour to
represent operations, green colour to
represent customer and yellow colour to
represent innovation clusters.</p>
          <p>$$
Suitability analysis of i* constructs (Table 1) and extension to i* constructs (Table 2)
for representing SM constructs led us to believe that we can faithfully capture all the
“structural constructs” of SM in a fully integrated SMi* model which unambiguously
shows the inter-relationships of “structural constructs”.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3 Development Steps</title>
      <p>In the development of SMi* model we use two-step approach of i*. First we develop
Strategic Dependency (SD) model in the context of Consumer Bank exemplar. SD
model helps us to capture dependency relationships among stakeholders for strategic
intents in the four perspectives of SM. Strategic intents can be captured in the form of
goals to be achieved, tasks to be performed and resources to be furnished. Second
based on detailed level of knowledge provided in the exemplar we identify rationale
behind those strategic intents in the form of goals, tasks and resources that each
stakeholder facilitate to achieve strategic intents. This is called Strategic Rationale
(SR) model which basically expands on SD model by showing internal arrangement
of an actor to achieve strategic intents. So, we term it as SMi* model comprises of SD
and SR models.</p>
      <sec id="sec-3-1">
        <title>3.1 Strategic Rationale (SR) Model</title>
        <p>This section presents detailed information about Consumer Bank exemplar for four
SM perspectives and how this information is used to develop SMi* model. We ensure
that the development of SMi* model is entirely based on the knowledge provided in
the exemplar.</p>
        <p>Financial perspective, Exemplar describes that the overarching shareholder
objective for Consumer Bank was to dramatically increase earning per share. This
statement presents two stakeholders1 – shareholder and Consumer Bank and one
strategic objective – increase earning per share. By using i* approach we can
conceptualise stakeholders and the objective by saying that shareholder depends on
Consumer Bank which we consider from now on as Financial Service Provider (FSP)
to increase earning per share. We use i* construct actor to represent these
stakeholders and the goal to represent the quantitative strategic objective of earning
per share be increased. Exemplar also describes that the target be achievable for
increase in earning per share which we consider a qualitative aspect of the target of
earning per share be increased. So, we use soft goal construct to represent target be
achievable for shareholder. The following information provided in the exemplar is
used as rationale to achieve shareholder objective.</p>
        <p>FSP sets a stretched target of net income - $100 million on which the strategic intent
depends. Net income is a precise objective and is represented by using goal construct
as shown in Figure 2. This stretched target can help to calculate earning per share for
shareholders precisely that’s why we represented strategic intent with goal construct.</p>
        <sec id="sec-3-1-1">
          <title>1 stakeholder: human, departments, organizations</title>
          <p>
            FSP sets two sub-objectives – increase productivity and profitable revenue growth.
FSP considers them as two high level and main objectives to achieve $100 million net
income target (p.374) [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ]. Therefore, we use AND decomposition link to show that the
achievement of productivity and growth objectives means achievement of the
stretched target of $100 million. We use goal construct to represent productivity be
increased and growth be achieved as both objectives can be measured quantitatively
based on the targets which are discussed in the next paragraph. In addition, FSP
expects 11% annual revenue growth which also refers to a clear-cut growth objective.
          </p>
          <p>According to the textual description of the exemplar FSP defines two growth
related sub-objectives – increase revenue per customer from $200 to $300 and
increase the number of high value customers from 200,000 to 600,000. These are two
quantitative sub-objectives to achieve a precise growth objective. Once again we use
goal construct to represent these objectives and AND decomposition link to show that
the achievement of both sub-objectives means achievement of growth objective.</p>
          <p>
            FSP defines one productivity related sub-objective reduce annual customer cost
from $100 to $75 [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ]. This is another clear-cut financial objective and we use goal
construct to represent the objective. This objective can help to measure productivity
objective therefore we use goal construct to represent the productivity objective.
Since cost per customer be reduced is a sole objective to increase productivity we use
means-ends link to show that it is strong enough to achieve the productivity objective.
In this way we capture rationale behind the financial strategic intents as shown in
Figure 2 which is entirely based on textual description of the Consumer Bank
exemplar.
          </p>
          <p>
            Customer perspective, FSP pursues relationship based customer strategy instead of
old transaction based customers strategy (p.377) [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ]. In relationship context, FSP
wants four strategic intents to be achieved in order to realise financial objectives:
(1) Products/services be provided, FSP defines precise target in terms of
products and service so we represent it with goal construct.
(2) Relationships with customers be developed is a qualitative objective which is
not measureable so, we represent it as a soft goal.
(3) One stop shopping is a precise goal in which FSP provides all the financial
related needs to its customer.
(4) Trusted financial advice is related to the provision of information which is
represented with resource construct.
          </p>
          <p>To deliver these strategic intents, FSP hires a financial advisor2 who is specialist in
this domain. So, FSP depends on financial advisor for these four strategic intents.
Rationale behind these four strategic intents is described below.</p>
          <p>With respect to the rationale, exemplar describes that strategic intent – trusted
financial advice depends on the goal of helping customers develop and implement
financial plans. Trusted financial advice is a resource and it is based on product
knowledge which we represent with resource construct, however, helping customers
2 We acknowledge that there can be other customer interfaces such as customer service agents,
bank tellers however Consumer Bank created new strategic role to shift customers from
transaction based to relationship based customers. Therefore we used financial advisor as
responsible role to deliver four strategic intents for customer perspective.</p>
          <p>Shareholder
Target be
achievable</p>
          <p>Earning per
share be
increased
Productivity be
increased
Cost per
customer be
reduced</p>
          <p>Increase in net
income be set
Revenue per
customer be
increased</p>
          <p>Growth be
achieved
High-value customers
be added and retained
Relationships with
cust. be developed</p>
          <p>One stop
shopping</p>
          <p>Trusted
financial
advice
Integrated
offerings
Fig 2. SMi* model of Consumer Bank</p>
          <p>Cross-sel
product line
Joint
Venture
mnger</p>
          <p>Develop new
products
Seek
partner</p>
          <p>s
Telemark
eter
Project
mgmt
system
Customer
profitability
system</p>
          <p>Webarchitecture</p>
          <p>Telemarketing
campaign
Calculate
new product
revenue</p>
          <p>CRM</p>
          <p>Shift to
appropriate
channel</p>
          <p>Consumer
marketer
Costeffective
approach
Acquire
prospect list
Manage lead
&amp; order</p>
          <p>Customer
feedback
system</p>
          <p>Understand
customer
segments
Clarify
CVP
Direct mail
support
program
Calculate
customer
profit</p>
          <p>Serve
customers
Segment
market</p>
          <p>Communicate
Customer
survey
to develop and implement their financial plans is a qualitative goal as it can not be
clearly measured. In addition, One stop shopping which means to provide all financial
solutions under one roof depends on helping customer in developing their products.</p>
          <p>Strategic intent relationship based customer supports financial target revenue per
customer be increased, according to the exemplar it depends on integrated offering.
Integrated offering is a quantitative goal as financial advisor can easily figure out how
many products/services a customer has been using.</p>
          <p>Strategic intent – products and services that helps to achieve cost per customer be
reduced depends on CVP Services be credible and effective. Textual description
presents price and quality of products and services as key CVPs to support
products/services to be credible and effective and hence helps to reduce cost per
customer for productivity objective, so we use positive contribution link showing that
the CVPs price and quality positively support the soft goal of products/services to be
credible and effective as shown in Figure 2.</p>
          <p>As price (value for money) is a known value it is represented with goal construct.
Firms use Service Level Agreement (SLA) to achieve quantitative goals in term of
quality of their services, so quality level can be identified precisely and is represented
with goal construct3. So, we can show through linkages that how strategic intents
depend on CVPs to support financial targets. One of the advantages of using i* is that
it helps to differentiate strategic intents from supporting objectives.</p>
          <p>Internal perspective, Exemplar describes six critical processes in three clusters –
operation, customer and innovation that must be executed to achieve four strategic
intents of customer perspective. Six core processes – minimize problems, provide
rapid response, cross-sell product line, develop new products, shift to appropriate
channels and understand customer segment are described as six themes. Exemplar
identifies six specialist roles to achieve targets set for six strategic themes. Therefore
by using i*, we capture dependency relationships between financial advisor and six
specialist roles for six strategic themes (along with some soft targets perceived from
the textual description) as shown in Figure 2. We introduce six strategic themes in the
context of three clusters below:</p>
          <p>The exemplar describes two operation management related themes which are
important to satisfy existing customers and delivering desired productivity objective.</p>
          <p>(1) Minimize problems is a strategic theme in which quality manager is given the
target of 0.1% reduction in incidents and cost of errors to achieve low price CVP.
Reducing the number of incidents and the cost of errors is the task that quality
manager performs to achieve 0.1% target and achieve it effectively. In i* terms
financial advisor depends on quality manager to achieve this strategic theme and to
achieve the strategic theme quality manager performs the task of reducing the number
of incidents and cost of errors.</p>
          <p>(2) Provide rapid response, means 24/7 service with fulfilment time. The exemplar
describes call centre representatives as responsible people to achieve this service
objective and task for them is to fulfil request. The response must be useful for
3 In some cases quality could include the level of customer experience in using the services
offered by Consumer Bank. In these cases, quality is not measureable entity and will be
represented as a soft goal.
customers. Same i* principle is used here and onward to represent relationship
between financial advisor and roles associated to rest of the four strategic themes.</p>
          <p>The exemplar described four more strategic themes in customer management &amp;
innovation clusters which can help to achieve revenue growth and increase in high
value customers objectives. Based on the textual description we find that two themes
cross-sell the product line and develop new products are more supportive to achieve
relationship based customers and hence increase in revenue per customer. However,
two other core processes – shift to appropriate channel and understand customer
segment are more supportive to achieve increase in high value customers.
(1) Cross-sell the product</p>
          <p>For this strategic theme, financial planner is considered an ideal role who is given
the target of 2.5 products per customer to be achieved. To achieve this target financial
planner is responsible to perform the task of providing broader range of products and
service.</p>
          <p>(2) Develop new products</p>
          <p>In this theme, joint venture manager is given the target of increase in revenue per
customer by 50%. To achieve this target joint venture manager performs the task of
seeking more partners in order to create additional products and services.
(3) Shift to appropriate channel</p>
          <p>This theme requires telemarketing program in which 40% shift in channel mix is
the target for telemarketers. To achieve this target, three types of tasks are suggested
in the exemplar – (1) telemarketing campaign, (2) the acquisition of prospect list and
(3) direct mail support program which are associated with the task through
decomposition link.</p>
          <p>(4) Understand customer segment</p>
          <p>Consumer marketer is the responsible person to achieve the target of 30% segment
share for this theme. To achieve this target responsible person has the major task of
serving customer which is divided into three sub-tasks - clarification of CVP,
segmenting the market and communicating the message with potential customers.
Achievement of the targets for these six themes through value creating tasks means
achievement of overarching net income target of $100 million.</p>
          <p>
            IT (L&amp;G perspective). This perspective focuses on three aspects – human,
organisational and IT. As we have described in Table 1 that i* inherently supports
expressing organisational and human aspects of information systems through
dependency relationships among actors for goals to be achieved, tasks to performed
and resources to be furnished [
            <xref ref-type="bibr" rid="ref18">18</xref>
            ]. Therefore, we do not need to model human and
organisational aspect separately in L&amp;G perspective however, we must represent IT
aspect for L&amp;G perspective.
          </p>
          <p>
            For information capital, exemplar presents that the IT organisation is responsible
of installing and maintaining several of the applications and integrate these
applications to the bank’s overall web infrastructure. Sub-processes supporting six
strategic themes encompass IT domain of L&amp;G perspective. Six specialist roles
depend on the IT organization (actor) for the support of sub-processes associated to
their domains. Exemplar describes eight sub-processes that an IT organisation needs
to support in order to realise six strategic themes. IT organisation as an actor for IC
capital furnish applications and infrastructures which are considered as resources [
            <xref ref-type="bibr" rid="ref16">16</xref>
            ]
IT organisation furnishes these resources to support six strategic themes.
          </p>
          <p>To achieve strategic theme minimize problems IT organisation installs problem
tracking system who’s main purpose is to perform service quality analysis in which it
helps to reduce operational errors. Thus according to i* quality manager responsible
to achieve strategic theme minimize problems depends on IT organisation to perform
the task of service quality analysis for which IT organisation furnish resource –
problem tracking system. Similarly five other roles responsible of strategic themes
depend on IT organisation to furnish resources for particular tasks which are
described below.</p>
          <p>To support the process of provide rapid response, IT organisation install customer
self help system. This system provides efficient and 24/7 services through
websystems. For cross-sell theme IT organisation installs two applications – customer
portfolio self management system and customer profitability system. Former system
helps customers to develop their financial plans and this system is supported by
webarchitecture providing customers 24/7 services. Later system provides facility for
financial planners to calculate profitability of customers. Strategic theme develop new
product requires project management system which helps project manager to product
based revenue.</p>
          <p>Shift to appropriate channel is another vital theme for which a complete suite of
Customer Relation Management system (CRM) including lead management system,
order management system and sales forces automation is used. CRM supports tasks
related to this strategic theme effectively. Customer profitability is partly useful for
the understand customer segments theme. Customer feedback system is also needed
to understand customer needs and it helps to segment customers. Customer feedback
system is supported (to some degree) by web-architecture providing the bank a cost
effective and efficient way of conducting surveys.</p>
          <p>With i*, relationships among objectives across four perspectives are explicit and in
one example (see Figure 2) we have shown traceability for a strategic theme –
minimize problems upwards for CVPs and financial objectives and downward support
from sub-processes and hence IT resources.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4 Lessons Learned from Using i* to Represent Strategy Map</title>
      <p>1. Development of goal structure using AND alternatives. i* has effectively shown
clarity in relationships among different types of objectives for four SM
perspectives. Linkages present relationship types among objectives.
Representation of different types of objectives with different types of i*
constructs such as goals, tasks and resources can also be observed in SMi*
model. It is also observed that the explicit representation of elements and their
relationships has enhanced readability of SM and thus executives should be able
to view SMi* model as an explicit model of relationships.
2. i* has facilitated more than just enhancing clarity in linkages. i* has captured
roles/actors related to each perspective (contrary to conventional SM in which
roles are identified only in L&amp;G perspective for strategic themes) and provided a
network of dependency relationships among actors. Through this dependency
approach i* actually addresses issues related to organisational and human capitals
which are highlighted in L&amp;G perspective for conventional SM. Therefore, only
IT is captured for L&amp;G perspective in SMi* model. SMi* is ideal to
communicate with executives explicitly showing them strategic intent and their
responsible roles and what measures these roles take to achieve their strategic
intents.
3. We do not represent clusters of core processes into groups as shown in
conventional SMs. The major reason is the representation of explicit relationships
making difficult to group the core processes. So, in SMi* model we use three
distinct colours (red for operations, green for customer and yellow for innovation
processes) to represent three groups of core processes. In this way we maintain
clarity in relationships among objectives.
4. Regulatory and social processes is the fourth cluster of core processes, required
for regulatory and environmental sustainability compliance purposes, which is
not being represented in this SMi* model for two reasons: (1) we do not find
sufficient information on this cluster in consumer bank exemplar and (2)
representation of this core process is debatable as the MIS literature mainly
discusses three core processes to achieve customer and financial targets which we
have represented in SMi* model.
5. SMi* model shows the complete linkages explicitly across the four perspectives
of SM. SMi* model, in one example clearly shows that the core process minimize
problems helps to achieve CVP low price and hence achieve productivity target
while having support from problem tracking system from IT organisation.
6. SM identifies aspects of strategic alignment in term of four perspectives. In this
regard new constructs are identified in Table 2. These constructs help to reduce
complexity of alignment process and enhances readability of SM.
7. In i* context, SMi* model is dependency heavy. The basic reason is that the
exemplar provides limited knowledge for four perspectives of SM process and it
is particularly visible for internal perspective. However, we have provided a
model – SMi* model which is further explore-able. Provision of such integrated
model of explicit linkages was our study objective which we have achieved
through this exercise.</p>
    </sec>
    <sec id="sec-5">
      <title>5 Conclusion and Future Work</title>
      <p>Application of i* has introduced structuredness and explicit traceability to SM that
was weak in the conventional SM. i* approach has provided meaningful visual
constructs to represent different types of targets and relationships among them for
four SM perspectives. Integrated network of relationships provides excellent
traceability across four perspectives. It is our conjecture that this kind of
structuredness and traceability can make SM easy to use as we have not yet validated
this in the field the SMi* model produced and the method used to develop it. Given
that the researchers from MIS have identified ambiguity in relationships among SM
objectives is the problem we believe that with the use of i* constructs relationships
among SM objectives now become explicit. Development of SMi* model is the first
step in this line of research. In the next step we intend to conduct interviews with IT
strategists to evaluate whether SMi* model has better structure and traceability than
conventional strategy map. In the final step we will evaluate the method used to
develop SMi* model through a field case study.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Luftman</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <source>Key Issues for IT Executives</source>
          <year>2004</year>
          .
          <source>MIS quarterly Executive</source>
          ,
          <year>2005</year>
          .
          <volume>4</volume>
          (
          <issue>2</issue>
          ): p.
          <fpage>269</fpage>
          -
          <lpage>285</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Tallon</surname>
            ,
            <given-names>P.P.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>L.K.</given-names>
            <surname>Kraemer</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V.</given-names>
            <surname>Gurbaxani</surname>
          </string-name>
          ,
          <source>Executives Perceptions of the Business Value of Information Technology: A Process-Oriented Approach Journal of Management Information Systems</source>
          ,
          <year>2000</year>
          .
          <volume>16</volume>
          (
          <issue>4</issue>
          ): p.
          <fpage>145</fpage>
          -
          <lpage>173</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. Reich,
          <string-name>
            <surname>B. and I. Benbasat</surname>
          </string-name>
          ,
          <article-title>Factors that Influence the Social Dimension of Alignment Bteween Business and Information Technology Objectives</article-title>
          .
          <source>MIS quarterly</source>
          ,
          <year>2000</year>
          .
          <volume>24</volume>
          (
          <issue>1</issue>
          ): p.
          <fpage>81</fpage>
          -
          <lpage>113</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Chan</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <source>Why We Have Not Mastered Alignment. MIS quarterly Executive</source>
          ,
          <year>2002</year>
          .
          <volume>1</volume>
          (
          <issue>2</issue>
          ): p.
          <fpage>97</fpage>
          -
          <lpage>112</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Cassidy</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          Practical Guide to Information Systems Strategic Planning 2nd ed.
          <year>2006</year>
          , FL: Auerbach Publications Taylor &amp; Francis Group.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Henderson</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          and
          <string-name>
            <given-names>N.</given-names>
            <surname>Venkatraman</surname>
          </string-name>
          , Strategic Alignment:
          <article-title>Leveraging Information Technology for Transforming Organisations</article-title>
          .
          <source>IBM Systems Journal</source>
          <year>1993</year>
          .
          <volume>38</volume>
          (
          <issue>2</issue>
          &amp; 3): p.
          <fpage>472</fpage>
          -
          <lpage>484</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Kaplan</surname>
            , R.S. and
            <given-names>D.P.</given-names>
          </string-name>
          <string-name>
            <surname>Norton</surname>
          </string-name>
          ,
          <source>Strategy Maps: Converting Intangible Assets into Tangible Outcomes</source>
          .
          <year>2004</year>
          ed. 2004: Harvard Business School Publishing Corporation.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Rigby</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Management</given-names>
            <surname>Tools</surname>
          </string-name>
          and
          <article-title>Techniques: A Survey California Management review</article-title>
          ,
          <year>2001</year>
          .
          <volume>43</volume>
          (
          <issue>2</issue>
          ): p.
          <fpage>13960</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Braam</surname>
            , G. and
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Nijssen</surname>
          </string-name>
          ,
          <article-title>Performance Effects of Using The Balanced Scorecard: A Note on the Dutch Experience</article-title>
          .
          <source>Long Range Planning</source>
          <year>2004</year>
          .
          <volume>37</volume>
          (
          <issue>4</issue>
          ): p.
          <fpage>335</fpage>
          -
          <lpage>349</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Marr</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <article-title>Business Performance Measurement: An Overview of the Current State of Use in The USA</article-title>
          .
          <source>Measuring Business Excellence</source>
          <year>2005</year>
          .
          <volume>9</volume>
          (
          <issue>3</issue>
          ): p.
          <fpage>56</fpage>
          -
          <lpage>62</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Kunc</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <article-title>Using Systems Thinking to Enhance Strategy Maps</article-title>
          .
          <source>Management Decision</source>
          ,
          <year>2008</year>
          .
          <volume>46</volume>
          (
          <issue>5</issue>
          ): p.
          <fpage>761</fpage>
          -
          <lpage>778</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Kaplan</surname>
            , R.S. and
            <given-names>D.P.</given-names>
          </string-name>
          <string-name>
            <surname>Norton</surname>
          </string-name>
          ,
          <source>The Balanced Scorecard: Translating Strategy into Action</source>
          .
          <year>1996</year>
          , Boston, MA: Harverd Business School Press.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          .
          <article-title>Why Goal-Oriented Requirements Engineering</article-title>
          .
          <source>in Proceedings of 4th International Workshop on Requirements Engineering</source>
          .
          <year>1998</year>
          . Pisa, Italy.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Kavakli</surname>
            , E. and
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Loucopoulos</surname>
          </string-name>
          . Goal Driven Requirements Engineering:
          <article-title>Evaluation of Current Methods</article-title>
          .
          <source>in Proceedings of 8th CAiSE/IFIP</source>
          .
          <year>2003</year>
          . Nicosia, Cyprus.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <source>Modelling Strategic Relationships for Process Engineering</source>
          .
          <year>1995</year>
          , University of Toronto, Computer Science Department: Toronto. p.
          <fpage>124</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Oh</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Pinsonneault</surname>
          </string-name>
          ,
          <article-title>On the Assessment of the Strategic Value of Information Technologies: Conceptual and Analytical Approaches</article-title>
          . MIS quarterly
          <year>2007</year>
          .
          <volume>31</volume>
          (
          <issue>2</issue>
          ): p.
          <fpage>239</fpage>
          -
          <lpage>265</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.Moody,
          <string-name>
            <surname>D.</surname>
          </string-name>
          <article-title>The Physics of Notations: A Scientific Approach to Design Visual Notations for Requirements Engineering</article-title>
          . in 17th International Conference on Requirements Engineering.
          <year>2009</year>
          . Atlanta, Georgia, USA.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <source>Social Modeling and i*</source>
          ,
          <source>in LNCS. 2009</source>
          , Springer Berlin / Heidelberg. p.
          <fpage>99</fpage>
          -
          <lpage>121</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>