IBITS Year 18, Semester Midterms - Systems Integration PDF

LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Module 1: Introduction to Systems Integration & Enterprise FOU...

LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Module 1: Introduction to Systems Integration & Enterprise FOUR STAGES OF SYSTEM INTEGRATION Architecture System integration can be achieved at different levels, which are labeled as follows: IMPORTANCE OF IT IN ORGANIZATIONS ○ Interconnectivity ○ Functional Interoperability The influence of IT Systems on business models is ○ Semantic Interoperability continuously increasing. ○ Optimization and Innovation Drivers for Information systems often become a backbone of major Systems Integration organizational changes and transformations. A combination of several factors have stimulated and The purpose of IT is to improve the quality of business facilitated system integration projects. These are: processes that require consistent and coordinated ○ Advances in computer networks and changes in the 3 broad organization aspects. information processing. ○ People: Training and Education to system ○ Globalization. users. ○ Need for organizational agility to cope with ○ Processes: Introducing new improved competition and rapid development. business processes enabled by system. ○ Market positioning through customization of Decision making procedures and rules. products and services. ○ Technology: Setting up new IT systems and ○ Regulatory compliance. required infrastructure. Providing technical and help desk support to ISSUES IN ENTERPRISE/SYSTEM INTEGRATION users. Current enterprise (or system) integration plans pose Information systems can help organization executes their significant challenges due to the following issues: business strategies and gain competitive advantage in ○ Nature of networking technology. terms: ○ The difficulties of standardization. ○ Operational Excellence and Cost Leadership ○ The security threat to institutions and ○ Product differentiation and leadership individuals. ○ Customer Intimacy and focus DEFINING ENTERPRISE ARCHITECTURE DEFINING SYSTEMS INTEGRATION Enterprise Architecture (EA) is the practice of analyzing, System integration is closely related to enterprise designing, planning and implementing enterprise integration which is concerned with facilitating analysis to successfully execute on business strategies. information, control, and material flows across EA helps businesses structure IT projects and policies to organizational boundaries by connecting all the achieve desired business results and to stay on top of necessary functions and heterogeneous functional industry trends and disruptions using architecture entities (information systems, devices application, and principles and practices, a process also known as people). enterprise architecture planning (EAP). Enterprise Application Integration (EIA) was one of the first architectural concepts to bring together the various HISTORY heterogeneous applications and information systems of an enterprise. The goal was to integrate the various 1960 - Enterprise Architecture born from “various platforms, tools, and applications spread across various architectural manuscripts on Business Systems Planning departments and areas separated by organizational (BSP) by Professor Dewey Walker”. boundaries, so that they could access the same data and John Zachman, one of Walker’s students, helped communicate using a common protocol. formulate those documents into the more structured format of EA. Zachman published the framework in the IBM Systems Journal in 1987. 1980s - The EA framework came as a response to the increase of business technology, when computer systems were just taking hold in the workplace. COURSE CODE LESSON # 1  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Modern EA strategies now extend this philosophy to the ENTERPRISE ARCHITECTURE METHODOLOGIES entire business, not just IT, to ensure the business is According to CompTIA, these are four leading Enterprise aligned with digital transformation strategies and Architect Planning (EAP) methodologies: technological growth. The Open Group Architectural Framework (TOGAF). EA is especially useful for large businesses going through ○ TOGAF provides principles for designing, digital transformations, because it focuses on bringing planning, implementing and governing legacy processes and applications together to form a enterprise IT architecture. more seamless environment. ○ The TOGAF framework helps businesses create a standardized approach to EA with a common vocabulary, recommended standards, GOALS OF ENTERPRISE ARCHITECTURE compliance methods, suggested tools and EA is guided by the organization’s business requirements software and a method to define best - it helps lay out how information, business and practices. technology flow together. The Zachman Framework for Enterprise Architecture. “The framework successfully combines people, data ○ The Zachman framework is named after one of and technology to show a comprehensive view of the the original founders of enterprise architecture inter-relationships within an information technology and it’s another popular EA methodology. organization,” ○ It’s better understood as a “taxonomy”, The process is driven by a “comprehensive picture of an according to CompTIA, and it spans six entire enterprise from the perspectives of owner, architectural focal points and six primary designer and builder.” stakeholders to help standardize and define A good EAP strategy considers the latest innovations in the IT architecture components and outputs. business processes, organizational structure, Federal Enterprise Architecture Framework (FEAF). information systems and technologies. ○ FEAF was introduced in 1996 as a response to The ultimate goal of any EAP strategy is to improve the the Clinger-Cohen act, which introduced efficiency, timeliness and reliability of business mandates for IT effectiveness in federal information. agencies. ○ It’s designed for the U.S. government, but it can also be applied to private companies that BENEFITS OF ENTERPRISE ARCHITECTURE want to use the framework. EA can offer support for re-designs and Gartner. re-organizations, especially during major organizational ○ After acquiring The Meta Group in 2005, changes, mergers or acquisitions. Gartner established best practices for EAP and adapted them into the company’s general EA is also used in system development, IT management and decision-making, IT risk management to eliminate consulting practices. errors, system failures and security breaches. ○ While it’s not an individual framework, CompTIA recognizes it as a “practical” The biggest benefits of EAP include: methodology that focuses on business ○ Allowing more open collaboration between IT and business units outcomes with “few explicit steps or components.” ○ Giving business the ability to prioritize investments ○ Making it easier to evaluate existing These are just four of the most commonly referenced architecture against long-term goals and recognized EA methodologies, but others exist. For example, there’s the European Space Agency ○ Establishing processes to evaluate and procure technology Architectural Framework (ESAAF), the Ministry of Defense Architecture Framework (MODAF) and the SAP ○ Giving comprehensive view of IT architecture to all business units outside of IT Enterprise Architecture Framework. These frameworks are specifically targeted to individual industries or ○ Providing a benchmarking framework to compare results against other organizations or products, targeting more of a niche market than the standards more generalized EA methodologies listed above. COURSE CODE LESSON # 2  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms ENTERPRISE ARCHITECT ROLE Enterprise architects typically report to the CIO or other IT managers. They’re responsible for analyzing business structures and processes to see that they align with business goals effectively and efficiently. As an enterprise architect, you’ll also be responsible for ensuring these structures and processes are agile and durable, so they can swiftly adapt and withstand major change. Module 2: Overview of Enterprise Architecture Frameworks Lesson 1: The Enterprise Architecture Framework Definition of EA Framework: EA frameworks are structured approaches to aligning IT systems with business goals. Provides a layered approach to help design, implement, and manage enterprise architecture Four Key Characteristics of EA 1. Skeleton/Structure COURSE CODE LESSON # 3  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Acts as the foundational outline that defines Subcontractor: Focuses on detailed all components. specifications and parts. Helps identify what is needed within each Functioning Enterprise: Represents layer of the architecture. the operational view after implementation. 2. Classification of Schema or Ontology Schema: Organizes EA components based on ○ Columns (Abstractions): shared characteristics, making it easier to What (Data): Defines the material or understand the elements involved. data necessary. Ontology: Defines relationships and properties How (Function): Outlines processes between components, showing how different and functionality. elements interact within EA. Where (Network): Determines physical or virtual locations. 3. Thinking Tool Who (People): Describes roles and Serves as a tool to plan and visualize the EA’s responsibilities. development. When (Time): Focuses on timing and Provides flexibility to adapt the EA as the schedules. organization evolves, helping decision-makers Why (Motivation): Examines reasons explore different configurations. and objectives. 4. Management Tool Advantages: Supports organizations in progressing from the ○ Holistic Enterprise View: Offers a complete current state to a desired target state. view of the enterprise, enabling stakeholders Acts as a roadmap, ensuring that the to understand the entire architecture. architecture remains aligned with the ○ Tool-Independent: Can be adapted to different organization’s strategic needs. tools and methodologies, enhancing flexibility. ○ Focus on Decision-Making: Organizes information systematically, which supports informed decision-making across the Lesson 2: The Zachman Framework for Enterprise enterprise. Architecture Background: ○ Developed by John Zachman at IBM in the 1980s. ○ Inspired by the structured methods seen in construction and aviation industries. ○ Known as a “taxonomy,” rather than a strict Drawbacks: methodology. ○ Complexity: Contains numerous cells, making ○ it challenging for practical application. Structure of the Zachman Framework: ○ Unclear Relationships: The framework does ○ Organized into a matrix with rows representing not define clear connections between cells, different roles and columns representing key which can complicate understanding. abstractions (or questions). ○ Lacks Step-by-Step Guidance: Provides a ○ Rows (Perspectives): structure but no specific methodology for Planner: High-level, strategic view of building EA, requiring additional planning from requirements. users. Owner: Focuses on business ○ Limited Future Evaluation: Offers no built-in requirements and what is needed. method for assessing future architecture Designer: Provides technical design efficiency or effectiveness. perspectives. Builder: Specifies the components and materials needed. Lesson 3: The Open TOGAF Framework COURSE CODE LESSON # 4  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms ○ Reduces Risk: By following open standards, History: TOGAF minimizes risks associated with system ○ Based on the U.S. Department of Defense’s interoperability and future upgrades. Technical Architecture Framework for ○ Scalability and Flexibility: Provides the Information Management (TAFIM). structure to support future growth, making it ○ Developed and maintained by The Open Group suitable for both large and small organizations. since 1995, TOGAF is one of the most popular EA frameworks. Additional Topics Comparison of EA Frameworks: Core Components of TOGAF: ○ Zachman: Ideal for high-level understanding; 1. Architecture Capability Framework: focuses on perspectives and abstractions but Details the necessary roles, skills, does not provide a step-by-step approach. processes, and responsibilities for ○ TOGAF: Detailed and prescriptive, popular for managing EA. its structured ADM and adaptability to Ensures that organizational structure complex organizations. supports architecture objectives and ○ FEAF (Federal Enterprise Architecture capabilities. Framework): U.S. government-focused, useful 2. Architecture Development Method (ADM): for regulatory needs, but adaptable to private The central process of TOGAF, organizations. providing a phased, step-by-step ○ Gartner: Business-focused with fewer explicit approach for developing EA. steps; emphasizes outcomes and business ADM phases include architecture results, making it flexible for custom use. vision, business architecture, information systems architecture, Role of an Enterprise Architect: and technology architecture. ○ Reports to the CIO or IT leadership, ensuring 3. Architecture Content Framework: that business structures and processes align Provides a structured metamodel to with business goals. create and organize EA artifacts (e.g., ○ Responsible for designing flexible and resilient diagrams, documents). structures that can adapt to change. Helps define and manage reusable ○ Involved in identifying the architecture’s building blocks, ensuring that alignment with business goals, maintaining architectures are consistent and agility, and ensuring sustainability. standardized. 4. Enterprise Continuum & Tools A taxonomy for organizing, storing, and categorizing architecture outputs. Supports reuse of components across projects and ensures consistency within the organization. Benefits of TOGAF: ○ Standardization and Consistency: Promotes a consistent approach across all architecture initiatives, making collaboration easier. ○ Alignment with Business Goals: Ensures that EA development aligns with organizational objectives, enabling IT to support business strategies effectively. COURSE CODE LESSON # 5  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Module 3: Components of Enterprise Architecture generated/required by a Unit of work and is subsequently passed to another unit of work. COMPONENTS OF ENTERPRISE ARCHITECTURE ○ Data Description (What does the data mean?) The Four Primary components of Enterprise Architecture are: Structured - Organized description of Enterprise Business Architecture data to convey semantic Enterprise Information Architecture understanding usually through an Enterprise Solution Architecture entity relationship diagram. Enterprise Technology Architecture Semi Structured - Has characteristics of both Structured and Unstructured The components of Enterprise Architecture: such email. Unstructured - More free-form format such as unstructured text. ○ Data Context (How do I find the data and access it?) Subject Area - Broad Categories of data that supports business processes. Information Class - Groupings of lines of business or community of interest. II. Enterprise Solution Architecture (ESA) Collection of information systems supporting or related I. Enterprise Business Architecture (EBA) to the business functions defined by EBA and the Documents the business strategy, governance, enterprise business model. organization and business functions. Includes applications and components that are Establishes a baseline that defines which organizations purchased or custom-developed. perform these functions. Also known as Enterprise Application Architecture Provides a holistic view of our state government from a business perspective. ESA includes: Answers questions like: Who we are?, What we do?, and 1) Inventory Solutions, applications, and components Where we want to go? currently used to support business functions in an Gives a common reference model of citizens, businesses, enterprise. members of General Assembly, current and future 2) Analysis of current/baseline solutions, and current administrations, and other interested parties that helps technology tools supporting existing automated define the business of state of government. solutions. 3) Future-state recommendations of automated solutions II. Enterprise Information Architecture (EIA) and related tools. Provides a framework, model, and method to enhance 4) ESA governance and implementation requirements. each agency's ability to quickly discover access, and understand data, while creating information needed to support critical agency business function decisions. III. Enterprise Technical Architecture (ETA) EIA must have three components that contain Is a consistent set of IT standards and models that: information about the enterprise’s data assets: ○ Reflect and support EBA, EIA, and ESA components. ○ Data Sharing (How do I exchange the data?) ○ Guides the engineering of emerging IS and Information Exchange and Query technology infrastructure. Points – Information COURSE CODE LESSON # 6  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms ETA Domains: instances of data describing the core business entities, Security such as customer or product data. Enterprise System Management Information 3. Operational Data Domain Database transactional data capturing data, which is derived Applications from business transactions. Integration Platform 4. Unstructured Data Domain Networking and Telecommunications Known as Content typically managed by an enterprise content management application. 5. Analytical Data Domain Usually derived through transformation from Module 4: Enterprise Information Architecture Concepts operational systems to address specific requirements of decision support applications. OVERVIEW The HEART of IA is information and knowledge IT Governance and Information Governance IT Governance is the key to deriving architectural EIA’s should better understand their: decisions Organization’s business strategy & what good architectural decisions are (nearly impossible Integrate the strategic vision because it is problem and context specific ○ Can be done with a good IT governance we describe a typical governance framework to help framework drive architectural principles, policies, and decisions Conceptual as well as on the Logical Layer, both represent well-defined layers describing the EIA Reference Architecture. Standard of IT Governance COBIT (Control Objectives for Information and related LESSON 1: EIA DATA DOMAINS, INFORMATION Technology) Standard owned by the IT Governance Institute GOVERNANCE, AND INFORMATION SECURITY From the COBIT perspective, IT Governance is considered a framework to govern IT assets over their Data Domains lifecycle. classifies information assets used for specific purposes Good IT Governance - supports and extends the where the purpose identifies usage patterns with a company strategies and business objectives dedicated set of capabilities. Certain types of data might be used enterprise-wide or only locally IT Governance is tightly coupled with the following: Data might be structured or unstructured 1. IT principles High-level statements about how IT will be used to Five Data Domains create business value and a generic information-centric set 1. Metadata Domain “Data about data” 2. IT architecture is the information that describes the characteristics of The set of technical choices that guide the enterprise in each piece of corporate data asset and other entities. satisfying business needs. 2. Master Data Domain 3. IT infrastructure strategies COURSE CODE LESSON # 7  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Describes the approach to building shared and external systems to protect data from unauthorized standard IT services across the enterprise access. Regulatory compliance pressures around the world 4. Functional business requirements across all industries demand strict enforcement of data Applications that need to be acquired or built access and Information Privacy. Access by partners to internal systems is ever increasing 5. Prioritization of IT investments as the new trends to distributed solutions and where they should be focused and the procedures for cooperation across business boundaries take place. progressing initiatives, their justification, approval, and As systems design leads to more consolidated data sets accountability. (around core enterprise-wide DW and MDM capabilities), the opportunity to hack one’s critical resource can actually increase Information Governance the orchestration of people, processes, and technology to enable an organization to leverage information as an Areas in which we must address Information Security in our enterprise asset. business: specifically details the area associated with managing issues (ex. Incomplete data) 1. Business Security Services Key objective: first establish a culture that recognizes Defined as security aspects of the business that must be the value of information as an enterprise asset. specified, owned, and managed for successful and requires real discipline and possibly the creation of new secure operations of an enterprise. roles within the business that didn’t exist previously Driven by regulatory concerns, partnerships, competitive influences, and more. Development of effective IG drives value into companies: 2. IT Security Services Compliance and regulatory adherence satisfies auditors Form the core technical components and regulators must be designed and deployed around our data Enhanced BI capabilities using high-quality information domains drives new opportunities for organic growth deliver the security functions as defined in the Business Enhanced alignment of IT initiatives with business Security Services layer. strategies responsible for addressing how the business security Improved platforms measure, monitor, and improve services are physically deployed. business performance Reduced environmental complexity improves business 3. Security Policy Management flexibility and accelerates strategic initiatives set of policies and principles that ensure that the Business Security Services are managed in a consistent manner with IT. Information Security and Information Privacy Security Policy Management links the business-related another aspect of managing and controlling the and IT-related security services together. information assets exposed to a growing number of security threats today Data Masking Trends around the security aspects of business systems: rapidly gaining prominence when dealing with data growing number of attacks on major enterprises with such as test databases (internal inspired) threats still high As defined by IBM, data masking is the process of Business infrastructures, such as utility networks for identifying sensitive data and overlaying values that water or electricity, are increasingly equipped with masks the sensitive data, but does not compromise the sensors to capture information. The information is used, functional integrity of an application. for example, to predict peak consumptions. The Cloud Computing delivery model requires new Enabling data masking manages the issue of today’s business: means to federate identities across internal and Meet regulatory compliance needs. Enhance data security. COURSE CODE LESSON # 8  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Protect against internal or external attacks as the data Real Time Analytics are capabilities to address the need has little or no external value. to analyze large-scale volumes of data in real time. Enable the use of production data within exposing private, sensitive or confidential data to any non-trusted 2. Business Performance Management party. Define the Key Performance Indicators (KPI) for the business. Two Techniques of Data Masking 3. Enterprise Information Integration (EII) 1. Extract-Mask-Transform-Load (EMTL) Provides abilities to understand, cleanse, transform, and Uses an enhancement to the well-known deliver data throughout its lifecycle. Extract-Transform-Load (ETL) mechanism often used with Data Warehouse environments. This is the process 4. Mashup of extracting data from production into flat files while Enable a business to quickly build web-based, masking the data and finally loading the data into situational applications at low cost for typically small multiple different environments. user groups (for example, all members of a department). 2. In-Place Data Masking 5. Information Governance Data is first copied from production into multiple environments and then masked in place. 6. Information Security and Information Privacy A crucial part for the design, deployment, and control processes of any instantiation of the EIA throughout its LESSON 2: CONCEPTUAL AND LOGICAL VIEW OF life cycle. The Information Governance capability enables a ENTERPRISE INFORMATION ARCHITECTURE business to manage and govern its information as strategic assets EIA Reference Architecture Necessary for the Conceptual Layer 7. Cloud Computing Necessary for many enterprises today and represents a Architecture Overview Diagram (AOD) new delivery model for IT. shows the various required capabilities in a consistent, conceptual overview for the EIA Reference Architecture. EIA Reference Architecture Logical View A framework characteristic of the EIA Reference first graphical representation of the logical architecture Architecture represented by the AOD is its industry and explain key Architecture Building Blocks (ABB). agnostic nature. Conceptual Architecture Overview Architecture Principle of EIA An EIA provides an information-centric view on the Architecture principles are a set of logically consistent overall Enterprise Architecture and easily understood guidelines that direct the design EIA Reference Architecture is developed from a and engineering of IT solutions and services in the top-down perspective enterprise. We look at information from an end user perspective provide an outline of the tasks, resources, and potential working with or operating on it to achieve certain goals. costs to the business for their implementation The EIA must cover all five data domains with Architecture principles should enable the EIA Reference appropriate capabilities as required by each individual Architecture as a tool domain. Logical View of EIA Reference Architecture EIA Reference Architecture additional capabilities: A set of common requirements that straddle all the layers of the information architecture: 1. Predictive Analytics and Real Time Analytics Business Process Orchestration and Collaboration Predictive Analytics are capabilities allowing the capabilities prediction of certain values and events in the future. COURSE CODE LESSON # 9  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Comprehensive Connectivity and Interoperability ○ For easy identification capabilities, Name Security- related requirements ○ Applying intuitive naming convention High-level description ○ Short paragraph for quick understanding Service description LESSON 3: COMPONENT MODEL AND OPERATIONAL ○ Focus on service, including service patterns Interfaces MODEL OF EIA ○ Component interactions and interface standards (such as XML) The Component Model describes how these functional aspects can be Component Interaction Diagrams assembled to add value in any solution stack These diagrams depict how components dynamically A component represents a logically grouped set of collaborate to support various required business specific capabilities to deliver particular software scenarios. functionality. These diagrams capture the most significant dynamic The Component Model is the HEART of the EIA relationships between components. describes the functional components in terms of their Focuses on the interactions between components and roles and responsibilities illustrate the derived flow of functionality in the context Each component is a relatively independent part of the of a specific deployment scenario. architecture, where its characteristics are described by Any customer use case scenario can be easily mapped to its functions, responsibilities, usage aspects, and the Component Model using the corresponding interfaces. Component Interaction Diagram. Main focus of the Component Model is the Component Relationship Diagram and the Component Interaction Operational Model Diagrams. details how these functional components can be deployed onto physical assets to deliver the 1. Component Relationship Diagram requirements (functional and non-functional) of the a depiction of the components, interfaces, and design. relationships that are a part of the Component Model. The Operational model is the definition and distribution interfaces and relationships can be described at different of an IT system’s components onto geographically levels. distributed nodes. They simply describe directional flows of data between It predominately targeted at enterprise architects, two components. information architects, and system architects; can also be used as a reference for IT experts from CRD Representation Colors: different skill domains dark gray boxes represent the information services physical nodes can be derived from logical components components for the metadata, data, content, master of the Component Model. data, and analytical data domain. According to the IBM Architecture Description Standard gray boxes represent information service-related (ADS), the Enterprise Architecture can be presented at components such as the EII Component, the Mashup different levels. Hub Component, and IT Service & Compliance Management Services Component. The EIA Reference Architecture is subdivided into three parts: light gray boxes are components that are not part of the Conceptual Level previous two categories and are typically found in a Logical Level solution based on the EIA. Physical Level Component Descriptions Forms of Operational Mode Levels It includes a detailed description of the main functionalities and the responsibilities of each component. 1. Logical Operational Model (LOM) identifies the required technical services, develops the ID connections, and refines the technical specifications. COURSE CODE LESSON # 10  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms 2. Physical Operational Model (POM) Operational Model derives from the Component Model the hardware and software technologies needed to and it details functional component interactions and deliver the Operational Model’s characteristics and deployment scenarios. capabilities are identified and configured. process of operational modeling means the partitioning documents the overall configuration of the and aggregation of logical components to DUs. technologies and products necessary to deliver the The generalized Operational Model allows to select, functional requirements and NFRs of the IT system customize, and integrate pre-developed architectural patterns for our needs. Operational Model Concepts and Notations Operational Model Relationship Diagram 1. Node The Operational Model relationship diagram is a Central concept of an Operational Model. depiction of nodes, locations, and correlating A platform on which software executes. connections separately documented as the design Represents a potential platform, before decisions have proceeds. been made about Generalization means we provide a collection of Each node has a name and optionally the number of standard node types, pre-defined connection types, instances. location types, and deployment unit placements for specific business scenarios 2. Connections “design building blocks” It represent physical data paths between nodes and show the shape of the network. Basic Location Types External Business Partners Location 3. Deployment units (DU) Public Service Providers Location Items placed on the nodes. Disaster Recovery Site Location Smallest unit of software or data for which an architect Branch Systems Location makes a placement decision. Deployment units are shown as named items on each Inter-Location Border Types node. Corporate WAN consists of one or more components. ○ Corporate wide area network Branch LAN 4. Execution deployment units (EDU) ○ Internal local area network (LAN within a installation and execution of components. branch) Head Office LAN 5. Locations ○ Internal local area network (within head office) Group of nodes. geographical entity (such as a zone or building type) Internet Link and is shown by pictorial elements around one or more ○ Internet link and access to the external nodes. business partner’s organization Key Design Concepts within Operational Modeling Access Mechanisms In order to describe how the component model is implemented The major conceptual work items are: across IT systems, the Operational Model documents the access The placement and grouping of components into mechanisms used by all users of the system. deployment units The application of walkthroughs confirming operational Standard Access Mechanisms: aspects. System Support and Management The consideration of constraints and quality File Download (from file producers) requirements File Upload (to file consumers) The physical configuration for a set of technologies Message Receipt (from message producers) Message Sending (to message consumers Context of Operational Model Design Techniques Socket Request (from socket requestors) Socket Response (from socket responders) COURSE CODE LESSON # 11  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms The integration of various technologies such as Standard of Specified Nodes message-based communication mechanisms Specified nodes do not represent actual computing resources. 4. Continuous Availability and Resiliency Pattern They provide a formal mechanism for enabling the High availability is a component of continuous specification of the location for the solution’s availability. application Classification is done in four layers: 5. Multi-Tier High Availability for Critical Data Pattern ○ Information Services Redundancy is a critical and well understood means of ○ Application Platform Layer for Information achieving high availability. Services ○ Technology Layer for Information Services. 6. Content Resource Manager Service Availability Pattern ○ IT Service & Compliance Management Contributes to availability by segregating functions and Services. can enable increased redundancy, increased scalability, and simplified management among components Framework of Operational Patterns a repository of recurring solution elements based from 7. Federated Metadata Pattern previous experiences. Communicates with and retrieve data from remote data It is a good practice to capture and reuse the experience sources through wrapper services of past engagements. “scope of integration” 8. Mashup Runtime and Security Pattern Scope of Integration can be classified in 3 ways: 9. Compliance and Dependency Management for Operational Discrete solution scope Risk Pattern ○ Predominately applies to the use of services in It addresses formal and documented dependency and a single Line of Business (LOB) configuration management procedures Integrated solution scope 10. Retention Management Pattern ○ Typically signifies the use of services as shared It is about retaining corporate records for the minimum services across the enterprise appropriate retention period to meet business and regulatory requirements Cross-domain solution scope ○ Applies to the use of services in a 11. Encryption and Data Protection Pattern multi-enterprise context, typically through the Provides greater data security, integrity, retention, interconnection with partners or third-party auditability, and privacy. providers 12. File System Virtualization Pattern Different Derived Operational Patterns (Selections and Reuse) File virtualization approach is through the use of a Distributed File System Services Clustered Node such as 1. Near-Real-Time Business Intelligence Pattern IBM General Parallel File System (GPFS). Provides access to information about business actions as soon after the fact as is justifiable based on the 13. Storage Pool Virtualization Pattern requirements. It addresses the increasing cost and complexity in data storage management 2. Data Integration and Aggregation Runtime Pattern Provides solutions for transparently managing both the 14. Automated Capacity and Provisioning Management Pattern volume and diversity of data that exists in enterprises It has the ability to control lifecycle, starting, stopping, across the LOBs. and provisioning of services automatically. 3. Enterprise Service Bus (ESB) Runtime for Guaranteed Data Delivery Pattern COURSE CODE LESSON # 12  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms Module 5: Enterprise Architecture Methods The approaches emerged: first approach was from the United Kingdom and OVERVIEW Europe second approach was from the United States The emphasis of these methods is to: third approach was business driven and emerged identify priority data independently in Australia business activities Each addressed the development of data modeling business processes methods, using normalization to eliminate redundant and then deliver these priority areas in 3-month data versions. increments as production systems. Information Engineering a rigorous engineering discipline LESSON 1: EVOLUTION OF SYSTEMS DEVELOPMENT Originally developed by Clive Finkelstein was popularized worldwide through-out the 1980s by METHODOLOGY James Martin evolved into what is today called enterprise engineering Methodologies that have evolved since the beginning of (EE). the Information Age have helped us to examine current manual processes so we could automate them. Evolution of Object-Oriented Methods From rudimentary methodologies in the 1960s, by the 1970s these had evolved into the software engineering 1980s methods which are also called structured methods. concepts of object-oriented (O-O) development and the unified modeling language (UML) were developed by: Evolutions of Software Engineering ○ Grady Booch, James Rumbaugh, and Ivar The software engineering methods analyzed current Jacobson manual processes, documenting them with data flow Object-oriented methods based on UML were found to diagrams (DFDs) and functional decomposition be very effective in developing reusable code. diagrams (FDDs). Established Rational Corporation to develop associated The structure of modular programs to automate these UML modeling tools. processes was documented using structure charts (SCs). They popularized UML and Rational software tools, With software engineering, each DFD that was defined which were widely used in the late 1990s for a process identified the data that it needed as data When IBM purchased Rational Corporation in 2003, stores. Rational became a subsidiary of IBM. Evolution of Information Engineering LESSON 2: STRATEGIES FOR ENTERPRISE Late 1960s - Early 1970s ARCHITECTURE IMPLEMENTATION Edgar Codd (research fellow at IBM San Jose Labs), developed the relational model from mathematical set Many strategies are available for implementing enterprise theory architecture, according to John Zachman: ○ Became foundation of relational database technology today 1. Strategy A: Implementation in top-down, rigorous detail; This strategy achieves enterprise-wide data integration IBM DB2 RDBMS with a fully attributed, fully normalized logical data ○ The first relational database management model. systems (RDBMSs) ○ Released by IBM Corporation (IBM DB2 2. Strategy B: Selective EA, based on ROI business case; RDBMS) and by Oracle Corporation (Oracle Strategy B is appropriate if an ROI business case must RDBMS) first be established before a decision is made to ○ Late 1970s & Early 1980s introduce an enterprise architecture approach. COURSE CODE LESSON # 13  LESSON #: LESSON TITLE COURSE CODE IBITS Year 18 | A.Y. 2024 - 2025 First Semester - Midterms 3. Strategy C: Deliver progressively in 3-month incremental builds. This approach leads to incremental implementation of priority areas that are needed first, before other areas that can wait until later. LESSON 3: ENTERPRISE ARCHITECTURE INCREMENTAL BUILD CONTEXT Step 1: Strategy analysis identified statements for mission, vision, core values, goals, objectives, issues, KPIs, and strategies in the strategic plan. Step 2: Strategy analysis identified from the organizational structure those managers and business experts responsible for implementing priority areas of the strategic plan. Step 3: With participation by the identified managers and business experts, over 5 days in a business planning workshop they optionally apply the strategy analysis methodology to define tactical business planning statements to implement strategic plans. Step 4: Data mapping is used to enable business experts and IT experts to work together to identify data for integration. This begins with a 2-day strategic modeling facilitated session. Entities that represent required information and data are listed. Step 5: The facilitated modeling session continues over 2 days, documenting key entities in a strategic model on a whiteboard. The strategic data map is a high-level enterprise model. COURSE CODE LESSON # 14