A Crash Course on ... ENTERPRISE ARCHITECTURE (EA) ( For Application and System Developers , IT professionals, Software engineers , Software Architects , Computer engineering Professors , System Analysts , System Administrators , Computer Science / Computer engineering/software engineering Students , Solution Architects, and so on ...) - Bhuwan Bhatt Software Engineer, RoR Developer Narmada Infosys Student of Computer Science , Far-Western University , Nepal ENTERPRISE ARCHITECTURE (EA) Chapter 1: Overview 1 what is architecture ? Architecture is the craft of the master builders 2. what is an Enterprise ? Enterprise means any entity or an organization . OR an single business unit OR collaborative approach to fulfill an objective to complete an goal to provide value to people 3. why do an enterprise needs an Architecture ? basically To handle Complex IT systems OBJECTIVE OF THIS MODULE !! 1. A working definition of enterprise architecture 2. Overview of the modules of the course Lets jump into the Subject ....... chapter 2 : ENTERPRISE ARCHITECTURE Enterprise Architecture is a discipline which enables designing the enterprise consciously and deliberately rather than letting it happen randomly . This design is informed by business vision , strategic intent and insights on functioning of the enterprise . when we say design it implies knowledge of a certain intented outcome or desired state . Mainly it includs target state . It also clears abouot the direction of enterprise where it goes .. Enterprise architeture provides various frameworks, tools, viewpoints and pespectives to comprehened the current state , articulate the target satate and enables road mapping the journey from curent state to its Goal State .. Enterprise Architecture Current State of Enterprise Target State of Enterprise Enterprises Are Complex Adaptive Systems Complex Adaptive systems (CAS) are systems characterized by complex behaviors that result from non-linear interactions among large numbers of components in time and space at various levels of organizations. An great example is Car . If we want to change the components from one car to another car it does not work properly . Because the Architecture of car is designed in such a way that it can not copied simply ! So our enterprise system should not be copied easily . Which Is primarily because of Its Inter- Connectivity, interactions and inter relationships gives rise to complexity . Chapter 3 : Making Sense of Plurality of Perspectives (History Of EA) We can see this clearly that today’s way of doing business is totally different from the businesses of 1960s or 1970s . This is because of nature of problems that belongs to business and The Overall Environment in which they operate . T he main factors which has changed in business 1. Nature of problems 2. Business Environment 3. opportunities 4. Business Models 5. Distributions channels 6. Supply and demand chain 7. Market 8. Customer Expectations 9. How they Access Products and services 10. Globalized competitive business plans the above are the factors that should be considered before making any product and enterprise plans . EA began as a discipline to architect IT Systems . Enterprises are like big cities ; they evolve the old the new The Brain The immune system The Society Ecosystem EA practice is evolving keeping pace with the need of an evolving enterprise. Chapter 4: Overview of Modules Enterprise Architecture Domains : L ist of Subsequent Modules ; 1. Introduction to EA 2. EA Frameworks 3. Business Architecture 4. Applications Architecture 5. Information Architecture 6. Infrastructure Architecture 7. Other Architecture Disciplines 8 . Enterprise Architecture Roles 9 . Agile & Enterprise Archite c ture Business Architecture Information System Architecture Technology Architecture (Infrastructure ) Applications Architecture Information Architecture