How to Build TOGAF Architectures With System Architect (2).ppt

© 2015 IBM Corporation
DAD-5869 --TOGAF Workshop
How to Build TOGAF
Architectures
With System Architect
Lou Varveris
WW Community of Practice Lead for EA

• Lab Intro
• TOGAF Preliminary Stage
• Business Architecture
• Business Service Layer
• Information Systems Architecture
• Application Portfolio Management
• Analysis
Agenda

The NEED for Enterprise Architecture
• Customer quote (paraphrased):
• ‘We get asked, on a regular basis -- usually at the
last minute -- for artifacts that describe the business.
• The information is:
– Served up in Powerpoints and Excel spreadsheets
– Assembled in a scramble
– There is no correlation between the artifacts
– We don’t know where the documents came from,
who owns them, how reliable the information is, nor
what it doesn’t show, etc’
• Need a delivery mechanism for this
information so it is served up in a
self-serve manner

The NEED for Enterprise Architecture
• Customer quote (paraphrased):
• ‘With disruptive technologies, such as the cloud and
mobile – the EA team – even at a formerly staid
Health Care company – is being put in the
spotlights (or headlights?)
• CEO wants to know:
– How can company react to demand for mobile and
cloud technologies, and utilize these technologies for
advantage
– What are the solution alternatives, and cost
– What is impact to current business
– What is the risk to current business
• CEO wants the information ASAP

Reference
Models
EA Operations Center
EA
Governance
Establish Sources of Record
Transition
Planning &
Roadmaps
Project
Prioritization
& Planning
These are the things we should do
These are our
roadmaps
Harvest
Enterprise Architecture
Core Business
Processes
Apps
Data
Security Tools
Disparate Spreadsheets Multiple Data Sources
Leverage what
everyone else is doing
Cause-effect Analysis,
Heatmaps, Business
Analytics & Dashboards
Clean up sources of record
Harvest
SA/Pub,
SA/XT,
SA/DM
Solution
Design
CMDB
tools
sniffing
network
Business
Capabilities
Infrastructure
Apps
Data
Harvest
Standards
databases
APM tools

Content Framework
• Core
Concepts
• Extensions
Core Services
Data
Modeling
Motivation Governance
Process
Modeling
Infrastructure
Consolidation
Core

Architecture Development Method (ADM) -- Phases
Application
Architecture
•Application and User Location
Diagram
•Application Communication
Diagram
•Application Interaction Matrix
•Application Migration
•Application Portfolio Catalog
•Interface Catalog
•Process/System Realization
Diagram
•Role/System Matrix
•Software Distribution Diagram
•System Use-Case Diagram
•System/Function Matrix
•System/Organization Matrix
Data Architecture
•Class/Entity Relation Diagram
•Data
•Data Dissemination Diagram
•Data Entity/Business Function
Matrix
•Data Entity/Data Component
Catalog
•Data Migration Diagram
•Data Security Diagram
•System/Data Matrix
Architecture Vision
•Stakeholder Management
Approach
•Stakeholder Map
•Stakeholder Map Matrix
•Stakeholder Position Matrix
•Value Chain Diagram
Technology
Architecture
•Environments and Locations
Diagram
•Network Concept Diagram
•Platform Decomposition Diagram
•System/Technology Matrix
•Technology Portfolio Catalog
•Technology Standards Catalog
Preliminary Phase
•Principles Catalog
Business Architecture
•Actor/Role Matrix
•Business Footprint Diagram
•Business Interaction Matrix
•Business Service Information
Diagram
•Business Service/Function Catalog
•Business Use-Case Diagram
•Contract/Measure Catalog
•Driver/Goal/Objective Catalog
•Event Diagram
•Functional Decomposition Diagram
•Goal Objective Service Diagram
•Location Catalog
•Organization Decomposition
Diagram
•Organization Unit/Actor Catalog
•Process Flow Diagram
•Process/Event/Control/Product
Catalog
•Product Lifecycle Diagram
•Role Catalog
Opportunities &
Solutions
•Project Context Diagram

