A list of topics related to Software design and architecture principles, styles, patterns, practices, etc.

To this end, this section draws on the excellent roadmap.sh tool, which can be used to define a complete map of the concepts and notions relating to a given subject.

Roadmap Software Design and Architecture System Design Software Architect Full Stack Backend Frontend API Design

Topics


Levels of Architecture

In software engineering, architecture can be viewed from different levels of abstraction. Each level addresses a distinct set of concerns and requires a different scope of thinking. Understanding these levels is crucial for aligning technology with business goals and ensuring that systems are well-designed from the macro to the micro scale.

While various categorizations exist, a common and practical way to segment architectural focus is across three primary levels: Application, Solution, and Enterprise.

graph TD
    subgraph Levels of Abstraction
        direction TB
        EA(Enterprise Architecture) -->|Guides| SA(Solution Architecture)
        SA -->|Composed of| AppA(Application Architecture)
    end

    subgraph Scope
        direction TB
        EA_Scope("Entire Organization")
        SA_Scope("Business Need / Problem")
        AppA_Scope("Single Application")
    end

    EA --- EA_Scope
    SA --- SA_Scope
    AppA --- AppA_Scope

    style EA fill:#f9f,stroke:#333,stroke-width:2px
    style SA fill:#ccf,stroke:#333,stroke-width:2px
    style AppA fill:#9cf,stroke:#333,stroke-width:2px

This diagram illustrates the hierarchical relationship between the levels. Enterprise Architecture provides the high-level strategic context for Solution Architecture, which in turn orchestrates one or more applications, each with its own Application Architecture.

Application Architecture

Application Architecture is the lowest and most concrete level of architecture. It focuses on the internal structure and design of a single software application. The primary goal is to create a robust, scalable, and maintainable application that meets its specific functional and non-functional requirements.

Scope and Focus

  • Scope: A single application or service.
  • Focus: Technology stack, programming languages, frameworks, and libraries. It defines the modules, components, classes, and their interactions within the application.
  • Concerns: clean-code, performance, security within the application, and adherence to GoF design patterns.

Key Activities

Example Patterns & Technologies

Solution Architecture

Solution Architecture operates at a middle level, focusing on addressing a specific business problem or need by orchestrating multiple applications and systems. It acts as a bridge between the high-level strategic goals of Enterprise Architecture and the low-level details of Application Architecture.

Scope and Focus

  • Scope: One or more applications and services working together to fulfill a business requirement.
  • Focus: Integration between systems, data flow, and ensuring that the collection of applications works as a cohesive whole. It translates business requirements into a technical solution.
  • Concerns: communication-protocols, asynchronous-messaging, api-gateway, and data consistency across systems.

Key Activities

  • Analyzing business requirements and identifying the applications and services needed to meet them.
  • Defining the interfaces and interactions between different components of the solution.
  • Selecting the right technologies for integration and communication.
  • Managing trade-offs between quality, cost, and time for the solution.

Example Patterns & Technologies

Enterprise Architecture

Enterprise Architecture is the highest level of abstraction. It provides a holistic, strategic view of the entire organization’s IT landscape, processes, and business capabilities. The goal is to align the technology strategy with the business strategy, driving standardization, reuse, and efficiency across the enterprise.

Scope and Focus

  • Scope: The entire organization, including all its business units, applications, data, and infrastructure.
  • Focus: Business strategy, capability mapping, technology portfolio management, and governance. It defines the principles, standards, and roadmaps that guide the evolution of the IT landscape.
  • Concerns: Long-term technology vision, IT governance, cost optimization, risk management, and business process alignment.

Key Activities

  • Developing and maintaining the enterprise’s technology roadmap.
  • Defining and enforcing architectural standards and principles across all projects.
  • Identifying opportunities for consolidation, reuse, and simplification of the IT landscape.
  • Assessing the impact of new technologies on the business.

Example Frameworks

  • Frameworks: TOGAF (The Open Group Architecture Framework), Zachman Framework, FEAF (Federal Enterprise Architecture Framework). These frameworks provide structured approaches for designing, planning, implementing, and governing an enterprise information technology architecture.

Summary of Levels

LevelScopeFocusKey Artifacts
ApplicationSingle ApplicationCode, Components, Classes, Technical StackDesign Docs, Code, Component Diagrams
SolutionBusiness ProblemSystem Integration, Data Flow, APIsSolution Design, Integration Diagrams
EnterpriseEntire OrganizationBusiness Strategy, IT Landscape, GovernanceTechnology Roadmap, Standards, Principles