Enterprise Architecture Lec1 PDF

# Enterprise Architecture Dr/Mai Ramadan Ibraheem 808011209156 Lecturer at Information Technology Dept., Faculty of Computers and Information – KFS University ## Context and Need for Architecture In simple endeavors, for example, construction of a mud hut, a formal architecture blueprint may not...

# Enterprise Architecture Dr/Mai Ramadan Ibraheem 808011209156 Lecturer at Information Technology Dept., Faculty of Computers and Information – KFS University ## Context and Need for Architecture In simple endeavors, for example, construction of a mud hut, a formal architecture blueprint may not be needed to ensure successful construction and subsequent maintenance. Greater the complexity of the endeavor, greater is the necessity of a guiding blueprint. Blueprint is also essential to undertake further development or make modifications. For significantly large endeavors, not only is a blueprint essential, a phased plan/roadmap is a must. Building large, complex, enterprise-wide information systems without an enterprise architecture is like trying to build a city without a city plan. Can you build a city without a city plan? Probably Yes. Would you want to live in such a city? Probably not. | Township | State | Enterprise and Partner Systems | | --------------- | ------------ | ------------------------------ | | Hut | Service | Module | | Wood Cabin | Agency | Package (HRMS) | | Urban House | Department | ERP (FMIS, HRMS, ...) | | Residential Tower | Sector | ERP, CRM, SCM,... | | Gated Community | State | --- | | Architecture for Construction | Architecture for Service Delivery in State | Architecture for Information Systems of Enterprise | ## Complexity due to Size and Scale ## Enterprise Architecture - A Recap ### Context and Need for Enterprise | Township | State | Enterprise and Partner Systems | | --------------- | ------------ | ------------------------------ | | Hut | Service | Module | | Wood Cabin | Agency | Package (HRMS) | | Urban House | Department | ERP (FMIS, HRMS, ...) | | Residential | Sector | ERP, CRM, SCM,... | | Gated Community | State | --- | | Architecture for Construction | Architecture for Service Delivery in State | Architecture for Information Systems of Enterprise | ### Dynamics of Change ## Defining Enterprise Architecture - Enterprise: Any collection of organizations that have common goals - Union Government or State Government at broader level - Individual Ministry or Department at narrower level - Enterprise Architecture: Description of the current and future services, processes and information systems of the enterprise aligned with its vision. ## How to define Enterprise Architecture - There is a process of architecting which is prescribed by the discipline of EA. - It produces outputs that describe the architecture of an enterprise. - The process of architecting involves, taking stock of the relevant components or building blocks that make up an enterprise. - An architect then needs to examine how these components enable or constrain the enterprise in fulfilling the goals of the enterprise. - This is done by looking at how the components are organized or configured, how they are used or how they behave or perform together - Study the enterprise in its current state and how it should be in the future. Work out the alternatives for moving from the current state to the future target state. - Create frameworks to manage the architecture, spell out descriptions of the architecture and its components and road maps to show the best way to change or improve the architecture. - Assess the constraints and opportunities, costs, benefits, risks and value in each option to help decision makers to select the best alternative. ## Value of Architectural Thinking - Public transit, schools and parks are afterthoughts - No common services - Inefficient and fragmented processes - Aesthetically unpleasing - Limited scope for growth - Future-oriented, planned and sustainable - Common services - Principles and standards (fire, safety, master plan) - Higher productivity and effectiveness - Aesthetically pleasing ## Enterprise Architecture is Analogous to City Planning for an Enterprise | Project focus | Enterprise-wide focus | | ----------- | ----------- | | | Governance Strategy | | | IT Strategy | | | Enterprise Architecture | | | Governance | | | Architecture | | | Service | | | Process | | | People | | | Aligning Change to Business Need | | | IS/IT Architecture | | | Information | | | Application | | | Technology | | | Transitic Planning | | Government Processes & IT Systems | | Enterprise Architecture: "the city plan" Solution: "the building design" ## EA - The Building Blocks | IT | Business | | | ---- | -------------- | ---------------------------- | | | Strategy & Performance Architecture | | | Service & Function Architecture | | | Architecture | | Security Architecture | | Capabilities & Processes | | | | Services & Products | | | | Data Architecture | | | | Application Architecture | | | | Technology Architecture | | | | Architecture Governance & Management | ## EA Leveraged to Plan and Manage Transformations - Target State - Transition State 2 - Transition State 1 - Step 2 - Step 1 ## Benefits of Enterprise Architecture - Increased efficiency of service delivery - Improved effectiveness of scheme implementation - Higher Rol from investments in technology, through common, re-usable components - Increased innovation enabled by a defined architecture and its governance - Increased agility through quicker technology changes in response dynamic business changes - Seamless interoperability between systems ## Decisions in Enterprise Architecture - Should we use a common set of applications across different programs / services OR develop independent applications? - Which systems must we develop / enhance / retire? - Which data area / elements must we standardize across the enterprise? - What enterprise-wide interfaces should our systems provide? - Should we standardize the technology we use? - What kind and which current or upcoming technologies should we invest in? ## Key Takeaways - Enterprise architecture: - is to understand the enterprise on a holistic basis (business, technology and operating environment) - helps effectively direct the enterprise to deliver strategic goals by aligning business and technology operations to strategic intent - We need enterprise architecture to: - improve service delivery efficiency and scheme implementation effectiveness by improving alignment of business & technology to strategic intent - increase agility by making faster changes in response to dynamic business - increase Rol from technology investments through optimized landscape enabled by common & re-usable components ## End ## Thank You