Software Architecture

Modularity refers to the design of systems from independent, interchangeable components.

An architecture decision record documents decisions about system architectures.

Framework and rules for steering architectural decisions, responsibilities and standards across an organization.

An architectural paradigm that shapes systems to evolve incrementally and in a controlled manner over time.

Concept for structuring interfaces between components, APIs and user-facing elements, focusing on consistency and integration readiness.

A message broker is a software framework that facilitates the exchange of data between different systems.

Service Integration unifies distributed applications and APIs into coherent business processes, covering interface, messaging, and orchestration strategies.

Guiding rules for decisions about system structure, interfaces and quality attributes that promote consistency, maintainability, and scalability.

Conceptual description of a software system's structure, components and interfaces to satisfy functional and non-functional requirements.

Conceptual guidelines for structuring and designing scalable, maintainable software systems.

ATAM is a structured method for analyzing and evaluating architectures.

A systematic approach to ensuring and improving system and software performance across the entire lifecycle.

Concept of non-functional quality properties of systems that shape architectural decisions and evaluation criteria.

An architectural approach based on the generation and processing of events to decouple and make systems responsive.

An architectural pattern that organizes systems into layers to promote modularity and separation of concerns.

Architectural style that splits applications into autonomous, small services to enable scalability, independence, and faster deployment.