-
Notifications
You must be signed in to change notification settings - Fork 3
SDS
Afek H edited this page Apr 14, 2016
·
32 revisions
#SDS - Software Design Specification
- Describe the system and the software components.
- Agreement and understanding of the software's implementation among all the team members.
- Efficient and unified programming of the software.
- Contribute for planning the software proccess on the best side.
Main Ability | Implementation |
---|---|
Web access product | Using Microsoft Azure cloud service |
Convenient viewing data | Using Angular JS, JavaScript and style utilities to display the contents to the users |
Identification of a crew members | Using Google Acounts service to identify the crew members and allow them access to the 'Management Panel' |
Creation content by crew members | Using templates of pages creator |
Creation of registration forms for events | Using templates of registration forms creator |
Export the data form the registration form | Saving the data from each registration form to the database. |
- UML Diagrams
- [User Manual] (https://github.com/afek590/Seniors-In-Touchnology/wiki/User-Manual)
- [Risk Management] (https://github.com/afek590/Seniors-In-Touchnology/wiki/Inception---Planning#risks-management)
- [SDS Review Summary] (link)
###Deployment Diagram
###Class Diagram
###Sequence Diagrams
###CRC Cards
##Persistence The following data will be saved in our database using MongoDB:
- All events and about it.
- For each event, all the users which registered the event.
- For each event, all the users which registered the event.
##Non-functional Requirements
- Performance - measured parameters about software performance like storage, response time, etc.
- Quality - testability, reliability, availability and usability.
- Convenient Use - The interface should be simple and convenient to use.
##Test Plan
- Panel Management Access Test
The test will examine if unauthorized google acount can access the crew's panel management.
We will create fictitious google acounts and try access with them to the panel.
- Loss Data Of Event Registration
The test will examine if the system can loose data of user who registered some event in the app.
We will create a test event and register to the event by serval different users which we will write first.
Then we will compare between the users we wrote and the users that added to the database.