enterprise architecture modeling with archimate &...
TRANSCRIPT
Adnaan Sikandar Capgemini Canada [email protected]
Enterprise Architecture ModelingWith ArchiMate & Sparx
AGENDA ArchiMate Overview
ArchiMate Concepts• Framework & Concept• Layers• Metamodels
ArchiMate Viewpoints• Information Structure Viewpoint• Business Process Viewpoint• Layered Viewpoint• Infrastructure Viewpoint• TOGAF ADM Viewpoints
ARCHIMATE What is it?
• ArchiMate is a modeling language for describing enterprise architectures
• Broader scope than UML. UML is for software engineering
• Supports EA frameworks like TOGAF & Zachman
• Can be used to create IAF views and artifacts
• ArchiMate viewpoints are more detailed than TOGAF’s architecture artifacts – TOGAF does not provide descriptions and examples
ARCHIMATE Which version should I use?
• Technical Specification 1.0 (Approved)• Technical Specification 2.0 (Under Review)
Is it a standard?• The Open Group’s ArchiMate Forum – Stewards of the ArchiMate
standard
What about the license?• Capgemini is an ArchiMate Forum member• ArchiMate Forum members have commercial license to use it for
consulting engagements
ArchiMate – Concepts
ARCHIMATE FRAMEWORK
Technology
Application
Business
Information Behavior Structure
ProcessesInformation
Data
Organisation
Products & Services
Applications
Technical Infrastructure
BusinessFunctions
ARCHIMATE CONCEPT
ArchiMate Structure - Services
Externalbusiness service
Internalbusiness service
Internalinfra. service
Externalinfra. service Technology
Application
Business
Customer
Externalapplication service
Internalapplication service
ARCHIMATE STRUCTURE - LAYERS Layers
• Business Layer - Offers products and services to external customers, which are realized in the organization by business processes performed by business actors
• Application Layer - Supports the business layer with application services which are realized by (software) applications.
• Technology Layer - offers infrastructure services (e.g., processing, storage, and communication services) needed to run applications, realized by computer and communication hardware and system software.
Generic Metamodel For Each Layer
Internal
External
Information Behavior Structure
Structureelement
Object
Service Interface
Behaviorelement
METAMODEL – BUSINESS LAYER
LANGUAGE NOTATIONS
BUSINESS LAYER - SPARX EXAMPLE
Actors
IT Help Desk
Exception Management Process
Create Event(Automatic)
Correlate & AnalyzeEvent (Automatic)
Triage & ResolveException Ticket
Close ExceptionTicket
SMI EventsExceptions
Tier 1 Help Desk Agent
Flows Flows Flows
Assigned To
Triggers
Assigned To
METAMODEL – APPLICATION LAYER
METAMODEL – TECHNOLOGY LAYER
ArchiMate – Viewpoints
Basic ArchiMate Viewpoints Introductory Viewpoint Organization Viewpoint Actor Co-operation Viewpoint Business Function Viewpoint Business Process Viewpoint Business Process Co-operation
Viewpoint Product Viewpoint Application Behavior Viewpoint Application Co-operation Viewpoint Application Structure Viewpoint Application Usage Viewpoint
Infrastructure Viewpoint Infrastructure Usage Viewpoint Implementation and Deployment
Viewpoint Information Structure Viewpoint Service Realization Viewpoint Layered Viewpoint Landscape Map Viewpoint
ACTOR CO-OPERATION VIEWPOINTLayered View Point
Stakeholders Enterprise, process, and domain architects
Concerns Relations of actors with their environment
Purpose Designing, deciding, informing
Abstraction Level Details
Business layer Business layer
Aspects Structure, behavior
ACTOR CO-OPERATION VIEWPOINT
Service Desk
Service Desk Manager
Tier 1 Service Desk
Tier 2 ApplicaitonAdministration
Tier 2 SystemAdministration
Tier 2 NetworkAdministration
Operations Optimization
Business Actor A
Business Actor B
Business Actor D
Business Actor C
«Tickets»
«Tickets»
«Tickets»
«Tickets»
«Tickets»«Tickets»«Tickets»
«Tickets»
LAYERED VIEWPOINTLayered View Point
Stakeholders Enterprise, process, application, infrastructure, and domain architects
Concerns Consistency, reduction of complexity, impact of change, flexibility
Purpose Designing, deciding, informing
Abstraction Level Overview
Layer Business layer, application layer, technology layer
Aspects Information, behavior, structure
LAYERED VIEWPOINT – SPARX EXAMPLE
Application Services
Application Components
Actors
IT Help Desk
Exception Management Process
Create Event(Automatic)
Correlate & AnalyzeEvent (Automatic)
Event AnalysisService
Triage & ResolveException Ticket
Close ExceptionTicket
SMI EventsExceptions
EventCorrelation &
Analysis
Trouble TicketManagement
Ticket ServiceEvent LoggingService
KnowledgeManagement
Tier 1 Help Desk Agent
Work InstructionsService
Event CorrelationService
Applications
BMC Event Manager BMC Remedy ITSM
BUSINESS PROCESS VIEW POINTBusiness Process View Point
Stakeholders Process and domain architects, operational managers
Concerns Structure of business processes, consistency and completeness, responsibilities
Purpose Designing
Abstraction Level Detail
Layer Business layer
Aspects Behavior
BUSINESS PROCESS VIEW POINT – SPARX EXAMPLEActors
IT Help Desk
Process
Create Event(Automatic)
Correlate & AnalyzeEvent (Automatic)
Resolve ExceptionTicket
Close ExceptionTicket
Event
IT Help Desk Tier 1 Agent
Event Exception Ticket
Asset
Device
Network Topology
Rules
Event Thresholds
Network Device
Read
Create / Update
Create / Read
CreateRead
Read
Read
Update Update
Read
Read
INFRASTRUCTURE VIEW POINTBusiness Process View Point
Stakeholders Infrastructure architects, Operational Managers
Concerns Stability, security, dependencies, infrastructure costs
Purpose Designing
Abstraction Level Detail
Layer Technology
Aspects Behavior, Structure
INFRASTRUCTURE VIEW POINT – SPARX EXAMPLE
Mobile Field Force Database Security Context
Secure Zone
Windows
Corporate LAN
Office Application Internal Firewall
Database
Windows
InternetInformation
Server
Private APN
Mobile Tablets
Mobile Field Force Application Security Context
HTTPSHTTPS
HTTPS
HTTPSHTTPS
SSL
APPLICATION LANDSCAPE VIEW POINTBaseline Application Model
Target Application Model
Level 1 Process
Existing SystemA
Existing SystemB
Existing SystemC
Existing SystemD
Existing SystemF
Existing SystemE
Level 1 Process
Existing SystemA
Existing SystemB
Existing SystemC
Existing SystemD
Existing SystemF
Existing SystemE
New System Y New System ZNew System X
ARCHIMATE RESOURCES ArchiMate 1.0 Technical Specification
ArchiMate Good Practices
Sparx Enterprise Architect
ArchiMate Presentations