TOGAF 9 Fundamental: 3. TOGAF ADM

Slides:



Advertisements
Similar presentations
Software Engineering: Research Romi Satria Wahono
Advertisements

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.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
The Open Group Architecture Framework (TOGAF) Version 7.
TOGAF 9 Fundamental: 3. Core Concepts
TOGAF 9 Fundamental: 5. ADM Introduction
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
The Use of Zachman Framework Primitives for Enterprise Modeling
BPMN Fundamentals: 4. BPMN Refactoring Romi Satria Wahono WA:
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.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
5. Project Scope Management
Tool support for Enterprise Architecture in System Architect Architecture Practitioners Conference, Brussels David Harrison Senior Consultant, Popkin.
Enterprise Architecture
TOGAF 9 Fundamental: 2. Basic Concepts
Developing Enterprise Architecture
An Introduction to the new features in TOGAF® 9
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
An Overview of TOGAF® Version 9.1
UML - Development Process 1 Software Development Process Using UML (2)
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
RUP Fundamentals - Instructor Notes
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
Architectures review for interoperability in e-health
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Rational Unified Process Fundamentals Module 4: Disciplines II.
TOGAF 9 Fundamental: 4. Key Terminology
The Challenge of IT-Business Alignment
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Knowledge Management: 2. Foundations Romi Satria Wahono WA/SMS:
BPMN Fundamentals: 2. BPMN Basic Concepts Romi Satria Wahono WA:
Chapter 7 Applying UML and Patterns Craig Larman
Apps.  Understand the list of applications or application components that are required, based on the baseline Application Portfolio, what the requirements.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Knowledge Management: 3. Solutions Romi Satria Wahono WA/SMS:
Copyright © The Open Group 2014 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2011 Lecture.
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
TOGAF 9 Fundamental: 2. TOGAF Concepts
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
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.
Basic Concepts Key Learning Points : The objectives of this chapter are as follows:  To provide an introduction to the basic Concepts of enterprise architectures,
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
BPMN Fundamentals: 5. BPMN Guide and Examples
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Process 4 Hours.
Michael J. Novak ASQ Section 0511 Meeting, February 8, 2017
What is Enterprise Architecture?
ARIS Extension Pack TOGAF April 2016
BPMN Fundamentals: 4. BPMN Refactoring
TOGAF 9.1 By: Samuel Mandebvu Sources: Primary Slide Deck
The Open Group Architecture Framework (TOGAF)
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
EA Framework TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture.
Presentation transcript:

TOGAF 9 Fundamental: 3. TOGAF ADM Romi Satria Wahono romi@romisatriawahono.net http://romisatriawahono.net/tfu WA/SMS: +6281586220090

Romi Satria Wahono SD Sompok Semarang (1987) SMPN 8 Semarang (1990) SMA Taruna Nusantara Magelang (1993) B.Eng, M.Eng and Ph.D in Software Engineering from Saitama University Japan (1994-2004) Universiti Teknikal Malaysia Melaka (2014) Research Interests: Software Engineering, Machine Learning Founder IlmuKomputer.Com PNS di PDII LIPI (1994-2007) Founder dan CEO PT Brainmatics Cipta Informatika

Course Outline Introduction TOGAF Concepts TOGAF ADM BPMN Overview UML Overview TOGAF Case Study

3. TOGAF ADM 3.1 ADM Iteration 3.2 ADM Process 3.2 TOGAF Artifacts

3.1 ADM Iteration

ADM Cycle The ADM consists of a number of phases that cycle through a range of architecture domains that enable the architect to ensure that a complex set of requirements is adequately addressed The ADM is applied iteratively throughout the entire process, between phases, and within them Throughout the ADM cycle, there should be frequent validation of results against the original requirements, both those for the whole ADM cycle, and those for the particular phase of the process. Such validation should reconsider scope, detail, schedules, and milestones Each phase should consider assets produced from previous iterations of the process and external assets from the marketplace, such as other frameworks or model

Three Levels of ADM Iteration Cycling around the ADM: The ADM is presented in a circular manner indicating that the completion of one phase of architecture work directly feeds into subsequent phases of architecture work Iterating between phases: TOGAF describes the concept of iterating across phases (e.g., returning to Business Architecture on completion of Technology Architecture) Cycling around a single phase: TOGAF supports repeated execution of the activities within a single ADM phase as a technique for elaborating architectural content

The Architecture Development Cycle The phases of the ADM cycle are further divided into steps For example, the steps within the Business Architecture phase are as follows

The Architecture Development Cycle In particular, a version numbering convention is used within the ADM to illustrate the evolution of Baseline and Target Architecture Definitions, as follows:

