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 / Glossary

Architecture design concepts · 3.4.6

Solution information package

The work product of an engineering effort that carries the solution design so that implementation and other engineering related work can proceed from it. It includes the physical structure, behaviour, how things sit in time and space, and other attributes needed for implementation.

  • definition
  • Term
  • ISO/IEC/IEEE DIS 42024
  • Last updated: 2026-10-21

What this term settles

The solution information package is the counterpart of the architecture information package. It carries what implementation needs, including the relationships and attributes that are easy to lose between design and build. Naming it makes the second handover visible, which is where many audit trails stop.

What to do in your practice

Use one package structure for every implementation handover. Include the solution design, the build constraints, the environment assumptions and the acceptance criteria. Version it and record what it replaces. Keep the package with the entity record, not only with the project.

Who it binds

The role that owns the practice area the term governs. A definition binds nobody on its own; it binds the reader who adopts the term in a method, a description or a contract.

Evidence an auditor or regulator asks for

  • The package index with version, recipient and acceptance criteria.
    An auditor asks what implementation was based on.
  • The supersession record against the previous package.
    Prevents two versions being used at once.
  • The acceptance criteria and their verification.
    Shows the build was tested against the design.
  • The package retained with the entity record after project closure.
    Keeps the evidence available after the team disperses.
Ask your teamAfter the project closes, where is the solution information package kept, and who can retrieve it?

Common gaps this page catches

  • Packages live in project folders that are archived or deleted at closure.
  • No acceptance criteria are carried with the package.
  • Two versions are in use because supersession was never recorded.

What to prepare before publication

Add the solution information package to the entity record. Retrieve one package from a closed project and test whether a new engineer could implement a change from it.

Common questions

What does Solution information package mean in ISO 42024?
The work product of an engineering effort that carries the solution design so that implementation and other engineering related work can proceed from it. It includes the physical structure, behaviour, how things sit in time and space, and other attributes needed for implementation.
What evidence should we keep for 3.4.6?
The package index with version, recipient and acceptance criteria. The supersession record against the previous package. The acceptance criteria and their verification.

Related units

Source. ISO/IEC/IEEE DIS 42024, Clause 3.4.6, Terms and definitions. 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: definition. The definition is in the public preview. This page states it in our own words and does not reproduce the text.

Last updated: 2026-10-21 · Markdown version · Check your practice