initiative for a public method [email protected]@praxeme.org +33...

15
nitiative for a public method [email protected] +33 (0) 6 77 62 31 75 ttp://www.praxeme.org ttp://dvau.praxeme.org Reference Version Protection Enterprise Architecture: a Method 2008-11-20 SLB-25 How a comprehensive approach of the enterprise can really change our systems « Theory without practice is useless; practice without theory is blind. » Immanuel Kant

Upload: eleanore-floyd

Post on 12-Jan-2016

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

Initiative for a public method

[email protected] +33 (0) 6 77 62 31 75 http://www.praxeme.orghttp://dvau.praxeme.org

Reference VersionProtection

Enterprise Architecture: a Method

2008-11-20SLB-25

How a comprehensive approach of the enterprise can really change our systems

« Theory without practice is useless; practice without theory is blind. »Immanuel Kant

Page 2: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12SLB-25 2

Presentation objective

Objective

Topics Architecture EA, TOGAF Modeling MDA Methodology, training, transition

Provide insight into the state of the art and advanced practices

Document protection

Page 3: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12

Dictum

1. Separation of concerns An ancient principle, in place since the beginning of

software engineering2. Continuity of the transformation chain

Strategy, EA, organization, logical architecture, software, physical architecture…

EA & SOA3. Isolation of the sources of variations

Time binding: adapt the enterprise to a changing environment Facilitate sustainable transformation

Space binding: reconfigure the Enterprise System Ensure convergence and interoperability

SLB-25 3

Page 4: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12

Novelties

SLB-25 4

Page 5: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12

How to do

1. Need for a methodological framework What are the different kinds of models? How to organize the skills?

2. “Productive” models If we are to produce different models, we want them to link

together Partial automation to obtain new modeling elements or to generate

the code

SLB-25 5

Page 6: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12

Which framework?

Zachman’s framework Cross questions and scopes

Enterprise Architecture Four levels of representation

Poorly articulated

Merise Levels of abstraction

Crossed with data/function separation

SLB-25 6

Technology Architecture

Data Architecture

Application Architecture

Business Architecture

Page 7: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12SLB-23 7

Pragmatic aspect

Business: the “good” description

Approach by activities Classical approach

Flawed with local variation

Functional & hierarchical breakdown structure

Semantic modelling Additional approach

Move to genericity New solution to cope

with complexityActors & organisational entitiesProcess & use-cases

Business objects, real objects(Information+Transformation+Action)

Semantic aspect

Refers to

Page 8: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12

Determine the software structure from the business description Applying MDA

standard Independence from

technical choices Technical Target free Long term

SLB-23 8

Software: the “good” structure

Pragmatic aspect

Semantic aspect Logical aspect

Derives

Derives

Logical services & aggregates(logical machines…)

Core Stratum

Organization Stratum

Interaction Stratum

Page 9: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12SLB-23 9

FD FD FD FD

Caricature of an architecturebased upon functional approach

Logical blocks take in charge functional domainsWhich structure the pragmatic modelIt stems from that important dependencies orredundancies since same business objects are usedinside many functional domains

BO

BO

FD FD FD FD

OD

OD OD

OD OD

Outlined logical architectureaccording to Praxeme method

Several logical blocks match with the objects domainsfrom semantic model.Dependencies obey topological constraints•Between strata (“Business Core”, “Organization”, “Interaction”)•Coupling reducing,•No dependency between FD, unless special cases, •etc.

Logical architecture: a new approach

FD: functional domainBO: business objectOD: objects domain

Page 10: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12

LogiqueSémantique

Pragmatique

Géographique Matériel

Technique

Logiciel

Physique

Logical aspect

Semanticaspect

Pragmatic aspect

Geographic aspect

Hardware

Technical aspect

Software

Physical aspect

The Enterprise System Topology

Page 11: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12

The method in a nutshell

Architectural decisions Define the objects domains

Semantic aspect

Define the functional domains Pragmatic aspect

Establish the logical architecture graph Logical aspect Choose style and express rules

Topological rules, derivation rules…

Approach First step using functional approach Then, correct by introducing semantic and endeavoring to

simplify the structureSLB-25 11

Page 12: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12

Conclusion

For further information The site of the association “Praxeme Institute”

http://www.praxeme.org

The site of the “Sustainable IT Architecture” community http://www.sustainableitarchitecture.com/

Next events Workshop around Christophe Roche, “Praxeme and ontologies” Symposium 2008, free conference

Register to keep in touch http://groups.google.com/group/Praxeme-Annonces

SLB-23 12

Help us to help you: please join us in our efforts!

Page 13: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12SLB-23 13/38

The Zachman framework

Page 14: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12SLB-23 14

The three chapters of methodology

WHAT

HOW(collective) (individual)

Page 15: Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75

“Enterprise Architecture: a Method”www.praxeme.org /12SLB-23 15

Position of current assets

WHAT

HOW(collective) (individual)

Start: the kinds of architecture…

Start: the kinds of architecture…

Detailed how-to-do ?

Detailed how-to-do ?