You are on page 1of 328

!

" #

SAP AG 2008 © SAP AG 2008

ARIS Toolset for SAP Enterprise Architecture Framework


Version 72
Material number 50088193
$ % &

Copyright 2007 SAP AG. All rights reserved.


No part of this publication may be reproduced or transmitted in
any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed
without prior notice.

SAP AG 2007

Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System
z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER,
POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM
Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks
of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world. All other product and service names
mentioned are the trademarks of their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced,
copied, or transmitted in any form or for any purpose without the express prior written permission of
SAP AG.
This document is a preliminary version and not subject to your license agreement or any other
agreement with SAP. This document contains only intended strategies, developments, and
functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course
of business, product strategy, and/or development. Please note that this document is subject to change
and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the
accuracy or completeness of the information, text, graphics, links, or other items contained within this
material. This document is provided without a warranty of any kind, either express or implied, including
but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-
infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect,
or consequential damages that may result from the use of these materials. This limitation shall not apply
in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over
the information that you may access through the use of hot links contained in these materials and does
not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-
party Web pages.
Unit 1 - Introduction to SAP EAF with ARIS

SAP AG 2008

© SAP AG SOA230 1-1


Unit 1 - Overview of SAP Enterprise Architecture Framework
Unit 1 – Introduction to ARIS

Unit 2 – Architecture Vision

Unit 3 – Business Architecture

Unit 4 – Application Architecture

Unit 5 – Data Architecture

Unit 6 – Technology Architecture

Unit 7 – Summary

SAP AG 2008

Unit 1 will give an overview of the SAP EAF, the metamodel and the TOGAF ADM.
It is assumed students will have already attended the SOA200 – SAP Enterprise Architecture
Framework course; only a refresher overview is given.
Unit 1 will also give an introduction into ARIS as an enterprise modeling and analysis platform and
framework. We will also introduce the basic features of the platform.

© SAP AG SOA230 1-2


SAP Enterprise Architecture Resource Base
Framework extensions Extensions

Released to the Open Group


Released to the Open Group

Usage Guidelines SAP Business


Reference Models
Architecture
Content
Development
Metamodel
Method
SAP Technology
Templates, Examples and Case Reference Models
Studies

SAP Mapping Extensions

SAP Tooling Extensions


SAP Content SAP Implementation
EA Modelling Tools
Tools Tools

TOGAF Architecture TOGAF


Development Method Resource Base

SAP AG 2008

This slide captures the framework in a very concise way and what it actually contains
Basically, our framework is built with TOGAF as a foundation and contains a set of extensions.
SOA200 goes through each of these extensions in detail.

© SAP AG SOA230 1-3


Usage Guidelines Reference Content
Framework tailoring
Engagement Initiation SAP Business Maps
Using EA to implement SOA SAP-TOGAF TRM
Service Contracts Reference Model
Business Capability Assessment
Technology Capability Assessment
SAP Enterprise Architecture Resource Base SAP Product Availability
Matrix
IT Governance Impact Assessment Framework extensions Extensions

Released to the Open Group


Released to the Open Group

Solution Architecture Scoping


Glossary
Usage Guidelines SAP Business
Metamodel
Architecture metamodel,
Reference Models aligned with TOGAF terms
Architecture
Content Defined set of architecture
Development catalogs, views and matrices
Metamodel
Method
SAP Technology SAP-Specific Mappings
Templates, Examples and Case Reference Models SAP Enterprise Architecture
Framework terminology to SAP
Studies terminology mapping
SAP product to TOGAF TRM
mapping
SAP Mapping Extensions SAP Enterprise Architecture
Framework method to SAP
method mapping
SAP Tooling Extensions SAP Glossary

SAP Content SAP Implementation SAP Tool Guides and Integration


EA Modelling Tools
Architecture MethodTools Tools and Examples
Case Studies IDS-Scheer / ARIS Implementation of
Iterative architecture process Case studies from real-world SAP Framework
extending TOGAF ADM architecture engagements Tool Guide for Solution Composer, Service
Worksheet for each architecture
TOGAF Architecture TOGAF
“FASST case study” worked example Marketplace, Roadmap Composer,
phase identifying inputs, steps and Development Method Resource Base
Examples for all defined architecture Solution Manager, Quick-Sizer, System
outputs views and matrices Landscape Directory, Enterprise Services
Repository
Narrative for each architecture phase Candidate Architecture Principles
explaining how to conduct the phase

SAP AG 2008

So what does SAP EAF contain?


Let us first focus on Framework extensions
Here it has an Architecture development method, as set of usage guidelines, an explicitly defined
content metamodel and a host of templates, examples and a case study
Next moving on to Enterprise Continuum extensions, the framework offers both business and
technology reference models
SAP mapping extensions - It contains mapping to SAP content at various levels namely terminology
mappings, method mappings, TRM mappings to SAP product suite and finally a SAP Glossary
Finally there are a number of SAP tooling extensions namely content tools, implementation tools and
modeling tools. We will go through them in detail in subsequent sections.
In this course, we will be concentrating on the ARIS Tool Implementation of the SAP EAF.

© SAP AG SOA230 1-4


! " #$

TOGAF ADM provides a number of


architectural phases (e.g. Business Prelim:
Framework and

Architecture, Information Systems Principles

Architecture) in a cycle
an overall process template for architectural
activity
A.
TOGAF ADM provides a narrative of each Architecture

architecture phase, describing the phase in


Vision
H.
Architecture
B.
Business
terms of objectives, approach, inputs, steps Change
Management Architecture

and outputs.
an informal definition of the architecture
content structure and deliverables
G. C.
TOGAF ADM provides cross-phase Implementation
Governance
Requirements
Management
Information
Systems

summaries on requirements management,


Architectures

phase inputs and phase outputs


TOGAF ADM provides a cross-phase section
explaining the concept of architecture F.
Migration
D.
Technology
building blocks, which allow the Enterprise Planning
Architecture

to be segmented into re-usable components. E.


Opportunities
and Solutions
For example, creation of a Portal application
building block that could be used to support
architecture definition for many specific web
applications
SAP AG 2008

Let us do a quick recap on TOGAF


TOGAF ADM is a multi-phased method and it explicitly defines 4 distinct architecture domains
With in each phase, it has a narrative that is made up of objectives, approach, inputs, steps and outputs
TOGAF also addresses “requirements management” which serve as cross-phase touch point and
inputs/outputs between phases
TOGAF introduces a concept of architecture building blocks that allow the enterprise to be segmented
into re-usable components enabling a better analysis of the enterprise

© SAP AG SOA230 1-5


% & ' ! "

TOGAF is designed to cope with all


situations, and designed to be extended Prelim:
Framework and

where necessary Principles

There are justifiable “gaps” :


Enterprise vs. Solution Architecture
One size fits all process
A.
Vague concept and product definitions Architecture
Vision
H.
B.
TOGAF is closer to an abstract template for Architecture
Change Business

architecture engagements Management Architecture

A more concrete product that is suitable for


immediate, direct usage on architecture
engagements where service-orientation G.
Requirements
C.
Information
Implementation
and/or packaged solutions are a given is Governance Management Systems
Architectures

needed

F. D.
Migration
Technology
Planning
Architecture

E.
Opportunities
and Solutions

SAP AG 2008

But TOGAF clearly has some gaps…


It is meant to be a meta-Framework which is designed to be customized or extended where necessary
It doesn’t differentiate between Enterprise Architecture and Solution Architecture
The process is very generic, the concept is vague and product definitions are not explicit
It is an abstract template
To support Packages & packaged services implementation, a more concrete framework is needed

© SAP AG SOA230 1-6


