SirGayle Exam Reviewer PDF

Document Details

HighQualityCotangent

Uploaded by HighQualityCotangent

Tags

systems integration erp systems information technology business management

Summary

This document provides an overview of systems integration concepts, focusing on Enterprise Resource Planning (ERP) systems. It details horizontal and vertical silos, the role of ERP in logical and physical integration, and the evolution of ERP systems through different timelines. It also introduces different ERP vendors and their related software.

Full Transcript

**LESSON 1** **Systems Integration** - implies users permit to communicate or connect effortlessly **Lehtonen** defined system integration, as the act of linking several sub-systems into a bigger system **System Integration** - combining all of the organization's physical and virtual components...

**LESSON 1** **Systems Integration** - implies users permit to communicate or connect effortlessly **Lehtonen** defined system integration, as the act of linking several sub-systems into a bigger system **System Integration** - combining all of the organization's physical and virtual components **ERP (Enterprise Resource Planning) Systems** - type of information technology that enables businesses to connect many systems into a single (sort of software that businesses often use) **Silos** - airtight pit or tower for preserving foodstuffs (segregated functioning units that are cut off) **Horizontal Silos** - Henry Fayol, separate functionalized organizations into five fundamental areas: planning, organizing, coordinating, commanding, and controlling in the early 1900s. Luther Gulick expanded Fayol\'s categorization in the 1930s, resulting in the POSDCORB functional model (planning, organizing, staffing, directing, coordinating, reporting, and budgeting) **Vertical Silos** - In the late 1960s, Harvard University\'s Robert Anthony discovered that businesses split responsibilities in hierarchical stages, from strategic planning through managerial control and operation control (prefer to split operations) **Application of information System** - Business Communications System, Business Operations Management, Company Decision-Making, and Company Recording-Keeping **Information System** - serve the organization\'s changing information demands (assist company processes) **Management Three Levels** -strategic, middle, and operational **Implications Of System Integration for Management** - Implementing rules on ethical information usage **ERP's Role in Logical Integration** - ERP solutions force companies (order input, routing via departments, and transmission of output to various stakeholders) **ERPs Role in Physical Integration** - An enterprise may need to upgrade or install middleware (Data integration, client integration, and application integration are all essential components of integration) **Timeline** **System** **Platform** -------------- ----------------------------------------- -------------------------------------------------------------------- 1960s Inventory Management & Control Mainframe legacy systems using third generation software 1970s Materials Requirements Planning (MRP) Mainframe legacy systems using third generation software 1980s Material Requirements Planning (MRP-II) Mainframe legacy systems using fourth generation database software 1990s Enterprise Resource Planning Enterprise Resource Planning 2000s Extended ERP or ERP-II Client-server systems using Web platform **E-Business** - Focuses on linking a business, **Disruptive Technology** - Totally transformed the way a business operates **ERP** - Focuses on integrating the internal, **Adaptive Technology** - Merged the early data processing **ERP Systems Components** - An ERP System is composed of Hardware, Software Process, Information, Process, and People **ERP Architecture** - The budget, operation, and the use of an ERP system are all influenced by the system\'s architecture (aids the deployment team in developing) - **Logical** - focuses on the supporting - **Physical** - focuses on the efficiency **TIERED ARCHITECTURE EXAMPLE OF ERP SYSTEM** 1\. Presentation Logic Tier 2\. Business Logic Tier 3\. Data Tier **Software and Vendor Selection** - company must assess its existing and future enterprise **Operation and Post-Implementation** - One of the most significant milestones in a project\'s success is when it goes live (or \"go-live\") **ERP VENDORS** **1. SAP** - world\'s most popular ERP software, (products are suitable for a wide range of industries) **2. Oracle/Peoplesoft** - second largest ERP provider, (offers solutions categorized by Industry) **3. Microsoft Dynamics** - formerly known as Microsoft Business Solutions or Great Plains, (complete business management system) **4. Infor** - world\'s third largest corporate software vendor (provides integrated supply chain) **5. Lawson** - Enterprise performance management **LESSON 2** **Information-Oriented** - convergence of two or more systems by permitting easy data flows (Moving data across systems) **INFORMATION-ORIENTED INTEGRATION CONCEPTS** **Coupling** - connects applications in reliant on one another **Cohesion** -act or state of sticking together or logical agreement (Applications and databases are distinct of one another in cohesiveness) **Information Producers and Consumers** - entities that create and consume information are known as **source and target systems** (Database, Application, User Interface, and Embedded Devices are examples of systems that create and consume data) **STEPS TO APPROACH INFORMATION INTEGRATION** 1\. Identify the data 2\. Catalog the data 3\. Build the Enterprise Metadata Model --used as master guide for integrating the various information **Data Replication** - shifting data across two or more databases (not suited for integrating functionalities in applications) **Data Federation** - combining various databases into a single virtual database **Interface Processing** - Integrating packaged and bespoke programs is part of interface processing (most often used method of integration) **BUSINESS PROCESS INTEGRATION-ORIENTED** - enable integration not just via the sharing of information **Application Integration** - capacity to build a common business process model (create a single logical model) (Provides a control method that describes and implements information flow) **TECHNOLOGY COMPONENTS** **1. Graphic Modeling Tool** -- business model is created and defined **2. Business Process Engine** -- controls the execution of the multi-steps business processes **3. Business Process Monitoring Interface** -- Allows end-users to monitor and control execution of a business **4. Business Process Engine Interface** -- Allows other applications to access the business process engine **5. Integration Technology (Middleware)** -- Connects the source and target system **THREE LEVELS OF TECHNOLOGY** **1. Process modelling** - Information mobility is specified in process modeling **2. Transformation, routing, and rules** - Information movement and formatting occur (Routing makes it possible to retrieve important data) **3. Message service** - in-charge of transferring data across all linked apps **Service-Oriented Application Integration** - provides a framework for connecting applications **Service-Oriented** - allows apps to share business logic and procedures **Application Service** - Sub-routines or procedures in applications **SOLUTIONS ARCHITECTURE** **1. Event-Drive** - designs that focus on data mobility **2. Composite-Application** - Describes architectures that require application services **3. Autonomous-Distributed** - web service architectures that have been so closely interwoven **Portal-Oriented Application Integration** - ability to access a variety of systems **Portal-Oriented** - combines programs through a single user interface or application access via web browser **PORTAL CATEGORIES** **1. Single-System Portals** - businesses that have extended their user interfaces to the web **2. Multiple-Enterprise-System Portals** - expands the design of a single-system gateway **3. Enterprise Portals** - broaden the scope of a multi-enterprise system **COMPONENTS OF PORTAL ARCHITECTURE** **1. Web Clients** - PC or any other device that can display HTML **2. Web Servers** - At their heart, web servers are file servers (reply to web client queries) **3. Database Servers** - respond to requests and return information **4. Back-end Applications** - corporate apps that reside within a single company **5. Application Servers** - provide middle layer between back-end applications **LESSON 3** **Middleware** - software that allows communication between two or more software systems **TWO TYPES OF MIDDLEWARE MODELS** **1. Logical Middleware Model** - conceptualizes how information travels **2. Physical Middleware Model** - actual mechanism of information flow and the technology used are **Point-to-Point Middleware** - connect one program to another (inability to link more than two apps) **Many-to-Many Middleware** - connects a large number of applications (can handle many sources or target apps) **Asynchronous** - middleware transfers data between one or more applications **Synchronous** - encounters issues such as network or remote server issues (consumes bandwidth since multiple network calls are required) **Connection-Oriented** - Two parties connect, exchange messages (usually a synchronous procedure, although it can be asynchronous as well) **Connectionless** - caller application does not establish a connection with the destination process **Direct Communication** - middleware layer takes the message from the caller application and sends it straight **Queued Communication** - use of a queue manager to place a message in a queue **Publish/Subscribe** - removes the requirement for an application (transmit the data it wants to share known as a **broker**) **Request Response** - used to send a request to an application **Fire and Forget** - enables a middleware user to \"fire off\" a message and then \"forget\" about it **TYPES OF MIDDLEWARE** **A. Remote Produce Calls (RPC)** - oldest kind of middleware (allows you to execute a function from one application) **B. Message-Oriented Middleware (MOM**) - queuing software that uses messages to transport data **C. Distributed Objects** - Small application programs that interact with one another **D. Database-Oriented Middleware** - makes it easier for an application or two databases to communicate with each other **E. Transaction-Oriented Middleware** - provides a framework for coordinating information flow **TP Monitors** - serve as a hub for communication between two or more applications **Application Servers** - provide the sharing and processing of application logic **Integration Servers** - allow data to flow between two or more resources

Use Quizgecko on...
Browser
Browser