power designer modelando la arquitectura de la empresa

8/8/2019 Power Designer Modelando La Arquitectura de La Empresa

http://slidepdf.com/reader/full/power-designer-modelando-la-arquitectura-de-la-empresa 1/50

PowerDesigner

Modelando la arquitectura de la empresaRoberto Olvera Sr. System Consultant

October 2008



Enterprise Architecture

Enter rise Architecture is a strate ic initiative that rovides 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)

nterpr se uepr nt

– Business –

– Technical

Sybase Confidential



Enterprise Architecture drivers

Enterprise Architectures to respond to

the following 3 key drivers: the need to better align IT systems with

business requirements

e nee or us ness an o responto competitive changes in a more agileway

the need to achieve regulatory

compliance and standards

Sybase Confidential



How do Enterprises Manage Change?

PowerDesigner is the

most effective tool thatallows organizations tomanage the ‘impact ofchange’ from business

technologicalimplementations andbe able to trace alltechnology changesdirectly to

specific business.

Sybase Confidential



PowerDesigner

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.

Ca ture, Mana e & Communicate

The Impact of Change in dynamic & complex enterprises

-

Integrated, Aligned & Agile Tooling Focused on

Modeling & Metadata Management

Sybase Confidential



PowerDesigner

PowerDesigner - Enterprise Architecture implementation from business goals through implementation

all architectural layers and perspectives of the Enterprise

Sybase Confidential



PowerDesigner features

Integrated modeling through standard methodologies:Data (E/R, Merise), Business (BPMN, BPEL, ebXML),Application (UML)

templates: SQL (with more than 50 supported DBMSs),Java, .NET

and update existing systems

A scalable enterprise repository solution with strongsecur y an vers on ng capa es o a mu -userdevelopment

Automated, customizable reporting capabilities

An extensible environment, permitting you to add newrules, commands, concepts and attributes to your

Sybase Confidential



PowerDesigner

PowerDesigner’s sophisticated inter- model and code and database generation

to synchronize your models and applications to prov e you w t control over each

and every

Sybase Confidential



PowerDesigner

tools for analyzing the dependencies

between model objects. When youperform an action on a model object,you can use:

Impact Analysis – to analyze the effectof the action on the objects thatde end on the initial ob ect.

Lineage Analysis – to identify theobjects that influence the initial object.

Sybase Confidential



Project Framework Matrix

A project allows you to group allthe models and other types ofdocuments you need to

accomplish a particular goal.

FEAF

Documents can be displayed in aproject diagram and includemodels and files with their

relationships. Framework matrix template help

to modeling process by providing agrid in which each cell must becompleted according to a set ofpredefined actions. Provides someof the most popular frameworks,including Zachman and FEAF andallows to create and customize

Sybase Confidential



Zachman Framework

Sybase Confidential



Modeling Techniques used by

Requirements, Business Process Models,Simple Data Models

All Models and Meta Data, Struggle most of

management.

UML (Unified Modeling Language)

Data Models (Conceptual, Physical)

Sybase Confidential



Modeling is NOT Development…

Sybase Confidential



PowerDesigner for BI/DW

Sybase Confidential



PowerDesigner for Model Driven Data

Analysis and Design

Development andDeployment

Sybase Confidential



PowerDesigner Architecture



Enterprise Architecture Model

The PowerDesigner enterprise architecture model (EAM) providesseven types of EA diagrams that allow you to model your businessprocesses and technology infrastructure, and to show the

relationshi s between them. The dia rams in the EAM are dividedinto three layers as follows:

• Business Layer• Or anization Chart

• Business Communication Diagram• Process Map -

• City Planning Diagram

• Application Layer• Application Architecture Diagram

• Service Oriented Diagram

• ec no ogy ayer• Technology Infrastructure Diagram

Sybase Confidential



Organization Chart

An Organization Chart

re resents the structure of an organization in a graphical tree format.

It can be used to analyze

and display the relationships between

• (divisions, groups, etc)

• Individuals and

• Roles

Sybase Confidential



Business Communication Diagram

A BusinessCommunicationdiagram can be usedto analyze anddis la :

• Relationships• Flows and

• Connections

between businesselements.

