Tool support for Enterprise
Architecture in System Architect
Architecture Practitioners Conference, Brussels
David Harrison
Senior Consultant, Popkin Software
22 April 2004
Topics
•
•
•
•
The target
Enterprise architecture and frameworks
Why tool support
Which frameworks


•
•
•
•
Zachman
TOGAF
TOGAF 7 and TOGAF 8
System Architect support for TOGAF 8
SA Release 10 - The Explorer Diagram
What next
The target
Enterprise Architecture
+ an architecture framework
+ tool support
alignment of business and IT
+ benefit (to the organisation)
Your Enterprise Architecture becomes an enterprise asset
Enterprise Architecture
“… the set of descriptive representations (models) that are relevant for describing an
Enterprise such that it can be produced to management’s requirements (quality) over
the period of its useful life (changed).” [q. J Zachman]
•
•
•
•
•
•
Set of models and documents
Graphical and textual artefacts
• Diagrams and symbols
• Definitions and descriptions
Describes multiple architecture domains
Describes many stakeholder views
Defines relationships between them
An Enterprise Architecture supports an operating business in achieving its
goals
Models in the Enterprise Architecture
• Graphical representation of the “real world” (the “picture on the lid”)
• Multiple architecture domains





Data
Business process
Technical
Application
Organisation
• Many stakeholder views
•
•
•
•
Management
Designer
Builder
User communities
• Many levels of model

•
•
•
•
Conceptual  logical  physical
Many artefacts and relationships
Supported by descriptive text
Governed by architecture principles and standards
Business-centred
Architecture Standards and Principles
• Re-use of architecture artefacts

•
•
•
•
•
•
across architecture domains and frameworks
Define / change once  use many
Full integration of graphical and textual artefacts
Support corporate standards
Support corporate naming conventions + business rules
Common vocabulary for all stakeholders
Consistency of:




meaning  core taxonomy
definition content
diagram styles
presentation
Business Process Model
Accommodation Decomposition Diagram for BPM-UML Example
Accommodation
Handle Enquiry
cancellation
requested
Customer
Requests
Accommodation
Make Reservation
accommodation
available
Confirm Reservation
Prov ide
Accommodation
Cancellation
request
Received
Check In Guest
Check Out Guest
payment
received
accommodation
charged to account
accommodation
unavailable
Customer
Advised of
Unavailability
Handle Cancellation
Payment
Received for
Accommodation
Invoice Raised
for
Accommodation
Bill f or
Accommodation
Data Model
Customer
Primary Key
ID [PK1]
Non-Key Attributes
name
address
telNo
f axN o
creditCard
is_a
Ov erseas Customer
Primary Key
ID [PK1] [F K]
Non-Key Attributes
Nationality
PassportN umber
Receptionist
Primary Key
employ eeID [PK1]
ID [PK2] [F K]
contacts
is_a
makes
UK Customer
Primary Key
ID [PK1] [F K]
Non-Key Attributes
Postcode
Trav el Agent
Primary Key
Agency _ID [PK1]
Non-Key Attributes
Agency _N ame
Agent
Phone
Y TD _Commission
makes
Reserv ation
Primary Key
code [PK1]
employ eeID [PK2] [FK]
ID [PK3] [F K]
Property _Code [PK4] [F K]
Unit_N umber [PK5] [F K]
Non-Key Attributes
status
date
duration
roomTy pe
Shif t_Num [FK]
Sales_Clerk [FK]
Agency _ID [F K]
Guest_Number [FK]
books
Room
Primary Key
number [PK1]
employ eeID [PK2] [FK]
ID [PK3] [F K]
Non-Key Attributes
status
ty pe
Application Model
A
Reserv ation
Booking
"New
Reserv ation"
reserv ation details
customer details
D
Customer
Customer
A
reserv ation request
P New
Reserv ation
reserv ation details
Accounts
authorisation code
P Accounts
Receiv able
customer credit rating
D
Customer
credit card action
account history
Customer Serv ices
P Customer
Maintenance
customer booking details
maintenance detail
Billing
"Accounts
Receiv able"
"Customer
Maintenance"
maintenance details
account history
Models in the Enterprise Architecture
Enterprise Architecture
CUSTOMER
PRODUCT
ORDER
Order
Receiv ed
Check
Details
Conf irm
Order
Enterprise Archi tecture
- principl es + standards
- Common Vocabulary
Order
Conf irmed
The Boss
The Middle
A
A
CRM
Pay ments
The Middle
D
The
Work ers
Customer
Database
Organising the enterprise architecture
models
• The Architecture alone is not enough:
• Need to understand how it all fits together
• Need a common vocabulary


communication
all stakeholders
• Need to manage multiple models, methods and notations
• Need to organise and classify the information
• Need an architecture framework
• Need methods for populating and maintaining the framework
Architecture frameworks
• Architecture framework provides:




Integration
Organisation
Classification
Accessibility
• Window on the underlying repository
• Gives the view you want to see, appropriate to your purpose
• “A place for everything and everything in its place”


Knowing where to put things
Knowing where to find them
• “Static” and “dynamic” frameworks


Content-focused frameworks (eg: Zachman)
Process-focused frameworks (eg: TOGAF)
Static and dynamic frameworks
• Static framework

Provides static picture of current content
• Dynamic framework




Defines process steps
Provides picture of current content (deliverables from steps)
Enables navigation the process
The process uses and populates the framework
• Architecture artefacts used and visible in many
frameworks
• Zachman

an implicit process
• TOGAF

an explicit process
Zachman Framework
Zachman Framework – key features
• “Reference model” for architecture frameworks
•
•
•
•
•
•
•
Supports all architecture domains (column)
Supports multiple perspectives (row)
Supports multiple stakeholder views
Not prescriptive about multiple modelling methods
Enables use of existing (legacy) models
Enables re-use of model artefacts
Enables a common vocabulary for IT and business
people
• “The system is the enterprise” [q. J Zachman]
TOGAF Enterprise
The Open Group Architecture Framework





