<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Towards A High-Level Business Architecture Methodology for Enterprise IT Strategy</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Juan Li</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Wei Xu</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Beijing University of Technology</institution>
          ,
          <addr-line>100 Pingleyuan, Chaoyang District, Beijing, 100124</addr-line>
          ,
          <country country="CN">China</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Shandong Lucion Investment Holdings Group</institution>
          ,
          <addr-line>Building 1, Yulan Plaza, No.8 Longao Bei Road, Jinan, 250102</addr-line>
          ,
          <country country="CN">China</country>
        </aff>
      </contrib-group>
      <fpage>162</fpage>
      <lpage>169</lpage>
      <abstract>
        <p>Due to the rapid development of enterprise digital transformation and the dynamic and changeable nature of enterprise strategy, the traditional enterprise business architecture methodologies are cumbersome for many enterprise IT strategy projects. To solve this problem, this paper proposes a high-level business architecture methodology, which is more suitable for application and promotion in enterprise IT strategy projects. This paper describes the application process of this methodology and illustrates its application results through the practical example.</p>
      </abstract>
      <kwd-group>
        <kwd>1 Digital transformation</kwd>
        <kwd>IT strategy</kwd>
        <kwd>Business architecture</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Enterprise digital transformation has become an inevitable choice of many enterprises. A digital
