Function-Behaviour-Structure ontology

The Function-Behaviour-Structure ontology – or short, the FBS ontology – is an ontology of design objects, i.e. things that have been or can be designed. The Function-Behaviour-Structure ontology conceptualizes design objects in three ontological categories: function (F), behaviour (B), and structure (S). The FBS ontology has been used in design science as a basis for modelling the process of designing as a set of distinct activities. This article relates to the concepts and models proposed by John S. Gero and his collaborators. Similar ideas have been developed independently by other researchers.[1][2][3]

Overview

The ontological categories composing the Function-Behaviour-Structure ontology are defined as follows:[4]

The three ontological categories are interconnected: Function is connected with behaviour, and behaviour is connected with structure. There is no connection between function and structure.

Ontological Models of Designing

The Function-Behaviour-Structure ontology is the basis for two frameworks of designing: the FBS framework, and its extension, the situated FBS framework. They represent the process of designing as transformations between function, behaviour and structure, and subclasses thereof.

The Function-Behaviour-Structure Framework

The original version of the FBS framework was published by John S. Gero in 1990.[5] It applies the FBS ontology to the process of designing, by further articulating the three ontological categories. In this articulation, behaviour (B) is specialised into expected behaviour (Be) (the "desired" behaviour) and behaviour derived from structure (Bs) (the "actual" behaviour). In addition, two further notions are introduced on top of the existing ontological categories: requirements (R) that represent intentions from the client that come from outside the designer, and description (D) that represents a depiction of the design created by the designer. Based on these articulations, the FBS framework proposes eight processes claimed as fundamental in designing,[4][6] specifically:

Image showing the Function-Behaviour-Structure Framework.
The Function-Behaviour-Structure Framework
  1. Formulation: formulates the problem space, by transforming requirements into a function state space (R → F), and transforming functions into a behaviour state space (F → Be).
  2. Synthesis: generates structure based on expectations of the behaviour state space (Be → S).
  3. Analysis: derives behaviour from the generated structure (S → Bs).
  4. Evaluation: compares expected behaviour with the behaviour derived from structure (Be ↔ Bs).
  5. Documentation: produces descriptions of the design based on structure (S → D).
  6. Reformulation type 1: modifies the structure state space, based on a re-interpretation of structure (S → S’).
  7. Reformulation type 2: modifies the behaviour state space, based on a re-interpretation of structure (S → Be’).
  8. Reformulation type 3: modifies the function state space, based on a re-interpretation of structure and subsequent reformulation of expected behaviour (S → F’ via Be).

Example

The eight fundamental processes in the FBS framework are illustrated using a turbocharger design process.

  1. Formulation: External requirements (R) for a turbocharger are interpreted by the designer as functions (F) including to increase the power output of an engine. A set of behaviours (Be) is then produced that are expected to achieve this function. They include the air mass flow and efficiency ratios for a range of engine speeds.
  2. Synthesis: Based on the expected behaviours (Be), a structure (S) is produced that includes components such as a compressor, a turbine, a core assembly, a shaft, and their interconnections. It also includes their geometry and materials.
  3. Analysis: After the structure (S) is produced, the "actual" behaviours (Bs) can be derived based on that structure. This may include the physical testing of prototypes (e.g. for measuring air mass flow), and computational simulations (e.g. for calculating thermal behaviours).
  4. Evaluation: The "actual" behaviours (Bs) of the turbocharger are compared against the expected behaviours (Be), to assess whether the current turbocharger design performs as required.
  5. Documentation: The turbocharger design is documented by generating a description (D), commonly a CAD model, based on the structure (S).
  6. Reformulation type 1: The designer modifies the space of possible design structures (S) by including a new component such as a variable sliding ring inside the turbine.
  7. Reformulation type 2: The designer modifies the space of expected behaviours (Be) by introducing a new control behaviour that allows varying the air mass flow. This is a consequence of introducing the variable sliding ring into the design structure (S).
  8. Reformulation type 3: The designer modifies the function space (F) by adapting it to serve the needs of an engine with increased exhaust temperature. This is based on the discovery of a high thermal strength (Be) of existing design materials (S).

The Situated Function-Behaviour-Structure Framework

The situated FBS framework was developed by John S. Gero and Udo Kannengiesser in 2000[6] as an extension of the FBS framework to explicitly capture the role of situated cognition or situatedness in designing.[7][8]

