Course summary

Software Architecture

Use this page to revisit what each stage gives you and return to the exact weak point that needs another pass.

Stage 1 of 3

Software Architecture Foundations

Start from what architecture is for, and how to think about components, boundaries and responsibilities in small systems.

M01

Discovery and requirements

Learn to identify what you're building and what could go wrong.

Open module
M02

Architecture and design

Document and communicate architectural decisions using C4 models, Architecture Decision Records, API contracts, and security by design principles.

Open module
M03

Implementation and build

Write secure, maintainable code with proper input validation, output encoding, session management, error handling, and supply chain security.

Open module
M04

Verification and testing

Ensure quality and security through comprehensive testing strategies, OWASP ASVS integration, accessibility testing with WCAG 2.2, and performance testing.

Open module
M05

Deployment and CI and CD

Automate secure deployments with CI/CD pipelines, DevSecOps integration, deployment strategies, and Infrastructure as Code basics.

Open module
M06

Operations

Run systems reliably in production with Google SRE principles, four golden signals, observability triad, and effective incident response.

Open module
M07

OSI model and diagnostics

Master troubleshooting tools and techniques using OSI layers, browser DevTools, command-line diagnostics, and TLS certificate inspection.

Open module
M08

The ilities framework

Evaluate systems across quality attributes including security, privacy, accessibility, performance, reliability, scalability, maintainability, and more.

Open module
M09

Foundations assessment

Now that you have worked through all eight modules, it is time to test your understanding.

Open module

Stage 2 of 3

Software Development and Architecture Intermediate

Layered patterns, microservices, events, data ownership and real trade offs between coupling, performance and changeability.

M01

Architecture styles in the real world

The big styles are patterns, not rules.

Open module
M02

Integration and APIs

Systems talk in two main ways.

Open module
M03

Quality attributes and trade offs

latency and throughput are easy to measure.

Open module
M04

Data, state and consistency

State hides everywhere.

Open module

Stage 3 of 3

Software Development and Architecture Advanced

Event driven systems, CQRS, integration patterns, observability and digitalisation strategy across whole organisations.

M01

Domains and bounded contexts

Glossary Tip.

Open module
M02

Advanced patterns and distribution

Glossary Tip.

Open module
M03

Resilience and performance under failure

Caching helps, but it creates new risks.

Open module
M04

Evolution and governance

Glossary Tip.

Open module