SlideShare a Scribd company logo

المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية

•
•
Egyptian Engineers Association
Egyptian Engineers Association

153 مبادرة #تواصل_تطوير المحاضرة ال 153 من المبادرة المهندس / محمد زكريا أخصائي البنية المؤسسية والاستراتيجية الرقمي بعنوان "مقدمة عن البنية المؤسسية" وذلك يوم الإثنين 21مارس 2022 الثامنة مساء توقيت القاهرة التاسعة مساء توقيت مكة المكرمة و الحضور عبر تطبيق زووم من خلال الرابط https://us02web.zoom.us/meeting/register/tZIqcu-spjoiH902NOccdtAoNJnGQ35joBnv علما ان هناك بث مباشر للمحاضرة على القنوات الخاصة بجمعية المهندسين المصريين ونأمل أن نوفق في تقديم ما ينفع المهندس ومهمة الهندسة في عالمنا العربي والله الموفق للتواصل مع إدارة المبادرة عبر قناة التليجرام https://t.me/EEAKSA ومتابعة المبادرة والبث المباشر عبر نوافذنا المختلفة رابط اللينكدان والمكتبة الالكترونية https://www.linkedin.com/company/eeaksa-egyptian-engineers-association/ رابط قناة التويتر https://twitter.com/eeaksa رابط قناة الفيسبوك https://www.facebook.com/EEAKSA رابط قناة اليوتيوب https://www.youtube.com/user/EEAchannal رابط التسجيل العام للمحاضرات https://forms.gle/vVmw7L187tiATRPw9 ملحوظة : توجد شهادات حضور مجانية لمن يسجل فى رابط التقيم اخر المحاضرة.

