Enterprise Architecture for IT-Specialists & IT-Architects

Bc1014dd893a5888c57be34985c70906?s=47 Ahmad Gohar
October 17, 2017

Enterprise Architecture for IT-Specialists & IT-Architects

My Session at Java2Days 2017 @ Sofia, Bulgaria

https://2017.java2days.com/speaker/ahmad-gohar/

Bc1014dd893a5888c57be34985c70906?s=128

Ahmad Gohar

October 17, 2017
Tweet

Transcript

  1. 1.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Enterprise Architecture

    for IT-Specialists & IT-Architects Ahmad Gohar Solution Architect IBM WTC
  2. 2.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects About Me

    Ahmad Gohar Ahmad Gohar Architect @ IBM Architect @ IBM Experience: 11+ years Experience: 11+ years IBIM Certified Expert IT Specialist IBIM Certified Expert IT Specialist Certified Openroup Master IT Specialist Certified Openroup Master IT Specialist M. SC in IS MIBA M. SC in IS MIBA OCEJPA OCPWCD OCP PL/SQL MCP OCEJPA OCPWCD OCP PL/SQL MCP Email: ansgohar@gmail.com Twitter: @ansgohar
  3. 4.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects What is

    next? You’re about 7 to 9 year in IT… You’re about 7 to 9 year in IT… Suddenly mid career crisis hit you!!! Suddenly mid career crisis hit you!!! Do I want to stay technical? Do I want to stay technical? Do you want to move to Business or Management roles? Do you want to move to Business or Management roles? IT Admin IT Admin IT Support IT Support Designer Designer Developer Developer Technical Roles Technical Roles Should I become a Team Lead or Project Manager? Should I become a Team Lead or Project Manager? Should I become an Architect? Should I become an Architect?  Is Architect role right for me?  What types of architects are there?  What are the options?
  4. 5.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Architects Describes

    the processes the business uses to meet its goals. Describes how specific applications are designed and how they interact with each other. Describes how the enterprise datastores are organised and accessed. Describes the hardware and software infrastructure that supports applications and their interactions.
  5. 6.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Views, Viewpoints

    • Viewpoint: is a perspective (where you are looking from) and generally specific to a stakeholder group • View: is what you see and is created to ensure that particular stakeholders can see an architecture from a point of view which matches their concerns
  6. 8.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Application Architect

     Application architecture (includes layering – both physical & logical, interfaces with external systems, etc.)  High and low level design’s  Database Model & Design  Application architecture (includes layering – both physical & logical, interfaces with external systems, etc.)  High and low level design’s  Database Model & Design Understands Understands  Technical depth in one or two technologies  Requirements and Business Impact  Project Management  Resourcing  Scheduling  Timelines  Risk & Risk Mitigation  POC  Rapid Prototyping  Technical depth in one or two technologies  Requirements and Business Impact  Project Management  Resourcing  Scheduling  Timelines  Risk & Risk Mitigation  POC  Rapid Prototyping Application Architect, Software Architect, Technology Architect Application Architect, Software Architect, Technology Architect Role Role Overall application architecture and design. Overall application architecture and design. Owns Owns Works with Works with  Project Managers  Business Analyst’s  Designers  Developers  Testers  Infrastructure Architect  Project Managers  Business Analyst’s  Designers  Developers  Testers  Infrastructure Architect Looks up to Looks up to  Solution architect  Enterprise architect  Solution architect  Enterprise architect Defines Defines Defines Standards for  Application Design  UI  Coding  Coding Templates  Naming convention  Software Patterns  Security  etc Defines Standards for  Application Design  UI  Coding  Coding Templates  Naming convention  Software Patterns  Security  etc Produces Produces
  7. 9.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Infrastructure Architect

     Manages and maintains infrastructure Risk  High and low level design’s for all the infrastructure components  Works with OEM vendors to mange integration challenges and risk  Manages and maintains infrastructure Risk  High and low level design’s for all the infrastructure components  Works with OEM vendors to mange integration challenges and risk Understands Understands  Has good technical breath  Can work with heterogonous technologies  Resourcing  Scheduling  Timelines  Risk & Risk Mitigation  Has good technical breath  Can work with heterogonous technologies  Resourcing  Scheduling  Timelines  Risk & Risk Mitigation IT Architect, Systems Architect, Security Architect, Network Architect IT Architect, Systems Architect, Security Architect, Network Architect Role Role Overall infrastructure architecture and design with operational requirements. Overall infrastructure architecture and design with operational requirements. Owns Owns Works with Works with  Application Architects  Project Managers  Business Analyst’s  Designers  Testers  Application Architects  Project Managers  Business Analyst’s  Designers  Testers Looks up to Looks up to  Solution architect  Enterprise architect  Solution architect  Enterprise architect Defines Defines Defines Standards for  Infrastructure Design  Component level interfaces  Naming convention for servers, objects, …  Security  Monitoring  Management  etc Defines Standards for  Infrastructure Design  Component level interfaces  Naming convention for servers, objects, …  Security  Monitoring  Management  etc Produces Produces
  8. 10.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Solution Architect

     Solution architecture (includes hardware, software, applications, infrastructure, etc.)  Sizing & Capacity planning  Bill of Material & Pricing  Solution architecture (includes hardware, software, applications, infrastructure, etc.)  Sizing & Capacity planning  Bill of Material & Pricing Understands Understands  Technical depth in one or two technologies  Has good technical breath (both Applications & Infrastructure)  Can work with heterogonous technologies  Architectural Trade-Off Matrix  Technical depth in one or two technologies  Has good technical breath (both Applications & Infrastructure)  Can work with heterogonous technologies  Architectural Trade-Off Matrix Information Architect, Integration Architect, Data Architect, Service Architect, Cloud Architect Information Architect, Integration Architect, Data Architect, Service Architect, Cloud Architect Role Role Overall solution architecture and design. Overall solution architecture and design. Owns Owns Works with Works with  Project Managers  Business Analyst’s  Designers  Developers  Testers  Application Architects  Infrastructure Architects  Project Managers  Business Analyst’s  Designers  Developers  Testers  Application Architects  Infrastructure Architects Looks up to Looks up to  Enterprise architect  Enterprise architect Defines Defines Defines Standards for  Solution Design  Common UI for solution  Software & Integration Patterns  End to end Security  etc Defines Standards for  Solution Design  Common UI for solution  Software & Integration Patterns  End to end Security  etc Produces Produces
  9. 11.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Enterprise Architect

     Creates and runs “Architecture Review & Governance Board”  TCO planning and modeling  Application & infrastructure lifecycle management  Creates and runs “Architecture Review & Governance Board”  TCO planning and modeling  Application & infrastructure lifecycle management Understands Understands  Has good technical breath (Apps, Infra, network, etc)  Can work with heterogonous technologies  Understands the domain well  Regulatory compliance  Culture of the organization  Has good technical breath (Apps, Infra, network, etc)  Can work with heterogonous technologies  Understands the domain well  Regulatory compliance  Culture of the organization Business Architect, Strategic Architect, Chief Architect Business Architect, Strategic Architect, Chief Architect Role Role Overall organization architecture and design Overall organization architecture and design Owns Owns Works with Works with  Application Architects  Solution Architects  Infrastructure Architects  OEM vendors  Project Managers  Business Analyst’s  Application Architects  Solution Architects  Infrastructure Architects  OEM vendors  Project Managers  Business Analyst’s Looks up to Looks up to  CIO  CTO  Board  CIO  CTO  Board Defines Defines Defines Standards for  Application and infrastructure portfolio  TCO of IT  Common Looks and feel for solutions  Data Governance and Policies  DR & BCP  Compliance Fx  etc Defines Standards for  Application and infrastructure portfolio  TCO of IT  Common Looks and feel for solutions  Data Governance and Policies  DR & BCP  Compliance Fx  etc Produces Produces
  10. 12.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Technical Career

    Path Technical Roles Technical Roles Developers, Programmers, IT Administrators, IT Support, etc Developers, Programmers, IT Administrators, IT Support, etc Application Architect Application Architect Infrastructure Architect Infrastructure Architect Solutions Architect Solutions Architect Enterprise Architect Enterprise Architect CIO, CTO CIO, CTO Technical Business
  11. 14.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Every enterprise

    has an IT architecture Some are designed and some just happen
  12. 15.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects What we

    need to go EA! Knowledgeable and professional practitioners Knowledgeable and professional practitioners Support tools at all levels A good architecture framework Striving to achieve a total, practical, architectural solution
  13. 16.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects In a

    Nutshell Enterprise Architecture = Strategy + Business + Technology EA = S + B + T
  14. 17.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects A good

    IT architecture will: • Directly address the needs of the enterprise • React to change at the rate dictated by the enterprise’s markets • Be understood and supported by senior management • Clearly define the structure of the existing system • Provide a roadmap and migration strategy for future purchases / developments • Reduce the number and complexity of the interfaces between components, improving the ease of: • Application portability • Component upgrade • Component exchange • Component development and maintenance
  15. 20.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Pick a

    Framework EABOK EABOK GERAM GERAM IDEAS Group IDEAS Group RM-ODP a RM-ODP a ARCON ARCON TRAK TRAK MEGAF MEGAF Praxeme Praxeme GOD GOD SABSA SABSA Zachman Zachman SAP EA SAP EA ATOS CLEAR ATOS CLEAR DoDAF DoDAF MoDAF MoDAF NAF NAF AGATE AGATE NORA NORA NIST EA NIST EA DNDAF DNDAF IAF IAF TOGAF TOGAF LEAD LEAD IBM EA IBM EA
  16. 21.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects TOGAF Origins

    and Motivations A customer initiative: • Formal user requirement developed 1994 • Main themes: • A single, unifying Architectural Framework for the IT industry • A framework for developing architectures to meet specific business needs • not a “one-size-fits- all” architecture • Originally based on TAFIM (U.S. DoD)
  17. 22.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects History •

    Customer members demand architecture standards … • DoD Information Systems Agency (DISA) donate TAFIM as base • TOGAF first published • Customer members select TAFIM as preferred starting point… ‘93 • TOGAF 7 – Technical Edition ‘94 ‘96 ‘02 TOGAF 8 – Enterprise Edition First TOGAF Certification Program Launched • The Interoperable Enterprise Business Scenario first published ‘01 ‘03 ‘09 ‘06 TOGAF 8.1.1 TOGAF 9.1 ‘11
  18. 23.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Why TOGAF®

    ? Vendor, tool and technology neutral open standard Avoids re-inventing the wheel A comprehensive general method Widely adopted in the market Available under a free perpetual license Tailorable to meet an organization and industry needs Possible to participate in the evolution of the framework Business IT alignment Complementary to, not competing with, other frameworks
  19. 25.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects The Architecture

    Development Method The core of TOGAF A proven way of developing an architecture Specifically designed to address business requirements An iterative method A set of architecture views to ensure that a complex set of requirements are adequately addressed
  20. 26.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects ADM –

    Basic Principles • An iterative method, over the whole process, between phases and within phases • Each iteration = new decisions: • Enterprise coverage • Level of detail • Time horizon • Architecture asset re-use: • previous ADM iterations • other frameworks, system models, industry models,… • Decisions based on: • Competence / resource availability
  21. 27.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects ADM Phases

    Prepare the organization for a successful architecture project Ensure that every stage of a TOGAF project is based on and validates business requirements Set the scope, constraints and expectations for a TOGAF project; create the Architecture Vision; validate the business context; create the Statement of Architecture Work Develop Business Architecture Develop baseline and target architectures and analyze the gaps Develop Information Systems Architectures Develop baseline and target architectures and analyze the gaps Develop Technology Architecture Develop baseline and target architectures and analyze the gaps Perform initial implementation planning; identify major implementation projects Analyze costs, benefits and risks; develop detailed Implementation and Migration Plan Provide architectural oversight for the implementation; ensure that the implementation project conforms to the architecture Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise
  22. 29.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects ADM Guidelines

    and Techniques • The guidelines help to adapt the ADM to deal with different scenarios, including different process styles (e.g. the use of iteration) and also specific requirements (e.g. security). • The techniques support specific tasks within the ADM (e.g. defining principles, business scenarios, gap analysis, migration planning, risk management, etc).
  23. 33.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Architecture Content

    Framework • Provides a detailed model of • architectural work products, including Deliverables, Artifacts within deliverables, and the Architecture Building Blocks (ABBs) that deliverables represent. • It drives for greater consistency in the outputs of TOGAF • It provides a comprehensive checklist of architecture outputs • It promotes better integration of work products • It provides a detailed open standard for how architectures should be described • It includes a detailed metamodel
  24. 39.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects TOGAF® Reference

    Models Two Reference Models are provided • The TOGAF Technical Reference Model (TRM) • A Foundation Architecture • A model and a taxonomy of generic platform services • The Integrated Information Infrastructure Model (III- RM). • A model for business applications and infrastructure applications • Specifically aimed to support the vision of Boundaryless Information Flow™
  25. 44.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects ArchiMate Scope

    Idea Design Use Management Formal models Analysis Napkin Whiteboard Powerpoint Link with implementation Maintenance Version control Communication with stakeholders Visualisation Architecture process
  26. 45.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects ArchiMat Language

    ArchiMate language High-level modelling within a domain Modeling relations between domains Basis for visualizations Basis for analyses Relate to standards
  27. 46.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Layers &

    Aspects Technology Application Business Passive structure “object” Behaviour “verb” Active structure “subject” Processes Information Data Organisation Products & Services Applications Technical Infrastructure Business Functions
  28. 47.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Agility and

    Architecture Use agile development to get to a good architecture by appropriately applying suitable combinations of • Architectural Functions: • (such as communication, quality attributes, and design patterns) and • Architectural Skills at four points in the development life cycle. • (up-front planning, storyboarding, sprint, and working software)
  29. 50.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Complementary TOGAF

    9 Modeling languages and notation Framework, method and resources ITIL IT Service Management Best Practice COBIT Governance and control
  30. 51.

    Zachman Framework – overview Scope (Ballpark) view Owners View (Enterprise

    Model) Designers View (System Model) Builder’s View (Technology Model) Out of Context View (Detailed Model) Operational View (Functioning) Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why)
  31. 52.

    Zachman’s EA Framework 21 e.g. DATA ENTERPRISE ARCHITECTURE - A

    FRAMEWORK Builder SCOPE (CONTEXTUAL) MODEL (CONCEPTUAL) ENTERPRISE Designer SYSTEM MODEL (LOGICAL) TECHNOLOGY MODEL (PHYSICAL) DETAILED REPRESEN- TATIONS (OUT-OF- CONTEXT) Sub- Contractor FUNCTIONING ENTERPRISE DATA FUNCTION NETWORK e.g. Data Definition Ent = Field Reln = Address e.g. Physical Data Model Ent = Segment/Table/etc. Reln = Pointer/Key/etc. e.g. Logical Data Model Ent = Data Entity Reln = Data Relationship e.g. Semantic Model Ent = Business Entity Reln = Business Relationship List of Things Important to the Business ENTITY = Class of Business Thing List of Processes the Business Performs Function = Class of Business Process e.g. Application Architecture I/O = User Views Proc .= Application Function e.g. System Design I/O = Data Elements/Sets Proc.= Computer Function e.g. Program I/O = Control Block Proc.= Language Stmt e.g. FUNCTION e.g. Business Process Model Proc. = Business Process I/O = Business Resources List of Locations in which the Business Operates Node = Major Business Location e.g. Business Logistics System Node = Business Location Link = Business Linkage e.g. Distributed System Node = I/S Function (Processor, Storage, etc) Link = Line Characteristics e.g. Technology Architecture Node = Hardware/System Software Link = Line Specifications e.g. Network Architecture Node = Addresses Link = Protocols e.g. NETWORK Architecture Planner Owner ENTERPRISE MODEL (CONCEPTUAL) Designer SYSTEM MODEL (LOGICAL) TECHNOLOGY MODEL (PHYSICAL) DETAILED REPRESEN- TATIONS (OUT-OF CONTEXT) Contractor FUNCTIONING MOTIVATION PEOPLE e.g. Rule Specification End = Sub-condition Means = Step e.g. Rule Design End = Condition Means = Action e.g., Business Rule Model End = Structural Assertion Means =Action Assertion End = Business Objective Means = Business Strategy List of Business Goals/Strat Ends/Means=Major Bus. Goal/ Critical Success Factor List of Events Significant Time = Major Business Event e.g. Processing Structure Cycle = Processing Cycle Time = System Event e.g. Control Structure Cycle = Component Cycle Time = Execute e.g. Timing Definition Cycle = Machine Cycle Time = Interrupt e.g. SCHEDULE e.g. Master Schedule Time = Business Event Cycle = Business Cycle List of Organizations People = Major Organizations e.g. Work Flow Model People = Organization Unit Work = Work Product e.g. Human Interface People = Role Work = Deliverable e.g. Presentation Architecture People = User Work = Screen Format e.g. Security Architecture People = Identity Work = Job e.g. ORGANIZATION Planner to the Business Important to the Business What How Where Who When Why John A. Zachman, Zachman International (810) 231-0531 SCOPE (CONTEXTUAL) Architecture e.g. STRATEGY ENTERPRISE e.g. Business Plan TM View Aspects Viewpoints
  32. 54.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects Summry •

    TOGAF®, an Open Group Standard, is… • An effective, industry standard framework and method for enterprise architecture. • Complementary to, not competing with, other enterprise frameworks • A repository of best practice • Vendor, tool, and technology neutral • A framework and method for achieving the “Boundaryless Information Flow” vision
  33. 55.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects The Role

    of Enterprise Architect Mission Strategy Actions Vision Goals as is to be enterprise architecture domain/aspect architectures culture people leadership Operations … people processes IT products
  34. 56.

    Java2Days 2017 Enterprise Architecture for IT-Specialists & IT-Architects I’ve had

    lots of questions… What about your questions? @ansgohar