System Architecture Design

A current map of your system, ranked quality attributes, trade-off decisions you can defend, and the review habits that keep the design honest as the build moves on.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for System Architecture Design, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

208

Starter tasks

⚙️ Software Engineering

System Architecture Design

Designing how a software system is structured, from components and data flow to boundaries and trade-offs, before and during the build.

  1. Current-state architecture map of the system
  2. Ranked quality attributes for the system
  3. Architectural constraints and drivers register
  4. External dependency and integration inventory
  5. Domain glossary and core entity map
  6. Request walkthrough of the busiest user flow
  7. Data flow map with sensitive data marked
  8. Diagram notation and tooling agreed for the team
  9. One-page design proposal format for the team
  10. Monthly architecture map refresh
  11. Weekly design clinic for the team
  12. Architecture risk register kept current
  13. Architectural fitness functions in the pipeline
  14. Architecture metrics log
  15. Quarterly architecture health review
  16. Assumptions log for load, team and growth
  17. Building blocks radar for approved technologies
  18. Design versus as-built retrospective
  19. Writing quality attribute scenarios that can be tested
  20. Trade-off analysis with a utility tree
  21. Architecture katas with the team
  22. Strategic domain-driven design and bounded contexts
  23. Back-of-envelope estimation for design choices
  24. Architecture styles compared on your own system
  25. Failure mode walkthrough of each component
  26. Architecture reading list for the year
  27. Modular monolith boundaries in the existing codebase
  28. Synchronous versus asynchronous integration for one flow
  29. Build versus buy for a non-core capability
  30. Choosing the data store for a new component
  31. Ports and adapters around one core module
  32. Removing a single point of failure from the map
  33. Where authentication and authorisation checks live
  34. Classifying pending decisions as reversible or one-way
  35. Design review of the next major feature
  36. Target architecture for the next 18 months
  37. Pre-launch architecture readiness check
  38. Architecture pack for a customer security review
  39. Kick-off architecture workshop for a new product
  40. Taking over a system as the new tech lead
  41. Keeping architecture simple in a small startup team
  42. Greenfield service design from a product brief
  43. Design reviews across time zones
  44. Reconciling two architectures after a team merger
  45. Architecture choices for a solo contractor build
  46. Tenant isolation model for a multi-tenant product
  47. Event storming a core business process
  48. Regional deployment and data residency architecture
  49. Plugin and extension architecture for third parties
  50. Cell-based layout to limit blast radius

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Current-state architecture map of the system

Most teams carry the architecture in two or three heads, and the diagram on the wiki shows the system as it was planned eighteen months ago. Drawing a context diagram and a container diagram of what actually runs in production today gives every later decision in this area a shared starting point and shows the surprises early: the cron job nobody owns, the second database, the service that calls back into its caller.

First tasks

  • List every deployable unit from the deployment configuration or cloud console
  • Sketch the context diagram with users and external systems on one page
  • Draw the container diagram with data stores and protocols on each arrow
  • Walk the diagrams with two colleagues and mark every disputed arrow
  • Commit the diagrams to the repository with the date drawn

Ranked quality attributes for the system

Every design choice trades one quality for another, and a team that has not ranked availability, latency, cost, security and ease of change will argue the same trade-off from scratch every sprint. Agreeing a ranked top five, each with a number attached where one is real, turns those arguments into a short check against something already written down.

First tasks

  • Ask five colleagues to name the quality they would protect above all others
  • Merge the answers into a single list of candidate attributes
  • Run a forced-ranking session with product and engineering leads
  • Attach a measurable target to each of the top five attributes
  • Publish the ranked list at the top of the architecture page

Architectural constraints and drivers register

Constraints are the decisions already made for you: the cloud provider the company signed with, the language the team knows, the regulator's rules on where data lives, the launch date marketing announced. Writing them down separately from preferences stops the team designing an ideal system that cannot be built, and makes it obvious when a constraint has quietly expired.

First tasks

  • Write down every rule the system must follow that the team did not choose
  • Sort the list into technical, organisational, regulatory and commercial groups
  • Mark each constraint fixed or negotiable and name who could change it
  • Confirm the three most limiting constraints with their owners

Make it yours.

Install System Architecture Design, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.