Engineering
1 of 250
Download to read offline
‫المؤسسية‬ ‫البنية‬ ‫عن‬ ‫مقدمة‬ ‫الطريق‬ ‫األمثل‬ ‫الرقمي‬ ‫التحول‬ ‫نحو‬
Enterprise Architecture let’s Play A Game !! | Most of agenda Items followed Togaf Standard 9.2 and tailored for presentation purposes to streamline understanding of EA Concepts 2
Agenda 3 ِ‫د‬ ْ ‫ش‬ُّ‫ر‬‫ال‬ ‫ى‬َ‫ل‬َ‫ع‬ َ‫ة‬َ‫يم‬ِ‫ز‬َ‫ع‬ْ‫ل‬‫ا‬َ‫و‬ ،ِ‫ر‬ ْ‫م‬َ ْ ‫األ‬ ‫ي‬ِ‫ف‬ َ ‫ات‬َ‫ب‬َّ‫ث‬‫ال‬ َ ‫ك‬ُ‫ل‬َ‫أ‬ ْ ‫س‬َ‫أ‬ ‫ي‬ ِّ‫ن‬ِ‫إ‬ َّ‫م‬ُ‫ه‬َّ‫ل‬‫ال‬ Overview – ‫عامة‬ ‫نظرة‬ Architecture Foundations – ‫المؤسسية‬ ‫البنية‬ ‫أساسيات‬ Architecture Method & Iterations – ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Guidelines and Techniques – ‫والتقنيات‬ ‫اإلرشادية‬ ‫القواعد‬ Architecture Governance – ‫البنية‬ ‫حوكمة‬ EA Office Setup Journey – ‫المؤسسية‬ ‫البنية‬ ‫مكتب‬ ‫إنشاء‬ ‫رحلة‬
1 Overview - ‫عامة‬ ‫نظرة‬ ▷Introduction ▷The Big Picture 4
Overview 1.1 Introduction 5
YOU MAY SETUP THE EMERGING TECHNOLOGIES , BUT WITHOUT ARCHITECTURE YOU STILL ..! Spaghetti Enterprise 6
IS THE BRIDGE BETWEEN STRATEGY FORMULATION AND EXECUTION ENTERPRISE ARCHITECTURE PRACTICES 7 FORMULATION EXECUTION
ENTERPRISE ARCHITECTURE ENABLES INTEGRATION OF VARIOUS TRANSFORMATION EFFORTS, FOSTER RESPONSIVE TO CHANGE IN BOTH CORPORATE STRATEGY AND OPERATING MODEL Business Transformation Pillars Enterprise Transformation Digital Transformation Technology Innovation IT Function Transformation Focuses on transforming the Operating Model of an enterprise Enabler of all other transformation types through Digitalization Focuses on customer facing areas of business and the extended enterprise How work gets done inside IT organization within an enterprise (Transform IT OM) EA 8
What is Enterprise Architecture ENTERPRISE ARCHITECTURE DEFINES THE STRUCTURE, OPERATION OF AN ORGANIZATION AND DETERMINE HOW IT CAN MOST EFFECTIVELY ACHIEVE ITS CURRENT AND FUTURE OBJECTIVES Enterprise Architecture Architecture Enterprise Architecture crosses multiple systems and multiple functional groups within the enterprise An enterprise could be: * A whole corporation / single division * Government agency / single department * A chain of geographically distant organizations linked together by common ownership * Groups of countries/ governments working together to create common or shareable deliverables or infrastructures * Partnership / alliances of businesses working together, such as a consortium or supply chain The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution The structure of components, their inter- relationships, and the principles and guidelines governing their design and evolution over time Reflect integration, standardization requirements of Enterprise Operating Model Any collection of organizations that has common goals Enterprise in EA, denote both an entire enterprise, encompassing all of its information systems, and a specific domain within the enterprise Extended enterprise frequently includes partners, suppliers, and customers. 9
EA Business Benefits ENTERPRISE ARCHITECTURE AIMS IS TO BUILD INTEGRATED ENVIRONMENT THAT IS RESPONSIVE TO CHANGE AND SUPPORTIVE OF THE DELIVERY OF THE BUSINESS STRATEGY Effective and efficient business operations Effective and efficient Digital Transformation and IT operations: Better return on existing investment, reduced risk for future investment Faster, simpler, and cheaper procurement 10 Agile Organization, shared business capacities, flexible workforce, lower change mgmt. cost, and Improved business productivity Lower software development, support, and maintenance costs, increased portability, Improved interoperability and address enterprise-wide issues Reduced complexity, Maximum ROI, flexible to make, buy, or out-source business and IT solutions and reduce overall risk Simpler buying decisions, maximizing procurement speed and flexibility without sacrificing architectural coherence and to secure economic capabilities
Architecture Framework AN ARCHITECTURE FRAMEWORK IS A FOUNDATIONAL STRUCTURE, OR SET OF STRUCTURES, THAT CAN BE USED FOR DEVELOPING A BROAD RANGE OF DIFFERENT ARCHITECTURES Architecture Framework Definition Architecture Framework Value Proposition Common Vocabulary Common Language & set of tools Simplify & Speedup Architecture Development Complete Coverage Ensure coverage of desired solution Future Growth Faster respond to future business needs (Responsive to change) Method Designing Enterprise Target state ( building blocks) Recommended standards Standards & compliant products Foundational Structure Foundational Structure used for developing range of different architectures A conceptual structure used to plan, develop, implement, govern, and sustain an architecture 11
Architecture Framework Structure ARCHITECTURE FRAMEWORK ENSURE THAT THE ARCHITECTURE SELECTED ALLOWS FOR FUTURE GROWTH IN RESPONSE TO THE NEEDS OF THE BUSINESS Consider Stakeholders Concerns Cover Stakeholder views and viewpoints Architecture Model The way to do architecture Cycle for develop architecture work Method Lego Box for your building blocks Classify your building blocks Categorization System How, with what you described architecture structure Start point to do EA in your enterprise Metamodel Architecture Model enrich the repos. consume the repos. to build viewpoints classify assets speak common lang. Iterative cycles 12
Various Frameworks Tailor Your Organizational Architecture Framework (Cook Book) Various Architecture Frameworks ARCHITECTURE FRAMEWORK SHOULD BE TAILORED TO MEET THE NEEDS OF THE ORGANIZATION http://www.iso-architecture.org/ieee-1471/afs/frameworks-table.html https://en.wikipedia.org/wiki/Enterprise_architecture_framework 13
Architecture Domains THEERE ARE FOUR COMMONLY ACCEPTED ARCHITECTURE DOMAINS AS SUBSETS OF AN OVERALL ENTERPRISE ARCHITECTURE 14 Business Architecture Data Architecture Technology Architecture Application Architecture ▪ Software and Hardware capabilities ▪ Help deployment of Business , application and data ▪ Includes ▪ IT infrastructure, middleware, ▪ Networks, communications, ▪ Processing, and standards. ▪ Structure of logical data assets ▪ Structure of physical data assets ▪ Data management resources. ▪ A blueprint of application ▪ Interaction to other applications ▪ Relationships to business processes ▪ Business strategy ▪ Governance ▪ Organization ▪ business processes ▪ People
Overview The Big Picture 1.2 15
ENTERPRISE ARCHITECTURE BIG PICTURE (aligned with Togaf 9.2) Consume building blocks (BB) Building Blocks Generate Building blocks (BB) Enterprise Continuum Guidelines and Techniques (Principles, Gap Analysis, CBP, Stakeholder Mgmt. ,…) Building Blocks Catalogs Matrices Diagrams Artifacts Architecture Development Method (ADM) Operating Model ( Governance Framework, Architecture Capability , Interaction Model, Architecture Compliance , Architecture Contracts, …) Architecture Metamodel Arch. Repository Management Deliverables Stakeholders, Views & Viewpoints Reference Models Ecosystem Tool Management 16
2 Architecture Foundations - ‫البنية‬ ‫أساسيات‬ ▷Stakeholders, Views and Viewpoints Basics (WHO,WHY) ▷Enterprise Continuum & Architecture Repository (WHERE) ▷Artifacts, Deliverables and Building Blocks (WHAT, HOW) 17
FOUNDATIONS 2.1 Stakeholders, Views & Viewpoints Basics ‫النظر‬ ‫ووجهات‬ ‫المنظور‬ ‫أساسيات‬ , ‫العالقة‬ ‫أصحاب‬ 18
Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 19
Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 20
EVERYTHING ABOUT ARCHITECTURE RELATES TO DEEPLY UNDERSTANDING OF TWO MAIN CONCEPTS (WHAT & HOW) What & How Concepts Differentiators (HOW) ‫كيف‬ - How do you visualize something ? / How can I do something ? - Differentiators point of views - i.e How I Make Coffee ? Building Blocks (WHAT) ‫ماذا‬ - Identify what you have ? - Basic unit (Building blocks ) from which something is built up. - i.e What I Have to Make Coffee ? 21
AS ENTERPRISE ARCHITECT, ECOSYSTEM/SYSTEM REPRESENT WHAT YOU SHOULD CONSIDER DURING YOUR ARCHITECTURE-RELATED ACTIVITIES AS “ A SCOPE OF ENTERPRISE IMPACTED” Ecosystem / System overview Ecosystem System is a combination of interacting elements organized to achieve one or more stated purposes Encompasses individual applications, systems in the traditional sense, subsystems, systems of systems, product lines, product families, whole enterprises, and other aggregations of interest System N Ecosystem go beyond organization boundary to include its environment industry (i.e. suppliers, distributors, customers, competitors, government agencies, and so on) Ecosystem network involved in the delivery of a specific product or service through both competition and cooperation 22
ECOSYSTEM / SYSTEM REAL EXAMPLE (1/2) Photosynthesis Ecosystem Ecosystem Plant Development System Photosynthesis Ecosystem 1 2 23
ECOSYSTEM / SYSTEM REAL EXAMPLE (2/2) Ant Colony Ecosystem Ecosystem Ant Colony System Ant Colony Ecosystem 1 2 24
EXTENDED ENTERPRISE SCOPE OF EXTENDED ENTERPRISE ENCOMPASSES BOTH ENTERPRISE SYSTEM AND ITS ECOSYSTEM … Enterprise / Extended Enterprise overview Any collection of organizations that has a common set of goals Large corporations may comprise multiple enterprises Enterprise Bigger umbrella care about its internal system as well as its ecosystem Comprises the partners, suppliers, and customers, as well as internal business units. ❖ Whole corporation, or division of a corporation ❖ Government agency or a single department; ❖ Chain of geographically distant organizations linked together by common ownership ❖ Groups of countries or governments working together to create common or shareable deliverables ❖ Partnerships and alliances of businesses working together, such as a consortium or supply chain ENTERPRISE 25
… TO PRESERVE ITS POSITION, ENTERPRISE SHOULD GUARANTEE ITS COMPETITIVE ADVANTAGES THROUGH EMPOWERING BOTH INTERNAL AND EXTERNAL PILLARS Connecting Dots Goals and values Resources and capabilities Structure & Systems Environment/Strategy Interface Firm/Strategy interface Strategy The Firm Enterprise (System) Environment Industry (Ecosystem) Customers Competitors Suppliers Partners Complementors 26
Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 27
STAKEHOLDERS ARE INDIVIDUALS, TEAMS, ORGANIZATIONS, OR CLASSES THEREOF, HAVING AN INTEREST IN A SYSTEM Stakeholders System 28
A SYSTEM HAS ONE OR MORE STAKEHOLDERS, EACH STAKEHOLDER TYPICALLY HAS ROLE, INTERESTS IN, OR CONCERNS RELATIVE TO, THAT SYSTEM Stakeholders for Enterprise Architecture 29 | Image Source: Togaf 9.2 Foundation Guide book – Typical set of stakeholders for EA
Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 30
INTERESTS IN A SYSTEM CAN BE RELEVANT TO ONE OR MORE OF ITS STAKEHOLDERS WHICH CAN BE FUTHER DECOMPOSED INTRO REQUIREMENTS Architecture Concern = Area of Interest Functionality Development Operations Acceptance Concerns related to any system aspects Performance Reliability Distribution Authorization Risk Audit Assurance … Agility Mobility … Coverage Usability Consistency … … … 31
Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 32
ARCHITECTURE VIEWPOINTS ESTABLISHES THE CONVENTIONS FOR CONSTRUCTING, INTERPRETING AND USING AN ARCHITECTURE VIEW TO ADDRESS CONCERN(S) ABOUT A SYSTEM-OF-INTEREST Viewpoints / Views What you see ? Where are you looking from ? Viewpoint ‫المنظور‬ View ‫النظر‬ ‫وجهات‬ - Representation of a system from the perspective of a related set of concerns - Visualized asset to inform stakeholders that their concerns are being met. - An architecture view is always specific to the architecture for which it is created. Instance of the completed template - Vantage point or perspective that determines what you see - Viewpoint defines the perspective from which an architecture view is taken. - The specification of the conventions for a particular kind of architecture view - Architecture viewpoints are generic, and can be stored in libraries for re-use, known as a viewpoint library. Template 33
VIEWPOINTS / VIEWS REAL EXAMPLES (1/4) Building Architecture VIEWPOINT VIEW 34
VIEWPOINTS / VIEWS REAL EXAMPLES (2/4) Scene Viewpoint & Camera View 35
VIEWPOINTS / VIEWS REAL EXAMPLES (3/4) Human Eye Retina Viewpoint Layers VIEWPOINT LAYERS (LIBRARY) LANSCAPE COMPLEX VIEW 36
VIEWPOINTS / VIEWS REAL EXAMPLES (4/4) Protractor Viewpoint (Contradicting Views) – No Cooperation 37
| Source: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap31.html EA FRAMEWORKS VIEWS / VIEWPOINTS (1/2) Togaf Standard Viewpoints 38
EA FRAMEWORKS VIEWS / VIEWPOINTS (2/2) Zachman Framework Viewpoints VIEWPOINT VIEW | Source: https://www.zachman.com/about-the-zachman-framework 39
FOUNDATIONS 2.2 Enterprise Continuum & Architecture Repository ‫المؤسسية‬ ‫البنية‬ ‫مستودع‬ ‫و‬ ‫التصنيف‬ ‫نظام‬ 40
Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 41
Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 42
WITHOUT DEFINING “A CLEAR CONTEXT”, PEOPLE DISCUSSING ARCHITECTURE CAN OFTEN TALK AT CROSS-PURPOSES (REFERENCING DIFFERENT POINTS AT THE SAME TIME) Classification System Unclassified Docs - Ad Hoc Store Games Classification of PS Store 1 2 43
THE ENTERPRISE CONTINUUM PROVIDES METHODS FOR CLASSIFYING ARCHITECTURE AND SOLUTION ARTIFACTS, BOTH INTERNAL AND EXTERNAL TO THE ARCHITECTURE REPOSITORY Views & Classification System Stakeholder Views of a System Architecture Domains Data Application Technology Business Security Strategy Business Finance BigData Data Mgmt. AI CyberSec. InfoSec. Foundation Extended Solution Architecture Generic Specific B D A T S B D A T S Foundation Common Sys. Industry Org. specific Classification System 44
Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 45
THE ENTERPRISE CONTINUUM CONSISTS OF THREE PARTS, EACH PART IS CONSIDERED TO BE A DISTINCT CONTINUUM Constituent Parts of the Enterprise Continuum (1/2) Enterprise Continuum Solution Continuum Architecture Continuum Outermost continuum and classifies assets related to the context of the overall Enterprise Architecture Classifies contextual assets used to develop architectures, such as policies, standards, strategic initiatives, organizational structures, and enterprise-level capabilities Consistent way to describe/ understand the implementation of the assets defined in the Architecture Continuum Defines what is available in the organizational environment as re- usable Solution Building Blocks (SBBs) Addresses the commonalities and differences among products, systems, and services of implemented systems Represents a structuring of Architecture Building Blocks (ABBs) which are re-usable architecture assets ABBs evolve through their development lifecycle from abstract/ generic entities to fully expressed Org- Specific Architecture assets Useful tool to discover commonality and eliminate unnecessary redundancy Guide specialized form 46
THE ENTERPRISE CONTINUUM CONSISTS OF THREE PARTS, EACH PART IS CONSIDERED TO BE A DISTINCT CONTINUUM Constituent Parts of the Enterprise Continuum (2/2) 47
THE ARCHITECTURE CONTINUUM SHOWS THE RELATIONSHIPS AMONG FOUNDATIONAL FRAMEWORKS, COMMON SYSTEMS, INDUSTRY, AND ENTERPRISE ARCHITECTURES … Architecture Continuum Specific Generic Solution Building Blocks SBBs B D A T S B D A T S Foundation Architecture Common Sys. Architecture Industry Architecture Org. specific Architecture Arch. Cont. Solu. Cont. Foundation Architecture Generic components, inter-relationships, principles, and guidelines that provide a foundation on which more specific architectures can be built Common Systems Architecture Use services in Foundation Architecture to create an architecture useful for building common Solutions (high reusable) across a wide number of relevant domains. Org-Specific Architecture Industry Architecture Describe and guide the final deployment of solution components for a particular enterprise Integration of common systems components with industry-specific components (certain vertical industries) 48
… THAT AIMS TO DISCOVER COMMONALITY AND ELIMINATE UNNECESSARY REDUNDANCY Architecture Continuum – Examples (1/2) - TRM (Technical Reference Model) - Specific Industry Architecture - e.g. Retail industry's "Active Store" architecture (SCOR- RM) - Energetics Oil and Gas data exchange standards - Bank X Architecture - Gov. Entity Y Architecture - Your Org. Architecture - SOA Architecture - ERP Architecture - Security Architecture - Network Architecture - Management Architecture - Operations Architecture - III-RM FA CSA IA OSA 49
SAMPLE COMMON SYSTEMS ARCHITECTURE – SOA REFERENCE MODEL Architecture Continuum – Examples (2/2) Related to BDAT Architecture Domains - Business Service - Data Service - Application Service - Infrastructure Service SOA is an architecture style for Enterprise Architecture 50
ALONGSIDE REQUIREMENTS AND PRINCIPLES, ARCHITECTURE CONTINUUM GUIDES, DIRECTS, AND SUPPORT SELECTION, REALIZATION AND DEVELOPMENT OF APPROPRIATE SOLUTIONS Architecture / Solution Continuum 51
THE SOLUTIONS CONTINUUM PROVIDES A CONSISTENT WAY TO DESCRIBE AND UNDERSTAND THE IMPLEMENTATION OF THE ASSETS DEFINED IN THE ARCHITECTURE CONTINUUM … Solution Continuum Foundation Solutions Highly generic concepts, tools, products, services, and solution components that are the fundamental providers of capabilities such as: - Professional services: training and consulting services - Support Services: Help Desk Common Systems Solutions - Implementation of a Common Systems Architecture and is comprised of a set of products and services. - Represent collections of common requirements and capabilities, rather than those specific to a particular customer or industry. Org-Specific Solutions Industry Solutions - Implementation of the Organization-Specific Architecture that provides the required business functions - Structured to support specific Service-Level Agreements (SLAs) to ensure support of the operational systems at desired service levels - Implementation of an Industry Architecture, which provides re-usable packages of common components and services specific to an industry. - Industry-specific, aggregate procurements that are ready to be tailored to an individual organization’s requirements Specific Generic Architecture Building Blocks ABBs Foundation Solutions Common Sys. Solutions Industry Solutions Org. specific Solutions Arch. Cont. Solu. Cont. B D A T S B D A T S 52
- Third-party solution with Specific Service-Level Agreements (SLAs) - key operating parameters and quality metrics to monitor and manage the organization environment - Specific products, services, and systems solutions that are appropriate to that industry - Physical database schema - An industry-specific point-of- service device … THROUGH DISCOVERTY OF WHAT IS AVAILABLE IN THE ORGANIZATIONAL ENVIRONMENT AS RE-USABLE SOLUTION BUILDING BLOCKS (SBBS) Solution Continuum – Examples - Programming languages - Foundational structures (EDI) - Generic Approaches to Organization structuring - Foundational structures for organizing IT operations (such as ITIL or the IT4IT RA) - Enterprise mgmt. sys. products - Security system products - Scalable data warehousing systems - “Software as a service” common apps solutions FS CSS IS OSS 53
Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 54
OPERATING A MATURE ARCHITECTURE CAPABILITY CREATES A HUGE VOLUME OF ARCHITECTURAL OUTPUT THAT EMPHASIZE THE ROLE OF EFFECTIVE MANAGEMENT … Architecture Repository Structure (1/2) 55
… TO OPERATE AND LEVERAGE THESE WORK PRODUCTS, A FORMAL TAXONOMY IS REQUIRED ALONGSIDE DEDICATED PROCESSES/TOOLS FOR ARCHITECTURAL CONTENT STORAGE Architecture Repository Structure (2/2) Architecture Metamodel Describes the organizationally tailored application of an architecture framework, including a method for architecture development and a metamodel for architecture content Architecture Capability Defines the parameters, structures, and processes that support governance of the Architecture Repository Architecture Landscape * presents an architectural representation of assets in use, or planned, by the enterprise at particular points in time Reference Library Governance Log Arch. Requirements Repository Solutions Landscape Standard Info. Base (SIB) * Provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise Provide a record of governance activity across the enterprise Provides a view of all authorized architecture requirements which have been agreed with the Architecture Board Presents an architectural representation of the SBBs supporting the Architecture Landscape which have been planned or deployed by the enterprise Captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization * Will be further detailed out in the next slides 56
DUE TO THE SHEER VOLUME AND THE DIVERSE STAKEHOLDER NEEDS THROUGHOUT AN ENTIRE ENTERPRISE, THE ARCHITECTURE LANDSCAPE IS DIVIDED INTO THREE LEVELS OF GRANULARITY Architecture Repository Structure - Architecture Landscape detailed view Strategic Architectures - Long-term summary view of the entire enterprise - Allow for direction setting at an executive level - Provide an organizing framework for operational and change activity Segment Architectures - More detailed operating models for areas within an enterprise - Can be used at the program or portfolio level - Organize and operationally align more detailed change activity Capability Architectures - Show in a more detailed fashion how the enterprise can support a particular unit of capability (overview about current/ target capability and capability increments) - Allow for individual work packages and projects to be grouped within managed portfolios and programs 57
DUE TO THE SHEER VOLUME AND THE DIVERSE STAKEHOLDER NEEDS THROUGHOUT AN ENTIRE ENTERPRISE, THE ARCHITECTURE LANDSCAPE IS DIVIDED INTO THREE LEVELS OF GRANULARITY Architecture Repository Structure - Architecture Landscape Example In Y 2000 Revenue 40M$ In Y 2001 Revenue 50M$ In Y 2002 Revenue 20M$ Why enterprise lose revenue ? Architecture models over time ( years) EA as strategic enabler , help business decisions Enterprise planning space where EA can add true value Business intelligence (Business Analytics) Stakeholder Leave Architecture Landscape Architecture Model 1 Architecture Model 2 Architecture Model 3 Capability Strategic Segmented 58
THE STANDARDS INFORMATION BASE IS A REPOSITORY AREA THAT HOLDS A RECORD OF THE SET OF SPECIFICATIONS, TO WHICH ARCHITECTURES MUST CONFORM Architecture Repository Structure - Standards Information Base detailed view Stated in a clear and unambiguous manner, so that compliance can be objectively assessed Easily accessible to projects and therefore the obligations of the project can be understood and planned for Basis for Architecture Governance Standards Information Base (SIB) Business Standards Application Standards Data Standards Technology Standards 59
Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 60
IMPLEMENTING THE ARCHITECTURE REPOSITORY IN A TOOL WILL CATER FOR STAKEHOLDER ENQUIRIES FOR MODELS, VIEWS, AND REQUIRED ANALYTICS FOR DECISION MAKING EA Tool - key benefits Promote RE-USE Facilitate easier maintenance of the architecture Provide stakeholders with relevant models Enable sharing of architecture information Ensure common terminology is used 61
EA Tool - key Features IMPLEMENTING THE ARCHITECTURE REPOSITORY IN A TOOL WILL CATER FOR STAKEHOLDER ENQUIRIES FOR MODELS, VIEWS, AND REQUIRED ANALYTICS FOR DECISION MAKING Impact Analysis Strategic dashboards Workflows Modeling & Heatmapping Dynamic Deliverables EA TOOL KEY FEATURES 62
ENTERPRISE ARCHITECTURE AND INNOVATION LEADERS SHOULD SELECT EA TOOLS THAT SUPPORT LONG-TERM BUSINESS TRANSFORMATION, MODERNIZATION AND INNOVATION GOALS EA Tools benchmarking 63 63
FOUNDATIONS 2.3 Artifacts, Deliverables and Building Blocks ‫العمل‬ ‫منتجات‬ , ‫المخرجات‬ ‫األساسية‬ ‫والمكونات‬ 64
Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 65
Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 66
Architecture Metamodel ARCHITECTURE METAMODEL OUTLINE HOW AND WITH WHAT THE ARCHITECTURE WILL BE DESCRIBED IN A STRUCTURED WAY TO ENSURE ENTERPIRSE-WIDE CONSISTENCY … Architecture Domains Data Application Technology Business Security Strategy Business Finance BigData Data Mgmt. AI CyberSec. InfoSec. Sample Stakeholders concern Areas Stakeholder Views of a System Phase I Phase II Initial Analysis Detailed Analysis 67 Tailored Metamodel Process
Architecture Metamodel … AND GUIDE ORGANIZATIONS TO IMPLEMENT THEIR ARCHITECTURE ASSETS WITHIN AN ARCHITECTURE TOOL Solution Architecture Generic Specific B D A T S B D A T S Foundation Common Sys. Industry Org. specific Tailored Metamodel Pillars Initial Analysis (Phase I) Metamodel Benchmarking Stakeholders Concerns Metamodel Attributes Metamodel Entities Metamodel Relationships Detailed Analysis (Phase II) 68
Tailor Architecture Framework ARCHITECTURE FRAMEWORKS PROVIDE SPECIALIZED METAMODEL, THE ROLE OF ARCHITECTURE PRACTITIONER IS TO TAILOR THESE METAMODEL FOR HIS ORGANIZATION PURPOSES 69
Togaf Metamodel ARCHITECTURE METAMODEL EXAMPLES (1/3) 70 | Image Source: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap30.html
ArchiMate Generic Metamodel ARCHITECTURE METAMODEL EXAMPLES (2/3) 71
Bizbok Metamodel ARCHITECTURE METAMODEL EXAMPLES (3/3) 72
Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 73
Architecture Deliverable DELIVERABLE IS A WORK PRODUCT THAT IS CONTRACTUALLY SPECIFIED AND IN TURN FORMALLY REVIEWED, AGREED, AND SIGNED OFF BY THE STAKEHOLDERS Stakeholder Views of a System ARCHITECTURE ARTIFACTS ARCHITECTURE DELIVERABLES Catalog Diagram Deliverable address stakeholders concerns Output of Architecture Iterations Architecture Development Iterations 74
Sample Architecture Deliverables A SET OF ARCHITECTURE DELIVERABLES WILL TYPICALLY BE CONSUMED AND PRODUCED ACROSS ITERATIVE ARCHITECTURE DEVELOPMENT CYCLES ARCHITECTURE DELIVERABLES Architecture Contract Architecture Principles Architecture Repository Architecture Requirements Specification Architecture Definition Document Architecture Roadmap Architecture Vision Business Principles, Business Goals, and Business Drivers Capability Assessment Change Request Communications Plan Compliance Assessment Implementation and Migration Plan Implementation Governance Model Organizational Model for Enterprise Architecture Request for Architecture Work Requirements Impact Assessment … and More Statement of Architecture Work Tailored Architecture Framework 75
Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 76
Architecture Artifact “ARTIFACT” IS AN ARCHITECTURAL WORK PRODUCT THAT DESCRIBES AN ASPECT OF THE ARCHITECTURE AND FORM THE CONTENT OF THE ARCHITECTURE REPOSITORY ARCHITECTURE ARTIFACTS Catalog Diagram 77
Togaf Artifacts TOGAF STANDARD DEFINE A SET OF ARTIFACTS ASSOCIATED WITH ARCHITECTURE METAMODEL … 78
Architecture Artifact & Architecture Deliverable … WHERE MULTIPLE ARTIFACTS MAY BE COMBINED TO FORM ARCHITECTURE DELIVERABLE 79
Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 80
Building blocks A BUILDING BLOCK REPRESENTS A (POTENTIALLY RE-USABLE) COMPONENT OF BUSINESS, IT, OR ARCHITECTURAL CAPABILITY … LEGO BUIDLING BLOCKS 81
Building blocks Interaction (1/2) … THAT CAN BE COMBINED WITH OTHER BUILDING BLOCKS TO DELIVER ARCHITECTURES AND SOLUTIONS Solution Building Blocks (SBBs) Arch. Building Blocks (ABBs) Describe Contains Many BB: Functionality package defined to meet the business needs Type Of ARCHITECTURE DELIVERABLE ARCHITECTURE ARTIFACTS STAKEHOLDERS CONCERNS CONTENT METAMODEL Classified as Consider implementation and usage, and evolves to exploit technology and standards May be assembled from other building blocks May be a subassembly of other building blocks Ideally re-usable and replaceable, and well specified Boundary and specification should be loosely coupled to its implementation CHARACTERISTICS Stored In ARCHTECTURE REPOSITORY 82
Building blocks Interaction (2/2) TOGAF STANDARDS VIEW OF INTERACTIONS BETWEEN METAMODEL, BUILDING BLOCKS, DIAGRAMS, AND STAKEHOLDERS 83
3 Architecture Method & Iterations ▷ADM Introduction ▷ADM Phases Kickstart ▷Scope Architecture Activity ▷Architecture Iteration ▷ADM Phases Deep Dive 84 - ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬
ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 85
ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 86
Architecture Development Method Introduction (1/3) THE ADM ENABLE THE ARCHITECTS TO ENSURE THAT A COMPLEX SET OF REQUIREMENTS IS ADEQUATELY ADDRESSED … 87
Architecture Development Method Introduction (2/3) THE ADM ENABLE THE ARCHITECTS TO ENSURE THAT A COMPLEX SET OF REQUIREMENTS IS ADEQUATELY ADDRESSED … Requirements Management Preliminary A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Consider assets produced from previous iterations of the process and external assets Building Blocks Building Blocks Architecture Iteration “SPRINT” Consume BB Publish BB Validation of results against the original requirements SCOPE “BDAT” DETAIL SEGEMENT SCHEDULES MILESTONES Validate BB, Artifacts, Deliverables 1 2 4 5 Produce BB 3 Reconsider … Repeatable process for developing Architectures 88
Architecture Development Method Introduction (3/3) … THROUGH ENABLEMENT OF CONTINUOUS ARCHITECTURE ITERATIONS Requirements Management Preliminary A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Cycling around the ADM Circular manner: completion of one phase of architecture work directly feeds into subsequent phases of architecture work Iterating between phases Across Phases: (e.g returning to Business Architecture on completion of Technology Architecture) Cycling around a single phase Repeated execution of the activities within a single ADM phase as a technique for elaborating architectural content Architecture Iteration Levels “SPRINT” 89
ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 90
Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary Phase Key Activities Establish Enterprise Architecture Operating Model (EAOM) (Capabilities, Processes, Interaction, Governance, Performance KPIs and Tools) Prepare, Initiate required activities to create Architecture Capability Identify the established frameworks, methods, and processes Define Architecture Principles Tailor Architecture Frameworks (Togaf, Nora, DoDAF, ..) ADM PHASES ACTIVITY KICKSTART (1/8) Preliminary 91
A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary Requirements Management Requirement Management ADM PHASES ACTIVITY KICKSTART (2/8) Key Activities Identify, stored, and fed architecture requirements into and out of relevant ADM phases Each state validate, address and prioritize requirements Requirement management is central to driving the ADM process 92
Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary A. Architecture Vision Phase A – Architecture Vision ADM PHASES ACTIVITY KICKSTART (3/8) Key Activities Set the scope, constraints, and expectations for architecture iterations Define Architecture Vision (Iteration, Partitioning) Identify stakeholders Validate the business context and create the Statement of Architecture Work. Obtain approvals 93
A. Architecture Vision E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary Requirements Management B. Business Architecture Phase B – Business Architecture ADM PHASES ACTIVITY KICKSTART (4/8) Key Activities Develop baseline architecture Develop target architecture (needs to operate > achieve business goals > respond to strategic drivers) Analyze gaps between target and baseline architecture Identify candidate Architecture Roadmap components C. Information Systems Architectures D. Technology Architecture 94
A. Architecture Vision F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions Phase E – Opportunities and solutions ADM PHASES ACTIVITY KICKSTART (5/8) Key Activities Perform initial implementation planning Identify delivery vehicles for architecture building blocks Determine Incremental Approach, Transition Architecture Solution Architect involved in this phase 95
E. Opportunities and solutions A. Architecture Vision G. Implementation Governance H. Architecture Change Mgmt. Preliminary Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture F. Migration Planning Phase F – Migration Planning ADM PHASES ACTIVITY KICKSTART (6/8) Key Activities Develop detailed Implementation and Migration Plan Address Transition Architecture and how to move from baseline to target architecture Overseed, and managed By Project Management Office (Portfolio, Program, Project) Include [cost , time , effort, quality, resource allocation , critical projects and Align other projects through various partitions (strategic , segmented , capability) 96
F. Migration Planning E. Opportunities and solutions A. Architecture Vision H. Architecture Change Mgmt. Preliminary Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture G. Implementation Governance Phase G – Implementation Governance ADM PHASES ACTIVITY KICKSTART (7/8) Key Activities Provide architectural oversight for the implementation Prepare and issue architecture contracts Handover your projects to be implemented by [internal dev team , vendor , outsource] Ensure Compliance architecture to our business [I Give you this > You deliver this > What is the gaps] Activate effective architecture governance bodies 97
F. Migration Planning E. Opportunities and solutions A. Architecture Vision Preliminary Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture G. Implementation Governance H. Architecture Change Mgmt. Phase H – Architecture Change Management ADM PHASES ACTIVITY KICKSTART (8/8) Key Activities Continual monitoring, Maintain architecture lifecycle Ensure that the Architecture Governance Framework is executed Ensure that the Enterprise Architecture Capability meets requirements, faster respond to the changing needs Maximize value of architecture practice to business 98
ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 99
Architecture Activity Scope Constraints THE SCOPE CHOSEN FOR THE ARCHITECTURE ACTIVITY IS NORMALLY DIRECTLY DEPENDENT ON AVAILABLE RESOURCES, AND, IN THE FINAL ANALYSIS, IS USUALLY A QUESTION OF FEASIBILITY Architecture Activity Constraints Stakeholders Concerns Design Authority Structure The objectives and stakeholder concerns to be addressed within the architecture Resources Availability The organizational authority of the team producing the architecture The availability of people, finance, and other resources 100
Architecture Activity Scope Dimensions THERE ARE FOUR DIMENSIONS IN WHICH THE SCOPE OF ARCHTIECTUE ACTIVITY MAY BE DEFINED AND LIMITED Breadth What is the full extent of the enterprise ? What part of that extent should the architecting effort deal with? Will the architecture cover suppliers, customers, and partners ? Depth To what level of detail should the architecting effort go? How much architecture is “enough”? What is the appropriate demarcation between the architecture effort and other, related activities (system design, system engineering, system development)? Architecture domains Due to resource and time constraints, There is not enough time, funding, or resources to build a top-down, all-inclusive architecture description encompassing all four architecture domains, so What are the architecture domains (BDAT) that initially should be covered ? Time period What is the time period needed to articulate Arch. Vision? Does it make sense (in terms of practicality and resources) for the same period to be covered in the detailed architecture description? If not, how many Transition Architectures are to be defined, and what are their time periods? Typically, the scope of an architecture is first expressed in terms of breadth, depth, and time. Once these dimensions are understood, a suitable combination of architecture domains can be selected that are appropriate to the problem being addressed Scope of Architecture Activity 101
ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 102
Architecture Iterations ARCHITECTURE ITERATION IS A TIMEBOX DURING WHICH ARCHITECTURE ACTIVITY TAKES PLACE STARTING WITH ARCHITECTURE VISION AND ENCOMPASS SELECTIVE CROSS-PHASES ACTIVITIES Requirements Management Preliminary A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning H. Implementation Governance H. Architecture Change Mgmt. Architecture Dev. Iteration Architecture Capability Iteration Architecture Governance Iteration Transition Planning Integration Architecture Iterations Architecture Capability Iterations support creation and evolution of the required Architecture Capability (initial mobilization, establishing or adjusting architecture approach, principles, scope, vision, and governance) Architecture Development Iterations allow the creation of architecture content by cycling through, or integrating, Business, Information Systems, and Technology Architecture phases Transition Planning Iterations support the creation of formal change roadmaps for a defined architecture Architecture Governance Iterations support governance of change activity progressing towards a defined Target Architecture 103
Baseline-first, Target-first Approaches ARCHITECTURE DEVELOPMENT ITERATION CAN FOLLOW EITHER BASELINE-FIRST OR TARGET-FIRST APPROACH TO IDENTIFY KEY ARCHITECTURE ASSETS IN “BDAT” DOMAINS Baseline-First Approach Target-First Approach 104
Architecture Dev. Iteration Typical Architecture Development Iteration ARCHITECTURE DEVELOPMENT ITERATION KEY ACTIVITIES ENCOMPASS COLLECTING KEY STAKEHOLDERS CONCERNS, DESIGN AS IS/TO BE ARCHITECTURE AND ANALYZE GAPS Preliminary E. Opportunities and solutions F. Migration Planning H. Implementation Governance H. Architecture Change Mgmt. Architecture Capability Iteration Architecture Governance Iteration Transition Planning Integration Architecture Development Iteration A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture Requirements Management Architecture Dev. Iteration Key Activities Define stakeholders view , viewpoints , concerns Utilize Reference model if exist , Building blocks if exist Design baseline “AS-IS” architecture according to vision scope Design target “TO-BE” architecture Identify GAP analysis between AS-IS and TO-BE 105
Typical Architecture Development Iteration HIGHER-LEVEL ARCHITECTURE USED TO GUIDE AND CONSTRAIN MORE DETAILED ARCHITECTURE, WHERE “MIGRATION PLANNING PHASE” CAN BE USED TO INITIATE NEW MORE DETAILED ARCHITECTURE PROJECTS Strategic Architecture Segment Architecture Capability Architecture 106
ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫مهنجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 107
DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary ADM Phases Deep Dive 108
Preliminary Phase Deep Dive PRELIMINARY PHASE AIMS TO PREPARE, INITIATE ACTIVITIES TO CREATE AN ARCHITECTURE CAPABILITY WITHIN THE ENTERPRISE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 109
PRELIMINARY PHASE CHARTER (1/2) 1. Defining the enterprise: Scope of the enterprise, define architecture stakeholders, appoint architecture project sponsor, ensure clear support from business management and involve stakeholders in defining, establishing and using the architecture capability. 2. Identifying key drivers review organizational context: understand the context surrounding the architecture including commercial model and budget, stakeholders, intention and organization culture, current processes, baseline architecture landscape, skills and capabilities of the enterprise 3. Defining the requirements for architecture work: business imperatives need to be articulated to identify key decision makers and stakeholders involved in defining and establishment of architecture capability including business requirements, cultural aspirations, organization intents, strategic intent and forecast financial requirements 4. Defining the Architecture Principles: definition of Architecture Principles is fundamental to the development of EA. Architecture work is informed by business principles as well as Architecture Principles • Determine the Architecture Capability desired by the organization: review organizational context for conducting EA, identify & Scope enterprise elements affected by architecture capability, identify established frameworks, methods and processes and establish capability maturity targets. • Establish the Architecture Capability: define, establish the organizational model for EA, establish architecture governance structure, interaction model and processes, select and impalement tools and define architecture principles • Prepare, initiate activities to create an Architecture Capability • Key activities: understand the business environment, ensure high-level management commitment, obtain agreement on scope, establish Architecture Principles, establish governance structure and customization of architecture framework Description Objectives Approach 110
PRELIMINARY PHASE CHARTER (2/2) 5. Defining the framework to be used: Tailoring architecture framework and enhance the operational capabilities of other frameworks in use within an organization. EA Team must be aware of the impact that the architecture has on the entire enterprise 6. Defining the relationships between management frameworks: Dependencies between various frameworks and business planning activities should be defined. EA can be used to provide a structure of the corporate initiatives. Management frameworks are required to complement each other and work in close harmony for the good of the enterprise. 7. Evaluating the Enterprise Architecture’s maturity: Capability Maturity Models (CMMs) are a good way of assessing the ability of an enterprise to exercise different capabilities. CMMs identify factors that is required to exercise a capability. Organization's ability to execute these factors measure the maturity of capabilities which gives executive insights into improving a capability • Determine the Architecture Capability desired by the organization: review organizational context for conducting EA, identify & Scope enterprise elements affected by architecture capability, identify established frameworks, methods and processes and establish capability maturity targets. • Establish the Architecture Capability: define, establish the organizational model for EA, establish architecture governance structure, interaction model and processes, select and impalement tools and define architecture principles • Prepare, initiate activities to create an Architecture Capability • Key activities: understand the business environment, ensure high-level management commitment, obtain agreement on scope, establish Architecture Principles, establish governance structure and customization of architecture framework Description Objectives Approach 111
Preliminary Phase Approach PRELIMINARY PHASE SUPPORTIVE ANALYSIS Management Frameworks to Coordinate with EA Framework Interoperability and Relationships between Management Frameworks 112
Architecture Vision Deep Dive ARCHITECTURE VISION ESTABLISHES ARCHITECTURE PROJECT AND INITIATES AN ADM ITERATION BY SETTING THE SCOPE, CONSTRAINTS, AND EXPECTATIONS FOR THE ITERATION ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 113
ARCHITECTURE VISION CHARTER (1/2) 1. Receive Request for Architecture Work: Sponsoring organization raise a request for architecture work for architecture team. EA Team ensure proper recognition and endorsement from corporate management, the support and commitment of line management for this evolution of the architecture iteration (ADM Cycle). 2. Creating the Architecture Vision: • Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture • Obtain approval for a Statement of Architecture Work: that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision • Establish architecture project and initiates an iteration of the Architecture Development Cycle, setting the scope, constraints, and expectations for the iteration • Create the Architecture Vision, validate the business context, and create the approved Statement of Architecture Work for each architecture cycle Description Objectives Approach • Verify and understand the documented business strategy and enterprise goals • Use business scenarios to discover and document business requirements, and to articulate Architecture Vision that responds to those requirements • Understand emerging technologies and their potential impact on industries and enterprises • Explore other domains appropriate for the Enterprise Architecture; e.g., information, security, digital, network mgmt. , services, cybersecurity • Provide a first-cut, high-level description of the Baseline and Target Architectures • Describe how new architecture iteration will meet the business goals and strategic objectives and address the stakeholder concerns when implemented • Use statement of architecture work to build stakeholders consensus (Architecture Governance) • Architecture sponsoring organization sign the Statement of Architecture work after stakeholders consensus 114
Architecture Vision Phase Approach ARCHITECTURE VISION SUPPORTIVE ANALYSIS Business Scenario can be used to identify business and architecture requirements 115
Architecture Vision Phase Approach ARCHITECTURE VISION SUPPORTIVE ANALYSIS Architecture vision deliverable content Problem description: Stakeholders and their concerns, List of issues/scenarios to be addressed and change drivers Detailed objectives that need to be fulfilled by the target architecture Use Business Scenario to articulate business emeratives draft necessary views for architecture definition document (ADD) high-level business and technology requirements that map onto the target architecture. Statement of architecture work deliverable content Architecture project request and background Architecture project description and scope Specific change of scope procedures Roles, responsibilities, deliverables, acceptance criteria and procedures Architecture project plan, schedule and approvals Overview and strategic alignment 116
Business Architecture BUSIENSS ARCHITECTURE PHASE AMINS TO DEVELOP BUSINESS ARCHITECTURE ASSETS TO SUPPORT AN AGREED ARCHITECTURE VISION ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 117
BUSINESS ARCHITECTURE PHASE CHARTER Developing the Baseline Description: Leverage input from Architecture vision to gather more information to develop business architecture artifacts using the following techniques: 1. Applying Business Capabilities : Business Capability Map is a self-contained view of the business that is independent of the current organizational structure, business processes, information systems and applications, and the rest of the product or service portfolio 2. Applying Value Streams: Value streams provide valuable stakeholder context into why the organization needs business capabilities, while business capabilities provide what the organization needs for a particular value stage to be successful 3. Applying the Organization Map: identities the business units or third parties that possess or use those capabilities and which participate in the value streams 4. Applying Modeling Techniques: other additional techniques may be used to enrich business architecture blueprints (i.e Business process models, use case models, …) 5. Using the Architecture Repository: consider what relevant Business Architecture resources are available from the Architecture Repository (i.e reference models and business artifacts and building blocks. • Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures • Develop Business Architecture assets to support an agreed Architecture Vision • Describes the fundamental organization of a business embodied in Its business process and people, their relationships to each other and the people, the principles governing its design and evolution and shows how an organization meets its business goals Description Objectives Approach 118
Business Architecture Overview Business Architecture Phase Approach BUSINESS ARCHITECTURE SUPPORTIVE ANALYSIS (1/3) 119 | Bizbok source: https://www.businessarchitectureguild.org/ Business Architecture Definition: A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders. Business Architecture & Other domain Architecture: A knowledge of the Business Architecture is a prerequisite for architecture work in any other domain (Data, Application, Technology), Therefore the first architecture activity that needs to be undertaken Business Architecture & Business Value: - Business Architecture is a means of demonstrating the business value of subsequent architecture work to key stakeholders - Business Architecture outline the return on investment to those stakeholders from supporting and participating in the subsequent work Stakeholders Strategies Policies Capabilities Value Streams Information organization Initiatives Products Metrics Business Architecture Domains
Business Architecture Phase Approach BUSINESS ARCHITECTURE SUPPORTIVE ANALYSIS (2/3) Applying Value Streams 120 Applying Business Capabilities Business Capability Map: provides a self-contained view of the business that is independent of the current organizational structure, business processes, information systems and applications, and the rest of the product or service portfolio Mapping to other Business views: Business capabilities should be mapped back to the organizational units, value streams, information systems, and strategic plans within the scope of the Enterprise Architecture project. Value streams: Provide valuable stakeholder context into why the organization needs business capabilities, while business capabilities provide what the organization needs for a particular value stage to be successful. Recommended Techniques: Mapping relationships between the stages in a value stream to business capabilities, and then performing a gap analysis for capabilities in the context of the business value achieved by the value stream for a specific stakeholder
Business Architecture Phase Approach BUSINESS ARCHITECTURE SUPPORTIVE ANALYSIS (3/3) Applying Business Modeling 121 Applying the Organization Map The Organization Map: Key element of Business Architecture - Provides organizational context for the whole Enterprise Architecture effort - Identities the business units or third parties that possess or use those capabilities and which participate in the value streams - Provides an understanding of which business units to involve in the architecture effort, who and when to talk about a given requirement, and how to measure the impact of various decisions The modeling and mapping techniques are extensions that implement the business capabilities, value streams, and organization maps Various modeling techniques may be employed when appropriate: Including Business process model, use case model and logical data model
Information Systems Architecture DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 122
INFORMATION SYSTEMS ARCHITECTURES PHASE CHARTER (1/2) 1. Key Considerations for the Data Architecture: • Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures • Documenting the Information Systems Architectures for an architecture project, including the development of Data and Application Architectures • Describes the major types of information and the application systems that process the information, and their relationships to each other and the environment Description Objectives Approach Data Management: - Defining application components which will serve as the system of record or reference for enterprise master data - Defining enterprise-wide standards that all application components, including software packages, need to adopt - Understanding how data entities are utilized by business functions, processes, and services - Understanding how and where enterprise data entities are created, stored, transported, and reported - Understanding the level and complexity of data transformations required to support the information exchange needs between applications - Defining the requirement for software in supporting data integration with the enterprise’s customers and suppliers (e.g. ETL tools) Data Governance: - Ensure that the enterprise has the necessary dimensions in place to enable the transformation - Structure: Does the enterprise have the necessary organizational structure and the standards bodies to manage data entity aspects of the transformation? - Management System: Does the enterprise have the necessary mgmt. system and data-related programs to manage governance aspects of data entities throughout its lifecycle? - People: What data-related skills and roles does the enterprise require for the transformation? 123
INFORMATION SYSTEMS ARCHITECTURES PHASE CHARTER (2/2) 1. Key Considerations for the Data Architecture: 2. Using the Architecture Repository: The architecture team should consider what relevant Data Architecture and Application Architecture resources are available in the organization’s Architecture Repository; in particular, generic models relevant to the organization’s industry “vertical” sector • Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures • Documenting the Information Systems Architectures for an architecture project, including the development of Data and Application Architectures • Describes the major types of information and the application systems that process the information, and their relationships to each other and the environment Description Objectives Approach Data Migration: - When an existing application is replaced, there will be a critical need to migrate data (master, transactional, and reference) to the new application - Identify data migration requirements and provide indicators for the level of transformation, and cleansing that will be required to present data in a format that meets the requirements and constraints of the target application - Ensure that the target application has quality data when it is populated - Ensure that an enterprise-wide common data definition is established to support the transformation 124
Technology Architecture DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 125
TECHNOLOGY ARCHITECTURE PHASE CHARTER 1. Emerging Technologies – A Driver for Change 2. Using the Architecture Repository: Consider what relevant Technology Architecture resources are available in the Architecture Repository including: • Develop the Target Technology Architecture that enables the Architecture Vision, target business, data, and application building blocks to be delivered through technology components and technology services, in a way that addresses the Statement of Architecture Work and stakeholder concerns • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures • Documenting the Technology Architecture for an architecture project, in the form of the fundamental organization of the IT systems • Embodied in the hardware, software, and communications technology and their relationships to each other and the environment • The principles governing its design and evolution Description Objectives Approach - Technology Architecture needs to capture the transformation opportunities available to the enterprise through the adoption of new technology - As more digital innovations reach the market, stakeholders need to both anticipate and be open to technology-driven change - Part of Digital Transformation has arisen due to convergence of telecommunications and computer capabilities, which have opened up new ways of implementing infrastructures - Technology change become a driver and strategic resource rather than a recipient of Change Requests - Technology Architecture may both drive business capabilities and respond to information system requirements at the same time - Existing IT services - The adopted technical reference model, if applicable - Generic technology models relevant to the organization's industry “vertical” sector; - Technology models relevant to Common Systems Architectures 126
Opportunities and Solutions DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 127
OPPORTUNITIES & SOLUTIONS PHASE CHARTER (1/2) Opportunities & Solutions Phase Concentrates on how to deliver the architecture • Takes into account the complete set of gaps between the Target and Baseline Architectures in all architecture domains • Logically groups changes into work packages within the enterprise’s portfolios • Build a best-fit roadmap that is based upon the stakeholder requirements, the enterprise’s business transformation readiness • Identified opportunities and solutions, and identified implementation constraints • Focus on the final target while realizing incremental business value • Initial step on the creation of a well considered Implementation and Migration Plan that is integrated into the enterprise’s portfolio in Migration Planning (Phase F) • Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D • Group changes into work packages, assess priorities and identify dependencies • Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value • Define the overall Solution Building Blocks (SBBs) to finalize the Target Architecture based on the Architecture Building Blocks (ABBs) • Decide on approach: Make versus buy versus re-use, Outsource, COTS, Open Source • First phase which is directly concerned with implementation • Describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture identified in previous phases • Perform initial implementation planning, Identify the major implementation projects Description Objectives Approach 128
OPPORTUNITIES & SOLUTIONS PHASE CHARTER (2/2) Four key concepts in the transition from developing to delivering a Target Architecture: Architecture Roadmap, Work Packages, Transition Architectures and Implementation and Migration Plan The Architecture Roadmap Transition Architecture Implementation and Migration Plan • Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D • Group changes into work packages, assess priorities and identify dependencies • Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value • Define the overall Solution Building Blocks (SBBs) to finalize the Target Architecture based on the Architecture Building Blocks (ABBs) • Decide on approach: Make versus buy versus re-use, Outsource, COTS, Open Source • First phase which is directly concerned with implementation • Describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture identified in previous phases • Perform initial implementation planning, Identify the major implementation projects Description Objectives Approach 129 • lists individual work packages in a timeline that will realize the Target Architecture • Each work package identifies a logical group of changes necessary to realize the Target Architecture • describes the enterprise at an architecturally significant state between the Baseline and Target Architectures • provide interim Target Architectures upon which the organization can converge • Provides a schedule of the projects that will realize the Target Architecture
Migration Planning DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 130
MIGRATION PLANNING PHASE CHARTER 1. Key Considerations for Phase F – Migration Planning: • Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan • Ensure that the Implementation and Migration Plan is coordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio • Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders • Addresses detailed migration planning that show how to move from the Baseline to the Target Architectures • Perform a cost/benefit analysis and a risk assessment for work packages and projects identified • Finalize a detailed Implementation and Migration Plan Description Objectives Approach - The focus of Migration Planning Phase is the Creation of an Implementation and Migration Plan in co-operation with the portfolio and project managers - Opportunities and solutions phase provides an incomplete Architecture Roadmap and Implementation and Migration Plan that address the Statement of Architecture Work - In Migration Planning, Roadmap and the Implementation and Migration Plan are integrated with the enterprise’s other change activity - Activities include assessing the dependencies, costs, and benefits of the various migration projects - The Architecture Roadmap, and Implementation and Migration Plan, from Phase E will form the basis of the detailed Implementation and Migration Plan that will include portfolio and project-level detail - The Architecture Development Cycle should then be completed, and lessons learned documented to enable continuous process improvement 131
Implementation Governance DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 132
IMPLEMENTATION GOVERNANCE PHASE CHARTER - All the information for successful management of the various implementation projects is brought together. The actual development occurs in parallel with implementation governance - Key Aspect of Phase G – Implementation Governance is ensuring compliance with the defined architecture(s), not only by the implementation projects, but also by other ongoing projects - The approach in Phase G is to: 1. Establish an implementation program that will enable the delivery of the agreed Transition Architectures 2. Adopt a phased deployment schedule that reflects the business priorities embodied in the Architecture Roadmap 3. Follow the organization’s standard for corporate, IT, and Architecture Governance 4. Use the organization’s established portfolio/program management approach, where this exists 5. Define an operations framework to ensure the effective long life of the deployed solution • Ensure conformance with the Target Architecture by implementation projects • Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests • Defines how the architecture constrains the implementation projects, monitors it while building it, and produces a signed Architecture Contract • Provide architectural oversight for the implementation • Govern and manage an Architecture Contract and monitor implementation work for conformance Description Objectives Approach 133
Architecture Change Management DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 134
ARCHITECTURE CHANGE MANAGEMENT PHASE CHARTER 1. The goal of an architecture change management process 2. The value and change management process, once established, will determine: • Ensure that the architecture lifecycle is maintained • Ensure that the Architecture Governance Framework is executed • Ensure that the enterprise’s Architecture Capability meets current requirements • Provide continual monitoring and a change management process and Monitor the business and capacity management • Ensure that changes to the architecture are managed in a cohesive and architected way (controlled manner) • Provide flexibility to evolve rapidly in response to changes in the technology or business environment Description Objectives Approach - Ensure that the architecture achieves its original target business value - Monitoring business growth and decline is a critical aspect of this phase - The circumstances under which the Architecture Development Cycle will be initiated to develop a new architecture and issue a request for architecture work - The circumstances under which the Enterprise Architecture, or parts of it, will be permitted to change after deployment, and the process by which that will happen 135
Architecture Change Management Phase Approach ARCHITECTURE CHANGE MANAGEMENT SUPPORTIVE ANALYSIS (1/2) Change Drivers Strategic, top-down directed change: to enhance or create new capability (capital) Bottom-up changes: to correct or enhance capability (operations and maintenance) for infrastructure under operations management Experiences with the previously delivered project increments in the care of operations management, but still being delivered by ongoing projects Change Classification Simplification change: Can normally be handled via change management techniques Driven By: reduce investment Requirement 1 Incremental change: May be handled by change mgmt. techniques or require partial re-architecting, depending on the nature of the change Driven By: derive additional value from existing investment 2 Re-architecting change: Requires putting the whole architecture through ADM Cycle again Driven By: increase investment to create new value for exploitation 3 136
Architecture Change Management Phase Approach ARCHITECTURE CHANGE MANAGEMENT SUPPORTIVE ANALYSIS (2/2) Change flow activities Guidelines for Maintenance versus Architecture Redesign REGISTER: All events that may impact the architecture ALLOCATE: Resource and management for architecture tasks ASSESS: What should be done leveraging these architecture resources EVALUATE: Architecture Change impact If the change impacts two stakeholders or more, then it is likely to require an architecture redesign and re-entry to the ADM If the change impacts only one stakeholder, then it is more likely to be a candidate for change management If the change can be allowed under a dispensation, then it is more likely to be a candidate for change management Significant impact for the business strategy – Re-architecting change A new technology/ standard emerges; refresh Tech. Architecture not all EA – Incremental change Change is at an infrastructure level (system reduced, change to 1 system, …) – Simplification change Examples: 137
Requirements Management DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 138
REQUIREMENTS MANAGEMENT PHASE CHARTER 1. Key Considerations for Requirements Phase: 2. Architecture Requirements Repository: should be used to record and manage all architecture requirements 3. Business scenarios technique can be used to: • Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases • Manage architecture requirements identified during any execution of the ADM cycle or a phase • Ensure that the relevant architecture requirements are available for use by each phase as the phase is executed • The Requirements Management process is a dynamic process, which addresses the identification of requirements for the enterprise, stores them, and then feeds them in and out of the relevant ADM phases • The ADM is continuously driven by the Requirements Management process Description Objectives Approach - The ability to deal with changes in requirements is crucial, as architecture by its nature deals with uncertainty and change, bridging the divide between the aspirations of the stakeholders and what can be delivered as a practical solution - Requirements Management manage the flow of the requirements : process itself does not dispose of, address, or prioritize any requirements; this is done within the relevant phase of the ADM - Discover and document business requirements, - Describe an Architecture Vision that responds to those requirements 139
4 Guidelines and Techniques ▷Introduction ▷Guidelines ▷Techniques 140 ‫والتقنيات‬ ‫اإلرشادية‬ ‫القواعد‬ -
Guidelines & Techniques EA with Specific Architecture Style ‫البنية‬ ‫طراز‬ Architecture principles ‫البنية‬ ‫مبادئ‬ Business Scenarios ‫األعمال‬ ‫سيناريوهات‬ Gap Analysis ‫الفجوات‬ ‫تحليل‬ Business Transformation Readiness Assessment ‫األعمال‬ ‫تحول‬ ‫جاهزية‬ ‫تقييم‬ Risk Management ‫المخاطر‬ ‫إدارة‬ Capability-Based Planning ‫بالقدرة‬ ‫التخطيط‬ Interoperability ‫التوافقية‬ 141
Guidelines and Techniques GUIDELINES AND TECHNIQUES CONTAINS A COLLECTION OF GUIDELINES AND TECHNIQUES FOR USE IN ADAPTING AND APPLYING THE ARCHITECTURE ITERATION How to adapt the Architecture method to deal with a number of usage scenarios Examples : - Apply iteration to the Architecture method - Applying Architecture method at different levels of the enterprise ( strategic, segment, capability) - Use the architecture framework with different architectural styles (i.e. SOA, Risk & Security)* Support specific tasks within the Architecture method Examples : - Architecture Principles* - Stakeholder Management - Architecture Patterns - Gap Analysis* - Migration Planning Techniques - Interoperability Requirements* - Business Transformation Readiness Assessment* - Risk Management* - Capability-Based Planning* Guidelines Techniques * Selected guidelines and techniques to be detailed out in the following section 142
Guidelines & Techniques Architecture principles ‫البنية‬ ‫مبادئ‬ Business Scenarios ‫األعمال‬ ‫سيناريوهات‬ Gap Analysis ‫الفجوات‬ ‫تحليل‬ Business Transformation Readiness Assessment ‫األعمال‬ ‫تحول‬ ‫جاهزية‬ ‫تقييم‬ Risk Management ‫المخاطر‬ ‫إدارة‬ Capability-Based Planning ‫بالقدرة‬ ‫التخطيط‬ Interoperability ‫التوافقية‬ EA with Specific Architecture Style ‫البنية‬ ‫طراز‬ 143
Architecture Style: The combination of distinctive features related to the specific context within which architecture is performed or expressed; A collection of principles and characteristics that steer or constrain how an architecture is formed. Distinctive features for SOA services: Architecture Style – SOA ARCHITECTURE FRAMEWORK SHOULD BE FLEXIBLE AND BE READILY ADAPT TO VARIOUS ARCHITECTURAL STYLES Service Design Mirror real-world business activities – comprising the enterprise (or inter- enterprise) business processes Service representation utilizes business descriptions to provide context (i.e., business process, goal, rule, policy, service interface, and service component) Service Implementation SOA implements services using orchestration Pattern Infrastructure Requirements Recommend service implementation use open standards to realize interoperability and location transparency Environment-specific Implementation Services are constrained or enabled by context and must be described within that context SOA Reference Architecture The Distinctive Features Of An Architecture Style Must Be Identified And considered While Architecture Development 144
Architecture Style and ADM ADDRESSING A DISTINCTIVE STYLE SHOULD NOT CALL FOR SIGNIFICANT CHANGES TO THE ARCHITECTURE FRAMEWORK; INSTEAD IT SHOULD ADJUST THE MODELS, VIEWPOINTS, AND TOOLS Requirements Management Preliminary A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning H. Implementation Governance H. Architecture Change Mgmt. Preliminary Phase Phase B,C,D Addressing the distinctive features will usually include extensions to the Architecture Content Metamodel and the use of specific notation or modeling techniques and the identification of viewpoints Architecture Metamodel Architecture Tool Select the relevant architecture resources, including models, viewpoints, and tools, to properly describe the architecture domain and demonstrate that stakeholder concerns are addressed Architecture Definition Document 145
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية
المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية

Recommended

كيفية قياس البنية المؤسسية
كيفية قياس البنية المؤسسيةكيفية قياس البنية المؤسسية
كيفية قياس البنية المؤسسية
Edarat Group
 
TOGAF 9.2 - ADM - Preliminary Phase
TOGAF 9.2 - ADM - Preliminary PhaseTOGAF 9.2 - ADM - Preliminary Phase
TOGAF 9.2 - ADM - Preliminary Phase
ManishMeshram18
 
الهيكلية المؤسسية الوطنية
الهيكلية المؤسسية الوطنيةالهيكلية المؤسسية الوطنية
الهيكلية المؤسسية الوطنية
YesserProgram
 
Enterprise architecture
Enterprise architectureEnterprise architecture
Enterprise architecture
Samah SAFI, MBA
 
Togaf introduction and core concepts
Togaf introduction and core conceptsTogaf introduction and core concepts
Togaf introduction and core concepts
Paul Sullivan
 
TOGAF
TOGAFTOGAF
TOGAF
Ahmed Gamil
 
TOGAF Certification
TOGAF Certification TOGAF Certification
TOGAF Certification
Miguel Vilaca
 
Togaf 9 an introduction
Togaf 9 an introductionTogaf 9 an introduction
Togaf 9 an introduction
Daan Bakboord
 

Recommended

كيفية قياس البنية المؤسسية
كيفية قياس البنية المؤسسيةكيفية قياس البنية المؤسسية
كيفية قياس البنية المؤسسية
Edarat Group
 
TOGAF 9.2 - ADM - Preliminary Phase
TOGAF 9.2 - ADM - Preliminary PhaseTOGAF 9.2 - ADM - Preliminary Phase
TOGAF 9.2 - ADM - Preliminary Phase
ManishMeshram18
 
الهيكلية المؤسسية الوطنية
الهيكلية المؤسسية الوطنيةالهيكلية المؤسسية الوطنية
الهيكلية المؤسسية الوطنية
YesserProgram
 
Enterprise architecture
Enterprise architectureEnterprise architecture
Enterprise architecture
Samah SAFI, MBA
 
Togaf introduction and core concepts
Togaf introduction and core conceptsTogaf introduction and core concepts
Togaf introduction and core concepts
Paul Sullivan
 
TOGAF
TOGAFTOGAF
TOGAF
Ahmed Gamil
 
TOGAF Certification
TOGAF Certification TOGAF Certification
TOGAF Certification
Miguel Vilaca
 
Togaf 9 an introduction
Togaf 9 an introductionTogaf 9 an introduction
Togaf 9 an introduction
Daan Bakboord
 
Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)Nathaniel Palmer
 
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
Daljit Banger
 
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
Chandrashekhar More
 
Togaf 9.2 Introduction
Togaf 9.2 IntroductionTogaf 9.2 Introduction
Togaf 9.2 Introduction
Mohamed Zakarya Abdelgawad
 
TOGAF Introduction
TOGAF IntroductionTOGAF Introduction
TOGAF Introduction
Ali Akbar
 
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...johnpolgreen
 
TOGAF 9.2 - Transforming Business
TOGAF 9.2 - Transforming BusinessTOGAF 9.2 - Transforming Business
TOGAF 9.2 - Transforming Business
Real IRM
 
Center of Excellence Building Blocks
Center of Excellence Building BlocksCenter of Excellence Building Blocks
Center of Excellence Building Blocks
Arup Dutta
 
IT4IT - The Full Story for Digital Transformation - Part 1
IT4IT - The Full Story for Digital Transformation - Part 1IT4IT - The Full Story for Digital Transformation - Part 1
IT4IT - The Full Story for Digital Transformation - Part 1
Mohamed Zakarya Abdelgawad
 
TOGAF ADM cycle
TOGAF ADM cycleTOGAF ADM cycle
TOGAF ADM cycle
Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW
 
Implementing Effective Enterprise Architecture
Implementing Effective Enterprise ArchitectureImplementing Effective Enterprise Architecture
Implementing Effective Enterprise Architecture
Leo Shuster
 
Организационная Архитектура EA Enterprise Architecture
Организационная Архитектура EA Enterprise ArchitectureОрганизационная Архитектура EA Enterprise Architecture
Организационная Архитектура EA Enterprise Architecture
TOR
 
Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2
Jean Gehring
 
Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!
Sam Mandebvu
 
Practical Enterprise Architecture in Medium-size Corporation using TOGAF
Practical Enterprise Architecture in Medium-size Corporation using TOGAFPractical Enterprise Architecture in Medium-size Corporation using TOGAF
Practical Enterprise Architecture in Medium-size Corporation using TOGAF
Michael Sukachev
 
Business Architecture Explained
Business Architecture ExplainedBusiness Architecture Explained
Business Architecture Explained
aaronwilliamson
 
البنية المؤسسية الوطنية
البنية المؤسسية الوطنيةالبنية المؤسسية الوطنية
البنية المؤسسية الوطنية
YesserProgram
 
TOGAF in 8 Steps
TOGAF in 8 StepsTOGAF in 8 Steps
TOGAF in 8 Steps
Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW
 
How to establish Enterprise Architecture in large organisations using TOGAF
How to establish Enterprise Architecture in large organisations using TOGAFHow to establish Enterprise Architecture in large organisations using TOGAF
How to establish Enterprise Architecture in large organisations using TOGAF
Nemanja Kostic
 
Business Architecture Foundations
Business Architecture FoundationsBusiness Architecture Foundations
Business Architecture Foundations
Mohamed Zakarya Abdelgawad
 
The Role Of The Architect In Turbulent Times
The Role Of The Architect In Turbulent TimesThe Role Of The Architect In Turbulent Times
The Role Of The Architect In Turbulent Times
David Chou
 
Enterprise Architecture
Enterprise ArchitectureEnterprise Architecture
Enterprise Architecture
Vikas Grover
 

More Related Content

What's hot

Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)Nathaniel Palmer
 
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
Daljit Banger
 
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
Chandrashekhar More
 
