Skip to content
shani-la edited this page Jun 9, 2016 · 17 revisions
  • SDS - Software Design Specification This Document is a documentation and its main goal is to give us a little " peek " to our system,it will demonstrate us the functionality of our app,how the app answers on the costumer's requirements ,and how the app deals with the varies edge cases that were derived from the SRS Document,

Document Goals

Main Product Features

  • SERVER-at this of the project we are holding two options

    1. We will build a server that will hold and manage all DB request from user,
  • WEB-APP-we will build a web-app that will be based on AJ.

  • CREATING USERS

our charterers are:

  • tutor-the teacher/student that will give the private lesson .
  • pupil- the student that will have the private lesson.

###permissions--------

Main Product Features & Capabilities

* Main ability Description Risks
1 login-authentication the user will enter his username and password (given by the organization)and the system will recognize which type of user he is and by his username will navigate the user to system adjusted to him High
2 pupil -enter time The pupil will enter time&day he is available to have lessons Low
3 enter requested lesson the pupil will enter the lessons he needs reinforcement in low
4 tutor enter time the tutor will enter the time and day he is available to teach in High
5 tutor enter list lessons the tutor will enter the lessons he is interested to teach in . Low
6 show pupils constraints the coordinator will want to view the pupil's constraints in order to do set the schedule to the system Low
7 show pupils constraints the coordinator will want to view the tutor's constraints in order to do set the schedule to the system Med
8 set schedule the coordinator would be interested to set the schedule by the pupil and tutor's constraints Med
9 Database we will provide the user an ability to update&store data to the DB,moreover we will provide certain users access to specific information from the DB that is relevant for him Med

UML Diagrams

Deployment Diagrams

seqViewAll diagram

CRC Cards & Class Diagrams

seqViewAll diagram ###Class Diagram seqViewAll diagram

Behaviour :State Diagrams

seqViewAll diagram

Persistence

Non-functional Requirements

  • The login system-our system will recognize by the authentication system which user is which and will connect them to their fitted system.
  • Users action-the system will provide for each different user- different actions.
  • DataBase- the system will store/update the database for every action that deals with the DB.

Risk Management

Risk Management

Risk Severity Response
1 New Technology Medium Take an online Mean course Build Prototype
2 Inexperienced team Low Use the staff's help and google
3 User's verity of ages Medium Make the app friendly and compatible to all different users
4 Bad understanding in computers from costumer's side Medium Giving good explanation about the new system to the costumer

Initial Test Plan

  • login/logout.
  • An interface for each one of the different types of users using this app.
  • Provide user name and a password according to the user's type.
  • Prepare Approval system.
  • pupil enter hours.
  • pupil enter requested lessons.
  • tutor enter hours.
  • tutor enter reported hours.
  • coordinator views pupil's constraints.
  • coordinator views tutor's constraints.
  • coordinator sets the schedule .

Related Documentation