Skip to content

System Requirements

Jump to bottom
Alex Gruenwald edited this page Oct 7, 2019 · 18 revisions

Requirements

Here are the 15 most important requirements. Detailed descriptions of the 5 most important can be found in their own wiki pages.

Cash Assumption: All payments will be done on the day of the session and be paid in cash.
Big Room Booking Assumptions: Requires direct conversion with company managers to book the larger rooms.
Adding Courses: For students to add courses to the tutoring company, must contact the company directly.
User Assumption: The word user refers to both student and tutor.
Assumptions: The system will attempt to display all visual information within 2 seconds after being triggered. Tutor information will consist of tutor's personal information (name, education level, etc.) as well as the reviews written about the tutor.

  1. The tutoring system shall allow users to register for an account by providing login credentials. (functional)
  2. The tutoring system shall allow the user to securely login when the appropriate username and password is provided for the user within 5 seconds. (functional)
  3. Upon student request, the tutoring system shall list available courses for the selected school within 2 seconds. (functional)
  4. Upon student request, the tutoring system shall list the tutor information for the selected course within 2 seconds. (functional)
  5. The tutoring system shall allow users to book a session between 1 day to 2 weeks in advance. (non-functional)
  6. The tutoring system shall allow the student to cancel their session up to 24 hours before their scheduled room booking. (non-functional)
  7. The tutoring system shall allow students to book a session scheduled between 9am and 9pm. (non-functional)
  8. The tutoring system shall check for room availability after initial session creation by the student within 5 seconds. (functional)
  9. The tutoring system shall notify the tutor selected by the student within 1 minute of the request being made. (functional)
  10. Upon tutor's reply to the session request, the tutoring system shall notify the requesting student of the response within 1 minute. (functional)
  11. Upon confirmation from the tutor, the tutoring system shall randomly assign a room to be used for the session within 1 minute. (functional)
  12. The tutoring system shall cancel a session confirmed by a tutor if there are no rooms available. (functional)
  13. The tutoring system shall have users review the session within 48 hours, by issuing a prompt, 1 hour after the end of the scheduled session. (functional)
  14. The tutoring system shall keep review writing authors anonymous for viewers. (functional)
  15. The tutoring system shall allow users to securely log out of their accounts within 5 seconds. (functional)


Edit Trail
Edited By RequirementsEdited Concerns Questions
Apg04.10.19
  1. reworded 6
  2. reworded 13
 No concerns
  1. Should users be verified before system shows them tutor or student information?
  2. Should there be a limit of how many reviews are shown at any give time - 10?
Cmc04.10.19
  1. 5 merged into 4
  2. 3, 4, 7 - adj. removed
  3. 8 - new req
 No Concerns
  1. No current questions
Tlc04.10.19
  1. 13 changed to accomodate 48 hour deadline
 No Concerns
  1. No current questions

Meeting Minutes
24/09/2019
27/09/2019
3/10/2019
8/10/2019
19/10/2019
24/10/2019
26/10/2019
07/11/2019
14/11/2019
19/11/2019
21/11/2019
26/11/2019

Project Assumptions

Sprint 1
Requirements
Use Case Diagram
UML Diagram
Detailed Specifications

Sprint 2
SQA Plan
SQA Report
Endpoints
Queries & Integration
RESTful API Tests

Sprint 3
System Architecture
UI Mockup

Sprint 4
Web Documentation
Android Documentation

Clone this wiki locally