Lecture 1: Introduction to System Integration

Learning Objective: Understand the historical evolution of information systems, the fundamental business drivers for system integration, and the architectural layers at which integration occurs.

1. What is System Integration?

In the context of Information and Communication Technology (ICT), System Integration (SI) is the process of linking together different computing systems and software applications physically or functionally to act as a coordinated whole. It involves bringing together disparate subsystems into a single system and ensuring that the subsystems function together flawlessly.

2. History and Evolution of Integrated Systems

The need for integration has evolved alongside the architecture of computing systems:

3. The Importance of Integration

Why do organizations invest heavily in system integration? The drivers are both technical and business-oriented:

4. Levels of System Integration

Integration is not a one-size-fits-all approach. It can be implemented at various architectural levels depending on the business requirements.

Data Level Direct database access, ETL, Data replication. High coupling, bypasses business logic. Application Level (APIs) Web Services, REST APIs, RPC. Communicates via defined business logic rules. Process Level (BPM) Orchestrates multiple applications. Workflow automation, choreography. Presentation (UI) Level Single Sign-On (SSO), Enterprise Portals. Aggregates UI for the end user.

Figure 1: The Four Levels of System Integration

A. Presentation (User Interface) Level

Integration occurs at the screen level. Data from multiple underlying systems is aggregated into a single web portal or dashboard. It requires no changes to the backend systems.

B. Business Process Level

Focuses on automating workflows that span multiple applications. Tools like Business Process Management (BPM) software are used to define triggers, conditions, and actions across systems.

C. Application (Method/API) Level

The most common form of modern integration. Systems communicate by invoking each other's functions or services using APIs (Application Programming Interfaces). It respects the business rules and validations of the target system.

D. Data Level

Systems are integrated by sharing databases or copying data directly from one database to another using ETL (Extract, Transform, Load) tools. While fast, it is risky because it bypasses application-level business logic and validations.

5. A Simple Example of Application Level Integration (JSON Payload)

In modern application-level integration, systems often communicate using lightweight data formats like JSON. Below is an example of an e-commerce system sending an order payload to a warehouse management system via a REST API.

{
  "orderId": "ORD-2026-98765",
  "customer": {
    "customerId": "CUST-1029",
    "name": "Budi Santoso",
    "email": "budi.s@example.com"
  },
  "items": [
    {
      "productId": "SKU-4451",
      "description": "Wireless Mouse",
      "quantity": 2,
      "warehouseLocation": "DPS-01"
    }
  ],
  "shippingDetails": {
    "method": "EXPRESS",
    "address": "Jl. PB. Sudirman, Denpasar, Bali"
  }
}
Discussion Prompt for Students: Think about the information systems in your current organization or university. Are they integrated? If so, at what level (UI, Process, Application, or Data)? What problems occur when systems are NOT integrated?