Översikt och diskussion kring EA-ramverk, en uppdatering..

Vilka ramverk? Ramverk Modelltekniker Zachman TOGAF IRM Astrakan ArchiMate Business Canvas Modelling Business System Planning Operating Model (Ross et.al)

Method for classifying the Enterprise: Useful for: Zachman Framework, introduced in 1987 by John Zachman and extended by John Sowa in 1992 (Sowa and Zachman 1992), as it applies to enterprises is a logical structure for classifying and organizing the descriptive representations of an enterprise that are significant to the management of the enterprise as well as to the development of the enterprise’s systems. It was derived from analogous structures that are found in the older disciplines of Architecture/Construction and Engineering/Manufacturing that classify and organize the design artifacts created over the process of designing and producing complex physical products (e.g., buildings or airplanes.) Method for classifying the Enterprise: Useful for: Verifying what is implemented Determining what is not implemented Defining the scope of the Enterprise © Biner Consulting

Zachman Ett kategoriserande och analytiskt ramverk som vi kan använda till att klassificera arkitekturarbete i andra arkitektoriska ramverk – Zachmanramverket är det som gör det möjligt och förstå hur andra ramverk är uppbyggda

Zachman © Biner Consulting

The Zachman Frameworks Seven rules The columns have no ordering. No one is more important than another but focusing on one may have significant practical implications. Each column represents a unique model. Each column is unique although they are interconnected. Each row represents a unique perspective. Therefore, each cell is unique (no item should show up in more than one cell). Each row is a complete model from the row's perspective. The logic is recursive and generic. The Zachman Frameworks Seven rules © Biner Consulting

Ideas Reality What How Where Who When Why Scope Strategists Business Exec Leaders System Architects Technology Reality Engineers Component Technicians Operations Workers Inventory Process Network Organization Timing Motivation Most of us are involved in moving Ideas to Reality Horizontal – Ideas are broad concepts generally from lateral thinking Vertical – Sequential steps structured thought Companies are interested in moving from ideas to reality as quickly as possible © Biner Consulting

Resource Behavior What How Where Who When Why Scope Strategists Business Exec Leaders System Architects Technology Engineers Component Technicians Operations Workers Inventory Process Network Organization Timing Motivation Resources/Behaviour © Biner Consulting

Physics specification Component configuration Operations Instantiation What How Where Who When Why Scope Idea Identification Strategists Business Concept definition Exec Leaders System Logic representation Architects Technology Physics specification Engineers Component Component configuration Technicians Operations Operations Instantiation Workers Inventory Process Network Organization Timing Motivation Stages of Reification “reification the conversion of an abstract concept into something concrete; a viewing of the abstract as concrete.” © Biner Consulting

Requirements – Concept What How Where Who When Why Scope Scope – Boundaries Strategists Business Requirements – Concept Exec Leaders System Design – Logic Architects Technology Plan – Physics Engineers Component Part– Configuration Technicians Operations Product–Instances Workers Inventory Process Network Organization Timing Motivation Different perspectives © Biner Consulting

What we would expect see in each layer How Where Who When Why Scope Lists Single words with dictionary meanings Strategists Business Semantic Models Establishes the relationships between business concepts Exec Leaders System Schematic Models Describes the logic which proves & supports the representation of the concepts Architects Technology Blueprint Models Specifies the physics constructs by which the logic and concept are made into reality Engineers Component Listings Documents the configuration of the various components Technicians Operations Instances Allows the operation of the Enterprise by permitting workers to use real instances of things Workers Inventory Process Network Organization Timing Motivation What do we expect to see in each cell across a layer Lists: Semantic : What is semantic knowledge modeling? Simply put, a knowledge model is a way to abstract disparate data and information. Knowledge modeling is about describing what data means and where it fits. It allows us to understand and abstract knowledge. Consequently it helps us to understand how different pieces of information relate to each other. A semantic model is one kind of a knowledge model. The semantic model consists of a network of concepts and the relationships between those concepts. Concepts are a particular idea or topic with which the user is concerned. Semantic models enable users to ask questions of the information in a natural way and help to identify patterns and trends in this information and discover relationships between disparate pieces of information. Schematic: Technology independent Blueprint: Date: 1886 1 : a photographic print in white on a bright blue ground or blue on a white ground used especially for copying maps, mechanical drawings, and architects' plans 2 : something resembling a blueprint (as in serving as a model or providing guidance); especially : a detailed plan or program of action <a blueprint for victory> What we would expect see in each layer © Biner Consulting

Olika branscher har fokus på olika kolumner Branscher som har sitt fokus i Vad kolumnen är tex Försäkringsbolag. Branscher som har sitt fokus i Hur kolumnen är tex Bilindustrin, läkemedelsindustrin. Branscher som har sitt fokus i Var kolumnen är tex DHL, ICA, IKEA, Flygbolag, Shipping, Kraftnät. Branscher som har sitt fokus i Vem kolumnen är tex Konsulter, Universitet, Myndigheter och alla företag som använder människor för att skapa tjänster. Branscher som har sitt fokus i När kolumnen är tex Polis, Brandkår, Musiker. Branscher som har sitt fokus i Varför kolumnen är tex Samfund. Källa Biner Consulting

