Enterprise Architecture as Inventory A Practical Guide to Establishing an Enterprise Architecture LonsdaleSystems.com

www.lonsdalesystems.com Presenter: Phil

Robinson

© Lonsdale Systems

1

Inventory A detailed descriptive list of articles, with number, quantity and value of each. Macquarie Dictionary

© Lonsdale Systems

2

Pythonesque Absurdly or surreally comical in a way that is reminiscent of the 1970s British TV comedy show Monty Python's Flying Circus MSN Encarta

© Lonsdale Systems

3

Enterprise Architecture the “Grand Plan”

© Lonsdale Systems

4

The Zachman Framework Data What?

Function Network How?

Where?

People

Time

Motivation

Who?

When?

Why?

Scope Planner

Business Model Owner

System Model Designer

Technology Model Builder

Detailed Definition Sub-Contractor

The Enterprise

© Lonsdale Systems

5

The Zachman Framework

© Lonsdale Systems

6

Zachman is the “what” of enterprise architecture

© Lonsdale Systems

7

The Open Group Architecture Framework (TOGAF) The objectives are… …Baseline Business Architecture …Target Business Architecture The objective is to develop Target Architectures … Data and Application Systems… The objective is to develop a Technology Architecture …basis of the following implementation work… © Lonsdale Systems

8

© Lonsdale Systems

9

TOGAF is the “how” of enterprise architecture

Yes! It is the Titanic…

© Lonsdale Systems

10

I fink that talkin ‘bout the UML makes me sound really, really intelligent…

Unified Modelling Language (UML) the “Grand Plan”

© Lonsdale Systems

11

What is the UML? OMG UML 2.0 Infrastructure Specification says… The UML is a visual language for specifying, constructing and documenting the artefacts of systems…

© Lonsdale Systems

12

The Unified Modelling Language (UML) «artifact» Object

Artifact

The UML is a notation not a methodology or process…

Class

Package

Use Case

Actor

Node

Component

© Lonsdale Systems

13

UML Diagrams

Structure Diagram

Class Diagram

Object Diagram

© Lonsdale Systems

Deployment Diagram

Component Diagram

Composite Structure Diagram

Package Diagram

14

UML Diagrams Behaviour Diagram

State Machine Diagram

Activity Diagram

Interaction Diagram

Sequence Diagram

Communication Diagram

© Lonsdale Systems

Interaction Overview Diagram

Use Case Diagram

Timing Diagram

15

UML is the detailed “what” of enterprise architecture

© Lonsdale Systems

16

Repository Based Tools the “Grand Plan”

© Lonsdale Systems

17

Enterprise Architect

• Repository-based UML modelling tool • Full support for UML 2.1.1

© Lonsdale Systems

18

© Lonsdale Systems

19

Repository based tools are… err the “tools” of enterprise architecture

© Lonsdale Systems

20

But now for something complexly different …

© Lonsdale Systems

21

Welcome to the “real world”…

‰ ‰ ‰ ‰

What have we got? What do we keep? What do we replace? What do we retire?

© Lonsdale Systems

22

Oh! And where are the life boats?

© Lonsdale Systems

23

Extreme Architecture Framework: A minimalist framework for modern times Phil Robinson and Floris Gout,

Enterprise System Architecture In Practice, IDEA Group Inc.

www.extremearchitecture.org © Lonsdale Systems

24

Systems Industry Sector

Enterprise

Human Activity Systems

Business Process

Application

Software Systems

Component © Lonsdale Systems

25

Systems vs. Zachman Roles

• Systems Mmmm… precisely defined by a boundary Am I “planner” I thought I was – Roles areasubjective or anbut “owner”… builder it turnsengineering approach • Encourages systems out I’mofaresponsibilities sub– Allocation contractor… – Consideration of interoperability

• Systems can be decomposed into components – Object-oriented architecture – Component-based architecture – Service-oriented architecture © Lonsdale Systems

26

Infrastructure

Business

Technology

Data

Software

Information

Activity

Views of an Enterprise

Information Systems © Lonsdale Systems

27

Views I keepvs. six Zachman honest serving Imperatives men…

Ooops! Forgot about “which”! • Zachman Framework is • Views are a widely honest serving men… I keep seven tied to English language used architectural Bugger! It doesn’t rhyme! – The elegance of the framework not so obvious for speakers of languages other than English (LOTE)

• For example some LOTEs have more interrogatives • How much?

mechanism

– TOGAF – IEEE 1471-2000

– French – Combien? – Thai – Tourai? – Hindi – Kitna?

• By the way, what happened to “which”? © Lonsdale Systems

28

UML diagrams are based on abstract views… This has several disadvantages… Idiots!

1. People think the diagrams are a methodology or process 2. People draw diagrams because they are “in the UML” and therefore “must be needed” 3. People assume that the abstract views define all possible UML diagrams

Views vs. UML Diagrams © Lonsdale Systems

29

UML Views …this taxonomy provides a logical organization for the various major kinds of diagrams. However, it does not preclude the mixing different kinds of diagram types… …the boundaries between the various kinds of diagram types are not strictly enforced… OMG UML 2.0 Infrastructure Specification © Lonsdale Systems

30

The Extreme Architecture Framework Activity

Information

Software

Data

Technology

Sector Enterprise Process Application Component

© Lonsdale Systems

31

The Extreme Architecture Framework Architectural Elements

Activity

Information

Software

Data

Technology

Sector Enterprise Process Application Component

Functional Requirements Non-Functional Requirements © Lonsdale Systems

32

Activity

Information

Software

Activities

Subject Areas

Functional Areas

Workflow

Information

Data

Technology

Sector Enterprise

Facts

Features

Process Networks

Application

Use Cases

Interface Requirements

Functional Requirements Non-Functional Requirements

Platforms Storage Requirements

Frameworks

Architecture

Component

User Interface Many thanks

to Peng Soong Schemas Code for this metaphor…

© Lonsdale Systems

33

The Extreme Architecture Framework Enterprise Elements

Activity

Information

Software

Data

Technology

Sector Activities Enterprise Workflow

Information Requirements

Functional Areas

Objects

• Accept reservations • Check in guest

Process

Application

Subject Areas

Use Cases

Functional room – Allocate Requirements Interface Storage – Record newspaper Requirements Requirements Non-Functional preference Requirements

– Record morning call time Architecture

Component

• Provide room service Schemas

User Interface

Code

– Record order – Deliver order – Collect dishes

• Provide laundry – Collect laundry – Wash laundry – Return laundry

• Check out guest © Lonsdale Systems

34