<!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>Aligning Data Warehouse Requirements with Business Goals</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Alejandro Mate</string-name>
          <email>amate@dlsi.ua.es</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Juan Trujillo</string-name>
          <email>jtrujillo@dlsi.ua.es</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Eric Yu</string-name>
          <email>eric@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>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Lucentia Research Group Department of Software and Computing Systems University of Alicante</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2013</year>
      </pub-date>
      <volume>978</volume>
      <fpage>67</fpage>
      <lpage>72</lpage>
      <abstract>
        <p>According to the Gartner Group, over 70% of Business Intelligence (BI) projects fail. Among the reasons are the di erent languages employed by IT and business people and the necessity of a long-term BI plan describing the goals of the organization. In current practice, when building the data warehouse (DW), strategic plans are rarely considered. In this paper, we propose a method to align the business plan with DW requirements analysis. By aligning the DW, we (i) validate the correctness of each decision makers' goals, (ii) ensure that their decisions and the DW contribute towards organization goals, and (iii) provide a longterm uni ed BI strategy. We instantiate this alignment by combining i* for DWs with strategic business models.</p>
      </abstract>
      <kwd-group>
        <kwd>Business Intelligence</kwd>
        <kwd>business plan</kwd>
        <kwd>data warehouses</kwd>
        <kwd>alignment</kwd>
        <kwd>BIM</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Data Warehouses (DW) integrate numerous heterogeneous data sources in
multidimensional structures in support of the decision-making process. In order to
be successful, recent DW development approaches, such as [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], include a
requirement analysis step based on goal models. During this step, the requirements of
individual decision makers, who are the users of the Business Intelligence (BI)
system, are gathered by means of questionnaires and interviews.
      </p>
      <p>The main drawback of the techniques used during the requirements step is
that they obtain only a partial view of the problem from each decision maker.
Moreover, these partial views may not always be aligned with the business plan,
which, together with the gap between IT and business people, makes it di cult
to validate the goal models. In turn, the lack of alignment between individual
decision makers and the business plan is translated into a lack of long term
enterprise BI strategy, which is one of the key factors to successfully apply BI.
This problem arises whenever business goals are not considered during the
requirements analysis step. For example, a ctitious car dealer company EURent
pursues the goal of \Be positioned within the top 10 car dealers". EURent Sales
Manager is considering how to improve the \Car Sales" process by \Increasing
the margin of bene t per sale". While this particular goal improves the results
of the sales process, it does not contribute to the increasing number of cars sold.</p>
      <p>In this paper, we propose to tackle this problem by aligning the business
strategy with current BI and DW goal models. Therefore, we ensure that our
BI-enabled decision making is consistent with the business strategy. First, we
elaborate a strategic goal model from the business plan to formalize business
goals and trace business indicators. Then, we align and relate decision makers'
goals with business goals. Therefore, we ensure that all the decision makers are
contributing towards the overall goals of the enterprise, and identify business
goals that are being overlooked by decision makers.</p>
      <p>The remainder of this paper is structured as follows: Section 2 presents the
related work in DW requirements. Section 3 describes the alignment process and
the main contributions of our work. Section 4 presents the conclusions. Section
5 describes the ongoing and future work in this area.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        Until now, most of the attention in DW requirements analysis has been focused
on requirements elicitation. Current techniques [2, 5{7] are focused on
gathering requirements by means of interviews and questionnaires. However, although
it has been stated that DW requirements can rarely be gathered correctly and
comprehensively from individual decision makers [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], only in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] do the authors
consider organizational modeling in the requirements step. Unfortunately, the
focus of organizational modeling in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] is to identify the information stored in
business processes, rather than obtaining business goals. Therefore, these
approaches do not ensure that decisions being taken are aiming to provide a bene t
for the organization according to the business plan, nor they do ensure that all
the organization's goals have been considered in the decision making process.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Scienti c Contributions &amp; Tool</title>
      <p>
        In this section we present the main contributions of our work, as well as the
current tool support for our approach. Our contributions are described in the
following order: (i) a method to perform the alignment between DW requirements
and business goals, (ii) a set of mappings to instantiate the alignment method,
by using i* for DWs [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] for modeling decision makers' goals, and the Business
Intelligence Model (BIM) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] for modeling the business strategy, and (iii) show
how these mappings and models can be implemented in a tool.
      </p>
      <p>First, the alignment method is shown in Figure 1. The alignment process
starts by modeling decision makers' goals by means of techniques used in
current DW approaches. As a result, an i* for DWs model is created for each decision
maker. In parallel, or after DW requirements have been obtained, the business
strategy model is created by using the information from the business plan.
Business plans include information regarding business goals, the objectives associated
with each goal, and may also include information regarding business processes.
Once both models have been obtained, we proceed to the alignment step. First,
we align the concepts used to model decision makers' goals with those used to
model business goals, in order to ensure that we correctly relate individual goals
with business goals. Then, in collaboration with a domain expert, we align each
concrete decision maker goal to a speci c business goal. Finally, we analyze the
alignment and perform changes as necessary.</p>
      <p>Since currently there is no standard for modeling decision makers' goals nor
