Business architecture

Last updated

Aspects of a business represented by a business architecture diagram Aspects of the Business Represented by Business Architecture.jpg
Aspects of a business represented by a business architecture diagram

In the business sector, business architecture is a discipline[ citation needed ] that "represents holistic, multidimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders." [2] [3]

Contents

In application, business architecture provides a bridge between an enterprise business model and enterprise strategy on one side, and the business functionality of the enterprise on the other side. It often[ quantify ] enables the Strategy to Execution methodology.

People who develop and maintain business architecture are known as business architects.

Overview

The term "business architecture" is often used to mean an architectural description of an enterprise or a business unit, an architectural model, or the profession itself. The Business Architecture Working Group of the Object Management Group (OMG) (2010) describes it as "a blueprint of the enterprise that provides a common understanding of the organization and is used to align strategic objectives and tactical demands." [4] According to the OMG, a blueprint of this type describes "the structure of the enterprise in terms of its governance structure, business processes, and business information." [5] As such, the profession of business architecture primarily focuses on the motivational, operational, and analysis frameworks that link these aspects of the enterprise together. [4]

The key characteristic of the business architecture is that it represents real world aspects of a business, along with how they interact. It is developed by an interdisciplinary practice area focused on defining and analyzing concerns of what business does, how it does it, how it is organized, and how it realizes value. [6] It is used to design competitive structures and processes, leverage existing strengths, and identify potential investment opportunities that advance the business's objectives and drive innovation. [7] Products of this business architecture efforts are used to develop plans, make business decisions and guide their implementations. [6]

In practice, business architecture effort is conducted on its own or as part of an enterprise architecture. [6] While an enterprise architecture practice in the past had focused primarily on the technological aspects of change, the practice is quickly evolving to use a rigorous business architecture approach to address the organizational and motivational aspects of change as well. [7] The alignment between business architecture and enterprise architecture is a natural architectural alignment of two related disciplines. Business architecture represents a business in the absence of any IT architecture while enterprise architecture provides an overarching framework for business and IT architecture. [8]

History of business architecture

The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" [9] closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, [10] [11] as business strategy, [12] and also as the representation of business design. [13]

The concept of business architecture has evolved over the years. It was introduced in the 1980s as architectural domains and as activity of business design. In the 2000s the study and concept development of business architecture accelerated. By the end of the 2000s the first handbooks on business architecture were published, separate frameworks for business architecture were being developed, separate views and models for business architecture were further under construction, the business architect as a profession evolved, and an increasing number of businesses added business architecture to their agenda.

By 2015 business architecture has evolved into a common practice. The business architecture body of knowledge has been developed and is updated multiple times each year, and the interest from the academic world and from top management is growing.[ citation needed ]

Business architecture topics

Different views of an organization

In order to develop an integrated view of an enterprise, many different views of an organization are typically developed. Each "view" is typically a diagram that illustrates a way of understanding the enterprise by highlighting specific information about it. The key views of the enterprise that may be provided by business architecture address several aspects of the enterprise; they are summarized by the Object Management Group (2012) [5] as follows:

  • The Business Strategy view captures the tactical and strategic goals that drive an organization forward...
  • The Business Capabilities view describes the primary business functions of an enterprise and the pieces of the organization that perform those functions...
  • The Value Stream view defines the end-to-end set of activities that deliver value to external and internal stakeholders...
  • The Business Knowledge view establishes the shared semantics (e.g., customer, order, and supplier) within an organization and relationships between those semantics (e.g., customer name, order date, supplier name)...
  • The Organizational view captures the relationships among roles, capabilities and business units, the decomposition of those business units into subunits, and the internal or external management of those units. [5]

In addition to the above views of the enterprise, the relationships that connect the aforementioned views form the foundation of the business architecture implementation. This foundation provides the framework that supports the achievement of key goals; planning and execution of various business scenarios; and delivery of bottom-line business value. [5]

Business strategy

In the 2006 article "Business Architecture: A new paradigm to relate business strategy to ICT," Versteeg & Bouwman explained the relation between business strategy and business architecture. They wrote:

