Architecture Models and Software Architecture (Week 6)

Vocabulary flashcards covering concepts from Architecture Models and Software Architecture.

Software Architecture

The high‑level structure of a software system; defines components, their relationships, and interactions, serving as a blueprint for design, implementation, and deployment.

UML

Unified Modeling Language; a standardized language for visualizing, specifying, constructing, and documenting software artifacts.

4+1 View Model

A software architecture description method using four concurrent views plus a set of scenarios (use cases) to describe the architecture.

Logical View

The 4+1 view focusing on system functionality, components, modules, and their interactions from an end‑user perspective.

Development View

The 4+1 view concerned with software modules and their relationships from a developer’s perspective.

Process View

The 4+1 view focusing on runtime behavior, concurrency, distribution, performance, and scalability.

Physical View

The 4+1 view mapping software components onto hardware for deployment.

Scenarios/Use Cases

The fifth view of 4+1; describes sequences of interactions illustrating how the system functions.

ADL

Architecture Description Language; a formal language to describe software architecture components and their interactions.

Data Flow Architecture

A design pattern describing how data moves through a system from input to processing to storage to output.

Batch Sequential

A data processing model where each subsystem completes before the next processes, often using intermediate files and batch data.

Pipe and Filter

A data processing pattern where data passes through a series of independent filters connected by pipes, enabling modularity and reusability.

Process Control Architecture

An architecture for systems that monitor and regulate physical processes, used in embedded and real‑time control scenarios.

Subsystem

A part of a system that performs a portion of its function; can be a processing unit, controller, or module.

Controller

An element in a control system that computes and applies changes to a process variable, typically using sensor data.

Component-Based Architecture

A design approach that decomposes systems into reusable, well‑defined components with clear interfaces.

Component

A modular, portable, replaceable set of functionality exposing a high‑level interface; a software object that interacts with other components.

Object‑Oriented View

A component perspective focusing on collaborating classes, analyzing domain and design infrastructure and their interfaces.

Conventional View

A component perspective treating a component as a functional element with processing logic, data structures, and an invocable interface.

Process-Related View

A perspective emphasizing assembling pre‑existing library components to build the system, highlighting reuse and composability.

React.js

A popular JavaScript library for building user interfaces using reusable components.

Angular

A TypeScript-based framework for building web applications with a component‑based architecture.

Vue.js

A progressive JavaScript framework for building interactive web interfaces with reusable components.

Class Diagram

A UML structural diagram showing classes, their attributes, methods, and relationships.

Deployment Diagram

A UML structural diagram showing how software artifacts are physically deployed on hardware.