Migration Planning
•Focal Point
•Gather priorities for projects
and opportunities
•Business Value Analysis
•Roadmapping
Opportunities &
Solutions
•System Architect
•Gap analysis
•Impact analysis
•Risk Analysis
•Cost Analyis
..beyond identifying solutions
Architecture Change
Management
•Rational Change
•Log & Manage change
requests
•System Architect
•Carry out governed changes
Implementation &
Governance
•System Architect
•Deployment Modelling
•EA Compliance Reviews
•DOORS
•Gather detailed requirements
•RSA
•Build Detailed Designs

How EA
• Establish Vision of EA & Stages of
Success
• Start Small – Establish Project
where you can establish deadline
and ROI
• Grow the EA
– Show value in analytics
– Show value in cleaning up sources of
record
– Show value in visibility
– “I want some of that”
– EA becomes systematic

TOGAF 9 Extended Content Metamodel

Perform Labs 1 & 2: TOGAF Preliminary Phase
• Lab 1
• Make sure SA & the Workshop Folder are Available
• Lab 2
• Create the EA Repository
• Establish the EA Metamodel

Metamodel Extended
• Disaster Recovery Properties
13
• Application
Portfolio Analysis
• Location Risk

Metamodel Extended
• Customer Facing
Process
14
• Strategic Value of
Functions

Business Architecture within Context of EA – TOGAF
• TOGAF Metamodel
• We want to
understand
1. Capabilities
2. Functions
3. Processes (that
orchestrate Functions)
4. Services (that
encapsulate Functions)
5. People (that own
Functions & Apps)
6. Applications (enabling
Services or Functions)
7. Information (data)
8. Technologies (used by
Applications & Services)
9. Locations (of Apps,
Technologies & People)
1
2
3
4
5
6
9
8
A
7

Functions, Processes, Services, Applications
• Function = something that an organization does.
• According to TOGAF, a function "delivers business capabilities
closely aligned to an organization, but not explicitly governed by
the organization."
• Process = how the organization performs a function.
• There are many cross function processes, and cross
organizational processes.
• According to TOGAF, a process "is a flow of interactions between
functions and services that cannot be physically deployed. All
processes should describe the flow of execution for a function and
therefore the deployment of a process is through the function it
supports;
• i.e., an application implements a function that has a process,
not an application implements a process."

• Follow the purple crayon:
• Function is realized by Process.
• Function is bounded by a Business
Service which may be automated
by an IS Service, which is further
implemented by an Application.
• In this workshop we are not
specifically modeling Business
Services or Information System
(IS) Services; we use the direct
relation between Function and
Application.

• From TOGAF spec:
• Function encapsulates
Business Service
• Business Service
encapsulates
Functions
• Business Service can
be performed by
Information System
(IS) Service
• IS Service part of
Application
Component

Reference
Models
Business Process Modeling (BPMN) Input to EA
RSA
Enterprise Architecture
Mobile Loans
Approval
Process
Delivery
Business Process
Modeling, Capturing
& Redesigning
Leverage what
everyone else is doing
Decision Making Platform:
Cause-effect Analysis,
Heatmaps, Business
Analytics & Dashboards
EA Transition Planning
EA Cockpit SA/Pub,
SA/XT,
SA/DM
Visio Models
•Import w SA-Visio Mapper Utility
BPMN Modeling in SA
BPMN Modeling in SA/XT
3.3.1
3.3.1
Solution
Design
System
Architect
IBM BlueWorksLive
3.3.2

Perform Lab 3.1: Business Architecture
• Lab 3.1
1. Import business Functions
2. Auto-Build Functional Decomposition Diagram
3. Add New Functions
4. Understand Function Owners

Functional Hierarchy & BPMN 2.0 Process Flows
Process Flow
Decomposition
A