Business Architecture is directly based on business strategy. It is the foundation for subsequent architectures (strategy embedding), where it is detailed into various aspects and disciplines. The business strategy can consist of elements like strategy statements, organizational goals and objectives, generic and/or applied business models, etc. The strategic statements are analyzed and arranged hierarchically, through techniques like qualitative hierarchical cluster analysis. Based on this hierarchy the initial business architecture is further developed, using general organizational structuring methods and business administration theory, like theories on assets and resources and theories on structuring economic activity. [14]

Versteeg & Bouwman further stipulated, that "the perspectives for subsequent design next to organization are more common: information architecture, technical architecture, process architecture. The various parts (functions, concepts and processes) of the business architecture act as a compulsory starting point for the different subsequent architectures. It pre-structures other architectures. Business architecture models shed light on the scantly elaborated relationships between business strategy and business design." [14]

Approaches for business architecture

The Business Architecture Guild

The primary purpose of the Business Architecture Guild [15] is "to promote best practices and expand the knowledge-base of the business architecture discipline." The Guild is a non-profit, international membership organization for practitioners and others interested in the developing the field of business architecture. With members on six continents, a strong Advisory Board and a growing number of business partners, the Guild positions itself as a focal point for the evolving practices and disciplines of business architecture.

Founded in late 2010, the Guild opened up membership in the fall of 2011 based on the initial release of A Guide to the Business Architecture Body of Knowledge(R) (BIZBOK(R) Guide). BIZBOK(R), currently at version 13, is a "practical guide for business architecture practitioners and individuals who wish to use business architecture to address business challenges. This practical guide comes in the form of best practices, gleaned from numerous companies and business architecture leaders.". [16]

The Business Architecture Association

The Business Architecture Association started as a DePaul based organization where practitioners came together to share and explore new ideas around Business Architecture. It later formalized itself into a formal organization that looked to build local chapters where practitioners could gather and share their ideas around Business Architecture. In addition, to building a chapter based organization, the Business Architecture Association coalesced a group of strong practitioners to put together the first practitioner exam. Eventually, the Business Architecture Association formalized the exam and it became the beta version of certified practitioner exam. In 2014, the Business Architecture Guild and the Business Architecture Association, joined forces where the beta exam became cornerstone of the certification program of the Business Architecture Guild looking to solidify the practice of Business Architecture in the marketplace.

The ASATE Group Business Capability Framework

The ASATE Group Business Capability Framework relies on business capabilities and the eight types of building blocks that make them up (processes, functions, organizational units, know-how assets, information assets, technology assets, brands and natural resource deposits) to model a business architecture. This framework was devised with five criteria in mind: (1) must be aligned with the ANSI/IEEE 1471-2000 standard definition of architecture; (2) must share an anchor point with business strategy, namely capabilities; (3) must rely on common business terms and definitions thereof; (4) must comprise all building block types necessary to model a complete business architecture; and (5) must not be burdened with unnecessary building blocks types. [17]

Enterprise architecture frameworks encompassing business architecture approaches

Zachman Framework

The Zachman Framework is a popular enterprise architecture framework used by business architects. The framework provides ontology of fundamental enterprise concepts that are defined from the intersection of six interrogative categories: What, How, Where, Who, When, Why, and six perspectives: Executive, Business Management, Architect, Engineer, Technician, and Enterprise. Typically, business architects are interested in the concepts associated with the top two perspectives: Executive and Business Management. The Executive perspective is concerned with the scope and context of the business. The Business Management perspective is concerned with business definition models. [18]

The Object Management Group

Modeling standards of the Object Management Group (OMG), including the Unified Modeling Language (UML), Model Driven Architecture (MDA), Business Motivation Model (BMM), Semantics of Business Vocabulary and Rules (SBVR) and the Business Process Modeling Notation (BPMN), and the Decision Model and Notation (DMN) enable powerful visual design, execution and maintenance of software and other processes, including IT Systems Modeling and Business Process Management. Currently, OMG works on the Value Delivery Modeling Language (VDML), a standard modeling language for analysis and design of the operation of an enterprise with particular focus on the creation and exchange of value [19]

The Open Group

The Open Group Architecture Framework (TOGAF) of The Open Group is a community-based standards effort for describing methods and tools used by architecture. It is being developed and continuously improved by the Open Group, a consortium of interested individuals and companies involved in information technology.

