Changes for page 3. Evaluation

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,5 +1,21 @@
1		-The design evaluation aims to test and validate the system’s design, or to discriminate between multiple design options, such that the current design can be improved upon in incremental development cycles. The SCE method describes two parts that are relevant with respect to the system evaluation: (1) the prototype and/or simulation, and (2) the evaluation that describes the evaluation method and results.
	1	+The design evaluation process is intended to assess and validate the system’s architecture, or to differentiate between various design alternatives, thereby facilitating incremental improvements in successive development cycles. The SCE methodology outlines two key components pertinent to system evaluation: (1) the prototype and/or simulation, and (2) the evaluation, which details the assessment approach and findings.
2	2
	3	+Within the SYNERGISE project, initial assessments were conducted through CFTs (Component Field Tests), followed by comprehensive SFTs (System Field Tests). The CFTs involved only selected technologies, whereas the SFTs integrated all developed technologies for thorough testing.
3	3
	5	+This evaluation chapter will present all prototypes created for the HMT framework, accompanied by their corresponding CFT tests. Prototype documentation illustrates the concepts and principles of HMT, while test reports detail interactions with users and summarize the results obtained.
4	4
	7	+
	8	+== CFT1: Data visualisation ==
	9	+
	10	+This first CFT evaluated how sensor data - specifically health, location, and communication data - can support decision-making in USAR operations at tactical and operational levels. Twelve participants from various roles completed questionnaires assessing their data needs and preference for [[visualization formats>>doc:.a\. Prototype.WebHome]]. The [[study found>>doc:.b\. Test.WebHome]] that different roles require different types and levels of data detail: tactical users prefer aggregated overviews, while operational users need real-time, detailed information.
	11	+
	12	+== CFT2: Concept of Operations ==
	13	+
	14	+During the second CFT the Concept of Operations (ConOps) was evaluated. Through[[ structured sessions>>doc:.d\. Test.WebHome]] involving presentations of multiple[[ use cases>>doc:.c\. Prototype .WebHome]] and participant feedback, the study explored operational feasibility, safetly, and team dynamics. [[Key findings>>doc:.d\. Test.WebHome]] highlighted the importance of context in technology deployment, the need for rapid and logical task distribution, and the critical role of human oversight.
	15	+
	16	+== CFT3: Two Detailed Use Cases ==
	17	+
	18	+
	19	+== CFT4: Human-Machine Teaming ==
	20	+
5	5