summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGuntas Singh Grewal <guntasgrewal@gmail.com>2014-02-10 18:49:12 -0500
committerGuntas Singh Grewal <guntasgrewal@gmail.com>2014-02-10 18:49:12 -0500
commitd92546e6c8a21985d0e653e7910af210705dc8bc (patch)
tree94d4f2a7f1dbc3835390b66c4ade3aed42d2ee4c
parent4c396d22c286049034a90ec9b287fadc210ee926 (diff)
Update DesignDocument.md
Added Part 2
-rw-r--r--docs/DesignDocument.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/DesignDocument.md b/docs/DesignDocument.md
index 8401d27..335485f 100644
--- a/docs/DesignDocument.md
+++ b/docs/DesignDocument.md
@@ -26,7 +26,10 @@ sleek web application which manages tournaments.
# Non-Functional Requirements
-TODO Guntas. Email Dunsmore and Marco about this, then fill it out.
+1. Security: - Security of Leaguer Database is a non-functional requirement because Leaguer is system that stores the information of a user like statistics, user-name, profile, etc.; The System may not be responsible for the theft of user information or even alterations made to the database from a source different from that of Leaguer.
+2. Backup: - The Leaguer system provides a user with a database of user information and is updated and stored, which is functional. In contrast, the non-functional requirement of leaguer is its ability to back up all the information of the user when the user chooses to suspend or delete record or even when the user happens to disconnect from the server.
+3. Platform Compatibility: - A non-functional requirement for the system is to be able to run on multiple platforms. Primarily a web based application, Leaguer may not be able to install into embedded gaming devices and special operation systems that do not run the interface that Leaguer was initially built on.
+
# Design Outlines