According to TOGAF, Business Architecture "defines the business strategy, governance, organization, and key business processes". [20] TOGAF refers to Business Architecture as one of the four architecture domains, which represent the subsets of the overall enterprise architecture with the other three architecture domains being Application Architecture, Data Architecture, and Technology Architecture. The key element of TOGAF, Architecture Development Method, identifies development of Business Architecture as necessary prerequisite for developing other architecture domains and provides guidance in regard to development steps and common artifacts. [20]

Industry reference models

Industry reference models are frameworks or models that provide a best practice off-the-shelf set of structures, processes, activities, knowledge and skills. The Business Architecture Guild provides reference models for many industries, including government, financial services, insurance, transportation, and healthcare, as well as a common reference model. [21] Other organizations are also beginning to develop complementary models for additional industries.

Other industry models

Many additional business models exist that can be related to business architecture, but are derived from other approaches, such as operating models and lower-level process frameworks. Examples of these include:

See also

Related Research Articles

Model-driven architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model Driven Architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.

<span class="mw-page-title-main">Business process modeling</span> Activity of representing processes of an enterprise

Business process modeling (BPM), mainly used in business process management; software development, or systems engineering, is the action of capturing and representing processes of an enterprise, so that the current business processes may be analyzed, applied securely and consistently, improved, and automated. BPM is typically orchestrated by business analysts, leveraging their expertise in modeling practices. Subject matter experts, equipped with specialized knowledge of the processes being modeled, often collaborate within these teams. Alternatively, process models can be directly derived from digital traces within IT systems, such as event logs, utilizing process mining tools.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

<span class="mw-page-title-main">The Open Group Architecture Framework</span> Reference model for enterprise architecture

The Open Group Architecture Framework (TOGAF) is the most used framework for enterprise architecture as of 2020 that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. TOGAF is a high-level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products.

A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.

Technology strategy is the overall plan which consists of objectives, principles and tactics relating to use of technologies within a particular organization. Such strategies primarily focus on the technologies themselves and in some cases the people who directly manage those technologies. The strategy can be implied from the organization's behaviors towards technology decisions, and may be written down in a document. The strategy includes the formal vision that guides the acquisition, allocation, and management of IT resources so it can help fulfill the organizational objectives.

<span class="mw-page-title-main">Enterprise architecture framework</span> Frame in which the architecture of a company is defined

An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models – typically matrices and diagrams – for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

<span class="mw-page-title-main">Enterprise modelling</span>

Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.

<span class="mw-page-title-main">TAFIM</span>

Technical Architecture Framework for Information Management (TAFIM) was a 1990s reference model for enterprise architecture by and for the United States Department of Defense (DoD).

Enterprise interoperability is the ability of an enterprise—a company or other large organization—to functionally link activities, such as product design, supply chains, manufacturing, in an efficient and competitive way.

Enterprise data planning is the starting point for enterprise wide change. It states the destination and describes how you will get there. It defines benefits, costs and potential risks. It provides measures to be used along the way to judge progress and adjust the journey according to changing circumstances.

Capability management is the approach to the management of an organization, typically a business organization or firm, based on the "theory of the firm" as a collection of capabilities that may be exercised to earn revenues in the marketplace and compete with other firms in the industry. Capability management seeks to manage the stock of capabilities within the firm to ensure its position in the industry and its ongoing profitability and survival.

Jaap Schekkerman is a Dutch computer scientist and founder of the Institute For Enterprise Architecture Developments (IFEAD) in the Netherlands. He is particularly known for his 2003 book How to Survive in the Jungle of Enterprise Architecture in which he compared 14 Enterprise Architecture Frameworks.

The Banking Industry Architecture Network e.V. (BIAN) is an independent, member owned, not-for-profit association to establish and promote a common architectural framework for enabling banking interoperability. It was established in 2008.

<span class="mw-page-title-main">William M. Ulrich</span> American business architecture consultant

William M. Ulrich is an American business architecture consultant, consultant at Cutter Consortium, director and lecturer, known for development of 'The Systems Redevelopment Methodology' (TSRM) in the 1990s, on legacy systems in the 2000s and more recently on his work on business architecture.

Gerrit Versteeg is a Dutch enterprise architect and management consultant, known for his work in defining the field of business architecture.

The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, as a business strategy, and also as the representation of a business design.

