Baumgart Software Guide Send a brief
  1. Home
  2. Services
  3. Software design

Software design and architecture

Design turns agreed requirements into a structure that can be built, tested and operated. We draw the system at the right level of detail, decide the hard questions in writing and test screens with users while changes are still cheap.

Illustration for Software design
Illustration drawn for this site, not a screenshot of a client system.

When this helps

  • Requirements are agreed and you need a buildable plan.
  • An existing system must be extended and nobody has a current diagram of it.
  • You want independent design documents before choosing a development team.

How the work runs

  1. Draw the context and containers. We use the C4 model, whose four hierarchical diagrams are system context, container, component and code (c4model.com). Most projects need the first two; the others are drawn only where they help.
  2. Model the data. Entities, their relations and their life cycle, including what personal data is stored, why, and for how long.
  3. Sketch and test screens. Low-fidelity wireframes first, then clickable prototypes for the critical journeys, checked against accessibility targets from WCAG 2.2.
  4. Record decisions. Every significant choice becomes an architecture decision record with title, context, decision, status and consequences, the format described by Michael Nygard.
  5. Review security early. We walk through the design against the risk categories of the current OWASP Top 10 and note the controls each one needs.
  6. Plan increments. The backlog is sliced into increments that each produce working, testable software.

Artefacts you receive

ArtefactWhat it is for
Context and container diagramsWho uses the system and which parts it consists of.
Data modelEntities, relations, retention notes.
Wireframes and prototypeThe critical screens and flows.
Architecture decision recordsWhy the structure looks the way it does.
Security and accessibility notesTargets and the controls that meet them.
Increment planWhat each increment delivers, without calendar promises.

What we need from you

  • Agreed user stories or time for a short analysis step first.
  • Information about existing systems and hosting rules.
  • Users available for prototype tests.