IT 009 - Module 1.1

Enterprise Architecture (EA)

A framework that links a company's business mission and strategy to its IT strategy, using multiple models that adapt to changing business needs and technology.

Enterprise Information Architecture (EIA)

A part of Enterprise Architecture that focuses on sharing data safely and efficiently across different departments of a company.

Business Architecture

The type of architecture that focuses on an organization's business processes and strategy.

Application Architecture

The type of architecture that focuses on how software applications are structured and interact.

Information Architecture

The type of architecture that focuses on organizing, managing, and structuring data and information.

Infrastructure Architecture

The type of architecture that focuses on the physical and technical foundation (servers, networks, hardware) supporting systems.

Integration Architecture

The type of architecture that focuses on how different systems connect and communicate with each other.

Operational Architecture

The type of architecture that focuses on the day-to-day processes needed to run and maintain systems.

Security Architecture

The type of architecture that focuses on protecting systems, data, and information from threats.

Network Architecture

The type of architecture that focuses on how devices and systems are connected through networks.

EIA Goal

To connect users with the information they need in the simplest way possible, while reducing complexity and removing barriers to change.

Metadata

"Data about data" — key information used to describe and organize data within EIA models.

Conceptual Level (EIA)

The highest level of abstraction in EIA, showing a big-picture view of information without technical details.

Logical Level (EIA)

The middle level of abstraction in EIA, showing how information is organized and related, without specifying actual technology.

Implementation Level (EIA)

The most detailed level of abstraction in EIA, showing exactly how information is built and stored using specific technology.

System Integration

The process of combining different subsystems or components so they work together as one unified system.

Horizontal Integration

Connecting different systems or apps that operate at the same level of the technology stack (e.g., linking two apps that handle similar data).

Vertical Integration

Connecting systems across different levels of the technology stack, such as linking databases to applications to user interfaces.

Functional Integration

Connecting different functions or modules within the same system to make it work as one cohesive application.

Middleware

Software that acts as a "bridge," allowing different systems or applications to communicate and share data.

Message Broker

A type of middleware that helps different systems exchange messages with each other.

API Gateway

A type of middleware that manages and directs API requests between clients and services.

Database Middleware

A type of middleware that connects applications to databases and manages data transactions and queries.

API (Application Programming Interface)

A set of rules that lets different software applications communicate and exchange data with each other.

Monolithic Architecture

An architectural style where all parts of an application are combined into one single unit; simple to build but hard to scale.

Layered Architecture

An architectural style that separates a system into layers (like presentation, business logic, and data access) that work together in order.

Microservices Architecture

An architectural style where a system is broken into small, independent services that communicate through APIs and can be built/deployed separately.

Service-Oriented Architecture (SOA)

An architectural style where a system is made of loosely connected services that communicate using standard protocols, allowing easy reuse and integration.

Modularity

A design principle where a system is broken into smaller, manageable parts that can be built and maintained independently.

Scalability

A design principle where a system can handle more users, data, or workload without losing performance.

Interoperability

A design principle where different systems can work together smoothly, even if built on different technologies or platforms.