ISO 42024 Revision Checker
ISO/IEC/IEEE DIS 42024 · Enterprise, systems and software, Architecture fundamentals Stage 40.99 Planning date 15 Sep 2027, an estimate 35 terms · 20 clause areas · 9 annex sections

Home / Concepts

Architecture concepts · 4.7

Architecture frameworks and architecture description languages

The subclause addresses architecture frameworks and architecture description languages. It builds on architecture framework (3.2.6) and the description concepts in 3.5. A framework supplies conventions, principles and practices for a domain or community; a description language supplies the means to express a description.

  • concept, not an obligation
  • Clause area
  • ISO/IEC/IEEE DIS 42024
  • Last updated: 2026-10-21

What this unit settles

The two are often conflated in procurement. A framework is a way of working; a language is a notation. The document places both in the surrounding practice rather than inside the definition of architecture, which is a useful boundary for a firm deciding what to buy and what to build.

What to do in your practice

Keep a register with two sections, frameworks and languages. For each, record the source, version, the part in use, the tailoring and the owner. Record the mapping between the language and the metamodel, and the precedence rule when two frameworks disagree. Test the language against three concepts the firm cares about but rarely models, for example a regulatory obligation or an operational mode. If the language cannot express them, the framework will silently exclude them from every review that relies on the tool. That is a governance finding, not a tool preference.

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 framework and language register.
    An auditor asks which conventions and notations the descriptions follow.
  • The tailoring record per framework.
    Shows what was changed and who approved it.
  • The language to metamodel mapping.
    Shows the notation can express the concepts.
  • The precedence rule.
    Prevents contradictory conventions.
Ask your teamWhich framework and which language does this description use, and who owns the tailoring of each?

Common gaps this page catches

  • The tool language is assumed to be the framework.
  • Tailoring is undocumented.
  • Two frameworks are in use with no precedence rule.

What to prepare before publication

Build the two section register. For the main description, record the framework, the language, the tailoring and the owner. Test the language against the concepts the firm needs.

Common questions

What does Architecture frameworks and architecture description languages mean in ISO 42024?
The subclause addresses architecture frameworks and architecture description languages. It builds on architecture framework (3.2.6) and the description concepts in 3.5. A framework supplies conventions, principles and practices for a domain or community; a description language supplies the means to express a description.
What evidence should we keep for 4.7?
The framework and language register. The tailoring record per framework. The language to metamodel mapping.

Related units

Source. ISO/IEC/IEEE DIS 42024, Clause 4.7. 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