0% found this document useful (0 votes)
7 views28 pages

System Integration and Architecture Overview

The document outlines a course on System Integration and Architecture, focusing on linking various computer systems and software applications to function cohesively. It highlights the importance of System Integration in improving efficiency, data accuracy, and decision-making while addressing common challenges and types of integration. Additionally, it discusses different architectural models for integration, such as Point-to-Point, Hub-and-Spoke, and Enterprise Service Bus (ESB).
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views28 pages

System Integration and Architecture Overview

The document outlines a course on System Integration and Architecture, focusing on linking various computer systems and software applications to function cohesively. It highlights the importance of System Integration in improving efficiency, data accuracy, and decision-making while addressing common challenges and types of integration. Additionally, it discusses different architectural models for integration, such as Point-to-Point, Hub-and-Spoke, and Enterprise Service Bus (ESB).
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

GOOD DAY!

IT313
System Integration
and Architecture 1
JENELLIE ROSE B. GUEVARRA
Introduction to System
This course Integration
is all about linking different
computer systems and software applications
together so they can work as a single,
coordinated whole. We'll be focusing on two main
areas: Enterprise Architecture Planning (EAP)
and Enterprise Application Integration (EAI).
Learning Objectives:
1. Define what System Integration is.
2. Explain the basic concepts and why it's so
important in IT.
3. Identify and differentiate between the main
types of system integration.
What is a System?
What is a System?
-In IT, a system is a set of interacting or
interdependent components that work
together to accomplish a common goal.
The Problem: Disconnected Systems
The Problem: Disconnected Systems
Scenario:
Imagine a company where the Sales department uses one
software, Inventory uses another, and Accounting uses a third.

Issues:

• Data Silos: Information is trapped in different systems.


• Manual Processes: A sale is made, and someone has to
manually enter that information into the inventory and
accounting software.
• Inefficiency & Errors: This is slow, prone to mistakes, and
leads to bad decision-making.
System Integration (SI) to the
Rescue!
System Integration (SI) (also referred to
as IT integration or software integration)
is the process of joining software and
hardware modules into one cohesive
infrastructure. The goal is to make these
systems work together smoothly so they
can share information and processes more
efficiently.
The Importance of System Integration
The Importance of System Integration
1. Improved Efficiency: Data and processes are automated,
reducing manual effort and errors.
The Importance of System Integration
1. Improved Efficiency: Data and processes are automated,
reducing manual effort and errors.
2. Enhanced Data Accuracy: Real-time data sharing ensures all
departments are working with the same, correct
information.
The Importance of System Integration
1. Improved Efficiency: Data and processes are automated,
reducing manual effort and errors.
2. Enhanced Data Accuracy: Real-time data sharing ensures all
departments are working with the same, correct
information.
3. Better Decision-Making: With a unified view of the business,
leaders can make faster, more informed decisions.
The Importance of System Integration
1. Improved Efficiency: Data and processes are automated,
reducing manual effort and errors.
2. Enhanced Data Accuracy: Real-time data sharing ensures all
departments are working with the same, correct
information.
3. Better Decision-Making: With a unified view of the business,
leaders can make faster, more informed decisions.
4. Reduces Costs: System integration allows you to connect
and leverage your existing infrastructure. This is often a
System Integration vs. Data Integration
System Integration: Focuses on connecting the
systems themselves to enable communication
and functionality.
Data Integration: Focuses on collecting and
consolidating data from different sources into a
single storage location for a unified view.

Key takeaway: System integration helps you


access data; data integration helps you organize
Common Integration Challenges
Common Integration Challenges
• Compatibility Issues: Different systems may
use different languages or formats.
• Security & Compliance: New connections can
create vulnerabilities.
• High Costs & Resources: It can be
time-consuming and expensive.
• Maintenance: Changing one system can affect
others.
The "What":
Integration Types by
Business Context
Legacy system integration
-Integration of modern applications into existing,
outdated systems.
-Connecting old, outdated systems to new, modern
applications.
Goal:
To keep critical, core business functions that an
organization relies on while modernizing the
overall IT environment.
Enterprise application integration
(EAI)-
-The unification of different subsystems and
applications within a single company.

Goal:
To automate processes and enable real-time
data exchange across an entire organization.
Third-party system integration -
-Expanding the functionality of an existing system by
connecting it to external tools or services.

Goal:
To add new features quickly without building
them from scratch.
Business-to-business integration -
-Connecting the systems of two or more different
organizations.
Goal:
To automate transactions and document exchange,
leading to more efficient cooperation with suppliers
and partners.
The "How":
Integration
Architectural Models
Point-to-Point Model
-Every system is directly connected to every other
system it needs to communicate with.

Pros: Quick for small


projects with few systems.

Cons: Hard to manage and


scale; becomes a messy
web of connections as
more systems are added.
Hub-and-Spoke Model
-All systems ("spokes") connect to a central, standardized platform
("hub").

Pros: More scalable, easier to manage,


better security.

Cons: The hub can become a bottleneck


or a single point of failure.
Enterprise Service Bus (ESB)
-A more distributed and flexible version of the hub-and-spoke
Model
model, with a "messaging bus" that connects different systems.

Pros: Each system is decoupled, making


it highly scalable and easier to replace
or change components without affecting
others.

Cons: Maintenance and troubleshooting


can be more complex.
CRYSTAL
CLEAR?
Reference:
[Link]

You might also like