-
Notifications
You must be signed in to change notification settings - Fork 0
3.2. Non Functional Requirements
Silfer edited this page Apr 18, 2017
·
3 revisions
| Index. | Description | Priority |
|---|---|---|
| 1. | Engaging battle system | High |
| 2. | Responsive whiteboard | High |
| 3. | Gamification to be intuitive, where users can pick up usage of the system easily | High |
| 4. | Ease of creation of lobbies | High |
From the littlest team with big dreams, SOLOQ:
Joey Yeo
Weizheng Lee
Goh Yuan Tat
- Introduction
- Getting Started
- Software Requirements
- 3.1. Functional Requirements
- 3.2. Non-Functional Requirements
- 3.3. Abuser Stories
- Software Design
- 4.1. User Interface
- 4.2. Software Architecture
- 4.3. Database Design
- Usability
- Performance, Robustness and Security
- Project Log
- Archive