$ (
) ( *

Architecture Context Underlying the catalogs,


matrices and views is a
Strategic Context
structured content metamodel.
This can be implemented in a
tool, or used as a checklist to
support less formal modeling
Architecture Requirements Change Roadmaps
approaches
The SAP EAF metamodel is
Business Information System
derived as much as possible
from TOGAF terminology
Motivation
IAF concepts have been added
to fill perceived gaps in the
Application Data
Technology TOGAF narrative (e.g. Contracts,
Organization
Information Components,
Logical and Physical
abstraction, etc)
Function
An informal Conceptual, Logical,
Physical abstraction layering is
used in the Information Systems
Implementation Governance Assets
and Technology domains.
Business architecture is layered
according to motivation,
organization and function

SAP AG 2008

This slide depicts the content metamodel at the highest level of abstraction and captures all aspects of an
enterprise, both architectural and non-architectural
The metamodel can be thought of three stripes or layers with the top and the bottom stripe depicting the
non-architectural aspects of an enterprise
The middle stripe contains the architectural entities of an enterprise
Looking at the architecture context, it contains “strategic context” which forms the input to the
architectural entities, “requirements” that are generated by developing the EA and identifying the gaps
between “As-is” and “to-be” architectures and the “Change roadmaps” which identify the initiatives,
their priority and the sequence of those initiatives
The business architecture attempts to model the motivational elements of the enterprise, how the
enterprise is organizationally structured and what business capabilities it currently possesses
Information Systems artifacts tend to model the IT systems which include both applications and data (as
classified by TOGAF ADM)
Technology artifacts capture procured technology assets that are used to implement, deploy and realize
Information System solutions (including the HW/SW and Communication protocols)

© SAP AG SOA230 1-7


$ (

Architecture Context Underlying the catalogs,


Strategic Context matrices and views is a
Statements Capability and Maturity Tailored Business Principles , Architecture Architecture
of Work Assessments Architecture Method Objectives and Drivers Principles Vision structured content metamodel.
This can be implemented in a
Architecture Requirements Change Roadmaps

Transformation
tool, or used as a checklist to
Requirements Contraints Assumptions Gaps
Plans
Work Packages
support less formal modeling
approaches
Business Information System Technology

Motivation Application Data The SAP EAF metamodel is


derived as much as possible
Drivers Goals Objectives Measures Information
System Data Entities
Platform from TOGAF terminology
Services
Services
IAF concepts have been added
Organization to fill perceived gaps in the
Logical Logical Logical
TOGAF narrative (e.g. Contracts,
Organization Location Actor, Role Application
Components
Information
Components
Technology
Components
Information Components,
Logical and Physical
abstraction, etc)
Function

Business
Processes ,
Physical
Application
Physical
Information
Physical
Technology
An informal Conceptual, Logical,
Services,
Contracts,
Events, Controls ,
Products
Functions Components Components Components Physical abstraction layering is
Service Qualities
used in the Information Systems
and Technology domains.
Implementation Governance Assets

Standards Guidelines Specifications Business architecture is layered


according to motivation,
organization and function

SAP AG 2008

Getting to the next level of details, we can look at the individual elements of each one of the metamodel
entities
Go through Business, Info Systems and Technology architecture entities briefly….
EAF is built on TOGAF in collaboration with Capgemini and hence we have adopted IAF concepts to
augment EAF

© SAP AG SOA230 1-8


+

TOGAF provides very few examples of architecture content


Difficult to understand and visualize what the end product is
Difficult to train Enterprise Architects in the method
SAP EAF provides an integrated case study
Based on a well-known SAP Education Case Study
Used to test the SAP EAF during its development
Worked through examples of all the main architecture products
Customer Relations Warehouse Supply Chain Management
Legacy Custom Interface
e-Price Catalog Catalog Contract
CRM
RFC e-Procure- Authoring Personalization Management
SAP BW ment Service Service
http/TCP RFC
CRM

Sales & Marketing Backend Systems Spare Parts Management


http/TCP RFC
BEEST Custom Interface
Portal http/TCP
RFC
http/TCP
RFC RFC Product Config Customer
RFC Price Invoice Quota Contracts
BYB Custom Interface SAP VMS RFC Master Rules Master
mySAP
SAP R/3 SCM
RFC
RFC

DMS RFC

Dealer Landscape Catalog Catalog


BEEST Systems Comparison &
Custom Interface Search
Custom Interface ImpPrice Service Promotion
RNI Systems
Custom Interface

ImpDMS Custom Interface ImpSales ImpCRM

SAP AG 2008

The case study was intended to fulfill the shortcomings of TOGAF


TOGAF offers very few examples of architecture content
EAF has an integrated case study to illustrate the concepts of the Framework with a practical application
Serves as a test of EAF during its development
The case study contains examples of key architectural deliverables from each phase
We will see the case study implemented in ARIS in this course.

© SAP AG SOA230 1-9


, !- $

An automotive company founded in 1931


Founded by Dr Ferdinand Fasst
One of the world’s most profitable car manufacturers
11,668 employees
Products:
High performance sports cars made in Germany in the premium
segment
Differentiators: performance, design and quality
Operations:
Focus Areas: Design, Engine Production, Sales and Marketing
Component manufacturing and final assembly partly outsourced for
some models
FASST value added: 10%-20%
Strategic Business Areas :
“Aftersales” due to revenue potential (car service training and spare
parts delivery)
Other business areas: Consulting, Engineering, IT and Financial
Services to external customers
SAP AG 2008

This slide provides an overview of FASST Company

© SAP AG SOA230 1-10


! + !

Case Study has been put together using ARIS


Proves the SAP EAF
Proves the ARIS Reference Implementation
Ability to demonstrate the SAP EAF more interactively
Show stakeholders what is possible, and an example of what can be done
Case Study is not used as part of SOA200
but features heavily in SOA250 – SAP Enterprise Architecture Framework
Level II Certification

SAP AG 2008

The FASST case study has been modeled in ARIS (using IT Architect & Business Architect products)
The tool based modeling helps to demonstrate EAF more interactively
Note that the case study is not covered in SOA200.
It will however be referred to in this course SOA230.
It will be heavily featured in a follow on course - SOA250

© SAP AG SOA230 1-11


(
Business .
Structure Context Operation
Organisation Chart
View
Functional Decomposition
View
Use Case
View
Role
Catalog
Actor /
Role Matrix
Business Architecture
Location Process Flow View Views
Catalog
Business Footprint
View
Organisation /
Actor Catalog Matrices
Goal /Objective/
Service View
Catalogs
Driver / Goal / Process / Event / Control /
Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application . Application
Structure Context Operation
Architecture
System / Function
Matrix
Application Interaction
Matrix
Process / System
Realization View
Views
Role / System Software Engineering Matrices
View Application
Application Portfolio Matrix
Catalog
Software Distribution
Communication View
Catalogs
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data . Data Architecture


Structure Context Operation Views
Conceptual / Logical
ER View
Data Entity / Business
Function Matrix
Data Dissemination
View Matrices
Data Migration View
Data Lifecycle View Catalogs
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View
Technology
Technology .
Architecture
Structure Context Operation
Technology Standard System / Technology Platform
Decomposition View
Processing View Views
Catalog Matrix Mandatory View

Technology Portfolio Networked


Matrices
Catalog Optional View
Environments and
Computing /
Hardware View Catalogs
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

This diagram shows the flow of how artifacts in the SAP EAF are produced. These are made up of
catalogs, matrices and views.
We can use an enterprise architecture modeling tool, such as ARIS IT Architect, to help produce and
maintain these artifacts by building an enterprise model.

© SAP AG SOA230 1-12


Unit 1 - Overview of SAP Enterprise Architecture Framework
Unit 1 – Introduction to ARIS

Unit 2 – Architecture Vision

Unit 3 – Business Architecture

Unit 4 – Application Architecture

Unit 5 – Data Architecture

Unit 6 – Technology Architecture

Unit 7 – Summary

SAP AG 2008

Unit 1 will give an overview of the SAP EAF, the meta model and the TOGAF ADM.
Unit 1 will also give an introduction into ARIS as a enterprise modeling and amalysis platform and
framework. We will also introduce the basci features of the platform.

© SAP AG SOA230 1-13


(

SAP AG 2008

This slide shows how SAP EAF (previous slide) is represented in ARIS.

© SAP AG SOA230 1-14


, . (( / + (
BUSIN
ESS PR
Sales,
Purcha OCESS
se, Pro E
duction S
Pr , Logis
o tics …
C o ces
ntr s
o ll
ing
Pr
o
Str ces
CHANGE MANAGEMENT
a te s
gy

Pr
o
Im c e s
p le s CONTINUOUS IMPROVEMENT
me
nta
t io
n

sig s
COM

D e ces
Sarb PLIANC

n
Quali nes-Oxle E PRO
a

o
Pr
ty Mana yA C
ct, ES
g emen Risk &C SES
t… ontro
ARIS
l Man
ag emen
t,

Business Process Excellence


© 2005 by IDS Scheer AG. All Rights reserved.

SAP AG 2008

This is the IDS Business Process Excellence Lifecycle. It shows the lifecycle from process strategy,
process design, process implementation to process controlling.

© SAP AG SOA230 1-15


( -! ((+

ARIS ARIS
Controlling Platform Strategy Platform
ARIS PPM ARIS BSC Solution
ARIS Audit Manager ARIS Business Optimizer
… ARIS Business Simulator

ARIS
Platform

ARIS ARIS
Implementation Platform Design Platform
ARIS Business Architect
ARIS for SAP NetWeaver
ARIS Business Publisher
ARIS SOA Designer
ARIS IT Architect
ARIS Business Rules Designer
ARIS IT Designer
ARIS UML Designer
ARIS ArchiMate Modeler
ARIS BI Modeler


© 2007 by IDS Scheer AG. All rights reserved.

SAP AG 2008

IDS Scheer has developed solution filled Platforms in alignment with the Business Process Management
lifecycle.
Every phase of the Lifecycle is supported by multiple products of the ARIS Platform.
We will be working with ARIS Business Designer and ARIS Business Architect within the ARIS
Design Platform.
On this course, we will focus on how ARIS IT Architect has been used to support the SAP EAF.

© SAP AG SOA230 1-16


) ' + *

Strategy View Organizational View

Process View
Application View
Data View

Risk View

Product/ Service View

“Enterprise Architecture is about understanding all of the different


elements that go to make up the Enterprise and how those elements inter-
relate.”
(Derived from definition by „Institute for Enterprise Architecture Developments“)
SAP AG 2008

ARIS method stands for Architecture of Integrated Information systems. It is a framework/concept for
describing companies and business application systems.
Using the ARIS Concept and model types available in ARIS, you can represent business structure of a
company, application software or a procedure. This gives you the opportunity to comprehensively
document the organizational and procedural structure of your company or individual areas of your
company.
Organizational view
The organizational view presents the organizational units in a company (e.g. departments,
positions, and people) and the static relationships that exist between them.
Data view
The data view shows the data (information objects) in a company and the static relationships
that exist between them.
Function view
The function view presents the functions (processes) in a company and the static
super/subordination relationships that exist between them.

© SAP AG SOA230 1-17



Product view
The view describes the products and services to be generated in a company and the static
super/subordination relationships that exist between them.
Process view
The process view primarily shows the processes (process flows), i.e. the chronological and
logical sequence of business functions. In addition, the process view is used to model problems
relating to at least two of the "external" ARIS views.
When you look at any organization this framework allows to capture information from each perspective.
The outside views are static views, process view allows you to connect all of the static views, logic,
visions, and who does what with what information.
The ARIS house is a framework, not a methodology. This is methodology independent. ARIS has 144 +
model types. Most other tools have between 6-20 model types.
We can see that the ARIS method is similar in its intention to TOGAF and SAP EAF. A comparison of
the strengths and weaknesses of proprietary versus “open standard” frameworks is contained in
SOA200.

© SAP AG SOA230 1-18


0 + +(

Architecture is usually represented by means of


one or more “models” that together provide a
full description of the whole thing.
We use multiple views of something to enable
the architecture to be communicated to, and
understood by, the different stakeholders.
Just as a Building Architect might create wiring Plumbing
diagrams, floor plans and elevations to describe
different facets of a house to its different
stakeholders (electricians, owners, planning
officials)
So an Enterprise Architect might create physical
and security views of an IT system for example
stakeholders. Floor Plan

3-D Visualization Wiring


Landscaping
SAP AG 2008

An architecture is usually represented by means of one or more architecture models that together
provide a coherent description of the system's architecture. A single, comprehensive model is often too
complex to be understood and communicated in its most detailed form, showing all the relationships
between the various business and technical components. As with the architecture of a building, it is
normally necessary to develop multiple views of the architecture of an information system, to enable the
architecture to be communicated to, and understood by, the different stakeholders in the system.
For example, just as a building architect might create wiring diagrams, floor plans and elevations to
describe different facets of a building to its different stakeholders (electricians, owners, planning
officials), so an IT architect might create physical and security views of an IT system for the
stakeholders who have concerns related to these aspects.

© SAP AG SOA230 1-19


1 (

Executive CxO

Architecture Context Programme


Management Office

Strategic Context
Line
Management

Architecture Requirements Change Roadmaps

Executive Business Information System

Motivation

Application
HR Line Technology Management
Management Organization Data Application

Procurement
Function Infrastructure
Management
Functional /
IT Service Business
Business
Management Domain
Process
Experts
Experts Implementation Governance Assets
Data / Voice
Communications

Stakeholder Types

QA/ Standards Product Enterprise Technical


Groups Specialists Security Specialists
Corporate System End - User Project
Functions Operations Organization Organization

SAP AG 2008

SAP EAF identifies the stakeholders of architecture, their typical interest in architecture and their
“view” of the different architecture domains
So we know who the key groups are, and are good idea of what “views” they will be interested
The metamodel enables us to define what is in each view for consistency – so we ensure all aspects of
the model are validated and communicated

© SAP AG SOA230 1-20


1 (

Executive CxO

Architecture Context Programme


Management Office

Strategic Context
Line
Management

Architecture Requirements Change Roadmaps

Executive Business Information System

Motivation

Application
HR Line Technology Management
Management Organization Data Application

Procurement
Function Infrastructure
Management
Functional /
IT Service Business
Business
Management Domain
Process
Experts
Experts Implementation Governance Assets
Data / Voice
Communications

Stakeholder Types

QA/ Standards Product Enterprise Technical


Groups Specialists Security Specialists
Corporate System End - User Project
Functions Operations Organization Organization

SAP AG 2008

SAP EAF identifies the stakeholders of architecture, their typical interest in architecture and their
“view” of the different architecture domains
So we know who the key groups are, and are good idea of what “views” they will be interested
The metamodel enables us to define what is in each view for consistency – so we ensure all aspects of
the model are validated and communicated

© SAP AG SOA230 1-21


2 ( ( / + ( $ 2

Plan / Design Build Run

Discovery Evaluation Implementation Operations


S AP E nt erp rise Architectu re Reso urce Base
Framework extensions Extensions
Released t o the Open Grou p

Release d to the Open Gro up

Usage Guideli nes SAP Business

SAP Enterprise Architecture Framework


Reference Models
Archi tecture
Content
Developm ent
M ethod Metamod el
SAP Te chnol ogy
Tem pl ates, Examples and Case Reference Models
Studies

S AP M apping E xtensions
S AP Tooling Ext ensions
SAP Content SAP Im plementation
E A Mod ell in g Too ls
Tools Tools

T O GAF Arch itec tur e T OG AF


D evelo pme nt Metho d Resou r ce Ba se

SAP Solution Composer

SAP Enterprise Modeling by IDS Scheer (Re-branded ARIS)

ASAP / GlobalASAP

SAP Scenario and Process Content Repository

SAP Enterprise Service Workplace

SAP Product Availability Matrix

SAP AG 2008

The SAP EAF is supported by a number of tools to help architects developed their enterprise
architecture. This is covered in more detail in SOA200.
However, here we can see how the SAP Enterprise Modeling offering from IDS Scheer covers the end-
to-end lifecycle covered by the SAP EAF.

© SAP AG SOA230 1-22


( $ ' - '
$ (
Process Configuration Modeling
Synchronize ARIS process models with SAP Solution Manager project & SAP
reference configuration content
Extending the Business Level Model to a Process Configuration Model
Use the Process Configuration Model for business configuration

Company View
Business
Processes

SAP Solution Manager


SAP NetWeaver

Component
View

SAP XI

Integration
Scenario

D
A Integration
E
Process

Workflow
Non- SAP SAP SAP xApp

by SAP NetWeaver
powered by
powered NetWeaver

SAP AG 2008

ARIS can synchronize process models with SAP Solution Manager project & SAP reference
configuration content
This allows for extending the Business Level Model to a Process Configuration Model
The Process Configuration Model is used for business configuration

© SAP AG SOA230 1-23


+ 3 456 ( $ '

SAP
Component

Objects synchronized:
SAP Scenarios
SAP Processes
SAP Process Steps
Transaction
Transactions
SAP System Landscape
SAP Process Step
SAP AG 2008

The following objects can be synchronized between ARIS and SolMan:


SAP Scenarios
SAP Processes
SAP Process Steps
Transactions
SAP System Landscape
These objects are synchronized both ways between the two tools. Depending on the project approach
they can be created and maintained in both tools.
These artifacts can be used to help the Enterprise Architect build up their Business and Application
Architecture.

© SAP AG SOA230 1-24


# ( ( $ ' 6

Documentation Link

Objects downloaded:
Organizational Units
Master Data
Documentation Links

SAP Organizational Unit


SAP Master Data
SAP AG 2008

During and after the project relevant information can be loaded back into ARIS for further
documentation. E.G. the selected master data elements can be used in ARIS for further data modeling.
The SAP related Organizational Units can be leveraged for a mapping process in ARIS.
Besides all general SAP and project documentation links can be transferred to ARIS.

© SAP AG SOA230 1-25


/ ' , # '

To launch ARIS Business Designer:


Alternative 1: Start Programs ARIS Platform ARIS
Design Platform ARIS IT Architect 7.0

Alternative 2: The program icon

The Login Wizard is started.

SAP AG 2008

We will now look more specifically at the ARIS IT Architect tool.


To launch the ARIS application follow the shown path in the Start – Programs menu or click on the
program icon for ARIS IT Architect.

© SAP AG SOA230 1-26


/ ' % 3 / '' ' #,

Enter User Name and Password

Note: A user can change their own password using the following
pathway:
File Change Password.

SAP AG 2008

Enter user name and password


Each modeler should model using his own user name. The system user creates the relevant user name
and the associated password in ARIS Business Architect and notifies the modeler of this data.
If a user has forgotten his password, the system user can assign him a new password in ARIS Business
Architect without having to enter the old password.
Users can be assigned particular privileges (e.g. read, write, delete privileges for particular parts of the
database). These are also set up in ARIS Business Architect.

© SAP AG SOA230 1-27


/ ' % 3 $ ( / ' '

1) Select the Method Filter

2) Select the DB Language

To change the filter you must log out of


NOTE
ARIS and then log back in.

3) Finish launches ARIS IT Architect and opens the selected DB

SAP AG 2008

In many projects, individual users are assigned only one method filter. IN this case, you will not need
the select filter step in the Log in Wizard. Always make sure your using the right filter.
1) Select method filter
Selecting a method filter means that only a selected part of the ARIS method is displayed in the tool
(different parts depending on the filter). This makes it easier for the modeler to handle the –
extensive – ARIS method, as only the methods that have previously been defined for the project are
displayed.
In projects, a user is often only assigned the method filter for that specific project. In this case, there
is no step "4) Select method filter". The filter is configured in ARIS Business Architect.
2) Select database language
The content of the ARIS database can be maintained and displayed in several languages. The type
and number of the languages displayed depends on the server installation.
3) Launch ARIS Business Designer
Click Finish

© SAP AG SOA230 1-28


, 1 $ (

Did you know that……?


Provides the user a list of
ARIS “Tips of the Day”.

Open the last Model edited


Allows you to quickly open the
most recent models opened.

How do you want to start


ARIS next time?
Using the drop down list -
allows you to choose the ARIS
view to be displayed upon
opening ARIS.

SAP AG 2008

In the ARIS home module you will find ‘Tips of the day’, a list of last used models and data.
Here you can also define the module where you want to start next time you logon.

© SAP AG SOA230 1-29


! $ (

Module Bar

Home contains some fundamental information:


Quick start, start screen setting, tips, login data

Explorer is used to manage the DB server and ARIS databases


(incl. groups, models, objects).

Designer is used for graphical modeling.

The Matrix Editor can be used to set up relationships between


different objects in the form of a matrix independent of the model
type.

SAP AG 2008

The ARIS IT Architect user interface makes the new role and view concept clear. The role-specific
functionality is provided in precisely defined areas. The required functionality can be accessed
depending on the roles. The "framework" is provided by the Home, Explorer, Designer, Matrix Editor,
Administration and Script Editor Modules. This division results in smaller popup menus and toolbars
adapted for the specific roles, ensuring that the software is more convenient to use.
The software automatically switches between the modules when a higher-level functionality is used. For
example, opening a model using the "Explorer" module automatically activates the "Designer" module.
In the Explorer tree in the Designer module, the group in which the open model is saved is expanded.
An integrated help function (Embedded Help) is provided across all modules. For all dialog boxes and
wizards, pressing the F1 key and clicking on "Help" shows a description of the different elements of the
dialog box or wizard.

© SAP AG SOA230 1-30


! $ (

Module Bar

Administration & Script Editor are


only available in ARIS IT Architect

Administration is used to manage the servers and ARIS databases:


(configuration, user and access privilege management etc.)

Script Editor is used to create evaluation scripts in Java Script:


(for reporting, semantic checks, macros, transformations)

SAP AG 2008

Only business architect has administration and script editor.

© SAP AG SOA230 1-31


! # ' $ (
The ‘Modules’,
‘Navigation’, and
Modeling is carried out in the Designer module. ‘Properties’ boxes should
be checked to enable and
Navigation Bar
disable bars.

Properties Bar Toolbar


The modeling toolbar
offers the object
symbols that you
need to create your
models.

Module Bar

Designer/Modelling Window

SAP AG 2008

A model can be opened in both the Designer and Explorer modules.


When a model is opened in Explorer, the software automatically switches to Designer and displays the
model in the modeling window.
The slide show the diffrent elements of the designer window:
Modelling window to compose the models
Toolbar presents the object icons to be used in the selected model type
Navigation bar allows the navigation in the explorer tree
Properties bar allows for acessing model and object properties
Module bar allows to swith to a diffren ARIS module.

© SAP AG SOA230 1-32


" ( ( '

General client settings are made using View Options.

SAP AG 2008

Some of the modeling options / conventions specified in the project preparation should be set before
starting to create the model.
These general settings are made under View -> Options. They apply to the client.

© SAP AG SOA230 1-33


' $ ( '

Settings in line with


project conventions

TIP
Before modeling, the basic settings specified in the project conventions
are made. This ensures that models and project standards will follow the
guidelines defined in the project preparation phase.

SAP AG 2008

Settings made for the modeling components under "Model – For New Models" only apply to those new
models that are created in the database after changing these options.
KEY POINT: Settings made for the modeling components under "Model – For New Models" only apply
to those new models that are created in the database after changing these options.
Before modeling, the basic settings specified in the project conventions are made.
This ensures that project standards defined in the project preparation phase are used in the modeling.

© SAP AG SOA230 1-34


7 $ (

The settings that influence the appearance of the (new) models are
made under Representation.
Attention: There is NO effect on existing models!

SAP AG 2008

For new models to be created you can make some optional settings here.
You can select a graphical template here.
The text attributes in symbol define how text is represented on an object in a model. What settings are
possible is shown on the next slide.

© SAP AG SOA230 1-35


! . 8 + 8 (

Text over and above the symbol Resize symbol


Advantages: Advantages:
Name of object can be read completely Name of object can be read completely
Manual line break gives maximum control Text fits into symbol
Disadvantages: Disadvantages:
Line of text may extend beyond the Different symbol sizes in model
margins of the symbol unsettled appearance

Multi-line text Single-line text


Advantages: Advantages:
Text does not extend beyond the margins Text fits into symbol
of the symbol Uniform appearance
Automatic line break Disadvantages:
Disadvantages: Text is not displayed in full if it does not fit
Text may not completely fit into symbol and onto one line
will be abbreviated
No hyphenation

SAP AG 2008

This slide shows the different settings of text attributes on a symbol and their meaning.

© SAP AG SOA230 1-36


! ( (

View Options Model For New Models Representation.

Click on Change

Select Template

SAP AG 2008

A template specifies the appearance of the models, e.g. background color of the model, appearance of
symbols (color, size etc.) and connections.
The template to be used in the project is selected using View -> Options -> Model -> For New Models -
> Representation.
Only existing templates can be selected. New, project-specific templates are created in ARIS IT
Architect.

© SAP AG SOA230 1-37


'

For Connections, you can set whether:


Connection ends are shown as right-angled or rounded
Bridges are used for crossing connections (30 recommended)
The Connection Settings should be made in line with the
project conventions.

SAP AG 2008

You can specify here how connections are shown in the designer module.

© SAP AG SOA230 1-38


" '

A Grid allows
Manual alignment of objects using the cursor keys
A more attractive visual layout of models, as the objects are
placed directly in the Grid
Check box to enable
the Grid

Enter Grid width

SAP AG 2008

A grid supports the modeler in creating a consistent and easy to read layout when creating models.
Therefore we recommend to always use the grid.
Grid width depends on the modeling standard of your organization but the recommended width is 5.

© SAP AG SOA230 1-39


+

This is the end of the 1st Unit


You should now understand SAP Enterprise Architecture Resource Base

Released to the Open Group

Released to the Open Group


Framework extensions Extensions
The basics of the SAP EAF. Usage Guidelines SAP Business
Reference Models
Architecture
Content
What ARIS stands for and Development
Method
Metamodel

what the ARIS framework is. Templates, Examples and Case


SAP Technology
Reference Models
Studies

The basic features of ARIS IT SAP Mapping Extensions


Architect. SAP Tooling Extensions

The next Unit explains the SAP Content


Tools
SAP Implementation
Tools
EA Modelling Tools

Architecture Vision. TOGAF Architecture TOGAF


Development Method Resource Base

SAP AG 2008

This is the end of the 1st Unit


You should now understand
The basics of the SAP EAF.
What ARIS stands for and what the ARIS framework is.
The basic features of ARIS IT Architect.
The next Unit explains the Architecture Vision.

© SAP AG SOA230 1-40


Unit 2 - Architecture Vision

SAP AG 2008

© SAP AG SOA230 2-1


Unit 1 - Overview of SAP Enterprise Architecture Framework
Unit 1 – Introduction to ARIS

Unit 2 – Architecture Vision

Unit 3 – Business Architecture

Unit 4 – Application Architecture

Unit 5 – Data Architecture

Unit 6 – Technology Architecture

Unit 7 – Summary

SAP AG 2008

You will be introduced to Architecture Vision phase of the SAP EAF.


You will understand create a Value Chain view using the Value-added Chain Diagram (VACD) and the
benefits of a Process Map
You will be familiar with the basic concepts of the ARIS Method
You will be able to open, modify and save models in
ARIS Business Designer within the context of a group structure

© SAP AG SOA230 2-2


Prelim:
Framework and
Principles

The Architecture Vision phase


is about validating the
A.
Architecture
business principles, goals and
drivers, defining the scope of
Vision
H.
Architecture
B.
Change Business
Management Architecture
the architecture engagement,
understanding the relevant
C.
stakeholder objectives and
G.
Implementation
Governance
Requirements
Management
Information
Systems articulating an architecture
Architectures

vision that meets the key


business requirements
F. D.
Migration
Technology
Planning
Architecture

E.
Opportunities
and Solutions

SAP AG 2008

What is the Vision phase about?


In this phase we validate the business principles, goals and drivers developed in the “Preliminary” phase
Generally the use of an advanced modeling tool like ARIS IT Architect is not used in the Preliminary
Phase so that is not covered here
The key tasks are to:
Define the scope of the architecture engagement
Understand stakeholder expectations and finally
Articulate a “Vision” that meets customer’s requirements

© SAP AG SOA230 2-3


Templates and Examples
Inputs BEEST Case Study

TOGAF SAP EAF Templates


Reference
Material

SAP EAF Glossary


Outputs
SAP EAF Stakeholder Map
Statement of Work
How EA Supports SOA Whitepaper
Scope and Constraints
TOGAF ADM Vision Narrative
Plan for Architecture Work
Phase Specific Inputs

SAP EAF Vision Phase Worksheet


Architecture Vision
SAP EAF Vision Narrative Document
Architecture Business Capability Assessment
SAP EAF Engagement Initiation Guide

Business Capability Assessment


Vision Technology Capability Assessment

Technology Capability Assessment


Phase IT Governance Impact Report

Stakeholder Map
IT Governance Impact Assessment
Baseline Business and Technology
Architecture
Request for Architecture Work
Architecture Principles
Pre-Existing or Previous

Architecture Repository
Steps
Phase Inputs

Business Strategy, Principles, Goals and


Drivers
Establish the Project
Architecture Principles
Define Scope and Constraints
IT Governance Model
Identify Stakeholder Concerns, Vision and
Architectural Principles (where existing) Requirements

Tailored Architecture Process and Metamodel Define Statement of Work

SAP AG 2008

This slide shows the details of all the inputs we need for the Architecture Vision phase which includes
Phase specific inputs
Reference material/accelerators and
Pre-existing or previous phase inputs.
The slide also shows the typical outputs from the phase
It also identifies the key steps of the phase

© SAP AG SOA230 2-4


!

ARCHITECTURE VISION, CONTEXT AND ROADMAP


Associated
With All Principle Constraint Requirement Gap Work Package
Objects

BUSINESS ARCHITECTURE

Operates in Participates
Organisation Unit in

Owns and
governs Is motivated by Contains Owns Produces
Operates in
Interacts with, Supports, Is Is Produced
Motivates Belongs to Performs performed by Is owned by by
Supplies or Consumes
Product
Driver Actor Can be
Function Process Extension

Consumes
Generates, accessed by
Creates Resolves Performs Supports, Is Is bounded by Is Produced
task in realised by by
Participates
Addresses in

Goal
Is Performed Orchestrates
,
by decomposes Produces
Is realised
through Involves
Role Process
Realises Accesses
Involves
Generates,

I s guided
Orchest rates,
decomposes
Resolves
Objective

by
ARCHITECTURE VISION, CONTEXT AND ROADMAP
Is tracked
against
Control
Process Extension Ensures correct
operation of

Associated Sets performance


criteria for
Is Resolved by
,
Is Generated by Applies to Meets

Principle Constraint Event Requirement Gap Work Package


Is Resolved by
,
With All Measure Is Generated by Service Quality
Governance
Contract
Governance
Contains

Contains

Objects Governance Extension Process Extension Extension Extension


Sets performance Is Resolved by Applies to Governs, Measures
criteria for
Supports, Is Is governed and
Location Is tracked against Is Provided to Resolves realised by Meets measured by
Infrastructure
Consolidation Is owned and (Business, Information System) Service
Extension governed by Services are Contained in Core , Business / IS split supports the Business / IT Alignment Extension Provides governed
interface to access
Provides, consumes Is realised Is implemented on
Motivates through
Is Supplied or Consumed by Is accessed and Is processed
updated through Supplies by
Operates Provides
on Implements platform for Supplies
Contains

Contains

Is Hosted Is Supplied By
Physical Information
Driver
Contains Logical Technology
in
Component Logical Application
Data Entity Component
Data Extension Component Platform Service
Consumes

Infrastructure Consolidation
Resides within Resides within Extension
Creates
Encapsulates Is Realised by Realises
Logical Information Physical Application
Component Component Physical Technology
Addresses
Data Extension Infrastructure Component
Consolidation Extension
Is Hosted in

Goal
Encapsulates
Is Hosted in

Is realised APPLICATION
through
DATA ARCHITECTURE ARCHITECTURE TECHNOLOGY ARCHITECTURE

Infrastructure Process Modelling


Realises Business / IT Alignment
Consolidation Extension Extension Extension Governance Extension Data Modelling Extension Core Content

Objective
Is tracked
against

SAP AG 2008

This slide highlights the entities of the SAP EAF Metamodel that we are looking to define and populate
in the Architecture Vision phase.
Some of these may have been discovered in the Preliminary Phase, but it is here they are recorded and
confirmed.

© SAP AG SOA230 2-5


"#$

The following concepts are informally modeled :


Business Principles, Objectives and Drivers
Architecture Vision
Statement of Work
The formally modeled concepts are :
Stakeholder Map Matrix
Value Chain View – Supported by ARIS
Solution Concept View

SAP AG 2008

What are the aspects of Vision phase that are formally and informally modeled?
We will use ARIS IT Architect to record the formally modeled concepts; the other information will
largely be captured as unstructured MS WORD or MS PowerPoint artifacts. Examples of these are
covered in SOA200.

© SAP AG SOA230 2-6


$#$

Catalog, Matrix or Purpose


View
Stakeholder Map The purpose of the stakeholder map is to identify the stakeholders for the architecture engagement,
Matrix their influence over the engagement and their key questions, issues or concerns that must be
addressed by the architecture framework.

Understanding Stakeholders and their requirements allows an architect to focus effort in areas that
meet the needs of stakeholders.

Due to the potentially sensitive nature of stakeholder mapping information and the fact that the
Architecture Vision phase is intended to be conducted using informal modeling techniques, no
specific metamodel entities will be used to generate a stakeholder map.
Value Chain View A Value Chain view provides a high-level orientation view of an enterprise and how it interacts with the
outside world. In contrast to the more formal Functional Decomposition view developed within the
Business Architecture phase, the Value Chain View focuses on presentational impact.

The purpose of this view is to quickly on-board and align stakeholders for a particular change
initiative, so that all participants understand the high-level functional and organizational context of the
architecture engagement.
Solution Concept A Solution Concept view provides a high-level orientation of the solution that is envisaged in order to
View meet the objectives of the architecture engagement. In contrast to the more formal and detailed
architecture views developed in the following phases, the Solution Concept represents a “pencil
sketch” of the expected solution at the outset of the engagement.

This view may embody key objectives, requirements and constraints for the engagement and also
highlight work areas to be investigated in more detail with formal architecture modeling.
The purpose of this view is to quickly on-board and align stakeholders for a particular change
initiative, so that all participants understand what the architecture engagement is seeking to achieve
and how it is expected that a particular solution approach will meet the needs of the enterprise.

SAP AG 2008

The key matrix and views are described on this slide


Please read through the purpose of each artifact.

© SAP AG SOA230 2-7


"#$

Value Chain Creator: system


SAP EA Framework Last change: 10/18/07 2:58:58 PM
FASST Organization Type: Value-added chain diagram
Sales & Marketing Manufacturing
Manufacturing
FASST Design
FASST
FASSTInformation
Information
&&Communication
Communication
Brand
Brand&&Customer
Customer
FASST Value Chain View
Group Management
Management
Services
Services

FASST
FASSTConsulting
Consulting FASST
FASSTEngineering
Engineering
Finance Car Top S ystems Vehicle
Vehicl eLife
Life Cycle
Cycle
Services
Services Services
Services

Supplier
Suppli er
Collaboration
Collaboration&& FASST
FASSTFinancial
Financial
Human
Human Resources R&D
Operational
Operational Ser
Services
vi ces
Procurement
Procurement

FASST Organization

FASST Design FASST Information Brand & Customer


Sales & Marketing Manufacturing & Communication
Group Management
Services

FASST FASST
Finance Consulting Car Top Systems Vehicle Life Cycle Engineering
Services Services

Value Added Supplier


Collaboration & Human FASST Financial R&D
Chain Diagram Operational
Procurement
Resources Services

A Value Chain view provides a high-level orientation view of an


enterprise and how it interacts with the outside world. In
contrast to the more formal Functional Decomposition view
developed within the Business Architecture phase, the Value
Chain View focuses on presentational impact.
The purpose of this view is to quickly on-board and align
stakeholders for a particular change initiative, so that all
participants understand the high-level functional and
organizational context of the architecture engagement.
Model Type

SAP AG 2008

Here you see the description of a Value Chain model and an example form the FASST business case.
The Value Chain model is represented in ARIS using the Value Added Chain diagram.

© SAP AG SOA230 2-8


$#$

Value Chain

Sales & Marketing Manufacturing


Manufacturing
FASST Organization

FASST Design
Group
FASST
FASSTInformation
Information
&&Communication
Communication
Services
Services
Brand
Brand&&Customer
Customer
Management
Management
ARIS Definition SAP EAF Definition
FASST
FASSTConsulting
Consulting FASST
FASSTEngineering
Engineering
Finance Car Top S ystems Vehicle
Vehicl eLife
Life Cycle
Cycle
Services
Services Services
Services

Supplier
Suppli er
Collaboration
Collaboration&& FASST
FASSTFinancial
Financial
Human
Human Resources R&D
Operational
Operational Ser
Services
vi ces
Procurement
Procurement

Value-added chain:
Value-added chain Process, Process Step, Process, Function
Function

Value Added
Chain Diagram
Value-added chain

Model Type Object Types (Symbol)

SAP AG 2008

The following symbols are used to describe the Value Chain. You see the ARIS definition of those
symbols and the SAP EAF definition.

© SAP AG SOA230 2-9


% &' () ()

Object type: Function


Process 1

is process-oriented superior

is predecessor of
Process 1.1 Process 1.2 Process 1.3

In a Value-Added Chain Diagram, there are 2 fundamental


connection types between Functions:
Is process-oriented superior ( process hierarchy)
Is predecessor to ( process sequence)

SAP AG 2008

You will notice a difference to when modeling using VISIO: When you draw a line, you are creating a
relationship. You are choosing the relationship that the objects have with one another. The
administrator can change the vocabulary. When you are creating the filter, you can change the verbiage.
Once established you will only get what’s available to you in the filter.
These two relationship options are specific to Value Added Chain Diagrams.

© SAP AG SOA230 2-10


% )! & * !

In Value-Added Chain Diagrams, there are two fundamental


Symbols for the object type Function.

Process 1.1 Process 1.2 Process 1.3

Symbol: "Closed" Symbol: "Open"


Value-Added Chain Value-Added Chain

In general:
A Symbol is the graphical representation of an object type in a
model.
An Object Type can be represented by different symbols in different
model types.

SAP AG 2008

History of chevron. A closed Chevron can be used when starting with the starting processes of a
VACD. Closed fx = start here

© SAP AG SOA230 2-11


% !

The Value-Added Chain Diagram often also includes:


performance relationships between processes, and
responsible Organizational Units

Process 1

Object type: Technical Term


has output of
TechnicalObject
term type:
is Organizational
input of Unit
Process 1.1 Process 1.2

carries out
Department 1
Department 2

Object type: Technical Term Object type: Organizational Unit

SAP AG 2008

We will now go through more detail with the VACD.


Who is responsible for these functions?
Go thru each function and who owns it and the relationships.
We can add technical term. Specifically- your companies specific company Jargon. Think about your
very first meeting in the company and all the letters and acronyms. And files and document names. ?
Glossary of technical terms”
Unless you draw a relationship, there is no assumed or automatic relationship; the relationship has to be
drawn. When you arrange the layout of your model; those not connected will fall to upper right corner.
We give you 2 options for an organization unit. A yellow oval or rectangle.
Although process 1.1 has output tech term. There is no assumed relationship, if there is a relation you
need to draw it. It just happens that they are both related to a same tech term.

© SAP AG SOA230 2-12


!! ) +,

Model of model type


Value-Added Chain Diagram
Enterprise process map

Model attribute of Connection of connection type


Process 1
attribute type Name Is process-oriented superior
is process-oriented superior

is predecessor of
Process 1.1 Process 1.2 Process 1.3

Object of object type Function,


represented by symbol Object attribute of attribute type Name
Closed Value-Added Chain
Connection of connection type
Is predecessor of

SAP AG 2008

So that we can become more familiar with the terminology, here is a summary of the basic ARIS
concepts. You will need a basic understanding of these and how they relate to the TOGAF/SAP EAF
terms.
Even the name of the object is considered an attribute.
Model Type=VACD
Name is an Attribute Type in this case it is an attribute of the model
Function is an Object type, in this case represented by the chevron symbol.
Connection Type
Name is an attribute type within an object attribute

© SAP AG SOA230 2-13


Models can be opened in both Explorer and Designer modules.
The Navigation and the Models filter must be activated.

1) Select group in which the model is saved.

2a) Double click on the model or


2b) Call up model pop-up menu Open

SAP AG 2008

To open a model navigate to the group that contains the model.


Double click on the model icon OR
Right click - Open

© SAP AG SOA230 2-14


4 Ways to Save a Model
1) Call up model pop-up
menu (right click in
model) Save
2) Menu bar:
File Save
3) Keyboard shortcut
Ctrl + S
4) In toolbar:
TIP Click on Save icon
Make sure to Save before closing a model

SAP AG 2008

To save a model do:


Call up model pop-up menu (right click in model) Save
Menu bar: File Save
Keyboard shortcut Ctrl + S
In toolbar: Click on Save icon
When you close a model without saving you will also be prompted to save the model.

© SAP AG SOA230 2-15


Close

1a)

1a) Call up pop-up menu on the tab with the


model name Close
1b) Menu bar: File Close

SAP AG 2008

To close a model do:


1a) Call up pop-up menu on the tab with the model name Close
1b) Menu bar: File Close
You can also close a model by clicking on the ‚x‘ on the model tap.

© SAP AG SOA230 2-16


!! )
Value Chain View
(VACD) Organizational unit
Solution Concept View
(EPC)unit
Organizational Gap
!
Process is technically responsible for is technically responsible for occurs at

is predecessor of is predecessor of
is process-oriented superior is process-oriented superior Process Function Function

supports supports supports


is predecessor of
Function Function

Driver Objective Requirement

can be user
Organizational unit Organizational unit Service
Abstract Service

is technically responsible for is technically responsible for supports


Business Service

is predecessor of is predecessor of
Process Function Function

Business Service Requirement

supports supports
Function Function

Driver Objective
Functional
Functional Decomposition View Decomposition View
Business Footprint View (IS Context Model) (IS Context Model)
(EPC)
SAP AG 2008

The slide shows the main views of the Architecture Vision phase and their main elements.
You can see how those elements link to elements in the Business Architecture which we will cover next.

© SAP AG SOA230 2-17


!! )

This is the end of the 2cd Unit ! -


+
You should now understand SAP Enterprise Architecture Resource Base

Released to the Open Group

Released to the Open Group


Framework extensions Extensions

The Architecture Vision of the Usage Guidelines SAP Business


Reference Models
SAP EAF Architecture
Development
Content
Metamodel
Method
SAP Technology
How to model the Value chain Templates, Examples and Case Reference Models
Studies
using and Value added chain
SAP Mapping Extensions
diagram in ARIS
SAP Tooling Extensions
The next Unit explains the SAP Content SAP Implementation
EA Modelling Tools
Tools Tools
Business Architecture
TOGAF Architecture TOGAF
Development Method Resource Base

SAP AG 2008

This is the end of the 2nd Unit


You should now understand
The Architecture Vision of the SAP EAF
How to model in ARIS
How to model the Value chain using and Value added chain diagram in ARIS
The next Unit explains the Business Architecture phase

© SAP AG SOA230 2-18


Unit 3 - Business Architecture

SAP AG 2008

© SAP AG SOA230 3-1


Unit 1 - Overview of SAP Enterprise Architecture Framework
Unit 1 – Introduction to ARIS

Unit 2 – Architecture Vision

Unit 3 – Business Architecture

Unit 4 – Application Architecture

Unit 5 – Data Architecture

Unit 6 – Technology Architecture

Unit 7 – Summary

SAP AG 2008

In this unit you will see an overview of the Business Architetcure of the SAP EAF.
You will learn how to model Business Architetcure views in ARIS.
You will learn more details on ARIS such as attributes, object properties and other.

© SAP AG SOA230 3-2


Prelim:
Framework and
Principles

The Business Architecture


A.
Architecture
phase is about defining the
H.
Architecture
Vision
B. As-Is and To-Be business
architectures for the
Change Business
Management Architecture

organization, detailing the


roadmap towards the To-Be
C.
G.
Implementation
Requirements Information
Systems
architecture, and identifying
Governance Management Architectures
key work packages in the
roadmap.
F. D.
Migration
Technology
Planning
Architecture

E.
Opportunities
and Solutions

SAP AG 2008

What is the Business Architecture phase about?


In this phase
We define the “as-is” and “to-be” business architectures for the enterprise
Define a roadmap to get to “to-be” architecture and
Identify key work packages in the roadmap

© SAP AG SOA230 3-3


Templates and Examples
Inputs BEEST Case Study

TOGAF SAP EAF Templates


Reference

SAP EAF Glossary


Material

Outputs
Service Contract Guidelines
Updated Statement of Work
Solution Composer Whitepaper
Validated Principles, Business Goals and
SAP EAF to SAP Terminology Mappings
Strategic Drivers
Phase Specific Inputs

Current State Business Architecture


ADM Business Architecture Narrative Business Target Business Architecture
SAP EAF Business Architecture Worksheet
Architecture Gap Analysis Results
SAP EAF Business Architecture Narrative
SAP EAF Metamodel and View Definition
Phase Updated Business Requirements, Policies,
Standards, Guidelines and Specifications
IS and Technology Requirements

Steps
Pre-Existing or Previous

Statement of Work

Architecture Vision Business Baseline Description


Phase Inputs

Architecture Principles Reference Models, Viewpoints and Tools


Baseline Business and Technology
Architecture Architecture Models
Stakeholder Map
Produce Gap Analysis
Tailored Architecture Process and Metamodel
Select Business Architecture Building
Blocks
Define Roadmap

Resolve Impacts Across the Enterprise

SAP AG 2008

This slide shows the details of all the inputs we need for the phase which includes
Phase specific inputs
Reference material/accelerators and
Pre-existing or previous phase inputs
The slide also depicts the typical outputs from the phase which is a bit of an elaboration compared to
TOGAF ADM
It also identifies the key steps of the phase

© SAP AG SOA230 3-4


!
ARCHITECTURE VISION, CONTEXT AND ROADMAP
Associated
With All Principle Constraint Requirement Gap Work Package
Objects

BUSINESS ARCHITECTURE

Operates in Participates
Organisation Unit in

Owns and
governs Is motivated by Contains Owns Produces
Operates in
Interacts with, Supports, Is Is Produced
Motivates Belongs to Performs performed by Is owned by by
Supplies or Consumes
Product
Driver Actor Can be
Function Process Extension

Consumes
Generates, accessed by
Creates Resolves Performs Supports, Is Is bounded by Is Produced
task in realised by by
Participates
Addresses in

Goal
Is Performed Orchestrates
,
by decomposes Produces
Is realised
through Involves
Role Process
Realises Accesses
Involves
Generates,

Is guided
Orchest rates,
decomposes
Objective Resolves

by
Is tracked Control
against Ensures correct Process Extension
operation of
Sets performance Is Resolved by
,
criteria for Is Generated by Applies to Meets
Is Resolved by
,
Is Generated by Service Quality Contract
Measure Event
Governance Governance
Contains

Contains

Governance Extension Process Extension Extension Extension


Sets performance Is Resolved by Applies to Governs, Measures
criteria for
Supports, Is Is governed and
Location Is tracked against Is Provided to Resolves realised by Meets measured by
Infrastructure
Consolidation Is owned and (Business, Information System) Service
Extension governed by Services are Contained in Core , Business / IS split supports the Business / IT Alignment Extension Provides governed
interface to access
Provides, consumes Is realised Is implemented on
through
Is Supplied or Consumed by Is accessed and Is processed Operates Provides
updated through by on Implements platform for Supplies
Contains

Contains

Is Hosted Is Supplied By
Contains Physical Information Logical Technology
in
Component Logical Application
Data Entity Component
Data Extension Component Platform Service
Infrastructure Consolidation

Organization / Actor Catalog Resides within Resides within

Encapsulates Is Realised by Realises


Extension
Location Catalog
Logical Information Physical Application
Component Component Physical Technology
Data Extension Infrastructure Component
Consolidation Extension
Encapsulates Is Hosted in

Driver / Goal / Objective Catalog Process / Event / Control / Product Catalog


Is Hosted in

APPLICATION
DATA ARCHITECTURE ARCHITECTURE TECHNOLOGY ARCHITECTURE

Infrastructure Process Modelling Business / IT Alignment

Role Catalog Consolidation Extension Extension Extension Governance Extension


Contract / Measure Catalog
Data Modelling Extension Core Content

Service / Function Catalog

SAP AG 2008

Here we can see how each entity of the metamodel in SAP EAF relates to the specific artifacts
produced.

© SAP AG SOA230 3-5


"
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


Business Architecture
Business Architecture
System / Function
Matrix
Application Interaction
Matrix
Role Catalog
Process / System
Realization View

Location Catalog
Application Portfolio
Role / System
Matrix
Software Engineering
View
Application
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise

Business Architecture Organization Matrix Manageability View

Data .
Driver/Goal//Objective
Catalog
Structure Context
Business Architecture
Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View
Business Architecture
Function Matrix Organization Actor Catalog
View

Data Lifecycle View


Data Migration View
Process/Event/Control/Product
Data Entity / Info
Component Catalog
Catalog
Data Entity Hierarchy Data Security View
View

Business Architecture Technology .

Technology Standard
Structure Context
System / Technology
Service Platform
FunctionOperation
Catalog
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Hardware View
Business Architecture
Environments and
Locations View Catalog
Communication
Contract/Measure Engineering View
Matrix

Catalog
SAP AG 2008

The slide shows the product flow of the Business Architecture and the catalogs that will be covered in
this unit.

© SAP AG SOA230 3-6


#$%

Catalog, Matrix or Purpose


View
Organization / The purpose of the Organization / Actor catalog is to capture a definitive listing of all
Actor Catalog participants that interact with IT, including users and owners of IT systems.

The Organization / Actor catalog contains the following metamodel entities:

Organization Unit, Actor, Location may be included in this catalog if an independent


location catalog is not maintained
Driver / Goal / The purpose of the Driver / Goal / Objective catalog is to provide a cross organizational
Objective Catalog reference of how an organization meets its drivers in practical terms through goals,
objectives and optionally measures.

The Driver / Goal / Objective catalog contains the following metamodel entities:

Organization Unit, Driver, Goal, Objective, Measure may optionally be included


Role Catalog The purpose of the Role catalog is to provide a listing of all authorization levels or zones
within an enterprise. Frequently, application security or behavior is defined against locally
understood concepts of authorization that create complex and unexpected consequences
when combined on the user desktop.

The Role catalog contains the following metamodel entities:

Role

SAP AG 2008

The purpose of each catalog is now explained.

© SAP AG SOA230 3-7


&$%

Catalog, Matrix or Purpose


View
Service / Function The purpose of the Service / Function catalog is to provide a functional decomposition in a
Catalog form that can be filtered, reported on and queried, as a supplement to graphical functional
decomposition views.

The Service / Function catalog contains the following metamodel entities:

Organization Unit, Business Function, Business Service, Information System Service may
optionally be included here
Location Catalog The Location catalog provides a listing of all locations where an enterprise carries out
business operations or houses architecturally relevant assets, such as data centers or end
user computing equipment.

The Location catalog contains the following metamodel entities:

Location
Process Catalog The Process catalog provides a hierarchy of processes, events that trigger processes,
outputs from processes and controls applied to the execution of processes.

The Process / Event / Control / Product catalog contains the following metamodel entities:

Process, Event, Control ,Product

SAP AG 2008

The purpose of each catalog is now explained

© SAP AG SOA230 3-8


%$%

Catalog, Matrix or Purpose


View
Contract / The Contract / Measure catalog provides a listing of all agreed service contracts and the
Measure Catalog optionally the measures attached to those contracts. It forms the master list of Service
Levels agreed to across the Enterprise.

The Contract / Measure catalog contains the following metamodel entities:

Business Service
Optionally Information System Service
Contract
Measure

SAP AG 2008

The purpose of each catalog is now explained

© SAP AG SOA230 3-9


SAP AG 2008

This slide shows in ARIS the catalogs as described previously and example objects for each catalog.
Objects can be imported through various ARIS importing features such as XML.
Objects can also be created manually in each catalog: right click -> new -> object
Objects are also created during creation of a diagram.

© SAP AG SOA230 3-10


'

ARIS Groups can be compared to folders in Windows Explorer.


ARIS Groups can be arranged in hierarchies.
Purpose:
Structuring the ARIS database
Structured storage (and searching) of ARIS DB content: models, objects

Definition of access privileges


Read privileges
Write privileges
Delete privileges
No privileges
for the content of the group

Note
Access privileges can only be managed in
ARIS Business Architect.

SAP AG 2008

Access and privileges are given on a group level and defined by the administrator.

© SAP AG SOA230 3-11


' ( !

Catalog
Catalog stores objects
of the architecture

Views
Views store the
diagrams of the
architecture

SAP AG 2008

Library groups
Provision of objects that are to be re-used in other models (e.g. process models). To make them easy
to find and to limit the access privileges, these objects are stored in special groups.
The objects can be shown in a structured form in models, in which case the models should then also
be stored in the corresponding groups.
Process model groups
Storage of process models with their associated objects that are not to be provided as a library for re-
use.

© SAP AG SOA230 3-12


' "' #$%

In Designer, the content of the groups (models, objects) can be


displayed exclusively in the left-hand window Filter
(Explorer tree). Models and/or objects
can be shown or
hidden. Click on boxes
to enable and disable.

Objects are
represented
by their symbol.
Symbol for models

Symbol for models

SAP AG 2008

The slide shows the content and symbology of a group.

© SAP AG SOA230 3-13


' "' &$%

In Explorer the content of a group (models, objects) can be displayed in both


the left-hand and the right-hand windows.
Models and/or objects can be shown or
hidden. Click on boxes to enable and Models tab is selected. Window displays
disable. all models within the folder named
Note: The objects box is not enabled; Organizational Structure
therefore, the objects are NOT displayed.

SAP AG 2008

In order to view the content of a group, the viewer must have at least “read” privileges for that group.

© SAP AG SOA230 3-14


' "' %$%
Models and/or objects can be shown or
Objects tab is selected. Window displays
hidden. Click on boxes to enable and
all objects within the folder named
disable.
Organization/Actors
Note: The objects box IS enabled;
therefore, the objects are now displayed

SAP AG 2008

The content of a group can be shown on the left by switching on the filter buttons or on the right sorted
by models and objects.

© SAP AG SOA230 3-15


) '

A new ARIS group is created using the pop-up menu for the group
under which the new group is to be added.
Creating a New Group
Only possible in Explorer

1) Right Click on superior


group
2) In pop-up menu select
New
3) In pop-up menu select
Group
4) Enter the Group Name
in text box

