Skip to Content
Version 1.6 by Tjalling Haije on 2026/07/27 10:39
Show last authors
1 Design patterns of interest:
2
3 * [[TDP2 — Robots First, Then Humans Protocol>>2\. Specification.Requirements.TDP2 — Robots First, Then Humans Protocol.WebHome]]
4 * [[IDP1 — Role-Based, Context-Specific Information Distribution>>2\. Specification.Requirements.IDP1 — Role-Based, Context-Specific Information Distribution.WebHome]]
5
6 Approaches for evaluating DPs:
7
8 1. Make new usecases based on how the FR actually did the TDP and IDP with the robots with claims and check those with the raw data.
9 1. Match the premade usecase [[UC04.3: Detailed indoor exploration with ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]] with the incident that fits best, and evaluate the claims for the TDP and IDP of interest using results from that incident.
10
11 Choosing approach 2 because it has been prepared better, and helps in improving the evaluation approach for SFT 2 by identifying what info we missed.
12
13
14 == Design Patterns Evaluation ==
15
16 Approach:
17
18 1. Figure out in which incidents TDP2 and IDP1 were used
19 1. Check if the tech worked as required (or good enough to be of value) in those incidents
20 1. Figure out which of those incidents correspond most with [[UC04.3: Detailed indoor exploration with ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]]
21 1. Try to fill in [[j. SFT1 evaluation templates >>3\. Evaluation.SFT1.g\. Prototype .WebHome]]from the raw results, which
22 1. Check for each of the claims the results for the connected measures > Evaluates UC
23 1. Check for each of the pros/cons for the Design Pattern if they are validated > Evaluates Design Pattern
24 1. Adjust the Design Patterns based on the results and/or their expected pros/cons.
25 1. Update how the users should use the technology and/or the technology itself to achieve the objectives.
26 1. Note missing data that should be included in the evaluation next time.
27
28 == Design Patterns per Incident ==
29
30 |**Incident**|**Design Pattern**
31 | |
32 | |
33 | |
34 | |
35
36