Togaf 9.2 Introduction
Togaf 9.2 IntroductionTogaf 9.2 Introduction
Togaf 9.2 Introduction
Mohamed Zakarya Abdelgawad
 
TOGAF Introduction
TOGAF IntroductionTOGAF Introduction
TOGAF Introduction
Ali Akbar
 
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...johnpolgreen
 
TOGAF 9.2 - Transforming Business
TOGAF 9.2 - Transforming BusinessTOGAF 9.2 - Transforming Business
TOGAF 9.2 - Transforming Business
Real IRM
 
Center of Excellence Building Blocks
Center of Excellence Building BlocksCenter of Excellence Building Blocks
Center of Excellence Building Blocks
Arup Dutta
 
IT4IT - The Full Story for Digital Transformation - Part 1
IT4IT - The Full Story for Digital Transformation - Part 1IT4IT - The Full Story for Digital Transformation - Part 1
IT4IT - The Full Story for Digital Transformation - Part 1
Mohamed Zakarya Abdelgawad
 
TOGAF ADM cycle
TOGAF ADM cycleTOGAF ADM cycle
TOGAF ADM cycle
Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW
 
Implementing Effective Enterprise Architecture
Implementing Effective Enterprise ArchitectureImplementing Effective Enterprise Architecture
Implementing Effective Enterprise Architecture
Leo Shuster
 