SAP AG 2008

Creating a new ARIS group


New groups can be created in both the Explorer and Designer modules using the pop-up menu.
In the Explorer module, new groups can also be added by clicking on an icon (see right-hand
Explorer window).

© SAP AG SOA230 3-16


"
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Business Architecture
Application Portfolio
Role / System
Matrix
Software Engineering
View
Application
Communication View
Actor Role Matrix
Catalog

Application and
Business Architecture
Software Distribution
View
Interface Catalog
User Location View
Business Interaction
Application Migration Matrix
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

The slide shows the product flow of the Business Architecture and the matrices that will be covered in
this unit.
Matrices will be covered in Unit 4.

© SAP AG SOA230 3-17


Catalog, Matrix Purpose
or View
Business The purpose of this matrix is to depict the relationship interactions between organizations
Interaction and business functions across the enterprise.
Matrix
Understanding Business Interaction of an enterprise is important as it helps to highlight value
chain and dependencies across organizations.

The Business Interaction Matrix shows the following metamodel entities and relationships:
Organization
Business Function
Business Service
Business Service communicates with Business Service relationships
Business Service is dependent on Business Service relationships
Actor / Role The purpose of this matrix is to show which actors perform which roles, supporting definition
Matrix of security and skills requirements.

Understanding actor to role relationships is a key supporting tool in definition of training


needs, user security settings and organizational change management,

The Actor / Role Matrix shows the following metamodel entities and relationships:
Actor
Role
Actor performs Role relationships

SAP AG 2008

The purpose of each matrix is now explained.

© SAP AG SOA230 3-18


"
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Business Architecture
Application Portfolio
Role / System
Matrix
Software Engineering
View
Application
Communication View
Organization Chart View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

Next we will look at the organizational chart view

© SAP AG SOA230 3-19


* + #$,

Organization Chart SAP EA Framework


Creator: system
Last change: 10/18/07 3:56:19 PM
FASST Organization Type: Organizational chart

FASST

Supplier
Collaboration and FASST Consulting
Finance Sales and Marketing Manufacturing HR
Operational Services
Procurement

FASST

Organization
Chart View Supplier
Collaboration and FASST Consulting
Finance Sales and Marketing Manufacturing HR
Operational Services
Procurement

An Organization Decomposition view describes the links


between Actor, Roles and Location within an organization
tree.
An organization map should provide a chain of command
of owners and decision makers in the organization.
Although it is not the intent of the Organization
Decomposition view to link Goal to Organization, one
should be able to intuitively link the Goals to the
Stakeholders from the Organization Decomposition view.
Model Type

SAP AG 2008

Here we have the description of the organization chart view and an example from the FASST case
study.
The organization chart is modeled in ARIS using the Organizational chart.

© SAP AG SOA230 3-20


* + &$,

Organization/ SAP EA Framework Creator: system

Actor/ Location
Last change: 10/18/07 4:04:07 PM
FASST Organization Actor Location Type: Organizational chart

FASST

Supplier
Collaboration and FASST Consulting
Finance Sales and Marketing Manufacturing HR
Operational Services
Procurement

loc-Weissach loc-
loc-Stuttgart
Ludwigsburg

org-Customer org- Financial


org-Customer
Organization Service
Service Services

Chart View org-Sales &


org-Sales &
Marketing
org- Financial Marketing
Services

rol-financial org-Production
adviser

The purpose of the Organization / Actor catalog is to capture a


definitive listing of all participants that interact with IT, including
users and owners of IT systems.
The Organization / Actor catalog can be referenced when
developing requirements in order to test for completeness.
The Organization / Actor catalog contains the following metamodel
entities:
Organization Unit
Actor
Model Type Location may be included in this catalog if an independent
location catalog is not maintained

SAP AG 2008

© SAP AG SOA230 3-21


* + %$,

Organization/ ARIS Definition SAP EAF Definition


Actor/ Location
FASST

Supplier
Collaboration and FASST Consulting
Finance Sales and Marketing Manufacturing HR

Organization Organization
Operational Services

Organizational unit
Procurement

Organization
Chart View
Location Location Location

Person type: Role,


Role
Actor, Role
Person

Object Types
Model Type

SAP AG 2008

Here we have listed the main object elements of the organization chart view.

© SAP AG SOA230 3-22


* + ,$,

Organization/
Actor/ Location
FASST
Organizational
unit
Supplier
Collaboration and FASST Consulting
Finance Sales and Marketing Manufacturing HR
Operational Services
Procurement

is composed of

Organization
Chart View Organizational is located at
Location
unit

is composed of encompasses

is located at
Actor Location

Relationship Types
Model Type

SAP AG 2008

Here you see the relationships that can be created between the elements of the organization chart.

© SAP AG SOA230 3-23


* -

The connections between Organizational Units


(departments) are normally expressed by Relationship Type
Here there is more than one
making departments superior/subordinate. Connection type between
the two organizational units
permitted by the method filter.

Executive Board
Example PLC

Finance &
Administration Purchasing

Pay close attention to the source (From Name) and target (To Name) objects!

SAP AG 2008

The relationships you can create are extensive.


Relationships can be defined specific to the organization and will be determined during the methods and
conventions workshop.
Be sure you are accurate in who reports to whom. It will depend on which object you have selected and
the direction you are making the connection.

© SAP AG SOA230 3-24


* -

Between Organizational Units (departments) and Positions, the


following information is primarily expressed:
A Position manages an Organizational Unit (department)
An Organizational Unit (department) contains particular Position(s).

Example 1: Position Manages Organizational Unit


(department).

Purchasing Purchasing

Heads Purchasing
is organization Manager for Purchasing Manager
Manager

Default Connection Type: Renamed Connection Type:

“is organization manager for” “Heads”


(from position to organizational unit) (ARIS Configuration)

SAP AG 2008

ARIS will automatically bring up the relationship option window.


This slide is showing that Connection names can be configured to project/company specific
terminology.

© SAP AG SOA230 3-25


* + ( ! . *

SAP
Implementation Group

Project manager
Jackson, Andrew SAP Implementation

Project team
MM

Team leader
Tyler, Steven MM

Miller, Barbara Employee (Internal person)


Jones, Paul
External employee (External person)

Project team
FI/CO

Team leader
Richardson, Peter FI/CO

Hunter, Edward

Role (Person type)


SAP AG 2008

A group represents a grouping of internal and possibly externally persons, who are working together
temporarily on a common task (e.g. a project team).
Groups are normally interdisciplinary and are therefore occupied by persons from different departments.
It is recommended that the organizational structure of a company and the project structures be
represented in separate models.
E.g. Project team vs. an org. unit.
E.g. Steering committee vs. Finance department

© SAP AG SOA230 3-26


* + ( !

In an Organizational Chart, Roles are mainly


"only" listed or also
related to one another.
SRM Roles Role (object type: Person type)

Strategic Purchaser

Operative Purchaser

Connection types permitted between roles in the method filter.

SAP AG 2008

Each organization will determine how they want to use the object types.
Roles represent technical tasks, qualifications and authorizations.
Examples of roles: Quality officer, Data Protection Officer, First Aider, SAP Implementation Project
Manager.
Roles should not be confused with positions.
Positions are mainly used in actual models (organizational chart, actual process models).
By contrast, roles are normally used in target models (e.g. target processes).
It is recommended that the organizational structure of a company and the roles be represented in
separate models.

© SAP AG SOA230 3-27


)

A new model can be created in both Explorer and Designer modules.

1) Select the group in which the model is to be saved

2) Call up group pop-up menu

3) Select New Model

New Model Icon


SAP AG 2008

To create a new model :


Select the group in which the model is to be saved
Call up group pop-up menu
Select New Model
You can also select the new model icon in the explorer.

© SAP AG SOA230 3-28


) *

1) Select the ARIS View to


which the model type to be
created belongs

2) Select Model Type

3) Enter Model Name

4) Click on OK The "blank" model is opened in Designer.

SAP AG 2008

The selection of a particular view acts like a filter, i.e. only the ARIS model types that are assigned
under the ARIS method for that view are displayed.
Multiple views can be displayed by activating several areas by clicking on them.

© SAP AG SOA230 3-29


$

Model name

The desired information can be


displayed again if necessary.

Click on the boxes to enble.

Toolbar

SAP AG 2008

Additional elements in the designer module can be turn on and off to enlarge the modeling area.
Modeling area
The modeling area can be adapted to meet specific requirements.
If a large modeling area is required, the entire screen width can be used; to do this hide all the other
ARIS windows. Check boxes are available for this purpose directly on screen.

© SAP AG SOA230 3-30


/ 0 1

The Toolbar can be adapted for individual users.

SAP AG 2008

We will now demonstrate this.


Modeling toolbar
The width of the modeling toolbar can be changed simply by dragging the edge.
Object symbols can be shown small, large or by the symbol names, depending on the user's
preference.
If the modeling toolbar is dynamically shown or hidden, a user only has to move the mouse pointer
over the edge of the toolbar to open it up. When the user moves the mouse pointer over the modeling
area, the modeling toolbar closes again.
The number of object symbols available can be limited or expanded as required. All object symbols
that are not needed can be hidden from the pop-up menu and all object symbols that are wanted can
be shown using a dialog box.

© SAP AG SOA230 3-31


0 1 2! 1

For reasons of clarity, not all available symbols are displayed in the
toolbar.
However, additional symbols can be displayed and added to the
toolbar using the corresponding button.
Add Symbols:
Double click on the
Symbol to add additional
Objects/Symbols

