Professional Documents
Culture Documents
Enterprise
p Architecture is a strategic
g initiative that provides
p
alignment and integration for increasingly dynamic and
complex environments resulting in business agility.
Sybase Confidential
Enterprise Architecture drivers
Sybase Confidential
How do Enterprises Manage Change?
PowerDesigner is the
most effective tool that
allows organizations to
manage the ‘impact of
change’ from business
goals down to the
technological
implementations and
be able to trace all
technology changes
directly to
specific business
goals.
goals
Sybase Confidential
PowerDesigner
Value in Enterprise Architecture
Capture,
p Manage
g & Communicate
The Impact of Change in
dynamic & complex enterprises
-
Integrated, Aligned & Agile Tooling
Focused on
Modeling & Metadata Management
Sybase Confidential
PowerDesigner
Enterprise Architecture
PowerDesigner - Enterprise Architecture implementation from business goals through implementation
using unique Link and Synch technology; automatically and intuitively captures the intersections between
all architectural layers and perspectives of the Enterprise
Sybase Confidential
PowerDesigner features
Integrated
g modeling g through
g standard methodologies:g
Data (E/R, Merise), Business (BPMN, BPEL, ebXML),
Application (UML)
Automatic code generation through customizable
templates: SQL (with more than 50 supported DBMSs),
Java, .NET
Powerful reverse engineering capabilities to document
and update existing systems
A scalable enterprise repository solution with strong
security
it and
d versioning
i i capabilities
biliti to
t aid
id multi-user
lti
development
Automated, customizable reporting g capabilities
An extensible environment, permitting you to add new
rules, commands, concepts and attributes to your
modeling and coding methodologies
Sybase Confidential
PowerDesigner
Linking and synchronizing models
PowerDesigner’s
sophisticated
hi i d iinter-
model and code and
database generation
capabilities allow you
to synchronize your
models and
applications to
id you with
provide ith
control over each
and every
modification.
Sybase Confidential
PowerDesigner
Impact and Lineage Analysis
Sybase Confidential
Project Framework Matrix
Sybase Confidential
Zachman Framework
Sybase Confidential
Modeling Techniques used by
Different Roles
Sybase Confidential
Modeling is NOT Development…
Where Tools Overlap
Sybase Confidential
PowerDesigner for BI/DW
Sybase Confidential
PowerDesigner for Model Driven Data
Integration
Development and
Deployment
Sybase Confidential
PowerDesigner Architecture
Models
PowerDesigner Architecture
Sybase Confidential
Enterprise Architecture Model
g
The PowerDesigner (
enterprise architecture model (EAM)) provides
seven types of EA diagrams that allow you to model your business
processes and technology infrastructure, and to show the
p between them. The diagrams
relationships g in the EAM are divided
into three layers as follows:
• Business Layer
• Organization Chart
• Business Communication Diagram
• Process Map -
• City Planning Diagram
• Application Layer
• Application Architecture Diagram
• Service Oriented Diagram
• Technology
T h l Layer
L
• Technology Infrastructure Diagram
Sybase Confidential
Organization Chart
An Organization Chart
represents
p the structure of
an organization in a
graphical tree format.
IIt can be
b used d to analyze
l
and display the
relationships between
• Organization units
(divisions, groups, etc)
• Individuals and
• Roles
Sybase Confidential
Business Communication Diagram
A Business
Communication
diagram can be used
to analyze and
display:
• Relationships
• Flows and
• Connections
between business
elements.
Sybase Confidential
Process Map
A process map
diagram can be
used to identify the
business
architecture
independent of
people and
organization units
and to describe:
• Business
functions and
y the
• Classify
processes.
Sybase Confidential
City Planning Diagram
A City Planning
diagram allows
you to focus on
the big picture of
your enterprise
architecture using
the metaphor of
planning the
infrastructure of a
city.
Sybase Confidential
Application Architecture Diagram
An Application
Architecture diagram
shows a high-level
view of the application
architecture, and
allows to identify:
• Applications, sub-
applications,
pp ,
• Components,
• Databases,
• Services, etc,
and their interactions.
Sybase Confidential
Service Oriented Diagram
A Service Oriented
diagram allows you to
associate applications
and other objects in
the application layer
with business
services and other
objects in the
business layer to
assist with SOA
design.
Sybase Confidential
Technology Infrastructure Diagram
A Technology
Infrastructure
di
diagram displays
di l a
high-level picture of
the physical
architecture
deployed in the
enterprise.
c
Sybase Confidential
Requirements Model
Sybase Confidential
Requirements document view
Sybase Confidential
Traceability Matrix View -
Requirements
Requirements from different hierarchies - to manage interconnected requirements.
Sybase Confidential
Traceability Matrix View – Design
Objects
Design objects (objects from other types of models) – to confirm that the requirements
have been integrated in the analysis and design processes
Sybase Confidential
Business Process Model
y the scope
• Define and analyze p of the
business process
High Level Analysis
– Describe data requirements
q of business p
processes
supported by the proposed system or Enterprise
Low Level Analysis
– Describe the data specifications for the software
modules impacted by the IT project
• Learn
L where
h the
th business
b i information
i f ti
comes from and what happens to it
Sybase Confidential
Business Process Model
Sybase Confidential
Process Hierarchy Diagram (PHD)
Sybase Confidential
Business Process Diagram (BPD),
A business p g
process diagram can be
created in a model, a package or within
a decomposed process.
There are three types of BPDs for
modeling different aspects of a system:
Top-level diagram – focuses on the
roles
l played
l db
by b
business
i partners
t iin
relation to a system
Choreography diagram – focuses on
allocating
ll ti responsibility
ibilit ffor activities,
ti iti
choreographing objects, analyzing flows
of data, and modeling the implementation
off activities
ti iti
Data flow diagram – focuses on data
exchange between processes
Sybase Confidential
Conceptual Data Model
Sybase Confidential
Data Flow Diagram
g
A data flow diagram ((DFD)) lets
you graphically represent the flow
of data through a system without
any indication of time
time.
Analysts can use DFD to model
the functions a system has to
carry out and the interactions
between those functions in terms
of data exchanges between
processes
Sybase Confidential
Logical Data Model
Is member of supervises
Start with a CDM containing entities, Task name <pi> NAME <M> Employee number <pi> ID <M> 0..n
Task cost MONEY <M> First name NAME
Idtf_6 <pi> Last name NAME <M>
Employee function NAME
Participate
c
Sybase Confidential
Physical Diagram
Ap y
physical g
diagram allows yyou to define
a database structure from the physical
implementation point of view. It takes into
account the physical resources: DBMS
DBMS,
data storage structures and software, to
describe the structure of the database.
Sybase Confidential
Multidimensional Diagram
g
A multidimensional diagram is a
model of business activities in terms
of cubes and dimensions. It
g
organizes business data into one or
other of these categories.
The multidimensional diagram is
used to design the cubes in an OLAP
engine, together with the different
analysis dimensions.
Business analysts use OLAP
databases to send queries and
retrieve business information from the
different dimensions existing in the
database.
c
Sybase Confidential
ILM Information Liquidity Model
Sybase Confidential
Data Replication
A replication process is a server engine that copies data from a given database into
one or more databases
d t b or replication
li ti processes.
• Publications – Specifies a set of data to
replicate, and from where it was extracted.
P bli ti
Publications contain
t i ttables
bl off th
the replicated
li t d
database and, which point to the tables of the
source database.
• Subscriptions – Specifies where the data is
replicated by indicating which replicated
database subscribes to which publication.
• Users – Specifies who is involved in the
replication process.
• Connection groups – Specifies a logical
group for database connections.
• Event
E t scripts
i t – Specifies
S ifi h
how events t on th
the
process are implemented.
Sybase Confidential
Data Transformation
A data transformation contains the detail of how data is extracted from data
p , transformed by
inputs, y actions and loaded into data outputs.
p p of
At each step
the transformation, you can display a mapping between the current data and
its parent.
c Sybase Confidential
Object Oriented Model
Sybase Confidential
Object Oriented Model
Use Case Diagram
A use case diagram is a high level UML diagram for analyzing requirements and system
behavior. It is part of an Object-Oriented Model (OOM), and graphically models the
functionality of the system in the form of use cases, and how outside users, called actors,
interact with them.
Sybase Confidential
Object Oriented Model
Sequence Diagram
Sybase Confidential
Object Oriented Model
Diagrams
Activity Diagram is a UML diagram that models
the
th dynamic
d i aspects
t off a system.
t It is
i a simplification
i lifi ti
of the UML statechart diagram for modeling control
flows in computational and organizational processes.
c Sybase Confidential
XML Model
XML is increasingly
g y used to hold application
pp data because it:
describes and structures data, whereas HTML only displays
data
uses a self-describing
self describing and personalized syntax
can be exchanged between incompatible systems, since data is
stored in plain text format
Sybase Confidential
XML Model
Sybase Confidential
XML Schema
The following example shows the diagram of an XSM which models an XML schema
for Resume documents Element
<xs:element minOccurs="0" ref="xs:annotation"/>
xs:annotation
complexRestrictionType
S
{- xs:restrictionType} C typeDefParticle
R
Receive
i IIssue Li
Listt
(BPM Sample)
Decision Parallel(AND)_7
[Lineage]
(BPM Sample) (BPM Sample)
Flow Flow_35 Flow Flow_36
Review Issue List
[Lineage] [Lineage]
<<Vote>>
Vote
P
Prepare R
Results
lt
(BPM Sample)
Process Prepare Results
[Lineage]
(BPM Sample)
Flow Flow_22
Post Results on Web Site E-mail Results of Vote
[Lineage]
(BPM Sample)
Process Collect Votes
[Lineage]
<<Vote Announcement>>
<<Vote Results>>
(BPM Sample)
<<Issue Announcement>> Flow Message Flow_23
<<Dealine Warning>> [Lineage]
<<Deadline Warning>>
(BPM Sample)
Process Voting Members
Voting Members
[Lineage]
(BPM Sample)
Process Announce Issues
[Change]
Sybase Confidential
CDM - Impact and lineage analysis
Team
Team number <pi>
Speciality
(Project Management (CDM))
Division Idtf_5 <pi>
Division number <pi> Field Impact Domain Short description
[Lineage]
Division name
Division address 0..n
Customer
Idtf_1 <pi>
Customer number <pi>
Member Customer name
Chief (Project Management (CDM))
1..1 Customer address
Is membersupervises
of Customer activity Data Item Division address
1..n 0..1 Customer telephone
Belongs to [Lineage]
Customer fax
Employee Idtf 3 <pi>
Idtf_3 pi
1..n Employee number <pi> 0..n
First name Is manager of
Is responsible for (Project Management (CDM))
Subcontract
Last name 0..1 Entity Attribute Division.Division address
1..1
Employee function Subcontract
Employee salary [Change]
Uses 0..n 0..n
Idtf_2 <pi>
Used 0..n
Project
0..n
1..1
Project number <pi>
Works on (P j t M
(Project Managementt (CDM))
P j t name
Project
Material 0..n
Project label Entity Participate
Material number <pi> Idtf_4 <pi> [Change]
Material name Participate
Material type
Start date (par)
Idtf_7 <pi> 1..1
End date (par)
Belongs to Relationships
0..n
Relationships
composes
composed of 1..1 by
Is done (Project Management (CDM)) (Project Management (CDM))
1..n
0..n0..n Entity Task Entity Customer
Task Activity
[Change] [Change]
Task name <pi> Start date (act)
Compose
Task cost End date (act)
Idtf_6 <pi>
Relationships
Relationships
Relationships
(Project Management (CDM)) (Project
Relationships
Management (CDM)) (Project Management (CDM))
Entity Team Entity Project Entity Material
[Change] [Change] [Change]
Relationships
Relationships Relationships
Entity impact Relationships (Project Management (CDM))
Conceptual Data Model Project Management (CDM)
(Project Management (CDM)) [Lineage]
Entity Employee
[Change]
Relationships
Relationships
(Project Management (CDM))
Entity Division
[Change]
Sybase Confidential