an architecture implementation method
TOGAF populates the Zachman (or other) framework
Defines process and deliverables
Navigates the process
Delivers the architecture
Why tool support
To bring the architecture alive ….. (useful, usable and used)
• Stores and integrates models and textual material in one place
• Enables navigation and sharing of information (but define and store
it only once)
• Improved quality, currency and completeness of information
• Enables analysis across domains and business areas
• Enables implementation of a corporate metamodel


defines content and style
no gap between visual representation and textual definition, hence …
• Enables improved communication between all stakeholders


Common vocabulary
Business, IT and other audiences
• In short …. delivers the benefits …
architecture + framework + tool support = an enterprise asset
System Architect summary in a single slide
Shared
Definitions
Business
Modeling
UML
Analyze Business:
•Processes
•Organization
•Functions
•Technology
Infrastructure
•IDEF0/IDEF3
•BPMN
•Simulation
Design
Applications:
•Use Cases
•Object Interactions
•Classes
•Components
•State Machines
•Java
Data
Modeling
Design
Databases:
•ERD Model
•Physical Model
•IDEF1X
•DB Synchronize™
Structured
Methods
XML Design
Design XML
Schemas:
Analyze Legacy
Systems:
• DTDs
• BizTalk
• Instance Docs
• Test Data
• UML Integration
• Data Modeling
Integration
• Gane/Sarson
• Ward/Mellor
• Yourdon/DeMarco
• SSADM
Shared Repository
Customizable Repository Metamodel
Reporting
XML
MS
Office
HTML
Browsing
XML
Win
Interfaces
OLE
HTML Automation
CSV
Matrices
XML/XMI HTML
MS
Office
XML
SA Framework and Method support overview
• Supports multiple frameworks and methods
• Supports re-use of artefacts
• Supports multiple frameworks, including:


Zachman
TOGAF
• Supports the standard methods and languages, including:

UML
BPMN, BPEL
ER
IDEF

Structured analysis and design



• Customisable




build-your-own framework
select appropriate methods
customise the metamodel
customise for display and publication
Zachman Framework in SA
TOGAF Enterprise Framework in SA
TOGAF Tool support requirements
• Main requirements of a supporting tool:









Supports the stages of the ADM process
Enables navigation through the ADM
Supports the ADM core deliverables
Supports the Foundation architecture and Enterprise
Continuum
Enables re-use of architecture components
Enables full integration of architecture components
Enables production of principal TOGAF documents and
models
Supports commonly-used modelling standards and methods
Has a common repository supporting multiple concurrent
users
TOGAF in System Architect
• TOGAF framework graphic
• Support for the TOGAF ADM


The phases of TOGAF 7 and TOGAF 8
Navigation through the phases
• Support for the TOGAF products and techniques

Definition templates for core deliverables, in particular:







Business Architecture
Data Architecture
Application Architecture
Technology Architecture
Business Scenarios
Requirements management
Gap analysis
• Support for the Foundation Architecture

The TRM graphic and taxonomy, including hyperlinks to TRM, SIB
• Support for publication of principal TOGAF document and views
• Enables re-use and integration of architecture artefacts
• Central repository + support for multiple concurrent users
TOGAF Preliminary Phase mini-browser:
definitions, matrices
TOGAF Phase A mini-browser: definitions,
diagrams, matrices
SA Release 10 – the Explorer Diagram
•
•
•
•
•
•
•
•
•
A significant enhancement to the user interface
Visualisation of models
Spider type diagram
Graphically explore encyclopaedia content
Displays model objects and relationships
Display / hide relationships
Show collections of objects and interdependencies with
objects in other collections
Based on report specifications using standard SA
reporting facility
User-defined reports to customise content of displays
Displays may be based on values in object properties
Explorer diagram: objects and collections
Explorer diagram: applications-technology
Explorer diagram: applications-processes
Explorer diagram: processes-roles
Explorer diagram: processes-data entities
Explorer diagram: processes-locations
Explorer diagram: one process with
relationships
Explorer diagram: one application with
relationships
Summary – the framework and the tool
• Support for your chosen framework(s) and method(s)
•
•
•
•
•
A way of organising information
A means to share information
Your set of reference material
Knowing where to put things …
Knowing where to find them …


Other people knowing where to find them
Now and next year …
• A common vocabulary
• In a single repository
• Brings your architecture alive
• Delivers business benefit
Conclusion – delivering the Enterprise Asset
Enterprise Architecture
CUSTOMER
PRODUCT
ORDER
Order
Receiv ed
Enterprise Archi tecture
- principl es + standards
- Common Vocabulary
Check
Details
A
A
CRM
Pay ments
The Boss
Conf irm
Order
Order
Conf irmed
The Middle
The Middle
D
The
Workers
enterprise architecture
+ a framework
+ tool support

Customer
Database
alignment (business and IT)
+ benefit (to the organisation)
Your Enterprise Architecture has become an enterprise asset
SA and TOGAF – next steps
• TOGAF 8 support in SA release 10 




Due June 2004
Includes new Explorer and Enterprise Direction diagrams
Includes TOGAF 8 sample encyclopaedia
Other enhancements in response to client requirements
• Develop / contribute to a TOGAF meta-model




Architecture artefacts
Principles and standards
TOGAF resources
ERD / UML
• Develop / contribute a TOGAF process model



ADM phases
Related processes
BPMN
• Commitment to support future TOGAF versions
• Policy of continuous improvement
• Promotion of TOGAF with Popkin clients
Descargar

No Slide Title