Организационная Архитектура EA Enterprise Architecture
Организационная Архитектура EA Enterprise ArchitectureОрганизационная Архитектура EA Enterprise Architecture
Организационная Архитектура EA Enterprise Architecture
TOR
 
Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2
Jean Gehring
 
Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!
Sam Mandebvu
 
Practical Enterprise Architecture in Medium-size Corporation using TOGAF
Practical Enterprise Architecture in Medium-size Corporation using TOGAFPractical Enterprise Architecture in Medium-size Corporation using TOGAF
Practical Enterprise Architecture in Medium-size Corporation using TOGAF
Michael Sukachev
 
Business Architecture Explained
Business Architecture ExplainedBusiness Architecture Explained
Business Architecture Explained
aaronwilliamson
 
البنية المؤسسية الوطنية
البنية المؤسسية الوطنيةالبنية المؤسسية الوطنية
البنية المؤسسية الوطنية
YesserProgram
 
How to establish Enterprise Architecture in large organisations using TOGAF
How to establish Enterprise Architecture in large organisations using TOGAFHow to establish Enterprise Architecture in large organisations using TOGAF
How to establish Enterprise Architecture in large organisations using TOGAF
Nemanja Kostic
 
Business Architecture Foundations
Business Architecture FoundationsBusiness Architecture Foundations
Business Architecture Foundations
Mohamed Zakarya Abdelgawad
 

What's hot (20)

Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)
 
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
A Day in the Life of an Enterprise Architect (Role Play Exercise) 2016
 
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
Enterprise Architecture using TOGAF 's ADM - Architecture Delivery Method (...
 
Togaf 9.2 Introduction
Togaf 9.2 IntroductionTogaf 9.2 Introduction
Togaf 9.2 Introduction
 
TOGAF Introduction
TOGAF IntroductionTOGAF Introduction
TOGAF Introduction
 
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...
Using togaf™ in government_enterprise_architecture_to_describe_the_it_archite...
 
TOGAF 9.2 - Transforming Business
TOGAF 9.2 - Transforming BusinessTOGAF 9.2 - Transforming Business
TOGAF 9.2 - Transforming Business
 
Center of Excellence Building Blocks
Center of Excellence Building BlocksCenter of Excellence Building Blocks
Center of Excellence Building Blocks
 
IT4IT - The Full Story for Digital Transformation - Part 1
IT4IT - The Full Story for Digital Transformation - Part 1IT4IT - The Full Story for Digital Transformation - Part 1
IT4IT - The Full Story for Digital Transformation - Part 1
 
TOGAF ADM cycle
TOGAF ADM cycleTOGAF ADM cycle
TOGAF ADM cycle
 
Implementing Effective Enterprise Architecture
Implementing Effective Enterprise ArchitectureImplementing Effective Enterprise Architecture
Implementing Effective Enterprise Architecture
 
Организационная Архитектура EA Enterprise Architecture
Организационная Архитектура EA Enterprise ArchitectureОрганизационная Архитектура EA Enterprise Architecture
Организационная Архитектура EA Enterprise Architecture
 
Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2
 
Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!
 
Practical Enterprise Architecture in Medium-size Corporation using TOGAF
Practical Enterprise Architecture in Medium-size Corporation using TOGAFPractical Enterprise Architecture in Medium-size Corporation using TOGAF
Practical Enterprise Architecture in Medium-size Corporation using TOGAF
 
Business Architecture Explained
Business Architecture ExplainedBusiness Architecture Explained
Business Architecture Explained
 
البنية المؤسسية الوطنية
البنية المؤسسية الوطنيةالبنية المؤسسية الوطنية
البنية المؤسسية الوطنية
 
TOGAF in 8 Steps
TOGAF in 8 StepsTOGAF in 8 Steps
TOGAF in 8 Steps
 
How to establish Enterprise Architecture in large organisations using TOGAF
How to establish Enterprise Architecture in large organisations using TOGAFHow to establish Enterprise Architecture in large organisations using TOGAF
How to establish Enterprise Architecture in large organisations using TOGAF
 
Business Architecture Foundations
Business Architecture FoundationsBusiness Architecture Foundations
Business Architecture Foundations
 

Similar to المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية

The Role Of The Architect In Turbulent Times
The Role Of The Architect In Turbulent TimesThe Role Of The Architect In Turbulent Times
The Role Of The Architect In Turbulent Times
David Chou
 
Enterprise Architecture
Enterprise ArchitectureEnterprise Architecture
Enterprise Architecture
Vikas Grover
 
Hk yeditepe university-systemsengg-seminar-102012
Hk yeditepe university-systemsengg-seminar-102012Hk yeditepe university-systemsengg-seminar-102012
Hk yeditepe university-systemsengg-seminar-102012Hakan KIRAN
 
Togaf
TogafTogaf
Togaf
Anjani Kumar
 
Architecture Series 5-1 EA As Corporate Strategy Introduction
Architecture Series 5-1 EA As Corporate Strategy IntroductionArchitecture Series 5-1 EA As Corporate Strategy Introduction
Architecture Series 5-1 EA As Corporate Strategy Introduction
Frankie Hsiang
 
Enterprise Architecture and TOGAF, Quick Look
Enterprise Architecture and TOGAF, Quick LookEnterprise Architecture and TOGAF, Quick Look
Enterprise Architecture and TOGAF, Quick Look
Sukru Kocakaya
 
Week 2-What is Enterprise Architecure (1).pptx
Week 2-What is Enterprise Architecure (1).pptxWeek 2-What is Enterprise Architecure (1).pptx
Week 2-What is Enterprise Architecure (1).pptx
RizalPrambudi3
 
A Method To Define An Enterprise Architecture Using The Zachman Framework
A Method To Define An Enterprise Architecture Using The Zachman FrameworkA Method To Define An Enterprise Architecture Using The Zachman Framework
A Method To Define An Enterprise Architecture Using The Zachman Framework
Kim Daniels
 
Enterprise Architecture Tools By Eacomposer
Enterprise Architecture Tools By EacomposerEnterprise Architecture Tools By Eacomposer
Enterprise Architecture Tools By Eacomposer
eacomposer
 
Enterprise architecture assessment guide v2.2
Enterprise architecture assessment guide v2.2Enterprise architecture assessment guide v2.2
Enterprise architecture assessment guide v2.2
Dania Abdel-aziz
 
Websphere Business Integration
Websphere Business IntegrationWebsphere Business Integration
Websphere Business Integration
Schubert Gomes
 
B140815
B140815B140815
B140815irjes
 
Max Poliashenko - Enterprise Product Architecture
Max Poliashenko - Enterprise Product ArchitectureMax Poliashenko - Enterprise Product Architecture
Max Poliashenko - Enterprise Product Architecture
iasaglobal
 
Enterprise Architecture Framework Paper
Enterprise Architecture Framework PaperEnterprise Architecture Framework Paper
Enterprise Architecture Framework Paper
Laura Benitez
 
Building An Information Technology And Information Systems
Building An Information Technology And Information SystemsBuilding An Information Technology And Information Systems
Building An Information Technology And Information Systems
Nicole Savoie
 
A framework for_enterprise_architecture_effectiveness
A framework for_enterprise_architecture_effectivenessA framework for_enterprise_architecture_effectiveness
A framework for_enterprise_architecture_effectivenessbambangpadhi
 
Delivering enterprise architecture
Delivering enterprise architectureDelivering enterprise architecture
Delivering enterprise architecture
Bas van Gils
 
Enterprise Architecture Approach Togaf 9
Enterprise Architecture Approach Togaf 9Enterprise Architecture Approach Togaf 9
Enterprise Architecture Approach Togaf 9Prashant Patade
 
ICT in BUSINESS_071619_06185majesty2.pptx
ICT in BUSINESS_071619_06185majesty2.pptxICT in BUSINESS_071619_06185majesty2.pptx
ICT in BUSINESS_071619_06185majesty2.pptx
anaba2926
 

Similar to المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية (20)

The Role Of The Architect In Turbulent Times
The Role Of The Architect In Turbulent TimesThe Role Of The Architect In Turbulent Times
The Role Of The Architect In Turbulent Times
 
Enterprise Architecture
Enterprise ArchitectureEnterprise Architecture
Enterprise Architecture
 
Hk yeditepe university-systemsengg-seminar-102012
Hk yeditepe university-systemsengg-seminar-102012Hk yeditepe university-systemsengg-seminar-102012
Hk yeditepe university-systemsengg-seminar-102012
 
Togaf
TogafTogaf
Togaf
 
Architecture Series 5-1 EA As Corporate Strategy Introduction
Architecture Series 5-1 EA As Corporate Strategy IntroductionArchitecture Series 5-1 EA As Corporate Strategy Introduction
Architecture Series 5-1 EA As Corporate Strategy Introduction
 
Enterprise Architecture and TOGAF, Quick Look
Enterprise Architecture and TOGAF, Quick LookEnterprise Architecture and TOGAF, Quick Look
Enterprise Architecture and TOGAF, Quick Look
 
Week 2-What is Enterprise Architecure (1).pptx
Week 2-What is Enterprise Architecure (1).pptxWeek 2-What is Enterprise Architecure (1).pptx
Week 2-What is Enterprise Architecure (1).pptx
 
A Method To Define An Enterprise Architecture Using The Zachman Framework
A Method To Define An Enterprise Architecture Using The Zachman FrameworkA Method To Define An Enterprise Architecture Using The Zachman Framework
A Method To Define An Enterprise Architecture Using The Zachman Framework
 
Enterprise Architecture Tools By Eacomposer
Enterprise Architecture Tools By EacomposerEnterprise Architecture Tools By Eacomposer
Enterprise Architecture Tools By Eacomposer
 
Enterprise architecture assessment guide v2.2
Enterprise architecture assessment guide v2.2Enterprise architecture assessment guide v2.2
Enterprise architecture assessment guide v2.2
 
Websphere Business Integration
Websphere Business IntegrationWebsphere Business Integration
Websphere Business Integration
 
B140815
B140815B140815
B140815
 
Max Poliashenko - Enterprise Product Architecture
Max Poliashenko - Enterprise Product ArchitectureMax Poliashenko - Enterprise Product Architecture
Max Poliashenko - Enterprise Product Architecture
 
Enterprise Architecture Framework Paper
Enterprise Architecture Framework PaperEnterprise Architecture Framework Paper
Enterprise Architecture Framework Paper
 
Building An Information Technology And Information Systems
Building An Information Technology And Information SystemsBuilding An Information Technology And Information Systems
Building An Information Technology And Information Systems
 
Child Wear Ea Blueprint V0.7
Child Wear Ea Blueprint V0.7Child Wear Ea Blueprint V0.7
Child Wear Ea Blueprint V0.7
 
A framework for_enterprise_architecture_effectiveness
A framework for_enterprise_architecture_effectivenessA framework for_enterprise_architecture_effectiveness
A framework for_enterprise_architecture_effectiveness
 
Delivering enterprise architecture
Delivering enterprise architectureDelivering enterprise architecture
Delivering enterprise architecture
 
Enterprise Architecture Approach Togaf 9
Enterprise Architecture Approach Togaf 9Enterprise Architecture Approach Togaf 9
Enterprise Architecture Approach Togaf 9
 
ICT in BUSINESS_071619_06185majesty2.pptx
ICT in BUSINESS_071619_06185majesty2.pptxICT in BUSINESS_071619_06185majesty2.pptx
ICT in BUSINESS_071619_06185majesty2.pptx
 

More from Egyptian Engineers Association

المحاضرة رقم 209 دكتور / يسرا الدسوقي عنوان المحاضرة Data Driven Management
المحاضرة رقم 209 دكتور / يسرا الدسوقي عنوان المحاضرة Data Driven Management المحاضرة رقم 209 دكتور / يسرا الدسوقي عنوان المحاضرة Data Driven Management
المحاضرة رقم 209 دكتور / يسرا الدسوقي عنوان المحاضرة Data Driven Management
Egyptian Engineers Association
 
المحاضرة رقم 208 مهندس / محمد ماجد حجازي عنوان المحاضرة Performance Measur...
المحاضرة رقم 208 مهندس / محمد ماجد حجازي عنوان المحاضرة Performance Measur... المحاضرة رقم 208 مهندس / محمد ماجد حجازي عنوان المحاضرة Performance Measur...
المحاضرة رقم 208 مهندس / محمد ماجد حجازي عنوان المحاضرة Performance Measur...
Egyptian Engineers Association
 
مبادرة #تواصل_تطوير المحاضرة رقم 205 م / محمود السعود استشاري إدارة مكاتب الم...
مبادرة #تواصل_تطوير المحاضرة رقم 205 م / محمود السعود استشاري إدارة مكاتب الم...مبادرة #تواصل_تطوير المحاضرة رقم 205 م / محمود السعود استشاري إدارة مكاتب الم...
مبادرة #تواصل_تطوير المحاضرة رقم 205 م / محمود السعود استشاري إدارة مكاتب الم...
Egyptian Engineers Association
 
تواصل_تطوير المحاضرة رقم 203 مستشار / محمد خليفة عنوان المحاضرة Establish an...
تواصل_تطوير المحاضرة رقم 203 مستشار / محمد خليفة عنوان المحاضرة Establish an...تواصل_تطوير المحاضرة رقم 203 مستشار / محمد خليفة عنوان المحاضرة Establish an...
تواصل_تطوير المحاضرة رقم 203 مستشار / محمد خليفة عنوان المحاضرة Establish an...
Egyptian Engineers Association
 
مبادرة #تواصل_تطوير المحاضرة رقم 200 أ. د/ هانىء محمود النقراشي عضو المجلس ال...
مبادرة #تواصل_تطوير المحاضرة رقم 200 أ. د/ هانىء محمود النقراشي عضو المجلس ال...مبادرة #تواصل_تطوير المحاضرة رقم 200 أ. د/ هانىء محمود النقراشي عضو المجلس ال...
مبادرة #تواصل_تطوير المحاضرة رقم 200 أ. د/ هانىء محمود النقراشي عضو المجلس ال...
Egyptian Engineers Association
 
تواصل_تطوير المحاضرة رقم 199 مهندس / محمود الديب عنوان المحاضرة Enterprise A...
تواصل_تطوير المحاضرة رقم 199 مهندس / محمود الديب عنوان المحاضرة Enterprise A...تواصل_تطوير المحاضرة رقم 199 مهندس / محمود الديب عنوان المحاضرة Enterprise A...
تواصل_تطوير المحاضرة رقم 199 مهندس / محمود الديب عنوان المحاضرة Enterprise A...
Egyptian Engineers Association
 
#تواصل_تطوير المحاضرة رقم 197 مهندس / محمد الشامي عنوان المحاضرة أمن المعلوم...
#تواصل_تطوير المحاضرة رقم 197 مهندس / محمد الشامي عنوان المحاضرة أمن المعلوم...#تواصل_تطوير المحاضرة رقم 197 مهندس / محمد الشامي عنوان المحاضرة أمن المعلوم...
#تواصل_تطوير المحاضرة رقم 197 مهندس / محمد الشامي عنوان المحاضرة أمن المعلوم...
Egyptian Engineers Association
 
تواصل_تطوير المحاضرة رقم 195 مهندس / أحمد أمين عنوان المحاضرة "The Era of Fr...
تواصل_تطوير المحاضرة رقم 195 مهندس / أحمد أمين عنوان المحاضرة "The Era of Fr...تواصل_تطوير المحاضرة رقم 195 مهندس / أحمد أمين عنوان المحاضرة "The Era of Fr...
تواصل_تطوير المحاضرة رقم 195 مهندس / أحمد أمين عنوان المحاضرة "The Era of Fr...
Egyptian Engineers Association
 
تواصل_تطوير المحاضرة رقم 194 دكتور / هشام ندا المدير الدولي لقسم الكباري بشرك...
تواصل_تطوير المحاضرة رقم 194 دكتور / هشام ندا المدير الدولي لقسم الكباري بشرك...تواصل_تطوير المحاضرة رقم 194 دكتور / هشام ندا المدير الدولي لقسم الكباري بشرك...
تواصل_تطوير المحاضرة رقم 194 دكتور / هشام ندا المدير الدولي لقسم الكباري بشرك...
Egyptian Engineers Association
 
تواصل_تطوير المحاضرة رقم 193 المهندس / أكرم النجار استشاري إدارة المشاريع عنو...
تواصل_تطوير المحاضرة رقم 193 المهندس / أكرم النجار استشاري إدارة المشاريع عنو...تواصل_تطوير المحاضرة رقم 193 المهندس / أكرم النجار استشاري إدارة المشاريع عنو...
تواصل_تطوير المحاضرة رقم 193 المهندس / أكرم النجار استشاري إدارة المشاريع عنو...
Egyptian Engineers Association
 
تواصل_تطوير المحاضرة رقم 191 المهندس / تامر فودة عنوان المحاضرة " Supply Cha...
تواصل_تطوير المحاضرة رقم 191 المهندس / تامر فودة عنوان المحاضرة " Supply Cha...تواصل_تطوير المحاضرة رقم 191 المهندس / تامر فودة عنوان المحاضرة " Supply Cha...
تواصل_تطوير المحاضرة رقم 191 المهندس / تامر فودة عنوان المحاضرة " Supply Cha...
Egyptian Engineers Association
 
تواصل_تطوير المحاضرة رقم 190 المهندس / أشرف نصير عنوان المحاضرة "إستراتيجيات...
تواصل_تطوير المحاضرة رقم 190 المهندس / أشرف نصير عنوان المحاضرة "إستراتيجيات...تواصل_تطوير المحاضرة رقم 190 المهندس / أشرف نصير عنوان المحاضرة "إستراتيجيات...
تواصل_تطوير المحاضرة رقم 190 المهندس / أشرف نصير عنوان المحاضرة "إستراتيجيات...
Egyptian Engineers Association
 
المحاضرة رقم 189 المهندس / محمد العربي بعنوان "Digital Disruption Act- From...
المحاضرة رقم 189 المهندس / محمد العربي بعنوان "Digital Disruption Act- From... المحاضرة رقم 189 المهندس / محمد العربي بعنوان "Digital Disruption Act- From...
المحاضرة رقم 189 المهندس / محمد العربي بعنوان "Digital Disruption Act- From...
Egyptian Engineers Association
 
#تواصل_تطوير المحاضرة رقم 188 الاستاذ الدكتور / أكرم حسن استاذ واستشاري إدارة...
#تواصل_تطوير المحاضرة رقم 188 الاستاذ الدكتور / أكرم حسن استاذ واستشاري إدارة...#تواصل_تطوير المحاضرة رقم 188 الاستاذ الدكتور / أكرم حسن استاذ واستشاري إدارة...
#تواصل_تطوير المحاضرة رقم 188 الاستاذ الدكتور / أكرم حسن استاذ واستشاري إدارة...
Egyptian Engineers Association
 