SA/XT – Live BPMN Modeling on Web Browser
• Model on BPMN near-zero
footprint web interface
• Only JavaScript to enable
• Model and save directly in
SA repository
• Can use SA rich-client on
same repository at same
time
Storage
Collaboration
Query
Discovery
Administration:
Users, projects,
process
Best Practice Processes
Presentation:
Mashups
Future
IBM
Capabilities
Product
& Project
Management
Collaborative
Lifecycle
Management Engineering
& Software
Tools
Business
Planning &
Alignment
Your
existing
capabilities
3rd-Party
Jazz
Capabilities
Compliance
& Security
Storage
Collaboration
Query
Discovery
Administration:
Users, projects,
process
Presentation:
Mashups
Future
IBM
Capabilities
Future
IBM
Capabilities
Product
& Project
Management
Collaborative
Lifecycle
Management Engineering
& Software
Tools
Engineering
& Software
Tools
Business
Planning &
Alignment
Business
Planning &
Alignment
Your
existing
capabilities
Your
existing
capabilities
3rd-Party
Jazz
Capabilities
Compliance
& Security
SQL Server or
Oracle Database
System
Architect Server
Microsoft IIS
Server
System
Architect
System
Architect XT
OSLC
BPMN modeling in SA/XT
B

SA – Visio Integration through Mapper Utility
• SA-Visio Mapper Utility available for
free on DeveloperWorks
• Map any Visio diagram to System
Architect
• Mapper Utility reads Visio diagram
and provides side-by-side mapping
interface to user
Landscape diagram in Visio
Diagram imported into SA
C

IBM BlueworksLive
• Easy web interface
• Engage line of business users
in process discovery,
documentation, & simple
process automation
• Import/Export:
• Import Visio XML diagram
format (.vdx)
• Bidirectional support for BPMN
2.0 interchange
• Bidirectional support for XPDL
2.1
• Generate IBM Websphere
Business Modeler XML
(Version 7.0)
• Generate to Microsoft Excel
(.xls)
D

SA-BlueWorksLive Integration via BPMN 2.0 Interchange
 IBM BlueWorksLive to
SA via BPMN 2.0
Interchange
 Bi-directional
BPMN in BlueWorksLive
1
2 Export in
BlueWorksLive
5
3 Export Choices in
BlueWorksLive
BPMN model in SA after import
4 BPMN Import into SA
D

Use of Reference Models to Jump Start EA Effort
 IBM Is a member of the APQC.org,
and has helped develop several
industry process frameworks,
including:
Aerospace & Defense
Automotive
Banking
Broadcasting
Consumer Products
Electric Utilities
Petroleum Downstream
Petroleum Upstream
Pharmaceutical
Telecommunications
 Pre-established 5-layer process
framework can be import into
modeling tools
Example:
APQC
Process
Framework
for Banking
which IBM
helped
develop
E

Using APQC
• According to APQC's John Tessmer,
"The PCF was originally envisioned
and is still based on the premise that
it is a classification system or
taxonomy of business processes,
similar to how a dictionary
classifies words. The categorization
does not imply that organizations
structure their internal operations
according to the taxonomy; it merely
provides a facility to help define
processes so that they can be
understood and referenced in a
consistent manner. Similarly, a
dictionary won't instruct you in
proper grammar or sentence
construction — you would have to
refer to a style guide for that."

Perform Labs 3.2 and 3.3: Business Architecture
• Lab 3.2
1. Examine APQC Process Framework for Banking
• Lab 3.3
1. Model a Process Flow with BPMN 2.0
2. Utilize BPMN 2.0 Interchange to Import BlueWorks Flow
3. Link Processes with Functions they Orchestrate
4. Create Function/Process Parent/Child Navigation Links

Business Service
• A Business Service can be
manual or automated
• It provides governed interface to
access Functions
• It supports business Processes
• It can be implemented by an
Information System (IS) Service
-- a fully automated service,
similar to what the industry might
call a SOA service

FEA Services Reference Model (SRM)
• US Federal Enterprise Architecture (FEA) Service Reference Model
(SRM)
• Part of the Consolidated Reference Model
• Contains a taxonomy of all of the services performed by all agencies of
the United States government, as specified by the US Office of
Management and Budget (OMB).
• Agencies must show that any system they wish funded support a
service in the SRM
• The commercial industry has adopted the SRM as a guide to what their
business is doing/should be doing