3.2 ADM Process

3.3 TOGAF Artifacts

Architectural Artifacts: Preliminary Phase and Phase A ADM Phase Artifact Preliminary Phase Principles catalog Phase A Stakeholder Map matrix Value Chain diagram Solution Concept diagram

Architectural Artifacts: Phase B ADM Phase Artifact Phase B (Business Architecture) Organization/Actor catalog Driver/Goal/Objective catalog Role catalog Business Service/Function catalog Location catalog Process/Event/Control/Product catalog Contract/Measure catalog Business Interaction matrix Actor/Role matrix Business Footprint diagram Business Service/Information diagram Functional Decomposition diagram Product Lifecycle diagram Goal/Objective/Service diagram Business Use-Case diagram Organization Decomposition diagram Process Flow diagram Event diagram

Architectural Artifacts: Phase C ADM Phase Artifact Phase C (Data Architecture) Data Entity/Data Component catalog Data Entity/Business Function matrix Application/Data matrix Conceptual Data Diagram Logical Data Diagram Data Dissemination diagram Data Security diagram Data Migration diagram Data Lifecycle diagram

Architectural Artifacts: Phase C ADM Phase Artifact Phase C (Application Architecture) Application Portfolio catalog Interface catalog Application/Organization matrix Role/Application matrix Application/Function matrix Application Interaction matrix Application Communication diagram Application and User Location diagram Application Use-Case diagram Enterprise Manageability diagram Process/Application Realization diagram Software Engineering diagram Application Migration diagram Software Distribution diagram

Architectural Artifacts: Phase D ADM Phase Artifact Phase D (Technology Architecture) Technology Standards catalog Technology Portfolio catalog Application/Technology matrix Environments and Locations diagram Platform Decomposition diagram Processing diagram Networked Computing/Hardware diagram Communications Engineering diagram

Architectural Artifacts: Phase E dan Requirements Management ADM Phase Artifact Phase E Project Context diagram Benefits diagram Requirements Management Requirements catalog

Test Yourself Questions Complete the sentence: Phase H _____________ Prepares the organization for successful TOGAF architecture projects Develops Baseline and Target Architectures and analyzes the gaps Prepares and issues Architecture Contracts Ensures that the architecture responds to the needs of the enterprise All of these

Test Yourself Questions Which of the following is the final step in development of the four architecture domains? Conduct formal stakeholder review Create Architecture Definition Document Perform gap analysis Select reference models, viewpoints, and tools

Test Yourself Questions Which of the following version numbers is used by TOGAF as a convention to denote a high-level outline of an architecture? Version 0 Version 0.1 Version 0.5 Version 1.0

Test Yourself Questions Which one of the following does not complete the sentence: When executing the ADM, the architect is not only developing a snapshot of the enterprise, but is also populating the ___________________ Architecture Repository Architecture Capability Framework Enterprise Continuum Foundation Architecture

Test Yourself Questions Which of the following statements does not describe the phases of the ADM? They are cyclical. They are iterative. Each phase refines the scope. Each phase is mandatory. They cycle through a range of architecture views.

Test Yourself Questions Which one of the following best describes a reason to adapt the ADM and take a federated approach? The maturity of the architecture discipline within the enterprise The use of the ADM in conjunction with another enterprise framework The ADM is being used by a lead contractor in an outsourcing situation The enterprise is very large and complex

Test Yourself Questions Which of the following are the major information areas managed by a governance repository? Foundation Architectures, Industry Architectures, Organization-Specific Architectures Standards Information Base, Architecture Landscape, Governance Log Reference Data, Process Status, Audit Information Application Architecture, Business Architecture, Data Architecture

Test Yourself Questions Which of these is not considered a dimension to consider when setting the scope of the architecture activity? Architecture Domains Breadth Depth Data Architecture Time Period

References Rachel Harrison, Study Guide TOGAF® 9 Foundation 2nd Edition, The Open Group, 2011 Rachel Harrison, Study Guide TOGAF® 9 Certified 2nd Edition, The Open Group, 2011 Open Group Standard, TOGAF® Version 9.1 (G116), The Open Group, 2011 Open Group Standard, TOGAF® Version 9.1 – A Pocket Guide (G117), The Open Group, 2011 Daniel Minoli, Enterprise Architecture A to Z: Frameworks, Business Process Modeling, SOA, and Infrastructure Technology, Taylor & Francis, 2008 Jon Holt and Simon Perry, Modelling Enterprise Architectures, The Institution of Engineering and Technology, 2010 Alan Dennis et al, Systems Analysis and Design with UML 4th Edition, John Wiley and Sons, 2013