Relationship-oriented function modelling
Jump to navigation
Jump to search
Activities
- Activity 1: Clarifying and itemising the problem or Task
- Activity 2: Determining functions and their structures
Necessary tools
- Software support for easier restructuring of a large number of elements
Description
Relation-oriented functional modeling can promote system understanding by identifying strengths, weaknesses, useful and harmful components, and relationships in the system. In this way, development priorities can be determined and recognized.
Procedure
- Formulate the goal of functional modeling: For what purpose should the system be abstracted?
- Determine the appropriate level of abstraction, depending on the purpose of the abstraction: focus on essential aspects
- Define the system boundary that separates the system under consideration from the environment
- Determine the essential useful function of the system under consideration
- Determine the main malicious function of the system under consideration
- Are there other functions for which the (essential) useful function is required?
- Are there functions that are required for the (essential) useful function?
- Are there other malicious functions caused by the (essential) malicious function?
- Are there functions that cause the (essential) malicious function?
- Are there any features introduced to avoid the (essential) malicious feature?
Complete the functional model using these questions
- The questions will be asked again for all newly added functions
- Stop building the functional model when all important useful and harmful functions of the system under consideration have been mapped (3 or 4 iterations are usual).
- Generate problem formulations to reinforce useful functions and to avoid/mitigate the harmful functions
Sources
- Kumke 2018
- Lindemann 2009, p. 301, 302