Skip to Content
Last modified by Tjalling Haije on 2025/09/15 08:07
From version 11.1
edited by Tjalling Haije
on 2025/09/08 13:50
Change comment: There is no comment for this version
To version 8.1
edited by Tjalling Haije
on 2025/09/08 13:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -b. Definitions and Concepts
1 +c. Definitions and Concepts
Content
... ... @@ -8,7 +8,7 @@
8 8  |**Design specification**|The design specification is the collection of use cases, requirements, claims, and ontology. Together they describe the outline of the system's behaviour, functionalities, and intended effects. This should be sufficient to provide a blueprint for developers to implement the design in an operational, interactive version of the system (a prototype). A specification refers to an explicit set of requirements to be satisfied by a design, system, product, or service.
9 9  |**Functional requirement**|In the SCE method, functional requirements describe functional properties of the system that follow directly from the user requirements and/or the operational demands. Functional requirements are described as “the system shall do <requirement>”. The MoSCoW (Must have, Should have, Could have, Won't have this time) method can be used to prioritise the requirements.
10 10  |**Human Factors concept**|A Human Factors (HF) concept is an idea, principle, or theory based in the human factors literature. The concept is deemed relevant to the design if it can be used to stipulate the design rationale, claims, or design pattern premises.
11 -|**Human-machine Teaming**|Human-machine teaming (HMT) refers to the collaborative interaction between humans and technological systems—including AI, robotics, and decision-support systems—designed to optimize performance, decision-making, and mission effectiveness in complex environments.
11 +|**Human Machine Teaming**|
12 12  |(% colspan="1" %)**Design pattern**|(% colspan="1" %)(((
13 13  Design is about shaping digital things for people’s use. Its main focus is on behaviour and imagining things as they might be.
14 14  
... ... @@ -18,7 +18,7 @@
18 18  
19 19  We distinguish Team Design Patterns (TDP) and Interaction Design Patterns (IDP).
20 20  )))
21 -|(% colspan="1" %)**Team design pattern**|(% colspan="1" %)Team Design Patterns (TDPs) are structured, reusable solutions that describe recurring configurations of team behavior—whether among humans, agents, or hybrid teams—to support effective collaboration, coordination, and adaptation in complex environments.
21 +|(% colspan="1" %)**Team design pattern**|(% colspan="1" %)<tbd>
22 22  |**Interaction design pattern**|(((
23 23  Interaction design is heavily focused on satisfying the needs and desires of the majority of people who will use the product. To be inclusive, the diversity of the potential end-user population should be well addressed.
24 24