7.2 Clause
Relation between AI tasks, AI components, AI methods and AI capabilities
The subclause relates four things that are often conflated: the task the system performs, the components that perform it, the methods those components use and the capabilities the system shows. The relation is what lets a reader move from a task to a method and from a capability to a component.
What this settles
Most description failures are category errors. A task is written where a method belongs, or a component is credited with a capability that only the combination delivers. Naming the four categories is half the fix.
Who it binds
The organisation, as a method choice. It creates no duty but it creates a discipline that makes the description usable by more than one team.
What to do in your practice
Use four columns for every system: task, component, method, capability. A row may repeat across columns, but each column answer must be independent. Then check the joins: every task has a component, every component a method, every capability a source.
Evidence an auditor or regulator asks for
| A four-column table for one live system. | Shows the categories are separated in practice. |
|---|---|
| A join check with no orphan task, component or capability. | Proves the relation is complete. |
| A note of any row where the category was contested. | Records the judgement, not just the result. |
Which row in our description mixes a task with a method, and what did that hide?
Common gaps this page catches
- The inventory column "use case" mixes tasks, components and methods in one free-text field.
- A component is credited with a capability that requires orchestration.
- No join check exists, so orphan rows go unnoticed.
What to prepare before publication
Rebuild one system description in the four columns and run the join check. The orphan rows are the action list.
How to test it here
Take one live system rather than a template, find the field or sentence where Relation between AI tasks, AI components, AI methods and AI capabilities is used, and put this page beside it. Record the answer, the artefact and the date. A glossary entry on its own is an intention; a dated record beside a live artefact is evidence.
What this page does not claim
The page does not reproduce the draft, does not know the descriptor wording that the public preview withholds, and does not certify the system or the organisation. It states the unit at the claim level "framework clause" and stops where the public record stops.
Common questions
- What does Relation between AI tasks, AI components, AI methods and AI capabilities mean in ISO/IEC DIS 42102?
- The subclause relates four things that are often conflated: the task the system performs, the components that perform it, the methods those components use and the capabilities the system shows. The relation is what lets a reader move from a task to a method and from a capability to a component.
- What evidence should we keep for 7.2?
- A four-column table for one live system. A join check with no orphan task, component or capability.
- Is Relation between AI tasks, AI components, AI methods and AI capabilities a requirement?
- No. The draft is a descriptive framework. It sets no management system requirement and no conformity test. It becomes binding only when a contract, a regulator or a management system adopts it.
Related units
Last updated: · Markdown version · Check your system