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

Entity related concepts · 3.3.6

System

A grouping of parts or elements whose combined behaviour or meaning is stated and is not present in any part alone. A complete system includes the equipment, facilities, material, programs, firmware, documentation, services and people needed for operation and support.

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

What this term settles

The definition makes the system boundary depend on the stated behaviour. That is a useful discipline: the boundary is not whatever the team finds convenient, it is the smallest arrangement that produces the behaviour in question. The second sentence also stops the common habit of calling software a complete system when it depends on people and facilities.

What to do in your practice

For each system, write the behaviour that the arrangement produces and that no part produces alone. Then list the equipment, people, facilities and services the behaviour depends on. If the list includes people outside the team control, the system boundary is wider than the delivery boundary, and that difference should be explicit.

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

  • A system boundary statement with the stated behaviour.
    An auditor asks what the system is supposed to do and where it stops.
  • A dependency list covering people, facilities and services.
    Shows the boundary is complete rather than convenient.
  • A record of interfaces at the boundary.
    Lets a reviewer test whether the behaviour can actually be delivered.
  • The owner of the stated behaviour.
    Gives the boundary an accountable role.
Ask your teamWhat behaviour does this arrangement produce that no part produces alone, and who owns that behaviour?

Common gaps this page catches

  • The system boundary is the application boundary, while the behaviour depends on people and suppliers.
  • No stated behaviour exists, so the boundary is contested at every change.
  • Interfaces are listed for software only.

What to prepare before publication

Take one system and write the stated behaviour in one sentence. Then list everything the behaviour needs, including people. The difference between that list and the current boundary is the first scope correction in the plan.

Common questions

What does System mean in ISO 42024?
A grouping of parts or elements whose combined behaviour or meaning is stated and is not present in any part alone. A complete system includes the equipment, facilities, material, programs, firmware, documentation, services and people needed for operation and support.
What evidence should we keep for 3.3.6?
A system boundary statement with the stated behaviour. A dependency list covering people, facilities and services. A record of interfaces at the boundary.

Related units

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