Best Practice:
• After importing the SRM, the Enterprise Architect can delete
Business Services not used in the organization, and add
Business Services that are used.
• The SRM is used to jump start the EA effort

For this Workshop:
• Metamodel of the SRM we use in workshop is modified from
SRM provided by the US government.
• In workshop metamodel, decomposition property of the
Service definition has been utilized to provide hierarchy of
services.
• In the US government's SRM, the metamodel starts with
highest level Service Domain, then breaks down into Service
Type, and then Service Component (lowest level). The SA
FEA Reference model add-in allows you to import that SRM
(provided by the US government via an xml file on
whitehouse.gov), align your architecture with it, & produce
reports mandated by OMB

Perform Lab 4: Business Service Layer
1. Import Modified Version of FEA Services Reference Model (SRM)
2. Add Business Service to the Architecture

Logical vs Physical App Components (and Tech Components)
• Optional to model Logical Application
Components
• Example:
– Sales Licensing tool
– Web development tool
– Enterprise Architecture tool
• Enables better analysis
• Understand how many Process
Modeling tools you have
• Understand why a tool is being used
(Photoshop for Web Dev)
• In SA, Application Component
definition has toggle for “Physical”; if
not toggled, it is logical app
component
• Note in TOGAF metamodel, Logical
App Component not connected to
Logical Tech Component

 Application Component (Logical)
 Enterprise Architecture tool
 Requirements Management tool
 Software Design tool
 Change Management
 Collaborative Development tool
 Application Component (Physical)
 System Architect
 DOORS
 Rational Software Architect
 Rational Team Concert
Examples of Logical & Physical App & Tech Components
 Technology Component (Logical)
 Relational Database
 Operating System
 Mobile Operating System
 Web Browser Script Language
 Technology Component (Physical)
 Microsoft SQL Server database
 Windows
 Android
 JavaScript

Use of Application, Data, and Technical Reference Models
• Application, Data, & Process
Reference Models:
• Telecommunications Forum Telecom
Applications Map (TAM) of TMForum
– Used by Telecom & other
industries
– Also: SID – Standard Information
Database
– Also: eTom – Business Process
Framework
• IBM & System Architect are TMForum
Certified
– Encyclopedia provided prepopulated with
TAM, eTOM, & SID
– IBM provides Telecom Catalog Order
Management Solution – maps IBM
solutions to SID, eTOM, TAM
IBM Catalog Driven
Order Management
Solution
Mapping to SID
Mapping to eTOM

Perform Lab 5: Information Systems Architecture
• Lab 5
1. Import Spreadsheet of Physical Applications
2. Visualize Physical Application Interfaces
3. Import Pre-Built Explorer Reports & Analytic Collections
4. Visualize Application Interfaces
5. Add an Application
• Lab 6
1. Utilize TMForum TAM for Logical Application Reference Model
2. Map Logical to Physical Apps
3. Build Report for Functions, Logical Apps, Physical Apps
1. Generate Report to HTML
2. Generate Report to Grid
3. Generate ‘Partial’ Report
4. Model Data Flows between Logical Apps (Optional)

Report to HTML
• Functions, their
Logical
Applications, and
their related
Physical
Applications
41

Report to Grid
• Functions, their Logical
Applications, and their
related Physical
Applications
42

Application Portfolio Analysis & Management
• Assess Applications using APM tools
• Cost of application
• Invest, Divest, Maintain
• Dev bandwidth
• What are the business priorities?
• What is working well?
• What is unnecessary, redundant or
obsolete?
• Where can costs be cut?
• Query workforce – example: vote on
usefulness and usability of applications used

Application Portfolio Management
Set values for
assessment
Review financial
details

• Lab 7 instructions come after next section

