Danairat T., 2011, [email protected] Enterprise Architecture 1
Building Enterprise ArchitectureThe 2 Days EA Intensive Course
Danairat T.Oracle Enterprise Architect, ASEAN
Certified Java Programmer, TOGAF – [email protected], +66-81-559-1446
Danairat T., 2011, [email protected] Enterprise Architecture 2
Agenda Day1
• Introduction• Today Architecture Challenges• The Need of Enterprise Architecture• What is Enterprise Architecture?• Enterprise Architecture and Architecture Development Method• Enterprise Reference Architecture Framework• Preparing your Current Enterprise Architecture• Group Brainstorm Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 3
Agenda Day2
• Building Enterprise Architecture• Enterprise Architecture Maturity Model• Understanding Today Technology Platforms and Key Considerations
• User Centric Platform• Process Centric Platform• Data Centric Platform• Decision Centric Platform• Application Server, Database Server and Hardware Platform
• TOGAF and ADM• Enterprise Architecture and Cloud Computing Roadmap• Enterprise Architecture and IT Governance• Build your Target Enterprise Architecture• Group Brainstorm Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 4
Introduction
Danairat T., 2011, [email protected] Enterprise Architecture 5
General IT Organization
Chief Executive Officer (CEO)
Chief FinancialOfficer (CFO)
BusinessExecutive
Chief InformationOfficer (CIO)
Head ofOperations
Head of IT Administration
Head ofDevelopment
BusinessProcess Owner
Chief ArchitectCompliance, Audit, Risk and Security
Project Management Office (PMO)
Danairat T., 2011, [email protected] Enterprise Architecture 7
Process, Application, Data, Technology
Business Objectives
Goals
Danairat T., 2011, [email protected] Enterprise Architecture 8
Kindly always understand the driver from political -> business
business -> technical
Danairat T., 2011, [email protected] Enterprise Architecture 10
CMMi, ITIL, COSO, etc.
BSC, ITG, etc.
Investment& Value
How to Explore the Enterprise
EA
Danairat T., 2011, [email protected] Enterprise Architecture 11
Today Architecture Challenges
Danairat T., 2011, [email protected] Enterprise Architecture 12
Today Architecture Challenges
• Technology Trends from Host Based to Smart Devices• Eco-System requirements, the expansion of requirements• Shorten product life cycle creates more Design to Change
requirement• Trends of Technology in Business
• Creating ___________• Creating ___________• Creating ___________• Creating ___________
Danairat T., 2011, [email protected] Enterprise Architecture 14
The Need of Enterprise Architecture
Danairat T., 2011, [email protected] Enterprise Architecture 15
There are many of IT related agendas
• Alignment with Business Goals• Change and Configuration Management• IT Governance, Risk, Compliance• Enterprise Portfolio Management
Danairat T., 2011, [email protected] Enterprise Architecture 16
There are so many Architects
• Software Architect• Data Architect• Application Architect• Business Architect• Technology Architect• Solution Architect
Danairat T., 2011, [email protected] Enterprise Architecture 17
What is Enterprise Architecture?
Danairat T., 2011, [email protected] Enterprise Architecture 18
Enterprise Architecture
Enterprise Architecture is a structure design to ensure alignment between the business and IT strategies plus operating model, guiding principles.
Danairat T., 2011, [email protected] Enterprise Architecture 20
There are many of related standards/guidelines for EA
CMMi
SixSigma ISO
9000
Score-cards
Abstraction
IT R
elev
ance
Hol
istic
Spec
ific
Low High
CobiTISO 38500
TOGAF
ITILISO 20000
ISO 2700127002
(17799)
SOXCOSOBasel II
Danairat T., 2011, [email protected] Enterprise Architecture 21
Enterprise Architecture and Architecture Development Method
Danairat T., 2011, [email protected] Enterprise Architecture 22
Enterprise Architecture and Architecture Development Method
Application and Solution
Architecture
BusinessProcess
Architecture
Data and Information Architecture
Technology and Infrastructure Architecture
Danairat T., 2011, [email protected] Enterprise Architecture 23
Enterprise Reference Architecture Framework
Danairat T., 2011, [email protected] Enterprise Architecture 24
The Enterprise Reference Architecture
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
System Monitoring
andManagement
Security/Auditing
and Identity
Management
Enterprise Infrastructure
Enterprise Information Management
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 25
The Enterprise Reference Architecture
Customer Data Product Data Payment Data Accounting Org. HierarchyEnterprise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer Platform
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 26
The Enterprise Reference Architecturewith Architecture Domains
Customer Data Product Data Payment Data Accounting Org. HierarchyEnterprise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer Platform
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Business
ArchitectureApplicationArchitecture
TechnologyArchitecture
Data
Arch.
Danairat T., 2011, [email protected] Enterprise Architecture 27
Group Workshop - The Current Enterprise Architecture
Enterprise Reference Architecture
Business Insight
and Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Business Processing Systems
System Monitoring
andManagement
Security/Auditing
and Identity
Management
Enterprise Infrastructure
Master Data
Access Channels
Write down your existing enterprise architecturefoot print
Team Name: xxx1. Name, Company, E-mail2. Name, Company, E-mail
3. Name, Company, E-mail4. Name, Company, E-mail
Danairat T., 2011, [email protected] Enterprise Architecture 28
Summary
• Today Architecture Challenges• The Need of Enterprise Architecture• What is Enterprise Architecture?• Architecture Development Method• Enterprise Reference Architecture Framework• Group Brainstorm Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 30
Agenda Day2
• Building Enterprise Architecture• Enterprise Architecture Maturity Model• Understanding Today Technology Platforms and Key Considerations
• User Centric Platform• Process Centric Platform• Data Centric Platform• Decision Centric Platform• Application Server, Database Server and Hardware Platform
• TOGAF and ADM• Enterprise Architecture and Cloud Computing Roadmap• Enterprise Architecture and IT Governance• Group Brainstorm Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 31
Building Enterprise Architecture
Danairat T., 2011, [email protected] Enterprise Architecture 32
Enterprise Continuum
www.opengroup.org
Danairat T., 2011, [email protected] Enterprise Architecture 33
Architecture and Solution Continuum
www.opengroup.org
Danairat T., 2011, [email protected] Enterprise Architecture 34
Building Enterprise ArchitectureThe Guideline
1. Select program or project to start (low risk) supported by C-Level
2. Establish Virtual Team maintain standard architecture development method
3. Acquire and Maintain Knowledge of Enterprise Architecture Development with change and feed back communication system
4. Create architecture reference based on current deployments
5. Develop new architecture layered model from current deployment with business alignment and operation life cycle consideration
6. Replicate to new program or project development
Danairat T., 2011, [email protected] Enterprise Architecture 35
The Enterprise Reference Architecturewith Architecture Domains
Customer Data Product Data Payment Data Accounting Org. HierarchyEnterprise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer Platform
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Business
ArchitectureApplicationArchitecture
TechnologyArchitecture
Data
Arch.
Danairat T., 2011, [email protected] Enterprise Architecture 36
Creating Target Enterprise ArchitectureVision and Business Architecture
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer Platform
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Business
ArchitectureApplicationArchitecture
TechnologyArchitecture
Data
Arch.
• Provide target business goals for the focus business areas or for the difference pillars• Revenue• Cost• Risk• Etc.
• Provide the target business objectivesfor the focus business areas with prioritization
• Provide the target business organization
• Provide detailed explanations if any
Remarks: To create business goals, you may consult CobiT framework
Danairat T., 2011, [email protected] Enterprise Architecture 37
Creating Target Enterprise ArchitectureApplication Architecture
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer Platform
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Business
ArchitectureApplicationArchitecture
TechnologyArchitecture
Data
Arch.
• Provide a target business serviceand its processesfor the focus business areas
• Provide a target process integrationsfor the focus business areas
• Provide related business roles for thebusiness process
• Define required resources forbusiness service development
• Define business service operation cycle
• Provide detailed explanations if any
Remarks: To create business process, you may consult the BPMN
Danairat T., 2011, [email protected] Enterprise Architecture 38
BPM - IT and Business Alignment
38
Business Artifact and Model IT Artifact and Model
Shared Metadata Model Repository
Generate/Merge
Oracle Corporation
Danairat T., 2011, [email protected] Enterprise Architecture 39
Application ArchitectureKey Common Requirements
Danairat T., 2011, [email protected] Enterprise Architecture 40
Application ArchitectureKey Common Requirements
Operation Management/ Automation
User Features, FunctionsEase of Use and Response Time
High AvailabilityDistributed Solution
GRID/Cloud
Access Control, SecurityGovernance, Standard and Compliance
Danairat T., 2011, [email protected] Enterprise Architecture 42
Creating Target Enterprise ArchitectureData Architecture
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer Platform
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Business
ArchitectureApplicationArchitecture
TechnologyArchitecture
Data
Arch.
• Provide reference data (master)• Provide common data relationship• Provide master data creation and its
life cycle (including cleansing process)
• Provide both logical and physicaldata architecture design
• Provide detailed explanations if any
Danairat T., 2011, [email protected] Enterprise Architecture 43
Enterprise Data and Integration
App1Data
App2 Data
App3 Data
Master Data
Data Management Process
ODS
DataWarehouse
Data Governance, Data Architecture Management, Data Modeling, Data Quality, DW/BI, Metadata Management, Document/Content Management
ApplicationSpecific
Data
Enterprise Operational
Data
EnterpriseData Warehouse,Data Marts and BI
ETL/ELT
ETL/ELT
SOA
TransactionalIntegration
Data
WS
WS
WS
Danairat T., 2011, [email protected] Enterprise Architecture 44
Transactional Integration Data
Guidelines:-1. Define Transactional Integration Data2. Identify Source and Target Systems3. Adoption of WS and WS Attachment4. Put All Data Models in XSD format5. Acquire Metadata Tool for keeping XSD6. Leverage XSLT for data transformation7. Leverage WS Security for Proxy Interface8. Use of Tool to perform online Data Field
Mapping between Enterprise Name and Application Specific Name
9. Acquire Real-time Data Integration Monitoring Tool
App1 Data
App2 Data
App3 Data
Master Data
Data Management Process
ODS
DataWarehouse
Data Governance, Data Architecture Management, Data Modeling, Data Quality, DW/BI, Metadata Management, Document/Content Management
ApplicationSpecific
Data
Enterprise Operational
Data
EnterpriseData Warehouseand Data Marts
ETL/ELT
ETL/ELT
SOA
TransactionalIntegration
Data
WS
WS
WS
Danairat T., 2011, [email protected] Enterprise Architecture 45
Application Specific Data
Guidelines:-1. Acquire Open Standard Industry Data Model
where possible2. Standardize Data Definition throughout
Applications3. Do Not Try to Create New Data Fields before
Checking Application Data Template4. Adoption of WS and WS Attachment for
Integration part 5. Minimize Point to Point Batch Integration where
possible to reduce Eco-System Overhead6. Always define Data Cleansing Roles in
Business User rather than doing in IT Department
7. Maximize Centralized Master Data Usage8. Also Classify an Unstructured Data in both
Master Data and Operational Data types
App1 Data
App2 Data
App3 Data
Master Data
Data Management Process
ODS
DataWarehouse
Data Governance, Data Architecture Management, Data Modeling, Data Quality, DW/BI, Metadata Management, Document/Content Management
ApplicationSpecific
Data
Enterprise Operational
Data
EnterpriseData Warehouseand Data Marts
ETL/ELT
ETL/ELT
SOA
TransactionalIntegration
Data
WS
WS
WS
Danairat T., 2011, [email protected] Enterprise Architecture 46
Enterprise Operational Data Store
Guidelines:-1. Focus Data only for Business Operation Level2. Understand Data Fields Requirement from
Business Units3. Understand ODS Usage Pattern
• Exchange Data between Applications • For Enterprise Operational Reporting
4. Leverage 3NF for ODS Database5. You may use DW Staging as ODS6. Standardize Data Key (eg. Customer ID) for All
Application where possible7. Define Data Create/Update Sequence from
authorized Application Systems8. Define Data Remove Process9. Maximize Master Data Usage10. Leverage System Monitoring
App1 Data
App2 Data
App3 Data
Master Data
Data Management Process
ODS
DataWarehouse
Data Governance, Data Architecture Management, Data Modeling, Data Quality, DW/BI, Metadata Management, Document/Content Management
ApplicationSpecific
Data
Enterprise Operational
Data
EnterpriseData Warehouseand Data Marts
ETL/ELT
ETL/ELT
SOA
TransactionalIntegration
Data
WS
WS
WS
Danairat T., 2011, [email protected] Enterprise Architecture 47
Enterprise Data Warehouse, Data Martsand BI
Guidelines:-1. Focus Data only for Business Strategic Level2. BI is NOT only in DW, DM. BI is Everywhere.3. Acquire Efficient Data Integration Tool (ETL/ELT)
for Data Loading, Transformation4. Create a Reliable DW for some ac-hoc query
might impact to overall performance5. Data Marts and OLAP for Business Requirements6. Always pro-active advertise the new set of subject
available to Business Users7. Educate End-User for the BI/Dashboard Tool8. Distribute Summary Report to End-User to
Minimize Large Data Inquiry Cost 9. Partitioning Data where possible10. 3NF schema design for a data warehouse11. Prioritize Parallel Execution12. DW Optimizer and Stats management
App1 Data
App2 Data
App3 Data
Master Data
Data Management Process
ODS
DataWarehouse
Data Governance, Data Architecture Management, Data Modeling, Data Quality, DW/BI, Metadata Management, Document/Content Management
ApplicationSpecific
Data
Enterprise Operational
Data
EnterpriseData Warehouseand Data Marts
ETL/ELT
ETL/ELT
SOA
TransactionalIntegration
Data
WS
WS
WS
Danairat T., 2011, [email protected] Enterprise Architecture 48
Master Data
Guideline:-1. Define Master Data Owner and Change Control2. Adopt Data Governance for MDM process3. Master Data Classification4. Define Source and Target of Master Data5. Acquire Data Profiling and Quality Tool for Data
Cleansing6. Define Master and Replica Data if any
App1 Data
App2 Data
App3 Data
Master Data
Data Management Process
ODS
DataWarehouse
Data Governance, Data Architecture Management, Data Modeling, Data Quality, DW/BI, Metadata Management, Document/Content Management
ApplicationSpecific
Data
Enterprise Operational
Data
EnterpriseData Warehouseand Data Marts
ETL/ELT
ETL/ELT
SOA
TransactionalIntegration
Data
WS
WS
WS
Danairat T., 2011, [email protected] Enterprise Architecture 49
Creating Target Enterprise ArchitectureTechnology Architecture
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer Platform
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Business
ArchitectureApplicationArchitecture
TechnologyArchitecture
Data
Arch.
• Considering an open computing platform
• Creating target ABB and SBB• Creating a common component
integration• Provide detailed explanations if any
ABB is architecture building block which is not tight to vendor productSBB is solution building block which is tight to vendor product
Danairat T., 2011, [email protected] Enterprise Architecture 50
Understanding Today Technology Platforms and Key Considerations
Danairat T., 2011, [email protected] Enterprise Architecture 51
Technology Standard and Key ConsiderationUser Interface and User Collaboration Layer
• Open User Interface Development Framework; JSF, etc.
• Event Driven UI; JSF, .NET, etc.• XML UI with Data Binding; JSF, ADF,
Taglibs, etc.(enable you to render in graph, table, map)
• Calendar and Holiday Aware System; .ics, etc.
• Metadata Management• Search Capability; Thai• Present Technology over HTTP
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer PlatformDecision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 52
Technology Standard and Key ConsiderationProcess Integration Layer
• BPMN 2.0 aware system• Business Process Execution Language• Standard Workflow Patterns
(FYI., Sequential, Vote, Delegation, Reassignment, etc.)
• XML Workflow Application• Process Simulation• WSDL• SOAP, REST (Representational State Transfer)
• UDDI (Universal Description Discovery and Integration)
• Side-By-Side Versioning in Runtime
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer PlatformDecision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 53
Technology Standard and Key ConsiderationData Integration Layer
• Reliable Data Transfer (persistence)• Queuing System• Transfer Priority and Security• XML Declaration• Routing Simulation• Monitoring System and Exception
Capturing• Side-By-Side Versioning in Runtime
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer PlatformDecision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 54
Technology Standard and Key ConsiderationDecision Layer
• Inference Rules Engine; User Invocation
• Event Condition Action; System Monitoring
• Rules describe in XML, POJOs, flat files
• Enterprise Metadata Repository System
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer PlatformDecision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 55
Technology Standard and Key ConsiderationDatabase Server and Application Server
Database • ANSI (American National Standards Institute) SQL• DB Programming support• DB and System Diagnostic and Tuning Tool• Segregation of Duty Support• Active-Active Clustering
Application Server• Open Development Framework• Monitoring Matric; eg. JMX, Managed Bean• In-Memory Session Clustering• Deployment Descriptor• Declarative Transaction• Declarative Security Access Control
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer PlatformDecision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 56
Technology Standard and Key ConsiderationMonitoring and Management
• Simplistic as possible• Segregation of Monitoring and
Management• JMX; Java Management Extension• SNMP support• Text, Graphical with actionable support• Information Correlation support
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer PlatformDecision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 57
Technology Standard and Key ConsiderationSecurity Auditing and Identity Management
• Access Control and Authorization Server• Encryption Mechanism• Key Management Support • Non-Repudiation Support• Enterprise Roles Management• User Roles an Accounts Provisioning• SAML for IdM Federation
Customer Data Product Data Payment Data Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer PlatformDecision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 58
Enterprise Architecture Maturity Model
Danairat T., 2011, [email protected] Enterprise Architecture 59
Enterprise Architecture Maturity Model
Level 1Awareness/Ad-Hoc
EA Awareness SessionSelected program/projectfor EA initializationPerform ADM for selected program/project
Level 2Repeat
Replicate the EA exercise to newbusiness area
Level 3Define
EA process to be defined.ADM activities alignment
Level 4Manage
Roll out EA activitiesto all business areas
Level 5Optimized
Create enterprisebest practices forEA activitiesFully IT and Businessalignment
Maturity Level
Danairat T., 2011, [email protected] Enterprise Architecture 60
Level 1 Results
• Initial program/project • Virtual Team for EA activities• EA Introduction and Awareness• Explain the business goals for selected
program/project• Organization Specific Architectures• Initial Architecture Development Method• Monitoring, Management and Security Policy
Danairat T., 2011, [email protected] Enterprise Architecture 61
Level 2 Results
• New identified business area• Explain the business goals for selected
program/project • Replicate Architecture Development Method
practice• Organization Specific Architectures – reuse
where possible• Solution Building Block – reuse where possible• Data Model and Application Scenarios
including external integration (BPMN) – reuse where possible
• Monitoring, Management and Security Policy Alignment – reuse where possible
Danairat T., 2011, [email protected] Enterprise Architecture 62
Level 3 Results
• Architecture Development Method as Standard Practice for IT Systems
• Provide enterprise standard technology for organization and minimize variety of platform
• Data Model and Application Scenariosincluding external integration (BPMN) – reuse where possible
• Apply IT Governance Guideline for “Create Agility”
Danairat T., 2011, [email protected] Enterprise Architecture 63
Level 4 Results
• Architecture Development Method fully communicate and document
• Provide enterprise standard technology for organization and minimize variety of platform
• Apply IT Governance Guideline for “Create Agility”• Apply to all business areas
Danairat T., 2011, [email protected] Enterprise Architecture 64
Level 5 Results
• Architecture Development Method fully communicate and document
• Provide enterprise standard technology for organization and minimize variety of platform
• Apply IT Governance Guideline for “Create Agility”• Organization Specific Solution (best practices)• Apply to all business areas and align IT Plan and
Business Plan
Danairat T., 2011, [email protected] Enterprise Architecture 65
TOGAF Architecture Development Method
Danairat T., 2011, [email protected] Enterprise Architecture 66
TOGAF Architecture Development Method
The ADM method consists of eight main phases. As preliminary work, the enterprise architecture framework and architecture principles are fixed for the effort. In the following, a short description of the phases.A. Architecture vision is the analysis phase of EA project. The project is organized; the scope and domain requirements and constraints are stated. Business scenarios can be used for this.B. In the Business architecture phase, the current baseline architecture is stated, target architecture is designed and a gap analysis between the two takes place.C. Information systems architecture consists of the parts Data and Applications. For Data architecture, the types and sources of data needed in the enterprise are defined and a data model is created. A gap analysis is conducted and data model is compared with the business architecture. As to the applications, the applications needed to meet the specified business requirements and data model are turned into an applications architecture and are checked back with the business architecture.D. For Technology architecture, the previous phases deliver inputs. In this phase, a baseline architecture is stated, and the target technology architecture is designed.E. Opportunities and solutions is the evaluation phase, where the solutions are selected.F. Migration planning is the point for checking dependencies in the environment and preparing for implementation of the target architecture.G. Implementation and Governance is about the administration of implementation and deployment phase of the development project.H. Architecture change management is the maintenance phase. A new baseline is created and changes in business environment are monitored as well as new technology opportunities.
www.opengroup.org
Danairat T., 2011, [email protected] Enterprise Architecture 68
Enterprise Architecture and Cloud Computing Roadmap
Danairat T., 2011, [email protected] Enterprise Architecture 69
NIST Definition of Cloud Computing
Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.
This cloud model promotes availability and is composed of:
Source: NIST Definition of Cloud Computing v15
3 Service Models• SaaS• PaaS• IaaS
4 Deployment Models• Public Cloud• Private Cloud• Community Cloud• Hybrid Cloud
5 Essential Characteristics• On-demand self-service• Resource pooling• Rapid elasticity• Measured service• Broad network access
Danairat T., 2011, [email protected] Enterprise Architecture 70
Private Cloud Evolution
Public Cloud Evolution PaaS
SaaSIaaS
Public Clouds
Hybrid• Federation with
public clouds• Interoperability• Cloud bursting
App1 App2 App3
Private IaaS
Private PaaS
Virtual Private Cloud
Hybrid
PaaS
SaaS
IaaS
Private Cloud• Self-service• Policy-based
resource mgmt• Chargeback• Capacity planning
App2 App3
Private IaaS
Private PaaS
App1
Silo’d Grid• Physical• Dedicated• Static• Heterogeneous
• Virtual• Shared services• Dynamic• Standardized
appliances
App1 App2 App3
App1 App2 App3
Private IaaS
Private PaaS
Cloud Roadmap
Oracle Corporation
Danairat T., 2011, [email protected] Enterprise Architecture 71
Cloud Management Capabilities
ConfigurationandCompliance
ApplicationPerformanceManagement
LifecycleManagement
ApplicationQuality
Management
Foundation Capabilities for Managing Datacenters
Cloud Management CapabilitiesSelf-ServiceProvisioning
Policy-Driven Resource Mgmt
Metering andChargeback
CapacityPlanning
AssemblyPackaging
Oracle Corporation
Danairat T., 2011, [email protected] Enterprise Architecture 72
Enterprise Architecture and IT Governance
Danairat T., 2011, [email protected] Enterprise Architecture 73
General Subjects for IT Governance
• Platform Consolidation• Business Continuity Planning• Disaster Recovery• System Test• Configuration Management• Performance Measurement• Data Security and Access Management• Identity Management• Regulatory Compliance• IT Master Plan• Internal Audit
Danairat T., 2011, [email protected] Enterprise Architecture 74
Why we need IT Governance
• IT aligns Business and maximizes benefits• IT Resources are used responsibly• IT Risks are managed appropriately
Business Goals IT Goals IT Processes
Danairat T., 2011, [email protected] Enterprise Architecture 75
What is IT Governance?
IT processes with control framework linking IT to business requirements
and goals
Danairat T., 2011, [email protected] Enterprise Architecture 76
IT Governance and CobiT Framework
isaca.org
Danairat T., 2011, [email protected] Enterprise Architecture 77
IT Governance Key Processes
• Plan and Organize• Acquire and Implement• Deliver and Support• Monitor and Evaluate
PO1 Define a strategic IT plan.PO2 Define the information architecture.PO3 Determine technological direction.PO4 Define the IT processes, organization and relationships.PO5 Manage the IT investment.PO6 Communicate management aims and direction.PO7 Manage IT human resources.PO8 Manage quality.PO9 Assess and manage IT risks.PO10 Manage projects.
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 78
IT Governance Key Processes
• Plan and Organize• Acquire and Implement• Deliver and Support• Monitor and Evaluate
AI1 Identify automated solutions.AI2 Acquire and maintain application software.AI3 Acquire and maintain technology infrastructure.AI4 Enable operation and use.AI5 Procure IT resources.AI6 Manage changes.AI7 Install and accredit solutions and changes.
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 79
IT Governance Key Processes
• Plan and Organize• Acquire and Implement• Deliver and Support• Monitor and Evaluate
DS1 Define and manage service levels.DS2 Manage third-party services.DS3 Manage performance and capacity.DS4 Ensure continuous service.DS5 Ensure systems security.DS6 Identify and allocate costs.DS7 Educate and train users.DS8 Manage service desk and incidents.DS9 Manage the configuration.DS10 Manage problems.DS11 Manage data.DS12 Manage the physical environment.DS13 Manage operations.
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 80
IT Governance Key Processes
• Plan and Organize• Acquire and Implement• Deliver and Support• Monitor and Evaluate
ME1 Monitor and evaluate IT performance.ME2 Monitor and evaluate internal control.ME3 Ensure compliance with external requirements.ME4 Provide IT governance.
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 81
Sample: DS4 Ensure Continuous Service
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 82
Sample: DS4 Ensure Continuous Service
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 83
Sample: DS4 Ensure Continuous Service
COBIT Framework
MATURITY MODEL
0 Non-existent whenThere is no understanding of the risks, vulnerabilities and threats to IT operations or the impact of loss of IT services to the
business. Service continuity is not considered to need management attention.
1 Initial/Ad Hoc whenResponsibilities for continuous service are informal, and the authority to execute responsibilities is limited. Management is
becoming aware of the risks related to and the need for continuous service. The focus of management attention on continuous
service is on infrastructure resources, rather than on the IT services. Users implement workarounds in response to disruptions of
services. The response of IT to major disruptions is reactive and unprepared. Planned outages are scheduled to meet IT needs but do
not consider business requirements.
2 Repeatable but Intuitive whenResponsibility for ensuring continuous service is assigned. The approaches to ensuring continuous service are fragmented.
Reporting on system availability is sporadic, may be incomplete and does not take business impact into account. There is no
documented IT continuity plan, although there is commitment to continuous service availability and its major principles are known.
An inventory of critical systems and components exists, but it may not be reliable. Continuous service practices are emerging, but
success relies on individuals.
Danairat T., 2011, [email protected] Enterprise Architecture 84
Sample: DS4 Ensure Continuous Service
COBIT Framework
MATURITY MODEL
3 Defined whenAccountability for the management of continuous service is unambiguous. Responsibilities for continuous service planning andtesting are clearly defined and assigned. The IT continuity plan is documented and based on system criticality and business impact.
There is periodic reporting of continuous service testing. Individuals take the initiative for following standards and receiving trainingto deal with major incidents or a disaster. Management communicates consistently the need to plan for ensuring continuous service.
High-availability components and system redundancy are being applied. An inventory of critical systems and components ismaintained.
4 Managed and Measurable whenResponsibilities and standards for continuous service are enforced. The responsibility to maintain the continuous service plan isassigned. Maintenance activities are based on the results of continuous service testing, internal good practices, and the changing IT
and business environment. Structured data about continuous service are being gathered, analysed, reported and acted upon. Formaland mandatory training is provided on continuous service processes. System availability good practices are being consistently
deployed. Availability practices and continuous service planning influence each other. Discontinuity incidents are classified, and theincreasing escalation path for each is well known to all involved. Goals and metrics for continuous service have been developed and
agreed upon but may be inconsistently measured.
Danairat T., 2011, [email protected] Enterprise Architecture 85
Sample: DS4 Ensure Continuous Service
COBIT Framework
MATURITY MODEL
5 Optimised whenIntegrated continuous service processes take into account benchmarking and best external practices. The IT continuity plan isintegrated with the business continuity plans and is routinely maintained. The requirement for ensuring continuous service is
secured from vendors and major suppliers. Global testing of the IT continuity plan occurs, and test results are input for updating theplan. The gathering and analysis of data are used for continuous improvement of the process. Availability practices and continuous
service planning are fully aligned. Management ensures that a disaster or major incident will not occur as a result of a single pointof failure. Escalation practices are understood and thoroughly enforced. Goals and metrics on continuous service achievement are
measured in a systematic fashion. Management adjusts the planning for continuous service in response to the measures.
Danairat T., 2011, [email protected] Enterprise Architecture 86
Sample: AI3 Acquire and Maintain Technology Infrastructure
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 87
Sample: AI3 Acquire and Maintain Technology Infrastructure
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 88
Sample: AI3 Acquire and Maintain Technology Infrastructure
COBIT Framework
MATURITY MODEL
0 Non-existent whenManaging the technology infrastructure is not recognised as a sufficiently important topic to be addressed.
1 Initial/Ad Hoc whenThere are changes made to infrastructure for every new application, without any overall plan. Although there is an awareness that
the IT infrastructure is important, there is no consistent overall approach. Maintenance activity reacts to short-term needs. Theproduction environment is the test environment.
2 Repeatable but Intuitive whenThere is a consistency amongst tactical approaches when acquiring and maintaining the IT infrastructure. Acquisition andmaintenance of IT infrastructure are not based on any defined strategy and do not consider the needs of the business applications
that must be supported. There is an understanding that the IT infrastructure is important, supported by some formal practices. Somemaintenance is scheduled, but it is not fully scheduled and co-ordinated. For some environments, a separate test environment exists.
3 Defined whenA clear, defined and generally understood process exists for acquiring and maintaining IT infrastructure. The process supports theneeds of critical business applications and is aligned to IT and business strategy, but it is not consistently applied. Maintenance is
planned, scheduled and co-ordinated. There are separate environments for test and production.
Danairat T., 2011, [email protected] Enterprise Architecture 89
Sample: AI3 Acquire and Maintain Technology Infrastructure
COBIT Framework
MATURITY MODEL
4 Managed and Measurable whenThe acquisition and maintenance process for technology infrastructure has developed to the point where it works well for mostsituations, is followed consistently and is focused on reusability. The IT infrastructure adequately supports the business applications.
The process is well organised and proactive. The cost and lead time to achieve the expected level of scalability, flexibility andintegration are partially optimised.
5 Optimised whenThe acquisition and maintenance process for technology infrastructure is proactive and closely aligned with critical businessapplications and the technology architecture. Good practices regarding technology solutions are followed, and the organisation is
aware of the latest platform developments and management tools. Costs are reduced by rationalising and standardising infrastructurecomponents and by using automation. A high level of technical awareness can identify optimum ways to proactively improve
performance, including consideration of outsourcing options. The IT infrastructure is seen as the key enabler to leveraging theuse of IT.
Danairat T., 2011, [email protected] Enterprise Architecture 90
Sample: AI6 Manage Changes
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 91
Sample: AI6 Manage Changes
COBIT Framework
Danairat T., 2011, [email protected] Enterprise Architecture 92
IT Governance and Enterprise ArchitectIT Governance: What and How in IT Processes to meet Business Goals
Enterprise Architect: Who to work on an architectural design and
support throughout IT Governance processes
Role (Mandatory: M, Optional: O) PO AI DS ME
Chief Information Officer (CIO) M O O M
Enterprise Architect M M M M
Compliance, Audit, Risk and Security M M M M
Head of Development O M O O
Business Process Owner M O O M
Project Management Office (PMO) M M O O
Head IT Administration O M M M
Head of Operations M O M M
Danairat T., 2011, [email protected] Enterprise Architecture 93
Linking Process to IT Goalsisaca.org
Danairat T., 2011, [email protected] Enterprise Architecture 94
Linking IT Goals to Business Goalsisaca.org
Danairat T., 2011, [email protected] Enterprise Architecture 95
Build Enterprise ArchitectureThe Group Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 96
The Enterprise Reference Architecture
Customer Data Product Data Payment Data Accounting Org. HierarchyEnterprise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
ManagementH/W, Storage, OS, Database, AppServer Platform
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
Danairat T., 2011, [email protected] Enterprise Architecture 97
The Enterprise Reference Architecture
Customer Data Product Data Payment Data Accounting Org. HierarchyEnterprise Information Management
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
System Monitoring andManagement
Security/Auditingand Identity Management
DB Machine Elastic Cloud App Data Partitioning Data Warehouse/ODS
CEP Business Rules Service Registry Enterprise Repository& Governance
SOA/Service Bus ETL Application Adapters DB RealtimeIntegration
Business Process Analysis BPM/BPEL Application Integration
Architecture Master Data Mgmt
Web Channel Operational BI Strategic BI ECM/E2.0
DB SOD
Audit Tool
Role/Access Manager
Diag and Monitor
Perf Mgmt
Service Level Management
Secured Backup
Grid Management
Enterprise Infrastructure
Danairat T., 2011, [email protected] Enterprise Architecture 98
Enterprise Architecture Initiatives• Create Enterprise Master Data
- Consolidated Profile - Master Data – Customer, Product, Payment, Organization
- Operational Data Store
- Enterprise Real-time Data warehouse
• Enable Flexibility to be Responsive to Market Needs- Enterprise Processing 2.0
- Straight Through Processing
- Service Components
• Business Insight and Enterprise Monitoring- Product Profitability
- Business Insight Sales & Cross Sell Opportunities
- Complete Solution for Entire Service Lifecycle
• Agile, Secure and Standard IT Infrastructure- Cloud Computing
- Information Lifecycle Management
- Last Mile SLA
- Data Center and DR Optimization
• Operational Excellence and Governance Regulatory Compliance- Application Integration Architecture for Operation Excellence
- Enhanced Transparency Control
- Governance Across Heterogeneous Information Assets
Danairat T., 2011, [email protected] Enterprise Architecture 99
Group Workshop – The Initiative
Initiative Name:
Description:
People Involved:
1. <10 Yrs up Customers>2. <Marketing Team>
Supported Technology:
1. <GIS >2. <BI and Web Portal>3. <Database>
<Drawing here with key points>Goals, Process, Data, Integration: from, toCurrent agendas (functional, performance, operation, security) and basic plan, No of users, DB and App Server utilization.
<Write your initiative name>
Date:Name:
Customers Products Payments Accounting Org. Hierarchy
Enterpr ise Information Management
Data CentricProcess Centric
User CentricEnterprise Infrastructure
System Monitoring
andManagement
Security/Auditing
and Identity
Management
H/W, Storage, OS, Database, AppServer
Decision Centric
Insightand
Monitoring
Sales andMarketing
Regulatory Compliance
CorporateAdmin.
Core Systems
Access Channels
Integration and Channel Systems
xxx
Notes: The Initiative can be in one business area or cross business area.
Danairat T., 2011, [email protected] Enterprise Architecture 100
Build Enterprise ArchitectureThe Group Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 101
Build Enterprise ArchitectureThe Group Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 102
Build Enterprise ArchitectureThe Group Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 103
Summary
• Building Enterprise Architecture• Enterprise Architecture Maturity Model• Understanding Today Technology Platforms and Key Considerations
• User Centric Platform• Process Centric Platform• Data Centric Platform• Decision Centric Platform• Application Server, Database Server and Hardware Platform
• TOGAF and ADM• Enterprise Architecture and Cloud Computing Roadmap• Enterprise Architecture and IT Governance• Group Brainstorm Workshop
Danairat T., 2011, [email protected] Enterprise Architecture 104
Thank you very much.
Danairat T., 2011, [email protected] Enterprise Architecture 105
Appendix – EA Tools• Vision to Deployment Arch.
• Business and IT Alignment
• EA Repository
• Architecture Revision
• Business Process Simulation
• PDF and Web/Mail Reporting
Description:-
Top Related