SAP AG 2008

The list of symbols suggested in the symbol bar can be extended depending on the permitted list of
symbols for that ARIS model type.

© SAP AG SOA230 3-32


1.

1) Left click on desired symbol

2) Move cursor to the desired


position in the modeling
window and left click
Object is placed.

3) Enter object name

SAP AG 2008

Tip: Multiple object placement


After selecting the symbol to be placed in the toolbar,
Holding down the Ctrl key allows multiple objects to be placed.

© SAP AG SOA230 3-33


2 1.

Individual or multiple selected objects can be moved manually:


By pressing the Shift key and using the arrow keys (only with
activated grid)
Using Drag & Drop by left clicking
With the grid activated, it is easy to manually align objects as they
are automatically placed in the grid when they are moved.
The grid can be activated using a button in the toolbar.

Grid activated Grid deactivated

SAP AG 2008

Individual or multiple selected objects can be moved manually:


By pressing the Shift key and using the arrow keys (only with activated grid)
Using Drag & Drop by left clicking
With the grid activated, it is easy to manually align objects as they are automatically placed in the
grid when they are moved.
The grid can be activated using a button in the toolbar.
Note: The object pop-up menu -> Select -> All of this type allows all objects of the selected object type
to be selected in the open models.

© SAP AG SOA230 3-34


! 2 1.

1) Select the objects to be aligned

3 Ways to Align Objects


1) From Tool Bar Click on
Arrange Align
2) Right Click on selected object(s)
Align choose alignment
option
3) From the toolbar choose the
alignement Button

SAP AG 2008

ARIS provides various menu items to align objects in a model.

© SAP AG SOA230 3-35


3 - 1. 3

If objects are placed or moved without the grid being activated,


they must be subsequently aligned with the grid, after activating
the grid. This can be done for individual / multiple objects or for
a complete model (shortcut: Ctrl + A).

1) Select the objects to be aligned

2a) In menu bar select Arrange


Align to grid
2b) Pop-up menu for selected objects
Arrange Align to grid

SAP AG 2008

If the grid is turned on a later point during modeling, you can re-align all objects to the grid.

© SAP AG SOA230 3-36


/

The modeler can determine the course of a connection.


Every object has several anchor points that can be used as
the start or end point for a connection. Simply ‘hover’ over
edge of the object for connection anchor to activate.

Connection anchor point on edge of object

Management

Marketing Production Sales

SAP AG 2008

You can see here how to start drawing a connection form one object to another.

© SAP AG SOA230 3-37


/

Fast Connection Drawing allows connections to be created


without having to select a connection anchor point on the edge
of the object. It is only necessary to click on the source and
target objects and the connection is automatically placed in the
center of the object.
Click Escape to stop drawing.

Management
Press F6 to turn off ‘Connection mode’

Marketing Production Sales

SAP AG 2008

You can also start a connection be clicking inside the first object.
ARIS will choose an anchor point for you.

© SAP AG SOA230 3-38


/

If the method filter allows multiple connections between a


source and target object (type), a selection window appears.

Click box to enable:


Keep same relationship type for next
connections to draw more connections of the same
type

SAP AG 2008

If multiple types of connections are allowed between two objects ARIS will prompt you to select a
relationship type.

© SAP AG SOA230 3-39


"

"Unattractive" connections can be changed manually:

1) Select connection(s)

2) Call up connection pop-up menu

3) Click on Align Connection

SAP AG 2008

You can manually change the course of a connection by using this method or move the anchor points of
the connection.

© SAP AG SOA230 3-40


+ #$&

The perspective on the model view can be changed as follows:


Plus (+) key to zoom in
In the number pad
Minus (-) key to zoom out

Alternative:
Zoom (in toolbar)

SAP AG 2008

You can zoom in or out of a model using the zoom buttons.


You can also use the + and – key.

© SAP AG SOA230 3-41


+ &$&

The model view can also be changed using View in the menu
bar.
Reset Zoom: Display size = 100%
Fit to Window: Model is enlarged or reduced so that it takes up the
entire modeling area.

Change model view

SAP AG 2008

You can also change the model view in the view menu.

© SAP AG SOA230 3-42


) ! !

All elements in the ARIS database are uniquely identified using


GUIDs (global unique identifiers).
However, since the GUID is not directly visible during modeling,
identification (particularly of models and objects) is carried out
by name.
For this reason, standard naming conventions are extremely
important:
For consistent and redundancy-free modeling
When creating occurrence copies
When searching for objects and models
When consolidating objects with synonymous names

SAP AG 2008

Naming conventions are important to create a consistent architecture and to enable other participants to
find the right architecture information.

© SAP AG SOA230 3-43


) ! '

Abbreviations should be avoided.


However, if abbreviations are used:
They should be commonly known and understood.
The name should be written out in the “full name” attribute.
Names should be readily comprehensible and commonly used,
short but precise.
Names should respect existing enterprise terminology.

SAP AG 2008

We recommend some general naming conventions.


Nevertheless, naming conventions have to be defined for each organization depending on their needs.
Conventions must be documented, communicated and administrated.

© SAP AG SOA230 3-44


' ( !
Role 1
IT system 1
Input 1

Output 1

Function
File
Without graphic conventions
Input 2
Role 2

Input 3
IT system 2

Input 1

Input 2 Function Output 1 File

Input 3
Role 1

Role 2

With graphic conventions


IT system 1

IT system 2

SAP AG 2008

Modeling conventions are important to create a consistent architecture and to enable other participants
to read diagrams.

© SAP AG SOA230 3-45


'

Graphic conventions:
Ensure that models look the same even when different modelers
are involved
Make the models clearer and easier to read
The following graphic conventions are defined in the template:
Model background color
The appearance of objects (symbols) and relationships: size, color,
lines, shade, etc.
Placing of attributes for objects and relationships (not of models)*
Attribute font formats

* As a general rule, less is more!

SAP AG 2008

We recommend some general modeling conventions shown here.


Nevertheless, modeling conventions have to be defined for each organization depending on their needs.
Conventions must be documented, communicated and administrated.

© SAP AG SOA230 3-46


1

Detailed information can be maintained about models, objects and


connections. Attributes are used for this purpose.
A variety of attributes are pre-defined in the ARIS Method. However,
there is also a large number of user-definable attributes that can be set
in the ARIS Configuration using ARIS Business Architect.
As well as editable attributes, ARIS includes automatically maintained
attributes whose values cannot be manually changed.
Example: Creation date, Created by, Date of last change, Last processor…
There are 2 types of attributes:
Generally applicable attributes
Specific attributes

Note: the SAP EAF Database/Filter includes pre-defined attributes according


to the SAP EAF Metamodel

SAP AG 2008

Attributes are used to store information about objects and models that cannot be represented graphically.
The SAP EAF defines a recommended set of attributes for each object ; these have been predefined in
the SAP EAF Database/Filter supplied with this course.

© SAP AG SOA230 3-47


' 2 1 1. 1 ( !

The greyed-out attributes cannot be edited.

SAP AG 2008

ARIS automatically greys out attributes that are automatically assigned attributes by ARIS This is
within the Attribute Wizard.
What are the different ways a user can edit attributes:
Properties icon (under arrange)
F8
View-Attribute Editor
Attribute Editor
Attribute Wizard
Properties window within model. Within the properties window, you can click on more attributes
and attributes that are available for that model or object can be added to be populated.

© SAP AG SOA230 3-48


" 1 ( !
Specific attributes of an Actor Specific attributes of a Function

Specific attributes of an Principle

SAP AG 2008

Specific attributes for the SAP EAF have been created. Some examples are shown here.

© SAP AG SOA230 3-49


1

There are two alternatives for maintaining Attributes:


The Properties window
The Attribute Editor (Attribute window)
The Properties window can only be displayed in Designer, not
in Explorer.
Only one item (one model, one object, one connection) can be
displayed in the Properties window.

SAP AG 2008

There are two alternatives for maintaining Attributes:


The Properties window
The Attribute Editor (Attribute window)

© SAP AG SOA230 3-50


1 4 #$&

3) Select Attributes tab 1) Properties must be activated

2) Select item

SAP AG 2008

This shows how you can maintain attribute information in the properties window.
If you don’t see an attribute that you are looking for you can use the feature on the next slide.

© SAP AG SOA230 3-51


1 4 &$&

The More Attributes button allows


you to select attributes from a list,
transfer them to the Properties
window and edit them. Multiple selections are possible

SAP AG 2008

Here you can add attributes to be visible in the properties window.

© SAP AG SOA230 3-52


1 1 #$&

4 Ways to Maintain an Attribute


1) Highlight object(s)
a) Select Attributes from pop-
up menu
b) F8 Key
c) In menu bar select:
Edit Attributes
d) In toolbar click on
Attributes button

SAP AG 2008

Other ways to access attribute information are shown here.


4 Ways to Maintain an Attribute
Highlight object(s)
Select Attributes from pop-up menu
F8 Key
In menu bar select: Edit Attributes
In toolbar click on Attributes button

© SAP AG SOA230 3-53


1 1 &$&

The Attribute Editor can be used to assign attributes to multiple


objects and connections, even if they are of different types.
There is a separate tab for each Object and Connection type.

SAP AG 2008

Attribute editing
As well as the attributes of connections, objects and models, the attributes of groups, databases, users
and fonts can be edited.
Associated database items are summarized on tabs. For example, objects of a particular type are
placed on a tab that has the name of the object type.
Attribute editing can be used to edit database items from different databases. The corresponding
database names are shown on the tabs.
The attribute group tree is displayed.

© SAP AG SOA230 3-54


1 3 5 (

1)

2)

SAP AG 2008

External files (Word, Excel documents etc.) can be linked directly to an object or model. To do this, the
Link 1-4 system attributes are used.
For example, a position description stored as a PDF document on your network can be called up directly
from ARIS.
Always give a link a name as that is what ARIS uses to relate to.
Make sure whatever you link into ARIS can be found. Use the example of giving directions to one
house, but when you move not giving you addresses to the new house. You will use the directions you
have. If only I have access to the link then it does not make sense to have it.
It must be accessible to whoever needs the information.

© SAP AG SOA230 3-55


- (

The linked external file can be called up in different ways. It is


always important to ensure that the user has access
authorization for the storage location of the file.

2a) Object pop-up menu Run


Sales Manager
2b) Keyboard shortcut F7
2c) Double click on file symbol
displayed (requirement:
attribute has been placed)
1) Select object

2a)
2b)
Sales Manager

2c)

SAP AG 2008

Point out where the file will show up in relation to the object. Bottom left.
If there is a link between an object and one or more external documents, this can be made visible in the
model using the attribute placement (see the module on attribute placement for details).
Normally the file symbol and the name of the file inc. the file path is displayed.
If the Title attribute (also in the System attributes group) is maintained, this attribute value is displayed
in the model.

© SAP AG SOA230 3-56


! " 1. 1 #$,

1) Select object(s)
2a)
Call up object properties:
2a) Object pop-up menu
Properties
2b) Object pop-up menu
Format -> Edit Attribute
Placements
2c) In menu bar: Format Edit
2c) Attribute Placements
2b)
2d) Double click on the object
2e) Keyboard shortcut Alt +
Enter
2f) Toolbar icon:

SAP AG 2008

The name of an object is automatically placed in the object when it is created.


Other attributes maintained can be displayed in the model using Attribute Placement.
This is done in the Object properties under Format Edit Attribute Placement (Objects)

© SAP AG SOA230 3-57


! " 1. 1 &$,

3) Click on Add

Select Add for additional


attributes to be placed.

Shows the position in/around the


object that the attribute will be placed

SAP AG 2008

Note: The window will tell you if you are placing object or model attributes.
Attribute placement
The "Restore ARIS Default" button allows settings previously made to be reset to default values.
The font format of individual placed attributes can be changed quickly and conveniently using the
pop-up menu.

© SAP AG SOA230 3-58


! " 1. 1 %$,

4) Select attributes to be placed (multiple selections possible).

Maintained attributes are marked with

TIP
Placing a check here means that only maintained
(populated) attributes are displayed for selection.

SAP AG 2008

You can select multiple attributes.


Use the ‘show only maintained attributes’ feature.

© SAP AG SOA230 3-59


! " 1. 1 ,$,

5) Select attribute

6) Determine position of
attribute and type of display Customer data

SAP AG 2008

Attribute placement – Positioning the attributes


For each attribute, the position at which it is to be displayed is specified.
Several attributes can be placed at one position.
The sequence of multiple attributes placed at one position can be changed as required.

© SAP AG SOA230 3-60


! " 1 #$&

Connection attributes are placed in the same way.


Multiple connections can be selected, including those of
different types.

2a) Connection pop-up


menu Properties
2b) Double click on the
connection
2c) Keyboard shortcut Alt +
Enter
2d) Toolbar

1) Select connection(s)

SAP AG 2008

Connection attributes can be shown in models using the same process as with object attributes

© SAP AG SOA230 3-61


! " 1 &$&

3) Determine position of Process 1


is process-oriented superior
attribute and type of display
is predecessor of
Process 1.1 Process 1.2 Process 1.3

SAP AG 2008

Determine the position of the attribute and type of display.

© SAP AG SOA230 3-62


1 ! " 1.

When an object is selected, its attributes are marked by a


dashed line. This enables you to identify which attribute
belongs to which object, allowing even attributes that are
placed a long way from the object to be located.

system

Customer request

Time of generation:

Object and connection attributes can be placed at different


positions directly in the model window. To do this, after
selecting simply click on the plus symbol on the selection frame
and drag the attribute to the desired position.

SAP AG 2008

You can drag the attribute placement in a model.

© SAP AG SOA230 3-63


! 1. $ 1

Object and Connection Attributes placed in the model are also


removed in the Attribute Placement window.

1) Select attribute to be removed 2) Click on Remove

SAP AG 2008

With a simple push of a button, you can remove placed attributes.

© SAP AG SOA230 3-64


"
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Business Architecture
Catalog
Business Footprint Organisation /
Process Flow View

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
Interface Catalog
Business Architecture User Location View
Application Migration

Use Case View System /


Organization Matrix
Business Architecture
View
Enterprise
Manageability View

Event View Data .


Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Business Architecture
Data Entity Hierarchy
Data Entity / Info
Component Catalog Data Security View

Business Footprint
View
View
Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

This slide shows the SAP EAF product flow with Business Architecture views.

© SAP AG SOA230 3-65


+

Catalog, Matrix or Purpose


View
Business Footprint A Business Footprint view describes the links between business goals, organizational
View units, business functions and services, and maps these functions to the technical
components delivering the required capability.

A Business Footprint view demonstrates only the key facts linking organization unit
functions to delivery services and is utilized as a communication platform for senior
(CxO) level stakeholders.
Business Service / The Business Service / Information view shows the information needed to support one or
Information View more Business Services. The Business Service / Information view shows what data is
consumed by or produced by a Business Service and may also show the source of
information.

Functional The purpose of this view is to show on a single page the capabilities of an organization
Decomposition View that are relevant to the consideration of an architecture.

By examining the capabilities of an organization from a functional perspective, it is


possible to quickly develop models of what the organization does without being dragged
into extended debate on how the organization does it.

SAP AG 2008

The purpose of each core view is described here.

© SAP AG SOA230 3-66