business strategies, they can be instantiated according to di erent frameworks,
thus leading to di erent results. Therefore, in order to instantiate the method,
it is necessary to perform an ontological mapping between the concepts of the
speci c frameworks being used. In our case, we make use of i* for DWs in order to
model decision makers' goals, and BIM for modeling the business strategy. Thus,
we analyze the de nitions and characteristics of each concept included in these
metamodels and align them to ensure their correct use. Due to space constraints,
we provide only a brief overview of the metamodels, and focus speci cally on
aligned elements.</p>
      <p>
        First, i* for DWs [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] is an extension of i* that includes several types of actor
goals to describe the decision making process rationale: Strategic Goals, Decision
Goals, and Information Goals. Strategic Goals are goals with the highest level of
abstraction, such as \Attract new customers", while Decision and Information
Goals are included to describe the steps required in the decision process to
achieve the Strategic Goals. We formally describe a Strategic Goal as follows: A
strategic goal Si describes a change from a current situation into a better one, as
seen by one decision maker DMj . The change described by Si must be related
to an objective Ok of one Business Process BPm, e.g. \Sales". Therefore, it is
said that Si improves BPm. If Si is achieved, it causes an immediate bene t Bp
for the organization, that may or may not be measurable. Finally, i* for DWs
also includes lower level abstraction elements that realize Information Goals
and de ne the structure of the DW: Contexts and Measures. Contexts describe
concepts involved in BPm, such as \Customers", while Measures are quantitative
values v that evaluate the performance of BPm, such as \Quantity Sold".
      </p>
      <p>
        Second, in order to create the business strategy model, we use BIM [
        <xref ref-type="bibr" rid="ref1 ref4">1, 4</xref>
        ].
BIM includes four core concepts that allow us to formalize the elements within
the business plan: Intentions (business goals), Situations, Indicators, and
Processes (see [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]). An Intention de nes a desired situation for the enterprise, as
de ned by one or more persons of authority A = fAi; :::; Ang in the business
plan, where A usually is a subset of the decision makers. Intentions can be
classi ed as Strategic (long term), Management (medium term), and Operational
(short term), and are realized by one or more Processes, BPi; :::; BP n. An
example of a Strategic Intention of the organization EURent is \To be a Premium
Brand car rental company". Next, Situations describe internal or external
factors, such as \Economic Crisis", that may a ect Intentions or Processes, while
Indicators measure the performance of a Process or Intention. Indicators include
a target value t to be achieved, a threshold th that separates average from bad
performance, and a worst value w that describes the worst performance. Finally,
Processes represent Business Processes, such as \Sales" or \Rentals".
      </p>
      <p>According to the descriptions provided in the i* for DWs and BIM proposals,
Decision and Information Goals, and Contexts from i* for DWs cannot be aligned
with any element in BIM. The main reason is that BIM focuses on representing
the business strategy and does not consider elements speci c to the individual
decision making process, such information requirements or actors.</p>
      <p>Next, Business Processes and Measures from i* for DWs can be easily aligned
with BIM elements. First, Business Processes refer to the same concept as
Processes. Second, Measures provide a value vi that measures the performance of
a business process. These values are one of the basic elements used to calculate
Indicators that monitor elements in the business strategy. A Measure can be
related or transformed into an Indicator Ij if (i) vi is used in the calculus of Ij
and (ii) the rest of the values tj , thj , and wj are de ned.</p>
      <p>Finally, Strategic Goals can be aligned with Intentions as follows:
according to our formalization, achieving a particular decision maker strategic goal
Strategic Goal Strategic Intention</p>
      <p>Future, Focused,</p>
      <p>Long-term</p>
      <p>Qualitative,</p>
      <p>Measured by KPI
Future, Time-Targeted,</p>
      <p>Long or Short-term,
Measures Goal and</p>
      <p>Process performance
Si improves a process BPm. Thus, this improvement helps the organization to
achieve a business intention Ij , realized by BPm. There are, however, two
limitations to automate this alignment. First, Si may improve a speci c objective
Ok that does not have an impact on Ij . For example, improving the \Car Sales"
process by \Increasing the margin of bene t" does not have an impact on \Be
positioned within the top 10 Car Dealers". Second, in practice, not every
business plan or strategy provides references to the business processes that realize
each intention. Thus, it is necessary to collaborate with a domain expert in order
to identify if the particular goals are aligned with the business intentions or not.</p>
      <p>The alignment is summarized in in Table 1, along with the informal
descriptions provided by the frameworks for each element.</p>
      <p>After aligning the concepts, the last step is aligning the elements within
