EA Intensive Course "Building Enterprise Architecture" by mr.danairat

  • 2,134 views
Uploaded on

EA Intensive Course "Building Enterprise Architecture" by mr.danairat …

EA Intensive Course "Building Enterprise Architecture" by mr.danairat


  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,134
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
274
Comments
0
Likes
4

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Building Enterprise Architecture The 2 Days EA Intensive Course Danairat T. Oracle Enterprise Architect, ASEAN Certified Java Programmer, TOGAF – Silver danairat@gmail.com, +66-81-559-1446Building Enterprise Architecture 1 Danairat T., 2011, danairat@gmail.com
  • 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 WorkshopBuilding Enterprise Architecture 2 Danairat T., 2011, danairat@gmail.com
  • 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 WorkshopBuilding Enterprise Architecture 3 Danairat T., 2011, danairat@gmail.com
  • 4. IntroductionBuilding Enterprise Architecture 4 Danairat T., 2011, danairat@gmail.com
  • 5. General IT Organization Chief Executive Officer (CEO) Business Chief Information Chief Financial Executive Officer (CIO) Officer (CFO) Business Chief Architect Head of Process Owner Compliance, Audit, Operations Risk and Security Project Head of Head of IT Management Office (PMO) Development AdministrationBuilding Enterprise Architecture 5 Danairat T., 2011, danairat@gmail.com
  • 6. Direction Organization Team workingBuilding Enterprise Architecture 6 Danairat T., 2011, danairat@gmail.com
  • 7. Goals Business Objectives Process, Application, Data, TechnologyBuilding Enterprise Architecture 7 Danairat T., 2011, danairat@gmail.com
  • 8. Kindly always understand the driver from political -> business business -> technicalBuilding Enterprise Architecture 8 Danairat T., 2011, danairat@gmail.com
  • 9. How to Explore the Enterprise Investment & Value E A BSC, ITG, etc. CMMi, ITIL, COSO, etc.Building Enterprise Architecture 10 Danairat T., 2011, danairat@gmail.com
  • 10. Today Architecture ChallengesBuilding Enterprise Architecture 11 Danairat T., 2011, danairat@gmail.com
  • 11. 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 ___________Building Enterprise Architecture 12 Danairat T., 2011, danairat@gmail.com
  • 12. The Need of Enterprise ArchitectureBuilding Enterprise Architecture 14 Danairat T., 2011, danairat@gmail.com
  • 13. There are many of IT related agendas • Alignment with Business Goals • Change and Configuration Management • IT Governance, Risk, Compliance • Enterprise Portfolio ManagementBuilding Enterprise Architecture 15 Danairat T., 2011, danairat@gmail.com
  • 14. There are so many Architects • Software Architect • Data Architect • Application Architect • Business Architect • Technology Architect • Solution ArchitectBuilding Enterprise Architecture 16 Danairat T., 2011, danairat@gmail.com
  • 15. What is Enterprise Architecture?Building Enterprise Architecture 17 Danairat T., 2011, danairat@gmail.com
  • 16. Enterprise Architecture Enterprise Architecture is a structure design to ensure alignment between the business and IT strategies plus operating model, guiding principles.Building Enterprise Architecture 18 Danairat T., 2011, danairat@gmail.com
  • 17. There are many of related standards/guidelines for EA Specific ITIL CMMi ISO 20000 TOGAF IT Relevance ISO 27001 27002 (17799) CobiT SOX ISO 38500 COSO Basel II Six Sigma ISO 9000 Score- Holistic cards Low High AbstractionBuilding Enterprise Architecture 20 Danairat T., 2011, danairat@gmail.com
  • 18. Enterprise Architecture and Architecture Development MethodBuilding Enterprise Architecture 21 Danairat T., 2011, danairat@gmail.com
  • 19. Enterprise Architecture and Architecture Development Method Business Process Architecture Technology and Data and Infrastructure Information Architecture Architecture Application and Solution ArchitectureBuilding Enterprise Architecture 22 Danairat T., 2011, danairat@gmail.com
  • 20. Enterprise Reference Architecture FrameworkBuilding Enterprise Architecture 23 Danairat T., 2011, danairat@gmail.com
  • 21. The Enterprise Reference Architecture Access Channels Integration and Channel Systems Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems Enterprise Information Management System Security/ Monitoring Enterprise Infrastructure Auditing and and Management Identity ManagementBuilding Enterprise Architecture 24 Danairat T., 2011, danairat@gmail.com
  • 22. The Enterprise Reference Architecture Access Channels Integration and Channel Systems Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems Enterprise Information Management Customer Data Product Data Payment Data Accounting Org. Hierarchy Enterprise Infrastructure User Centric System Process Centric Security/ Monitoring Auditing Data Centric and and Management Decision Centric Identity Management H/W, Storage, OS, Database, AppServer PlatformBuilding Enterprise Architecture 25 Danairat T., 2011, danairat@gmail.com
  • 23. The Enterprise Reference Architecture with Architecture Domains Architecture Access Channels Business Integration and Channel Systems Architecture Application Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems Arch. Architecture Data Technology Enterprise Information Management Customer Data Product Data Payment Data Accounting Org. Hierarchy Enterprise Infrastructure User Centric System Process Centric Security/ Monitoring Auditing Data Centric and and Management Decision Centric Identity Management H/W, Storage, OS, Database, AppServer PlatformBuilding Enterprise Architecture 26 Danairat T., 2011, danairat@gmail.com
  • 24. Group Workshop - The Current Enterprise Architecture Team Name: xxx 1. Name, Company, E-mail 3. Name, Company, E-mail 2. Name, Company, E-mail 4. Name, Company, E-mail Write down your existing enterprise Enterprise Reference Architecture architecture foot print Access Channels Business Sales and Core Business Corporate Regulatory Insight Marketing Admin. Compliance and Processing Systems Monitoring Master Data System Security/ Monitoring Auditing and Enterprise Infrastructure and Management Identity ManagementBuilding Enterprise Architecture 27 Danairat T., 2011, danairat@gmail.com
  • 25. Summary • Today Architecture Challenges • The Need of Enterprise Architecture • What is Enterprise Architecture? • Architecture Development Method • Enterprise Reference Architecture Framework • Group Brainstorm WorkshopBuilding Enterprise Architecture 28 Danairat T., 2011, danairat@gmail.com
  • 26. 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 WorkshopBuilding Enterprise Architecture 30 Danairat T., 2011, danairat@gmail.com
  • 27. Building Enterprise ArchitectureBuilding Enterprise Architecture 31 Danairat T., 2011, danairat@gmail.com
  • 28. Enterprise Continuum www.opengroup.orgBuilding Enterprise Architecture 32 Danairat T., 2011, danairat@gmail.com
  • 29. Architecture and Solution Continuum www.opengroup.orgBuilding Enterprise Architecture 33 Danairat T., 2011, danairat@gmail.com
  • 30. Building Enterprise Architecture The 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 developmentBuilding Enterprise Architecture 34 Danairat T., 2011, danairat@gmail.com
  • 31. The Enterprise Reference Architecture with Architecture Domains Architecture Access Channels Business Integration and Channel Systems Architecture Application Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems Arch. Architecture Data Technology Enterprise Information Management Customer Data Product Data Payment Data Accounting Org. Hierarchy Enterprise Infrastructure User Centric System Process Centric Security/ Monitoring Auditing Data Centric and and Management Decision Centric Identity Management H/W, Storage, OS, Database, AppServer PlatformBuilding Enterprise Architecture 35 Danairat T., 2011, danairat@gmail.com
  • 32. Creating Target Enterprise Architecture Vision and Business Architecture • Provide target business goals for the focus business areas or Architecture Access Channels Business Integration and Channel Systems for the difference pillars Insight Sales and Corporate Regulatory Architecture Application and Marketing Admin. Compliance • Revenue Monitoring Core Systems • Cost Arch. Architecture Data Technology Enter pr ise Infor m ation Managem ent Custom er Data Pr oduct Data Paym ent Data Accounting Or g. Hier ar chy Enterprise Infrastructure User Centric System Process Centric Security/ • Risk Monitoring Auditing and Data Centric and Management Identity Decision Centric Management H/W, Storage, OS, Database, AppServer Platform • Etc. • Provide the target business objectives for 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 frameworkBuilding Enterprise Architecture 36 Danairat T., 2011, danairat@gmail.com
  • 33. Creating Target Enterprise Architecture Application Architecture • Provide a target business service Architecture Access Channels Business Integration and Channel Systems and its processes Insight Sales and Corporate Regulatory for the focus business areas Architecture Application and Marketing Admin. Compliance Monitoring Core Systems • Provide a target process integrations Arch. Architecture Data Technology Enter pr ise Infor m ation Managem ent Custom er Data Pr oduct Data Paym ent Data Accounting Or g. Hier ar chy Enterprise Infrastructure User Centric Security/ for the focus business areas System Process Centric Monitoring Auditing and Data Centric and Management Decision Centric H/W, Storage, OS, Database, AppServer Platform Identity Management • Provide related business roles for the business process • Define required resources for business service development • Define business service operation cycle • Provide detailed explanations if any Remarks: To create business process, you may consult the BPMNBuilding Enterprise Architecture 37 Danairat T., 2011, danairat@gmail.com
  • 34. BPM - IT and Business Alignment Business Artifact and Model IT Artifact and Model Generate/ Merge Shared Metadata Model Repository Oracle Corporation 38Building Enterprise Architecture 38 Danairat T., 2011, danairat@gmail.com
  • 35. Application Architecture Key Common RequirementsBuilding Enterprise Architecture 39 Danairat T., 2011, danairat@gmail.com
  • 36. Application Architecture Key Common Requirements User Features, Functions Ease of Use and Response Time High Availability Distributed Solution Operation Management/ GRID/Cloud Automation Access Control, Security Governance, Standard and ComplianceBuilding Enterprise Architecture 40 Danairat T., 2011, danairat@gmail.com
  • 37. Creating Target Enterprise Architecture Data Architecture Architecture Access Channels • Provide reference data (master) Business Integration and Channel Systems Insight Sales and Corporate Regulatory • Provide common data relationship Architecture Application and Marketing Admin. Compliance Monitoring Core Systems • Provide master data creation and its Arch. Architecture Data Technology life cycle (including cleansing Enter pr ise Infor m ation Managem ent Custom er Data Pr oduct Data Paym ent Data Accounting Or g. Hier ar chy Enterprise Infrastructure User Centric System Monitoring and Management Process Centric Data Centric Security/ Auditing and Identity process) Decision Centric Management H/W, Storage, OS, Database, AppServer Platform • Provide both logical and physical data architecture design • Provide detailed explanations if anyBuilding Enterprise Architecture 42 Danairat T., 2011, danairat@gmail.com
  • 38. Enterprise Data and Integration Transactional Application Enterprise Enterprise Integration Specific Operational Data Warehouse, Data Data Data Data Marts and BI WS App1 Data ETL/ELT ODS WS App2 SOA Data ETL/ELT Data Warehouse WS App3 Data Master Data Data Management Process Data Governance, Data Architecture Management, Data Modeling, Data Quality, DW/BI, Metadata Management, Document/Content ManagementBuilding Enterprise Architecture 43 Danairat T., 2011, danairat@gmail.com
  • 39. Transactional Integration Data Guidelines:- Transactional Application Enterprise Enterprise Integration Specific Operational Data Warehouse Data Data Data and Data Marts WS App1 Data ETL/ELT 1. Define Transactional Integration Data ODS SOA WS App2 Data 2. Identify Source and Target Systems ETL/ELT Data Warehouse WS App3 Data 3. Adoption of WS and WS Attachment Master Data 4. Put All Data Models in XSD format 5. Acquire Metadata Tool for keeping XSD Data Management Process Data Gover nance, Data Ar chitectur e Managem ent, Data Modeling, Data Quality, DW/BI, Metadata Managem ent, Docum ent/Content Managem ent 6. Leverage XSLT for data transformation 7. Leverage WS Security for Proxy Interface 8. Use of Tool to perform online Data Field Mapping between Enterprise Name and Application Specific Name 9. Acquire Real-time Data Integration Monitoring ToolBuilding Enterprise Architecture 44 Danairat T., 2011, danairat@gmail.com
  • 40. Application Specific Data Guidelines:- Transactional Application Enterprise Enterprise Integration Specific Operational Data Warehouse Data Data Data and Data Marts WS App1 Data 1. Acquire Open Standard Industry Data Model ETL/ELT ODS where possible WS SOA App2 Data ETL/ELT Data Warehouse 2. Standardize Data Definition throughout WS App3 Data Applications 3. Do Not Try to Create New Data Fields before Master Data Checking Application Data Template Data Management Process Data Gover nance, Data Ar chitectur e Managem ent, Data Modeling, Data Quality, DW/BI, Metadata Managem ent, Docum ent/Content Managem ent 4. Adoption of WS and WS Attachment for Integration part 5. Minimize Point to Point Batch Integration where possible to reduce Eco-System Overhead 6. Always define Data Cleansing Roles in Business User rather than doing in IT Department 7. Maximize Centralized Master Data Usage 8. Also Classify an Unstructured Data in both Master Data and Operational Data typesBuilding Enterprise Architecture 45 Danairat T., 2011, danairat@gmail.com
  • 41. Enterprise Operational Data Store Guidelines:- Transactional Application Enterprise Enterprise Integration Specific Operational Data Warehouse Data Data Data and Data Marts WS App1 Data 1. Focus Data only for Business Operation Level ETL/ELT ODS SOA WS App2 Data 2. Understand Data Fields Requirement from ETL/ELT Data Warehouse Business Units 3. Understand ODS Usage Pattern WS App3 Data Master Data • Exchange Data between Applications Data Management Process Data Gover nance, Data Ar chitectur e Managem ent, Data Modeling, Data Quality, DW/BI, Metadata Managem ent, Docum ent/Content Managem ent • For Enterprise Operational Reporting 4. Leverage 3NF for ODS Database 5. You may use DW Staging as ODS 6. Standardize Data Key (eg. Customer ID) for All Application where possible 7. Define Data Create/Update Sequence from authorized Application Systems 8. Define Data Remove Process 9. Maximize Master Data Usage 10. Leverage System MonitoringBuilding Enterprise Architecture 46 Danairat T., 2011, danairat@gmail.com
  • 42. Enterprise Data Warehouse, Data Marts and BI Guidelines:- Transactional Application Enterprise Enterprise Integration Specific Operational Data Warehouse Data Data Data and Data Marts WS App1 Data 1. Focus Data only for Business Strategic Level ETL/ELT ODS SOA WS App2 Data 2. BI is NOT only in DW, DM. BI is Everywhere. ETL/ELT Data Warehouse 3. Acquire Efficient Data Integration Tool (ETL/ELT) for Data Loading, Transformation WS App3 Data Master Data 4. Create a Reliable DW for some ac-hoc query Data Management Process might impact to overall performance Data Gover nance, Data Ar chitectur e Managem ent, Data Modeling, Data Quality, DW/BI, Metadata Managem ent, Docum ent/Content Managem ent 5. Data Marts and OLAP for Business Requirements 6. Always pro-active advertise the new set of subject available to Business Users 7. Educate End-User for the BI/Dashboard Tool 8. Distribute Summary Report to End-User to Minimize Large Data Inquiry Cost 9. Partitioning Data where possible 10. 3NF schema design for a data warehouse 11. Prioritize Parallel Execution 12. DW Optimizer and Stats managementBuilding Enterprise Architecture 47 Danairat T., 2011, danairat@gmail.com
  • 43. Master Data Transactional Application Enterprise Enterprise Integration Specific Operational Data Warehouse Data Data Data and Data Marts Guideline:- WS App1 Data ETL/ELT ODS 1. Define Master Data Owner and Change Control WS SOA App2 Data ETL/ELT Data Warehouse 2. Adopt Data Governance for MDM process 3. Master Data Classification WS App3 Data Master Data 4. Define Source and Target of Master Data Data Management Process Data Gover nance, Data Ar chitectur e Managem ent, Data Modeling, Data Quality, DW/BI, Metadata Managem ent, Docum ent/Content Managem ent 5. Acquire Data Profiling and Quality Tool for Data Cleansing 6. Define Master and Replica Data if anyBuilding Enterprise Architecture 48 Danairat T., 2011, danairat@gmail.com
  • 44. Creating Target Enterprise Architecture Technology Architecture Architecture • Considering an open computing Access Channels Business Integration and Channel Systems Insight Sales and Corporate Regulatory platform Architecture Application and Marketing Admin. Compliance Monitoring Core Systems • Creating target ABB and SBB Arch. Architecture Data Technology • Creating a common component Enter pr ise Infor m ation Managem ent Custom er Data Pr oduct Data Paym ent Data Accounting Or g. Hier ar chy Enterprise Infrastructure User Centric System Monitoring and Management Process Centric Data Centric Decision Centric Security/ Auditing and Identity integration Management H/W, Storage, OS, Database, AppServer Platform • Provide detailed explanations if any ABB is architecture building block which is not tight to vendor product SBB is solution building block which is tight to vendor productBuilding Enterprise Architecture 49 Danairat T., 2011, danairat@gmail.com
  • 45. Understanding Today Technology Platforms and Key ConsiderationsBuilding Enterprise Architecture 50 Danairat T., 2011, danairat@gmail.com
  • 46. Technology Standard and Key Consideration User Interface and User Collaboration Layer Access Channels • Open User Interface Development Integration and Channel Systems Framework; JSF, etc. Insight and Sales and Marketing Corporate Regulatory Admin. Compliance • Event Driven UI; JSF, .NET, etc. Monitoring Core Systems Custom er Data Pr oduct Data Enter pr ise Infor m ation Managem ent Paym ent Data Accounting Or g. Hier ar chy • XML UI with Data Binding; JSF, ADF, Enterprise Infrastructure User Centric Process Centric Taglibs, etc. System Monitoring Data Centric Security/ Auditing (enable you to render in graph, table, map) and Decision Centric and Management Identity H/W, Storage, OS, Database, AppServer Platform Management • Calendar and Holiday Aware System; .ics, etc. • Metadata Management • Search Capability; Thai • Present Technology over HTTPBuilding Enterprise Architecture 51 Danairat T., 2011, danairat@gmail.com
  • 47. Technology Standard and Key Consideration Process Integration Layer Access Channels Integration and • BPMN 2.0 aware system Channel Systems • Business Process Execution Language Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems • Standard Workflow Patterns Custom er Data Pr oduct Data Enter pr ise Infor m ation Managem ent Paym ent Data Accounting Or g. Hier ar chy (FYI., Sequential, Vote, Delegation, Reassignment, etc.) Enterprise Infrastructure • XML Workflow Application User Centric Process Centric Security/ System Monitoring Data Centric Auditing and Decision Centric and Management Identity H/W, Storage, OS, Database, AppServer Platform Management • Process Simulation • WSDL • SOAP, REST (Representational State Transfer) • UDDI (Universal Description Discovery and Integration) • Side-By-Side Versioning in RuntimeBuilding Enterprise Architecture 52 Danairat T., 2011, danairat@gmail.com
  • 48. Technology Standard and Key Consideration Data Integration Layer Access Channels Integration and • Reliable Data Transfer (persistence) Channel Systems • Queuing System Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems • Transfer Priority and Security Enter pr ise Infor m ation Managem ent Custom er Data Pr oduct Data Paym ent Data Accounting Or g. Hier ar chy Enterprise Infrastructure User Centric • XML Declaration Process Centric Security/ System Monitoring Data Centric Auditing and Management Decision Centric H/W, Storage, OS, Database, AppServer Platform and Identity Management • Routing Simulation • Monitoring System and Exception Capturing • Side-By-Side Versioning in RuntimeBuilding Enterprise Architecture 53 Danairat T., 2011, danairat@gmail.com
  • 49. Technology Standard and Key Consideration Decision Layer Access Channels Integration and Channel Systems • Inference Rules Engine; User Invocation Insight Sales and Corporate Regulatory and Monitoring Marketing Core Systems Admin. Compliance • Event Condition Action; System Custom er Data Pr oduct Data Enter pr ise Infor m ation Managem ent Paym ent Data Accounting Or g. Hier ar chy Monitoring Enterprise Infrastructure User Centric System Monitoring Process Centric Data Centric Security/ Auditing • Rules describe in XML, POJOs, flat files and Decision Centric and Management Identity H/W, Storage, OS, Database, AppServer Platform Management • Enterprise Metadata Repository SystemBuilding Enterprise Architecture 54 Danairat T., 2011, danairat@gmail.com
  • 50. Technology Standard and Key Consideration Database Server and Application Server Database Access Channels • ANSI (American National Standards Institute) SQL Integration and Channel Systems • DB Programming support • DB and System Diagnostic and Tuning Tool Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems • Segregation of Duty Support Custom er Data Pr oduct Data Enter pr ise Infor m ation Managem ent Paym ent Data Accounting Or g. Hier ar chy • Active-Active Clustering Enterprise Infrastructure User Centric Process Centric Security/ System Monitoring Data Centric Auditing and Decision Centric and Management H/W, Storage, OS, Database, AppServer Platform Identity Management Application Server • Open Development Framework • Monitoring Matric; eg. JMX, Managed Bean • In-Memory Session Clustering • Deployment Descriptor • Declarative Transaction • Declarative Security Access ControlBuilding Enterprise Architecture 55 Danairat T., 2011, danairat@gmail.com
  • 51. Technology Standard and Key Consideration Monitoring and Management Access Channels • Simplistic as possible Integration and Channel Systems • Segregation of Monitoring and Insight Sales and Corporate Regulatory Management and Marketing Admin. Compliance Monitoring Core Systems Enter pr ise Infor m ation Managem ent • JMX; Java Management Extension Custom er Data Pr oduct Data Paym ent Data Accounting Or g. Hier ar chy Enterprise Infrastructure User Centric Process Centric • SNMP support System Security/ Monitoring Data Centric Auditing and Management Decision Centric H/W, Storage, OS, Database, AppServer Platform and Identity Management • Text, Graphical with actionable support • Information Correlation supportBuilding Enterprise Architecture 56 Danairat T., 2011, danairat@gmail.com
  • 52. Technology Standard and Key Consideration Security Auditing and Identity Management Access Channels • Access Control and Authorization Server Integration and Channel Systems • Encryption Mechanism Insight and Sales and Marketing Corporate Regulatory Admin. Compliance • Key Management Support Monitoring Core Systems Custom er Data Pr oduct Data Enter pr ise Infor m ation Managem ent Paym ent Data Accounting Or g. Hier ar chy • Non-Repudiation Support System Enterprise Infrastructure User Centric Process Centric Security/ • Enterprise Roles Management Monitoring Data Centric Auditing and Decision Centric and Management H/W, Storage, OS, Database, AppServer Platform Identity Management • User Roles an Accounts Provisioning • SAML for IdM FederationBuilding Enterprise Architecture 57 Danairat T., 2011, danairat@gmail.com
  • 53. Enterprise Architecture Maturity ModelBuilding Enterprise Architecture 58 Danairat T., 2011, danairat@gmail.com
  • 54. Enterprise Architecture Maturity Model Maturity Level Level 1 Level 2 Level 3 Level 4 Level 5 Awareness/ Repeat Define Manage Optimized Ad-Hoc EA Awareness Session Replicate the EA EA process to be Roll out EA Create enterprise Selected program/project exercise to new defined. activities best practices for for EA initialization business area ADM activities to all business EA activities Perform ADM for alignment areas Fully IT and Business selected program/project alignmentBuilding Enterprise Architecture 59 Danairat T., 2011, danairat@gmail.com
  • 55. 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 PolicyBuilding Enterprise Architecture 60 Danairat T., 2011, danairat@gmail.com
  • 56. 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 possibleBuilding Enterprise Architecture 61 Danairat T., 2011, danairat@gmail.com
  • 57. 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 Scenarios including external integration (BPMN) – reuse where possible • Apply IT Governance Guideline for “Create Agility”Building Enterprise Architecture 62 Danairat T., 2011, danairat@gmail.com
  • 58. 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 areasBuilding Enterprise Architecture 63 Danairat T., 2011, danairat@gmail.com
  • 59. 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 PlanBuilding Enterprise Architecture 64 Danairat T., 2011, danairat@gmail.com
  • 60. TOGAF Architecture Development MethodBuilding Enterprise Architecture 65 Danairat T., 2011, danairat@gmail.com
  • 61. 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.orgBuilding Enterprise Architecture 66 Danairat T., 2011, danairat@gmail.com
  • 62. Enterprise Architecture and Cloud Computing RoadmapBuilding Enterprise Architecture 68 Danairat T., 2011, danairat@gmail.com
  • 63. 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: 5 Essential Characteristics 3 Service Models 4 Deployment Models • On-demand self-service • SaaS • Public Cloud • Resource pooling • PaaS • Private Cloud • Rapid elasticity • IaaS • Community Cloud • Measured service • Hybrid Cloud • Broad network access Source: NIST Definition of Cloud Computing v15Building Enterprise Architecture 69 Danairat T., 2011, danairat@gmail.com
  • 64. Cloud Roadmap Public Clouds Hybrid IaaS PaaS IaaS SaaS Public Cloud Evolution PaaS SaaS Private Cloud Evolution Virtual Private Cloud App1 App2 App3 App1 App2 App3 App1 App2 App3 App1 App2 App3 Private PaaS Private PaaS Private PaaS Private IaaS Private IaaS Private IaaS Silo’d Grid Private Cloud Hybrid • Physical • Virtual • Self-service • Federation with • Dedicated • Shared services • Policy-based public clouds • Static • Dynamic resource mgmt • Interoperability • Heterogeneous • Standardized • Chargeback • Cloud bursting appliances • Capacity planning Oracle CorporationBuilding Enterprise Architecture 70 Danairat T., 2011, danairat@gmail.com
  • 65. Cloud Management Capabilities Cloud Management Capabilities Self-Service Metering and Policy-Driven Capacity Assembly Provisioning Chargeback Resource Mgmt Planning Packaging Foundation Capabilities for Managing Datacenters Configuration Lifecycle and Compliance Management Application Application Performance Quality Management Management Oracle CorporationBuilding Enterprise Architecture 71 Danairat T., 2011, danairat@gmail.com
  • 66. Enterprise Architecture and IT GovernanceBuilding Enterprise Architecture 72 Danairat T., 2011, danairat@gmail.com
  • 67. 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 AuditBuilding Enterprise Architecture 73 Danairat T., 2011, danairat@gmail.com
  • 68. 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 ProcessesBuilding Enterprise Architecture 74 Danairat T., 2011, danairat@gmail.com
  • 69. What is IT Governance? IT processes with control framework linking IT to business requirements and goalsBuilding Enterprise Architecture 75 Danairat T., 2011, danairat@gmail.com
  • 70. IT Governance and CobiT Framework isaca.orgBuilding Enterprise Architecture 76 Danairat T., 2011, danairat@gmail.com
  • 71. IT Governance Key Processes • Plan and Organize PO1 Define a strategic IT plan. • Acquire and Implement PO2 Define the information architecture. • Deliver and Support PO3 Determine technological direction. • Monitor and Evaluate 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 FrameworkBuilding Enterprise Architecture 77 Danairat T., 2011, danairat@gmail.com
  • 72. 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 FrameworkBuilding Enterprise Architecture 78 Danairat T., 2011, danairat@gmail.com
  • 73. IT Governance Key Processes DS1 Define and manage service levels. • Plan and Organize DS2 Manage third-party services. • Acquire and Implement DS3 Manage performance and capacity. • Deliver and Support DS4 Ensure continuous service. • Monitor and Evaluate 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 FrameworkBuilding Enterprise Architecture 79 Danairat T., 2011, danairat@gmail.com
  • 74. 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 FrameworkBuilding Enterprise Architecture 80 Danairat T., 2011, danairat@gmail.com
  • 75. Sample: DS4 Ensure Continuous ServiceCOBIT FrameworkBuilding Enterprise Architecture 81 Danairat T., 2011, danairat@gmail.com
  • 76. Sample: DS4 Ensure Continuous ServiceCOBIT FrameworkBuilding Enterprise Architecture 82 Danairat T., 2011, danairat@gmail.com
  • 77. Sample: DS4 Ensure Continuous Service MATURITY MODEL 0 Non-existent when There 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 when Responsibilities 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 when Responsibility 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.COBIT FrameworkBuilding Enterprise Architecture 83 Danairat T., 2011, danairat@gmail.com
  • 78. Sample: DS4 Ensure Continuous Service MATURITY MODEL 3 Defined when Accountability for the management of continuous service is unambiguous. Responsibilities for continuous service planning and testing 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 training to 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 is maintained. 4 Managed and Measurable when Responsibilities and standards for continuous service are enforced. The responsibility to maintain the continuous service plan is assigned. 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. Formal and 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 the increasing 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.COBIT FrameworkBuilding Enterprise Architecture 84 Danairat T., 2011, danairat@gmail.com
  • 79. Sample: DS4 Ensure Continuous Service MATURITY MODEL 5 Optimised when Integrated continuous service processes take into account benchmarking and best external practices. The IT continuity plan is integrated 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 the plan. 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 point of 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.COBIT FrameworkBuilding Enterprise Architecture 85 Danairat T., 2011, danairat@gmail.com
  • 80. Sample: AI3 Acquire and Maintain Technology InfrastructureCOBIT FrameworkBuilding Enterprise Architecture 86 Danairat T., 2011, danairat@gmail.com
  • 81. Sample: AI3 Acquire and Maintain Technology InfrastructureCOBIT FrameworkBuilding Enterprise Architecture 87 Danairat T., 2011, danairat@gmail.com
  • 82. Sample: AI3 Acquire and Maintain Technology Infrastructure MATURITY MODEL 0 Non-existent when Managing the technology infrastructure is not recognised as a sufficiently important topic to be addressed. 1 Initial/Ad Hoc when There 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. The production environment is the test environment. 2 Repeatable but Intuitive when There is a consistency amongst tactical approaches when acquiring and maintaining the IT infrastructure. Acquisition and maintenance 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. Some maintenance is scheduled, but it is not fully scheduled and co-ordinated. For some environments, a separate test environment exists. 3 Defined when A clear, defined and generally understood process exists for acquiring and maintaining IT infrastructure. The process supports the needs 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.COBIT FrameworkBuilding Enterprise Architecture 88 Danairat T., 2011, danairat@gmail.com
  • 83. Sample: AI3 Acquire and Maintain Technology Infrastructure MATURITY MODEL 4 Managed and Measurable when The acquisition and maintenance process for technology infrastructure has developed to the point where it works well for most situations, 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 and integration are partially optimised. 5 Optimised when The acquisition and maintenance process for technology infrastructure is proactive and closely aligned with critical business applications 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 infrastructure components 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 the use of IT.COBIT FrameworkBuilding Enterprise Architecture 89 Danairat T., 2011, danairat@gmail.com
  • 84. Sample: AI6 Manage ChangesCOBIT FrameworkBuilding Enterprise Architecture 90 Danairat T., 2011, danairat@gmail.com
  • 85. Sample: AI6 Manage ChangesCOBIT FrameworkBuilding Enterprise Architecture 91 Danairat T., 2011, danairat@gmail.com
  • 86. IT Governance and Enterprise Architect IT 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 MBuilding Enterprise Architecture 92 Danairat T., 2011, danairat@gmail.com
  • 87. Linking Process to IT Goals isaca.orgBuilding Enterprise Architecture 93 Danairat T., 2011, danairat@gmail.com
  • 88. Linking IT Goals to Business Goals isaca.orgBuilding Enterprise Architecture 94 Danairat T., 2011, danairat@gmail.com
  • 89. Build Enterprise Architecture The Group WorkshopBuilding Enterprise Architecture 95 Danairat T., 2011, danairat@gmail.com
  • 90. The Enterprise Reference Architecture Access Channels Integration and Channel Systems Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems Enterprise Information Management Customer Data Product Data Payment Data Accounting Org. Hierarchy Enterprise Infrastructure User Centric System Process Centric Security/ Monitoring Auditing Data Centric and and Management Decision Centric Identity Management H/W, Storage, OS, Database, AppServer PlatformBuilding Enterprise Architecture 96 Danairat T., 2011, danairat@gmail.com
  • 91. The Enterprise Reference Architecture Access Channels Integration and Channel Systems Insight Sales and Corporate Regulatory and Marketing Admin. Compliance Monitoring Core Systems Enterprise Information Management Customer Data Product Data Payment Data Accounting Org. Hierarchy System Monitoring and Enterprise Infrastructure Security/Auditing and Identity Management Web Channel Operational BI Strategic BI ECM/E2.0 Management Service Level Role/Access Management Business Process Application Integration Manager BPM/BPEL Architecture Master Data Mgmt Analysis Perf Mgmt DB Realtime Audit Tool SOA/Service Bus ETL Application Adapters Integration Diag and Enterprise Repository DB SOD Monitor CEP Business Rules Service Registry & Governance Grid Secured Management Data Backup DB Machine Elastic Cloud App Data Partitioning Warehouse/ODSBuilding Enterprise Architecture 97 Danairat T., 2011, danairat@gmail.com
  • 92. 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 • Operational Excellence and Governance Regulatory Compliance - Application Integration Architecture for Operation Excellence - Enhanced Transparency Control - Governance Across Heterogeneous Information Assets • Agile, Secure and Standard IT Infrastructure - Cloud Computing - Information Lifecycle Management - Last Mile SLA - Data Center and DR OptimizationBuilding Enterprise Architecture 98 Danairat T., 2011, danairat@gmail.com
  • 93. Group Workshop – The Initiative Access Channels Name: Date: Integration and Channel Systems Insight and Monitoring Sales and Marketing Corporate Admin. Regulatory Compliance Initiative Name: <Write your initiative name> Core Systems xxx Custom er s Pr oducts Enter pr ise Infor m ation Managem ent Paym ents Accounting Or g. Hier ar chy Description: Enterprise Infrastructure System Monitoring and User Centric Process Centric Data Centric Security/ Auditing and <Drawing here with key points> Management Decision Centric H/W, Storage, OS, Database, AppServer Identity Management Goals, Process, Data, Integration: from, to Current agendas (functional, performance, operation, security) and basic plan, No of users, DB and App Server utilization. People Involved: Supported Technology: Notes: The Initiative can be in one business area or 1. <GIS > cross business area. 1. <10 Yrs up Customers> 2. <BI and Web Portal> 2. <Marketing Team> 3. <Database>Building Enterprise Architecture 99 Danairat T., 2011, danairat@gmail.com
  • 94. Build Enterprise Architecture The Group WorkshopBuilding Enterprise Architecture 100 Danairat T., 2011, danairat@gmail.com
  • 95. Build Enterprise Architecture The Group WorkshopBuilding Enterprise Architecture 101 Danairat T., 2011, danairat@gmail.com
  • 96. Build Enterprise Architecture The Group WorkshopBuilding Enterprise Architecture 102 Danairat T., 2011, danairat@gmail.com
  • 97. 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 WorkshopBuilding Enterprise Architecture 103 Danairat T., 2011, danairat@gmail.com
  • 98. Thank you very much.Building Enterprise Architecture 104 Danairat T., 2011, danairat@gmail.com
  • 99. Appendix – EA Tools Description:- • Vision to Deployment Arch. • Business and IT Alignment • EA Repository • Architecture Revision • Business Process Simulation • PDF and Web/Mail ReportingBuilding Enterprise Architecture 105 Danairat T., 2011, danairat@gmail.com