| Name | Functional Model |
| Abbreviation | FUM |
| Learning Cost | 100 |
| Playing Cost | 300 |
| Suggested Phases | 1,2 |
Engineers
| Mechanical Engineer | Industrial Design | System Engineer | Electrical Engineer | Production Engineer | Software Engineer |
| ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Technique and Issue Views
| BusinessNeeds | Stakeholder | Stakeholder Needs | System Requirements | System Structure Architecture |
| ✗ | ✗ | ✗ | ✔ | ✗ |
| System Functional Architecture | Detail Hardware Design | Detail Service Design | Detail Software Design | Manufacturing Operations |
| ✔ | ✗ | ✗ | ✗ | ✗ |
Technique Traits
| Identify Stakeholders | Elicit Needs | Remove Ambiguity | Layman's Terms | Technical Terms | Teamworkings |
| 1 | 1 | 2 | 2 | 3 | 1 |
| Traceability | Prioritizing | Exploring Breadth | Inside the Box | Outside the box | V&V |
| 2 | 0 | 0 | 0 | 0 | 2 |
Verification and Validation
| Analysis | Calculus | Inspection | Demonstration | Test |
| ✔ | ✗ | ✗ | ✗ | ✗ |
A functional model is a “structured representation of the functions (activities, actions, processes, operations) within the modelled system or subject area”. [1] While its history can be traced back in the 19th century, the technique as we know it now originates in the ‘50s/’60s in the fields of system and software engineering. The functional model is usually created in early stages and its aim is to graphically represent the functions and processes, help recognize information needs, identify opportunities, and create a baseline that will later be used to determine product and service costs. A ffunctional model can take several forms: block diagrams, flow block diagrams, HIPO (hierarchical input process output), N2 Charts, SADT (structured analysis and design technique) and IDEF0 are all common ways to perform and represent a function model. [2]
