SYSTEMS INTEGRATION AND ARCHITECTURE
OVERVIEW
•
Hardware Interfaces: USB, PCIe, HDMI, SATA, Ethernet.
•
Software
Interfaces:
API
(REST,
SOAP),
GraphQL,
WebSockets.
1.
System: An interconnected set of components working together.
2.
Interface: A boundary where systems communicate
Platforms & Frameworks
(e.g., API, USB, HTTP).
3.
•
Platform: The environment where software runs
(Windows + .NET, Android + Java).
(e.g., Windows, Linux, Android).
4.
Platforms: Combination of hardware and software
•
Framework: A structured toolset for software development
Frameworks: Provide reusable code and libraries
(Spring Boot, React, Angular).
(e.g., Xamarin, .NET, Laravel).
5.
Database & DBMS: Organized collections of data
RELATED DISCIPLINES
(SQL, NoSQL, MySQL, PostgreSQL).
6.
Network: Connected computers sharing data
(LAN, WAN, Internet, Protocols).
System Analysis and Design (SAD)
•
System Analysis: Identifies system requirements
(Use Case Diagrams, Data Flow Diagrams).
CONCEPT REVIEW
•
System Design: Defines architecture, models, UI/UX, data
structures.
Hardware & Software
•
Hardware: Physical components
(CPU, RAM, SSD, GPU).
•
Operating System (OS): Manages hardware
(Windows, macOS, Linux, Android).
•
Applications: Software programs for users
(MS Word, Photoshop, Games).
Interfaces
Software Engineering (SE)
Phases of Software Development:
1. Requirements Engineering – Gathering and analyzing needs.
2. Software Design – Creating architecture, UI, database schema.
3. Software Development – Writing code, using IDEs, frameworks.
4. Software Testing – Unit testing, integration testing, debugging.
5. Software
Maintenance
optimizations.
–
Updates,
security
patches,
o
communication.
SYSTEM INTEGRATION (SI)
•
Goal: Interoperability between different systems.
•
Middleware: Software that connects different systems (MQTT,
APPROACHES TO INTEGRATION
•
API Integration: Web services connecting apps
(REST, SOAP, GraphQL).
Types of Integration
1. Horizontal Integration (ESB - Enterprise Service Bus)
o
Uses a centralized message bus to connect subsystems.
2. Vertical Integration (Silos)
o
Connects related systems based on function.
3. Star Integration (Spaghetti Architecture)
o
Each system connects to multiple others, high maintenance.
4. Common Data Format
o
Converts all data to a universal format (JSON, XML, CSV).
5. Point-to-Point Integration
o
Directly connects systems, but difficult to scale.
6. Middleware Integration
o
Acts as a middle layer between systems
(IBM MQ, Apache Kafka).
7. Web Services Integration
Tightly Coupled SI: Systems are dependent on each other,
hard to modify.
Kafka, RabbitMQ).
•
Uses SOAP, REST, WSDL, XML, HTTP, FTP for system
•
Service-Oriented Architecture (SOA): Uses independent
services for flexibility.