Chapter 1: The Concept of Enterprise Architecture PDF

Chapter 1: The Concept of Enterprise Architecture D R. P I L I TA A G A S - A M A H A N A S S O C I AT E P R O F E S S O R I V D O C T O R I N I N F O R M AT I O N T E C H N O L O G Y “Opportunity does not happen; You need to create them.”  Class Orientation (Aug 12-16) Course Title: Sy...

Chapter 1: The Concept of Enterprise Architecture D R. P I L I TA A G A S - A M A H A N A S S O C I AT E P R O F E S S O R I V D O C T O R I N I N F O R M AT I O N T E C H N O L O G Y “Opportunity does not happen; You need to create them.”  Class Orientation (Aug 12-16) Course Title: System Integration and Architecture 2 (PL4107) ▪ This course is the continuation of PC3105. The emphasis of this subject is to construct an architectural model of a complex system using an architectural framework, summarize and analyze the data from a usability test and recommend appropriate actions. ▪ 5 Units (2 Hours Lecture and 3 Hours Laboratory Works)  Class Orientation Course Requirements: Grading System: ▪ Class activities Class Standing =30% ▪ Presentations Mid-Term/Final Examination =30% ▪ Attendance Laboratory =40% 100% ▪ Recitations ▪ Assignments *Final Rating = Midterm (40%) + Final Term (60%) ▪ Quizzes ▪ Projects ▪ Laboratory activities ▪ Midterm and Final term Examination Class Orientation Course Policies: Attendance 1. Students having seven (7) absences without valid reasons will be dropped from the class. Students are required to present admit to class slip from the Office of Student Affairs and Services after being absent in the previous meeting. 2. Three (3), not necessarily consecutive, tardiness without further notice is equivalent to one (1) absence. Incomplete Grade: 1. Students who were not able to complete the time given requirement. Incomplete grade should be complied within one year. Chapter 1: The Concept of Enterprise Architecture (Aug 19-Sept 20) Desired Learning Outcomes: ▪ Analyze the appropriateness of a decision to in-source or out-source IT services in a given situation. ▪ Analyze both quantitative and qualitative data gathered from usability tests using programming languages like R or Python, incorporating statistical analysis of quantitative data and thematic analysis for qualitative data. ▪ Summarize and analyze the data from a usability test and recommend appropriate actions.  1.1 Architecture Defined ▪An Architecture is the fundamental organisation of a system, embodied in its services and components, their relationships to each other and the environment, and the principles governing their design and evolution. 1.1 Example of an Architecture 1.2 Enterprise Architecture Defined ▪An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operations of organizations. The intent of enterprise architecture is to determine how an organization can effectively achieve its current and future objectives. 1.3 Purpose of EA ▪Enables organizations to align their business strategies with technology solutions, thereby improving their efficiency and reducing risks. 1.4 Objectives of EA ▪To create a map of IT assets and business processes and a set of governing principles that drive an ongoing discussion about business strategy and how it can be expressed through IT. 1.5 Benefits of EA Flexibility ▪Fast changing work-processes and workflows need flexible access to functions and data. ▪High barriers between systems are falling or changing to small boundaries as modularity is growing. ▪A good system integration architecture and the appropriate middleware are helping to provide this flexibility 1.5 Benefits of EA Speed ▪Where functions and data have to be used across systems, middleware speeds development and changes (in the long terms, but not necessarily in the short term). 1.5 Benefits of EA Cost ▪Where functions and data have to be used across systems, middleware speeds development and changes (in the long terms, but not necessarily in the short term). ▪the costs of building and maintaining unique one-to-one integration between systems is rapidly growing for larger systems ▪A hub-and-spoke approach is more efficient. Middleware can act as a hub. 1.5 Benefits of EA Data Integrity, reliability, and robustness ▪as more and more data are used across systems and different work processes, a system integration architecture and some middleware solutions ensure the data integrity across systems and situations of use. ▪For horizontal systems, efforts spent in making the evolution reliable, secure and robust can be concentrated in the service layers rather than distributed over single applications. 1.5 Benefits of EA New Products and Services ▪easy and secure access to information across systems opens up opportunities for new products, especially on new delivery platforms. 1.5 Benefits of EA Overview ▪as common ways of achieving integration are established, the organization gets a better overview; both due to the standardization and to the needed repository of information about systems, functions, data, integrations, interfaces and metadata. ▪This opens up opportunities for stronger change management routines. More specifically, the ability to search within data across systems is improved. System planning: standardization allows 1.5 Benefits of EA System Planning ▪standardization allows technical planning departments to use tools which will make the planning process much easier. ▪The focus will no longer be fixed on specific technical problems but much more on workflows, or rather on optimizing the workflows. Planning of complex broadcast-systems in future could be much more like “Lego ”. 1.5 Benefits of EA Training ▪an understanding of the workflows in which the operators are involved will become more necessary in the future than today. ▪Therefore, not only will dedicated technical training for a device or software application be necessary, but also education on understanding the whole production chain. This can become much simpler if the system architecture is based on generic and pre- defined processes rather than on proprietary structures.  1.6 Risks of no EA Failure to implement an EA will present the ff risks: Inability to rapidly respond to challenges driven by Lack of focus on enterprise requirements business changes Lack of common direction and synergies Incomplete visibility of the current and future target EA vision Inability to predict impacts of future changes Increased gaps and architecture conflicts Lack of commonality and consistency due to the Dilution and dissipation of critical information and absence of standards knowledge of the deployed solutions Rigidity, redundancy and lack of scalability and Lack of integration, compatibility and flexibility in the deployed solutions interoperability between applications Complex, fragile and costly interfaces between Decision-making gridlock incongruent applications 1.7 EA Initiatives LD1-Discussion