Functional specification Operating Instructions What How Where Who When Why Scope Bill of Material Inventory Functional specification Process Drawings Network Operating Instructions Organization Timing Diagrams Timing Design Objectives Motivation Strategists Business Exec Leaders System Architects Technology Engineers Component Technicians Operations Workers What – Financial Services, where counting is important How – Manufacturing, where process driven and quality are important Where – DHL/FedEx or Aviation, where the location is important Who – Education, Consultancy, Hospital, where the individual is important When – Emergency Services, where the event is important Why – No Enterprise can exist without validation in the Why column – the Church is about the only enterprise that exists in the Why column Abstractions and where to start your effort based on focus of different industries.

”Operation Model” Kan hjälpa till att klassa affären och ge en indikation på vilka kolumner i Zachmanmatrisen som är mer intressant än andra i just för denna affär

kan hjälpa till att klassa braschen och ge en indikation på vilka kolumner i Zachmanmatrisen som är mer intressant än andra

What How Where Who When Why Scope Strategists Business Exec Leaders System Architects Technology Engineers Component Technicians Operations Workers Inventory Process Network Organization Timing Motivation Align horizontally Transform vertically Detta betyder att ni ska för varje innehåll I en cell se till att det innehållet är I linje med innehållet I alla andra celler på samma rad.

TOGAF 9

Architecture Capability ADM Architecture Content Framework Reference Models Architecture Capability Framework ADM Guidelines & Techniques Enterprise Continuum Architecture Development Method (ADM) An iterative sequence of steps to develop an enterprise-wide architecture ADM Guidelines and Techniques Guidelines and techniques to support the application of the ADM Architecture Content Framework A detailed model of architectural work products, including deliverables, artifacts within deliverables, and the Architecture Building Blocks (ABBs) that deliverables represent. The Enterprise Continuum A model for structuring a virtual repository and methods for classifying architecture and solution artifacts TOGAF Reference Models: The TOGAF Technical Reference Model (TRM) The Integrated Information Infrastructure Model (III-RM). The Architecture Capability Framework A structured definition of the organizations, skills, roles and responsibilities to establish and operate an Enterprise Architecture. De sex stora delarna i TOGAF 9 specifikationen © Biner Consulting

TOGAF Standard Courseware V9 Edition 03/04/2017 ADM består av nio faser som cykliskt bearbetar arkitekturdomänerna (verksamhet, applikation, data, teknologi). ADM ska användas iterativt i hela processen, mellan faserna och inom faserna. Each iteration = new decisions: Enterprise coverage, Level of detail, Time horizon, Architecture asset re-use: previous ADM iterations other frameworks, system models, industry models… Decisions based on: Competence / resource availability, Value accruing to the enterprise. © Biner Consulting © Biner Consulting Copyright © 2009, The Open Group 20

TOGAF ”punsch”-lines Views and Viewpoints ADM Principles Repository(Zachman) Referens models Content Kan göras nestat på olika nivåer i verksamheten

Hur hänger det ihop med Zachman och TOGAF? Arkitektur ala IRM Hur hänger det ihop med Zachman och TOGAF?

Arbetsgång Processkartläggning Modelleringsseminarium Begreppsidentifiering (Vilka begrepp finns) Begreppskategorisering (Vilka är objekt vad är egenskaper) Informationsmodellering Renritning Återkoppling – datamodell Matrisanalyser Process/Objektgrupp System/Objektgrupp Arkitekturmatris – naturliga moduler av Objektgrupper

Mappar direkt mot Zachman IRM Mappar direkt mot Zachman

Zachman - IRM IRM matrisanalyser lyfter kategoriserad information från Zachman-matrisen © Biner Consulting

Begrepp Information Domän Data Komponenter Standarden visar oss en bra kornighet på informationsnedbrytning (4 nivåer) som väl kan användas för att bestämma vilka nivåer som ska produceras. Följer Zachmans 6 rader Dessa steg motsvarar IRM:S ramverk i informationsperspektivet Informationsnedbrytning av en domän mappat mot TOGAF 9 ADM för att skapa arkitekturer © Biner Consulting

Är ett ypperligt komplement till IRM Astrakanmetoden Är ett ypperligt komplement till IRM

Begreppstätning och Processkarta Man definierar alla begrepp som finns Man använder inte ett begrepp utan att det finns en definition Det får inte finnas en begreppsdefinition som innehåller begrepp som inte är definierade Processkartläggning

IRM – Astrakan Kompletterar varandra – ger olika perspektiv på nästan samma problemområde IRM kan slarvar lite i begreppsdefinitionen där Astrakan är bättre. Medan IRM transformerar begreppen till en vettig datamodell – på processidan skiljer det inte så mycket, dock så mappar IRM mot fler celler i Zachman

Archimate

BCM Ett sätt att fånga upp saker Zachman rad 1 o 2 – flera kolumner

Operational Model Ross et. al.

Arkitekturarbete Arbete Förutsättningar Governance – ta fram Kravinventering Kravanalys ”Ekorre” – den som spar han har Sponsorer Governancestruktur

EA-ramverk och metoder Ingen generallösningar finns Ramverken ger dig bara förslag på hur du skall göra – vilket iofs är vad ett ramverk skall göra Ramverk försöker säga att de är holistiska – stämmer inte Lite som religion – man blir frälst på sitt

Slutsats Alla ramverk och modelltekniker kompletterar varandra och representerar olika perspektiv. Metabeskrivningarna till modellerna hjälper till att beskriva vilken modell som passar bäst till vilket problemområde. Det är här i svårigheten ligger. Den ena modellen hjälper otroligt i ena fallet medans i ett annat fall är utfallet inta alls lika bra.