You are on page 1of 50

PowerDesigner

Modelando la arquitectura de la empresa


Roberto Olvera Sr. System Consultant
October 2008
Enterprise Architecture

Enterprise
p Architecture is a strategic
g initiative that provides
p
alignment and integration for increasingly dynamic and
complex environments resulting in business agility.

Enterprise Architecture perspectives


ƒ As is …. To be
ƒ Information Management and data Lineage
(critical and sensitive)
ƒ Enterprise
E t i Blueprint
Bl i t
– Business
– Information
– Technical

Sybase Confidential
Enterprise Architecture drivers

Businesses today are implementing


Enterprise Architectures to respond to
the following 3 key drivers:
ƒ the need to better align IT systems with
business requirements
ƒ the
th need
d ffor Business
B i andd IT to
t respondd
to competitive changes in a more agile
way
ƒ the need to achieve regulatory
compliance and standards

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

PowerDesigner is an integrated modeling solution that empowers effective


Enterprise Architecture through clear, concise, and accurate, metadata synergy
from all three views of the organization: business, information, and technology.

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

PowerDesigner provides powerful


tools for analyzing the dependencies
between model objects. When you
perform an action on a model object,
you can use:
ƒ Impact Analysis – to analyze the effect
of the action on the objects that
p
depend on the initial object.
j

ƒ Lineage Analysis – to identify the


objects that influence the initial object.

Sybase Confidential
Project Framework Matrix

ƒ A project allows you to group all


the models and other types of
documents you need to FEAF
accomplish a particular goal.
ƒ Documents can be displayed in a
project diagram and include
models and files with their
relationships.
ƒ Framework matrix template help
to modelinggpprocess byypproviding
ga
grid in which each cell must be
completed according to a set of
predefined actions. Provides some
of the most popular frameworks,
including Zachman and FEAF and
allows to create and customize

Sybase Confidential
Zachman Framework

Sybase Confidential
Modeling Techniques used by
Different Roles

Requirements, Business Process Models,


Simple Data Models

All Models and Meta Data, Struggle most of


the time with integration and change
management.

UML (Unified Modeling Language)

Data Models (Conceptual, Physical)

Sybase Confidential
Modeling is NOT Development…
Where Tools Overlap

Sybase Confidential
PowerDesigner for BI/DW

Sybase Confidential
PowerDesigner for Model Driven Data
Integration

Analysis and Design

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

A Requirements Model (RQM) describes a project by


listing and explaining precisely what actions must be
implemented during a development process.
Offers three types of views:
ƒ Requirements document views: numbered lists of
requirements with a common set of properties
ƒ Traceability matrix views: links requirements and design
objects (objects from other types of models)
models), external files
files,
and/or other requirements
ƒ User allocation matrix views: links requirements and
users or groups who must meet these requirements during
a development process

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

• Define and analyze


y the main p processes
and their informational requirements

• 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

ƒ Create as manyy interconnected business p g


process diagram
as are needed to describe your system to a suitable level of
granularity
ƒ Generate code for Sybase WorkSpace Business Process,
Process
ebXML BPSS, ebXML CPA, BPEL4WS, or WS-BPEL
ƒ Reverse engineer
g code from ebXML BPSS,, BPEL4WS,, or
WS-BPEL
ƒ Simulate your model with the Simul8 application
ƒ Generate automatic PowerDesigner reports to document
your model
ƒ Import a Process Analyst Model (PAM) version 6 into a
Data Flow Diagram

Sybase Confidential
Process Hierarchy Diagram (PHD)

Specify the structure of a system


by identifying
b id tif i hihigh-level
hl l ffunctions,
ti
decompose processes to an
appropriate level of detail in order
t understand
to d t d the th functions
f ti
required by your system.
The PHD is mostly used during the
analysis
l i phase
h off a project:
j t
ƒ Define all the processes performed
in the scope of a business function
ƒ Focus
F on process recognition
iti andd
enumeration
ƒ Decompose already identified
processes into sub-processes until
an appropriate atomic level is
reached

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

A Conceptual Data Model (CDM)


represents the logical structure of
a data system independent of any
software or data storage structure.
A CDM allows
ll you tto:
ƒ Represent the organization of
data in a graphic format to create
Entity Relationship Diagrams
(ERD).
ƒ Verify the validity of data design.
ƒ Generate a Logical Data Model
(LDM), a Physical Data Model
(PDM) or an Object-Oriented
Model ((OOM), ), which specifies
p an
object representation of the CDM
using the UML standard.

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

A Logical Data Model helps you design a


database
d t b structure
t t andd perform
f some
database denormalization actions
independent of any specific DBMS physical
requirements
requirements. Division name
Di i i
Division
Division number <pi> ID
NAME
<M>
<M>
T
Team
T eam number <pi> ID
Speciality SHORT _TEXT
<M>

