Business Services Architecture And Enterprise Architecture
BusinessServicesArchitectureand and EnterpriseArchitecture 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 rolemodel 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 theTOGAF Business and Information Systems Architecture deliverables1 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004
Business Services Architecture and Enterprise ArchitectureTOGAF 8 Enterprise anning2 of 50Architecting-the-EnterpriseLimitedCopyright uirementsManagementEEOpportunitiesOpportunities&& ramework TechnologyArchitectureArchitecture
Business Services Architecture and Enterprise ArchitecturePreliminary Phase ObjectivesPreliminaryPreliminaryFrameworkFramework &&PrinciplesPrinciples To ensure that everyone who will be involved in or benefit from this approachis committed to the success of the architectural process. To define the architecture principles that will inform the constraints on anyarchitecture work. To define the "architecture footprint" for the organization - the peopleresponsible for performing architecture work, where they are located, and theirresponsibilities. To define the scope and assumptions To define the framework and detailed methodologies that are going to be usedto develop enterprise architectures in the organization concerned. To set up and monitor a process to confirm the fitness for purpose of thedefined framework.3 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004 To define a set of criteria for evaluating architecture tools repositories andrepository management processes to be used to capture, publish, andmaintain architecture artefactsNEXT
Business Services Architecture and Enterprise ArchitectureBusiness Focused TOGAF Enterprise ContinuumArchitecture ContinuumFoundation Common res ArchitecturesArchitecturesBusiness ApplicationsQualitiesGuides &Supports4 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004Guides &SupportsProducts &SystemsServicesSolutionsSolutions ContinuumGuides &SupportsGuides T
Business Services Architecture and Enterprise rk &&PrinciplesPrinciplesPhase AThe objective of Phase A isto define the scope; createthe vision; identify thestakeholders and tionGovernanceGovernanceDuring each Phase, the work isvalidated against the currentbusiness requirements thatmotivate the development.5 of 50Architecting-the-EnterpriseLimitedCopyright ementEEOpportunitiesOpportunities&& ectureArchitectureNEXT
Business Services Architecture and Enterprise ArchitectureTOGAF 8: Phase AAAArchitectureArchitectureVisionVision Ensure that this evolution of the architecture development cycle has properrecognition and endorsement from the corporate management of theenterprise, and the support and commitment of the necessary linemanagement. Validate the business principles, business goals, and strategic businessdrivers of the organization. Define the scope of, and to identify and prioritize the components of, thecurrent architecture effort. Define the relevant stakeholders, and their concerns and objectives. Define the key business requirements to be addressed in this architectureeffort, and the constraints that must be dealt with Articulate an architectural vision that demonstrates a response to thoserequirements and constraints. Secure formal approval to proceed.6 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004 Understand the impact on, and of, other enterprise architecture developmentcycles going on in parallel.NEXT
Business Services Architecture and Enterprise TOGAF 8 Phase A Steps9Request forArchitecture Work9Existing BusinessGoals andBusiness DriversEstablish project Use Business ScenariosIdentify Business Principles,Goals and StrategyReview Architecture Principles9Existing Business& ArchitecturePrinciplesVersion 1 of: Business Baseline ArchitectureScope the Architecture Project Technical Baseline Architecture Business Target Architecture9EnterpriseContinuumDefine ConstraintsCreate the Business Scenario &Architecture Vision7 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004Produce Statement of ArchitectureWork & Gain Approval Technical Target Architecture9Refined Business & ArchitecturePrinciples9Architecture Vision9Statement of Architecture WorkNEXT
Business Services Architecture and Enterprise ArchitectureAAWhat is a Business Scenario?ArchitectureArchitectureVisionVision The TOGAF technique for identifying and articulating the businessrequirements implied in newbusiness functionality to address key business drivers, and the impliedtechnical architecture requirements. The technique may be used iteratively, at different levels of detail in thehierarchical decomposition of the Business Architecture. The generic Business Scenario process is as follows:8 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004NEXT
Business Services Architecture and Enterprise ArchitectureAAWhat is a Business Scenario?ArchitectureArchitectureVisionVision Problem: Identify, document and rank the problem that is driving the project. Business and technical environments: Document, as high-level architecturemodels, the business and technical environment where the problem situation isoccurring. 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, thehuman 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 andmeasures of success per actor, the required scripts per actor, and the desiredresults of handling the situation properly. Refine: Check for fitness for purpose of inspiring subsequent architecture work,and refine only if necessary.9 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004NEXT
Business Services Architecture and Enterprise ArchitecturePhase B Business anning10 of 50Architecting-the-EnterpriseLimitedCopyright uirementsManagementEEOpportunitiesOpportunities&& ramework ectureThe objective of Phase B isto describe the currentbaseline BusinessArchitecture and to developa Target nologyTechnologyArchitectureArchitectureNEXT
Business Services Architecture and Enterprise ArchitectureWhat are the Objectives for Business Architecture work?TOGAF Phase B re Describe the current baseline business architecture Develop a target Business Architecture describing the product and/or service strategy, the organizational, functional, process, information, and geographicaspects 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 todemonstrate how the stakeholder concerns are addressed in the BusinessArchitecture.11 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004 Select the relevant tools and techniques to be used in association with theselected viewpointsNEXT
Business Services Architecture and Enterprise ArchitectureBusiness Architecture Re-use12 of 50Architecting-the-EnterpriseLimitedCopyright e Key elements of the Business Architecture may be produced elsewhere The enterprise mission, vision, strategy and goals may be produced as part of awider business strategy or enterprise planning activity with its own life-cycle inthe enterprise. The new architecture work will need to verify and update the currentlydocumented business strategy and plans, and/or to bridge between high-levelbusiness drivers, business strategy and goals on the one hand, and the specificbusiness requirements A key objective is to reuse existing material and components as much aspossible. Use existing architecture definitions and architectural descriptions Use only information that allows informed decisions to be made for thescope If little or no business architecture work has been undertaken: the architecture team need to research, verify and gain buy-in to, the keybusiness objectives and processes that the architecture is to support. as a free-standing exercise or preceding architecture development or as partof the Architecture Development Business Scenarios or other methods of information capture may be used. If new business processes required then this Phase will involve a lot of detailedwork including a Process Architecture.NEXT
Business Services Architecture and Enterprise ArchitectureTOGAF 8 ADM: How do you create a Business Architecture?Inputs Request for Architecture WorkDevelop BusinessBaseline Description Approved Statement of ArchitectureWork / Project Definition, including inparticular:Develop Reference Models,Viewpoints and Tools Scope and constraintsCreate Architecture Models Refined statements of BusinessPrinciples, Business Goals andStrategic DriversSelect Business ArchitectureBuilding Blocks Architecture Principles Architecture Vision Business Scenarios, including: Business Baseline Version 1 Technical Baseline Version 1 Business Architecture Version 1 Technical Architecture Version 1 Enterprise ContinuumCheckpoint ReviewWith StakeholderOutputs Statement of Architecture Work Validated Business Principles,business goals, and strategicdrivers Target Business Architecture Version 2 Business Baseline - Version 2 Views corresponding to theselected viewpoints addressingkey stakeholder concerns Gap analysis resultsComplete Business Architecture Technical requirements - driversfor the Technical Architecturework:Produce Gap Analysis & Report Business Architecture Report Updated business requirements13 of 50Architecting-the-EnterpriseLimitedCopyright eNEXT
Business Services Architecture and Enterprise ArchitectureBusiness Architecture: reTOGAF Target Business Architecture Organization structure. identifying business locations and relatingthem to organizational units. Business goals and objectives. for each organizational unit. Business functions. a detailed, recursive step involving successivedecomposition of major functional areas into sub-functions. Business Services - the services that each enterprise unit provides toits customers, both internally and externally. Business processes, including measures and deliverables Business roles, including development and modification of skillsrequirements.14 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004 Correlation of organization and functions. Relate business functionsto organizational units in the form of a matrix report.NEXT
Business Services Architecture and Enterprise ArchitectureTOGAF 8 Role ModelAAArchitectureArchitectureVisionVision Are we ready to do our IT Architecture? Do we need to complete the Business Architecture before we canproceed further? Do we need an Information Systems Architecture before we cancreate an IT Architecture? What is the scope of the Information Systems Architecture? What else do we need? Information Process Data Applications Business Requirements15 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004 Who needs to buy-in?NEXT
Business Services Architecture and Enterprise rk &&PrinciplesPrinciplesThe objective of this phase is todevelop target architecturescovering either or both (dependingon project scope) of the Data andApplication Systems domains.The scope of the businessprocesses supported in this phaseis limited to those that aresupported by informationtechnology, and the interfaces ofthose IT-related processes to nonIT-related processes.Phase C Information Systems nGovernanceGovernanceFor the Application Architecturethe objective and goal is to definewhat kinds of application systemsare relevant to the enterprise, andwhat those applications need to doin order to manage data and topresent information to the humanand computer actors in the16 of yright ementEEOpportunitiesOpportunities&& nologyArchitectureArchitectureFor the Data Architecture, theobjective is to define the majortypes and sources of datanecessary to support the business,in a way that is understandable bystakeholders and which iscomplete, consistent and stable.NEXT
Business Services Architecture and Enterprise ArchitectureTOGAF Information Systems chitecturesArchitecturesObjectives To develop target architectures covering the Data and Application Systemsdomains. The scope of the business processes supported in this phase is limited to those that are supported by information technology the interfaces of IT-related processes to non-IT-related processes. The focus is on a combination of Data and Applications Architecture, in eitherorder.17 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004NEXT
Business Services Architecture and emSystemArchitecturesArchitecturesInputs and OutputsOutputsInputs Statement of Architecture Work Statement of Architecture Work Target Data Architecture Validated Business Principles,business goals, and strategicdrivers Target Business Architecture Version 2 Business Baseline - Version 2 Views corresponding to theselected viewpoints addressingkey stakeholder concerns Target Applications Architecture Data Architecture Views addressing keystakeholder ecturesArchitectures Applications Architecture Views addressingkey stakeholder concerns Data Architecture Report Applications Architecture Report Gap analysis results Gap Analysis Technical requirements - driversfor the Technical Architecturework: Constraints on Technology Architecture work: Business Architecture Report18 of ht 2003-2004business requirements Business Architecture Changes & Report Impact Analysis Updated Business RequirementsNEXT
Business Services Architecture and Enterprise ArchitectureData Architecture: itecturesArchitectures To define the major types and sources of data necessary to support thebusiness, in a way that is understandable by stakeholders complete and consistent stable The goal is to define the data entities relevant to the Enterprise Linkages to existing files and databases may be developed and demonstratesignificant areas for improvement. This effort is NOT concerned with database design, or design of logical orphysical storage systems.19 of 50Architecting-the-EnterpriseLimitedCopyright 2003-2004NEXT
Business Services Architecture and Enterprise ArchitectureOutputsData ArchitectureInputs Data Principles Request for ArchitectureWork Statement ofArchitecture Work Architecture Vision Relevant technicalrequirements that willapply to this phase Gap analysis Business Baseline Version 2 Target BusinessArchitecture - Version 2 Re-usable buildingblocks from theEnterprise Continuum Definitions of current20 of 50dataArchitecting-the-EnterpriseLimitedCopyright 2003-2004Develop DataBaseline DescriptionDevelop Principles,Reference Models,Viewpoints and ToolsCreate Architecture Models Select Data ArchitectureBuilding BlocksCheckpoint ReviewWith StakeholderReview qualitative criteriaComplete Data Architecture Produce Gap Analysis& Report Statement of Architecture WorkData Baseline Description - if appropriateValidated or new Data PrinciplesTarget Data ArchitectureConceptual data modelLogical data modelData Management Process modelsData entity / business function matrixData interoperability requirementsViewpoints and views addressing keystakeholder concerns for data Data dissemination view Data lifecycle view Data security view Data model management viewGap analysis resultsTechnical requirementsData Architecture Report,Impact AnalysisData Architecture driven changes to theBusiness and Application ArchitecturesConstraints on the TechnologyArchitectureUpdated business requirementsNEXT
Business Services Architecture and Enterprise ArchitectureApplications ArchitectureObjective To define the major kinds of application system required to process the dataand support the business. The goal is to define what kinds of application systems are relevant to theenterprise, and what those applications need to do in order to manage dataand to present information to the human and computer actors in theenterprise. The applications : are described as logical groups of capabilities that manage the dataobjects in the data architecture and support the business functions in theBusiness Architecture. and their capabilities are defined without reference to particulartechnologies. The applications are stable and relatively unchanging over time.21 of 50 The technology used to implement the applications will change over time,based on the technologies currently available and changing business needs. This effort is NOT concerned with applications systems designArchitecting-the-EnterpriseLimitedCopyright 2003-2004NEXT
Business Services Architecture and Enterprise ArchitectureOutputsApplications ArchitectureInputs Applications Principles Request for ArchitectureWork Statement of ArchitectureWork Architecture VisionDevelop ApplicationsBaseline DescriptionDevelop Principles,Ref
Key elements of the Business Architecture may be produced elsewhere The enterprise mission, vision, strategy and goals may be produced as part of a wider business strategy or enterprise planning activity with its own life-cycle in the enterprise. The new architecture work will need to verify and update the currently documented business strategy and plans, and/or to bridge between high-level .
CARESOURCE'S BUSINESS ARCHITECTURE PRACTICE ¡CareSource's Business Architecture practice is part of the Enterprise Architecture team ¡EA team uses Orbus iServer as our primary architecture tool ¡In 2020, launched a reset / maturing focus on the business architecture practices: ¡ Existing capability model rebuilt leveraging Business Architecture Guild's industry reference models
FEA Federal Enterprise Architecture FEAF Federal Enterprise Architecture Framework GEA-NZ Government Enterprise Architecture for New Zealand HR Human Resources IaaS Infrastructure as a Service IM/IT Information Management / Information Technology IT Information Technology IFEAD Institute for Enterprise Architecture Development .
VA Enterprise Architecture Per the Clinger-Cohen Act, it is a requirement for federal agencies to maintain an IT architecture (Clinger-Cohen Act of 1996). The government developed the Federal Enterprise Architecture (FEA) specifically for federal agencies, however; The VA uses its own architecture framework called the VA Enterprise Architecture.
According to the Institute for Enterprise Architecture Developments, "Enterprise Architecture is about understanding all of the different elements that make up an enterprise and how those elements inter-relate".6 Gartner Consulting says, "Enterprise architecture provides a decision framework, in the context of the
Architecture Trend 2: Project to Product Trend 3: The Democratization of Enterprise Architecture Trend 4: Continuous Improvement of Way-of-Working Trend 5: Enterprise Architecture as a Digital Twin of the Organization Summary of Enterprise Architecture Trends p. 3 - 6 p. 7 - 12 p. 13 - 21 p. 28 - 34 p. 35 - 41 p. 42 - 46 p. 22 - 27 Reference .
Architecture Frameworks - Architecture Frameworks 20 January, 2020 TOGAF The Open Group Architecture Framework (TOGAF) is one of the most widely accepted methods for developing enterprise architecture. TOGAF is an open framework, providing a practical, definitive and proven step-by-step method for developing and maintaining enterprise architecture.
What is Computer Architecture? “Computer Architecture is the science and art of selecting and interconnecting hardware components to create computers that meet functional, performance and cost goals.” - WWW Computer Architecture Page An analogy to architecture of File Size: 1MBPage Count: 12Explore further(PDF) Lecture Notes on Computer Architecturewww.researchgate.netComputer Architecture - an overview ScienceDirect Topicswww.sciencedirect.comWhat is Computer Architecture? - Definition from Techopediawww.techopedia.com1. An Introduction to Computer Architecture - Designing .www.oreilly.comWhat is Computer Architecture? - University of Washingtoncourses.cs.washington.eduRecommended to you b
The section on illustration greatly benefited from Lys Drewett s ten years experience teaching archaeological illustration at the Institute of Archaeology and as illustrator on all my archaeological projects. Most of the illustrations derive from my field projects but, where not, these are gratefully acknowledged under the illustration. To any other archaeologists who feel I may have used .