Sybase Confidential



Process Map

A process map

used to identify thebusinessarchitecture

people andorganization unitsand to describe:

• Businessfunctions and

• Classify theprocesses.

Sybase Confidential



City Planning Diagram

A Cit Plannin diagram allowsyou to focus onthe big picture ofyour enterprisearchitecture usingthe metaphor of

infrastructure of a

city.

Sybase Confidential



Application Architecture Diagram

An Application

Architecture diagramshows a high-levelview of the applicationarchitecture, and

allows to identify:• Applications, sub-a lications

• Components,

• Databases,• Services, etc,

and their interactions.

Sybase Confidential



Service Oriented Diagram

diagram allows you toassociate applications

the application layerwith business

objects in the

business layer to

design.

Sybase Confidential



Technology Infrastructure Diagram

A TechnologyInfrastructure

agram sp ays ahigh-level picture ofthe physicalarchitecturedeployed in the

enterprise.

Sybase Confidential

c



Requirements Model

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

, ,and/or other requirements

User allocation matrix views: links requirements andusers or groups who must meet these requirements duringa development process

Sybase Confidential



Requirements document view

Sybase Confidential

Traceability Matrix View



Traceability Matrix View -

Requirements from different hierarchies - to manage interconnected requirements.

Sybase Confidential

Traceability Matrix View Design



Traceability Matrix View – Design

Design objects (objects from other types of models) – to confirm that the requirements

Sybase Confidential

c



Business Process Model

• Define and anal ze the sco e of thebusiness process

High Level Analysis

– Describe data re uirements of business rocessessupported by the proposed system or Enterprise

Low Level Analysis – Describe the data specifications for the software

• Define and anal ze the main rocessesand their informational requirements

• earn w ere e us ness n orma oncomes from and what happens to it

Sybase Confidential



Business Process Model

Create as man interconnected business rocess dia ramas are needed to describe your system to a suitable level ofgranularity

,ebXML BPSS, ebXML CPA, BPEL4WS, or WS-BPEL

Reverse en ineer code from ebXML BPSS BPEL4WS or

WS-BPEL Simulate your model with the Simul8 application

Generate automatic PowerDesigner reports to documentyour model

Data Flow Diagram

Sybase Confidential



Process Hierarchy Diagram (PHD)

Specify the structure of a systemy ent y ng g - eve unct ons,

decompose processes to an

appropriate level of detail in ordero un ers an e unc onsrequired by your system.The PHD is mostly used during theana ys s p ase o a pro ect: Define all the processes performed

in the scope of a business function ocus on process recogn on an

enumeration

Decompose already identified- an appropriate atomic level isreached

Sybase Confidential



Business Process Diagram (BPD),

A business rocess diagram can becreated in a model, a package or withina decomposed process.

modeling different aspects of a system:

Top-level diagram – focuses on thero es p aye y us ness par ners n

relation to a system Choreography diagram – focuses on

a ocat ng respons ty or act v t es,choreographing objects, analyzing flows

of data, and modeling the implementationo ac v es

Data flow diagram – focuses on dataexchange between processes

Sybase Confidential

C l D M d l



Conceptual Data Model

A Conceptual Data Model (CDM)represents the logical structure ofa data system independent of any

software or data storage structure.a ows you o: Represent the organization of

data in a graphic format to create

(ERD). Verify the validity of data design.

(LDM), a Physical Data Model(PDM) or an Object-OrientedModel OOM which s ecifies anobject representation of the CDMusing the UML standard.

Sybase Confidential

D t Fl Di



Data Flow Diagram

A data flow dia ram DFD letsyou graphically represent the flowof data through a system without

.

Analysts can use DFD to modelthe functions a system has to

carry out and the interactionsbetween those functions in terms

processes

Sybase Confidential

L i l D t M d l



Logical Data Model

A Logical Data Model helps you design aata ase structure an per orm some

database denormalization actionsindependent of any specific DBMS physical

.

You can use a logical model as anintermediary step in the database design

Member

0..n

1..1

Division

Division number

Division name

Division address

<pi > ID

NAME

SHORT_TEXT

<M>

<M>

Idtf_1 <pi>

Team

Team number

Speciality