Division address SHORT_T EXT

You can use a logical model as an Idtf_1 <pi>


Idtf_5 <pi>

intermediary step in the database design


0..n
1..1

process between the conceptual and B l


Belongs tto
Member

Is member of supervises

physical designs: Task


1..n
Employee
1..n 0..1 Chief

ƒ 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

attributes, relationships, domains, data items


Works on 1..1 Employee salary MONEY
Idtf 2 <pi>
Idtf_2
1..1
Is done by 0..n

and business rules. 1..n

Participate

ƒ Generate an LDM. Create indexes and


Start date (par) D
End date (par) D

specify FK column names and other


common features
f t
ƒ Generate one or more PDMs, each targeted
to a specific DBMS implementation

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.

You build a physical diagram at the end


of the data analysis process
process, before you
start the software programming. The
physical diagram allows you to define
h
how d
data
t ffrom conceptual
t l model
d l are
implemented in 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

The movement of data is a central concern for the


enterprise. Data movement modeling allows you to
model where data originates to where it is loaded, and
how it is transformed on the way.
ILM is a graphical modeling environment focused on
data movement, which lets you model:
ƒ Data replication – Data are replicated from source
databases to target databases via replication engines,
engines
such as Replication Server and MobiLink.
ƒ Data transformation – Data from diverse sources are
combined to be extracted, transformed, and loaded to
output sources via ETL (Extract Transform and Load)
and EII (Enterprise Information Integration).
Integration)

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

An Object-Oriented Model (OOM) is a graphical analysis of a system using the


symbols and language notations of the Unified Modeling Language (UML)
(UML). UML
is the standard language for object-oriented modeling.

ƒ Is a graphical analysis of a system using the symbols and language


notations of the Unified Modeling Language (UML).
ƒ Build an Object-Oriented Model (OOM) using the standard UML
diagrams
ƒ Generate and reverse engineer Java, C#, VB.NET, and
PowerBuilder files
ƒ Generate code for C++, Visual Basic, IDL-CORBA, etc.
ƒ Generate
G t EJB,
EJB servlets,
l t and d JSP componentst
ƒ Generate Conceptual Data Models (CDMs), Physical Data Models
(PDMs), XML Models (XSMs), and other Object-Oriented Models
(OOMs) from your OOM
ƒ Generate an OOM from a CDM, PDM, XML, or other OOM

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

A sequence diagram is a UML interaction diagram. It represents the chronology of the


passing of messages between system objects and actors. It may be used to illustrate a
possible scenario of a use case, the execution of an operation, or simply an interaction
scenario between classes of the system.

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

Since XML structures can be very complex, it is much easier to


visualize them through comprehensive and explicit diagrams,
than to read XML-coded pages.
An XML model (XSM) is a graphical representation of:
ƒ an XML Schema Definition file (.XSD),
ƒ a Document Type Definition file (.DTD) or
ƒ an XML-Data
XML Data Reduced file ((.XDR).
XDR)

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

A PowerDesigner XSM allows you to:


ƒ Build and check XML models
ƒ Map objects in
in, and create reports of XML
models
ƒ Generate and reverse engineer XSD
XSD, DTD and
XDR files
ƒ Generate an XML model from a Physical Data
Model (PDM), Object Oriented Model (OOM), or
another XSM

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

Complex Type attrDecls


<xs:complexType name="complexRestrictionType">
<xs:complexContent>
<xs:restriction base="xs:restrictionType">
Group
<xs:group ref="xs:attrDecls">
<xs:sequence>
</xs:group>
<xs:element minOccurs="0" ref="xs:annotation"/>
<xs:choice minOccurs="0">
<xs:annotation>
<xs:documentation>This choice is added simply to
make this a valid restriction per the REC</xs:documentation>
</xs:annotation>
<xs:group ref=
ref="xs:typeDefParticle">
xs:typeDefParticle >
</xs:group>
</xs:choice>
<xs:group ref="xs:attrDecls">
</xs:group>
</xs:sequence>
<xs:anyAttribute namespace="##other"
## processContents="lax"/>
C /
</xs:restriction>
</xs:complexContent> c
</xs:complexType>
Sybase Confidential
BPM - Impact and lineage analysis

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]

(BPM Sample) (BPM Sample)


Discussion Cycle Announce Issues Process Post Results on Web Site Process E-mail Results of Vote
Collect Votes
[Lineage] [Lineage]

(BPM Sample) (BPM Sample)


[7 Days]
Flow Flow_33 Flow Flow_9
[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) (BPM Sample) (BPM Sample)


Flow Message Flow_33 Flow Message Flow_34 Flow Flow_30
[Lineage] [Lineage] [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

You might also like