DOCSLIB.ORG

Business Services Architecture and Enterprise Architecture

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Business Services Architecture and Enterprise Architecture BusinessBusiness Services Services Architecture Architecture and Enterpriseand Enterprise Architecture Architecture This Workshop – Two parts Background: Business Value of Enterprise Architecture TOGAF Architectures and the Business Services Architecture We will use the key steps, methods and information requirements of TOGAF as a role model to create the Business Architecture and the supporting Information Systems Architectures Business Services Architecture On the way we will examine the Zachman Framework and its relationship with the TOGAF Business and Information Systems Architecture deliverables 1of 50 Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture TOGAF 8 Enterprise Architecture PreliminaryPreliminary FrameworkFramework && PrinciplesPrinciples AA ArchitectureArchitecture GG VisionVision ArchitectureArchitecture BB ChangeChange BusinessBusiness ManagementManagement ArchitectureArchitecture C CCC Information GG InformationInformationInformation Requirements System ImplementationImplementation SystemSystemSystem Management Architectures GovernanceGovernance ArchitecturesArchitecturesArchitectures FF DD MigrationMigration TechnologyTechnology PlanningPlanning ArchitectureArchitecture EE 2of 50 OpportunitiesOpportunities && SolutionsSolutions Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture PreliminaryPreliminary Preliminary Phase Objectives FrameworkFramework && PrinciplesPrinciples To ensure that everyone who will be involved in or benefit from this approach is committed to the success of the architectural process. To define the architecture principles that will inform the constraints on any architecture work. To define the "architecture footprint" for the organization - the people responsible for performing architecture work, where they are located, and their responsibilities. To define the scope and assumptions To define the framework and detailed methodologies that are going to be used to develop enterprise architectures in the organization concerned. To set up and monitor a process to confirm the fitness for purpose of the defined framework. To define a set of criteria for evaluating architecture tools repositories and repository management processes to be used to capture, publish, and maintain architecture artefacts 3of 50 NEXT Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture Business Focused TOGAF Enterprise Continuum Architecture Continuum Foundation Common Systems Industry Organization Architectures Architectures Architectures Architectures Business Applications Qualities Guides & Guides & Guides & Guides & Supports Supports Supports Supports Products & Systems Industry Organization Services Solutions Solutions Solutions 4of 50 Solutions Continuum NEXT Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture AA PreliminaryPreliminary ArchitectureArchitecture FrameworkFramework && Phase A VisionVision PrinciplesPrinciples The objective of Phase A is to define the scope; create AA the vision; identify the ArchitectureArchitecture HH stakeholders and obtain VisionVision ArchitectureArchitecture BB approvals. ChangeChange BusinessBusiness ManagementManagement ArchitectureArchitecture C CCC Information GG InformationInformationInformation Requirements System ImplementationImplementation SystemSystemSystem Management Architectures GovernanceGovernance ArchitecturesArchitecturesArchitectures FF DD During each Phase, the work is MigrationMigration TechnologyTechnology validated against the current PlanningPlanning ArchitectureArchitecture business requirements that EE motivate the development. OpportunitiesOpportunities 5of 50 && SolutionsSolutions NEXT Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture AA ArchitectureArchitecture TOGAF 8: Phase A VisionVision Ensure that this evolution of the architecture development cycle has proper recognition and endorsement from the corporate management of the enterprise, and the support and commitment of the necessary line management. Validate the business principles, business goals, and strategic business drivers of the organization. Define the scope of, and to identify and prioritize the components of, the current architecture effort. Define the relevant stakeholders, and their concerns and objectives. Define the key business requirements to be addressed in this architecture effort, and the constraints that must be dealt with Articulate an architectural vision that demonstrates a response to those requirements and constraints. Secure formal approval to proceed. Understand the impact on, and of, other enterprise architecture development cycles going on in parallel. 6of 50 NEXT Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture AA ArchitectureArchitecture TOGAF 8 Phase A Steps VisionVision Establish project 9Request for Use Business Scenarios Architecture Work Identify Business Principles, 9Existing Business Goals and Strategy Goals and Business Drivers Review Architecture Principles 9Existing Business Version 1 of: & Architecture Business Baseline Architecture Principles Scope the Architecture Project Technical Baseline Architecture Business Target Architecture 9Enterprise Define Constraints Technical Target Architecture Continuum Create the Business Scenario & Architecture Vision 9Refined Business & Architecture Principles 9Architecture Vision 7of 50 Produce Statement of Architecture 9Statement of Architecture Work Work & Gain Approval NEXT Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture AA ArchitectureArchitecture What is a Business Scenario? VisionVision The TOGAF technique for identifying and articulating the business requirements implied in new business functionality to address key business drivers, and the implied technical architecture requirements. The technique may be used iteratively, at different levels of detail in the hierarchical decomposition of the Business Architecture. The generic Business Scenario process is as follows: 8of 50 Architecting-the-Enterprise NEXT Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture AA ArchitectureArchitecture What is a Business Scenario? VisionVision Problem: Identify, document and rank the problem that is driving the project. Business and technical environments: Document, as high-level architecture models, the business and technical environment where the problem situation is occurring. Objectives and Measures of Success: Identify and document desired objectives, the results of handling the problems successfully. Human Actors: Identify human actors and their place in business model, the human participants and their roles. Computer Actors: Identify computer actors and their place in technology model, the computing elements and their roles. Roles and Responsibilities: Identify and document roles, responsibilities and measures of success per actor, the required scripts per actor, and the desired results of handling the situation properly. Refine: Check for fitness for purpose of inspiring subsequent architecture work, and refine only if necessary. 9of 50 Architecting-the-Enterprise NEXT Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture BB PreliminaryPreliminary BusinessBusiness Phase B Business Architecture FrameworkFramework && ArchitectureArchitecture PrinciplesPrinciples The objective of Phase B is to describe the current AA baseline Business ArchitectureArchitecture Architecture and to develop HH VisionVision a Target Business ArchitectureArchitecture BB Architecture ChangeChange BusinessBusiness ManagementManagement ArchitectureArchitecture C CCC Information GG InformationInformationInformation Requirements System ImplementationImplementation SystemSystemSystem Management Architectures GovernanceGovernance ArchitecturesArchitecturesArchitectures FF DD MigrationMigration TechnologyTechnology PlanningPlanning ArchitectureArchitecture EE OpportunitiesOpportunities 10 of 50 && SolutionsSolutions NEXT Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture What are the Objectives for Business Architecture work? BB BusinessBusiness TOGAF Phase B Objectives ArchitectureArchitecture Describe the current baseline business architecture Develop a target Business Architecture describing the product and/or service strategy, the organizational, functional, process, information, and geographic aspects of the business environment based on the business principles, business goals, and strategic drivers. Analyze the gaps between the baseline and target Business Architectures Select the relevant architectural viewpoints that will enable the architect to demonstrate how the stakeholder concerns are addressed in the Business Architecture. Select the relevant tools and techniques to be used in association with the 11 of 50 selected viewpoints NEXT Architecting-the-Enterprise Limited Copyright © 2003-2004 Business Services Architecture and Enterprise Architecture BB BusinessBusiness Business Architecture Re-use ArchitectureArchitecture Key elements of the Business Architecture may be produced elsewhere The enterprise
Load more

