## 5 Proposed Interface Design Method
### Design Conceptualization  
As depicted in Figure 4, the design conceptualization integrates the outcomes from prior phases along with the SA and IA design guidelines. These guidelines comprise 50 SA-oriented design principles (available in [15]) and design guidelines derived from the different areas of the IA theoretical framework (found in [2, 34, 35, 36, 37]). A subset of these principles and guidelines, used in the practical application of the proposed method, is presented in Section 6.3. Design conceptualization within the Practical Application and Results section.  
The conceptualization process begins with selecting a goal and its SA requirements, which are elicited in the requirements analysis phase. The SA requirements are added to the design matrix, as depicted in Figure 3. The next step is to specify the design concept for each SA requirement according to the six design parameters of the matrix, as detailed below.  
1. _Description._ The GDATA method facilitates the description of the SA requirement by providing context or insights into the practitioners' work and information needs. It also identifies the SA level of the information requirement, which is crucial for effectively applying the SA and IA design guidelines.
2. _Type._ As indicated in Table 1, SA requirements can be explicit or implicit. For explicit SA requirements (e.g., text, numeric, date, and files such as attachments or multimedia), their type can be identified within their information source. Implicit SA requirements are mental constructs (e.g., SA levels 2-comprehension or 3-projection, practitioner's experience) and it should be stated in the design concept.
3. _Spatial association._ The association of a SA requirement with specific elements within the immersive environment depends on its nature or context. For instance, a \"practitioner's experience\" is implicit information that cannot be directly linked to an element. In contrast, a \"planned task\" is explicit information that can be associated with all the building elements involved in that task. In both cases, the design concept should explicitly state it. Additionally, the IA design guidelines from the situated analytics area provide insights for addressing the spatial association parameter.
4. _Visualization._ This specifies the position, visibility scope, arrangement, notifications, and other display features for the addressed SA requirement. The SA and IA design guidelines steer this specification. The designer should filter and apply the appropriate guidelines based on the SA level, type, and context of the SA requirement. A practical example is provided in Section 6.3 to assist the designer in this process.
5. _AR and MR interaction,_ respectively. It specifies the devices (e.g., handset, headset), interaction modes (e.g., tactile, eye/head gaze, and hand gesture), interaction tasks (e.g., selecting, tracking, and navigating), and the overall AR/MR interaction flow for all SA requirements addressed. AR/MR design considerations from the technology analysis phase assist in this specification. In addition, the SA and IA design guidelines, particularly those from the embodied data exploration area, contribute to conceptualizing the interaction flow.  
The system's operational requirements can provide valuable insights during the conceptualization process. Additionally, AR/MR design considerations and design guidelines from the various IA areas can support the conceptualization process across parameters. In this regard, it is recommendable for the designer to gather and thoroughly review these inputs for a more complete information presentation.  
The completed matrix documents the AR/MR interface design specifications, providing sufficient detail for prototyping and evaluating the design to effectively enable SA.