ilovepdf_#تواصل_تطوير المحاضرة رقم 187 أستاذ دكتور / مدحت كمال عبدالله عنوان ...
ilovepdf_#تواصل_تطوير المحاضرة رقم 187 أستاذ دكتور / مدحت كمال عبدالله عنوان ...ilovepdf_#تواصل_تطوير المحاضرة رقم 187 أستاذ دكتور / مدحت كمال عبدالله عنوان ...
ilovepdf_#تواصل_تطوير المحاضرة رقم 187 أستاذ دكتور / مدحت كمال عبدالله عنوان ...
Egyptian Engineers Association
 
ilovepdf_ المحاضرة رقم 186 دكتور / اشرف حمدان بمشاركة الاستاذة /سارة سالم عنو...
ilovepdf_ المحاضرة رقم 186 دكتور / اشرف حمدان بمشاركة الاستاذة /سارة سالم عنو...ilovepdf_ المحاضرة رقم 186 دكتور / اشرف حمدان بمشاركة الاستاذة /سارة سالم عنو...
ilovepdf_ المحاضرة رقم 186 دكتور / اشرف حمدان بمشاركة الاستاذة /سارة سالم عنو...
Egyptian Engineers Association
 
تواصل_تطوير المحاضرة رقم 185 دكتور / هبة محروس علي بعنوان "Between Environme...
تواصل_تطوير المحاضرة رقم 185 دكتور / هبة محروس علي بعنوان "Between Environme...تواصل_تطوير المحاضرة رقم 185 دكتور / هبة محروس علي بعنوان "Between Environme...
تواصل_تطوير المحاضرة رقم 185 دكتور / هبة محروس علي بعنوان "Between Environme...
Egyptian Engineers Association
 
#تواصل_تطوير المحاضرة رقم 184 دكتور / شيماء محمد الشرقاوي بعنوان "مبادرة الت...
#تواصل_تطوير المحاضرة رقم 184 دكتور / شيماء محمد الشرقاوي بعنوان "مبادرة الت...#تواصل_تطوير المحاضرة رقم 184 دكتور / شيماء محمد الشرقاوي بعنوان "مبادرة الت...
#تواصل_تطوير المحاضرة رقم 184 دكتور / شيماء محمد الشرقاوي بعنوان "مبادرة الت...
Egyptian Engineers Association
 
المحاضرة رقم 183 الاستاذ الدكتور / طارق عطية بعنوان "اعتماد المتحف المصري ا...
المحاضرة رقم 183 الاستاذ الدكتور / طارق عطية بعنوان "اعتماد المتحف المصري ا... المحاضرة رقم 183 الاستاذ الدكتور / طارق عطية بعنوان "اعتماد المتحف المصري ا...
المحاضرة رقم 183 الاستاذ الدكتور / طارق عطية بعنوان "اعتماد المتحف المصري ا...
Egyptian Engineers Association
 
المحاضرة رقم 182 الدكتور / أسامة أبوالمكارم مستشار التغيير والابداع المؤسسي ...
المحاضرة رقم 182 الدكتور / أسامة أبوالمكارم مستشار التغيير والابداع المؤسسي ... المحاضرة رقم 182 الدكتور / أسامة أبوالمكارم مستشار التغيير والابداع المؤسسي ...
المحاضرة رقم 182 الدكتور / أسامة أبوالمكارم مستشار التغيير والابداع المؤسسي ...
Egyptian Engineers Association
 

More from Egyptian Engineers Association (20)

المحاضرة رقم 209 دكتور / يسرا الدسوقي عنوان المحاضرة Data Driven Management
المحاضرة رقم 209 دكتور / يسرا الدسوقي عنوان المحاضرة Data Driven Management المحاضرة رقم 209 دكتور / يسرا الدسوقي عنوان المحاضرة Data Driven Management
المحاضرة رقم 209 دكتور / يسرا الدسوقي عنوان المحاضرة Data Driven Management
 
المحاضرة رقم 208 مهندس / محمد ماجد حجازي عنوان المحاضرة Performance Measur...
المحاضرة رقم 208 مهندس / محمد ماجد حجازي عنوان المحاضرة Performance Measur... المحاضرة رقم 208 مهندس / محمد ماجد حجازي عنوان المحاضرة Performance Measur...
المحاضرة رقم 208 مهندس / محمد ماجد حجازي عنوان المحاضرة Performance Measur...
 
مبادرة #تواصل_تطوير المحاضرة رقم 205 م / محمود السعود استشاري إدارة مكاتب الم...
مبادرة #تواصل_تطوير المحاضرة رقم 205 م / محمود السعود استشاري إدارة مكاتب الم...مبادرة #تواصل_تطوير المحاضرة رقم 205 م / محمود السعود استشاري إدارة مكاتب الم...
مبادرة #تواصل_تطوير المحاضرة رقم 205 م / محمود السعود استشاري إدارة مكاتب الم...
 
تواصل_تطوير المحاضرة رقم 203 مستشار / محمد خليفة عنوان المحاضرة Establish an...
تواصل_تطوير المحاضرة رقم 203 مستشار / محمد خليفة عنوان المحاضرة Establish an...تواصل_تطوير المحاضرة رقم 203 مستشار / محمد خليفة عنوان المحاضرة Establish an...
تواصل_تطوير المحاضرة رقم 203 مستشار / محمد خليفة عنوان المحاضرة Establish an...
 
مبادرة #تواصل_تطوير المحاضرة رقم 200 أ. د/ هانىء محمود النقراشي عضو المجلس ال...
مبادرة #تواصل_تطوير المحاضرة رقم 200 أ. د/ هانىء محمود النقراشي عضو المجلس ال...مبادرة #تواصل_تطوير المحاضرة رقم 200 أ. د/ هانىء محمود النقراشي عضو المجلس ال...
مبادرة #تواصل_تطوير المحاضرة رقم 200 أ. د/ هانىء محمود النقراشي عضو المجلس ال...
 
تواصل_تطوير المحاضرة رقم 199 مهندس / محمود الديب عنوان المحاضرة Enterprise A...
تواصل_تطوير المحاضرة رقم 199 مهندس / محمود الديب عنوان المحاضرة Enterprise A...تواصل_تطوير المحاضرة رقم 199 مهندس / محمود الديب عنوان المحاضرة Enterprise A...
تواصل_تطوير المحاضرة رقم 199 مهندس / محمود الديب عنوان المحاضرة Enterprise A...
 
#تواصل_تطوير المحاضرة رقم 197 مهندس / محمد الشامي عنوان المحاضرة أمن المعلوم...
#تواصل_تطوير المحاضرة رقم 197 مهندس / محمد الشامي عنوان المحاضرة أمن المعلوم...#تواصل_تطوير المحاضرة رقم 197 مهندس / محمد الشامي عنوان المحاضرة أمن المعلوم...
#تواصل_تطوير المحاضرة رقم 197 مهندس / محمد الشامي عنوان المحاضرة أمن المعلوم...
 
تواصل_تطوير المحاضرة رقم 195 مهندس / أحمد أمين عنوان المحاضرة "The Era of Fr...
تواصل_تطوير المحاضرة رقم 195 مهندس / أحمد أمين عنوان المحاضرة "The Era of Fr...تواصل_تطوير المحاضرة رقم 195 مهندس / أحمد أمين عنوان المحاضرة "The Era of Fr...
تواصل_تطوير المحاضرة رقم 195 مهندس / أحمد أمين عنوان المحاضرة "The Era of Fr...
 
تواصل_تطوير المحاضرة رقم 194 دكتور / هشام ندا المدير الدولي لقسم الكباري بشرك...
تواصل_تطوير المحاضرة رقم 194 دكتور / هشام ندا المدير الدولي لقسم الكباري بشرك...تواصل_تطوير المحاضرة رقم 194 دكتور / هشام ندا المدير الدولي لقسم الكباري بشرك...
تواصل_تطوير المحاضرة رقم 194 دكتور / هشام ندا المدير الدولي لقسم الكباري بشرك...
 
تواصل_تطوير المحاضرة رقم 193 المهندس / أكرم النجار استشاري إدارة المشاريع عنو...
تواصل_تطوير المحاضرة رقم 193 المهندس / أكرم النجار استشاري إدارة المشاريع عنو...تواصل_تطوير المحاضرة رقم 193 المهندس / أكرم النجار استشاري إدارة المشاريع عنو...
تواصل_تطوير المحاضرة رقم 193 المهندس / أكرم النجار استشاري إدارة المشاريع عنو...
 
تواصل_تطوير المحاضرة رقم 191 المهندس / تامر فودة عنوان المحاضرة " Supply Cha...
تواصل_تطوير المحاضرة رقم 191 المهندس / تامر فودة عنوان المحاضرة " Supply Cha...تواصل_تطوير المحاضرة رقم 191 المهندس / تامر فودة عنوان المحاضرة " Supply Cha...
تواصل_تطوير المحاضرة رقم 191 المهندس / تامر فودة عنوان المحاضرة " Supply Cha...
 
تواصل_تطوير المحاضرة رقم 190 المهندس / أشرف نصير عنوان المحاضرة "إستراتيجيات...
تواصل_تطوير المحاضرة رقم 190 المهندس / أشرف نصير عنوان المحاضرة "إستراتيجيات...تواصل_تطوير المحاضرة رقم 190 المهندس / أشرف نصير عنوان المحاضرة "إستراتيجيات...
تواصل_تطوير المحاضرة رقم 190 المهندس / أشرف نصير عنوان المحاضرة "إستراتيجيات...
 
المحاضرة رقم 189 المهندس / محمد العربي بعنوان "Digital Disruption Act- From...
المحاضرة رقم 189 المهندس / محمد العربي بعنوان "Digital Disruption Act- From... المحاضرة رقم 189 المهندس / محمد العربي بعنوان "Digital Disruption Act- From...
المحاضرة رقم 189 المهندس / محمد العربي بعنوان "Digital Disruption Act- From...
 
#تواصل_تطوير المحاضرة رقم 188 الاستاذ الدكتور / أكرم حسن استاذ واستشاري إدارة...
#تواصل_تطوير المحاضرة رقم 188 الاستاذ الدكتور / أكرم حسن استاذ واستشاري إدارة...#تواصل_تطوير المحاضرة رقم 188 الاستاذ الدكتور / أكرم حسن استاذ واستشاري إدارة...
#تواصل_تطوير المحاضرة رقم 188 الاستاذ الدكتور / أكرم حسن استاذ واستشاري إدارة...
 
ilovepdf_#تواصل_تطوير المحاضرة رقم 187 أستاذ دكتور / مدحت كمال عبدالله عنوان ...
ilovepdf_#تواصل_تطوير المحاضرة رقم 187 أستاذ دكتور / مدحت كمال عبدالله عنوان ...ilovepdf_#تواصل_تطوير المحاضرة رقم 187 أستاذ دكتور / مدحت كمال عبدالله عنوان ...
ilovepdf_#تواصل_تطوير المحاضرة رقم 187 أستاذ دكتور / مدحت كمال عبدالله عنوان ...
 
ilovepdf_ المحاضرة رقم 186 دكتور / اشرف حمدان بمشاركة الاستاذة /سارة سالم عنو...
ilovepdf_ المحاضرة رقم 186 دكتور / اشرف حمدان بمشاركة الاستاذة /سارة سالم عنو...ilovepdf_ المحاضرة رقم 186 دكتور / اشرف حمدان بمشاركة الاستاذة /سارة سالم عنو...
ilovepdf_ المحاضرة رقم 186 دكتور / اشرف حمدان بمشاركة الاستاذة /سارة سالم عنو...
 
تواصل_تطوير المحاضرة رقم 185 دكتور / هبة محروس علي بعنوان "Between Environme...
تواصل_تطوير المحاضرة رقم 185 دكتور / هبة محروس علي بعنوان "Between Environme...تواصل_تطوير المحاضرة رقم 185 دكتور / هبة محروس علي بعنوان "Between Environme...
تواصل_تطوير المحاضرة رقم 185 دكتور / هبة محروس علي بعنوان "Between Environme...
 
#تواصل_تطوير المحاضرة رقم 184 دكتور / شيماء محمد الشرقاوي بعنوان "مبادرة الت...
#تواصل_تطوير المحاضرة رقم 184 دكتور / شيماء محمد الشرقاوي بعنوان "مبادرة الت...#تواصل_تطوير المحاضرة رقم 184 دكتور / شيماء محمد الشرقاوي بعنوان "مبادرة الت...
#تواصل_تطوير المحاضرة رقم 184 دكتور / شيماء محمد الشرقاوي بعنوان "مبادرة الت...
 
المحاضرة رقم 183 الاستاذ الدكتور / طارق عطية بعنوان "اعتماد المتحف المصري ا...
المحاضرة رقم 183 الاستاذ الدكتور / طارق عطية بعنوان "اعتماد المتحف المصري ا... المحاضرة رقم 183 الاستاذ الدكتور / طارق عطية بعنوان "اعتماد المتحف المصري ا...
المحاضرة رقم 183 الاستاذ الدكتور / طارق عطية بعنوان "اعتماد المتحف المصري ا...
 
المحاضرة رقم 182 الدكتور / أسامة أبوالمكارم مستشار التغيير والابداع المؤسسي ...
المحاضرة رقم 182 الدكتور / أسامة أبوالمكارم مستشار التغيير والابداع المؤسسي ... المحاضرة رقم 182 الدكتور / أسامة أبوالمكارم مستشار التغيير والابداع المؤسسي ...
المحاضرة رقم 182 الدكتور / أسامة أبوالمكارم مستشار التغيير والابداع المؤسسي ...
 

Recently uploaded

一比一原版(IIT毕业证)伊利诺伊理工大学毕业证成绩单专业办理
一比一原版(IIT毕业证)伊利诺伊理工大学毕业证成绩单专业办理一比一原版(IIT毕业证)伊利诺伊理工大学毕业证成绩单专业办理
一比一原版(IIT毕业证)伊利诺伊理工大学毕业证成绩单专业办理
zwunae
 
AKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdf
AKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdfAKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdf
AKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdf
SamSarthak3
 
HYDROPOWER - Hydroelectric power generation
HYDROPOWER - Hydroelectric power generationHYDROPOWER - Hydroelectric power generation
HYDROPOWER - Hydroelectric power generation
Robbie Edward Sayers
 
Cosmetic shop management system project report.pdf
Cosmetic shop management system project report.pdfCosmetic shop management system project report.pdf
Cosmetic shop management system project report.pdf
Kamal Acharya
 
Student information management system project report ii.pdf
Student information management system project report ii.pdfStudent information management system project report ii.pdf
Student information management system project report ii.pdf
Kamal Acharya
 
space technology lecture notes on satellite
space technology lecture notes on satellitespace technology lecture notes on satellite
space technology lecture notes on satellite
ongomchris
 
ML for identifying fraud using open blockchain data.pptx
ML for identifying fraud using open blockchain data.pptxML for identifying fraud using open blockchain data.pptx
ML for identifying fraud using open blockchain data.pptx
Vijay Dialani, PhD
 
Design and Analysis of Algorithms-DP,Backtracking,Graphs,B&B
Design and Analysis of Algorithms-DP,Backtracking,Graphs,B&BDesign and Analysis of Algorithms-DP,Backtracking,Graphs,B&B
Design and Analysis of Algorithms-DP,Backtracking,Graphs,B&B
Sreedhar Chowdam
 
Industrial Training at Shahjalal Fertilizer Company Limited (SFCL)
Industrial Training at Shahjalal Fertilizer Company Limited (SFCL)Industrial Training at Shahjalal Fertilizer Company Limited (SFCL)
Industrial Training at Shahjalal Fertilizer Company Limited (SFCL)
MdTanvirMahtab2
 
H.Seo, ICLR 2024, MLILAB, KAIST AI.pdf
H.Seo, ICLR 2024, MLILAB, KAIST AI.pdfH.Seo, ICLR 2024, MLILAB, KAIST AI.pdf
H.Seo, ICLR 2024, MLILAB, KAIST AI.pdf
MLILAB
 
DESIGN A COTTON SEED SEPARATION MACHINE.docx
DESIGN A COTTON SEED SEPARATION MACHINE.docxDESIGN A COTTON SEED SEPARATION MACHINE.docx
DESIGN A COTTON SEED SEPARATION MACHINE.docx
FluxPrime1
 
English lab ppt no titlespecENG PPTt.pdf
English lab ppt no titlespecENG PPTt.pdfEnglish lab ppt no titlespecENG PPTt.pdf
English lab ppt no titlespecENG PPTt.pdf
BrazilAccount1
 
CFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptx
CFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptxCFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptx
CFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptx
R&R Consult
 
Immunizing Image Classifiers Against Localized Adversary Attacks
Immunizing Image Classifiers Against Localized Adversary AttacksImmunizing Image Classifiers Against Localized Adversary Attacks
Immunizing Image Classifiers Against Localized Adversary Attacks
gerogepatton
 
MCQ Soil mechanics questions (Soil shear strength).pdf
MCQ Soil mechanics questions (Soil shear strength).pdfMCQ Soil mechanics questions (Soil shear strength).pdf
MCQ Soil mechanics questions (Soil shear strength).pdf
Osamah Alsalih
 
AP LAB PPT.pdf ap lab ppt no title specific
AP LAB PPT.pdf ap lab ppt no title specificAP LAB PPT.pdf ap lab ppt no title specific
AP LAB PPT.pdf ap lab ppt no title specific
BrazilAccount1
 
Governing Equations for Fundamental Aerodynamics_Anderson2010.pdf
Governing Equations for Fundamental Aerodynamics_Anderson2010.pdfGoverning Equations for Fundamental Aerodynamics_Anderson2010.pdf
Governing Equations for Fundamental Aerodynamics_Anderson2010.pdf
WENKENLI1
 
Hierarchical Digital Twin of a Naval Power System
Hierarchical Digital Twin of a Naval Power SystemHierarchical Digital Twin of a Naval Power System
Hierarchical Digital Twin of a Naval Power System
Kerry Sado
 
Water Industry Process Automation and Control Monthly - May 2024.pdf
Water Industry Process Automation and Control Monthly - May 2024.pdfWater Industry Process Automation and Control Monthly - May 2024.pdf
Water Industry Process Automation and Control Monthly - May 2024.pdf
Water Industry Process Automation & Control
 
ASME IX(9) 2007 Full Version .pdf
ASME IX(9) 2007 Full Version .pdfASME IX(9) 2007 Full Version .pdf
ASME IX(9) 2007 Full Version .pdf
AhmedHussein950959
 

Recently uploaded (20)

一比一原版(IIT毕业证)伊利诺伊理工大学毕业证成绩单专业办理
一比一原版(IIT毕业证)伊利诺伊理工大学毕业证成绩单专业办理一比一原版(IIT毕业证)伊利诺伊理工大学毕业证成绩单专业办理
一比一原版(IIT毕业证)伊利诺伊理工大学毕业证成绩单专业办理
 
AKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdf
AKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdfAKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdf
AKS UNIVERSITY Satna Final Year Project By OM Hardaha.pdf
 
HYDROPOWER - Hydroelectric power generation
HYDROPOWER - Hydroelectric power generationHYDROPOWER - Hydroelectric power generation
HYDROPOWER - Hydroelectric power generation
 
Cosmetic shop management system project report.pdf
Cosmetic shop management system project report.pdfCosmetic shop management system project report.pdf
Cosmetic shop management system project report.pdf
 
Student information management system project report ii.pdf
Student information management system project report ii.pdfStudent information management system project report ii.pdf
Student information management system project report ii.pdf
 
space technology lecture notes on satellite
space technology lecture notes on satellitespace technology lecture notes on satellite
space technology lecture notes on satellite
 
ML for identifying fraud using open blockchain data.pptx
ML for identifying fraud using open blockchain data.pptxML for identifying fraud using open blockchain data.pptx
ML for identifying fraud using open blockchain data.pptx
 
Design and Analysis of Algorithms-DP,Backtracking,Graphs,B&B
Design and Analysis of Algorithms-DP,Backtracking,Graphs,B&BDesign and Analysis of Algorithms-DP,Backtracking,Graphs,B&B
Design and Analysis of Algorithms-DP,Backtracking,Graphs,B&B
 
Industrial Training at Shahjalal Fertilizer Company Limited (SFCL)
Industrial Training at Shahjalal Fertilizer Company Limited (SFCL)Industrial Training at Shahjalal Fertilizer Company Limited (SFCL)
Industrial Training at Shahjalal Fertilizer Company Limited (SFCL)
 
H.Seo, ICLR 2024, MLILAB, KAIST AI.pdf
H.Seo, ICLR 2024, MLILAB, KAIST AI.pdfH.Seo, ICLR 2024, MLILAB, KAIST AI.pdf
H.Seo, ICLR 2024, MLILAB, KAIST AI.pdf
 
DESIGN A COTTON SEED SEPARATION MACHINE.docx
DESIGN A COTTON SEED SEPARATION MACHINE.docxDESIGN A COTTON SEED SEPARATION MACHINE.docx
DESIGN A COTTON SEED SEPARATION MACHINE.docx
 
English lab ppt no titlespecENG PPTt.pdf
English lab ppt no titlespecENG PPTt.pdfEnglish lab ppt no titlespecENG PPTt.pdf
English lab ppt no titlespecENG PPTt.pdf
 
CFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptx
CFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptxCFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptx
CFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptx
 
Immunizing Image Classifiers Against Localized Adversary Attacks
Immunizing Image Classifiers Against Localized Adversary AttacksImmunizing Image Classifiers Against Localized Adversary Attacks
Immunizing Image Classifiers Against Localized Adversary Attacks
 
MCQ Soil mechanics questions (Soil shear strength).pdf
MCQ Soil mechanics questions (Soil shear strength).pdfMCQ Soil mechanics questions (Soil shear strength).pdf
MCQ Soil mechanics questions (Soil shear strength).pdf
 
AP LAB PPT.pdf ap lab ppt no title specific
AP LAB PPT.pdf ap lab ppt no title specificAP LAB PPT.pdf ap lab ppt no title specific
AP LAB PPT.pdf ap lab ppt no title specific
 
Governing Equations for Fundamental Aerodynamics_Anderson2010.pdf
Governing Equations for Fundamental Aerodynamics_Anderson2010.pdfGoverning Equations for Fundamental Aerodynamics_Anderson2010.pdf
Governing Equations for Fundamental Aerodynamics_Anderson2010.pdf
 
Hierarchical Digital Twin of a Naval Power System
Hierarchical Digital Twin of a Naval Power SystemHierarchical Digital Twin of a Naval Power System
Hierarchical Digital Twin of a Naval Power System
 