<p i> ID

SHORT_TEXT

<M>

Idtf_5 <pi>

physical designs: Start with a CDM containing entities,

attributes relationshi s domains data items

Chiefsupervises

0..1

0..n

Is member of

1..n

Works on 1..1

Belongs to

1..n

Employee

Employee number

First na me

Last name

Employee function

Employee salary

<p i> ID

NAME

NAME

NAME

MONEY

<M>

<M>

f i

Task

Task name

Task cost

<pi> NA ME

MONEY

<M>

<M>

Idt f_6 <pi>

and business rules.

Generate an LDM. Create indexes and

specify FK column names and other

Is done by1..1

1..n0..n

_

Participate

Start date (par)

End date (par)

D

D

common ea ures

Generate one or more PDMs, each targetedto a specific DBMS implementation

Sybase Confidential

c

Ph sical Diagram



Physical Diagram

A h sical dia ram allows ou to definea database structure from the physicalimplementation point of view. It takes into

,data storage structures and software, todescribe the structure of the database.

You build a physical diagram at the end,

start the software programming. The

physical diagram allows you to defineow ata rom conceptua mo e are

implemented in the database.

Sybase Confidential



ILM Information Liquidity Model



ILM Information Liquidity Model

enterprise. Data movement modeling allows you to

model where data originates to where it is loaded, andhow 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

,such as Replication Server and MobiLink.

Data transformation – Data from diverse sources arecombined to be extracted, transformed, and loaded tooutput sources via ETL (Extract Transform and Load)

Sybase Confidential

.

Data Replication



Data Replication

A replication process is a server engine that copies data from a given database into

• Publications – Specifies a set of data to

replicate, and from where it was extracted.

one or more a a ases or rep ca on processes.

Publications contain tables of the replicateddatabase and, which point to the tables of thesource database.

• –

replicated by indicating which replicateddatabase subscribes to which publication.

• Users – Specifies who is involved in the

replication process.

• Connection groups – Specifies a logical

group for database connections.• ven scr p s – pec es ow even s on e

process are implemented.

Sybase Confidential

Data Transformation



Data Transformation

A data transformation contains the detail of how data is extracted from datain uts transformed b actions and loaded into data out uts. At each ste ofthe transformation, you can display a mapping between the current data andits parent.

Sybase Confidentialc

Object Oriented Model




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

.is the standard language for object-oriented modeling.

notations of the Unified Modeling Language (UML).

Build an Object-Oriented Model (OOM) using the standard UMLdiagrams

Generate and reverse engineer Java, C#, VB.NET, andPowerBuilder files

Generate code for C++, Visual Basic, IDL-CORBA, etc. enerate , serv ets, an components Generate Conceptual Data Models (CDMs), Physical Data Models

(PDMs), XML Models (XSMs), and other Object-Oriented Models

Generate an OOM from a CDM, PDM, XML, or other OOM

Sybase Confidential




A use case diagram is a high level UML diagram for analyzing requirements and systembehavior. It is part of an Object-Oriented Model (OOM), and graphically models thefunctionality of the system in the form of use cases, and how outside users, called actors,interact with them.

Sybase Confidential




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




Activity Diagram is a UML diagram that models

e ynam c aspec s o a sys em. s a s mp ca onof the UML statechart diagram for modeling controlflows in computational and organizational processes.

Sybase Confidentialc

XML Model



XML Model

Since XML structures can be very complex, it is much easier tovisualize them through comprehensive and explicit diagrams,than to read XML-coded pages.

An XML model XSM is a ra hical re resentation of: an XML Schema Definition file (.XSD),

a Document Type Definition file (.DTD) or

- . .

XML is increasin l used to hold a lication data because it: describes and structures data, whereas HTML only displays

data

uses a self-describin and ersonalized s ntax can be exchanged between incompatible systems, since data is

stored in plain text format

Sybase Confidential

XML Model



XML Model

Build and check XML models

,models

,

XDR files

Model (PDM), Object Oriented Model (OOM), or

another XSM

Sybase Confidential

XML Schema



Sc e a

The following example shows the diagram of an XSM which models an XML schema

xs:annotation

Element<xs:element minOccurs="0" ref="xs:annotation"/>

