# Privacy Framework for the Development of IoT-Based Systems
## 4 Related Work
### Positioning Against Existing IoTS Development Methodologies  
While the comparative analysis focused on privacy- and security-oriented approaches, it is also relevant to consider IoTS development methodologies that provide a more general project structure. One such example is the Three-Phase Methodology (TpM), which organizes the development process into three vendor-agnostic stages: business consideration, requirements gathering, and implementation. Its extended version, TpM-Pro, incorporates a situational method composition approach to enable the selection of development artifacts based on specific project needs.  
However, despite their practical value in structuring IoTS development activities, neither TpM nor TpM-Pro provides direct integration of privacy-by-design principles or specific support for privacy requirements across the development lifecycle. Our proposed framework addresses this shortcoming by systematically embedding privacy mechanisms, thereby offering developers structured, privacy-aware guidance throughout all phases of IoTS system development. More precisely, our proposal introduces the following key advantages over existing approaches:  
* Integration of privacy concerns throughout the entire IoTS development lifecycle, addressing gaps present in existing solutions.
* A developer-oriented workflow with clear and practical steps for embedding privacy.
* Support emerging technologies, such as federated learning and zero trust, to enhance adaptability.  
\begin{table}
\begin{tabular}{p{56.9 pt} p{56.9 pt} p{56.9 pt} p{56.9 pt} p{56.9 pt} p{56.9 pt}} \hline \hline
**Aspect** & **Security-Focused Approaches** & **AI-Based Detection** & **Zero Trust Models** & **Frameworks and Guidelines** & **Privacy-by-Design Framework** \\ \hline Main Focus & Vulnerabilities and countermeasures & Threat detection via ML/DL/FL verification & Access control and contributions verification & Regulatory & Developer & Systematic privacy \\ Privacy-by-Design & Limited or absent & Partial, privacy-preserving techniques & Limited privacy focus & Limited developer-focused integration & Strong focus on PbD & Core element throughout development \\ Developer Support & Minimal procedural guidance & Focus on detection, not development & Complex implementation & Limited developer & Guidelines & Stepwise, but limited developer-friendly tools \\ Alignment & Limited with IoTS Development & Limited relevance & Operational focus & Limited lifecycle integration & Design-phase focused & Full lifecycle integration \\ Resource & Moderate to high resource demands & Computationally intensive & Challenging for constrained devices & Dominant specific, variable & Lightweight and scalable \\ Privacy Risk & General or minimal & Privacy-preserving ML techniques & Mainly access control techniques & Limited beyond compliance & Emphasis on privacy protection & Adaptive risk management and enforcement \\ \hline \hline \end{tabular}
\end{table}
Table 2: Comparative Analysis of Security and Privacy Approaches in IoTS Development.  
Real-world applicability through actionable guidelines tailored to diverse IoTS environments.