strategy is a means of embracing new and different technologies in ways that challenge operational and
value assumptions and which integrate them with existing technologies to deliver new products,
services, business models, revenue streams and/or customer/stakeholder experiences [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. In fact, in the
practice of enterprise digitalization, enterprise digital strategy is often the evolution of enterprise IT
strategy. Even in some enterprises, digital strategy and IT strategy are implemented in one. Therefore,
in this paper, our view is that the approach of IT strategy is equally applicable to digital strategy, no
longer entangled in the conceptual difference between the two.
      </p>
      <p>
        In June, 2021, Tencent Research Institute released the digital transformation report of China
stateowned enterprises. Through the research questions of more than 60 enterprises, it was found that the
main challenge of digital transformation in various industries was not the lack of leadership support and
financial support, but the difficulty in integrating digital technology and business scenarios, resulting
in many enterprises not knowing where to start to promote the digital transformation [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Enterprise IT
strategy is the methodology to solve this dilemma, and among them, business architecture plays a key
role as a bridge connecting enterprise strategy and IT strategy [
        <xref ref-type="bibr" rid="ref3 ref4">3,4</xref>
        ].
      </p>
      <p>
        Business architecture is the set of structures and stories that underpin “the business of the business”.
The structures might include higher-level concerns such as business models, organizational structures,
brand architectures, and financial structures [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. According to TOGAF (The Open Group Architecture
Framework), business architecture defines the business strategy, governance, organization, and key
business processes [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        Due to the complexity of traditional business architecture methodologies, the design and delivery of
business architecture are often completed by professional IT consulting companies in enterprise IT
strategy planning projects. In fact, because of the dynamic and changing nature of enterprise strategy
[
        <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
        ], a more operational and flexible business architecture is often needed. Based on the review of
business architecture methodologies, this paper proposes a high-level business architecture
methodology to make it more suitable for enterprise IT strategy practice.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Existing business architecture practices</title>
      <p>In the practice of enterprise IT strategy over the past few decades, there are two typical business
architecture methodologies. One is from IT consulting companies such as IBM and Accenture, and the
other is that some industry organizations provide such methodologies. Below, this paper will illustrate
these two methodologies with examples.</p>
    </sec>
    <sec id="sec-3">
      <title>2.1. Component business architecture</title>
      <p>
        Summarizing many enterprise IT strategy projects and establishing typical component business
models of enterprises in various industries is the quintessence of IT consulting company methodology.
The Component Business Model (CBM) developed by IBM is a typical representative of this type of
methodology [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
    </sec>
    <sec id="sec-4">
      <title>2.2. Industry reference business architecture</title>
      <p>In some industries, industry organizations will take the lead in formulating and publishing reference
business architectures for the industry. For example, the ACORD reference framework published by
the insurance industry international organization ACORD (Association for Cooperative Operations
Research and Development) contains seven industry models closely related to the insurance industry;
the SCOR (Supply the Chain Operations Reference) reference architecture defines the three-level
business architecture of the supply chain industry; the eTOM（enhanced Telecom Operations Map）
released by the TeleManagement Forum has become an industry standard for telecom operators'
operations management.</p>
      <p>
        This paper takes eTOM as an example to illustrate the industry reference business architecture [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
    </sec>
    <sec id="sec-5">
      <title>3. Enterprise high-level business architecture requirements</title>
      <p>The above two typical enterprise business architecture methodologies have been applied in many
enterprise IT strategies. However, because the enterprise strategy itself is often dynamic and changeable,
it is often necessary to adjust and reconstruct the enterprise business architecture in a timely manner,
and the above traditional methodologies are too heavy. Enterprise IT strategy mainly needs to ensure
consistency with the enterprise strategy, rather than going into the details of the enterprise process. In
this regard, the enterprise high-level business architecture is more suitable for providing effective input
to the IT architecture in terms of direction and structure.</p>
      <p>Therefore, the point of this paper is to establish an easy to implement high-level business architecture
methodology, which should meet the following requirements.</p>
      <p>1. Focus on high-level business architecture</p>
      <p>Enterprise IT strategy planning is the top-level design for the overall IT of the enterprise, and takes
the business architecture as an important foundation. In this field, the enterprise business architecture
should be a high-level business architecture that can match the enterprise strategy and help IT strategy
planners build the work foundation of IT strategy planning from an overall view of the enterprise.</p>
      <sec id="sec-5-1">
        <title>2. Componentization is the right choice</title>
        <p>Whether it is the practice of consulting companies or the research of industry organizations, it is
obvious that the componentization approach is the basic tool of business architecture. Starting from the
business capability, through the relationship analysis between them, just like building the architecture
of a computer system, by defining and using business components to build the business architecture
view of an enterprise. This business architecture can become an important tool for IT strategy planners
to communicate and analyze with enterprise management, operation, execution and internal and
external technical teams, making it an important foundation for IT strategy planning.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>4. A high-level business architecture methodology</title>
      <p>The high-level business architecture methodology proposed in this paper is shown in the following
figure.</p>
    </sec>
    <sec id="sec-7">
      <title>4.1. Understanding of the enterprise</title>
      <sec id="sec-7-1">
        <title>The target enterprise should be understood from three aspects.</title>
        <p>1. Enterprise strategy</p>
        <p>From the perspective of business architecture, the most important thing to understand enterprise
strategy is to grasp the business model, development vision and strategic path of the enterprise. This
determines the target business architecture required by the enterprise.</p>
        <p>2. Enterprise organizational structure</p>
        <p>An enterprise's internal business units and department settings are the basis for the definition of
enterprise business components. At the same time, the process of implementing many enterprise
strategies is often a process of organizational structure adjustment. Therefore, the current organizational
structure of the enterprise and the foreseeable adjustment of the organizational structure are the
important basis for the construction of the business architecture.</p>
        <p>3. The current state of enterprise IT</p>
        <p>In the business architecture, it should not only be limited to business and management, but should
also incorporate the current state of enterprise IT into the scope of business architecture work.
Especially for enterprises that rely on IT to carry out business with a high degree, their IT status is often
a concrete manifestation of the actual situation of enterprise management and business. Taking the
current state of enterprise IT into account in the business architecture will help the business architecture
conform to the actual situation of the enterprise.</p>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>4.2. Understanding of the industry</title>
      <p>The enterprise business architecture cannot be separated from the industry of the enterprise. The
industry of the enterprise can be understood from the following three points.</p>
      <p>1. Industry reference information</p>
      <p>Industry reference information from authoritative and professional industry organizations, industry
regulatory agencies, and professional research institutions is the most valuable. Industry reference
business architectures like eTOM are obviously very helpful to the construction of enterprise business
architectures. However, such mature industry reference business architectures are rare. In many
industries, there is often no reference business architecture to obtain. In this case, a structured industry
understanding framework can be established by means of multi-angle information collection and
comprehensive induction.</p>
      <p>2. Industry benchmarking enterprise</p>
      <p>Since the business architecture itself needs to carry the goal of implementing the enterprise strategy,
many companies often build their enterprise strategy based on the benchmarking enterprise in the
industry. Therefore, if the benchmarking enterprises can be determined, the business architecture of the
benchmarking enterprise is often of great reference significance. In most cases, the benchmarking
enterprise is often a listed company, and its annual report, industry research report for it and other
related information often describe its business architecture in a relatively complete manner.
3. Industry IT practices</p>
      <p>Industry IT practices, especially those of benchmarking enterprises, often contribute to the
development of business architecture. Under the current wave of enterprise digital transformation,
technology-driven business architecture transformation and upgrading has become an unavoidable and
important trend. Therefore, in the business architecture, we must also pay attention to the evolution
direction and specific form of business architecture brought about by industry IT practices.</p>
    </sec>
    <sec id="sec-9">
      <title>4.3. Create a high-level business architecture sketch</title>
      <p>It is a very necessary choice for the business architecture of the IT strategy planning project to build
a high-level business architecture sketch as soon as possible and carry out communication and
demonstration.</p>
      <p>If the industry to which the target enterprise belongs has an industry reference business architecture,
it is the best way to build a sketch by directly tailoring it. However, most enterprises often do not have
this industry reference business architecture. Here, this paper proposes the following three-tier
architecture method, which can be used to quickly build sketches.
administration, finance and human resource, and may also include backstage support capabilities such
as operation, risk and compliance in combination with industry characteristics.</p>
    </sec>
    <sec id="sec-10">
      <title>4.4. High-level business architecture communication and demonstration</title>
      <p>Carrying out communication and demonstration work based on the sketch of the enterprise's
highlevel business architecture is an inevitable process to complete the delivery of it. Typically, this can be
done using a two-step method.</p>
      <p>The first is to preach and guide. This needs to explain the logic and supporting basis for the
construction of the sketch to the middle and senior managers of the enterprise, and lay a foundation for
understanding and consensus for communication and argumentation.</p>
      <p>The second is hierarchical communication and demonstration, demonstrating the overall logic of the
high-level business architecture with the CEO and CXO, and communicating with the middle and senior
managers of each business unit and department to demonstrate the definition of each component and
the sorting out of the relationship between them.</p>
    </sec>
    <sec id="sec-11">
      <title>4.5. High-level business architecture finalization</title>
      <p>Through communication and argumentation, after obtaining the support of the middle and senior
management of the enterprise, the finalization of the enterprise's high-level business architecture can be
completed. In the subsequent IT architecture design, this high-level business architecture will serve as
the most important basis, and also provide a foundation for the middle and senior leaders of the
enterprise, who are often not IT professionals, to understand the IT architecture.</p>
    </sec>
    <sec id="sec-12">
      <title>5. Example of the methodology application</title>
    </sec>
    <sec id="sec-13">
      <title>6. Conclusions</title>
      <p>Facing the practice of enterprise IT strategy, this paper proposes a high-level business architecture
methodology. Compared with the existing methodologies, this methodology has three characteristics.
First, it is higher-level, which is easier for CEOs and CXOs to understand; second, it is convenient for
continuous adjustment and improvement from the overall perspective of the enterprise, rather than being
trapped in the specific process of the enterprise, which helps to be consistent with the enterprise strategy;
third, it is more suitable for IT strategy planners to master, and is conducive to promotion and use in
enterprise IT strategy projects.</p>
      <p>Undoubtedly, the application of this methodology requires a systematic understanding of the
industry to which the target enterprise belongs. Therefore, in the future work, the research and setup of
high-level business reference architectures for those industries with high demand for digital
transformation will be more conducive to the practice of this methodology in enterprise IT strategy
projects.</p>
    </sec>
    <sec id="sec-14">
      <title>7. References</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J. D.</given-names>
            <surname>McKeen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <source>IT Strategy: Issues and Practices, Edition</source>
          <volume>3</volume>
          .1,
          <string-name>
            <surname>Prospect</surname>
            <given-names>Press</given-names>
          </string-name>
          , Inc., Burlington,
          <string-name>
            <surname>VT</surname>
          </string-name>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>F.L.</given-names>
            <surname>Niu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.X.</given-names>
            <surname>Chen</surname>
          </string-name>
          , X. Cheng,
          <article-title>The current process, challenges and ideas of digital transformation of state-owned enterprises</article-title>
          ,
          <year>2021</year>
          . URL:https://new.qq.com/omn/20210607/20210607A09OR500.html.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>T.</given-names>
            <surname>Saldanha</surname>
          </string-name>
          ,
          <article-title>Why Digital Transformations Fail - The Surprising Disciplines of How to Take Off and Stay Ahead</article-title>
          , Berrett-Koehler, Oakland, CA,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>J.</given-names>
            <surname>Whelan</surname>
          </string-name>
          , G. Meaden, Business Architecture:
          <string-name>
            <given-names>A Practical</given-names>
            <surname>Guide</surname>
          </string-name>
          , Routledge, New York, NY,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>D.</given-names>
            <surname>Simon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <string-name>
            <surname>Business Architecture</surname>
          </string-name>
          Management - Architecting
          <source>the Business for Consistency and Alignment</source>
          , Springer International Publishing, Switzerland,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6] The Open Group,
          <source>The TOGAF® Standard, Version9.2</source>
          ,
          <year>2018</year>
          . URL:https://www.opengroup.org/togaf.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Parnell</surname>
          </string-name>
          ,
          <source>Strategic Management: Theory and Practice</source>
          , 4th. ed.,
          <source>SAGE Publications</source>
          , Thousand Oaks, CA,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>BCG</given-names>
            <surname>Henderson Institute</surname>
          </string-name>
          , Dynamic Business Strategy:
          <article-title>Competing in a Fast-changing</article-title>
          , Uncertain Context, De Gruyter, Berlin,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>G.</given-names>
            <surname>Pohle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Korsten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ramamurthy</surname>
          </string-name>
          ,
          <string-name>
            <surname>Component Business</surname>
          </string-name>
          Model - Making
          <source>Specialization Real</source>
          ,
          <year>2020</year>
          . URL:www.ibm.com/downloads/cas/8RB5RWVE.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <article-title>TeleManagement Forum, enhanced Telecom Operations Map (eTOM)</article-title>
          , CITIC Press, Beijing,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>