for Resume documents

SC typeDefParticle

complexRestrictionType

{- xs:restrictionT ype}

attrDecls<xs:complexType name="complexRestrictionType">

<xs:complexContent><xs:restriction base="xs:restrictionType">

<xs:sequence><xs:element minOccurs="0" ref="xs:annotation"/>

Group<xs:group ref="xs:attrDecls">

</xs:group>

<xs:choice minOccurs="0"><xs:annotation>

<xs:documentation>This choice is added simply tomake this a valid restriction per the REC</xs:documentation>

</xs:annotation>" "

</xs:group></xs:choice><xs:group ref="xs:attrDecls">

</xs:group></xs:sequence>

Sybase Confidential

<xs:anyAttribute namespace="##other" processContents="lax"/>

</xs:restriction></xs:complexContent></xs:complexType>

c

BPM - Impact and lineage analysis



p g y

(BPM Sample)

Flow Flow_36

[Lineage]

(BPM Sample)

Decision Parall el(AND)_7

[Lineage](BPM Sample)

Flow Flow_35

[Lineage]

ece ve ssue s

Review Issue List

(BPM Sample)

Flow Flow_9

[Lineage]

Process E-mail Results of Vote

[Lineage]

Process Post Results on Web Site

[Lineage]

(BPM Sample)

Flow Flow_33

[Lineage]

[7 Days]

<<Vote>>

Discussion Cycle Announce Issues Collect Votes

(BPM Sample)

Flow Flow_22

[Lineage]

(BPM Sample)

Process Prepare Results

[Lineage]

repare esut s

Post Results on Web Site E-mail Results of Vote

(BPM Sample)

Process Collect Votes

[Lineage]

(BPM Sample)

Flow Message Flow_23

[Lineage]<<Dealine Warning>>

<<Issue Announcement>>

<<Vote Results>><<Vote Announcement>>

(BPM Sample)

Flow Flow_30

[Lineage]

(BPM Sample)

Process Voting M embers

[Lineage]

(BPM Sample)

Flow Message Flow_33

[Lineage]

(BPM Sample)

Flow Message Flo w_34

[Lineage]

<<Deadline Warning>>

Voting Members

Sybase Confidential

(BPM Sample)Process Announce Issues

[Change]

CDM - Impact and lineage analysis



p g y

Division

Team

Team number

Speciality

<pi>

Idt f_5 <pi>(Project Management (CDM))

Chief

supervises0..1

Member

0..n

Is member of1..n

Belongs to

1..1

Division numb er

Division nam e

Division address

<pi>

Idt f_1 <pi>

Customer

Customer number

Customer name

Customer address

Customer activity

Customer tel ephone

Customer fax

<pi>

Idtf 3 <pi >

(Project Management (CDM))

Data Item Division address

[Lineage]

[Lineage]

Subcontract

Subcontract1..1

0..n

Used

0..n

Uses0..n

Is responsible forIs manager of

0..1

0..n

0..n

Works on

1..1

1..n Employee number

First name

Last name

Employee function

Employee salary

<pi>

Idt f_2 <pi>

_

Project

Project number <pi>


Entity Attribute Division.Division address

[Change]

Relationships

RelationshipsRelationships

Relationships(Project Management (CDM))

Entity Customer

Change


Entity Task

Change

roec anagemen

Entity Participate

[Change]

composes0..n

composed of0..n

Belongs to

1..1

0..n

Is done by1..11..n

0..nProject name

Project label

Idt f_4 <pi>

Task

Material

Material number

Material name

Material type

<pi>

Idt f_7 <pi>

Participate

Start date (par)

End date (par)

Activity

RelationshipsRelationshipsRelationships



Entity Material

[Change]


Entity Team

[Change]


Entity Project

[Change]

ComposeTask name

Task cost

<pi>

Idt f_6 <pi>

Start date (act)

End date (act)

Relationships

RelationshipsRelationshipsRelationshipsRelationshipsRelationshipsRelationships


Entity Employee

[Change]


Conceptual Data Model Project M anagement (CDM)

[Lineage]

Entity impact

Sybase Confidential


(Project Management (CDM))Entity Division

[Change]