Use Case 11

Sequence diagram:

Test Cases

2. User clicks on a time slot, if user is not logged in prompt for login. If a user is logged in and when user clicks for a signup, it will test for specific cases mentioned below. If fields are ok, it updates GUI and the schedule file. Specific Cases:
a) If a user enters invalid time, we get an invalid time error.
b) If a user enters too long a time , we get a time too long error.
c) If a user has reached a signup limit, we get too many signups error.
d) If a user enters an invalid date, we get an invalid date error.
e) If a user enters an invalid email, we get an invalid email address error.

Classes, methods and variables:

Schedule
Methods:
+makeAppointment()
+makeAppointment(date, starttime, endtime)

Login
Methods:
+getUserInfo()
+verify(username, password)
Variables:
loggedin
username
profile

Week
Methods:
+makeAppointment(start, end, profile)
-checkAvailable(start, end)
Variables:
start
end
date

Appointment
Constructors:
-Appointment(start, end, profile)

File
Methods:
updateSchedule()

GUI
Methods:
update(message)
promptForLogin()
refresh()