Updated SDS (markdown)

Sagi Dayan 2015-04-29 17:18:32 +03:00
parent 8d4a5fe908
commit 8611abaea0

32
SDS.md

@ -22,22 +22,34 @@
|Notifications/Alerts|Medium| We wish to have an option to notify the students about upcoming submition dates and/or messages from student/lecturer.| |Notifications/Alerts|Medium| We wish to have an option to notify the students about upcoming submition dates and/or messages from student/lecturer.|
|Simple UI|Medium-Low| The UI should be as simple as can be, yet contain all features. It's very important to make the Dashboard a "clean" working enviorment with no distractions| |Simple UI|Medium-Low| The UI should be as simple as can be, yet contain all features. It's very important to make the Dashboard a "clean" working enviorment with no distractions|
4.**Sequence Diagram** 2. **Deployment Diagram**
[Deployment Diagram Page](https://github.com/sagidayan/SE-Hub/wiki/Deployment-Diagram)
3. **Class diagram & CRC cards**
[Class diagram & CRC cards - Wiki Page](https://github.com/sagidayan/SE-Hub/wiki/Class-diagram-&-CRC-Cards)
4. **Sequence Diagram**
**Send Class message** **Send Class message**
![Sequence Diagram](http://i61.tinypic.com/rqy9a1.png)
1. The lecturer must login with valid account.
2. Once in lecturer dashboard, press messaging system button.
3. Choose message type - private/group/class. (in this case Class)
4. Input message.
5. Check optional fields (Notify all/on-response).
6. Send or cancel message.
7. Returns to messaging system window.
![Sequence Diagram](http://i61.tinypic.com/rqy9a1.png) 5. **Persistence**
1. The lecturer must login with valid account. [Persistence Page](https://github.com/sagidayan/SE-Hub/wiki/Persistence)
2. Once in lecturer dashboard, press messaging system button.
3. Choose message type - private/group/class. (in this case Class)
4. Input message.
5. Check optional fields (Notify all/on-response).
6. Send or cancel message.
7. Returns to messaging system window.
6. **Non-Functional Demands**
6.**Non-Functional Demands**
* **a. Simple to use-** UI would be simple and "clean" so that usage will be as easy as possible. * **a. Simple to use-** UI would be simple and "clean" so that usage will be as easy as possible.
* **b. Secure-** Login via Github will suffice a secure connection to an already existing profile. * **b. Secure-** Login via Github will suffice a secure connection to an already existing profile.
* **c. Generic Structure-** Dashboard is designed in a way that it can be used for different Courses/Colleges * **c. Generic Structure-** Dashboard is designed in a way that it can be used for different Courses/Colleges