The Business Architecture Special Interest Group (BASIG) is a working group on business architecture of the Object Management Group (OMG), known for their contribution to the history of business architecture. This working group was founded in 2007 as the Business Architecture Working Group (BAWG).

A data architect is a practitioner of data architecture, a data management discipline concerned with designing, creating, deploying and managing an organization's data architecture. Data architects define how the data will be stored, consumed, integrated and managed by different data entities and IT systems, as well as any applications using or processing that data in some way. It is closely allied with business architecture and is considered to be one of the four domains of enterprise architecture.

References

  1. ↑ Business Architecture Guild, A Guide to the Business Architecture Body of Knowledge™, v 7.5 (BIZBOK® Guide), 2019. Part 1, Section N/A & Page 2
  2. ↑ "FEAPO Announces New Enterprise Architecture Genre Definitions". FEAPO. June 7, 2017. Archived from the original on April 19, 2019. Retrieved April 19, 2019. For the first time, a large consortium of professional organizations collaborated to publish Architecture genre definitions.
  3. ↑ "The Federation of Enterprise Architecture Domains". FEAPO. Retrieved April 19, 2019. Business Architecture represents holistic, multidimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.
  4. 1 2 OMG Business Architecture Special Interest Group "What Is Business Architecture?" at bawg.omg.org, 2008 (archive.org). Accessed 04-03-2015; Cited in: William M. Ulrich, Philip Newcomb Information Systems Transformation: Architecture-Driven Modernization Case Studies. (2010), p. 4.
  5. 1 2 3 4 OMG Business Architecture Working Group, "Business architecture overview Archived February 3, 2009, at the Wayback Machine ," at bawg.omg.org. Accessed December 18, 2014,
  6. 1 2 3 Business Architecture Guild, Business Architecture and BPM - Differentiation and Reconciliation - Whitepaper
  7. 1 2 FEAPO, "A Common Perspective on Enterprise Architecture Archived January 2, 2015, at the Wayback Machine " in: Architecture and Governance Magazine, 2013(11): 1–2.
  8. ↑ Business Architecture Guild, A Guide to the Business Architecture Body of Knowledge™, v 4.1 (BIZBOK® Guide), 2014. Part 6, Section 6.2 & Page 374
  9. ↑ Paul Arthur Bodine and Jack Hilty. "Business Architecture: An Emerging Profession," at businessarchitectsassociation.org, Business Architects Association Institute. April 28, 2009. (online Archived November 7, 2010, at the Wayback Machine )
  10. ↑ Michael K. Bourke (1994). Strategy and architecture of health care information systems. p. 55
  11. ↑ OMG Business Architecture Working Group. "Business Architecture Working Group," at bawg.omg.org, Oct 10, 2008. (archive.org, Oct. 10, 2008).
  12. ↑ Peter T. Davis (1996) Securing Client/server Computer Networks. p. 324
  13. ↑ SOA Consortium, EA2010 working group. Business Architecture; The Missing Link between Business Strategy and Enterprise Architecture Archived January 30, 2012, at the Wayback Machine . Copyright by OMG, 2010.
  14. 1 2 Versteeg, G & H. Bouwman. "Business Architecture: A new paradigm to relate business strategy to ICT." Information Systems Frontiers 8 (2006) pp. 91-102.
  15. ↑ Business Architecture Guild
  16. ↑ Business Architecture Guild, A Guide to the Business Architecture Body of Knowledge™, v 7.5 (BIZBOK® Guide), March 2019. Part 1, Section 1 & Page 1
  17. ↑ Pierre Hadaya and Benard Gagnon (2017). Business Architecture - The Missing Link in Strategy Formulation, Implementation and Execution. ASATE Publishing. ISBN   978-0994931900.
  18. ↑ Business Architecture Guild, A Guide to the Business Architecture Body of Knowledge™, v 4.1 (BIZBOK® Guide), 2014. Part 6, Section 6.2 & Page 384
  19. ↑ Object Management Group, VDML Specification
  20. 1 2 The Open Group, TOGAF 9.1 specification
  21. ↑ "BIZBOK® Guide v7.5 Rolls Out New Business Architecture Reference Model Content, Other Updates". PR Newswire. March 5, 2019. Retrieved April 19, 2019.

Further reading

Commons-logo.svg Media related to Business architecture at Wikimedia Commons

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.