( + #$&

Catalog, Matrix or Purpose


View

Organization An Organization Decomposition view describes the links between Actor, Roles and
Decomposition Location within an organization tree.
View An organization map should provide a chain of command of owners and decision makers in
the organization.
Event View The purpose of this view is to depict the relationship between events and process.
Certain events such arrival of certain information (e.g. customer submits sales order) or a
certain point in time (e.g. end of fiscal quarter), causes work and certain actions need to be
undertaken within the business.

These are often referred to as “Business Events” or simply “Events” and are considered as
“triggers” for a process.

The view could be adapted to show event variation across global business units to highlight
harmonization opportunities.
Goal / Objective / The purpose of a Goal / Objective / Service view is to define the ways in which a Service
Service View contributes to the achievement of a business vision or strategy.

Services are associated with the Drivers, Goals, Objectives and Measures that they
support, allowing the enterprise to understand which services contribute to similar aspects
of business performance.

SAP AG 2008

The purpose of each Extension view is explained here.

© SAP AG SOA230 3-67


( + &$&

Catalog, Purpose
Matrix or
View
Process The purpose of this view is to depict all models and mappings related to the “process’ meta model
Flow View entity. Process Flow views show sequential flow of control between activities and may utilize
“swimlane” techniques to represent ownership and realization of process steps. For example, the
application that supports a process step may be shown as a swimlane.
In addition to showing a sequence of activity, process flows can also be used to detail the controls
that apply to a process, the events that trigger or result from completion of a process and also the
products that are generated from process execution.

The view could be adapted to show process flow variation across global business units to highlight
harmonization opportunities.
Use Case A Use Case view displays the relationships between consumers and providers of Business Services.
View Business Services are consumed by Actors or other Business Services and the Use Case view
provides added richness in describing business capability by illustrating how and when that capability
is used.

The purpose of the Use Case view is to help to describe and validate the interaction between actors
and their roles to processes and functions. As the architecture progresses, the use case can evolve
from business level to include data, application and technical details.

SAP AG 2008

The purpose of each Extension view is explained here.

© SAP AG SOA230 3-68


+

Process Flow
SAP EA Framework Creator: system
Last change: 10/18/07 11:39:49 AM
L4 Inbound Logistics Type: EPC
Inbound Logistics

Transport Receive Order Goods


planning order ReConciliation Receipt

Inbound Logistics

Event-driven Transport
planning
Receive
order
Order
ReConciliation
Goods
Receipt
Process chain

The purpose of this view is to depict all models and mappings


related to the “process’ meta model entity. Process Flow views
show sequential flow of control between activities and may utilize
“swimlane” techniques to represent ownership and realization of
process steps. For example, the application that supports a
process step may be shown as a swimlane.
Process flow views are useful in elaborating the architecture with
subject specialists, as they allow the specialist to describe “how
the job is done” for a particular function. Through this process,
each process step can become a more fine grained function and
Model Type can then in turn be elaborated as a process.

SAP AG 2008

This shows the process flow view description and an example from the FASST case study. The process
flow is created using an Event-driven process chain (EPC) in ARIS

© SAP AG SOA230 3-69


+

Process Flow
SAP EA Framework Creator: system
Last change: 10/18/07 3:23:24 PM
Events-Process View Type: EPC
Inbound Logistics
Catalog Management
Function
Transport Receive Order Goods
planning order ReConciliation Receipt

Activate Global Global Catalog Publish Global


Catalog Activated Catalog

Event-driven New Country Create New New Country

Process chain
Added Catalog
Country(local)
to BEEST Created
Business Catalog

New Sales Country Catalog


Update Global Global Catalog Update Country Activate Country
Package Personalized and
Catalog Updated Catalog Catalog
Released Updated

The purpose of this view is to depict the relationship between


events and process.
Certain events such arrival of certain information (e.g. customer
submits sales order) or a certain point in time (e.g. end of fiscal
quarter), causes work and certain actions need to be undertaken
within the business. These are often referred to as “Business
Events” or simply “Events” and are considered as “triggers” for a
process. It is important to note that the event has to trigger a
Model Type process and generate a business response or result.

SAP AG 2008

This shows the event view description and an example from the FASST case study. The event view is
created using an Event-driven process chain (EPC) in ARIS

© SAP AG SOA230 3-70


+

Process Flow ARIS Definition SAP EAF Definition


Inbound Logistics

Transport
planning
Receive
order
Order
ReConciliation
Goods
Receipt
Function Function Process, Function

Event Event Event

Event-driven
Process chain Role Role Role
Application
system Application Application
type System, Service System, Service

Risk Risk Gap

Control
Control Control

Model Type Object Types

SAP AG 2008

We show here the main elements of the process flow and event view.

© SAP AG SOA230 3-71


+

Process Flow

Inbound Logistics

Transport Receive Order Goods


planning order ReConciliation Receipt

Organizational Actor Role


unit
contributes contributes
to to
is technically
responsible for

Event-driven Event
activates Process creates Event activates Process
produces Product/
Service
Process chain is carried
occurs at
out at
supports

Control Gap Service

Model Type Relationship Types

SAP AG 2008

We show here the main relationship types of the process flow and event view.

© SAP AG SOA230 3-72


( !

Booking
Start inquiry
received

Check
F1 booking
inquiry

Booking
E1 inquiry
complete

F2 F3 Book flight Book hotel

E2 E3 Flight booked Hotel booked

F4 Create invoice

Invoice
End
created

SAP AG 2008

Functions describe what you are doing and what are you doing it to.
Do not go into merging paths here, this is just and example of an EPC.

© SAP AG SOA230 3-73


/ " ) !

Function: Technical task performed on an (information) object


in support of one or more business objectives
Synonyms: activity, process step, procedure…
Naming convention for functions in an EPC:
Action + Information object

Action
Approve
customer order Information object

SAP AG 2008

The action states what are you doing and what are you doing it to.
We will use the term function, not activity throughout the training.
Note these are naming conventions, not rules.

© SAP AG SOA230 3-74


/ " ) !

Event: Describes a commercially relevant status of an


information object that occurs, which controls or influences the
subsequent sequence of a process.
Naming convention for "standard" events:
Information object + Change of status

Customer order Information object


approved
Change of status

SAP AG 2008

Naming convention. Reverse of function. Noun and verb


Commercially means that it is viable, workable, practical, and doable.

© SAP AG SOA230 3-75


) ! 6

After decision-making / test functions:


Incorrect: "Test performed"
Correct: Specify test results
A “test” function normally has at least 2 exclusive Events.

Perform Perform XOR:


test test Only one option

Test
Test Test
performed
ok not ok

WRONG! RIGHT!

SAP AG 2008

The XOR is used in combination with a function and events to show the typical decision making
process. In a flow chart this construct is shown using a diamond shape.

© SAP AG SOA230 3-76


( ! " )/

Independent parallel paths

Cancel customer
order

AND:
All options must occur for the
process to continue.

Customer
Customer order informed
canceled about
cancellation

SAP AG 2008

Neither one has to happen first, but the both have to happen before you go on.

© SAP AG SOA230 3-77


( ! "

At least one or all of the paths must be chosen.

Identify
customer
requirements OR = and / or:
At least one of the options

Customer Customer Customer


requirement= requirement= requirement=
hotel booking flight booking rental car booking

SAP AG 2008

A little bit of a different concept. From this function one or all of these paths need to be taken or 2 of
these have to be taken. Think of the Flight train hotel car options if I live in 200 miles from Washington
DC. If I’m going to DC, I only need car and hotel. If I’m going to California, I need flight, car and hotel.

© SAP AG SOA230 3-78


E1 E1

F1 F2 F1 F2

Who decides which path to take?

No XOR or OR after a SINGLE event!

SAP AG 2008

You cannot have an or or an xor after a single event. There is no decision or to do after that.

© SAP AG SOA230 3-79


Start Start
Paths must be merged again using
the same Connector used to create
F1 the branch. F1

E1

E1 E2

F2 F3 F2 F3

E2 E3
E2 E3

F4
F4

End
End

SAP AG 2008

This is a very logical rule. The operator at the top of the decision path, must be the same as the bottom
operator. Because the decision you made at the top, doesn’t change. At the top we already have decided
either one or the other occurred. The decision has already been made.
Note that left side has LO after event and right side has LO after function. Be sure to understand why.

© SAP AG SOA230 3-80


Multiple incoming/outgoing connections for a connector ?

NO!!

Meaning of operator is ambiguous

SAP AG 2008

You can have have EITHER


One incoming and multiple out going connectors OR
multiple incoming and one out going connector.

© SAP AG SOA230 3-81


7

Sequence Start Start

F1 F1

???
E1 E1

F2
F2 F3

E2
E2 E3

F3
Check chronological and logical dependencies

E3

SAP AG 2008

If you look at a process and see the left, ask your self is that really a process. Is there something else we
are missing. No process is that smooth. There are almost always alternative events and functions.

© SAP AG SOA230 3-82


8/ " 8

Every EPC begins with at least one start Event (or a Process
Interface).
Every EPC ends with at least one end Event (or a Process
Interface).
An Event is followed by either a Function or a Connector
(exception: end event).
A Function is followed by either an Event or a Connector.
Every Function has a single incoming Connection and a single
outgoing Connection.
Every Event has a single incoming Connection and a single
outgoing Connection (exception: start and end Events)
A Connector has either:
Multiple incoming connections and a single outgoing connections,
or
A single incoming connection and multiple outgoing connections

SAP AG 2008

This is a review of modeling rules for EPC models.

© SAP AG SOA230 3-83


9 2

Supply
Process Management

Area
 

Main Inventory
Management
Process

 

Goods
Process Receive

  
 

Receive
Shipping
Activity Notification

  

SAP AG 2008

Standard business process hierarchy concept from high level process to detail process.

© SAP AG SOA230 3-84


3 ( " !

SAP Solution
Map

SAP Solution
Manager BPR

Supply
Process Management

Area      

Enterprise
Main Inventory
Service Process 
Management

Inventory

Goods
Process Receive


Receive
HR APO Shipping
Activity Notification
FI/CO PM  
CRM
MM BW

Re-Documentation

SAP AG 2008

A mapping of SAP process information to the standard business process hierarchy.

© SAP AG SOA230 3-85


9 2

BUSINESS ARCHITECTURE SAP – Solution Composer


consists of
SAP.Industry Value
Chain consists of

(Macro-Level) is equivalent to SAP.Value Chain belongs to


Function Element

utilize belongs to
SAP.Business Scenario groups
is utiliized by Group

Business Service is part of

SAP.Business Scenario is a sequence of


is composed of

is part of
is used within covers
is covered by
SAP.Process SAP.Product
has a
(Micro-Level) is a variant of
Function
is part of SAP.Process
SAP.Process Step
Configuration Variant

SAP – Solution Manager

SAP AG 2008

The SAP EAF metamodel is very specific about how we define and models Functions and Processes;
this is because SAP EAF is TOGAF- compliant.
On the SAP EAF metamodel there is the generic concept of a Function. A certain level is indicated as a
Business Service which supports certain business capabilities through an explicitly defined interface and
is explicitly governed by an organization. Coarser granularity functions are considered as a Macro-Level
Function whereas fine granular functionality is named as Micro-Level function.
Since the borderline can be chosen in the context of a concrete enterprise or even in a certain area, the
level of similar granularity cannot be set in general.
Macro-Level Function could be related to all hierarchies beginning with SAP.Value Chain Element
down to SAP.Process although we expect in reality, that SAP.Process is a good candidate for a Business
Services.
The dotted lines illustrated that in principle SAP.Process could be either related to the Macro- or the
Micro level as well.
The current granularity of the existing SAP content leads to the point that process steps are mostly
located on the Micro-Level Function.

© SAP AG SOA230 3-86


" 3

ARIS Solution Manager

Business Process SAP Process


Hierarchy Hierarchy

Supply
Process Management

Area      

Main Inventory
Management
Scenario Scenario
Process 

Synchronization
Process

Goods
Receive
Process Process

Activity
Receive
Receive
Shipping
Shipping
Notification
Process Process
 Notification

Step Step
Release
Transaction Purchase
Requisition
TA TA

SAP AG 2008

This slides shows the mapping of the process hierarchy in ARIS to the hierarchy in SolMan if you are
using the SAP Solution Manager function and process content in ARIS.

© SAP AG SOA230 3-87


" ( ! :+ /; <

Model level:
P1 P2 P3 n

P1 P P Model level:
P2
E1 2 P1
3 n+1

E3 E5
F1

F3
E2
F5 F6

E4
F2
E6 E7

F4

E3
F7
E5

P2
E8
P3

SAP AG 2008

Model level n: The objects in this model (VACD) are level n objects (level of detail).
Model level n+1: The green functions in the EPCs are level n+1 objects. These are sub-functions of the
superior functions from level n.
The process interfaces are an exception in the EPCs. They are level n objects (occurrence copies).
Occurrence copies of the upstream and downstream functions for the detailed function in the source
model (in this case level n VACD) are created in the level n+1 EPCs.
In order to identify these immediately as process interfaces, their symbol is changed to the Process
interface symbol (-> Object Properties -> Properties -> Format -> Object Appearance -> Symbol)
Copy the function before /after and events before and after. Think about it logically. The ending event
for process one is logically the trigger event for process 2, whose ending event is the trigger event for
process 3.
To decompose 2 you have to tell audience you are in the middle of a process.
2nd part of rule is to do the same with events.
Then it becomes an occurrence copy. Which occurs twice but doesn‘t necessarily have to be done twice.
It becomes clearer once you start to model.
All the process interfaces are navigation points.

© SAP AG SOA230 3-88


- " "

Superior Model – Sub-process Model –


Model level n Model Level n+1

Event 1

Function 1
Function 1 Previous Function
Occurrence
Copies!
Event 2 Event 2 Start event
Previous and subsequent
Events and Process
Function 2
interfaces are occurrence
copies
Event 3 Event 3 End event
Occurrence
Copies!
Function 3 Subsequent Function
Function 3

Event 4

SAP AG 2008

This slide shows how an interface is composed on the first and second level.

© SAP AG SOA230 3-89


"
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View

Business Architecture User Location View Interface Catalog


Application Migration
View
Service Information View System /
Organization Matrix
Enterprise
Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We will now look at the business architecture service information view.

© SAP AG SOA230 3-90


" ! + #$%

Service Information SAP EA Framework


Creator: system
Last change: 10/18/07 3:30:10 PM

Catalog Authoring
Service-Information View Type: IS context model
Service

Product Master Price


Catalog Catalog
Authoring Personalization Management
Service Service

IS Context Model Product Config Customer


Price Invoice Quota Contracts
Master Rules Master

Catalog Catalog
Search Comparison &
Service Promotion

The Business Service / Information view shows the


information needed to support one or more Business
Services. The Business Service / Information view shows
what data is consumed by or produced by a Business
Service and may also show the source of information.
The Business Information view shows an initial
representation of the information present within the
architecture and therefore forms a basis for elaboration
Model Type and refinement within the Data Architecture phase.

SAP AG 2008

This shows the service information view description and an example from the FASST case study. The
service information view is created using an IS Context model in ARIS

© SAP AG SOA230 3-91


" ! + &$%

Service Information ARIS Definition SAP EAF Definition


Catalog Authoring
Service

Functional
block Business Service Business Service
Product Master Price

Data Entity Data Entity Data Entity


IS Context Model

Role Role Actor

Document
Information Carrier Contract

Object Types
Model Type

SAP AG 2008

We show here the main elements of the service information view.

© SAP AG SOA230 3-92


" ! + %$%

Service Information
Catalog Authoring
Service

Contract

Product Master Price

provides input for


calls

IS Context Model

is input for Business has output of


Data Entity Service Data Entity

can be user
is owner of accesses

Actor

Relationship Types
Model Type

SAP AG 2008

We show here the relationships of the service information view

© SAP AG SOA230 3-93


!! 2 +
Business Footprint View can be user Functional Decomposition View
Organizational unit Organizational unit Service Abstract Service
(EPC) (IS Context Model)
Business Service
is technically responsible for is technically responsible for supports

is predecessor of is predecessor of Business Service


Process Function Function Requirement

Function Function
supports supports

Functional Decomposition
calls
Driver Objective View
(IS Context Model)
Service/Information View Data Entity
is input for
Business Service
has output of
Data Entity
(IS Context Model)

can be user
is owner of accesses

Actor
Actor
Application transmits data to Application
can be user can be user
Component Component

is input for has output of calls


Application
Service
Component
Data Entity Data Entity

can be located at can be located at

has output of is input for


Location
Interface Application Application Application and User Location
Communication View View (EPC)
SAP AG 2008 (EPC)

This view shows how the SAP EAF metamodel is related in terms of the key views.

© SAP AG SOA230 3-94


!! 2

This is the end of the 3rd Unit ! 5


"
You should now understand SAP Enterprise Architecture Resource Base

Released to the Open Group

Released to the Open Group


Framework extensions Extensions
The SAP EAF Business Usage Guidelines SAP Business
Reference Models
Architecture Architecture
Development
Content
Metamodel
Method
How the views of the Business Templates, Examples and Case
SAP Technology
Reference Models
Studies
Architecture are create din ARIS
SAP Mapping Extensions
How to model in ARIS SAP Tooling Extensions
SAP Content SAP Implementation
How to maintain object Tools Tools
EA Modelling Tools

information in ARIS TOGAF Architecture TOGAF


Development Method Resource Base
The next Unit explains the
Application Architecture

SAP AG 2008

© SAP AG SOA230 3-95


© SAP AG SOA230 3-96
Exercise

Unit: Unit 3 – Business Architecture


Topic: Organizational Modeling

At the conclusion of this exercise, you will be able to:


• Familiarization with the Business Organization model type

1) Create a Group under Main group/Business Architecture call ‘Views’.


2) Create an Organizational Chart model and call it FASST
Organization within the Business Architecture/Views group of your
database. Then create the Organizational Chart model with the
information supplied.
3) Save and Close your model

1. The FASST Organizational Unit consists of and is composed of to the following


Organizational Units:
• Supplier Collaboration and Operational Procurement
• Finance
• FASST Consulting Services
• Sales and Marketing
• Manufacturing
• HR

© SAP AG SOA230 3-97


© SAP AG SOA230 3-98
Exercise
Unit: Unit 3 – Business Architecture
Topic: EPC Modeling

At the conclusion of this exercise, you will be able to:


• Familiarize yourself with the Event-Driven Process Chain (EPC)
method
• Be able to model EPC for Process Flows
1) Create a EPC named Catalog Management under the Business
Architecture/Views group
2) Create the content of the EPC based on the information provided
below
3) Save and close the model

1. The Catalog Management Process


• An new sales package is released
• It must be determined whether a global catalog update is required
• If yes than the global catalog is updated
• In any case the country catalog must be updated
• Once the catalogs are updated they are activated
• Activated catalogs are than published

© SAP AG SOA230 3-99


© SAP AG SOA230 3-100
Unit 4 - Application Architecture

SAP AG 2008

© SAP AG SOA230 4-1


Unit 1 - Overview of SAP Enterprise Architecture Framework
Unit 1 – Introduction to ARIS

Unit 2 – Architecture Vision

Unit 3 – Business Architecture

Unit 4 – Application Architecture

Unit 5 – Data Architecture

Unit 6 – Technology Architecture

Unit 7 – Summary

SAP AG 2008

Application Architecture is the first part of the Information Systems Architecture phase of SAP EAF.
This unit shows an overview of the Application Architecture and how to model it in ARIS.
We will also show what the key models are and how to use occurrence and definition copy in ARIS

© SAP AG SOA230 4-2


Prelim:
Framework and
Principles

The Information Systems


Architecture phase is about
A. defining As-Is and To-Be
Architecture
H.
Architecture
Vision
B.
Business
application and data
architectures for the
Change
Management Architecture

organization, detailing the


roadmap towards the To-Be
C.
G.
Implementation
Governance
Requirements
Management
Information
Systems
architecture and identifying
key work packages in the
Architectures

roadmap.
F. D.
Migration
Technology
Planning
Architecture

E.
Opportunities
and Solutions

SAP AG 2008

The Information Systems Architecture Phase is about defining both the application and data
architecture.
The scope of the business processes supported in this phase is limited to those that are now or need to be
supported by Information Technology
The objective here is to define the major kinds of application system necessary to process the data and
support the business architecture defined in Phase B.

© SAP AG SOA230 4-3


!

IS Architecture involves a combination of Data


Prelim:
and Applications Architecture, in either order.
Framework and
Principles
SAP EAF recommends Application Architecture
is performed first :
Packages or packaged services provide a
A.
Architecture
combination of technology infrastructure and
H. Vision Application business application logic
B.
Architecture
Change Business Architecture
Management Architecture
Some organizations take an application-driven
approach, where key applications form the core of
mission-critical business processes,
C.
G.
Implementation
Requirements Information
Systems
SAP EAF assumes some functionality will be
Management
delivered through a packaged or packaged
Governance Architectures

service solution
F. D.
The Application Architecture phase must examine
Migration
Planning
Technology
commercially available solution models in addition
Architecture
Data
E. Architecture
to traditional requirements and current state
Opportunities
and Solutions analysis.
Commercially available templates may need to be
adopted at the expense of the business ideal.
In general, SAP EAF recommends that
architecture definition is an iterative activity and
that not all answers can be completed in a single
cycle.

SAP AG 2008

Information Systems Architecture can be broken down into Application and Data Architecture.
In a landscape dominated by packages or packaged service providers, it makes sense to model
Application Architecture first.

© SAP AG SOA230 4-4


"

Templates and Examples


BEEST Case Study

SAP EAF Templates


Inputs
Outputs
Reference
Material

TOGAF
Updated Statement of Work
SAP EAF Glossary
Current State Application Architecture
SAP EAF to SAP Terminology Mappings
Current State Data Architecture
Phase Specific Inputs

Target Application Architecture


ADM IS Architecture Narrative
Information Target Data Architecture
SAP EAF IS Architecture Worksheet
Systems Gap Analysis Results
SAP EAF Application Architecture Narrative
Updated Business Requirements, IS
Architecture Requirements, Policies, Standards,
SAP EAF Data Architecture Narrative
Guidelines and Specifications
SAP EAF Metamodel and View Definition
Phase Technology Requirements

Steps
Pre-Existing or Previous

Statement of Work
Application Architecture Baseline
Phase Inputs

Architecture Vision
Data Architecture Baseline
Architecture Principles Reference Models, Viewpoints and Tools
Develop Application Architecture Models
Business Architecture
Develop Data Architecture Models
Stakeholder Map
Perform Gap Analysis
Tailored Architecture Process and Metamodel Select IS Architecture Building Blocks
Define Roadmap
Resolve Impacts Across the Enterprise

SAP AG 2008

This slide show the key inputs, steps and outputs involved in Information Systems Architecture.
The precise steps are covered in SOA200.

© SAP AG SOA230 4-5


# $

Resolves realised by

(Business, Information System)


Contained in Core, /IS split supports the Business / IT Alignment
umes Is realised Is implemented on
through
Is processed Operates Provides
by on Implements platform for

Logical Application Logical


Data Entity Com
Component
Infrastructu
Resides within Ext

Encapsulates Is Realised by Realises


gical Information Physical Application
Component Component Physical
Data Extension Infrastructure Com
Consolidation Extension
Encapsulates Is Hosted in
Is Hosted in

APPLICATION
ARCHITECTURE

SAP AG 2008

This slides shows how the SAP EAF metamodel is populated in this phase
Start by identifying the Information System Services
Business services specifically provided by an automated IT-based solution
E.g. Purchase Request Processing
It is important to define what we mean by Logical and Physical Applications :
A Logical Application Component is an encapsulation of application functionality that is independent of
a particular implementation.
E.g. Organization X Purchase Request Processing Enterprise Service
An application, application module, application service or other deployable component of functionality.
E.g. A configured and deployed instance of the SAP Purchase Request Processing Enterprise
Service

© SAP AG SOA230 4-6


Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Business Footprint
Catalog
Organisation / Application Architecture

Process for Creating an Architecture


Application Architecture
View Actor Catalog

Goal / Objective/
Interface Catalog
Application
Service View Portfolio Catalog
Driver / Goal / Process / Event / Control /
Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing /
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

Populating the catalogs of the Application Architecture is generally recommended as the first step.

© SAP AG SOA230 4-7


#

Catalog, Matrix or Purpose


View
Application The purpose of this catalog is to identify and maintain a list of all the applications in the
Portfolio Catalog enterprise. This list helps to define the horizontal scope of change initiatives that may impact
particular kinds of applications.

Existing application registries and repositories, such as SAP’s Solution Manager and System
Landscape Directory products also provide input into this catalog from an As-Is and To-Be
perspective

The Application Portfolio Catalog contains the following metamodel entities :

Information System Service


Logical Application Component
Physical Application Component
Interface Catalog The purpose of this catalog is to scope and document the interfaces between applications to
enable the overall dependencies between applications to be scoped as early as possible.

The Interface Catalog contains the following metamodel entities :

Logical Application Component


Physical Application Component
Application communicates with Application relationship

SAP AG 2008

The two main catalogs used in Application Architecture – are the applications, and the interfaces
between those applications.

© SAP AG SOA230 4-8


#

SAP AG 2008

This shows the Application Architecture catalog example from the FASST case study.

© SAP AG SOA230 4-9


Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal Application Architecture


/ Objective/
Service View
System-Function
Driver / Goal / Process / Matrix
Event / Control /
Event View
Objective Catalog Product Catalog

Contract / Measure
Service / Function Catalog
Service / Information Application Architecture
Business Interaction
Catalog View Matrix
Role-System Matrix
Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View
Application Architecture
Data Lifecycle View
System-Organization
Data Migration View
Matrix
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

Once the catalogs are populated, the matrices from the Application Architecture can be established.

© SAP AG SOA230 4-10


$

Catalog, Matrix or Purpose


View
System / Business functions are performed by organizational units. Some of the functions and
Organization Matrix services performed by those organizational units will be supported by IT systems

The relationship between these two entities is a composite of a number of metamodel


relationships that need validating :
Organization Units own Services
Actors that belong to Organization Units use Services
Services are realized by Logical/Physical Application Components
System / Role People in an organization interact with systems. During this interaction, these people
Matrix assume a specific role to perform a task; for example, product buyer.

The relationship between these two entities is a composite of a number of metamodel


relationships that need validating :
Role accesses Function
Function is bounded by Service
Services are realized by Logical/Physical Application Components
System / Function Business functions are performed by organizational units. Some of the business functions
Matrix and services will be supported by IT systems

The relationship between these two entities is a composite of a number of metamodel


relationships that need validating :
Function is bounded by Service
Services are realized by Logical/Physical Application Components

SAP AG 2008

The key matrices help to link the applications/systems between the key parts of the Business
Architecture already defined – that is:
Organisation Units
Roles
Functions

© SAP AG SOA230 4-11


# $

SAP AG 2008

This shows the catalogs and matrices of the application archietcture in ARIS.

© SAP AG SOA230 4-12


$

A matrix in ARIS shows a two dimensional table with


relationships between included objects.

Included Objects

Included Objects Relationships

Included Object Types

Matrix Editor
SAP AG 2008

Here we see the composition of a matrix in ARIS.

© SAP AG SOA230 4-13


%

Catalog, Matrix or Purpose


View

Application to The purpose of this view is to depict all models and mappings related to “communication’
Application between Applications in the meta model entity.
Communication
View It shows application components and interfaces between components.

Interfaces may be associated with Data Entities where appropriate. Applications may be
associated with business services where appropriate. Communication should be logical and
should only show intermediary technology where it is architecturally relevant.
Application / User This view shows the geographical distribution of applications.
Location View
It can be used to show where applications are used by the end user; the distribution of
where the host application is executed and/or delivered in thin client scenarios; the
distribution of where applications are developed, tested and released; etc.

SAP AG 2008

The two core views in SAP EAF Application Architecture are shown here – they are the most useful
views – showing how applications interact with other applications, and how applications are accessed by
users at which locations.

© SAP AG SOA230 4-14


Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location
Catalog Application Architecture
Process Flow View
Business Footprint Organisation /

Process for Creating an Architecture


View
Application Architecture Actor Catalog
Application Communication View
Goal/ Objective/
Application Migration View
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We will now cover the application migration view and the application communication view.

© SAP AG SOA230 4-15


%

Application – SAP EA Framework Creator: system


Last change: 10/10/07 8:01:20 AM
Application Application - Application Communication View
Type: Program flow chart

Communication
Application transmits data to Application
Application transmits data to Application
Component Component
Component Component
transmits data to transmits data to
Interface

is input for has output of

Data Entity Data Entity

Program Flow has output of is input for

Chart Interface

The purpose of this view is to depict all models and


mappings related to “communication’ between
Applications in the meta model entity.
It shows application components and interfaces
between components. Interfaces may be associated
with Data Entities where appropriate. Applications
may be associated with business services where
appropriate. Communication should be logical and
should only show intermediary technology where it
is architecturally relevant.
Model Type

SAP AG 2008

The application communication view is shown here as an example from the FASST case study. The
application communication view is modeled in ARIS using a program flow chart.

© SAP AG SOA230 4-16


$ # % &'(

Application Migration SAP EA Framework Creator: system


Last change: 10/10/07 8:03:28 AM
Type: Program flow chart
Application Migration View

Application transmits data to Application


Component Component

transmits data to transmits data to


Interface

Application transmits data to Application


Component Component

Program Flow
Chart transmits data to transmits data to
Interface

This view identifies application migration from AS-IS


to TO-BE application components. It enables a more
accurate estimation of migration costs by showing
precisely which applications and interfaces need to
be mapped between migration stages.

Model Type

SAP AG 2008

The application migration view is shown here as an example from the FASST case study. The
application migration view is modeled in ARIS using a program flow chart.

© SAP AG SOA230 4-17


$ # % )'(

Application Migration ARIS Definition SAP EAF Definition

Application
Component
transmits data to Application
Component
Application
transmits data to
Interface
transmits data to
system type System, Service System, Service

Data Entity Entity Data Entity


Program Flow
Chart

Interface Interface Interface

Logical Information
Logical Information
Component Cluster
Component

Object Types
Model Type

SAP AG 2008

Here we see the main components of the application migration view.

© SAP AG SOA230 4-18


$ # % ('(

Application Migration

Application
Component
transmits data to Application
Component
Application transmits data to Application
transmits data to transmits data to
Component Component
Interface

is input for has output of


Program Flow
Chart Data Entity Data Entity

has output of is input for

Interface

Relationship Types
Model Type

SAP AG 2008

We see here the main relationships of the application migration view.

© SAP AG SOA230 4-19


#

The Program Flow Chart model type is used to map interfaces


between IT systems.
Ideally, the Program Flow Chart should be assigned to the IT
system.

Application transmits data to Application


Component Component

transmits data to transmits data to


Interface

Relationship type:
“transmits data to”

To map interfaces, IT systems (object type: application system


type) are connected to each other via relationships (relationship
type: transmits data to).
SAP AG 2008

The Program Flow Chart model type is used to map interfaces between IT systems.
An interface can be modeled as a relationship ‘transmits data to’ or as an interface object.

© SAP AG SOA230 4-20


# *+ &')

Another Program Flow Chart, in which the transferred used are


individually mapped, can be assigned to each relationship.

Application transmits data to Application


Component Component

is input for has output of

Data Entity Data Entity

has output of is input for

Interface

A separate Program Flow Chart is assigned for each interface


(and direction!).
However, the transfer of multiple sets of data via the same
interface between two IT systems is shown in the same
diagram.

SAP AG 2008

The ‘transmits data to’ relationships can have a Program flow chart assigned that provide more detail of
the interface.

© SAP AG SOA230 4-21


# *+ )')

Relationship Type:
“transmits data to”

Application transmits data to Application


Component Component

has output of
is input for

Data Entity Data Entity


Object Type:
“Application
Relationship type: System Type”
is input for
“has output of” has output of

Interface

Relationship type:
Object Type: “is input for”
Class”

SAP AG 2008

Components and relationships of the program flow chart for the application to application
communication view

© SAP AG SOA230 4-22


, - . #

Model level = Occurrence level


Execution Board
Examples Inc. A model contains occurrences,
which are graphical representations of
object definitions.
Department 1 Department 2 Department 3

Database level = Definition level


When you create an occurrence in a model,
an entry known as the object definition is
Department 3 created in the ARIS database.
This stores all the object information:
attributes, connections etc.

SAP AG 2008