Recommended publications
  • Business Architecture: Setting the Record Straight
    BUSINESS ARCHITECTURE: SETTING THE RECORD STRAIGHT By William Ulrich and Whynde Kuehn This is a Reprint of Chapter 2, Part 1, of Business and Dynamic Change: The Arrival of Business Architecture, Published by Future Strategies, Inc. © 2015, but revised January 2019 http://BusinessandDynamicChange.com COPYRIGHT © 2019 BUSINESS ARCHITECTURE ASSOCIATES 1 BUSINESS ARCHITECTURE: SETTING THE RECORD STRAIGHT BUSINESS ARCHITECTURE: SETTING THE RECORD STRAIGHT William Ulrich, TSG, Inc. and BAA, Inc., USA Whynde Kuehn, S2E Transformation Inc. and BAA, Inc., USA An Introduction to Business Architecture Business architecture is drawing significant interest from a wide variety of organizations worldwide. Yet business architecture is often misperceived as to its uses, origins, and value proposition. These misperceptions are the biggest barrier to adoption, because it prevents businesses in many cases from getting a business architecture effort off the ground, and undercuts sponsorship and business engagement. Business architecture is not a buzzword or a quick fix solution for a broken process, a computer system, or a single project or business unit. It is a holistic discipline that is most effective when applied across business units, practices, disciplines, and stakeholders. The discussion that follows lays out a number of fundamental business archi- tecture concepts. This includes an overview, beneficiaries, common myths, core and extended perspectives, interdisciplinary alignment, governance, get- ting started, and a vision for the future. Business Architecture: What Is It? Formally defined, business architecture represents holistic, multidimensional business views of: capabilities, end-to-end value delivery, information, and or- ganizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.2.(1) It is an ab- stract set of standardized perspectives that represent a given business ecosys- tem.
    [Show full text]
  • Enterprise Architecture Techniques for SAP Customers
    October 2007 Enterprise Architecture Techniques for SAP Customers by Derek Prior Enterprise architecture has rapidly matured in recent years as a business-driven technique to provide companies with the big picture needed to optimize long-term IT investments. Some of the leading SAP customers have been quietly deploying enterprise architecture techniques to transform their business and prepare for SOA. Why haven’t you? Enterprise Strategies Report Acronyms and Initialisms ADM Architecture development method ERP Enterprise resource planning BPM Business process management ISV Independent software vendor CMDB Configuration management database ITIL IT infrastructure library CRM Customer relationship management PPM Project portfolio management DMTF Distributed Management Task Force SOA Service-oriented architecture EA Enterprise architecture TOGAF The Open Group Architecture Framework EAF Enterprise architecture framework © Copyright 2007 by AMR Research, Inc. AMR Research® is a registered trademark of AMR Research, Inc. No portion of this report may be reproduced in whole or in part without the prior written permission of AMR Research. Any written materials are protected by United States copyright laws and international treaty provisions. AMR Research offers no specific guarantee regarding the accuracy or completeness of the information presented, but the professional staff of AMR Research makes every reasonable effort to present the most reliable information available to it and to meet or exceed any applicable industry standards. AMR Research is not a registered investment advisor, and it is not the intent of this document to recommend specific companies for investment, acquisition, or other financial considerations. This is printed on 100% post-consumer recycled fiber. It is manufactured entirely with wind-generated electricity and in accordance with a Forest Stewardship Council (FSC) pilot program that certifies products made with high percentages of post-consumer reclaimed materials.
    [Show full text]
  • Linking Business Models with Business Architecture to Drive Innovation
    Linking Business Models with Business Architecture to Drive Innovation Linking Business Models with Business Architecture to Drive Innovation A Business Architecture Guild Whitepaper Principal Co-Authors: Steve DuPont, Karen Erwin, Bryan Lail, Stephen Marshall Reviewers: Remco Blom, Frank Fons, William Ulrich, Wilton Wratten, Carl Zuhl August 2015 1 Copyright ©2015 Business Architecture Guild Linking Business Models with Business Architecture to Drive Innovation Executive Summary A business model describes the rationale of how an organization creates, delivers, and captures value.1 Organizations are expanding their innovation focus from products and processes to business models in order to remain competitive in the face of shrinking product lifecycles and growing market uncertainties. They are increasingly embracing the business model concept in strategic planning, accompanied by a greater focus on customers and corresponding value propositions. In a parallel development, organizations are using business architecture to provide increased business transparency and maximize the likelihood of an effective and successful deployment of strategy. Business architecture is defined as “a blueprint of the enterprise that provides a common understanding of the organization and is used to align strategic objectives and tactical demands.”2 Despite the natural progression from business models (as an expression of business strategy) to business architecture (as the actionable blueprint for that strategy), these two concepts have evolved separately. To date, limited consideration has been given as to how they relate to each other. This white paper aims to address that gap, by demonstrating that the two approaches not only relate to each other but also work well together to effect change. We further expand on this synergy with a practical case study.
    [Show full text]
  • The Process Architect: the Smart Role in Business Process Management
    Redpaper Roland Peisl The Process Architect: The Smart Role in Business Process Management This IBM® Redpaper™ publication describes the concept of business process management (BPM) and specifically focuses on the role of the process architect within BPM. This paper covers in detail how to design business processes and how to enhance those processes for automated business process execution on a BPM platform. It addresses the requirements to successfully drive BPM programs in terms of what process knowledge, methodology, and technology needs to exist or be developed within an organization. Within the context of this paper, the process architect is defined as having the responsibility to model, analyze, deploy, monitor, and continuously improve business processes. This paper defines the role of the process architect as the driver of creating and improving processes and as a key bridge between business and process focused technology. This paper is intended for anyone who is involved in creating and improving BPM within an organization. © Copyright IBM Corp. 2009, 2012. All rights reserved. ibm.com/redbooks 1 Introduction Today, organizations that are facing aggressive market challenges share focus. To be more agile and to react faster to market changes, they must understand business processes better and in more detail. Business processes represent the organization’s key assets. The way a company invents, provides, and controls its core products and services depends on its core business processes. How well these processes can be managed and adapted to market changes is critical and more important than ever. Knowing business processes in detail requires further investigation. People from lines of businesses and from IT must understand the details of their business or IT capabilities.
    [Show full text]
  • Business Architecture a Balance of Approaches to Implementation
    Business Architecture A Balance of Approaches to Implementation Business Architecture Innovation Summit – June 2013 Presenter: Andrew Sommers Implementing Business Architecture at Capital Group Positioning Communicating Measuring Integrating 2 Measuring – What is the value of Business Architecture? Useful information, but starting a discussion of Business Architecture from here was challenging 3 Measuring – What is the Value of Business Architecture? If we have a successful Business Architecture practice, what are we able to do in 5 years that we cannot do now? Some ideas: • Provide a consistent method to directly link business objectives and drivers to the features that are required in our operating model, business processes, and technology solutions. • Provide a consistent enterprise view of the organization to quickly understand the entire impact of a business proposal. • Provide a consistent enterprise view of the organization to teams for analysis, planning, risk management, and support. • Improve our ability to leverage people, process, technology and information solutions for the same capability across the organization. • … But, what is it worth? 4 Positioning –Business Architecture in Our Organizational Model Placement is traditionally discussed in terms of our organizational chart Business Lead Management Services Investment Operations Technology Services Enterprise Architecture, Strategy, and Planning Equity Order Application Processing Services Solution Fixed Income Architecture Infrastructure Order Processing Business Architecture
    [Show full text]
  • Holistic Layer of the Enterprise Architecture on the Basis of Process-Driven Organization
    Complex Systems Informatics and Modeling Quarterly CSIMQ, Article 65, Issue 11, June/July 2017, Pages 69–84 Published online by RTU Press, https://csimq-journals.rtu.lv https://doi.org/10.7250/csimq.2017-11.04 ISSN: 2255-9922 online Holistic Layer of the Enterprise Architecture on the Basis of Process-Driven Organization Stepan Alexa1* and Vaclav Repa1 1 Department of Information Technologies (FIS), University of Economics in Prague W. Churchill Sq. 1938/4, 130 67 Prague 3 - Žižkov, Czech Republic [email protected], [email protected] Abstract. Growing complexity of the enterprise ecosystem along with the existence of legacy approaches in the organization can result in a number of challenges when maintaining the solid baseline of its information assets. The digital industry has, over past two decades, passed through rapid evolution triggered both by availability of new technologies, and business as well as operating and funding models. These enablers have direct impact on the way that organizations design and execute their business processes in order to maintain the alignment between their capabilities and targets. This trend implies that enterprises and organizations need to remain flexible by maintaining the alignment of their business and their infrastructure in a dynamically changing and integrated ecosystem. It has been widely recognized that the enterprise architecture as well as the process driven approaches provide tools used by organizations to explain how business, resources and other elements within the organization are related to each other. This article discusses the role, and associated value, that the enterprise architecture and process driven approach have when describing what constitutes the enterprise.
    [Show full text]
  • BUSINESS ARCHITECTURE and BPM ALIGNMENT Austin, Texas, USA - September 17, 2014 INNOVATION WORKSHOP
    BUSINESS ARCHITECTURE AND BPM ALIGNMENT Austin, Texas, USA - September 17, 2014 INNOVATION WORKSHOP Lloyd Dugan, Business Process Management, Inc. Neal McWhorter, Strategic Value Partners Copyright 2014 @ Business Architecture Guild 1 TEAM OVERVIEW Copyright 2014 @ Business Architecture Guild 2 BPM ALIGNMENT COLLABORATIVE TEAM PROBLEM STATEMENT AND GOAL One of the key issues facing practitioners that are attempting to establish a Business Architecture (BA) practice is how to reconcile some of its concepts with those of other related analytic practices. This issue is perhaps most frequently encountered when organizations attempt to reconcile Business Architecture with existing practices in their Business Process Management (BPM) areas. The BPM-BA Alignment Group is striving to provide a foundation for organizations to use to begin building linkages between these two analytic areas by defining and illuminating the differences and touch points between these two related disciplines and associated practice areas. This foundation will recognize that many BPM practitioners, particularly with respect to process modeling, are already doing what is described here. 9/12/2014 Copyright 2014 3 BPM ALIGNMENT COLLABORATIVE TEAM DELIVERABLES COMPLETE . Updated Section 3.4 of BIZBOK® Guide (Version 4.0), “Business Architecture and Business Process Modeling & Management” . Delivered webinar June 2014 PLANNED . Forthcoming Position Papers on relationship between BA and BPM . First version of “Business Architecture and BPM - Differentiation and Reconciliation” whitepaper is released on website, but is currently under review by BPM Community and subject to change . Related Clarification in Business Architecture Framework and Metamodel . Other BIZBOK® Guide Section 3.4 changes TBD . Other priorities TBD based on community feedback today 9/12/2014 Copyright 2014 4 BPM ALIGNMENT COLLABORATIVE TEAM TEAM MEMBERS Member Company Role William Ulrich TSG, Inc.
    [Show full text]
  • Archimate And
    Using the ArchiMate® Modeling Language with BMM™ Representing the Concepts of the Business Motivation Model (BMM) using the ArchiMate 3.0 Specification A White Paper by: Ed Walters and Antonio Plais August 2017 Using the ArchiMate® Modeling Language with BMM™ Copyright © 2017, The Open Group The Open Group hereby authorizes you to use this document for any purpose, PROVIDED THAT any copy of this document, or any part thereof, which you make shall retain all copyright and other proprietary notices contained herein. This document may contain other proprietary notices and copyright information. Nothing contained herein shall be construed as conferring by implication, estoppel, or otherwise any license or right under any patent or trademark of The Open Group or any third party. Except as expressly provided above, nothing contained herein shall be construed as conferring any license or right under any copyright of The Open Group. Note that any product, process, or technology in this document may be the subject of other intellectual property rights reserved by The Open Group, and may not be licensed hereunder. This document is provided "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. Any publication of The Open Group may include technical inaccuracies or typographical errors. Changes may be periodically made to these publications; these changes will be incorporated in new editions of these publications.
    [Show full text]
  • The Business Architecture Metamodel Guide
    The Business Architecture Metamodel Guide Defining a business architecture knowledgebase founded on formal principles Authors Thomas Bata, Paul Lyndon, Hermann Schlamann, William Ulrich Contributors Business Architecture Guild Metamodel Team Reviewers Bert Hooyman, Stephen Marshall, Jim Rhyne August 2020 1 Copyright ©2020 Business Architecture Guild® The Business Architecture Metamodel Guide CONTENTS 1. Abstract .......................................................................................................................................... 4 2. Introduction.................................................................................................................................... 6 3. Business Architecture Overview ..................................................................................................... 8 4. The Business Architecture Framework ......................................................................................... 10 4.1 The Business Architecture Knowledgebase .......................................................................... 10 4.2 Business Architecture Blueprints .......................................................................................... 11 4.3 Business Architecture Scenarios ........................................................................................... 11 5. Business Architecture Domain Associations ................................................................................. 13 5.1 Introducing the Business Architecture Metamodel .............................................................
    [Show full text]
  • Complex Event As an Core Aspect of Enterprise Architecture EDEMF: Event Driven Enterprise Architecture Modeling Framework
    Complex Event as an Core Aspect of Enterprise Architecture EDEMF: Event Driven Enterprise Architecture Modeling Framework Hyeonsook Kim, Samia Oussena and Peter Komisarczuk School of Computing and Technology, University of West London, St. Mary’s Road, London, U.K. Keywords: Enterprise Architecture, Business Modelling, Complex Event Modelling, Event Driven Architecture, Complex Event Processing, Model Driven Architecture, Linked Data, Data Integration. Abstract: For the last decade, Complex Event Processing (CEP) has been emerged as a powerful instrument supporting a more agile and intelligent enterprise. Although several studies have attempted to extend current business modelling standards with elements of complex event modelling they have not fully integrated into Enterprise Architecture (EA). EA provides holistic approach of enterprise business and IT system modelling. In our view CEP is not just an element associated with a business process, but at the centre of business analysis and design. This paper proposes an EA modelling framework that takes CEP as a core aspect of modelling. The framework supports CEP based business architecture within different levels of abstraction: contextual, conceptual/logical, and physical. Meta-models in three hierarchies and model mapping between the meta-models have been developed and demonstrated on a linked data platform in a case study. The case study used the framework as a tool of analysis and modelling, aiming to integrate scattered information as event data by specifying a complex event layer on top of legacy systems. The designed models were then transformed into executable program codes using the model transformation, for example, RDF script from information model; SPARQL query from complex event model.
    [Show full text]
  • Business Architecture
    FRONT MATTER FM 1 – TABLE OF CONTENTS Front Matter Front Matter– Table of Contents Table of Contents FRONT MATTER TABLE OF CONTENTS ....................................................................................................... FM1 ABSTRACT .......................................................................................................................... FM2 MITA AT A GLANCE ............................................................................................................ FM3 Introduction .................................................................................................................... 4 Front Matter .................................................................................................................... 5 Part I Business Architecture .......................................................................................... 6 Part II Information Architecture ..................................................................................... 9 Part III Technical Architecture ....................................................................................... 11 State Self-Assessment ................................................................................................... 13 ACRONYMS AND TERMS ................................................................................................... FM4 OVERVIEW OF THE MITA INITIATIVE ................................................................................ FM5 Introduction ...................................................................................................................
    [Show full text]
  • The Oracle Enterprise Architecture Framework
    An Oracle White Paper in Enterprise Architecture October 2009 The Oracle Enterprise Architecture Framework Oracle White Paper in Enterprise Architecture—The Oracle Enterprise Architecture Framework Disclaimer The following is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Oracle White Paper in Enterprise Architecture—The Oracle Enterprise Architecture Framework Executive Overview...........................................................................1 Introduction .......................................................................................1 Enterprise Architecture ......................................................................2 Enterprise Architecture Frameworks..................................................3 The Oracle Enterprise Architecture Framework .................................4 The Oracle Architecture Development Process .................................9 Summary: Value & Benefits............................................................10 A Case Study ..................................................................................11 Conclusion ......................................................................................12 Oracle White Paper in Enterprise Architecture—The Oracle Enterprise Architecture Framework Executive Overview The Oracle Enterprise Architecture Framework helps Oracle to collaboratively work with customers
    [Show full text]