• Use the architecture to answer questions:
• Budget Constraints
– If a System is retired, what Capabilities are affected?
– How many projects are underway to supply similar capabilities?
– If I want to field a new system, what other systems do I currently have that
are similar to it, based on functions they perform?
• Disaster Recovery
– If a System is put out of service, what Capabilities are affected?
• Risk
– If an operating system is changed, what Capabilities could be affected?
Gap Analysis and Cause-Effect Analysis

Cause-Effect
Analysis
Example: Traverse
relationships
Capability to
ActivityPartOfCap
ability to Activity to
ActivityPerformedb
yPerformer to
Performer

Cause-Effect Analysis
See what Systems enable what Capabilities, by
traversing Activities and System Functions

Cause-Effect Analysis
Isolation analysis – hide all lines and only show
how a single Capability is enabled

• Use the architecture to answer questions:
• Budget Constraints
– How can we reduce costs to meet budget constraints but still provide
needed Capabilities
– What are the costs associated with Activities and Systems that
support a Capability?
– Unintended effects of cost reduction – if we virtualize servers, what
Apps are affected; what Activities are affected; what Capabilities are
put at risk?
– Lots of ways to calculate costs: Activity Based Costing, Cost of
Purchased Systems, Maintenance, Manpower, etc
• Disaster Recovery
– What capabilities are at risk if different systems go down at certain
locations?
– Is there a disaster recovery plan in place for important systems?
Analytics and Heatmaps

• sgfsdfs
Example uses Activity Based Costing rolled up to System cost

Perform Lab 7: Application Portfolio Analysis
1. Import APM Information from APM tool
2. Perform Cause-Effect Analysis
3. Create Landscape View
4. Perform Heatmap Analysis

End of Current Workshop Exercises
• The Next Sections Are for Theory Only

TOGAF Metamodel Extensions for Infrastructure
• Metamodel Additions Needed to Model Application and IT
Portfolio to Version and Instance Level
Physical Application Component Instance
Physical Technology Component Type
Physical Application Component Version
<<Abstract>>
Configuration Item
<<Phy sical>>
Application Component
<<Phy sical>>
Technology Component
<<Logical>>
<<Logical>>
Operating Sy stem Instance
Physical Data Component
Architecture Building Block
Platform Service
IS Service
Logical Data Component Solution Building Block
Data Entity
Location
Vendor
Database Instance
Device Instance
Server Instance
deployed instance of
is extended by
is extended by
is realized by
has deployable version
hosted at
is implemented by
deployable version of
decomposes
implements
supplies
encapsulates
operates on
is realized by
encapsulates
supports
hosted at
provided by

• Configuration Item =
A physical device or
executable software
that is part of an
enterprise’s current
infrastructure.
• Is abstract
• Is instantiated by
• Physical Application
Instance
• Server Instance
• Database Instance
• Device Instance
Physical Technology Component Type
Physical Application Component Version
Physical Application Component Instance
<<Abstract>>
Configuration Item
<<Physical>>
Operating System Instance
<<Physical>>
Architecture Building Block
<<Logical>>
<<Logical>>
Physical Data Component
Logical Data Component Solution Building Block
Database Instance
Device Instance
Server Instance
Platform Service
Location
IS Service
Data Entity
Vendor
is extended by
is extended by
is realized by
has deployable version
hosted at
is implemented by
deployable version of
decomposes
implements
supplies
encapsulates
operates on
is realized by
encapsulates
supports
hosted at
provided by

 Application Component (Logical)
 Enterprise Architecture tool
 Requirements Management tool
 Software Design tool
 Change Management
 Collaborative Development tool
 Application Component (Physical)
 System Architect
 DOORS
 Rational Software Architect
 Rational Team Concert
 Physical Application Component Version
 System Architect 11.4.2.5
 DOORS 10.1
 RSA 8.0
 Physical Application Component Instance
 System Architect 11.4.2.5 License 1
 Technology Component (Logical)
 Relational Database
 Operating System
 Mobile Operating System
 Web Browser Script Language
 Physical Technology Component Type
 Microsoft SQL Server database
 Windows
 Android
 JavaScript
 Technology Component (Physical)
 Microsoft SQL Server 2008 R2
 Microsoft Windows 7
 JavaScript 4
 Database Instance
 SQL Server 2008 R2 Running Instance
 Operating System Instance
 Windows 7 Running Instance
 Device Instance
 Lenovo Laptop S/N 1234