the goal models obtained from decision makers with the business strategy, thus
obtaining a combined model that covers both individual as well as organizational
views. We have successfully tested our approach in an experimental case study,
creating a business strategy from a business plan and interviewing experts in
information analysis to obtain decision makers' goals. However, due to space
constraints, the case study will be described in a future extended version.</p>
      <p>
        Our approach is supported by our tool, the Lucentia BI suite, which allows
us to model (i) user requirements by means of i* for DWs, (ii) business strategies
by means of a particular implementation of BIM, and (iii) a trace metamodel,
described in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], that allows us to materialize the alignment between user
requirements and the business strategy. The tool is based on Eclipse and includes
a set of modules, each designed to support an speci c task. An screenshot of the
tool can be seen in Figure 2.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Conclusions</title>
      <p>In this paper we have presented an alignment between the business strategy,
modeled using BIM, and DW requirements, represented by i* for DWs. Our
process results in an alignment that allows us to (i) validate DW requirements
according to the business strategy and identify non-aligned goals, (ii) provide a
long-term BI strategy to be pursued, including what information is being used by
the organization to support each goal, (iii) identify the di erent decision makers
participating in a business goal, thus providing awareness, and (iv) evaluate if
decision makers are being successful by analyzing the values of indicators related
to business goals.</p>
      <p>While extending i* to consider all the elements within the business strategy
would overcomplicate the model, our initial applications have shown that it can
be combined with other models in order to capture both the particular viewpoint
of each decision maker as well as the overall strategy of the organization.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Ongoing and Future work</title>
      <p>The current ongoing work is focused on making it easier for businesses to apply
our proposal. In order to achieve this, we plan to semi-automate the process of
obtaining an strategic model directly from the business plan. Therefore, we are
analyzing the viability of de ning a series of pattern-based transformations in
order to save time and costs.</p>
      <p>In the medium-term we plan to apply our approach to a real case study
and evaluate the results. Since then structure of business plans may vary from
one organization to another, we plan to minimize the impact of this
variability by using the standard Business Motivation Model, proposed by the Object
Management Group group.</p>
      <p>Acknowledgments This work has been supported by the MESOLAP
(TIN201014860) and GEODAS-BI (TIN2012-37493-C03-03) projects from the Spanish
Ministry of Education and the Spanish Ministry of Economy and Competitivity.
Alejandro Mate is funded by the Generalitat Valenciana (ACIF/2010/298).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>D.</given-names>
            <surname>Barone</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Won</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Jiang</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          .
          <article-title>Enterprise modeling for business intelligence</article-title>
          .
          <source>The Practice of Enterprise Modeling</source>
          , pages
          <volume>31</volume>
          {
          <fpage>45</fpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Rizzi</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Garzetti. GRAnD</surname>
          </string-name>
          :
          <article-title>A goal-oriented approach to requirement analysis in data warehouses</article-title>
          .
          <source>Decision Support Systems</source>
          ,
          <volume>45</volume>
          (
          <issue>1</issue>
          ):4{
          <fpage>21</fpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>A.</given-names>
            <surname>Mate</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Trujillo</surname>
          </string-name>
          .
          <article-title>A trace metamodel proposal based on the model driven architecture framework for the traceability of user requirements in data warehouses</article-title>
          .
          <source>Information Systems</source>
          ,
          <volume>37</volume>
          (
          <issue>8</issue>
          ):
          <volume>753</volume>
          {
          <fpage>766</fpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>A.</given-names>
            <surname>Mate</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Trujillo</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          .
          <article-title>Conceptualizing and specifying key performance indicators in business strategy models</article-title>
          .
          <source>ER'12</source>
          , pages
          <fpage>282</fpage>
          {
          <fpage>291</fpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>J.N.</given-names>
            <surname>Mazon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Pardillo</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Trujillo</surname>
          </string-name>
          .
          <article-title>A model-driven goal-oriented requirement engineering approach for data warehouses</article-title>
          .
          <source>Advances in Conceptual Modeling{ Foundations and Applications</source>
          , pages
          <volume>255</volume>
          {
          <fpage>264</fpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>N.</given-names>
            <surname>Prakash</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Gosain</surname>
          </string-name>
          .
          <article-title>Requirements driven data warehouse development</article-title>
          .
          <source>In CAiSE Short Paper Proceedings</source>
          , pages
          <volume>13</volume>
          {
          <fpage>17</fpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>R.</given-names>
            <surname>Winter</surname>
          </string-name>
          and
          <string-name>
            <given-names>B.</given-names>
            <surname>Strauch</surname>
          </string-name>
          .
          <article-title>A method for demand-driven information requirements analysis in data warehousing projects</article-title>
          .
          <source>In System Sciences</source>
          ,
          <year>2003</year>
          .
          <source>Proceedings of the 36th Annual Hawaii International Conference on, pages 9{</source>
          pp.
          <source>IEEE</source>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>