# 3.4.6 Solution information package, ISO 42024 ## Published contents Contents1 Scope2 Normative references3 Terms and definitions4 Architecture concepts4.1 Overview4.2 Architecture and architecting4.3 Architecture design and solution design4.4 Architecture definition and communication4.5 Stakeholder concerns and architectural aspects4.6 Architecture viewpoints and architecture views4.7 Architecture frameworks and architecture description languages4.8 Architecture descriptions and architecture models4.9 Reference architectures and reference models4.10 Life cycle and life history4.11 Architecting precepts5 Architecting principles5.1 Introduction to the principles5.2 Principles about the purpose of an architecture5.3 Principles about the focus of an architecture5.4 Principles about architecting outcomesTerms 3.2 Architecting concepts 3.2.1 Architecture3.2.2 Architecture feature3.2.3 Architecting3.2.4 Architecting principle3.2.5 Architecture principle3.2.6 Architecture framework3.2.7 Reference architecture3.3 Entity related concepts 3.3.1 Entity of interest3.3.2 Solution entity3.3.3 Environment3.3.4 Context3.3.5 Enterprise3.3.6 System3.3.7 Aspect3.3.8 Dimension3.4 Architecture design concepts 3.4.1 Design (noun)3.4.2 Architecture design3.4.3 Architecture information package3.4.4 Engineering effort3.4.5 Solution design3.4.6 Solution information package3.4.7 Stakeholder3.4.8 Stakeholder perspective3.4.9 Concern3.5 Architecture description concepts 3.5.1 Architecture description3.5.2 Solution description3.5.3 Architecture view3.5.4 Architecture viewpoint3.5.5 Model3.5.6 Metamodel3.5.7 Reference model3.6 Entity life cycle concepts 3.6.1 Life cycle3.6.2 Life cycle phase3.6.3 Life cycle stage3.6.4 Life historyAnnexes A.1 Architecture design and solution related entitiesA.2 Architecture expressed as a set of modelsA.3 Life cycle and life history conceptsA.4 Enterprise and system conceptsA.5 Duality of architectural decomposition and architectural synthesisB.1 BackgroundB.2 Aligning architecture in designB.3 Duality of architectureB.4 Pursuit of opportunities 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 - 3.4.3 - 3.4.5 - 3.5.2 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 Source: https://iso-42024-revision-checker.theartofservice.com/glossary/solution-information-package/