System Functions

1.

Collect User Needs

There are various User Needs Analysis methods. Most widely used are user journey nap, scenario, interviews, and questionnaires. You may fine more information on the webpages dedicated to each method.

2.

Map User Needs to Flows (E,M,S)

Flow is a representation of quantities that are input and output by functions. There are three basic flows for design problems:

• Energy - human, electrical, hydraulic, magnetic, mechanical etc.

• Material - human, gas, solid, liquid

• Signal - information (status, control)

3.

Create Function Tree/Chain/List  for Flow/Need/Activity

A function list is a list of product functions presented in functional basis form. In this form function is characterized in a verb-object (functional basis*). 

​

A function tree is used to represent the system architecture that is intended to be developed in this roadmap, and to provide the context within which each subsequent design team will operated. 

​

A function structure is a graphical form of a functional model where its overall function is represented by a collection of sub-functions connected by the flows on which they operate. Explicitly related to customer needs.

​

*A functional basis that is used for creating system function is a design language where product function is characterized in a verb-object (function-flow) format.

4.

Aggregate/Combine

A unifying review that summarizes the explored functional requirements.

A.

Decomposition and breaking down function is a recognized skill of the top designers. Therefore it is important to know how to breakdown a system into key subsystems.

B.

Develop an extensive vocabulary of functions such as with the functional basis or vocabulary. This takes practice.

C.

Seek an "atomic" level of function i.e, atomic functions are actionable. They can be solved with single entities. (e.g. Function: translatory motion - action: install a single motor)

D.

Function and function modelling enable and empower creativity. Therefore, use a set of key functions as the opportunity statements for ideation/develop methods such as mind mapping.

E.

Functions/functional models are the building blocks for system architecture, seeking insides such as modularity, portfolio, etc.

F.

In function flow, it is important to map inputs to outputs.

G.

Functions are abstract because they are about actions while ideas start with objects (nouns).