The first time an object is created ("occurs") in a model, the associated object definition is saved in the
same group in which the model is also stored.
The term object is often used instead of object definition. However, the term object is also often used in
the sense of object occurrence. The context determines whether "object" refers to an object definition or
an object occurrence.
Objects are independent units that are used in models. Therefore an object never "belongs" to a
particular model.

© SAP AG SOA230 4-23


Many objects occur in several contexts and thus in a number of
models, e.g.
Organizational Unit in both Organizational Chart and in EPC’s
Application System Type in both Application System Type Diagram
and in EPC’s
The object that exists in the ARIS database is therefore re-used
in several models.
To ensure that the objects are identical, an Occurrence Copy (of
the object definition) must be created.

SAP AG 2008

Occurrence copies can be made of individual objects, multiple objects (including different object types),
model extracts (objects and connections), entire models and multiple models.
ARIS provides many different ways to create occurrence copies because they are the most used types of
object/model copies and for many basic modeling needs, the only copying mode necessary.
It should be confirmed with the ARIS Administrator and/or the Business Process owner whether or not
to use something besides an occurrence copy (i.e. Definition or variant copy)

© SAP AG SOA230 4-24


Purchasing
Executive Board
Example PLC

Marketing,
Finance &
Vertrieb & Purchasing Purchasing
Administration
Services

Purchasing

One object definition with multiple occurrences


(in one model or in different models)
SAP AG 2008

Changes made to an object, e.g. changing or maintaining attributes, are written directly to the object
definition and are thus available to all occurrence copies immediately.
Therefore, when making changes to an object it is not necessary to check the points at which the object
occurs in order to make the same changes there.

© SAP AG SOA230 4-25


,

Many modeled structures can occur several times in a similar


form, e.g.
Domestic organizational structure similar to that in other countries
Similar processes in different plants, branches
To prevent the model from having to be completely remodeled
in such cases, an independent copy of an existing model can be
created.
This independent copy is known as a Definition Copy.
Definition copies of objects, model extracts or complete models
can only be created using Copy and Paste as Definition Copy.

SAP AG 2008

Like occurrence copies, definition copies can also be made of individual objects, multiple objects
(including different object types), model extracts (objects and connections), entire models and multiple
models.
Whether a definition copy is useful must be decided in individual cases. Changes to attributes or
structures often involve more work than creating a new object / model / model extract.
When a definition copy is created, the edited attribute values of the original object / model are retained.
The GUID and attributes such as the creation time, date of last change, creator and last processor are
changed.
In this case, it is necessary to check whether the attribute values are really correct for the definition
copy.
Note: To avoid objects / models with the same names (homonyms), the name of at least one of the
objects / models (original or definition copy) should be changed.

© SAP AG SOA230 4-26


,

Purchasing Purchasing
Home Abroad

Original Definition copy

Purchasing Purchasing
Home Abroad

Object occurrences resulting from definition copies


have their own, independent object definitions.
SAP AG 2008

Changes made to an object are written to the object definition of that object. This does not affect the
definition copy as it relates to a different object definition.
Let‘s say that you have local purchasing processes locally and abroad, but there are some differences
that need to be identified and documented. Maybe its customs issues or something similar to that. You
can create a Definition Copy. A definition copy is an independent object in your database. An
occurrence copy is the same object definition from the database level, but the object can occur many
times within a database maintaining all of the same attributes, properties and relationships.
Once you create a Definition copy, the Attributes remain the same, but the relationships between other
objects and models changes. Also, the time, date and creator of the definition copy changes also.
The problem with creating a definition copy when you really mean to create an occurrence copy is that
your database becomes jumbled and there will be several definition copies of one process or object
when only one is necessary. This will hamper your reporting and make your reporting inaccurate.

© SAP AG SOA230 4-27


%

Purchasing Purchasing
Home Abroad

Master Variant

Purchasing Purchasing
Home Abroad

Variant link between Master and Variant(s)

SAP AG 2008

Here we are asking ARIS to keep tabs on this object that is a variance copy.
When a variant copy is created, new objects are created at the definition level for all objects used in the
models. Occurrences are then created in the copied models on the basis of these new objects. Once
created, the following relationship applies between the copied objects and models: The source object
(source model) is the master of the copy. The copy is the variant. To create variants in the target group,
the user logged in requires at least write privileges in the target group.
Variants can be used when formally comparing AS IS and TO BE process maps.

© SAP AG SOA230 4-28


*+ &'/

Alternative 1: Occurrence Copy using object placement in model


Case 1.1: Object name is completely known

1) Select object (symbol)

2) Place object in model and enter object name

IMPORTANT: In order to be able to make Occurrence Copies of


an object, the modeler must have read privileges for the group
in which the object is saved.

SAP AG 2008

Advantage:
The modeler does not need to know which group contains the object definition for the object he
wants to make an occurrence copy of.
Disadvantage:
The modeler must know the (approximate) name of the object.
Only one occurrence copy of an individual object can ever be created.

© SAP AG SOA230 4-29


*+ )'/

The selection list shows all objects whose name matches the
name of the object placed.
If there are several objects (of the relevant object type) with the
same name, multiple objects can be selected ( homonyms).

3)
3) Click on Use an existing object
4a) Select object in list and click on OK or
4b) Double click on the object
An Occurrence Copy is created

4a)

SAP AG 2008

Selecting "Create or use a new object with this name" creates a new object definition.
In this case, there will be objects with the same name in the database. As this is to be avoided where
possible, it is recommended that a different name be selected.
Always use an existing object.
Go to that object. Find out who created it then send them an email asking about the object to be sure.

© SAP AG SOA230 4-30


*+ ('/

Case 1.2: Object name is partially known

3) 1) Select object (symbol) from Toolbar

Result of search for


objects with same name

2) Place object in model and enter at least 2 letters (characters) from


the object name
3) Run a DB-wide search for objects with the same name
4) Select object (double click)

SAP AG 2008

An asterisk (*) can be used as a wildcard, including at the beginning of the object name.

© SAP AG SOA230 4-31


*+ 0'/

Alternative 2: Occurrence Copy from Explorer Tree in Designer


module
Explorer Tree and Objects filter must be active

1) Select group in which the object is contained


2) Select object
3a) Drag object into the model using Drag & Drop
3b) Copy object
- In pop-up menu Copy or
- Keyboard shortcut Ctrl + C
and paste into target model [see 4a to 4c]
SAP AG 2008

The modeler must know which group the object to be copied is in.
Only one occurrence copy of an individual object can ever be created.

© SAP AG SOA230 4-32


*+ 1'/

Pasting an object into the target model as an Occurrence Copy

4a) Model pop-up menu Paste


4b) Keyboard shortcut Ctrl + v
4c) Model pop-up menu Paste as Occurrence Copy

SAP AG 2008

You have to make sure that the object you want to paste into the model is “allowed” in that model.
You can’t paste an event into a VACD, because it is not allowed.
Note that they are creating occurrence copies, not definition. “Paste as” is the only way to create
definition copy. It is not easy to create a definition copy as it is an occurrence copy, which is why it is
not commonly used.

© SAP AG SOA230 4-33


$ *+ 2'/

Alternative 3: Occurrence Copy from a different model

1) Open the model containing the object


2) Select and copy the object (Ctrl + C)
3) Paste object into target model (Ctrl + V)
Occurrence Copies of multiple objects of different object types are possible.
Only the objects that are permitted by the method filter are transferred to the
target model.
SAP AG 2008

You can also create an occurrence copy from objects in another model:
1) Open the model containing the object
2) Select and copy the object (Ctrl + C)
3) Paste object into target model (Ctrl + V)

© SAP AG SOA230 4-34


$ *+ 3'/

Alternative 4: Occurrence Copy from the Explorer module


In the left-hand Explorer window, only one object can be selected,
in the right-hand Explorer window several objects, including
different types
The Occurrence Copies are created using Copy and Paste. To do
this, it is necessary to switch to Designer.

The Objects filter or tab must be active.

SAP AG 2008

Disadvantage:
Only objects from one group can be selected.

© SAP AG SOA230 4-35


$ *+ /'/

Alternative 5: Occurrence Copy from the Search dialog box


The Occurrence Copies are created using Copy and Paste.

Multiple objects possible, including different object types


and from multiple groups.

SAP AG 2008

Advantages:
The modeler does not need to know either the exact name of the object or the group in which the object
is located.
Occurrence copies of multiple objects are possible, including different object types and from multiple
groups, by selecting the relevant objects in the results list, copying them and pasting them to the target
model (as an occurrence copy).

© SAP AG SOA230 4-36


$

Occurrence Copies can also be created of model extracts


(objects and connections) and entire models.
To do this, the model extract (or all objects and connections) is
selected, copied and pasted to the target model.
Occurrence Copies of complete (or multiple) models can be
created in the Explorer tree.
Copy model(s) and paste to the target group.
To create occurrence copies of all models in a group, copy the
group and paste to a different target group.

SAP AG 2008

More alternative ways exist to create an occurance copy.

© SAP AG SOA230 4-37


4 # 5 # 6& 7

In Designer, the Occurrences tab in the Properties window for a


selected object shows the models in which occurrence copies
of that object are used.

Travel Agency 1) Select object


Fly away

2) In Object Properties window,


Flight
select Occurrences tab
Call Center
arrangement

Mrs Smith Mrs Brown

List of all models with model name/type, in which the object occurs. The
symbol used to represent the object in the model is also displayed.

SAP AG 2008

We can see here how to navigate from one model to another using the object property information of an
occurrence copy.

© SAP AG SOA230 4-38


4 # 5 # 6&*7

It is possible to open a model in the Properties window:


Select model Open Model or
Double click on the model
The model is opened and the "source" object is selected - it can
be brought into focus by zooming.

Booking inquiry
received

Check booking Mrs Brown


inquiry

Booking inquiry
complete

SAP AG 2008

You see the result here as the tool navigates to the object in the other model.

© SAP AG SOA230 4-39


4 # 5 #

As well as using the Properties Window in Designer it is also possible


to call up the object’s Properties from the object pop-up menu – both
in Designer and Explorer.
To do this, an Occurrence or the object definition must be selected.

Ocurrences in selected model

Calls up the object properties


SAP AG 2008

This is another way to access the properties of an object to see object occurrence information.

© SAP AG SOA230 4-40


*+

In the object‘s Properties, Occurrences is initially relevant for


navigation.

Properties include other important object information:


Attributes ( opens the object attribute list)
Relationships ( displays the relationships that the object is
involved in in the database)
Assignments ( shows the models assigned to the object)
Variants ( shows the variants / master for the object)

SAP AG 2008

Other information can also be accesses in the properties window.

© SAP AG SOA230 4-41


*+

All relationships (connections) that the source object is


involved in with other objects in the ARIS DB are displayed.
The other object involved in the relationship is also displayed.

For the objects involved in the Relationship,


the pop-up menu can be called up.

SAP AG 2008

In the relationships tab, all relationships (connections) that the source object is involved in with other
objects in the entire repository are displayed.

© SAP AG SOA230 4-42


8 %

Catalog, Matrix or Purpose


View

Process / System The purpose of this view is to clearly depict the sequence of events when multiple
Realization View applications are involved in executing a business process. It enhances the Application to
Application Communication View by augmenting it with any sequencing constraints, and
handoff points between batch and real-time processing.

Enterprise This view shows how one or more applications interact with application and technology
Manageability View components that support operational management of a solution.
This view is really a filter on the application-application communication view, specifically for
Enterprise Management class software.
Application This view identifies application migration from AS-IS to TO-BE application components. It
Migration View enables a more accurate estimation of migration costs by showing precisely which
applications and interfaces need to be mapped between migration stages.

Software This view breaks applications into packages, modules, services and operations from a
Engineering View development perspective. It enables more detailed impact analysis when planning migration
stages, and analyzing opportunities and solutions.
Software This shows how application software is structured and distributed across the estate. It is
Distribution View useful in systems upgrade or application consolidation projects.
This view shows how physical applications are distributed across physical technology and
the location of that technology.

SAP AG 2008

These Application extension views can be used to further present the Enterprise Model
SOA200 provides advice and guidance on choosing which extensions to use in different situations.

© SAP AG SOA230 4-43


Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Application Architecture Location Application Architecture


Process Flow View

Application &
Business User Location
Footprint
Catalog
View Actor Catalog Software Distribution View
Organisation /

Process for Creating an Architecture


View

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View
Application Architecture
Enterprise Manageability View Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We see here the application architecture views that will be modeled with the following ARIS method.

© SAP AG SOA230 4-44


'5 - % &'(

Application / SAP EA Framework Creator: system


Last change: 10/19/07 10:56:01 AM
User Location Application and User
Type: Access diagram

Location View
SAP R/3

Stuttgart

SAP R/3 SAP IPC DMS VMS

Stuttgart

Access diagram
Production and
Logistics

Sales and Marketing

This view shows the geographical distribution of


applications. It can be used to show where
applications are used by the end user; the
distribution of where the host application is
executed and/or delivered in thin client scenarios;
the distribution of where applications are developed,
tested and released; etc.
Model Type

SAP AG 2008

The application/user location view is modeled in ARIS with an Access diagram.

© SAP AG SOA230 4-45


'5 - % )'(

Application / ARIS Definition SAP EAF Definition


User Location
SAP R/3

Application
Stuttgart
system type System, Service System, Service

Organizational unit Organization Organization


Access diagram

Location Location Location

Person type: Role,


Actor Actor, Role
Person

Architecture Architecture Technology


element Element Component

Object Types
Model Type

SAP AG 2008

We see here the main elements of the application/user location view.

© SAP AG SOA230 4-46


'5 - % ('(

Application /
User Location
SAP R/3

Stuttgart

Actor
can be user can be user

Access diagram
Technology is relevant for Application calls
Service
Component Component

can be located at
can be located at

Location

Relationship Types
Model Type

SAP AG 2008

We see here the relationships of the application/user location view.

© SAP AG SOA230 4-47


, # *+ . &')

IT component (software)
SUN/Solaris
Describes all IT components that constitute
software
ARIS object type is application system type.

IT component (hardware)
HP 9001
Describes all IT components that constitute
hardware
ARIS object type is hardware component type.

IT component (guidelines) Policies

Describes all IT components that


constitute policies or documentation
ARIS object type is technical term.

SAP AG 2008

Primary components of an access diagram with description.

© SAP AG SOA230 4-48


, # *+ . )')

The architecture elements from the Architecture Set are used in order
to map the relevance of the architecture elements to the IT system.

Operating Systems Hardware Server

In addition, responsibilities can be mapped, such as, people,


positions, roles, and organizational units:

People David Sunday

Positions IT Manager

Roles Project manager EA

Organizational units FG-523

SAP AG 2008

Further primary components of an access diagram with description are shown here.

© SAP AG SOA230 4-49


, # .
Operating Systems
Connection Relationship Type: “is
relevant to”
Hardware Windows Programming
Operating Systems Operating
DBMS
server languages systems

Windows
HP 9001 DB/2 Java operating
systems

KIS (Loan Information Sys)


HP 9001 Connection Relationship Type:
KIS (Loan
Connection Relationship Type: “is responsible for”
information
“can run on” KIS system) Shows the employees
(Loan Information System) responsible for KIS
Hotline support
Peter Tuesday
Policies
Policies

Frank Bauer

Policies
DB/2
Connection Relationship Type: David Sunday
Connection Relationship Type:
“uses” KIS
“uses” KIS
(Loan Information System)
(Loan Information System)
SAP AG 2008

This is an ARIS style alternative of what can be shown in an Access diagram

© SAP AG SOA230 4-50


Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Migration View


Data Entity / Info
Application
Data Lifecycle View
Architecture
Data Entity Hierarchy
View
Component Catalog
Software Engineering View
Data Security View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing /
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We now will show how to create the Software Engineering view.

© SAP AG SOA230 4-51


# #% &')

Software Engineering SAP EA Framework Creator: system


Last change: 10/30/07 9:16:05 AM
Type: Application system type diagram
Software Engineering View

Cust omer Relatio ns Systems Warehouse Systems SCM Systems Sa le s and Marketing Systems

e-Price SAP BW e-Procurement FASST Porta l

Legacy CRM BIF

CRM DMS

Customer Relations Warehouse Systems SCM Systems Sales and Marketing Backend Systems Spare Parts Systems
Systems Systems

e-Procure- FASST
e-Price
e-Price SAP BW
SAP BW e-Procurement
ment
FASST Portal
SAP VMS
SAP VMS
Portal
mySAP
mySAP SCM
Legacy SCM
Application Legacy CRM
CRM
BIF
BIF
SAP R/3
SAP R/3

System Type CRM


CRM DMS
DMS

This view breaks applications into packages,


modules, services and operations from a
development perspective.
It enables more detailed impact analysis when
planning migration stages, and analyzing
opportunities and solutions.
It is ideal for Application Development teams and
Application Management teams when managing
complex development environments.
Model Type

SAP AG 2008

We see here a FASST case study example of the software engineering view.
The software engineering view is modeled in ARIS with an Application system type diagram.

© SAP AG SOA230 4-52


# #% )')

Software Engineering ARIS Definition SAP EAF Definition

Cust omer Relatio ns Systems Warehouse Systems SCM Systems Sa le s and Marketing Systems

e-Price SAP BW e-Procurement FASST Porta l

Application system
Class of Systems Module, Component
Legacy CRM BIF

CRM DMS

class

Application Application system


System Type type
Application, Service Application, Service

Application
system type

Model Type

SAP AG 2008

We see here a FASST example of the software engineering view.


The software engineering view is modeled in ARIS with an Application system type diagram.

© SAP AG SOA230 4-53


. , # 8
-

One of the first tasks in architecture management projects is to


document the existing system landscape. This involves
mapping hierarchical structures using a top-down approach.
SAP
BIF EA Framework Creator: system
Last change: 10/30/07 9:16:05 AM
Software Engineering View Type: Application system type diagram

Application Class

Customer Relations Warehouse Systems SCM Systems Sales and Marketing Backend Systems Spare Parts Systems
Systems Systems

e-Price
e-Price SAPBW
SAP BW e-Procurement
e-Procurement FASSTPortal
FASST Portal SAPVMS
SAP VMS

mySAP
mySAP SCM
SCM

Legacy
LegacyCRM
CRM BIF
BIF SAP
SAPR/3
R/3

CRM
CRM DMS
DMS

Embedded Systems

SAP AG 2008

Here we can see how we build the Software engineering view using application classes and embedded
systems.

© SAP AG SOA230 4-54


. , #
8 9
KIS (Loan
encompasses KIS
informationKIS 1.2 Relationship Type
system)
“Encompasses”
encompasses
KIS 1.0 ‘encompasses’
encompasses encompasses KIS 1.0 KIS 1.1 and KIS 1.2

encompasses

KIS KIS encompasses


KIS order KIS 1.1
creation processing

is predecessor of

In the application system type diagram, encompasses


KIS 1.2
there are essentially two relationship
Relationship Type
types between application system types: “Is predecessor of”
Encompasses ( system hierarchy) KIS 1.1 is
‘predecessor of’
Is predecessor of ( system sequence) KIS1.2

SAP AG 2008

Here is an example of how to build a system hierarchy.

© SAP AG SOA230 4-55


4 *+

When placing an object within an object, users can define whether


implicit relationships should be created between the “external” object
and the “internal” object.

KIS

KIS 1.0
If the box is checked, an
implicit relationship will be KIS 1.1
created

KIS 1.2

SAP AG 2008

The relationships here for nested objects are created implicitly.

© SAP AG SOA230 4-56


4 # . &')

It is particularly important to apply the general conventions when


naming IT systems. Names of IT systems vary greatly from
organization to organization. Where standard products are involved
(e.g., SAP), the following naming conventions can be applied:

Subsystems include
Parent Object Name = the name of the
“SAP” “parent” object.
Example: “SAP FI”
SAP

SAP FI
SAP FI SAP
SAP CO
CO

SAP MM
SAP MM SAP PP
SAP PP

SAP
SAP LES
LES SAP SD
SAP SD

SAP AG 2008

Naming conventions are important to create a consistent architecture and enable other participants to
identify the objects.
We show here general recommendations for naming conventions of systems.

© SAP AG SOA230 4-57


4 # . )')

Naming conventions also play a key role in describing versions of IT


systems and components. A mandatory, uniform system of notation
must be defined, such as:

My Application
X, YY, ZZ
X = Major release My Application
1.00

My Application
1.10

YY = Minor release
My Application
1.20

My Application
ZZ = Bug fix 1.20.01

SAP AG 2008

Here are some example suggestions for naming conventions of a system hierarchy with system versions.

© SAP AG SOA230 4-58


%
Application to Application Application and User Location
Communication View View
(EPC) (EPC)
Actor
can be user can be user
Application transmits data to Application
Component Component

Application calls
is input for has output of Service
Component

Data Entity Data Entity


can be located at can be located at

has output of is input for Location

Interface

is located at
Location

Physical Information is input for Physical Application has output of Physical Information
1 n
has relationship to Component Component Component
Data Entity Data Entity

occurs at

Conceptual/Logical ER View Data Dissemination


Gap
View
(EPC) (EPC)

SAP AG 2008

This shows how the key entities in the SAP EAF metamodel are linked from the Application
Architecture to the Data Architecture.

© SAP AG SOA230 4-59


This is the end of the 4th Unit
You should now understand
:

The SAP EAF Application SAP Enterprise Architecture Resource Base


Architecture

Released to the Open Group

Released to the Open Group


Framework extensions Extensions
Usage Guidelines SAP Business
How to use occurrence and Architecture
Content
Reference Models
Development
definition copy Method
Metamodel
SAP Technology
Templates, Examples and Case Reference Models
The next Unit explains the Studies

Data Architecture SAP Mapping Extensions

SAP Tooling Extensions


SAP Content SAP Implementation
EA Modelling Tools
Tools Tools

TOGAF Architecture TOGAF


Development Method Resource Base

SAP AG 2008

This is the end of the 4th Unit


You should now understand
The SAP EAF Application Architecture
How to use occurrence and definition copy
The next Unit explains the Data Architecture.

© SAP AG SOA230 4-60


Exercise
Unit: Unit 4 – Application Architecture
Topic: Software Engineering View

At the conclusion of this exercise, you will be able to:


• Familiarize yourself with the Application system type diagram
• Be able to model the software engineering view

1) Create a Application system type diagram named Software


Engineering View under the Information Architecture/Application
Architecture /Views group
2) Create a new group called Application Portfolio Catalog under the
Application Architecture /Catalogs group
3) Create the required objects in the catalog using the Application
system class and Application system type objects as described below
4) Create the content of the model based on the information provided
below
5) Save and close the model

1. Software Engineering View


• The applications of the FASST company can be distinguished in three classes:
- Customer Relations Systems
- Warehouse Systems
- SCM Systems
- Sales and Marketing Systems
• The Customer Relations Systems encompasses the following applications:
- e-Price
- Legacy CRM
- CRM
• The Warehouse Systems encompasses the following applications:
- SAP BW

© SAP AG SOA230 4-61


• The SCM Systems encompasses the following applications:
- e-Procurement
• The Sales and Marketing Systems encompasses the following applications:
- FASST Portal
- BIF
- DMS

© SAP AG SOA230 4-62


Unit 5 - Data Architecture

SAP AG 2008

© SAP AG SOA230 5-1


Unit 1 - Overview of SAP Enterprise Architecture Framework
Unit 1 – Introduction to ARIS

Unit 2 – Architecture Vision

Unit 3 – Business Architecture

Unit 4 – Application Architecture

Unit 5 – Data Architecture

Unit 6 – Technology Architecture

Unit 7 – Summary

SAP AG 2008

This unit will introduce the Data Architecture.


We will also show how to print models in ARIS.

© SAP AG SOA230 5-2


Prelim:
Framework and
Principles

The Information Systems


Architecture phase is about
A. defining As-Is and To-Be
Architecture
H.
Architecture
Vision
B.
Business
application and data
architectures for the
Change
Management Architecture

organization, detailing the


roadmap towards the To-Be
C.
G.
Implementation
Governance
Requirements
Management
Information
Systems
architecture and identifying
key work packages in the
Architectures

