0% found this document useful (0 votes)
22 views31 pages

Chapter 1_Lesson 1

Systems integration is the process of connecting disparate computing systems to function as a cohesive unit, improving efficiency, data sharing, and decision-making. It involves various types of integration, including legacy, third-party, business-to-business, big data, and cloud services integration. Successful integration meets cost-effectiveness and operational needs while utilizing existing system capabilities.

Uploaded by

artkaine lopero
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)
22 views31 pages

Chapter 1_Lesson 1

Systems integration is the process of connecting disparate computing systems to function as a cohesive unit, improving efficiency, data sharing, and decision-making. It involves various types of integration, including legacy, third-party, business-to-business, big data, and cloud services integration. Successful integration meets cost-effectiveness and operational needs while utilizing existing system capabilities.

Uploaded by

artkaine lopero
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
You are on page 1/ 31

ITP622:

Systems Integration &


Architecture
Lesson 1: Introduction to Systems
and System Integration
What is Systems Integration?
● Systems integration is a way of getting separate or disparate computing
systems to “talk” to each other.
● It is the process of connecting different systems and subsystems together
to work as a single, cohesive system.
● Systems integration involve integrating hardware, software, and data from
different sources to create a cohesive system that can perform a specific
function or set of functions.
Reasons For Integration

Improved
Improved Cost
Data
Efficiency Savings
Sharing
Reasons For Integration

Better Better
Better Competitive
monitoring decision
compliance advantage
and reporting making
Systems Integration

In today’s business environment where acquisitions, partnerships, and the


continued existence of legacy computing systems are the norm, systems
integration can mean the difference between smooth and efficient data
exchange and a chaotic low-quality process of managing data.
Key Concepts

American Standard Code for Information


Interchange (ASCII)
Key Concepts

American Standard Code for Information


Interchange (ASCII)
Key Concepts

Interface
An interface must have stable and well-defined characteristics.
Key Concepts

Application Programming Interface (API)


Key Concepts

Media
Refers to the physical or logical channels used to transmit data
between different systems or components.
Key Concepts
○ Physical Media
■ Copper wires
■ Fiber-optic cables
■ Wireless media
Key Concepts
○ Logical Media
■ Network protocols
■ APIs
■ Cloud-based services
Key Concepts

Middleware
Functions:

○ Data integration

○ Service integration

○ Security
Key Concepts

● Protocol - A protocol is a set of rules governing the exchange or transmission of data


electronically between devices.

Examples:

○ TCP/IP/UDP - Transmission Control Protocol/Internet Protocol/User Datagram


Protocol
○ HTTP - Hypertext Transmission Protocol
○ FTP - File Transfer Protocol
Open Systems Interconnection (OSI) Model

Is a reference model for networking


that describes how different systems
and devices can communicate with
each other.
Key Concepts

● System - Is a set of interacting or interdependent components that work together to


achieve a common goal or set of goals.
Types of Integration

Besides the size and scope of integration projects


ranging from clear and simple to massive and complex,
there are also different types of system integration:

● Legacy System Integration -


Refers to the process of
connecting older, established
systems with newer systems or
technologies.
Types of Integration

Example of legacy system integration:

○ A legacy financial system integrated with new accounting software

○ A legacy CRM system integrated with a newer marketing automation platform

○ A legacy inventory management system integrated with a newer e-commerce


platform
Types of Integration

● Third-party System Integration - refers to the process of connecting a system or


application developed by one organization (the third party) with a system or
application developed by another organization.

Examples:

○ An e-commerce platform integrated with a third-party payment gateway

○ A website or mobile app integrated with a third-party analytics tool


Types of Integration

● Business-to-Business Integration

○ A bank’s accounting system integrated with an organization’s payroll system

○ A supplier’s inventory management system integrated with a manufacturer’s


order management system

○ A logistics management system integrated with a retail company’s warehouse


management system
Types of Integration

● Big Data Integration - is the process of extracting, transforming, and loading (ETL)
data from different sources into a big data platform.

○ Collecting and aggregating data from various sources such as social media, IoT
devices, and transactional systems

○ Storing data in a big data platform or data warehouse


Types of Integration
● Cloud Services Integration

○ Migrating data and applications from


on-premises systems to cloud-based
services, such as moving a company's
data to a cloud-based storage service.

○ Synchronizing data between cloud-based


services and on-premises systems, such
as keeping a company's customer data up
to date across both cloud-based and
on-premises systems.
What defines a successful system integration?

● Successful integration meets the system owner’s needs most cost-effectively.

● Generally, the most cost-effective integration is achieved by making use of


the existing capabilities of the systems involved.

● Performing system integration can be a complex and costly process. Before


proceeding with system integration, be certain it is necessary.
Integration Rules of Thumb
1. Begin a system integration project by evaluating the requirements for
integration:

○ Do not make up detailed requirements based on your assumptions – require


specification details be provided.

○ Understand the intent of the people responsible for the specifications.

○ Understand the needs of the operational people – these may not agree with the
specification.

○ Make sure the interested parties resolve their differences.

○ Before proceeding, be sure integration is the most effective way to meet the needs of
the clients.
Integration Rules of Thumb

2. If integration is required, understand the scope of integration that is needed.

○ If the requirement is to integrate the display of data from different systems, integration
through the workstation may be more practical than a controller level solution.

○ If full data exchange between the systems is required and only a custom solution can
achieve it, a workstation-based solution may be more cost effective than a controller
level solution.
Integration Rules of Thumb

3. Seek a solution that makes use of the built-in capabilities of the systems
involved and/or uses off-the-shelf alternatives that can meet the
requirements.

○ When non-compatible systems must be integrated, look for commercially available


gateway products that can connect the systems together.

○ When requirements specify controllers that are not compatible with supported
protocols, look for and propose alternatives that work with a supported protocol.
Integration Rules of Thumb

4. A solution that requires custom hardware or software should be a last


resort. A custom solution brings the following issues:

○ The implementation cost is high; it may not be cost effective within the budget of the
project.

○ The cost of system maintenance is increased; changes or updates made to the


integrated systems may require updates to the custom solution.

○ Unproven solutions have an increased risk of failure.

○ Maintenance may be difficult to arrange.


THANK YOU

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy