Skip to content

3.2. Non Functional Requirements

Jump to bottom
Silfer edited this page Apr 18, 2017 · 3 revisions

Non-Functional Requirements

Index. Description Priority
1. Engaging battle system High
2. Gamification to be intuitive, where users can pick up usage of the system easily High
3. Ease of creation of lobbies High

From the littlest team with big dreams, SOLOQ:

Joey Yeo
Weizheng Lee
Goh Yuan Tat

Navigate

  1. Introduction
  2. Getting Started
  3. Software Requirements
  4. Software Design
  5. Usability
  6. Performance, Robustness and Security
  7. Project Log
  8. Archive
Clone this wiki locally