UML Deployment Component diagram - MadeWithPaper/Simternship GitHub Wiki

---

Software Architecture

---

---

Component diagram

---

---

Deployment diagram

---

---

Written Explanation:

---

Addressing NFR (B, D,E) Reliability (in terms of availability, fault tolerance, or recoverability)

• Since we are using a cloud, we are addressing reliability because it will be available to all users. Our program is running on the web, so as long as the user is connected to the internet on the user’s device, the program will run properly. Our architecture allows for quick recoverability because the data base is a cloud instead of a physical database.

Security in terms of non-repudiation, authenticity or accountability

• Users should be able access to their profiles once they are logged in with passwords.Once they sign out, they will not able to view their information until log in again. (warn users not to save password on public computer). Data of the game is stored in the cloud which is protected.

Portability (in terms of adaptability)

• Since our program is based on the cloud, it does not rely on hardware.Therefore, hardware will not hinder our program as it does for other programs. This is a large factor in its adaptability since adaptability relies on changing hardware and software. Our program is relying on our software and the cloud’s environment. It will be completely portable given the software’s capabilities. Our program has the ability to support different web browsers, such as Chrome, Safari and Firefox.