Upload
aamir97
View
1.933
Download
2
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
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
Bill forAccommodation
Handle CancellationProvideAccommodation
Handle Enquiry
Accommodation Decomposition Diagram for BPM-UML Example
PaymentReceived for
Accommodation
Invoice Raisedfor
Accommodation
CustomerRequests
Accommodation
Cancellationrequest
Received
CustomerAdvised of
Unavailability
Check Out GuestCheck In GuestConfirm ReservationMake Reservation
accommodationcharged to account
paymentreceived
cancellationrequested
accommodationunavailable
accommodationavailable
Data Model
ReservationPrimary Key
code [PK1]employeeID [PK2] [FK]ID [PK3] [FK]Property_Code [PK4] [FK]Unit_Number [PK5] [FK]Non-Key Attributes
statusdatedurationroomTypeShift_Num [FK]Sales_Clerk [FK]Agency_ID [FK]Guest_Number [FK]
RoomPrimary Key
number [PK1]employeeID [PK2] [FK]ID [PK3] [FK]Non-Key Attributes
statustype
CustomerPrimary Key
ID [PK1]Non-Key Attributes
nameaddresstelNofaxNocreditCard
Travel AgentPrimary Key
Agency_ID [PK1]Non-Key Attributes
Agency_NameAgentPhoneYTD_Commission
Overseas CustomerPrimary Key
ID [PK1] [FK]Non-Key Attributes
NationalityPassportNumber
UK CustomerPrimary Key
ID [PK1] [FK]Non-Key Attributes
Postcode
ReceptionistPrimary Key
employeeID [PK1]ID [PK2] [FK]
makes
books
makes
contacts
is_ais_a
Application Model
A
Billing"Accounts
Receivable""Customer
Maintenance"
A
ReservationBooking
"NewReservation"
D Customer
account history
maintenance details
customer details
reservation details
Customer Services
Accounts
Customer
P CustomerMaintenance
P AccountsReceivable
P NewReservation
D Customer
account history
maintenance detail
customer credit rating
reservation details
customer booking details
credit card action
authorisation code
reservation request
Models in the Enterprise Architecture
Enterprise Architecture
A
Payments
A
CRM
D CustomerDatabaseThe
Workers
The MiddleThe Middle
The Boss
OrderConfirmed
OrderReceived
ConfirmOrder
CheckDetails
PRODUCTORDER
CUSTOMER
Enterprise Architecture- principles + standards- Common Vocabulary
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 supportTo 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
XML MS
OfficeHTML XML Win HTML
OLE Automation CSV XML/XMI HTML
MS Office
XML
Reporting Browsing Interfaces Matrices
Customizable Repository Metamodel
Shared Repository
Analyze Business:•Processes•Organization•Functions•Technology Infrastructure•IDEF0/IDEF3•BPMN•Simulation
UMLDesign Applications:•Use Cases•Object Interactions •Classes•Components•State Machines•Java
Design Databases:•ERD Model •Physical Model •IDEF1X•DB Synchronize™
Analyze Legacy Systems:• Gane/Sarson• Ward/Mellor• Yourdon/DeMarco• SSADM
Design XML Schemas:• DTDs• BizTalk• Instance Docs• Test Data• UML Integration• Data Modeling Integration
XML DesignStructuredMethods
Data Modeling
Business Modeling
System Architect summary in a single slideSystem Architect summary in a single slide
Shared Definitions
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 DiagramA 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 alignment (business and IT) + a framework + benefit (to the organisation) + tool support
Your Enterprise Architecture has become an enterprise asset
Enterprise Architecture
A
Payments
A
CRM
D CustomerDatabase
TheWorkers
The MiddleThe Middle
The Boss
OrderConfirmed
OrderReceived
ConfirmOrder
CheckDetails
PRODUCTORDER
CUSTOMER
Enterprise Architecture- principles + standards- Common Vocabulary
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