IT-312 Systems Integration and Architecture Midterm Review

Vocabulary flashcards covering architectural patterns, system modeling techniques, integration strategies, and API/middleware concepts for IT-312 Systems Integration and Architecture.

Service-Oriented Architecture (SOA)

An architectural pattern that organizes functionality as services with defined interfaces, emphasizing reusability and allowing services to be accessed by other parts of a system when needed.

Layered Architecture

An architectural pattern where a system is organized into hierarchical layers, each with a defined responsibility to make the structure easier to understand and maintain.

Repository Architecture

An architectural pattern in which components access a shared, central repository for data, supporting data sharing while potentially creating dependencies on the central store.

Client–Server Architecture

An architectural pattern where clients request data or services, and servers process those requests and provide responses, dividing responsibilities between the two sides.

Pipe-and-Filter Architecture

An architectural pattern where data passes through a sequence of independent filters connected by pipes, with each filter performing a processing step before passing its output onward.

Event-Driven Architecture

An architectural pattern where components produce and respond to events to trigger actions or communicate occurrences, reducing the need for direct component-to-component calls.

Microservices Architecture

An architectural pattern where an application is divided into relatively independent services that can be developed, deployed, and scaled separately.

Model–View–Controller (MVC)

An architectural pattern that separates responsibilities among the Model, View, and Controller to keep application data, presentation, and input-handling logic organized.

Architectural Patterns

Reusable guidance for recurring system-design problems that are selected based on the system's requirements and associated trade-offs.

Context Model

A system model that gives an overview of the system boundary and the external people, organizations, or systems that interact with it, clarifying what is inside versus outside the system.

Data Flow Model

A system model that represents how information moves through processes, data stores, and external entities, useful for examining inputs, transformations, storage, and outputs.

Class Model

A system model that represents the static structure of a system through classes, attributes, methods, and relationships to describe object-oriented software organization.

Activity Model

A system model that represents actions and the flow of work within a process, explaining the steps and possible paths in a workflow.

Sequence Model

A system model that displays messages exchanged between objects or components in time order, emphasizing the chronological sequence of interactions.

State Machine Model

A system model that represents the states an object can occupy and the events that trigger transitions between those states.

Deployment Model

A system model that shows where software artifacts are placed on hardware nodes or runtime environments, focusing on physical or execution arrangement.

Component Model

A system model that describes software components and how they are organized or interact through interfaces, detailing the system's software building blocks.

Entity-Relationship (ER) Model

A system model that represents data entities, their attributes, and relationships between them, commonly used to plan or communicate data structures.

Top-Down Integration

An integration approach that starts with the high-level architecture and then addresses subsystems and details, supporting alignment with the overall design.

Bottom-Up Integration

An integration approach that begins with individual components or subsystems, tests them, and combines them gradually to reveal component-level issues early.

Middleware-Based Integration

An integration strategy where middleware acts as an intermediary to facilitate communication and potentially transform data formats or protocols between systems.

API-Based Integration

An integration strategy where systems communicate via defined API endpoints and service interfaces to provide standardized access to services and data.

Application Programming Interface (API)

A specification that defines how one software component can request data or functionality from another through agreed interfaces.

REST

An architectural approach used to design web APIs centered around resources and standardized web interactions, commonly utilized for web and mobile access to services.

API Gateway

A centralized entry point for requests directed to APIs that can route requests and enforce shared policies, though it does not automatically eliminate security risks.

OAuth

An authorization framework used to grant applications limited access to protected resources.

API Security

The implementation of suitable authentication and authorization controls to safeguard the services and data exposed by APIs.

Middleware

Software that helps separate applications or systems communicate by managing messages, coordinating interactions, or transforming data.

Message Broker

A software intermediary that receives and routes messages between applications or services to help decouple senders from receivers.

Message-Oriented Middleware (MOM)

Middleware that supports message-based communication, including asynchronous messaging where senders and receivers do not need to process messages simultaneously.