TOGAF 9.1 Extensions for Infrastructure by IBM
59
Physical Application
Instance
Version
Operating System
Instance
Device Instance
Technology
Component (Physical)
Lenovo W510
SA 11.4.3.2 -- L1234
Lenovo W510 S#1234
Windows 7 – L1234
Application
Component (Phys)
SA 11.4.3.2
SA
Application
Component (Log)
EA Tool
Technology
Windows 7
Physical Technology
Component Type
Lenovo Laptop
Physical Technology
Component Type
Windows
Technology
Component (Logical)
Technology
Component (Logical)
Laptop
Operating System
Base TOGAF 9.1
IBM extensions for infrastructure

Simplified TOGAF 9.1 Extensions – SA 11.4.3.2
60
Instance
Version
Operating System
Instance
Device Instance
Technology
Lenovo W510
SA 11.4.3.2 -- L1234
Lenovo W510 S#1234
Windows 7 – L1234
Application
Component (Phys)
SA 11.4.3.2
SA
Application
Component (Log)
EA Tool
Technology
Windows 7
Physical Technology
Component Type
Lenovo Laptop
Physical Technology
Component Type
Windows
Technology
Component (Logical)
Technology
Component (Logical)
Laptop
Operating System
,<Operating System>
,<Device>
Base TOGAF 9.1
IBM extensions for infrastructure

61
Tivoli Application Dependency Discovery Manager (TADDM)
 Application Mapping with
Dependencies
– Agent-less and Credential-free
– Discover interdependencies
between Applications,
middleware, servers and
network components)

Tivoli Application Dependency Discovery Manager (TADDM)

System Architect – TADDM Integration
 TADDM produces XML
output file
 SA-TADDM Integration
provides VBA integration
that utilizes XML Mapping
file to import TADDM info
into SA definition/property
set
TADDM Export
SA-TADDM
Mapping File
SA-TADDM
Integration in
SA

Perform Lab 8: Infrastructure Analysis
1. Import Infrastructure Info from CMDB tool
2. Create Heatmap

Notices and Disclaimers
Copyright © 2015 by International Business Machines Corporation (IBM). No part of this document may be reproduced or
transmitted in any form without written permission from IBM.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM.
Information in these presentations (including information relating to products that have not yet been announced by IBM) has been
reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM
shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY,
EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF
THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT
OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the
agreements under which they are provided.
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without
notice.
Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are
presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual
performance, cost, savings or other results in other operating environments may vary.
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products,
programs or services available in all countries in which IBM operates or does business.
Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not
necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither
intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.
It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal
counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s
business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or
represent or warrant that its services or products will ensure that the customer is in compliance with any law.

Notices and Disclaimers (con’t)
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products in connection with this
publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to
interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
The provision of the information contained herein is not intended to, and does not, grant any right or license under any
IBM patents, copyrights, trademarks or other intellectual property right.
• IBM, the IBM logo, ibm.com, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document
Management System™, Global Business Services ®, Global Technology Services ®, Information on Demand,
ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™,
PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®,
pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®,
urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of
International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and
service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on
the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

Thank You
Your Feedback is
Important!
Access the InterConnect 2015
Conference CONNECT Attendee
Portal to complete your session
surveys from your smartphone,
laptop or conference kiosk.

How to Build TOGAF Architectures With System Architect (2).ppt

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie How to Build TOGAF Architectures With System Architect (2).ppt

Ähnlich wie How to Build TOGAF Architectures With System Architect (2).ppt (20)

Mehr von StevenShing

Mehr von StevenShing (18)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

How to Build TOGAF Architectures With System Architect (2).ppt