Function-Behaviour-Structure ontology¶
The Function-Behaviour-Structure ontology represents a designed object through what it is for, what it does, and how it is constituted, and models designing as transformations among those three views.
Core Idea¶
The Function–Behaviour–Structure (FBS) ontology represents a designed object through three related categories: function is what the object is for, behaviour is what it does or the measurable attributes through which purpose is realized, and structure is the components and relations of which it consists. Function is linked to structure through behaviour rather than mapped directly. A turbocharger's function may be to increase engine power; expected behaviours include target air-flow and efficiency characteristics; its structure includes compressor, turbine, shaft, geometry, materials, and interconnections.
Scope of Application¶
-
Requirements interpretation. Stakeholder purposes are formulated as functions rather than silently treated as component descriptions.
-
Synthesis. Designers propose structures expected to produce behaviors that satisfy selected functions.
-
Analysis and evaluation. Behavior derived from a structure is compared with expected behavior and functional need.
-
Reformulation. Mismatch can change the structure, expected behavior, or understanding of function rather than forcing one fixed path.
-
Documentation and traceability. Typed links explain why components exist and which performance claims justify them.
Clarity¶
Function–Behaviour–Structure ontology separates three statements often collapsed in design discussions: what an artifact is for, what it is expected or observed to do, and what components and relations embody it. The behavior layer makes the proposed realization testable without equating a purpose with one physical design. It also distinguishes expected from derived behavior, exposing mismatches that drive redesign.
Manages Complexity¶
Function–Behaviour–Structure ontology compresses a design's many requirements, analyses, and parts into three linked views. Functions state purposes, expected behaviors translate those purposes into observable performance, derived behaviors report what a proposed structure actually produces, and structure records components and relations. The analyst tracks mismatches between expected and derived behavior to locate redesign needs instead of debating purpose and embodiment in one vocabulary.
Abstract Reasoning¶
Decomposition move. From a design brief, infer functions first, then express expected behaviors before proposing structure. Analysis move. From a candidate structure, derive behavior and compare it with expected behavior to locate mismatch. Reformulation move. If mismatch persists, change function framing, behavior targets, or structure at the appropriate layer rather than editing components blindly. Comparison move. Evaluate alternative structures against the same functions and behaviors. Boundary move.
Knowledge Transfer¶
Within the home domain. The Function–Behaviour–Structure ontology transfers across product, mechanical, architectural, and software design when requirements are represented as functions, expected and derived behaviours mediate evaluation, and structure describes components and relations. Reformulation among these spaces retains the design-theory mechanism. Beyond the home domain (B — shared abstract mechanism). Biology and organizations also connect purpose-like roles, observable behavior, and arrangement, but intentional design and designer expectations may be absent. The portable pattern is mapping desired effects through behavior to organization. Using FBS outside design should not import teleology or claim that every function has an authored requirement.
Relationships to Other Abstractions¶
Current abstraction Function-Behaviour-Structure ontology Domain-specific
Parents (1) — more general patterns this builds on
-
Function-Behaviour-Structure ontology is a kind of Ontology Prime
Function-Behaviour-Structure ontology is a domain-specific kind of Ontology: The Function-Behaviour-Structure ontology represents a designed object through what it is for, what it does, and how it is constituted, and models designing as transformations among those three views.
Hierarchy path (1) — routes to 1 parentless root
- Function-Behaviour-Structure ontology → Ontology → Set and Membership
Neighborhood in Abstraction Space¶
Function-Behaviour-Structure ontology sits in a sparse region of the domain-specific corpus (63rd percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Cognitive & Behavioral Theories (16 abstractions)
Nearest neighbors
- Prototype-based programming — 0.86
- Long Parameter List — 0.84
- Naturalization of intentionality — 0.84
- Functional Fixedness — 0.84
- Simulation — 0.84
Computed from structural-signature embeddings · 2026-10-08