Enterprise Architecture Modeling With ArchiMate & Sparx

Slides:



Advertisements
Similar presentations
1 Aspects of IEEE P1471 Viewpoints in Unified Modeling Language (UML) Manzur Ashraf, BRAC University Humayra Binte Ali, Dhaka University Md.Mahfuz Ashraf,
Advertisements

Copyright © 2006 Data Access Technologies, Inc. Open Source eGovernment Reference Architecture Approach to Semantic Interoperability Cory Casanave, President.
<<Titre du cours>>
Staffordshire University : Learning Development and Innovation part of the University’s Academic Development Unit About Enterprise Architecture > Why we.
Viewpoint.
Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the.
Moving from Checkmate to ArchiMate An introduction to the ArchiMate Forum & Language Louw Labuschagne Certified TOGAF Practitioner.
Training of master Trainers Workshop 10 – 15 November 2012 e-Services Design and Delivery Module IIX Emilio Bugli Innocenti.
ArchiMate of Architectures Rene van Buuren and AnalysisIntegration,Visualisation.
An Integrated Approach to Enterprise Architecture LIACS, Martijn Wiering 23 juni ‘04.
OASIS Reference Model for Service Oriented Architecture 1.0
Enterprise Architect and SysML – the story so far Sam Mancarella Chief Technology Officer Sparx Systems May 13, 2008
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
© 2005 Prentice Hall7-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
The Use of Zachman Framework Primitives for Enterprise Modeling
EA Modelling & Communications Tutorial 5. Your EA Learning Journey So Far  Week 1 Introduction Concepts WHAT IS  Week 2 EA Theories WHAT IS  Week 3.
David Harrison Senior Consultant, Popkin Software 22 April 2004
Tool support for Enterprise Architecture in System Architect Architecture Practitioners Conference, Brussels David Harrison Senior Consultant, Popkin.
Enterprise Architecture
Enterprise Architecture Modelling with ArchiMate Marc Lankhorst Principal Researcher Enterprise Architecture Utrecht University, January 11, 2010.
Chapter 6– Artifacts of the process
Developing Enterprise Architecture
An Overview of TOGAF® Version 9.1
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
TDT4252/DT8802 Exam 2013 Guidelines to answers
Solution Architecture
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2011 Lecture.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
Software Architecture in Practice Architectural description (The reduced version)
Modelling Class T16: Conceptual Modelling – Architecture Image from
The Open Group Architecture Framework (TOGAF) Version 7 John Spencer, Director – Architecture Forum Anaheim, January 24 th 2002.
1 Agenda Introduction Energistics Standards Panorama / History / Participants Web Services Interoperability Standards v1.0 WITSML Version 1.x Services.
System Context and Domain Analysis Abbas Rasoolzadegan.
Technology Layer. Technology Layer Metamodel Technology Layer Concepts.
Case studies ABP Meta-Model. Concepts ABP Meta-Model.
EServices Enablement Framework Session 3 Business Process Redesign.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
OBJECT ORIENTED AND FUNCTION ORIENTED DESIGN 1 Chapter 6.
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2011 Lecture.
Computer Science 340 Software Design & Testing Software Architecture.
Object Oriented Analysis and Design 1 Chapter 9 From Design to Implementation  Implementation Model  Forward, Reverse, and Round-Trip Engineering  Mapping.
Slide no. 1  =====!"§!“!Nova§ ITU-T work on technical languages and general software issues Amardeo Sarma Chairman, ITU-T Study Group 10.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures. Core Concepts Key Learning Points: This chapter will help you to answer the following questions: What are the ADM phase names.
Armstrong Process Group, Inc. Copyright © Armstrong Process Group, Inc., All rights reserved National Information Exchange.
TOGAF 9 and ArchiMate 2.0 for aligning SOA with Changing Strategies and Capabilities using Sparx EA A presentation on a short Case Study using Sparx EA.
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
CTMS Coordination Team CTMS Coordination Team: Model and Documentation Management John Koisch Paul Boyes
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Michael J. Novak ASQ Section 0511 Meeting, February 8, 2017
What is Enterprise Architecture?
ARIS Extension Pack TOGAF April 2016
Ministry of Healthcare and Social Development
A Comparative Survey of Enterprise Architecture Frameworks
The Open Group Architecture Framework (TOGAF)
CIMI Enterprise Architecture Proposal
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Unified Modeling Language
“The Right Work, Using The Right Tool, At The Right Time”
Geospatial Service Architecture Viewpoints
واسط كاربري هوشمند Intelligent User Interface
EA Framework TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture.
Prevention is better than the cure
ESTP Training Course “Enterprise Architecture and the different EA layers, application to the ESS context ” Rome, 16 – 19 October 2017.
Presentation transcript:

