Architecture concepts · 4.3
Architecture design and solution design
The subclause addresses the split between architecture design and solution design. It builds on 3.4.2 and 3.4.5: architecture design is the information needed to create, transform or understand an architecture, while solution design is the information needed to implement a solution entity.
What this unit settles
The introduction treats the split as basic: two kinds of design, one strategic and enduring, the other detailed and tactical. It also says the two can run concurrently. That is the clearest public statement of the split in the document.
What to do in your practice
Write the split into the delivery method as two outputs with different readers. Define what each must contain and which decisions belong to each. Where the two run concurrently, name the interface and the decision rights.
Who it binds
The organisation and the architecture practice. This unit is not a shall requirement; the claim level states what it is.
Evidence an auditor or regulator asks for
- The method with two design outputs and their readers.An auditor asks which output a decision belonged to.
- A decision rights table for architecture and solution decisions.Shows the split is operable.
- A concurrency note for parallel work.Explains how risk was managed.
- A sample of decisions classified by level.Proves the split is used.
Common gaps this page catches
- One design stage produces both outputs and no one owns the split.
- Solution teams make architecture decisions because no decision rights exist.
- Concurrent work has no interface record.
What to prepare before publication
Add the two outputs to the method and a decision rights table. Classify the last ten decisions. Where a solution team made an architecture decision, record it as a finding and fix the route.
Related units
Source. ISO/IEC/IEEE DIS 42024, Clause 4.3. Open the official record. Retrieved 21 October 2026.
https://www.iso.org/obp/ui/en/#iso:std:iso-iec-ieee:42024:dis:ed-1:v1:en
ISO catalogue record 87510, the status, stage and page count.
Claim level: concept, not an obligation. The subclause title is in the public preview. The body text is not public.
Last updated: 2026-10-21 · Markdown version · Check your practice