Home - ktagg/FinalProject GitHub Wiki

UML Class Diagram

---

---

UML Activity Diagrams

---

1. Gameplay Activity Diagram

2. Shop Activity Diagram

---

UML State Diagrams

---

1. Opening the game
2. Playing the game

---

UML Deployment/Component Diagram

---

---

Written explanation about how your architectural design addresses NFRs. Refer to illustrations whenever possible to clarify your arguments.

During conception of these nonfunctional requirements, what was most important to us was rapid functionality. This came to fruition in our requirements, by being strict on how quickly our game must respond. In our architecture this is accounted for my its simplicity. By having a simplistic game structure and functions, we allow the user a rapid response time, thus accommodating the functionality we sought out for.