Water Industry Process Automation and Control Monthly - May 2024.pdf
Water Industry Process Automation and Control Monthly - May 2024.pdfWater Industry Process Automation and Control Monthly - May 2024.pdf
Water Industry Process Automation and Control Monthly - May 2024.pdf
 
ASME IX(9) 2007 Full Version .pdf
ASME IX(9) 2007 Full Version .pdfASME IX(9) 2007 Full Version .pdf
ASME IX(9) 2007 Full Version .pdf
 

المحاضرة 153 بعنوان مقدمة عن البنية المؤسسية

  • 1.
  • 2. ‫المؤسسية‬ ‫البنية‬ ‫عن‬ ‫مقدمة‬ ‫الطريق‬ ‫األمثل‬ ‫الرقمي‬ ‫التحول‬ ‫نحو‬
  • 3. Enterprise Architecture let’s Play A Game !! | Most of agenda Items followed Togaf Standard 9.2 and tailored for presentation purposes to streamline understanding of EA Concepts 2
  • 4. Agenda 3 ِ‫د‬ ْ ‫ش‬ُّ‫ر‬‫ال‬ ‫ى‬َ‫ل‬َ‫ع‬ َ‫ة‬َ‫يم‬ِ‫ز‬َ‫ع‬ْ‫ل‬‫ا‬َ‫و‬ ،ِ‫ر‬ ْ‫م‬َ ْ ‫األ‬ ‫ي‬ِ‫ف‬ َ ‫ات‬َ‫ب‬َّ‫ث‬‫ال‬ َ ‫ك‬ُ‫ل‬َ‫أ‬ ْ ‫س‬َ‫أ‬ ‫ي‬ ِّ‫ن‬ِ‫إ‬ َّ‫م‬ُ‫ه‬َّ‫ل‬‫ال‬ Overview – ‫عامة‬ ‫نظرة‬ Architecture Foundations – ‫المؤسسية‬ ‫البنية‬ ‫أساسيات‬ Architecture Method & Iterations – ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Guidelines and Techniques – ‫والتقنيات‬ ‫اإلرشادية‬ ‫القواعد‬ Architecture Governance – ‫البنية‬ ‫حوكمة‬ EA Office Setup Journey – ‫المؤسسية‬ ‫البنية‬ ‫مكتب‬ ‫إنشاء‬ ‫رحلة‬
  • 5. 1 Overview - ‫عامة‬ ‫نظرة‬ ▷Introduction ▷The Big Picture 4
  • 7. YOU MAY SETUP THE EMERGING TECHNOLOGIES , BUT WITHOUT ARCHITECTURE YOU STILL ..! Spaghetti Enterprise 6
  • 8. IS THE BRIDGE BETWEEN STRATEGY FORMULATION AND EXECUTION ENTERPRISE ARCHITECTURE PRACTICES 7 FORMULATION EXECUTION
  • 9. ENTERPRISE ARCHITECTURE ENABLES INTEGRATION OF VARIOUS TRANSFORMATION EFFORTS, FOSTER RESPONSIVE TO CHANGE IN BOTH CORPORATE STRATEGY AND OPERATING MODEL Business Transformation Pillars Enterprise Transformation Digital Transformation Technology Innovation IT Function Transformation Focuses on transforming the Operating Model of an enterprise Enabler of all other transformation types through Digitalization Focuses on customer facing areas of business and the extended enterprise How work gets done inside IT organization within an enterprise (Transform IT OM) EA 8
  • 10. What is Enterprise Architecture ENTERPRISE ARCHITECTURE DEFINES THE STRUCTURE, OPERATION OF AN ORGANIZATION AND DETERMINE HOW IT CAN MOST EFFECTIVELY ACHIEVE ITS CURRENT AND FUTURE OBJECTIVES Enterprise Architecture Architecture Enterprise Architecture crosses multiple systems and multiple functional groups within the enterprise An enterprise could be: * A whole corporation / single division * Government agency / single department * A chain of geographically distant organizations linked together by common ownership * Groups of countries/ governments working together to create common or shareable deliverables or infrastructures * Partnership / alliances of businesses working together, such as a consortium or supply chain The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution The structure of components, their inter- relationships, and the principles and guidelines governing their design and evolution over time Reflect integration, standardization requirements of Enterprise Operating Model Any collection of organizations that has common goals Enterprise in EA, denote both an entire enterprise, encompassing all of its information systems, and a specific domain within the enterprise Extended enterprise frequently includes partners, suppliers, and customers. 9
  • 11. EA Business Benefits ENTERPRISE ARCHITECTURE AIMS IS TO BUILD INTEGRATED ENVIRONMENT THAT IS RESPONSIVE TO CHANGE AND SUPPORTIVE OF THE DELIVERY OF THE BUSINESS STRATEGY Effective and efficient business operations Effective and efficient Digital Transformation and IT operations: Better return on existing investment, reduced risk for future investment Faster, simpler, and cheaper procurement 10 Agile Organization, shared business capacities, flexible workforce, lower change mgmt. cost, and Improved business productivity Lower software development, support, and maintenance costs, increased portability, Improved interoperability and address enterprise-wide issues Reduced complexity, Maximum ROI, flexible to make, buy, or out-source business and IT solutions and reduce overall risk Simpler buying decisions, maximizing procurement speed and flexibility without sacrificing architectural coherence and to secure economic capabilities
  • 12. Architecture Framework AN ARCHITECTURE FRAMEWORK IS A FOUNDATIONAL STRUCTURE, OR SET OF STRUCTURES, THAT CAN BE USED FOR DEVELOPING A BROAD RANGE OF DIFFERENT ARCHITECTURES Architecture Framework Definition Architecture Framework Value Proposition Common Vocabulary Common Language & set of tools Simplify & Speedup Architecture Development Complete Coverage Ensure coverage of desired solution Future Growth Faster respond to future business needs (Responsive to change) Method Designing Enterprise Target state ( building blocks) Recommended standards Standards & compliant products Foundational Structure Foundational Structure used for developing range of different architectures A conceptual structure used to plan, develop, implement, govern, and sustain an architecture 11
  • 13. Architecture Framework Structure ARCHITECTURE FRAMEWORK ENSURE THAT THE ARCHITECTURE SELECTED ALLOWS FOR FUTURE GROWTH IN RESPONSE TO THE NEEDS OF THE BUSINESS Consider Stakeholders Concerns Cover Stakeholder views and viewpoints Architecture Model The way to do architecture Cycle for develop architecture work Method Lego Box for your building blocks Classify your building blocks Categorization System How, with what you described architecture structure Start point to do EA in your enterprise Metamodel Architecture Model enrich the repos. consume the repos. to build viewpoints classify assets speak common lang. Iterative cycles 12
  • 14. Various Frameworks Tailor Your Organizational Architecture Framework (Cook Book) Various Architecture Frameworks ARCHITECTURE FRAMEWORK SHOULD BE TAILORED TO MEET THE NEEDS OF THE ORGANIZATION http://www.iso-architecture.org/ieee-1471/afs/frameworks-table.html https://en.wikipedia.org/wiki/Enterprise_architecture_framework 13
  • 15. Architecture Domains THEERE ARE FOUR COMMONLY ACCEPTED ARCHITECTURE DOMAINS AS SUBSETS OF AN OVERALL ENTERPRISE ARCHITECTURE 14 Business Architecture Data Architecture Technology Architecture Application Architecture ▪ Software and Hardware capabilities ▪ Help deployment of Business , application and data ▪ Includes ▪ IT infrastructure, middleware, ▪ Networks, communications, ▪ Processing, and standards. ▪ Structure of logical data assets ▪ Structure of physical data assets ▪ Data management resources. ▪ A blueprint of application ▪ Interaction to other applications ▪ Relationships to business processes ▪ Business strategy ▪ Governance ▪ Organization ▪ business processes ▪ People
  • 17. ENTERPRISE ARCHITECTURE BIG PICTURE (aligned with Togaf 9.2) Consume building blocks (BB) Building Blocks Generate Building blocks (BB) Enterprise Continuum Guidelines and Techniques (Principles, Gap Analysis, CBP, Stakeholder Mgmt. ,…) Building Blocks Catalogs Matrices Diagrams Artifacts Architecture Development Method (ADM) Operating Model ( Governance Framework, Architecture Capability , Interaction Model, Architecture Compliance , Architecture Contracts, …) Architecture Metamodel Arch. Repository Management Deliverables Stakeholders, Views & Viewpoints Reference Models Ecosystem Tool Management 16
  • 18. 2 Architecture Foundations - ‫البنية‬ ‫أساسيات‬ ▷Stakeholders, Views and Viewpoints Basics (WHO,WHY) ▷Enterprise Continuum & Architecture Repository (WHERE) ▷Artifacts, Deliverables and Building Blocks (WHAT, HOW) 17
  • 19. FOUNDATIONS 2.1 Stakeholders, Views & Viewpoints Basics ‫النظر‬ ‫ووجهات‬ ‫المنظور‬ ‫أساسيات‬ , ‫العالقة‬ ‫أصحاب‬ 18
  • 20. Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 19
  • 21. Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 20
  • 22. EVERYTHING ABOUT ARCHITECTURE RELATES TO DEEPLY UNDERSTANDING OF TWO MAIN CONCEPTS (WHAT & HOW) What & How Concepts Differentiators (HOW) ‫كيف‬ - How do you visualize something ? / How can I do something ? - Differentiators point of views - i.e How I Make Coffee ? Building Blocks (WHAT) ‫ماذا‬ - Identify what you have ? - Basic unit (Building blocks ) from which something is built up. - i.e What I Have to Make Coffee ? 21
  • 23. AS ENTERPRISE ARCHITECT, ECOSYSTEM/SYSTEM REPRESENT WHAT YOU SHOULD CONSIDER DURING YOUR ARCHITECTURE-RELATED ACTIVITIES AS “ A SCOPE OF ENTERPRISE IMPACTED” Ecosystem / System overview Ecosystem System is a combination of interacting elements organized to achieve one or more stated purposes Encompasses individual applications, systems in the traditional sense, subsystems, systems of systems, product lines, product families, whole enterprises, and other aggregations of interest System N Ecosystem go beyond organization boundary to include its environment industry (i.e. suppliers, distributors, customers, competitors, government agencies, and so on) Ecosystem network involved in the delivery of a specific product or service through both competition and cooperation 22
  • 24. ECOSYSTEM / SYSTEM REAL EXAMPLE (1/2) Photosynthesis Ecosystem Ecosystem Plant Development System Photosynthesis Ecosystem 1 2 23
  • 25. ECOSYSTEM / SYSTEM REAL EXAMPLE (2/2) Ant Colony Ecosystem Ecosystem Ant Colony System Ant Colony Ecosystem 1 2 24
  • 26. EXTENDED ENTERPRISE SCOPE OF EXTENDED ENTERPRISE ENCOMPASSES BOTH ENTERPRISE SYSTEM AND ITS ECOSYSTEM … Enterprise / Extended Enterprise overview Any collection of organizations that has a common set of goals Large corporations may comprise multiple enterprises Enterprise Bigger umbrella care about its internal system as well as its ecosystem Comprises the partners, suppliers, and customers, as well as internal business units. ❖ Whole corporation, or division of a corporation ❖ Government agency or a single department; ❖ Chain of geographically distant organizations linked together by common ownership ❖ Groups of countries or governments working together to create common or shareable deliverables ❖ Partnerships and alliances of businesses working together, such as a consortium or supply chain ENTERPRISE 25
  • 27. … TO PRESERVE ITS POSITION, ENTERPRISE SHOULD GUARANTEE ITS COMPETITIVE ADVANTAGES THROUGH EMPOWERING BOTH INTERNAL AND EXTERNAL PILLARS Connecting Dots Goals and values Resources and capabilities Structure & Systems Environment/Strategy Interface Firm/Strategy interface Strategy The Firm Enterprise (System) Environment Industry (Ecosystem) Customers Competitors Suppliers Partners Complementors 26
  • 28. Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 27
  • 29. STAKEHOLDERS ARE INDIVIDUALS, TEAMS, ORGANIZATIONS, OR CLASSES THEREOF, HAVING AN INTEREST IN A SYSTEM Stakeholders System 28
  • 30. A SYSTEM HAS ONE OR MORE STAKEHOLDERS, EACH STAKEHOLDER TYPICALLY HAS ROLE, INTERESTS IN, OR CONCERNS RELATIVE TO, THAT SYSTEM Stakeholders for Enterprise Architecture 29 | Image Source: Togaf 9.2 Foundation Guide book – Typical set of stakeholders for EA
  • 31. Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 30
  • 32. INTERESTS IN A SYSTEM CAN BE RELEVANT TO ONE OR MORE OF ITS STAKEHOLDERS WHICH CAN BE FUTHER DECOMPOSED INTRO REQUIREMENTS Architecture Concern = Area of Interest Functionality Development Operations Acceptance Concerns related to any system aspects Performance Reliability Distribution Authorization Risk Audit Assurance … Agility Mobility … Coverage Usability Consistency … … … 31
  • 33. Stakeholders, Views & Viewpoints Stakeholders ‫العالقة‬ ‫أصحاب‬ Concerns ‫اإلهتمامات‬ Views & Viewpoints ‫المنظور‬ – ‫النظر‬ ‫وجهات‬ Ecosystem / System ‫منظومة‬ - ‫نظام‬ 32
  • 34. ARCHITECTURE VIEWPOINTS ESTABLISHES THE CONVENTIONS FOR CONSTRUCTING, INTERPRETING AND USING AN ARCHITECTURE VIEW TO ADDRESS CONCERN(S) ABOUT A SYSTEM-OF-INTEREST Viewpoints / Views What you see ? Where are you looking from ? Viewpoint ‫المنظور‬ View ‫النظر‬ ‫وجهات‬ - Representation of a system from the perspective of a related set of concerns - Visualized asset to inform stakeholders that their concerns are being met. - An architecture view is always specific to the architecture for which it is created. Instance of the completed template - Vantage point or perspective that determines what you see - Viewpoint defines the perspective from which an architecture view is taken. - The specification of the conventions for a particular kind of architecture view - Architecture viewpoints are generic, and can be stored in libraries for re-use, known as a viewpoint library. Template 33
  • 35. VIEWPOINTS / VIEWS REAL EXAMPLES (1/4) Building Architecture VIEWPOINT VIEW 34
  • 36. VIEWPOINTS / VIEWS REAL EXAMPLES (2/4) Scene Viewpoint & Camera View 35
  • 37. VIEWPOINTS / VIEWS REAL EXAMPLES (3/4) Human Eye Retina Viewpoint Layers VIEWPOINT LAYERS (LIBRARY) LANSCAPE COMPLEX VIEW 36
  • 38. VIEWPOINTS / VIEWS REAL EXAMPLES (4/4) Protractor Viewpoint (Contradicting Views) – No Cooperation 37
  • 39. | Source: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap31.html EA FRAMEWORKS VIEWS / VIEWPOINTS (1/2) Togaf Standard Viewpoints 38
  • 40. EA FRAMEWORKS VIEWS / VIEWPOINTS (2/2) Zachman Framework Viewpoints VIEWPOINT VIEW | Source: https://www.zachman.com/about-the-zachman-framework 39
  • 41. FOUNDATIONS 2.2 Enterprise Continuum & Architecture Repository ‫المؤسسية‬ ‫البنية‬ ‫مستودع‬ ‫و‬ ‫التصنيف‬ ‫نظام‬ 40
  • 42. Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 41
  • 43. Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 42
  • 44. WITHOUT DEFINING “A CLEAR CONTEXT”, PEOPLE DISCUSSING ARCHITECTURE CAN OFTEN TALK AT CROSS-PURPOSES (REFERENCING DIFFERENT POINTS AT THE SAME TIME) Classification System Unclassified Docs - Ad Hoc Store Games Classification of PS Store 1 2 43
  • 45. THE ENTERPRISE CONTINUUM PROVIDES METHODS FOR CLASSIFYING ARCHITECTURE AND SOLUTION ARTIFACTS, BOTH INTERNAL AND EXTERNAL TO THE ARCHITECTURE REPOSITORY Views & Classification System Stakeholder Views of a System Architecture Domains Data Application Technology Business Security Strategy Business Finance BigData Data Mgmt. AI CyberSec. InfoSec. Foundation Extended Solution Architecture Generic Specific B D A T S B D A T S Foundation Common Sys. Industry Org. specific Classification System 44
  • 46. Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 45
  • 47. THE ENTERPRISE CONTINUUM CONSISTS OF THREE PARTS, EACH PART IS CONSIDERED TO BE A DISTINCT CONTINUUM Constituent Parts of the Enterprise Continuum (1/2) Enterprise Continuum Solution Continuum Architecture Continuum Outermost continuum and classifies assets related to the context of the overall Enterprise Architecture Classifies contextual assets used to develop architectures, such as policies, standards, strategic initiatives, organizational structures, and enterprise-level capabilities Consistent way to describe/ understand the implementation of the assets defined in the Architecture Continuum Defines what is available in the organizational environment as re- usable Solution Building Blocks (SBBs) Addresses the commonalities and differences among products, systems, and services of implemented systems Represents a structuring of Architecture Building Blocks (ABBs) which are re-usable architecture assets ABBs evolve through their development lifecycle from abstract/ generic entities to fully expressed Org- Specific Architecture assets Useful tool to discover commonality and eliminate unnecessary redundancy Guide specialized form 46
  • 48. THE ENTERPRISE CONTINUUM CONSISTS OF THREE PARTS, EACH PART IS CONSIDERED TO BE A DISTINCT CONTINUUM Constituent Parts of the Enterprise Continuum (2/2) 47
  • 49. THE ARCHITECTURE CONTINUUM SHOWS THE RELATIONSHIPS AMONG FOUNDATIONAL FRAMEWORKS, COMMON SYSTEMS, INDUSTRY, AND ENTERPRISE ARCHITECTURES … Architecture Continuum Specific Generic Solution Building Blocks SBBs B D A T S B D A T S Foundation Architecture Common Sys. Architecture Industry Architecture Org. specific Architecture Arch. Cont. Solu. Cont. Foundation Architecture Generic components, inter-relationships, principles, and guidelines that provide a foundation on which more specific architectures can be built Common Systems Architecture Use services in Foundation Architecture to create an architecture useful for building common Solutions (high reusable) across a wide number of relevant domains. Org-Specific Architecture Industry Architecture Describe and guide the final deployment of solution components for a particular enterprise Integration of common systems components with industry-specific components (certain vertical industries) 48
  • 50. … THAT AIMS TO DISCOVER COMMONALITY AND ELIMINATE UNNECESSARY REDUNDANCY Architecture Continuum – Examples (1/2) - TRM (Technical Reference Model) - Specific Industry Architecture - e.g. Retail industry's "Active Store" architecture (SCOR- RM) - Energetics Oil and Gas data exchange standards - Bank X Architecture - Gov. Entity Y Architecture - Your Org. Architecture - SOA Architecture - ERP Architecture - Security Architecture - Network Architecture - Management Architecture - Operations Architecture - III-RM FA CSA IA OSA 49
  • 51. SAMPLE COMMON SYSTEMS ARCHITECTURE – SOA REFERENCE MODEL Architecture Continuum – Examples (2/2) Related to BDAT Architecture Domains - Business Service - Data Service - Application Service - Infrastructure Service SOA is an architecture style for Enterprise Architecture 50
  • 52. ALONGSIDE REQUIREMENTS AND PRINCIPLES, ARCHITECTURE CONTINUUM GUIDES, DIRECTS, AND SUPPORT SELECTION, REALIZATION AND DEVELOPMENT OF APPROPRIATE SOLUTIONS Architecture / Solution Continuum 51
  • 53. THE SOLUTIONS CONTINUUM PROVIDES A CONSISTENT WAY TO DESCRIBE AND UNDERSTAND THE IMPLEMENTATION OF THE ASSETS DEFINED IN THE ARCHITECTURE CONTINUUM … Solution Continuum Foundation Solutions Highly generic concepts, tools, products, services, and solution components that are the fundamental providers of capabilities such as: - Professional services: training and consulting services - Support Services: Help Desk Common Systems Solutions - Implementation of a Common Systems Architecture and is comprised of a set of products and services. - Represent collections of common requirements and capabilities, rather than those specific to a particular customer or industry. Org-Specific Solutions Industry Solutions - Implementation of the Organization-Specific Architecture that provides the required business functions - Structured to support specific Service-Level Agreements (SLAs) to ensure support of the operational systems at desired service levels - Implementation of an Industry Architecture, which provides re-usable packages of common components and services specific to an industry. - Industry-specific, aggregate procurements that are ready to be tailored to an individual organization’s requirements Specific Generic Architecture Building Blocks ABBs Foundation Solutions Common Sys. Solutions Industry Solutions Org. specific Solutions Arch. Cont. Solu. Cont. B D A T S B D A T S 52
  • 54. - Third-party solution with Specific Service-Level Agreements (SLAs) - key operating parameters and quality metrics to monitor and manage the organization environment - Specific products, services, and systems solutions that are appropriate to that industry - Physical database schema - An industry-specific point-of- service device … THROUGH DISCOVERTY OF WHAT IS AVAILABLE IN THE ORGANIZATIONAL ENVIRONMENT AS RE-USABLE SOLUTION BUILDING BLOCKS (SBBS) Solution Continuum – Examples - Programming languages - Foundational structures (EDI) - Generic Approaches to Organization structuring - Foundational structures for organizing IT operations (such as ITIL or the IT4IT RA) - Enterprise mgmt. sys. products - Security system products - Scalable data warehousing systems - “Software as a service” common apps solutions FS CSS IS OSS 53
  • 55. Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 54
  • 56. OPERATING A MATURE ARCHITECTURE CAPABILITY CREATES A HUGE VOLUME OF ARCHITECTURAL OUTPUT THAT EMPHASIZE THE ROLE OF EFFECTIVE MANAGEMENT … Architecture Repository Structure (1/2) 55
  • 57. … TO OPERATE AND LEVERAGE THESE WORK PRODUCTS, A FORMAL TAXONOMY IS REQUIRED ALONGSIDE DEDICATED PROCESSES/TOOLS FOR ARCHITECTURAL CONTENT STORAGE Architecture Repository Structure (2/2) Architecture Metamodel Describes the organizationally tailored application of an architecture framework, including a method for architecture development and a metamodel for architecture content Architecture Capability Defines the parameters, structures, and processes that support governance of the Architecture Repository Architecture Landscape * presents an architectural representation of assets in use, or planned, by the enterprise at particular points in time Reference Library Governance Log Arch. Requirements Repository Solutions Landscape Standard Info. Base (SIB) * Provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise Provide a record of governance activity across the enterprise Provides a view of all authorized architecture requirements which have been agreed with the Architecture Board Presents an architectural representation of the SBBs supporting the Architecture Landscape which have been planned or deployed by the enterprise Captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization * Will be further detailed out in the next slides 56
  • 58. DUE TO THE SHEER VOLUME AND THE DIVERSE STAKEHOLDER NEEDS THROUGHOUT AN ENTIRE ENTERPRISE, THE ARCHITECTURE LANDSCAPE IS DIVIDED INTO THREE LEVELS OF GRANULARITY Architecture Repository Structure - Architecture Landscape detailed view Strategic Architectures - Long-term summary view of the entire enterprise - Allow for direction setting at an executive level - Provide an organizing framework for operational and change activity Segment Architectures - More detailed operating models for areas within an enterprise - Can be used at the program or portfolio level - Organize and operationally align more detailed change activity Capability Architectures - Show in a more detailed fashion how the enterprise can support a particular unit of capability (overview about current/ target capability and capability increments) - Allow for individual work packages and projects to be grouped within managed portfolios and programs 57
  • 59. DUE TO THE SHEER VOLUME AND THE DIVERSE STAKEHOLDER NEEDS THROUGHOUT AN ENTIRE ENTERPRISE, THE ARCHITECTURE LANDSCAPE IS DIVIDED INTO THREE LEVELS OF GRANULARITY Architecture Repository Structure - Architecture Landscape Example In Y 2000 Revenue 40M$ In Y 2001 Revenue 50M$ In Y 2002 Revenue 20M$ Why enterprise lose revenue ? Architecture models over time ( years) EA as strategic enabler , help business decisions Enterprise planning space where EA can add true value Business intelligence (Business Analytics) Stakeholder Leave Architecture Landscape Architecture Model 1 Architecture Model 2 Architecture Model 3 Capability Strategic Segmented 58
  • 60. THE STANDARDS INFORMATION BASE IS A REPOSITORY AREA THAT HOLDS A RECORD OF THE SET OF SPECIFICATIONS, TO WHICH ARCHITECTURES MUST CONFORM Architecture Repository Structure - Standards Information Base detailed view Stated in a clear and unambiguous manner, so that compliance can be objectively assessed Easily accessible to projects and therefore the obligations of the project can be understood and planned for Basis for Architecture Governance Standards Information Base (SIB) Business Standards Application Standards Data Standards Technology Standards 59
  • 61. Enterprise Continuum Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬ Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬ Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬ Enterprise Continuum ‫التصنيف‬ ‫نظام‬ 60
  • 62. IMPLEMENTING THE ARCHITECTURE REPOSITORY IN A TOOL WILL CATER FOR STAKEHOLDER ENQUIRIES FOR MODELS, VIEWS, AND REQUIRED ANALYTICS FOR DECISION MAKING EA Tool - key benefits Promote RE-USE Facilitate easier maintenance of the architecture Provide stakeholders with relevant models Enable sharing of architecture information Ensure common terminology is used 61
  • 63. EA Tool - key Features IMPLEMENTING THE ARCHITECTURE REPOSITORY IN A TOOL WILL CATER FOR STAKEHOLDER ENQUIRIES FOR MODELS, VIEWS, AND REQUIRED ANALYTICS FOR DECISION MAKING Impact Analysis Strategic dashboards Workflows Modeling & Heatmapping Dynamic Deliverables EA TOOL KEY FEATURES 62
  • 64. ENTERPRISE ARCHITECTURE AND INNOVATION LEADERS SHOULD SELECT EA TOOLS THAT SUPPORT LONG-TERM BUSINESS TRANSFORMATION, MODERNIZATION AND INNOVATION GOALS EA Tools benchmarking 63 63
  • 65. FOUNDATIONS 2.3 Artifacts, Deliverables and Building Blocks ‫العمل‬ ‫منتجات‬ , ‫المخرجات‬ ‫األساسية‬ ‫والمكونات‬ 64
  • 66. Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 65
  • 67. Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 66
  • 68. Architecture Metamodel ARCHITECTURE METAMODEL OUTLINE HOW AND WITH WHAT THE ARCHITECTURE WILL BE DESCRIBED IN A STRUCTURED WAY TO ENSURE ENTERPIRSE-WIDE CONSISTENCY … Architecture Domains Data Application Technology Business Security Strategy Business Finance BigData Data Mgmt. AI CyberSec. InfoSec. Sample Stakeholders concern Areas Stakeholder Views of a System Phase I Phase II Initial Analysis Detailed Analysis 67 Tailored Metamodel Process
  • 69. Architecture Metamodel … AND GUIDE ORGANIZATIONS TO IMPLEMENT THEIR ARCHITECTURE ASSETS WITHIN AN ARCHITECTURE TOOL Solution Architecture Generic Specific B D A T S B D A T S Foundation Common Sys. Industry Org. specific Tailored Metamodel Pillars Initial Analysis (Phase I) Metamodel Benchmarking Stakeholders Concerns Metamodel Attributes Metamodel Entities Metamodel Relationships Detailed Analysis (Phase II) 68
  • 70. Tailor Architecture Framework ARCHITECTURE FRAMEWORKS PROVIDE SPECIALIZED METAMODEL, THE ROLE OF ARCHITECTURE PRACTITIONER IS TO TAILOR THESE METAMODEL FOR HIS ORGANIZATION PURPOSES 69
  • 71. Togaf Metamodel ARCHITECTURE METAMODEL EXAMPLES (1/3) 70 | Image Source: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap30.html
  • 72. ArchiMate Generic Metamodel ARCHITECTURE METAMODEL EXAMPLES (2/3) 71
  • 74. Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 73
  • 75. Architecture Deliverable DELIVERABLE IS A WORK PRODUCT THAT IS CONTRACTUALLY SPECIFIED AND IN TURN FORMALLY REVIEWED, AGREED, AND SIGNED OFF BY THE STAKEHOLDERS Stakeholder Views of a System ARCHITECTURE ARTIFACTS ARCHITECTURE DELIVERABLES Catalog Diagram Deliverable address stakeholders concerns Output of Architecture Iterations Architecture Development Iterations 74
  • 76. Sample Architecture Deliverables A SET OF ARCHITECTURE DELIVERABLES WILL TYPICALLY BE CONSUMED AND PRODUCED ACROSS ITERATIVE ARCHITECTURE DEVELOPMENT CYCLES ARCHITECTURE DELIVERABLES Architecture Contract Architecture Principles Architecture Repository Architecture Requirements Specification Architecture Definition Document Architecture Roadmap Architecture Vision Business Principles, Business Goals, and Business Drivers Capability Assessment Change Request Communications Plan Compliance Assessment Implementation and Migration Plan Implementation Governance Model Organizational Model for Enterprise Architecture Request for Architecture Work Requirements Impact Assessment … and More Statement of Architecture Work Tailored Architecture Framework 75
  • 77. Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 76
  • 78. Architecture Artifact “ARTIFACT” IS AN ARCHITECTURAL WORK PRODUCT THAT DESCRIBES AN ASPECT OF THE ARCHITECTURE AND FORM THE CONTENT OF THE ARCHITECTURE REPOSITORY ARCHITECTURE ARTIFACTS Catalog Diagram 77
  • 79. Togaf Artifacts TOGAF STANDARD DEFINE A SET OF ARTIFACTS ASSOCIATED WITH ARCHITECTURE METAMODEL … 78
  • 80. Architecture Artifact & Architecture Deliverable … WHERE MULTIPLE ARTIFACTS MAY BE COMBINED TO FORM ARCHITECTURE DELIVERABLE 79
  • 81. Artifacts, Deliverables and Building Blocks Artifacts ‫المؤسسية‬ ‫البنية‬ ‫عمل‬ ‫منتج‬ Deliverables ‫المؤسسية‬ ‫البنية‬ ‫مخرجات‬ Reusable Building Blocks ‫األساسية‬ ‫المكونات‬ Architecture Metamodel ‫للبنية‬ ‫الوصفي‬ ‫النموذج‬ 80
  • 82. Building blocks A BUILDING BLOCK REPRESENTS A (POTENTIALLY RE-USABLE) COMPONENT OF BUSINESS, IT, OR ARCHITECTURAL CAPABILITY … LEGO BUIDLING BLOCKS 81
  • 83. Building blocks Interaction (1/2) … THAT CAN BE COMBINED WITH OTHER BUILDING BLOCKS TO DELIVER ARCHITECTURES AND SOLUTIONS Solution Building Blocks (SBBs) Arch. Building Blocks (ABBs) Describe Contains Many BB: Functionality package defined to meet the business needs Type Of ARCHITECTURE DELIVERABLE ARCHITECTURE ARTIFACTS STAKEHOLDERS CONCERNS CONTENT METAMODEL Classified as Consider implementation and usage, and evolves to exploit technology and standards May be assembled from other building blocks May be a subassembly of other building blocks Ideally re-usable and replaceable, and well specified Boundary and specification should be loosely coupled to its implementation CHARACTERISTICS Stored In ARCHTECTURE REPOSITORY 82
  • 84. Building blocks Interaction (2/2) TOGAF STANDARDS VIEW OF INTERACTIONS BETWEEN METAMODEL, BUILDING BLOCKS, DIAGRAMS, AND STAKEHOLDERS 83
  • 85. 3 Architecture Method & Iterations ▷ADM Introduction ▷ADM Phases Kickstart ▷Scope Architecture Activity ▷Architecture Iteration ▷ADM Phases Deep Dive 84 - ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬
  • 86. ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 85
  • 87. ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 86
  • 88. Architecture Development Method Introduction (1/3) THE ADM ENABLE THE ARCHITECTS TO ENSURE THAT A COMPLEX SET OF REQUIREMENTS IS ADEQUATELY ADDRESSED … 87
  • 89. Architecture Development Method Introduction (2/3) THE ADM ENABLE THE ARCHITECTS TO ENSURE THAT A COMPLEX SET OF REQUIREMENTS IS ADEQUATELY ADDRESSED … Requirements Management Preliminary A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Consider assets produced from previous iterations of the process and external assets Building Blocks Building Blocks Architecture Iteration “SPRINT” Consume BB Publish BB Validation of results against the original requirements SCOPE “BDAT” DETAIL SEGEMENT SCHEDULES MILESTONES Validate BB, Artifacts, Deliverables 1 2 4 5 Produce BB 3 Reconsider … Repeatable process for developing Architectures 88
  • 90. Architecture Development Method Introduction (3/3) … THROUGH ENABLEMENT OF CONTINUOUS ARCHITECTURE ITERATIONS Requirements Management Preliminary A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Cycling around the ADM Circular manner: completion of one phase of architecture work directly feeds into subsequent phases of architecture work Iterating between phases Across Phases: (e.g returning to Business Architecture on completion of Technology Architecture) Cycling around a single phase Repeated execution of the activities within a single ADM phase as a technique for elaborating architectural content Architecture Iteration Levels “SPRINT” 89
  • 91. ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 90
  • 92. Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary Phase Key Activities Establish Enterprise Architecture Operating Model (EAOM) (Capabilities, Processes, Interaction, Governance, Performance KPIs and Tools) Prepare, Initiate required activities to create Architecture Capability Identify the established frameworks, methods, and processes Define Architecture Principles Tailor Architecture Frameworks (Togaf, Nora, DoDAF, ..) ADM PHASES ACTIVITY KICKSTART (1/8) Preliminary 91
  • 93. A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary Requirements Management Requirement Management ADM PHASES ACTIVITY KICKSTART (2/8) Key Activities Identify, stored, and fed architecture requirements into and out of relevant ADM phases Each state validate, address and prioritize requirements Requirement management is central to driving the ADM process 92
  • 94. Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary A. Architecture Vision Phase A – Architecture Vision ADM PHASES ACTIVITY KICKSTART (3/8) Key Activities Set the scope, constraints, and expectations for architecture iterations Define Architecture Vision (Iteration, Partitioning) Identify stakeholders Validate the business context and create the Statement of Architecture Work. Obtain approvals 93
  • 95. A. Architecture Vision E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary Requirements Management B. Business Architecture Phase B – Business Architecture ADM PHASES ACTIVITY KICKSTART (4/8) Key Activities Develop baseline architecture Develop target architecture (needs to operate > achieve business goals > respond to strategic drivers) Analyze gaps between target and baseline architecture Identify candidate Architecture Roadmap components C. Information Systems Architectures D. Technology Architecture 94
  • 96. A. Architecture Vision F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions Phase E – Opportunities and solutions ADM PHASES ACTIVITY KICKSTART (5/8) Key Activities Perform initial implementation planning Identify delivery vehicles for architecture building blocks Determine Incremental Approach, Transition Architecture Solution Architect involved in this phase 95
  • 97. E. Opportunities and solutions A. Architecture Vision G. Implementation Governance H. Architecture Change Mgmt. Preliminary Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture F. Migration Planning Phase F – Migration Planning ADM PHASES ACTIVITY KICKSTART (6/8) Key Activities Develop detailed Implementation and Migration Plan Address Transition Architecture and how to move from baseline to target architecture Overseed, and managed By Project Management Office (Portfolio, Program, Project) Include [cost , time , effort, quality, resource allocation , critical projects and Align other projects through various partitions (strategic , segmented , capability) 96
  • 98. F. Migration Planning E. Opportunities and solutions A. Architecture Vision H. Architecture Change Mgmt. Preliminary Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture G. Implementation Governance Phase G – Implementation Governance ADM PHASES ACTIVITY KICKSTART (7/8) Key Activities Provide architectural oversight for the implementation Prepare and issue architecture contracts Handover your projects to be implemented by [internal dev team , vendor , outsource] Ensure Compliance architecture to our business [I Give you this > You deliver this > What is the gaps] Activate effective architecture governance bodies 97
  • 99. F. Migration Planning E. Opportunities and solutions A. Architecture Vision Preliminary Requirements Management B. Business Architecture C. Information Systems Architectures D. Technology Architecture G. Implementation Governance H. Architecture Change Mgmt. Phase H – Architecture Change Management ADM PHASES ACTIVITY KICKSTART (8/8) Key Activities Continual monitoring, Maintain architecture lifecycle Ensure that the Architecture Governance Framework is executed Ensure that the Enterprise Architecture Capability meets requirements, faster respond to the changing needs Maximize value of architecture practice to business 98
  • 100. ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 99
  • 101. Architecture Activity Scope Constraints THE SCOPE CHOSEN FOR THE ARCHITECTURE ACTIVITY IS NORMALLY DIRECTLY DEPENDENT ON AVAILABLE RESOURCES, AND, IN THE FINAL ANALYSIS, IS USUALLY A QUESTION OF FEASIBILITY Architecture Activity Constraints Stakeholders Concerns Design Authority Structure The objectives and stakeholder concerns to be addressed within the architecture Resources Availability The organizational authority of the team producing the architecture The availability of people, finance, and other resources 100
  • 102. Architecture Activity Scope Dimensions THERE ARE FOUR DIMENSIONS IN WHICH THE SCOPE OF ARCHTIECTUE ACTIVITY MAY BE DEFINED AND LIMITED Breadth What is the full extent of the enterprise ? What part of that extent should the architecting effort deal with? Will the architecture cover suppliers, customers, and partners ? Depth To what level of detail should the architecting effort go? How much architecture is “enough”? What is the appropriate demarcation between the architecture effort and other, related activities (system design, system engineering, system development)? Architecture domains Due to resource and time constraints, There is not enough time, funding, or resources to build a top-down, all-inclusive architecture description encompassing all four architecture domains, so What are the architecture domains (BDAT) that initially should be covered ? Time period What is the time period needed to articulate Arch. Vision? Does it make sense (in terms of practicality and resources) for the same period to be covered in the detailed architecture description? If not, how many Transition Architectures are to be defined, and what are their time periods? Typically, the scope of an architecture is first expressed in terms of breadth, depth, and time. Once these dimensions are understood, a suitable combination of architecture domains can be selected that are appropriate to the problem being addressed Scope of Architecture Activity 101
  • 103. ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 102
  • 104. Architecture Iterations ARCHITECTURE ITERATION IS A TIMEBOX DURING WHICH ARCHITECTURE ACTIVITY TAKES PLACE STARTING WITH ARCHITECTURE VISION AND ENCOMPASS SELECTIVE CROSS-PHASES ACTIVITIES Requirements Management Preliminary A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning H. Implementation Governance H. Architecture Change Mgmt. Architecture Dev. Iteration Architecture Capability Iteration Architecture Governance Iteration Transition Planning Integration Architecture Iterations Architecture Capability Iterations support creation and evolution of the required Architecture Capability (initial mobilization, establishing or adjusting architecture approach, principles, scope, vision, and governance) Architecture Development Iterations allow the creation of architecture content by cycling through, or integrating, Business, Information Systems, and Technology Architecture phases Transition Planning Iterations support the creation of formal change roadmaps for a defined architecture Architecture Governance Iterations support governance of change activity progressing towards a defined Target Architecture 103
  • 105. Baseline-first, Target-first Approaches ARCHITECTURE DEVELOPMENT ITERATION CAN FOLLOW EITHER BASELINE-FIRST OR TARGET-FIRST APPROACH TO IDENTIFY KEY ARCHITECTURE ASSETS IN “BDAT” DOMAINS Baseline-First Approach Target-First Approach 104
  • 106. Architecture Dev. Iteration Typical Architecture Development Iteration ARCHITECTURE DEVELOPMENT ITERATION KEY ACTIVITIES ENCOMPASS COLLECTING KEY STAKEHOLDERS CONCERNS, DESIGN AS IS/TO BE ARCHITECTURE AND ANALYZE GAPS Preliminary E. Opportunities and solutions F. Migration Planning H. Implementation Governance H. Architecture Change Mgmt. Architecture Capability Iteration Architecture Governance Iteration Transition Planning Integration Architecture Development Iteration A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture Requirements Management Architecture Dev. Iteration Key Activities Define stakeholders view , viewpoints , concerns Utilize Reference model if exist , Building blocks if exist Design baseline “AS-IS” architecture according to vision scope Design target “TO-BE” architecture Identify GAP analysis between AS-IS and TO-BE 105
  • 107. Typical Architecture Development Iteration HIGHER-LEVEL ARCHITECTURE USED TO GUIDE AND CONSTRAIN MORE DETAILED ARCHITECTURE, WHERE “MIGRATION PLANNING PHASE” CAN BE USED TO INITIATE NEW MORE DETAILED ARCHITECTURE PROJECTS Strategic Architecture Segment Architecture Capability Architecture 106
  • 108. ARCHITECTURE DEV. METHOD INTRODUCTION ‫المؤسسية‬ ‫البنية‬ ‫مهنجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫المؤسسية‬ ‫البنية‬ ‫منهجية‬ ‫عن‬ ‫مقدمة‬ ADM Overview ‫واالنشطة‬ ‫المنهجية‬ ‫مراحل‬ ADM Phases Activity Kickstart ‫المنهجية‬ ‫نطاق‬ ‫تحديد‬ Scope Architecture Activity ‫الرشيقة‬ ‫البنية‬ ‫منهجية‬ Architecture Iteration ‫البنية‬ ‫تطوير‬ ‫منهجية‬ ‫تفصيل‬ ADM Phases Deep Dive 107
  • 109. DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary ADM Phases Deep Dive 108
  • 110. Preliminary Phase Deep Dive PRELIMINARY PHASE AIMS TO PREPARE, INITIATE ACTIVITIES TO CREATE AN ARCHITECTURE CAPABILITY WITHIN THE ENTERPRISE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 109
  • 111. PRELIMINARY PHASE CHARTER (1/2) 1. Defining the enterprise: Scope of the enterprise, define architecture stakeholders, appoint architecture project sponsor, ensure clear support from business management and involve stakeholders in defining, establishing and using the architecture capability. 2. Identifying key drivers review organizational context: understand the context surrounding the architecture including commercial model and budget, stakeholders, intention and organization culture, current processes, baseline architecture landscape, skills and capabilities of the enterprise 3. Defining the requirements for architecture work: business imperatives need to be articulated to identify key decision makers and stakeholders involved in defining and establishment of architecture capability including business requirements, cultural aspirations, organization intents, strategic intent and forecast financial requirements 4. Defining the Architecture Principles: definition of Architecture Principles is fundamental to the development of EA. Architecture work is informed by business principles as well as Architecture Principles • Determine the Architecture Capability desired by the organization: review organizational context for conducting EA, identify & Scope enterprise elements affected by architecture capability, identify established frameworks, methods and processes and establish capability maturity targets. • Establish the Architecture Capability: define, establish the organizational model for EA, establish architecture governance structure, interaction model and processes, select and impalement tools and define architecture principles • Prepare, initiate activities to create an Architecture Capability • Key activities: understand the business environment, ensure high-level management commitment, obtain agreement on scope, establish Architecture Principles, establish governance structure and customization of architecture framework Description Objectives Approach 110
  • 112. PRELIMINARY PHASE CHARTER (2/2) 5. Defining the framework to be used: Tailoring architecture framework and enhance the operational capabilities of other frameworks in use within an organization. EA Team must be aware of the impact that the architecture has on the entire enterprise 6. Defining the relationships between management frameworks: Dependencies between various frameworks and business planning activities should be defined. EA can be used to provide a structure of the corporate initiatives. Management frameworks are required to complement each other and work in close harmony for the good of the enterprise. 7. Evaluating the Enterprise Architecture’s maturity: Capability Maturity Models (CMMs) are a good way of assessing the ability of an enterprise to exercise different capabilities. CMMs identify factors that is required to exercise a capability. Organization's ability to execute these factors measure the maturity of capabilities which gives executive insights into improving a capability • Determine the Architecture Capability desired by the organization: review organizational context for conducting EA, identify & Scope enterprise elements affected by architecture capability, identify established frameworks, methods and processes and establish capability maturity targets. • Establish the Architecture Capability: define, establish the organizational model for EA, establish architecture governance structure, interaction model and processes, select and impalement tools and define architecture principles • Prepare, initiate activities to create an Architecture Capability • Key activities: understand the business environment, ensure high-level management commitment, obtain agreement on scope, establish Architecture Principles, establish governance structure and customization of architecture framework Description Objectives Approach 111
  • 113. Preliminary Phase Approach PRELIMINARY PHASE SUPPORTIVE ANALYSIS Management Frameworks to Coordinate with EA Framework Interoperability and Relationships between Management Frameworks 112
  • 114. Architecture Vision Deep Dive ARCHITECTURE VISION ESTABLISHES ARCHITECTURE PROJECT AND INITIATES AN ADM ITERATION BY SETTING THE SCOPE, CONSTRAINTS, AND EXPECTATIONS FOR THE ITERATION ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 113
  • 115. ARCHITECTURE VISION CHARTER (1/2) 1. Receive Request for Architecture Work: Sponsoring organization raise a request for architecture work for architecture team. EA Team ensure proper recognition and endorsement from corporate management, the support and commitment of line management for this evolution of the architecture iteration (ADM Cycle). 2. Creating the Architecture Vision: • Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture • Obtain approval for a Statement of Architecture Work: that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision • Establish architecture project and initiates an iteration of the Architecture Development Cycle, setting the scope, constraints, and expectations for the iteration • Create the Architecture Vision, validate the business context, and create the approved Statement of Architecture Work for each architecture cycle Description Objectives Approach • Verify and understand the documented business strategy and enterprise goals • Use business scenarios to discover and document business requirements, and to articulate Architecture Vision that responds to those requirements • Understand emerging technologies and their potential impact on industries and enterprises • Explore other domains appropriate for the Enterprise Architecture; e.g., information, security, digital, network mgmt. , services, cybersecurity • Provide a first-cut, high-level description of the Baseline and Target Architectures • Describe how new architecture iteration will meet the business goals and strategic objectives and address the stakeholder concerns when implemented • Use statement of architecture work to build stakeholders consensus (Architecture Governance) • Architecture sponsoring organization sign the Statement of Architecture work after stakeholders consensus 114
  • 116. Architecture Vision Phase Approach ARCHITECTURE VISION SUPPORTIVE ANALYSIS Business Scenario can be used to identify business and architecture requirements 115
  • 117. Architecture Vision Phase Approach ARCHITECTURE VISION SUPPORTIVE ANALYSIS Architecture vision deliverable content Problem description: Stakeholders and their concerns, List of issues/scenarios to be addressed and change drivers Detailed objectives that need to be fulfilled by the target architecture Use Business Scenario to articulate business emeratives draft necessary views for architecture definition document (ADD) high-level business and technology requirements that map onto the target architecture. Statement of architecture work deliverable content Architecture project request and background Architecture project description and scope Specific change of scope procedures Roles, responsibilities, deliverables, acceptance criteria and procedures Architecture project plan, schedule and approvals Overview and strategic alignment 116
  • 118. Business Architecture BUSIENSS ARCHITECTURE PHASE AMINS TO DEVELOP BUSINESS ARCHITECTURE ASSETS TO SUPPORT AN AGREED ARCHITECTURE VISION ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 117
  • 119. BUSINESS ARCHITECTURE PHASE CHARTER Developing the Baseline Description: Leverage input from Architecture vision to gather more information to develop business architecture artifacts using the following techniques: 1. Applying Business Capabilities : Business Capability Map is a self-contained view of the business that is independent of the current organizational structure, business processes, information systems and applications, and the rest of the product or service portfolio 2. Applying Value Streams: Value streams provide valuable stakeholder context into why the organization needs business capabilities, while business capabilities provide what the organization needs for a particular value stage to be successful 3. Applying the Organization Map: identities the business units or third parties that possess or use those capabilities and which participate in the value streams 4. Applying Modeling Techniques: other additional techniques may be used to enrich business architecture blueprints (i.e Business process models, use case models, …) 5. Using the Architecture Repository: consider what relevant Business Architecture resources are available from the Architecture Repository (i.e reference models and business artifacts and building blocks. • Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures • Develop Business Architecture assets to support an agreed Architecture Vision • Describes the fundamental organization of a business embodied in Its business process and people, their relationships to each other and the people, the principles governing its design and evolution and shows how an organization meets its business goals Description Objectives Approach 118
  • 120. Business Architecture Overview Business Architecture Phase Approach BUSINESS ARCHITECTURE SUPPORTIVE ANALYSIS (1/3) 119 | Bizbok source: https://www.businessarchitectureguild.org/ Business Architecture Definition: A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders. Business Architecture & Other domain Architecture: A knowledge of the Business Architecture is a prerequisite for architecture work in any other domain (Data, Application, Technology), Therefore the first architecture activity that needs to be undertaken Business Architecture & Business Value: - Business Architecture is a means of demonstrating the business value of subsequent architecture work to key stakeholders - Business Architecture outline the return on investment to those stakeholders from supporting and participating in the subsequent work Stakeholders Strategies Policies Capabilities Value Streams Information organization Initiatives Products Metrics Business Architecture Domains
  • 121. Business Architecture Phase Approach BUSINESS ARCHITECTURE SUPPORTIVE ANALYSIS (2/3) Applying Value Streams 120 Applying Business Capabilities Business Capability Map: provides a self-contained view of the business that is independent of the current organizational structure, business processes, information systems and applications, and the rest of the product or service portfolio Mapping to other Business views: Business capabilities should be mapped back to the organizational units, value streams, information systems, and strategic plans within the scope of the Enterprise Architecture project. Value streams: Provide valuable stakeholder context into why the organization needs business capabilities, while business capabilities provide what the organization needs for a particular value stage to be successful. Recommended Techniques: Mapping relationships between the stages in a value stream to business capabilities, and then performing a gap analysis for capabilities in the context of the business value achieved by the value stream for a specific stakeholder
  • 122. Business Architecture Phase Approach BUSINESS ARCHITECTURE SUPPORTIVE ANALYSIS (3/3) Applying Business Modeling 121 Applying the Organization Map The Organization Map: Key element of Business Architecture - Provides organizational context for the whole Enterprise Architecture effort - Identities the business units or third parties that possess or use those capabilities and which participate in the value streams - Provides an understanding of which business units to involve in the architecture effort, who and when to talk about a given requirement, and how to measure the impact of various decisions The modeling and mapping techniques are extensions that implement the business capabilities, value streams, and organization maps Various modeling techniques may be employed when appropriate: Including Business process model, use case model and logical data model
  • 123. Information Systems Architecture DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 122
  • 124. INFORMATION SYSTEMS ARCHITECTURES PHASE CHARTER (1/2) 1. Key Considerations for the Data Architecture: • Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures • Documenting the Information Systems Architectures for an architecture project, including the development of Data and Application Architectures • Describes the major types of information and the application systems that process the information, and their relationships to each other and the environment Description Objectives Approach Data Management: - Defining application components which will serve as the system of record or reference for enterprise master data - Defining enterprise-wide standards that all application components, including software packages, need to adopt - Understanding how data entities are utilized by business functions, processes, and services - Understanding how and where enterprise data entities are created, stored, transported, and reported - Understanding the level and complexity of data transformations required to support the information exchange needs between applications - Defining the requirement for software in supporting data integration with the enterprise’s customers and suppliers (e.g. ETL tools) Data Governance: - Ensure that the enterprise has the necessary dimensions in place to enable the transformation - Structure: Does the enterprise have the necessary organizational structure and the standards bodies to manage data entity aspects of the transformation? - Management System: Does the enterprise have the necessary mgmt. system and data-related programs to manage governance aspects of data entities throughout its lifecycle? - People: What data-related skills and roles does the enterprise require for the transformation? 123
  • 125. INFORMATION SYSTEMS ARCHITECTURES PHASE CHARTER (2/2) 1. Key Considerations for the Data Architecture: 2. Using the Architecture Repository: The architecture team should consider what relevant Data Architecture and Application Architecture resources are available in the organization’s Architecture Repository; in particular, generic models relevant to the organization’s industry “vertical” sector • Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures • Documenting the Information Systems Architectures for an architecture project, including the development of Data and Application Architectures • Describes the major types of information and the application systems that process the information, and their relationships to each other and the environment Description Objectives Approach Data Migration: - When an existing application is replaced, there will be a critical need to migrate data (master, transactional, and reference) to the new application - Identify data migration requirements and provide indicators for the level of transformation, and cleansing that will be required to present data in a format that meets the requirements and constraints of the target application - Ensure that the target application has quality data when it is populated - Ensure that an enterprise-wide common data definition is established to support the transformation 124
  • 126. Technology Architecture DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 125
  • 127. TECHNOLOGY ARCHITECTURE PHASE CHARTER 1. Emerging Technologies – A Driver for Change 2. Using the Architecture Repository: Consider what relevant Technology Architecture resources are available in the Architecture Repository including: • Develop the Target Technology Architecture that enables the Architecture Vision, target business, data, and application building blocks to be delivered through technology components and technology services, in a way that addresses the Statement of Architecture Work and stakeholder concerns • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures • Documenting the Technology Architecture for an architecture project, in the form of the fundamental organization of the IT systems • Embodied in the hardware, software, and communications technology and their relationships to each other and the environment • The principles governing its design and evolution Description Objectives Approach - Technology Architecture needs to capture the transformation opportunities available to the enterprise through the adoption of new technology - As more digital innovations reach the market, stakeholders need to both anticipate and be open to technology-driven change - Part of Digital Transformation has arisen due to convergence of telecommunications and computer capabilities, which have opened up new ways of implementing infrastructures - Technology change become a driver and strategic resource rather than a recipient of Change Requests - Technology Architecture may both drive business capabilities and respond to information system requirements at the same time - Existing IT services - The adopted technical reference model, if applicable - Generic technology models relevant to the organization's industry “vertical” sector; - Technology models relevant to Common Systems Architectures 126
  • 128. Opportunities and Solutions DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 127
  • 129. OPPORTUNITIES & SOLUTIONS PHASE CHARTER (1/2) Opportunities & Solutions Phase Concentrates on how to deliver the architecture • Takes into account the complete set of gaps between the Target and Baseline Architectures in all architecture domains • Logically groups changes into work packages within the enterprise’s portfolios • Build a best-fit roadmap that is based upon the stakeholder requirements, the enterprise’s business transformation readiness • Identified opportunities and solutions, and identified implementation constraints • Focus on the final target while realizing incremental business value • Initial step on the creation of a well considered Implementation and Migration Plan that is integrated into the enterprise’s portfolio in Migration Planning (Phase F) • Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D • Group changes into work packages, assess priorities and identify dependencies • Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value • Define the overall Solution Building Blocks (SBBs) to finalize the Target Architecture based on the Architecture Building Blocks (ABBs) • Decide on approach: Make versus buy versus re-use, Outsource, COTS, Open Source • First phase which is directly concerned with implementation • Describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture identified in previous phases • Perform initial implementation planning, Identify the major implementation projects Description Objectives Approach 128
  • 130. OPPORTUNITIES & SOLUTIONS PHASE CHARTER (2/2) Four key concepts in the transition from developing to delivering a Target Architecture: Architecture Roadmap, Work Packages, Transition Architectures and Implementation and Migration Plan The Architecture Roadmap Transition Architecture Implementation and Migration Plan • Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D • Group changes into work packages, assess priorities and identify dependencies • Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value • Define the overall Solution Building Blocks (SBBs) to finalize the Target Architecture based on the Architecture Building Blocks (ABBs) • Decide on approach: Make versus buy versus re-use, Outsource, COTS, Open Source • First phase which is directly concerned with implementation • Describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture identified in previous phases • Perform initial implementation planning, Identify the major implementation projects Description Objectives Approach 129 • lists individual work packages in a timeline that will realize the Target Architecture • Each work package identifies a logical group of changes necessary to realize the Target Architecture • describes the enterprise at an architecturally significant state between the Baseline and Target Architectures • provide interim Target Architectures upon which the organization can converge • Provides a schedule of the projects that will realize the Target Architecture
  • 131. Migration Planning DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 130
  • 132. MIGRATION PLANNING PHASE CHARTER 1. Key Considerations for Phase F – Migration Planning: • Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan • Ensure that the Implementation and Migration Plan is coordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio • Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders • Addresses detailed migration planning that show how to move from the Baseline to the Target Architectures • Perform a cost/benefit analysis and a risk assessment for work packages and projects identified • Finalize a detailed Implementation and Migration Plan Description Objectives Approach - The focus of Migration Planning Phase is the Creation of an Implementation and Migration Plan in co-operation with the portfolio and project managers - Opportunities and solutions phase provides an incomplete Architecture Roadmap and Implementation and Migration Plan that address the Statement of Architecture Work - In Migration Planning, Roadmap and the Implementation and Migration Plan are integrated with the enterprise’s other change activity - Activities include assessing the dependencies, costs, and benefits of the various migration projects - The Architecture Roadmap, and Implementation and Migration Plan, from Phase E will form the basis of the detailed Implementation and Migration Plan that will include portfolio and project-level detail - The Architecture Development Cycle should then be completed, and lessons learned documented to enable continuous process improvement 131
  • 133. Implementation Governance DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 132
  • 134. IMPLEMENTATION GOVERNANCE PHASE CHARTER - All the information for successful management of the various implementation projects is brought together. The actual development occurs in parallel with implementation governance - Key Aspect of Phase G – Implementation Governance is ensuring compliance with the defined architecture(s), not only by the implementation projects, but also by other ongoing projects - The approach in Phase G is to: 1. Establish an implementation program that will enable the delivery of the agreed Transition Architectures 2. Adopt a phased deployment schedule that reflects the business priorities embodied in the Architecture Roadmap 3. Follow the organization’s standard for corporate, IT, and Architecture Governance 4. Use the organization’s established portfolio/program management approach, where this exists 5. Define an operations framework to ensure the effective long life of the deployed solution • Ensure conformance with the Target Architecture by implementation projects • Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests • Defines how the architecture constrains the implementation projects, monitors it while building it, and produces a signed Architecture Contract • Provide architectural oversight for the implementation • Govern and manage an Architecture Contract and monitor implementation work for conformance Description Objectives Approach 133
  • 135. Architecture Change Management DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 134
  • 136. ARCHITECTURE CHANGE MANAGEMENT PHASE CHARTER 1. The goal of an architecture change management process 2. The value and change management process, once established, will determine: • Ensure that the architecture lifecycle is maintained • Ensure that the Architecture Governance Framework is executed • Ensure that the enterprise’s Architecture Capability meets current requirements • Provide continual monitoring and a change management process and Monitor the business and capacity management • Ensure that changes to the architecture are managed in a cohesive and architected way (controlled manner) • Provide flexibility to evolve rapidly in response to changes in the technology or business environment Description Objectives Approach - Ensure that the architecture achieves its original target business value - Monitoring business growth and decline is a critical aspect of this phase - The circumstances under which the Architecture Development Cycle will be initiated to develop a new architecture and issue a request for architecture work - The circumstances under which the Enterprise Architecture, or parts of it, will be permitted to change after deployment, and the process by which that will happen 135
  • 137. Architecture Change Management Phase Approach ARCHITECTURE CHANGE MANAGEMENT SUPPORTIVE ANALYSIS (1/2) Change Drivers Strategic, top-down directed change: to enhance or create new capability (capital) Bottom-up changes: to correct or enhance capability (operations and maintenance) for infrastructure under operations management Experiences with the previously delivered project increments in the care of operations management, but still being delivered by ongoing projects Change Classification Simplification change: Can normally be handled via change management techniques Driven By: reduce investment Requirement 1 Incremental change: May be handled by change mgmt. techniques or require partial re-architecting, depending on the nature of the change Driven By: derive additional value from existing investment 2 Re-architecting change: Requires putting the whole architecture through ADM Cycle again Driven By: increase investment to create new value for exploitation 3 136
  • 138. Architecture Change Management Phase Approach ARCHITECTURE CHANGE MANAGEMENT SUPPORTIVE ANALYSIS (2/2) Change flow activities Guidelines for Maintenance versus Architecture Redesign REGISTER: All events that may impact the architecture ALLOCATE: Resource and management for architecture tasks ASSESS: What should be done leveraging these architecture resources EVALUATE: Architecture Change impact If the change impacts two stakeholders or more, then it is likely to require an architecture redesign and re-entry to the ADM If the change impacts only one stakeholder, then it is more likely to be a candidate for change management If the change can be allowed under a dispensation, then it is more likely to be a candidate for change management Significant impact for the business strategy – Re-architecting change A new technology/ standard emerges; refresh Tech. Architecture not all EA – Incremental change Change is at an infrastructure level (system reduced, change to 1 system, …) – Simplification change Examples: 137
  • 139. Requirements Management DEEP DIVE ANALYSIS SECTION OUTLINE OBJECTIVES AND APPROACH FOR EACH ADM PHASE ‫األولية‬ ‫المرحلة‬ Preliminary Phase ‫أ‬ ‫المرحلة‬ – ‫البنية‬ ‫رؤية‬ Phase A – Architecture Vision ‫ب‬ ‫المرحلة‬ – ‫األعمال‬ ‫بنية‬ Phase B – Business Architecture ‫ج‬ ‫المرحلة‬ – ‫واألنظمة‬ ‫المعلومات‬ ‫بنية‬ Phase C – Info. Systems Arch. ‫د‬ ‫المرحلة‬ – ‫التقنية‬ ‫البنية‬ Phase D – Technology Architecture ‫ـ‬‫ه‬ ‫المرحلة‬ - ‫والحلول‬ ‫الفرص‬ Phase E – Opp. & Solutions ‫و‬ ‫المرحلة‬ – ‫واإلنتقال‬ ‫التحول‬ ‫تخطيط‬ Phase F – Migration Planning ‫ز‬ ‫المرحلة‬ – ‫التنفيذ‬ ‫حوكمة‬ Phase G – Impl. Governance ‫ح‬ ‫المرحلة‬ – ‫البنية‬ ‫تغيير‬ ‫إدارة‬ Phase H – Arch. Change Mgmt. ‫المتطلبات‬ ‫إدارة‬ Requirements Management Requirements Management A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning G. Implementation Governance H. Architecture Change Mgmt. Preliminary 138
  • 140. REQUIREMENTS MANAGEMENT PHASE CHARTER 1. Key Considerations for Requirements Phase: 2. Architecture Requirements Repository: should be used to record and manage all architecture requirements 3. Business scenarios technique can be used to: • Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases • Manage architecture requirements identified during any execution of the ADM cycle or a phase • Ensure that the relevant architecture requirements are available for use by each phase as the phase is executed • The Requirements Management process is a dynamic process, which addresses the identification of requirements for the enterprise, stores them, and then feeds them in and out of the relevant ADM phases • The ADM is continuously driven by the Requirements Management process Description Objectives Approach - The ability to deal with changes in requirements is crucial, as architecture by its nature deals with uncertainty and change, bridging the divide between the aspirations of the stakeholders and what can be delivered as a practical solution - Requirements Management manage the flow of the requirements : process itself does not dispose of, address, or prioritize any requirements; this is done within the relevant phase of the ADM - Discover and document business requirements, - Describe an Architecture Vision that responds to those requirements 139
  • 141. 4 Guidelines and Techniques ▷Introduction ▷Guidelines ▷Techniques 140 ‫والتقنيات‬ ‫اإلرشادية‬ ‫القواعد‬ -
  • 142. Guidelines & Techniques EA with Specific Architecture Style ‫البنية‬ ‫طراز‬ Architecture principles ‫البنية‬ ‫مبادئ‬ Business Scenarios ‫األعمال‬ ‫سيناريوهات‬ Gap Analysis ‫الفجوات‬ ‫تحليل‬ Business Transformation Readiness Assessment ‫األعمال‬ ‫تحول‬ ‫جاهزية‬ ‫تقييم‬ Risk Management ‫المخاطر‬ ‫إدارة‬ Capability-Based Planning ‫بالقدرة‬ ‫التخطيط‬ Interoperability ‫التوافقية‬ 141
  • 143. Guidelines and Techniques GUIDELINES AND TECHNIQUES CONTAINS A COLLECTION OF GUIDELINES AND TECHNIQUES FOR USE IN ADAPTING AND APPLYING THE ARCHITECTURE ITERATION How to adapt the Architecture method to deal with a number of usage scenarios Examples : - Apply iteration to the Architecture method - Applying Architecture method at different levels of the enterprise ( strategic, segment, capability) - Use the architecture framework with different architectural styles (i.e. SOA, Risk & Security)* Support specific tasks within the Architecture method Examples : - Architecture Principles* - Stakeholder Management - Architecture Patterns - Gap Analysis* - Migration Planning Techniques - Interoperability Requirements* - Business Transformation Readiness Assessment* - Risk Management* - Capability-Based Planning* Guidelines Techniques * Selected guidelines and techniques to be detailed out in the following section 142
  • 144. Guidelines & Techniques Architecture principles ‫البنية‬ ‫مبادئ‬ Business Scenarios ‫األعمال‬ ‫سيناريوهات‬ Gap Analysis ‫الفجوات‬ ‫تحليل‬ Business Transformation Readiness Assessment ‫األعمال‬ ‫تحول‬ ‫جاهزية‬ ‫تقييم‬ Risk Management ‫المخاطر‬ ‫إدارة‬ Capability-Based Planning ‫بالقدرة‬ ‫التخطيط‬ Interoperability ‫التوافقية‬ EA with Specific Architecture Style ‫البنية‬ ‫طراز‬ 143
  • 145. Architecture Style: The combination of distinctive features related to the specific context within which architecture is performed or expressed; A collection of principles and characteristics that steer or constrain how an architecture is formed. Distinctive features for SOA services: Architecture Style – SOA ARCHITECTURE FRAMEWORK SHOULD BE FLEXIBLE AND BE READILY ADAPT TO VARIOUS ARCHITECTURAL STYLES Service Design Mirror real-world business activities – comprising the enterprise (or inter- enterprise) business processes Service representation utilizes business descriptions to provide context (i.e., business process, goal, rule, policy, service interface, and service component) Service Implementation SOA implements services using orchestration Pattern Infrastructure Requirements Recommend service implementation use open standards to realize interoperability and location transparency Environment-specific Implementation Services are constrained or enabled by context and must be described within that context SOA Reference Architecture The Distinctive Features Of An Architecture Style Must Be Identified And considered While Architecture Development 144
  • 146. Architecture Style and ADM ADDRESSING A DISTINCTIVE STYLE SHOULD NOT CALL FOR SIGNIFICANT CHANGES TO THE ARCHITECTURE FRAMEWORK; INSTEAD IT SHOULD ADJUST THE MODELS, VIEWPOINTS, AND TOOLS Requirements Management Preliminary A. Architecture Vision B. Business Architecture C. Information Systems Architectures D. Technology Architecture E. Opportunities and solutions F. Migration Planning H. Implementation Governance H. Architecture Change Mgmt. Preliminary Phase Phase B,C,D Addressing the distinctive features will usually include extensions to the Architecture Content Metamodel and the use of specific notation or modeling techniques and the identification of viewpoints Architecture Metamodel Architecture Tool Select the relevant architecture resources, including models, viewpoints, and tools, to properly describe the architecture domain and demonstrate that stakeholder concerns are addressed Architecture Definition Document 145