roadmap.
F. D.
Migration
Technology
Planning
Architecture

E.
Opportunities
and Solutions

SAP AG 2008

The Information Systems Architecture Phase is about defining both the application and data
architecture.
The scope of the business processes supported in this phase is limited to those that are now or need to be
supported by Information Technology
The objective here is to define the major kinds of application system necessary to process the data and
support the business architecture defined in Phase B.

© SAP AG SOA230 5-3


! "

IS Architecture involves a combination of Data


Prelim:
and Applications Architecture, in either order.
Framework and
Principles
SAP EAF recommends Application Architecture
is performed first :
Packages or packaged services provide a combination
A.
Architecture
of technology infrastructure and business application
H. Vision Application logic
B.
Architecture
Change Business Architecture
Management Architecture
Some organizations take an application-driven
approach, where key applications form the core of
mission-critical business processes,
C.
G.
Implementation
Requirements Information
Systems
SAP EAF assumes some functionality will be
Management
delivered through a packaged or packaged
Governance Architectures

service solution
F. D.
The Application Architecture phase must examine
Migration
Planning
Technology
commercially available solution models in addition to
Architecture
Data
E. Architecture
traditional requirements and current state analysis.
Opportunities
and Solutions
Commercially available templates may need to be
adopted at the expense of the business ideal.
In general, SAP EAF recommends that
architecture definition is an iterative activity and
that not all answers can be completed in a single
cycle.

SAP AG 2008

Information Systems Architecture can be broken down into Application and Data Architecture.

© SAP AG SOA230 5-4


#

Templates and Examples


BEEST Case Study

SAP EAF Templates


Inputs
Outputs
Reference
Material

TOGAF
Updated Statement of Work
SAP EAF Glossary
Current State Application Architecture
SAP EAF to SAP Terminology Mappings
Current State Data Architecture
Phase Specific Inputs

Target Application Architecture


ADM IS Architecture Narrative
Information Target Data Architecture
SAP EAF IS Architecture Worksheet
Systems Gap Analysis Results
SAP EAF Application Architecture Narrative
Updated Business Requirements, IS
Architecture Requirements, Policies, Standards,
SAP EAF Data Architecture Narrative
Guidelines and Specifications
SAP EAF Metamodel and View Definition
Phase Technology Requirements

Steps
Pre-Existing or Previous

Statement of Work
Application Architecture Baseline
Phase Inputs

Architecture Vision
Data Architecture Baseline
Architecture Principles Reference Models, Viewpoints and Tools
Develop Application Architecture Models
Business Architecture
Develop Data Architecture Models
Stakeholder Map
Perform Gap Analysis
Tailored Architecture Process and Metamodel Select IS Architecture Building Blocks
Define Roadmap
Resolve Impacts Across the Enterprise

SAP AG 2008

This slide show the key inputs, steps and outputs involved in Information Systems Architecture.
The precise steps are covered in SOA200.

© SAP AG SOA230 5-5


! $ % !&'&

criteria for
Is tracked against Is Provided to Resolves
ned and (Business, Infor
rned by
Services are Contained in Core Business ,

Provides , consumes

Is Supplied or Consumed by Is accessed and Is processed Ope


updated through by
Is Hosted
Physical Information
in
Component Data Entity

Data Extension
Resides within Resides within

Encapsulates
Logical Information Ph
Component
Data Extension

Encapsulates

DATA ARCHITECTURE

SAP AG 2008

Start by identifying the Information System Services


Business services specifically provided by an automated IT-based solution
E.g. Purchase Request Processing
Identify the data entities needed to support the service :
A data entity- An encapsulation of data that is recognized by a business domain expert as a thing –
e.g. a Purchase Order
It is important we differentiate between logical and physical information components :
A logical information component - A boundary zone that encapsulates related data entities to form a
logical location to be held External Procurement Information
A physical information component - A boundary zone that encapsulates related data entities to form
a physical location to be held SAP Purchase Order Business Object, comprising Purchase Order
header and item Business Object Nodes.

© SAP AG SOA230 5-6


!
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View
Data Architecture
Data Entity/Information Catalog Role / System Software Engineering
Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing /
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

The Data Architecture contains the data entity/information catalog.

© SAP AG SOA230 5-7


!$

Catalog, Matrix or Purpose


View

Data Entity / The purpose of this catalog is to identify and maintain a list of all the data
Information entities/information components in the enterprise. This list helps to define
Component Catalog the scope of data cleansing, collection and migration initiatives that may
impact particular kinds of applications. An agreed data portfolio allows a
standard set of corporate data to be defined and governed.

The Data Entity / Information Component Catalog contains the following


metamodel entities :
Data Entity
Logical Information Component
Physical Information Component

SAP AG 2008

The main catalog in Data Architecture is the Data Entity Catalog – i.e. a list of the main information
objects in an enterprise.

© SAP AG SOA230 5-8


!
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Data Architecture Application and
Software Distribution
View

Data Entity/Business Function Matrix User Location View Interface Catalog


Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing /
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

The Data Architecture contains the Data Entity/Business Function Matrix.

© SAP AG SOA230 5-9


%

Catalog, Matrix or Purpose


View
Data Entity / The purpose of this matrix is to depict the relationship between data entities
Business Function and business functions within the enterprise.
Matrix
Business functions are supported by business services with explicitly defined
boundaries and will be supported and realized by business processes.

The Data Entity / Business Function Matrix shows the following entities and
relationships:

Data Entity
Business Function
Data Entity relationship to owning Organization Unit
System / Data The purpose of this matrix is to depict the relationship between systems (i.e.,
Matrix application components) and the data entities that are accessed and updated
by them.

Systems will create, read, update and delete specific data entities that are
associated with them. For example, a CRM application will create, read, update
and delete customer entity information.

The System / Data Matrix is a 2-dimensional table with Logical Application


Component on one axis and Data Entity on the other axis.

SAP AG 2008

The purpose of the matrices is to relate the Data Architecture back to the Applications and Business
Functions that use each data entity.

© SAP AG SOA230 5-10


!$ %

SAP AG 2008

You see here an example of the catalogs and matrices of the data architecture in ARIS.

© SAP AG SOA230 5-11


(

Catalog, Matrix or Purpose


View
Conceptual Logical The key purpose of this view is to depict the relationships among the Critical
Entity-Relationship Data Entities within the enterprise.
View
This view is developed to clearly present the relationships and to help
understand the lower level Data Models for the enterprise.
Data Dissemination The purpose of this view is to show the relationship between data entity,
View business service and application components.

The view shows how the logical entities are to be physically realized by
application components.

Additionally the view may show data replication and system ownership of
the master reference for data. In this instance it can show two copies and the
master-copy relationship between them.

SAP AG 2008

These are the main two CORE views of the data architecture in SAP EAF.

© SAP AG SOA230 5-12


!
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data Architecture Data .


Data Dissemination View
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing /
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We will now show the Data Dissemination view.

© SAP AG SOA230 5-13


( )'&

Data Dissemination SAP EA Framework Creator: system


Last change: 10/19/07 11:08:30 AM
Type: Access diagram
Data Dissemination View

Business Service
Catalog
Contract Catalog Se arch Catalog Authoring Catalog Comparison
Personalization
Management Service Service & Promotion

Business Service

Catalog Catalog Catalog Catalog


Contract
Search Authoring Personalization Comparison
Management Service Service Service & Promotion

Access diagram

ImpSales VMS SAP R/3 BIF DMS

Product Master
Product Master Rules
Rules Business Partner
Business Partner Price
Price

Rules
Rules Product Master
Product Master Product Master
Product Master

Rules
Rules Rules
Rules

Model Type

SAP AG 2008

This is an example of the data dissemination view form the FASST case study.

© SAP AG SOA230 5-14


( &'&

Data Dissemination

Business Service
Catalog
Contract Catalog Se arch Catalog Authoring Catalog Comparison
Personalization
Management Service Service & Promotion

Access diagram The purpose of this view is to show the relationship


between data entity, business service and
application components. The view shows how the
logical entities are to be physically realized by
application components. This effective sizing to be
carried out and the IT footprint to be refined.
Moreover, by assigning business value to data an
indication of the business criticality of application
components can be gained.

Model Type

SAP AG 2008

The data dissemination view is modeled in ARIS using the Access diagram. We have shown and
discussed the access diagram in a previous unit.

© SAP AG SOA230 5-15


!
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Data Architecture Matrix Matrix Realization View

Conceptual/ Logical ER View Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Migration View Data Lifecycle View

Data Entity / Info


Data Entity Hierarchy Component Catalog Data Security View
View
Data Architecture
Data Entity Hierarchy View Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing /
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We show now the Conceptual/logical ER view and the Data Entity hierarchy view.

© SAP AG SOA230 5-16


!* $ ! ( )'+

Conceptual/ SAP EA Framework Creator: system


Last change: 10/19/07 11:11:28 AM
Logical ER Conceptual-Logical ERD
Type: IE Data model

Business Partner

Contract
Importer OEM
1 n 1 1

1 m

Business Partner

IE Data Model

Contract Contract Contract


Dealer Importer OEM Customer
m 1 n 1 1 n

The key purpose of this view is to depict the


relationships among the Critical Data Entities within
the enterprise. This view is developed to clearly
present the relationships and to help understand the
lower level Data Models for the enterprise.

Model Type

SAP AG 2008

We see here an example of the Conceptual/logical ER view.


This view is modeled in ARIS using the IE Data model.

© SAP AG SOA230 5-17


!* $ ! ( &'+

Conceptual/ ARIS Definition SAP EAF Definition


Logical ER
Business Partner

Importer
n
Contract
OEM
1
Entity type Entity Type Data Entity
1 1

1 m

IE Data Model

Object Types
Model Type

SAP AG 2008

The main element of this view is the entity.

© SAP AG SOA230 5-18


!* $ ! ( +'+

Conceptual/
Logical ER
Business Partner

Importer
Contract
OEM
Cardinality
Cardinality
1 n 1 1

1 m

IE Data Model

1 n
has relationship to
Data Entity Data Entity

Relationship Types
Model Type

SAP AG 2008

We see here an example of relationships between entities.

© SAP AG SOA230 5-19


$

General Print settings are made under View Options:


Model General Print
Model For New Models Print
Page Layout
The settings under View Options are basic settings for the client.
They can be changed for a specific model.
The Print options set under View Options can be individually
changed for a specific model
in the File menu, or
using the model pop-up menu

SAP AG 2008

Database-specific print options are set under Database pop-up menu -> Properties in the Administration
module of ARIS Business Architect. These include:
Header / footer
Logo management (print logo and wallpaper)
Page layout

© SAP AG SOA230 5-20


, ! $ ( - )'&

From the Toolbar:


View Options Model General Print Print Header/Footer
Check box to enable

Print Empty pages


Check box to enable

Display Print Page


Check box to enable

SAP AG 2008

You see here the general print settings under View Options.

© SAP AG SOA230 5-21


, ! $ ( - &'&

From the Toolbar:


View Options Model For New Models Print
Select Print Scale
percentage

Color or Black/white
printing
Check box to enable

Select Orientation:
Portrait or Landscape

NOTE As these settings depend on the size and alignment (length,


width) of the model, they are normally set individually in the
Print Preview. When printing the model.

SAP AG 2008

You see here the print settings for new models.

© SAP AG SOA230 5-22


$. / ' $ *

Print options in File menu:

Select Page Setup


To execute Page Setup pop-up
window

SAP AG 2008

You can access the page setup under File -> Page setup.

© SAP AG SOA230 5-23


$ /

Header and 1. Select Local 2. Place the cursor in the


Footer Settings desired Header/Footer field
Highlighted – i.e. Left, Center or Right
placement

3. Insert Attribute
by double
clicking
4) Make settings

5) Select OK

SAP AG 2008

You see here the settings that can be made for printing header/footer information.
Local settings can be changed by the user for a specific model.
Global settings use the defaults saved for the database.
These settings are made using ARIS Business Architect.

© SAP AG SOA230 5-24


$ $ *

1) Page Layout
Highlighted

2) Set Margins:
Left
Top
Right
Botton

3) Select OK

SAP AG 2008

Here you can define the margins for printing.

© SAP AG SOA230 5-25


)'&

As well as using File Print Preview, the Print Preview can be


called up using
the keyboard shortcut Ctrl+F2 or
the icon in the toolbar

SAP AG 2008

The methods for accessing the print preview are:


the keyboard shortcut Ctrl+F2 or
the icon in the toolbar
As well as using File Print Preview, the Print Preview

© SAP AG SOA230 5-26


&'&

The settings are made using the Print Preview toolbar:

Fit to Page Print blank Black/White Show 1 Page


pages Printing

Print Set number of Print


Command pages Wallpaper

Print
Page Setup header/footer

SAP AG 2008

Page Setup: Definition of header/footer and page layout


Fit to page: Places the entire model graphic on one page
Set number of pages: Number of pages wide and high on which the model is to be printed. The print
scale corresponding to the settings is displayed.
Print blank pages: In models that are printed on several pages, it can happen that blank pages occur (e.g.
"wide" process representation at the beginning, but only a thin process path afterwards). These can be
printed so that the A4 pages can subsequently be combined into a larger model.
Header and footer: Specifies whether the header and footer are to be printed. The content is defined
under "Page Setup".
Print wallpaper: Wallpaper can be printed if it is incorporated into the database (ARIS Business
Architect).

© SAP AG SOA230 5-27


0 $ ,

Using the model pop-up menu: Export As Graphic…, the


model graphic can be exported to an .emf file (Windows
Enhanced Metafile).
Select Storage
Location of
Output File

The selected sections


or the entire model is
exported

SAP AG 2008

The method above shows how to export a model graphic to be included in another file.

© SAP AG SOA230 5-28


!
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View
Data Architecture Role / System Software Engineering
Application
Data Migration View
Application Portfolio
Catalog
Matrix View
Communication View
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing /
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We will now show the Data Migration view.

© SAP AG SOA230 5-29


0 (

Catalog, Purpose
Matrix or View
Data Lifecycle This view is an essential part of managing business data throughout its lifecycle
View from conception until disposal within the constraints of the business process.

Each change in state is represented on the view which may include the event or
rules that trigger that change in state.
Data Security Data is considered as an asset to the enterprise and Data security simply means
View ensuring that enterprise data is not compromised and that access to it is suitably
controlled.

The purpose of the view is to depict which Actor (person, organization or system)
can access which enterprise data. This relationship can be shown in a matrix form
between two objects or can be shown as a mapping.
Data Data migration is critical when implementing a package or packaged service
Migration based solution.
View
The view will provide a visual representation of the spread of sources/targets and
serve as a tool for data auditing and establishing traceability.
Entity The purpose of this view is to show the Technical Stakeholders a perspective of
Hierarchy the Entity Hierarchy. The advantage of this view is that it allows the Stakeholders a
View technical Utilization/Usage view of the Data Entity. This view gives the
stakeholders an Idea of who is using the Data, how, why and when.

SAP AG 2008

These are the main four EXTENSION views of the Data Architecture in SAP EAF

© SAP AG SOA230 5-30


% $ (

Data Migration SAP EA Framework Creator: system


Last change: 10/10/07 8:08:46 AM
Type: Program flow chart
Data Migration View

Application transmits data to Application Logical Application Logical Application


Component Component
Component Component
transmits data to transmits data to
Interface

has output of is input for

Logical Information Logical Information


Component Component

Program Flow
Chart is input for has output of

Interface

Data migration is critical when implementing a


package or packaged service based solution. This
is particularly true when an existing legacy
application is replaced with a package or an
enterprise is to be migrated to a larger
packages/packaged services footprint. Packages
tend to have their own data model and during data
migration the legacy application data may need to
be transformed prior to loading into the package.
Model Type

SAP AG 2008

We see here an example of the data migration view.


The data migration view is modeled in ARIS using the program flow chart.
We have shown and discussed the program flow chart in a previous unit.

© SAP AG SOA230 5-31


(
Conceptual/Logical ER View Data Dissemination View
(EPC) (EPC)
is located at
Location
1 n
has relationship to
Data Entity Data Entity

Physical Information is input for Physical Application has output of Physical Information
Component Component Component

occurs at

Gap
!

Tier Tier

can be located at Application system can be platform of Hardware


Platform Decomposition Location
type component
View
(EPC) Logical Application
Component
Architecture layer
Technology Environments and Location
Component
View
Logical Techncial
Component
(EPC)

SAP AG 2008

This shows how the key entities in the SAP EAF are linked from the Data architecture to the
Technology architecture.

© SAP AG SOA230 5-32


This is the end of the 5th Unit
You should now understand
1

The SAP EAF Data SAP Enterprise Architecture Resource Base


Architecture

Released to the Open Group

Released to the Open Group


Framework extensions Extensions
Usage Guidelines SAP Business
How to represent the Data Architecture
Content
Reference Models
Development
Architecture in ARIS Method
Metamodel
SAP Technology
Templates, Examples and Case Reference Models
How to print in ARIS Studies

SAP Mapping Extensions


The next Unit explains the SAP Tooling Extensions
Technology Architecture. SAP Content
Tools
SAP Implementation
Tools
EA Modelling Tools

TOGAF Architecture TOGAF


Development Method Resource Base

SAP AG 2008

This is the end of the 5th Unit


You should now understand
The SAP EAF Data Architecture
How to represent the Data Architecture in ARIS
How to print in ARIS
The next Unit explains the Technology Architecture.

© SAP AG SOA230 5-33


© SAP AG SOA230 5-34
Exercise
Unit: Unit 5 – Data Architecture
Topic: Data Dissemination View

At the conclusion of this exercise, you will be able to:


• Familiarize yourself with the Access diagram
• Be able to model the data dissemination view

1) Create a Access diagram named Data Dissemination View under the


Information Architecture/Data Architecture /Views group
2) Create the content of the model based the information provided below
3) Save and close the model

1. Data Dissemination View


• The application SAP R/3 has the following data entities as input:
- Business Partner
- Product Master
- Rules
• The SAP R/3 system supports the following services:
- Contract Management
- Catalog Personalization Service

© SAP AG SOA230 5-35


© SAP AG SOA230 5-36
Unit 6 - Technology Architecture

SAP AG 2008

© SAP AG SOA230 6-1


Unit 1 - Overview of SAP Enterprise Architecture Framework
Unit 1 – Introduction to ARIS

Unit 2 – Architecture Vision

Unit 3 – Business Architecture

Unit 4 – Application Architecture

Unit 5 – Data Architecture

Unit 6 – Technology Architecture

Unit 7 – Summary

SAP AG 2008

This unit will introduce the Technology Architecture of the SAP EAF.
We will also show how to run searches and semantic checks in ARIS.

© SAP AG SOA230 6-2


Prelim:
Framework and
Principles

The Technology Architecture


phase is about defining the
A.

H.
Architecture
Vision
B.
As-Is and To-Be technology
architectures for the
Architecture
Change Business
Management Architecture

organization, detailing the


C.
roadmap towards the To-Be
G.
Requirements
architecture, and identifying
Information
Implementation
Systems
Governance Management Architectures

key work packages in the


roadmap.
F. D.
Migration
Technology
Planning
Architecture

E.
Opportunities
and Solutions

SAP AG 2008

The Technology Architecture Phase is about defining the technology required to deliver the applications
and data required by the Business to achieve its goals
The scope of the business processes supported in this phase is limited to those that are now or need to be
supported by Information Technology
The objective here is to define the major kinds of technology necessary to process the data and run the
applications defined in Phase C.

© SAP AG SOA230 6-3


Templates and Examples
Inputs
TOGAF BEEST Case Study
Reference
Material

SAP EAF Glossary SAP EAF Templates


SAP EAF to SAP Terminology Mappings
Mapping of TOGAF TRM to SAP Outputs
Updated Statement of Work
Phase Specific Inputs

Current State Technology Architecture


ADM Technology Architecture Narrative
Technology Target Technology Architecture
SAP EAF Technology Architecture Worksheet

SAP EAF Technology Architecture Narrative


Architecture Gap Analysis Results

SAP EAF Metamodel and View Definition Phase Updated Technology, Policies, Standards,
Guidelines and Specifications

Updated Business, IS and Technology


Requirements
Pre-Existing or Previous

Statement of Work

Architecture Vision Steps


Phase Inputs

Architecture Principles Technology Baseline Description


Reference Models, Viewpoints and Tools
Business Architecture
Develop Architecture Models
Information Systems Architecture
Perform Gap Analysis
Stakeholder Map Select Technology Architecture Building
Blocks
Tailored Architecture Process and Metamodel
Define Roadmap
Resolve Impacts Across the Enterprise

SAP AG 2008

This slide show the key inputs, steps and outputs involved in Technology Architecture.
The precise steps are covered in SOA200.

© SAP AG SOA230 6-4


! "

realised by Meets measured by

Service
Business /IT Alignment Extension Provid
interfac
Is implemented on
Provides
platform for Supplies
Is Supplied By
Logical Technology
Component
Platform Service
Infrastructure Consolidation
Extension

ed by Realises

Physical Technology
Component

Is Hosted in

TECHNOLOGY ARCHITECTURE

SAP AG 2008

Start by identifying the Information System Services


Business services specifically provided by an automated IT-based solution
E.g. Purchase Request Processing
Identify the logical technology components required to fulfill that service
An encapsulation of technology infrastructure that is independent of a particular product.
A class of technology product. E.g. Supply Chain Management software as part of an ERP Suite.
Identify the Platform Services required
A technical capability required to provide enabling infrastructure that supports the delivery of
applications e.g. Data Management, Transaction Processing
Identify the physical technology components required to provision the logical technology components
A specific technology infrastructure product or technology infrastructure product instance. E.g. SAP
BBPCRM 5.0

© SAP AG SOA230 6-5


#
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View
Technology Architecture
Technology Standards Catalog Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Technology Architecture
Data Entity / Info
Data Entity Hierarchy
View Technology Portfolio Catalog
Component Catalog Data Security View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

The Technology Architecture contains the Technology Standards catalog and the Technology Portfolio
catalog.

© SAP AG SOA230 6-6


Catalog, Matrix Purpose
or View
Technology The purpose of this catalog is to identify and maintain a list of all the
Portfolio technology in use across the enterprise, including hardware, infrastructure
Catalog software and application software. An agreed technology portfolio supports
lifecycle management of technology products and versions and also forms the
basis for definition of technology standards.

The Technology Portfolio Catalog contains the following metamodel entities :

Platform Service
Logical Technology Component
Physical Technology Component
Technology This catalog documents the agreed standards for technology across the
Standards enterprise. Covering technologies, and versions, the technology lifecycles,
Catalog and the refresh cycles for the technology.
Depending upon the organization this may also include location or business
domain specific standards information.

The Technology Portfolio Catalog contains the following metamodel entities :

Platform Service
Logical Technology Component
Physical Technology Component

SAP AG 2008

The main Catalogs in this phase are a list of the main technology components that form the portfolio,
and a list of the Technology Standards relating to those.

© SAP AG SOA230 6-7


#
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Technology Architecture Data .


System Technology Matrix
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

The Technology Architecture contains the System Technology matrix.

© SAP AG SOA230 6-8


!

Catalog, Matrix or Purpose


View
System / This matrix documents the mapping of business systems to technology
Technology Matrix platform.

This matrix should be aligned with and complement one or more


Platform decomposition views.

The System / Technology Matrix shows:

Logical / Physical Application Components


Platform Services, Logical Technology Components and Physical
Technology Components
Physical Technology Component realizes Physical Application
Component relationships

SAP AG 2008

This is the main matrix in Technology Architecture is used to relate the technology components to the
application components that utilize them.

© SAP AG SOA230 6-9


!

SAP AG 2008

Example of the catalogs and matrices of the Technology Architecture in ARIS are shown here

© SAP AG SOA230 6-10


#
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
Technology Architecture System /
Organization Matrix
Enterprise
Manageability View

Environments and Locations Data .


View Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We will now cover the Environments and Locations view of the Technology Architecture.