Enterprise Architecture Modeling With ArchiMate & Sparx Adnaan Sikandar Capgemini Canada Inc. Adnaan.Sikandar@capgemini.com

Agenda ArchiMate Overview ArchiMate Concepts ArchiMate Viewpoints Framework & Concept Layers Metamodels ArchiMate Viewpoints Information Structure Viewpoint Business Process Viewpoint Layered Viewpoint Infrastructure Viewpoint TOGAF ADM Viewpoints

ArchiMate What is it? ArchiMate is a modeling language for describing enterprise architectures Broader scope than UML. UML is for software engineering Supports EA frameworks like TOGAF & Zachman Can be used to create IAF views and artifacts ArchiMate viewpoints are more detailed than TOGAF’s architecture artifacts – TOGAF does not provide descriptions and examples

ArchiMate Which version should I use? Is it a standard? Technical Specification 1.0 (Approved) Technical Specification 2.0 (Under Review) Is it a standard? The Open Group’s ArchiMate Forum – Stewards of the ArchiMate standard What about the license? Capgemini is an ArchiMate Forum member ArchiMate Forum members have commercial license to use it for consulting engagements

ArchiMate – Concepts

Technical Infrastructure ArchiMate Framework Products & Services Business Information Behavior Business Functions Organisation Information Processes Application Data Applications Technology Technical Infrastructure Structure

ArchiMate Concept

ArchiMate Structure - Services Customer External business service Business Internal business service External application service Application Internal application service External infra. service Technology Internal infra. service

ArchiMate Structure - Layers Business Layer - Offers products and services to external customers, which are realized in the organization by business processes performed by business actors Application Layer - Supports the business layer with application services which are realized by (software) applications. Technology Layer - offers infrastructure services (e.g., processing, storage, and communication services) needed to run applications, realized by computer and communication hardware and system software. Generic Metamodel For Each Layer Internal External Information Behavior Structure

Metamodel – Business Layer

Language Notations

Business Layer - Sparx Example

Metamodel – Application Layer

Metamodel – Technology Layer

ArchiMate – Viewpoints

Basic ArchiMate Viewpoints Introductory Viewpoint Organization Viewpoint Actor Co-operation Viewpoint Business Function Viewpoint Business Process Viewpoint Business Process Co-operation Viewpoint Product Viewpoint Application Behavior Viewpoint Application Co-operation Viewpoint Application Structure Viewpoint Application Usage Viewpoint Infrastructure Viewpoint Infrastructure Usage Viewpoint Implementation and Deployment Viewpoint Information Structure Viewpoint Service Realization Viewpoint Layered Viewpoint Landscape Map Viewpoint

Actor Co-Operation Viewpoint Layered View Point Stakeholders Enterprise, process, and domain architects Concerns Relations of actors with their environment Purpose Designing, deciding, informing Abstraction Level Details Business layer Aspects Structure, behavior

Actor Co-Operation Viewpoint

Layered Viewpoint Layered View Point Stakeholders Enterprise, process, application, infrastructure, and domain architects Concerns Consistency, reduction of complexity, impact of change, flexibility Purpose Designing, deciding, informing Abstraction Level Overview Layer Business layer, application layer, technology layer Aspects Information, behavior, structure

Layered Viewpoint – Sparx Example

Business Process View Point Stakeholders Process and domain architects, operational managers Concerns Structure of business processes, consistency and completeness, responsibilities Purpose Designing Abstraction Level Detail Layer Business layer  Aspects Behavior

Business Process View Point – Sparx Example

Infrastructure View Point Business Process View Point Stakeholders Infrastructure architects, Operational Managers Concerns Stability, security, dependencies, infrastructure costs Purpose Designing Abstraction Level Detail Layer Technology Aspects Behavior, Structure

Infrastructure View Point – Sparx Example

Application Landscape View Point Baseline Application Model Target Application Model

ArchiMate Resources ArchiMate 1.0 Technical Specification ArchiMate Good Practices Sparx Enterprise Architect ArchiMate Presentations