SIA Module 1.1

System Integration

The process of combining various subsystems or components to work together as a unified system.

Horizontal Integration

Connects different systems or applications at the same level of the technology stack.

Vertical Integration

Connects systems across different levels of the technology stack.

Functional Integration

Focuses on integrating different functionalities or modules within the same system.

Middleware

Software that facilitates communication between different systems or applications.

Message Brokers

Facilitate message exchange between different systems.

API Gateways

Manage and route API requests.

Database Middleware

Connects applications to databases, handling data transactions and queries.

API (Application Programming Interface)

A set of rules and protocols that allows different software applications to communicate with each other.

Monolithic Architecture

All components of the application are interconnected and operate as a single unit.

Layered Architecture

Divides the system into distinct layers that interact hierarchically.

Presentation Layer

User interface layer of a layered architecture.

Logic Layer

Processes business logic in a layered architecture.

Data Access Layer

Handles interaction with data storage.

Evaluation Layer

Layer included in the reviewer as part of the layered architecture.

Microservices Architecture

Decomposes a system into small, independent services that communicate through APIs.

Service-Oriented Architecture (SOA)

Designs the system as a collection of loosely coupled, reusable services communicating through standardized protocols.

Modularity

Breaking down a system into smaller components or modules that can be developed and maintained independently.

Scalability

Designing a system to handle increased load and data volume without significant performance degradation.

Interoperability

Ensuring different systems and components work together seamlessly, even if built on different technologies or platforms.

Enterprise

The information needed to run a profitable business and the characteristics of that information.

Business Level

Top of the semantic information model; includes enterprise vocabulary and concepts describing interactions between people and systems.

Application Level

Part of the internal value chain where activities are treated as independent domains.

Architecture

High-level planning showing the overall structure or design of an organization or system.

Enterprise Architecture

A framework aligning business goals, processes, technology, and information systems to achieve an organization's mission.

IBM Definition of Enterprise Architecture

A tool that links an organization's business mission and strategy to its IT strategy.

P.O.L.D.A.T

Processes, Organizations, Location, Data, Application, Technology.

Information Architecture (IA)

A shared and organized information environment that stores, manages, and provides trustworthy information across enterprise applications.

Principle of Objects

Treat content as something with a lifecycle.

Principle of Choices

Create pages that offer meaningful choices.

Principle of Disclosure

Show only enough information to help people understand.

Principle of Exemplars

Describe category contents by showing examples.

Principle of Front Doors

Visitors may enter through pages other than the home page.

Principle of Multiple Classification

Offer several classification schemes for browsing content.

Principle of Focused Navigation

Do not mix unrelated navigation schemes.

Principle of Growth

Assume today's content is only a small fraction of future content.

Enterprise Information Architecture (EIA)

A component of Enterprise Architecture providing a common framework for securely sharing and managing information.

Transaction Data

Business transactions captured during operations and processes.

Metadata

Data about data; describes the data.

Master Data

Enterprise-level data entities of strategic value.

Reference Data

Facts that support transaction processing, master data management, and decision support.

Unstructured Data

Documents, images, geospatial data, multimedia, and other non-structured information.

Analytical Data

Data derived from business operations for reporting and analysis.

Big Data

Large datasets that are difficult to store, search, share, and analyze.

Data Governance

Management of data availability, usability, integrity, and security.

Data Standards

Common definitions, specifications, and vocabularies for data assets.

Data Sharing

The combination of technology, people, and processes used to collect, process, and disseminate information.

Zachman Framework

Enterprise Architecture framework with six descriptive foci and six stakeholder perspectives.

TOGAF

The Open Group Architecture Framework that divides EA into Business, Application, Data, and Technical architectures.

Gartner Framework

Enterprise Architecture that brings together business owners, information specialists, and technology implementers.

Federal Enterprise Architecture

Framework consisting of Business, Components, Technical, Data, and Performance reference models.

Metadata Domain

Information describing the characteristics of each corporate data asset.

Master Data Domain

Data describing the core business entities.

Operational Data Domain

Transactional data derived from business transactions.

Unstructured Data Domain

Content typically managed by enterprise content management applications.

Analytical Data Domain

Data transformed from operational systems to support decision making.