Situatedness

The basic assumption underpinning the situated FBS framework is that designing involves interactions between three worlds: the external world, the interpreted world and the expected world. They are defined as follows:[4][6]

The three worlds are interconnected by four classes of interaction:

Situatedness and FBS Combined

The situated FBS framework is a result of merging the three-world model of situatedness with the original FBS framework, by specialising the ontological categories as follows:[4][6]

  • Fei: expected function
  • Fi: interpreted function
  • Fe: external function
  • FRe: external requirements on function
  • Bei: expected behaviour
  • Bi: interpreted behaviour
  • Be: external behaviour
  • BRe: external requirements on behaviour
  • Sei: expected structure
  • Si: interpreted structure
  • Se: external structure
  • SRe: external requirements on structure
Image showing the situated Function-Behaviour-Structure Framework.
The Situated Function-Behaviour-Structure Framework

20 processes connect these specialised ontological categories. They elaborate and extend the eight fundamental processes in the FBS framework, providing more descriptive power with regards to the situatedness of designing.

  1. Formulation: generates a design state space in terms of a function state space (process 7 in the image showing the situated Function-Behaviour-Structure Framework), a behaviour state space (processes 8 and 10), and a structure state space (process 9). It is based on the interpretation of external requirements on function (process 1), behaviour (process 2), and structure (process 3), and on the construction of memories of function (process 4), behaviour (process 5), and structure (process 6).
  2. Synthesis: produces a design solution that is a point in the structure state space (process 11) and an external representation of that solution (process 12).
  3. Analysis: interprets the synthesised structure (process 13) and derives behaviour from that structure (process 14).
  4. Evaluation: compares the expected behaviour with the interpreted behaviour (process 15).
  5. Documentation: produces an external representation of the design, which may be in terms of structure (process 12), behaviour (process 17) and function (process 18).
  6. Reformulation type 1: generates a new or modified structure state space (process 9). Potential drivers of this reformulation include processes 3, 6 and 13.
  7. Reformulation type 2: generates a new or modified behaviour state space (process 8). Potential drivers of this reformulation include processes 2, 5, 14 and 19.
  8. Reformulation type 3: generates a new or modified function state space (process 7). Potential drivers of this reformulation include processes 1, 4, 16 and 20.

Applications

The FBS ontology has been used as a basis for modelling designs (the results of designing) and design processes (the activities of designing) in a number of design disciplines, including engineering design, architecture, construction and software design.[10][11][12][13][14][15][16] While the FBS ontology has been discussed in terms of its completeness,[17][18][19][20] several research groups have extended it to fit the needs of their specific domains.[21][22][23][24][25][26] It has also been used as a schema for coding and analysing behavioural studies of designers.[27][28][29][30][31]

Notes

  1. ↑ Umeda et al. (1990)
  2. ↑ Chandrasekaran and Josephson (2000)
  3. ↑ Bhatta and Goel (1994)
  4. 1 2 3 4 Gero and Kannengiesser (2004)
  5. ↑ Gero (1990)
  6. 1 2 3 4 Gero and Kannengiesser (2002)
  7. 1 2 Schön (1983)
  8. ↑ Clancey (1997)
  9. ↑ Dewey (1896)
  10. ↑ Deng (2002)
  11. ↑ Christophe et al. (2010)
  12. ↑ Clayton et al. (1999)
  13. ↑ Kruchten (2005)
  14. ↑ Howard et al. (2008)
  15. ↑ Yan (1993)
  16. ↑ Colombo et al. (2007)
  17. ↑ Galle (2009)
  18. ↑ Dorst and Vermaas (2005)
  19. ↑ Vermaas and Dorst (2007)
  20. ↑ Ralph (2010)
  21. ↑ Cascini et al. (2013)
  22. ↑ Uflacker and Zeier (2008)
  23. ↑ Cebrian-Tarrason et al. (2008)
  24. ↑ Gu et al. (2012)
  25. ↑ Eichhoff and Maass (2011)
  26. ↑ Russo et al. (2012)
  27. ↑ Jiang (2012)
  28. ↑ Kan (2008)
  29. ↑ Kan and Gero (2009)
  30. ↑ McNeill (1998)
  31. ↑ Lammi (2011)

References

This article is issued from Wikipedia - version of the Thursday, December 10, 2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.