# A Study on Design Requirement Development and Satisfaction for Future Virtual World Systems
## 5 Discussion
### Architecture Comparison
\begin{table}
\begin{tabular}{c c c c c c c} \hline \hline
**Requirement** & **Feature** & **C/S** & **P2P** & **Hybrid-I** & **Hybrid-II** & **Virtual Net** \\ \hline \multirow{3}{*}{Sufficiency} & Lightweight Device Support & Code offload, Cloud gaming & No & \begin{tabular}{c} Code offload, \\ Cloud gaming \\ \end{tabular} & No & \begin{tabular}{c} Code offload \\ Cloud gaming \\ \end{tabular} \\ \hline \multirow{3}{*}{Reliability} & Connect Failure Tolerance & No & No & No & No & \begin{tabular}{c} Replicated \\ Connection \\ \end{tabular} \\ \cline{2-7}  & Replica consistency & Yes & \
\begin{tabular}{c} No \\ guarantee \\ \end{tabular} & Yes & No guarantee & Yes \\ \hline \multirow{3}{*}{Content persistency} & Content lost due to platform failure & Likely & Unlikely & Likely & Unlikely & Unlikely \\ \hline \multirow{3}{*}{Credibility} & Transparency to Compliance & No & Yes & No & Yes & Yes \\ \cline{2-7}  & Content Ownership & Separated & User-owned & Separated & User-owned & User-owned \\ \cline{2-7}  & Platform Owner’s & \multirow{2}{*}{Yes} & \multirow{2}{*}{No} & \multirow{2}{*}{Yes} & \multirow{2}{*}{No} & \multirow{2}{*}{No} \\  & Liability for illegal & & & & & \\ \cline{2-7}  & content & & & & & \\ \cline{2-7}  & DRM Violation & \multirow{2}{*}{No} & \multirow{2}{*}{Yes} & \multirow{2}{*}{No} & \multirow{2}{*}{Yes} & \multirow{2}{*}{Possible} \\ \cline{2-7}  & Traceability & & & & & \\ \hline \multirow{2}{*}{Scalability} & Scalability Cost to Application Provider & High & Low & Moderate & Moderate to low & Moderate to low \\ \hline \multirow{2}{*}{Cheating-prevention} & Client-side Code Tampering & Highly secure & Vulnerable & Highly secure & Vulnerable &
\begin{tabular}{c} Moderately \\ secure \\ \end{tabular} \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Features comparison of virtual world architectures. P2P storage techniques [125] ensure that the failure of a node will not spread over the entire system, and local failure can be recovered from data replicas. Data security can also be satisfied by decentralization. The security compliance of the centralized architectures is normally nontransparent to the external and is subjective to many firm-specific factors. Users only put limited trust in the protection of their data and information, even for cloud-based systems. An industry observation has shown that security and compliance are still significant challenges to cloud computing in 2019 [145]. The decentralized architectures, on the other hand, do not have a single stakeholder. Every user is the stakeholder of a system, and P2P-based security mechanisms can be applied effectively as long as most users are obedient to the system rules [146]. Thus, users need to trust no entity but only the system per se, which is also the argument why Blockchain-based solutions can achieve higher security in data access [94]. Thus, decentralized architectures can provide more trust in data security to users. Legal protection can be satisfied with unitary ownership. In the existing virtual worlds, which are centralized, control entities own all digital assets (i.e., file and data), while users own their virtual assets, leading to ownership inconsistency and disputation [96]. The decentralized architectures, on the other hand, do not have a control entity. Both virtual objects and digital assets belong to users. Thus, users' virtual property can be legally protected by property or copyright law. Moreover, application providers do not need to worry about their liability for, e.g., plagiarism or offensive content, since they do not own them. Thus, decentralized architectures can offer higher legal protection to both users and application providers. Table 2 also shows the architectural comparison for existing requirements, including scalability and security. Scalability cost refers to the economic cost imposed on someone or some entity, who provides the virtual world application, for scaling up the system to accommodate the growth of the user population.