© SAP AG SOA230 6-11


$

Catalog, Matrix or Purpose


View
Environments and These views depict which locations host which applications, identify
Locations View what technologies and/or applications are used at which locations, and
finally to identify the locations from which business users typically
interact with the applications.
Platform Depicts the technology platform that supports the operations of the
Decomposition Information System architecture. The view covers all aspects of the
view infrastructure platform and provides an overview of the enterprise’s
technology platform.

SAP AG 2008

These are the two main core views of Technology Architecture.

© SAP AG SOA230 6-12


" % $ &'(

Environments and
Location SAP EA Framework Creator: system
Last change: 10/19/07 1:12:48 PM
Environment-Location View Type: Access diagram

Oracle Oracle Access Oracle

HP HP HP HP

Unix Uni x Unix

BIF FASST SCM ImpDMS R.N.I. ImpCRM

Oracle Oracle
Oracle Access
Access Oracle
HP
HP HP
HP HP
HP HP
HP

Access diagram Unix


Unix Unix
Unix Unix
Unix

Leipzig
Leipzig Leipzig
Leipzig Russia
Russia

Stuttgart
Stuttgart Stuttgart
Stuttgart

USA
USA USA
USA

Model Type

SAP AG 2008

An example of the Environments and Location View from the FASST case study is shown here.
The environments and location view is created in ARIS using the access diagram. We have shown and
discussed the access diagram in a previous unit.

© SAP AG SOA230 6-13


" % $ ('(

Environments and
Location

Oracle Oracle Access Oracle

HP HP HP HP

Unix Uni x Unix

Access diagram
These views depict which locations host which
applications, identify what technologies and/or
applications are used at which locations, and finally
to identify the locations from which business users
typically interact with the applications.
This view should also show the existence and
location of different deployment environments,
including non-production environments, such as
development and pre-production.

Model Type

SAP AG 2008

The Environments and Location View is created in ARIS using the access diagram.
We have shown and discussed the access diagram in a previous unit.

© SAP AG SOA230 6-14


The standard search function can be used to make focused
searches of the database for:
Models
Objects
Groups
Objects with identical names
You can search for the following items stored in a group or its
subgroups:
Subgroups of the selected group
Models
Objects
Objects with identical names
Both name and full-text searches can be made.

SAP AG 2008

The purpose of the search in ARIS is to find architecture elements that are located in an unfamiliar place
or you may not be sure if they exist at all.

© SAP AG SOA230 6-15


Start the search in the Explorer and Designer modules using
one of the following methods:
The group, model, or object context menu Find
The key combination Ctrl+F
The icon

SAP AG 2008

The following methods can be used to start a search.


Start the search in the Explorer and Designer modules using one of the following methods:
The group, model, or object context menu -> Find
The key combination Ctrl+F
The icon

© SAP AG SOA230 6-16


# )
With groups, the
Select
search area can
Standard Tab
What are you looking for? be changed
Highlight and double click to
select

The date of last change can also


be included in the search
and will appear in the search
result.

SAP AG 2008

Here you see the components of the search window.

© SAP AG SOA230 6-17


#

First, the relevant business objects (cluster) are found and listed:
Select Standard Tab

1) Select object type

2) Select object name

3) Start search to generate


4) List of Objects. Select all list – Results displayed
to highlight – right click below
to display pop-up menu

5) Call query via


context menu -> Find

SAP AG 2008

Here you see the elements of the search window for an object search.

© SAP AG SOA230 6-18


*

Queries enable search criteria to be defined and combined.


Queries are defined in the Administration module of ARIS IT
Architect using a wizard and are available on the central server.
Nested queries:
Queries can be nested.
This means that complex queries can be constructed out of
multiple simple queries without complexity adversely affecting
clarity.

SAP AG 2008

Queries are predefined searches that can be saved and repeated.

© SAP AG SOA230 6-19


* * &'(

The query searches within the results of the standard search,


thus further restricting the search results.
List of queries

Select query
Start query by choosing OK ->
Start

SAP AG 2008

Here you see the search window for queries. You can select queries from a drop down list.

© SAP AG SOA230 6-20


* * ('(

List of results for first query

Further queries can be run on the results


already obtained, using the context menu ->
Find.

SAP AG 2008

You can run another query with the results of a previous query.

© SAP AG SOA230 6-21


" +

Like reports, semantic checks are an evaluation option in ARIS


IT Architect
Evaluations can be started manually (supported by a wizard) or
via macros.
Evaluations are defined in ARIS IT Architect.
In ARIS IT Designer, evaluations can be performed in the
Explorer and Designer modules.
Evaluations are started via the context menu of:
One or more groups
One or more models
One or more objects
Choose: Evaluate …

SAP AG 2008

Semantic checks evaluate the correctness of models based on predefined standards.


They are one of the important tools for model administration and architecture governance.

© SAP AG SOA230 6-22


" +

Semantic checks can be used to check that models:


Have the correct structure and syntax
Are complete
The modeling conventions defined in the project preparation
phase determine which semantic checks are relevant to the
project.
Semantic checks should therefore be defined during the project
preparation phase.
The conventions manual should specify which semantic checks
must be performed for which models.

SAP AG 2008

Semantic checks should be defined and implemented before the user community starts to work on the
architecture.
The quality management process must include semantic checks.

© SAP AG SOA230 6-23


" + , "

Some examples of what CAN be checked using semantic


checks:
Is at least one responsible business employee or organizational
unit assigned to each IT system?
Are the name, identifier, and full name attributes included for all
data?
Does every IT system support at least one function?
Does every position assigned to an IT system also appear in an
organizational chart?
Does every EPC begin/end with an event or a process interface?
In an EPC, is there an OR/XOR connector after a single event?

The types of question are defined in the project conventions.

SAP AG 2008

This is an example list of possible semantic checks.

© SAP AG SOA230 6-24


" +

Semantic checks are started manually as follows:

In the menu bar via Evaluate -> Start semantic check…


(after selecting the element to be evaluated) or via the
following button:

This launches the Semantic Check Wizard.

SAP AG 2008

To start a semantic check go to Evaluate -> Start semantic check

© SAP AG SOA230 6-25


" +- . &

In step 1 of the Semantic Check Wizard, the profile is selected.

In the Step Tab: Select profile is


highlighted

If User-defined is selected, all rules (grouped by rule type) will be listed, and
in the next step the modeler/checker must select the rule(s) to be applied.
If a different profile is selected, all rules assigned to that profile are
automatically applied.

SAP AG 2008

This is step 1 of the semantic check wizard.

© SAP AG SOA230 6-26


" +- . (

Step 2 of the Semantic Check Wizard: Select the rules to be applied for
the chosen profile (different rule types can also be selected)*.
In the Step
Tab: Select rules is highlighted

Select Rules: Check the box of


next to rule profile

Click on next to continue

* User-defined profile only


SAP AG 2008

Step 2 allows to select from a list of predefined rules profiles.

© SAP AG SOA230 6-27


" +- . /

In step 3 of the Semantic Check Wizard, the output settings are


defined.
In the Step Tab: Select output
settings is highlighted

Output Settings:
Database Language
Check box to Click on Finish
Evaluation filter
Display Results
Output format
Save output as

SAP AG 2008

Step 3 defines the output format and location.

© SAP AG SOA230 6-28


, " " + 0 12 1 3

Procedure:
Choose Evaluate Start semantic check from the model context menu.
Choose the User-defined profile.
Choose “cluster attributes” in the rule type “object attribute rule.”
Set output options (output to Word).
Finish

“Identifier” and “Full


name” attributes are
blank!

SAP AG 2008

Here is an example of a semantic check that evaluates if specific attributes are maintained.

© SAP AG SOA230 6-29


, " # " +

Output to Word

Missing/Incorrect attributes types are listed

SAP AG 2008

The result of the semantic check from the previous slide.

© SAP AG SOA230 6-30


#
Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Technology Architecture Organization Matrix Manageability View

Platform Decomposition View Data .


Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We will now look at the Platform Decomposition View.

© SAP AG SOA230 6-31


# " 4 " $ &'(

Platform
Decomposition SAP EA Framework Last change: 10/19/07 1:34:03 PM
Platform Decomposition Type: IT architecture matrix
View (conceptual)

Web Server Layer Hardware Web Server Layer Software

Web Server Layer


HP Proliant SAP WAS 6.4

Web Server Layer Web Server Layer


Hardware Software
Web Server
IT Architecture Layer HP Proliant
HP Proliant SAP WAS
SAP WAS 6.4
6.4

Matrix
Application Layer Application Layer
Hardware Software
Application
Layer BIFBIF
configurator
configurator
HP Proliant
HP Proliant (custom)
(custom)

Model Type

SAP AG 2008

This is an example of the Platform Decomposition View from the FASST case study.

© SAP AG SOA230 6-32


# " 4 " $ ('(

Platform
Decomposition

Web Server Layer Hardware Web Server Layer Software

Depicts the technology platform that supports the


Web Server Layer
HP Proliant SAP WAS 6.4

operations of the Information System architecture.


The view covers all aspects of the infrastructure
IT Architecture
platform and provides an overview of the
Matrix enterprise’s technology platform. The view can be
expanded to map the technology platform to
appropriate application components within a
specific functional or process area. This view may
show details of specification, such as product
versions, number of CPUs, etc or simply could be an
informal “eye-chart” providing an overview of the
technical environment.

Model Type

SAP AG 2008

The Platform Decomposition view is created in ARIS using the IT Architecture Matrix.

© SAP AG SOA230 6-33


! , &'(

Platform ARIS Definition SAP EAF Definition


Decomposition

Web Server Layer Hardware Web Server Layer Software

Architecture
Architecture Layer Architecture Layer
Web Server Layer
HP Proliant SAP WAS 6.4

layer

Technology
IT Architecture Component Architecture Layer Architecture Layer
Matrix
Application
system type Logical Application
System, Service
Component

Hardware
component
type Logical Technical
Hardware Type
Component

Object Types
Model Type

SAP AG 2008

Here we see a list of main elements of the Platform Decomposition view.

© SAP AG SOA230 6-34


! , ('(

Platform
Decomposition
Relationship
Web Server Layer
Web Server Layer Hardware

HP Proliant
Web Server Layer Software

SAP WAS 6.4


‘belongs to’

IT Architecture
Matrix Logical Application
Component
Technology
Architecture layer
Component

Logical
Techncial
Component

Relationship Types
Model Type

SAP AG 2008

The relationships are created implicit.

© SAP AG SOA230 6-35


"" $

Application to Application Application and User Location


Communication View View
(EPC) (EPC)

Actor
Application transmits data to Application
Component Component can be user can be user

is input for has output of


Application calls
Service
Component
Data Entity Data Entity

can be located at can be located at


has output of is input for

Location
Interface

Tier Tier
can be located at Application system can be platform of Hardware
Location
type component
Platform Decomposition
View
(EPC) Logical Application
Component Environments and Location
Technology
Architecture layer
Component View
Logical Techncial
(EPC)
Component

SAP AG 2008

This shows how the key entities in the SAP EAF metamodel are linked by the different views linking
the Application Architecture with the Technology Architecture.

© SAP AG SOA230 6-36


, $

Catalog, Matrix or Purpose


View
Processing View This view focuses on deployable units of code/configuration and how these
are deployed onto the technology platform. A deployment unit represents
grouping of business function, service or application component.

The organization and grouping of deployment units depends on separation


concerns of the presentation, business logic and data store layers and
service level requirements of the components.
Network Starting with the transformation to client-server systems from mainframes
Computing / and later with the advent of e-business and J2EE, large enterprises moved
Hardware view predominantly into a highly network based distributed network computing
environment with firewalls and demilitarized zones.

The purpose of this view is to show the “as-deployed” logical view of


application components in a distributed networking computing
environment.
Communications The communications map view describes the means of communications,
Engineering view the method of sending and receiving information, between these assets in
the Technology Architecture. The communications engineering view will
take logical connections between client and server components and
identify network boundaries and network infrastructure required to
physically implement those connections.

SAP AG 2008

These are 3 main extension views in the Technology Architecture phase – they are used when the
appropriate extensions are selected.
SOA200 provides advice on selecting extensions.

© SAP AG SOA230 6-37


""

This is the end of the 6th Unit " +


#
You should now understand SAP Enterprise Architecture Resource Base

Released to the Open Group


Released to the Open Group
Framework extensions Extensions
The SAP EAF Technology Usage Guidelines SAP Business
Reference Models
Architecture Architecture
Development
Content
Metamodel
Method
How to run a search in ARIS Templates, Examples and Case
SAP Technology
Reference Models
Studies

How to run a semantic check in SAP Mapping Extensions


ARIS SAP Tooling Extensions

The next Unit is the summary of SAP Content


Tools
SAP Implementation
Tools
EA Modelling Tools

this course TOGAF Architecture TOGAF


Development Method Resource Base

SAP AG 2008

This is the end of the 6th Unit


You should now understand
The SAP EAF Technology Architecture
How to run a search in ARIS
How to run a semantic check in ARIS
The next Unit is the summary of this course

© SAP AG SOA230 6-38


Exercise
Unit: Unit 6 – Technology Architecture
Topic: Semantic Check

At the conclusion of this exercise, you will be able to:


• Execute semantic checks
• Be able to read the results of a semantic check

1) Select the EPC that you have modeled in the Unit 3 Exercise 2
2) Execute a semantic check on the model
3) Evaluate the results and try to eliminate all errors in the model

1. Semantic Check
• Select the EPC model that you have created earlier
• Execute the semantic check -> right click/Evaluate/Start semantic check
• Select the profile: Standard rules for process models

• Specify the output information

• Select Finish
• Evaluate the results

© SAP AG SOA230 6-39


© SAP AG SOA230 6-40
Exercise
Unit: Unit 6 – Technology Architecture
Topic: Environment and Location View

At the conclusion of this exercise, you will be able to:


• Familiarize yourself with the Access diagram
• Be able to model the environment and location view

4) Create a Access diagram named Environment and Location View


under the Technology Architecture /Views group
5) Create the content of the model based the information provided below
6) Save and close the model
Hint: make use of the indirect relationship feature.

1. Environment and Location View


• The application BIF (Build it Fast) is located at the following location:
- Leipzig
- Stuttgart
- USA
• The application BIF (Build it Fast) uses Oracle as the database system
• The database system can run under the flowing physical technology components:
- HP
- Unix

© SAP AG SOA230 6-41


© SAP AG SOA230 6-42
Exercise
Unit: Unit 6 – Technology Architecture
Topic: Database Organization

At the conclusion of this exercise, you will be able to:


• Be able to structure an ARIS database based on framework or project
requirements
• Be able to move object definitions within an ARIS database
7) Create the Catalogs groups as defined in the EAF framework and
ARIS FASST Example database
8) Move the object definitions from the objects that you have created
during exercises into the appropriate catalog folders
9) Save the database
10) Reorganize the database and review the results

1. Database Organization
• Create the Catalogs groups as defined in the EAF framework and ARIS FASST
Example database
• Select you object definitions and drag and drop them into the appropriate folders
• Log out of all models
• Right click on the database and select -> backup
• Select the administration tap
• Right click on the database and select -> reorganize
• After reorganization is completed go back to the catalog groups and review the
results

© SAP AG SOA230 6-43


© SAP AG SOA230 6-44
Unit 7 - Architecture Summary

SAP AG 2008

© SAP AG SOA230 7-1


Unit 1 - Overview of SAP Enterprise Architecture Framework
Unit 1 – Introduction to ARIS

Unit 2 – Architecture Vision

Unit 3 – Business Architecture

Unit 4 – Application Architecture

Unit 5 – Data Architecture

Unit 6 – Technology Architecture

Unit 7 – Summary

SAP AG 2008

This course will provide a summary of how to create an SAP EAF based architecture in ARIS.
We will also show how to run reports to evaluate the architecture content now that it has been modeled
and entered into the toolset.

© SAP AG SOA230 7-2


Business .
Structure Context Operation
Organisation Chart Functional Decomposition Use Case Role Actor /
View View View Catalog Role Matrix

Location Process Flow View


Catalog
Business Footprint Organisation /

Process for Creating an Architecture


View Actor Catalog

Goal/ Objective/
Service View

Driver / Goal / Process / Event / Control /


Event View
Objective Catalog Product Catalog

Contract / Measure Service / Information Business Interaction


Service / Function Catalog
Catalog View Matrix

Application .

Structure Context Operation


System / Function Application Interaction Process / System
Matrix Matrix Realization View

Role / System Software Engineering


Application
Application Portfolio Matrix View
Communication View
Catalog
Software Distribution
Application and View
User Location View Interface Catalog
Application Migration
View
System / Enterprise
Organization Matrix Manageability View

Data .
Structure Context Operation

Conceptual / Logical Data Entity / Business Data Dissemination


ER View Function Matrix View

Data Lifecycle View


Data Migration View
Data Entity / Info
Data Entity Hierarchy Component Catalog Data Security View
View

Technology .
Structure Context Operation
Technology Standard System / Technology Platform
Processing View
Catalog Matrix Decomposition View Mandatory View

Technology Portfolio Networked


Catalog Optional View
Computing/
Environments and Hardware View
Locations View Catalog
Communication
Engineering View
Matrix

SAP AG 2008

We now have a completed a full iteration of the SAP EAF.

© SAP AG SOA230 7-3


Catalogs for Architecture
Vision

Models for Architecture


Vision

Catalogs for Business


Architecture

Models for Business


Architecture

SAP AG 2008

Here you see a summary of catalogs, matrices and views created during the Architecture Vision, and
Business Architecture phases, based on the FASST case study.

© SAP AG SOA230 7-4


!

Catalogs for Application


Architecture

Matrices for Application


Architecture

Models for Application


Architecture

Catalogs for Data


Architecture
Matrices for Data
Architecture

Models for Data


Architecture

SAP AG 2008

Here you see a summary of catalogs, matrices and views created for application architecture and the
data architecture based on the FASST case study.

© SAP AG SOA230 7-5


Catalogs for Technology
Architecture

Matrices for Technology


Architecture

Models for Technology


Architecture

SAP AG 2008

Here you see a summary of catalogs, matrices and views created for the technology architecture based
on the FASST case study.

© SAP AG SOA230 7-6


" # "

Reports can be used to:


Evaluate the content of an ARIS database in text or table form
Example: Automatic creation of project documentation,
e.g., a system fact sheet
Import or export database content
Change database content (esp. where mass data is involved)
Example: Database-wide change to an object type, e.g., transforming
“application system” objects into “application system type” objects

SAP AG 2008

Reports can be used to:


Evaluate the content of an ARIS database in text or table form
Import or export database content
Change database content

© SAP AG SOA230 7-7


" # $ %

The following “elements” can be evaluated using reports:


A database*
One or more groups
One or more models
One or more objects
A method filter*
These “elements” are also referred to as the (report) context.
* Not in ARIS IT Designer

SAP AG 2008

The following “elements” can be evaluated using reports:


A database*
One or more groups
One or more models
One or more objects
A method filter*

© SAP AG SOA230 7-8


" # " &

A report (script) always refers to a (report) context:


Database*
Group
Model (including model types)
Object (including object types)
Method filter*
The context is defined when the report is created (in the
Administration/ Script Editor modules).
A report can only be run on the context for which it was
defined.
* Not in ARIS IT Designer

SAP AG 2008

A report (script) always refers to a (report) context:


Database*
Group
Model (including model types)
Object (including object types)
Method filter*

© SAP AG SOA230 7-9


" # # "

Reports can be called in the Explorer and Designer modules.


Reports can be started manually (supported by a wizard) or via
macros.
Macros can be started manually or automatically.
For macros to be started automatically, an event must be
defined that triggers the macro.
Example: Closing a model calls a macro that outputs all model
changes as a text report.

SAP AG 2008

Reports can be started different ways. A macro is a report that starts based on a predefined event.

© SAP AG SOA230 7-10


# "

Reports are started manually:

In the menu bar via Evaluate ->


Start report… (after selecting the
element to be evaluated) or via the
following button:

This launches the Report Wizard.

SAP AG 2008

To start a report manually use Evaluate -> Start report

© SAP AG SOA230 7-11


" ' ( ) "

In step 1 of the Report Wizard, select the report to be run.


In the Step Tab:
Select report is highlighted
1) Select report category

2)
2) Select report
Select report

Report
Report description
description

SAP AG 2008

Here you see step one of the report wizard to select the report that you want to execute.

© SAP AG SOA230 7-12


" ' ( ) "!

In step 2 of the Report Wizard, define the output settings.


In the Step Tab:
Select output settings

Output Settings:
Select Finish to start report
Database Language
Evaluation filter
Output format
Save output as

SAP AG 2008

In step 2 you define the output format and location.

© SAP AG SOA230 7-13


" ' ( ) "!

In some reports, additional output options are available.

SAP AG 2008

This is an example of a user input window during report execution.

© SAP AG SOA230 7-14


* "

Macros can be used to automatically run the following on the client:


Semantic checks
Reports
Macros can be started manually (context menu Start macros…)
or automatically (event-driven).
Macros are assigned to macro categories.
Macros can be run in the Explorer, Designer, and Administration
modules

SAP AG 2008

A macro is an automatically executed report.

© SAP AG SOA230 7-15


* " )+ $ ,

Macros
React to events triggered by the user or system
Are run on the client
Have their own object model compared to report scripts
Can run report scripts and semantic checks
Report scripts
Are started explicitly
Are run on the server
Have their own object model compared to macros
Cannot run any further report scripts or semantic checks

SAP AG 2008

Here you see the differences between reports and macros.

© SAP AG SOA230 7-16


$ "

The information managed in the ARIS repository can be


evaluated in a number of ways.
In addition to the usual navigation options and standard search
function, ARIS IT Architect provides a variety of reports and
macros tailored to the requirements of IT architecture
management.
The reports and macros are described on the following slides,
supported by examples of how to navigate through and search
IT-specific data.

SAP AG 2008

© SAP AG SOA230 7-17


" - $ * . $

The “system list” report enables various system lists to be


created, according to the selection set. The following system
lists can be created:
System list for selected IT components
System list for selected business processes
List of IT components for selected business processes
Output to RTF/Word, PDF, HTML, or Excel
ARIS provides a wizard to support this report.

SAP AG 2008

© SAP AG SOA230 7-18


" - $ * $ + $

All the information that describes an IT system (application


system type) can be output in condensed form as a system fact
sheet.
The system fact sheet describes a system from the following
viewpoints:
System description
Contact (person, organizational unit)
Service level agreements
Technical functionalities
Processes
Information architecture
Architecture Set
Operation
Output to RTF, PDF, HTML, Word, or Excel
SAP AG 2008

The system fact sheet is a standard report in ARIS IT Architect that compiles all the information of a
selected system.

© SAP AG SOA230 7-19


" )

SAP AG 2008

Here you see the first pages of a completed system fact sheet report.

© SAP AG SOA230 7-20


" ) !

SAP AG 2008

Here you see the remaining pages of a completed system fact sheet report.

© SAP AG SOA230 7-21


" )

SAP AG 2008

Here you see the final pages of a completed system fact sheet report.

© SAP AG SOA230 7-22


This is the end of the 7th Unit " /
"
You should now understand SAP Enterprise Architecture Resource Base

Released to the Open Group


Released to the Open Group
Framework extensions Extensions
How a completed EAF Usage Guidelines SAP Business
Reference Models
architecture looks in ARIS Architecture
Development
Content
Metamodel
Method
How to execute reports in ARIS Templates, Examples and Case
SAP Technology
Reference Models
Studies

This is the end of the SOA 230 SAP Mapping Extensions


course. SAP Tooling Extensions
SAP Content SAP Implementation
EA Modelling Tools
Tools Tools

TOGAF Architecture TOGAF


Development Method Resource Base

SAP AG 2008

This is the end of the final Unit


You should now understand
How a completed EAF architecture looks in ARIS
How to execute reports in ARIS
This is the end of the SOA 230 course.

© SAP AG SOA230 7-23


© SAP AG SOA230 7-24