# Architectural Trends in Collaborative Computing: Approaches in the Internet of Everything Era
## 3 Methodology  
This section outlines the research process used in this work, which follows the Rapid Review methodology [13]. This methodology emerged in the medical field as a quicker alternative to the Systematic Literature Review for gathering evidence [39]. Rapid Reviews address broader research questions than Systematic Literature Reviews, with these questions defined a priori. Like Systematic Literature Reviews, Rapid Reviews follow a predefined protocol to maintain academic rigor. Compared to Systematic Literature Reviews, the Rapid Review protocol is less labor-intensive as it may omit or simplify certain steps, such as a limited number of databases analyzed, allowing a single person to select studies, and skipping the formal synthesis of results [40]. We formulated two research questions (RQs) to address this practical problem:  
**RQ1. **: How does computing architecture relate to the collaboration type? **RQ2. **: Due to the rapid evolution of IoE devices, what adaptive and forward-looking architectural strategies can be developed? The first question (RQ1) focuses on architectural computing to support collaboration; this question is crucial to observe how architecture affects collaboration and what the most important characteristics are beyond the application's objective to enhance and increase the desired type of collaboration. The second question (RQ2) emphasizes the need for a proactive architecture that anticipates the societal impacts of rapidly evolving IoT devices, ensuring both functionality and ethical user experiences. The search string used in this work followed this structure: Analyze Technology and Architecture, Collaborative Computing, Trends and Future. The expression to analyze technology and computing architecture focuses on smart devices in the computing domain. The expression to collect collaborative computing articles targets the synergy between collaboration and computing. Finally, the expression to study the future and trends seeks articles outlining forward-looking insights in collaborative computing architecture. Table 1 shows the final search string. **Analyze Technology and Architecture:**: \"Smart\" AND \"Device\" AND (\"Architecture\" OR \"Approach\" );
**Collaborative Computing:**: (\"Collaborative\" OR \"Collaboration\") AND \"Computing\";
**Trends and Future:**: \"Future\" OR \"Roadmap\" OR \"Research Avenue\" OR \"Research Agenda\" OR \"Trend\" OR \"Vision\" OR \"Prospect\" OR \"Outlook\". **Query String**  
smart AND device AND (collaborative OR collaboration) AND computing AND (architecture OR approach) AND (future OR roadmap OR \"research avenue\" OR \"research agenda\" OR trend OR vision OR prospect OR outlook) AND (PUBYEAR \(\geq\) 2018) AND (LIMIT-TO (LANGUAGE, \"English\")) \begin{table}
\begin{tabular}{l}
**Query String** \\ smart AND device AND (collaborative OR collaboration) AND computing AND (architecture OR approach) AND (future OR roadmap OR \"research avenue\" OR \"research agenda\" OR trend OR vision OR prospect OR outlook) AND (PUBYEAR \(\geq\) 2018) AND (LIMIT-TO (LANGUAGE, \"English\")) \\ \end{tabular}
\end{table} 
Table 1: Search expression for Scopus database. Figure 2: 3C Model proposed, adapted from [PERSON] et al. [20]. In developing the methodology for our research, we adapted our proposed search query across various academic research platforms to collect articles pertinent to our study. ISI Web of Science, Scopus, and Google Scholar were the chosen platforms. For the ISI Web of Science platform, we used a search strategy targeting the topics: title, abstract, author keywords, and keywords plus. Meanwhile, for the Scopus platform, our search was narrowed to focus on the bstract, title, andkeywords. The inclusion criteria used in our work were defined as follows:  
**Thematic Relevance:**: Articles must directly address the research question's theme, exploring the relationship between computing architecture and collaboration types for RQ1 and proposing adaptive architectural strategies for IoE devices for RQ2.