Math Tutoring System MTS:

1
Math Tutoring System (MTS) An
Online Scheduling System
Fall 05 Progress Presentation
November 16th, 2005
Project Clients Alison Green Cynthia Jahn
OATS Team Members Sunny Yue Hui Zhou Ritesh Sood
Advisor Jun Suzuki
2
Terms

• OATS Online Application for Tutor
• Scheduling
• MTS Math Tutoring System (math tutoring
  program)
• OTS Online Tutoring System (subject tutoring
  program)

3
Clients

• Cynthia Jahn(Director)
• Academic Support Programs
• phone [phone]cynthia.jahn_at_umb.edu
•  
• Alison Green
• (Director of Mathematics)
• Math Resource Centerphone 617-287-6658alison.g
  reen_at_umb.edu

Academic Support Programs (OTS) Academic Support
Programs is to offer comprehensive coursework and
services to both native and non-native speakers
of English with the goal of helping students to
succeed in their studies. Math Resource Center
(MTS) Math Resource Center focuses on
Mathematics and computer science tutoring.
4
Project VisionPlatformProject Timeline
Client Meeting
5
Project Vision and Objectives
Vision The MTS System will provide math and
computer science students who are currently
registered as part-/full-time 24/7 access to
schedule tutoring help session offered here at
UMass Boston. The integration of OTS and MTS
will provide a single access point where
students can utilize all tutoring programs
offered by Academic Support Programs.

• Objectives
• Identify and correct all the major bugs present
  in the current version of MTS.
• Ensure that the current MTS system and database
  is operational on a UNIX server.
• Implement additional administrative functions and
  reporting features.
• Incorporate MTS (Math Tutoring System) and OTS
  (Online Tutoring System, subject tutoring) with a
  Universal Login.

6
Software Requirements

• The following applications are required
• Apache Ant 1.6.5
• Apache Tomcat 5.5 Servlet/JSP Container
• MySQL 4.0
• MySQL Connector/J 3.1.10

7
Version Control System

• CVS Server Tigris
• www.tigris.org
• Module name is 'umb-oats
• Developer Eclipse Simple interface

8
Project Timeline
9
OATS Task List
10
Client Meetings

• 1st meeting
• Introduction of the team members, overview of
  MTS/OTS. Demo.
• 2nd meeting
• Data/ requirement gathering. Discussion on the
  known bugs as well as the approach on fixing
  these bugs.
• 3rd meeting
• OATS team gave a short demo to the client on
  some of the fixed bugs. Customers agree on
  current project timeline and tasks.
• 4th meeting (upcoming on Nov 21st,2005)
• Requirement gathering on future implementation.
  Discussion/ clarification on some of the new /
  existing features.
• For detailed information on each of the meetings,
  please visit our project website.

11
System Overview
12
Architecture-Overview
13
System Architecture
14
Database Overview

• The MTS involves 3 main databases inside MySQL
  Server

green
tomcatusers
acad
15
Database Overview (cont.)
tomcatusers acad green

• Username / Password / Role
• Authenication

• Student enrollment database (import from
  Registrar)

• All related MTS/OTS information

16
More Database Overview

• User Login Tomcat lt-gt MySQL
• Authentication via j-security-check
• configure in file server.xml

• DDD (Database Design Documentation)
• For the completed design of the databases used
  in MTS, please refer to our project website.

17
Use Case Diagrams

• In our project we have the following actors
• 1. Tutor
• 2. Student
• 3. Staff
• 4. Admin
• 5. System
• The diagrams below show the following
  actors and their respective use cases.

18
Use Case for Student
19
Use Case for Tutor
20
Use Case for Staff
21
Use Case for Administrator
22
Use Case Diagrams

• Use case diagrams is extremely important to
  discover the bugs existing in the current system!
• Test Cases Use Cases
• For more details, please visit our website for a
  detail documentation.

23
Bugs
24
Bugs Fixed Update week

• Symptom User cannot see the current date
• Cause math_week table not updated correctly.
• Solution create a method that is called whenever
  user enters the system to update the date.

25
Bugs Fixed View appointments

• Symptom Users cannot see scheduled appointments
• Cause Use of subqueries that are not supported
  in MySQL 4.0
• Solution Rewrite subqueries
• sql "Select from t1.tlogin, t1.slotid FROM
  Math_tutor_schedule t1, math_tutor_profile t2
  where t1.tlogint2.tlogin and t1.tlogin IN
  (Select tlogin from math_tutor_courses where
  courseidcourseid ) and t1.tlogin!'username
  order by t1.slotid"
• ?
• sql "SELECT t1.tlogin, t2.slotid FROM
  math_tutor_courses t1, math_tutor_schedule t2
  WHERE t1.tlogint2.tlogin AND t1.courseid'coursei
  d AND t1.tlogin!'username ORDER BY t2.slotid"

26
Bugs Fixed others

• Symptom Student cannot add courses
• Cause Query not written correctly (a unwated
  field appeared in query)
• Symptom Tutor cannot view course schedule
• Cause Subquery used
• Symptom Tutor change/delete schedule behaves
  boldly.
• Cause Query not written correctly at all

27
New Features
28
New Features

• Enable tutors to call in sick and request days
  off. Also reschedule students if an another tutor
  is available.
• Assigning staff read/write privileges to tutor
  and student profiles, calendars and schedule.
• Enhancing certain functions to make MTS more user
  friendly.
• For e.g. Improving the display of names in the
  drop down menu box
• -Enhancing the holiday feature in
  the current system
• Implementing student feedback and comments
  section.

29
New Features (2)

• Generating new reports
• e.g. Summary of bookings and empty slots for
  tutors and courses.
• -Daily tutor schedule and bookings
• -Adding instructor field in student
  reports
• Develop a workshop component that will provide
  students with an option to sign up for group
  workshop sessions.
• Reset and archive database
• Finally, integrate MTS with OTS

30
Conclusion
31
Goals

• Short term goals
• Fixing all the bugs present in the previous
  version MTS System.
• Refactoring the existing code.
• Deploying working MTS on a UNIX platform.
• Fixing the current GUI of MTS
• Long term goals
• Adding new features
• Incorporating OTS and MTS together having a
  common login Dialog Box

32
Past, Present and Future

• What we have done
• Fixing some major bugs. (75-85 completed)
• What we are doing
• Minor Bugs, refactoring
• What we will do next within 2 months
• GUI, deployment, estimation time (man power
  needed) on new features

33
Project Timeline Revisit
34
Finally

• On time! (Beginning of Spring 2006)
• Flexible on our future deadline

35
Questions ?

• For
• feedback/comments/suggestions
• Email
• UMB_OATS_at_googlegroups.com
• Project Website
• http//www.cs.umb.edu/ritsood/oats/oats.htm