ebel Innovations

Project: Super Scheduler

Team Members:

Raymond Braselman Collin Durrett

Sammy Qasem Emily Weaner Brien Weydert

ISDS 3100 Spring 2013 March 12, 2013

Table of Contents

Executive Summary ................................ 1 System Glossaries ................................... 2

Actor Glossary ................................... 2 Use Case Glossary .............................. 3

Use Case Diagram ................................... 4 Use Case Narratives ................................ 5

Maintain Tasks .................................. 5 Browse Tasks ..................................... 7 Send Pop-up Notification .................. 8 Update Calendars .............................. 9

System Forms ....................................... 10 Detailed Activities ................................. 13 Appendix ............................................... 14

Functional Requirements ................ 14

1

Executive Summary Rebel Innovations desires to create an application that would effectively aid an LSU

student in time management. We envision students having the ability to prioritize their schedules in order to become more efficient. Our answer for this is Super Scheduler. Super Scheduler would be available 24 hours a day, 365 days a year, and would update schedules from Moodle and Google Calendars daily. This would significantly help the student keep track of everything they have to do throughout the day.

The target audience for the Super Scheduler application is LSU students. We are exclusively looking for students that find difficulty in prioritizing their activities for the day. The students who would most likely find this application useful are those who have many different obligations with extracurricular activities, a challenging course load, a busy work schedule, and a drive to succeed. Our application will be available on the iOS platform. This application will be very intuitive and easy to use, especially for your typical LSU student.

An average LSU student will have no problem telling you that their schedule is full, and

that they have very little time between work, class, being part of organizations, and of course

having a few hours to go out to Tigerland. Many students become stressed when they have a

week with multiple exams and other responsibilities, and Super Scheduler would enable them

to conquer their anxiety. When the user opens the application for the first time, they will be

asked to log in to their Google Calendar and Moodle accounts. Syncing will happen almost

instantaneously and the student would not have a great deal of information to enter into the

application. Once the information syncs, the student will be brought to the Calendar screen.

Here, they will be able to browse all of their events for that month. The user also has the

option to see their daily and weekly schedule on the Calendar screen and can use the tabs

beneath the Calendar to do this. The user may also modify or delete any event listed on the

Calendar screen. At the top of the screen, the user will also find an Events tab that allows the

user to manually add an event to their Calendar. The Events tab is where the user will be able

to set their preference to receive a pop-up notification for each event.

Rebel Innovations wishes to empower LSU students with the ability to navigate their

busy schedules. Our unique algorithm will prioritize a user’s schedule and allow them to go

through their agenda with ease. The pop-up notification feature will remind users of the things

that would have slipped their mind. Super Scheduler will make managing a busy college

schedule seem like a walk in the park.

2

System Glossaries Actor Glossary

Term Synonym Description

User A person who has downloaded and installed the application on their smart phone.

Moodle Calendar A calendar that the user has to track events relative to LSU classes.

Google Calendar An optional calendar that a user has to keep track of their personal schedule.

Time An actor concept used for triggering temporal events.

3

Use Case Glossary

Use-Case Name Use Case Description Participating Actors and Roles

Maintain Tasks This use case describes the event of a user adding, modifying, or deleting events from the calendar. Upon completion of this use case the system will perform the algorithm.

User

Browse Tasks This use case describes the event of a User viewing items already on the calendar in three different views.

User

Send Pop-up Notification

This use case describes the event of a stored task scheduled for a specific time sending an alert to the User.

Time

User

Update Calendars This use case describes the event of an automatic sync with Moodle and Google Calendars. The sync will be performed daily at 2:00 am local time.

Time(initiating actor)

Google Calendar

Moodle Calendar

4

Use Case Diagram

5

Use Case Narratives

Super Scheduler

Author (s): Collin Durrett Date: 3/09/2013

USE CASE NAME: Maintain Tasks

PRIMARY BUSINESS ACTOR:

User

OTHER PARTICIPATING ACTORS:

DESCRIPTION: This use case describes the event of a user adding, modifying, or deleting events from the calendar. Upon completion of this use case the system will perform the algorithm.

PRE-CONDITION: The application is open and accounts must have been previously accessed by the User.

TRIGGER: This use case is initiated when the User selects or creates an event.

TYPICAL COURSE Actor Action System Response

OF EVENTS:

Step 1: The User clicks the Events tab.

Step 2: The system responds by displaying the Events Form.

Step 3: The User clicks the “plus sign” button to add a new event.

Step 4: The User enters desired information for Event Title, Time, Date, and Priority.

Step 5: The User clicks the submit button.

Step 6: The system responds by performing the algorithm comparing the priorities of all events listed on the same day as the new event.

Step 7: The system displays the calendar tab.

ALTERNATE COURSES: Alt-Step 1: The User double clicks on an event underneath the calendar. Alt-Step 2: The system responds by displaying the Events Form with previously saved information. Alt-Step 3: The User enters desired changes for Event Title, Time, Date, and Priority. Alt-Step 4: The User clicks the submit button. Alt-Step 5: The system responds by performing the algorithm comparing the priorities of all events listed on the same day as the new event. Alt-Step 6: The system displays the calendar tab.

Alt-Step 1: The User clicks on an event underneath the calendar. Alt-Step 2: The User slides their finger to the right on top of the selected event. Alt-Step 3: The system displays a delete button on the right side of the selected event. Alt-Step 4: The User clicks on the delete button. Alt-Step 5: The system removes the selected event.

6

CONCLUSION: This use case concludes when the system displays the updated calendar tab.

POST-CONDITION: The system saves all information.

BUSINESS RULES

IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS

User must have enough memory on phone to save information.

ASSUMPTIONS:

OPEN ISSUES: If a User’s memory is at full capacity, there is not an additional location to store.

CORRESPONDING FORMS AND REPORTS:

Events Form Calendar Form

7

Super Scheduler

Author (s): Collin Durrett Date: 3/09/2013

USE CASE NAME: Browse Tasks

PRIMARY BUSINESS ACTOR:

User

OTHER PARTICIPATING ACTORS:

DESCRIPTION: This use case describes the event of a User viewing items already on the calendar in three different views.

PRE-CONDITION: Events must have been previously added by the User or synced from outside calendars.

TRIGGER: This use case is initiated when the User opens the application.

TYPICAL COURSE Actor Action System Response

OF EVENTS:

Step 1: The User opens the application.

Step 2: The system responds displaying the Calendar Form with the Daily tab selected.

Step 3: The User scrolls through the listed tasks.

ALTERNATE COURSES: Alt-Step 3: The User clicks the Weekly tab. Alt-Step 4: The system displays the Calendar form with the Weekly tab selected. Alt-Step 5: The User scrolls through the listed tasks.

Alt-Step 3: The User clicks the Monthly tab. Alt-Step 4: The system displays the Calendar form with the Monthly tab selected. Alt-Step 5: The User scrolls through the listed tasks.

CONCLUSION: This use case concludes when the User closes the application.

POST-CONDITION:

BUSINESS RULES

IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS

ASSUMPTIONS:

OPEN ISSUES:

CORRESPONDING FORMS AND REPORTS:

Calendar Form

8

Super Scheduler

Author (s): Brien Weydert Date: 3/09/2013

USE CASE NAME: Send Pop-up Notification

PRIMARY BUSINESS ACTOR:

Time

OTHER PARTICIPATING ACTORS:

User

DESCRIPTION: This use case describes the event of a stored task scheduled for a specific time sending an alert to the User.

PRE-CONDITION: The User must have previously set the task to send a pop-up notification.

TRIGGER: This use case is initiated when a scheduled task with pop-up enabled occurs.

TYPICAL COURSE Actor Action System Response

OF EVENTS:

Step 1: The internal clock (Time) of the system strikes an hour before the time a task is scheduled.

Step 2: The system responds by verifying the tasks scheduled time.

Step 3: The system sends a notification to the User.

ALTERNATE COURSES:

CONCLUSION: This use case concludes when the system sends a notification to the User.

POST-CONDITION: The User acknowledges the notification

BUSINESS RULES

IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS

ASSUMPTIONS: The User’s phone is turned on and has a charged battery.

OPEN ISSUES:

CORRESPONDING FORMS AND REPORTS:

9

Super Scheduler

Author (s): Collin Durrett Date: 3/09/2013

USE CASE NAME: Update Calendars

PRIMARY BUSINESS ACTOR:

Time

OTHER PARTICIPATING ACTORS:

Google Calendar Moodle Calendar

DESCRIPTION: This use case describes the event of an automatic sync with Moodle and Google Calendars. The sync will be performed daily at 2:00 am local time.

PRE-CONDITION: Accounts must have been previously accessed by User.

TRIGGER: This use case is initiated when a set time is reached.

TYPICAL COURSE Actor Action System Response

OF EVENTS:

Step 1: The internal clock (Time) of the system strikes 2:00 am local time.

Step 2: The system responds by connecting to the User’s Google and Moodle accounts.

Step 3: The system checks for any changes to existing events that were synced, and any new events.

Step 4: The system downloads the information.

Step 5: The system verifies the downloaded information and performs the algorithm.

Step 6: The system closes the connection to the external accounts.

ALTERNATE COURSES: Alt-Step 4: The system closes the connection to the external accounts.

Alt-Step 3: If the system is unable to connect to the account the first time it will try three additional times with thirty minute increments. Alt-Step 4: The system does not connect to an account and does not make any updates.

CONCLUSION: This use case concludes when the system closes the connection to the external accounts

POST-CONDITION: The system saves all information.

BUSINESS RULES

IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS

The User must have a stable internet connection either through Wi-Fi or their cell phone carrier.

ASSUMPTIONS: The User’s phone is turned on and has an internet connection. The User has not deleted any of the external accounts.

OPEN ISSUES: If external accounts servers are down, we are unable to perform updates.

CORRESPONDING FORMS AND REPORTS:

10

System Forms Maintain Tasks

Add:

Modify:

11

Delete:

Browse Tasks

12

Send Pop-up Notification

Update Calendars

13

Detailed Activities

Milestone 2

Team Member Name Role

Raymond Braselman Member

Collin Durrett Member

Sammy Qasem Member

Brien Weydert Leader

Emily Weaner Member

Milestone Activity Team Member

Executive Summary Raymond Braselman Collin Durrett Sammy Qasem Emily Weaner Brien Weydert

Actor Glossary Brien Weydert

Use Case Glossary Brien Weydert

Use Case Diagram Emily Weaner

Use Case Narratives Collin Durrett Brien Weydert

System Forms Sammy Qasem

Detailed Activities Emily Weaner

Functional Requirements Raymond Braselman

Table of Contents Brien Weydert

Milestone 3

Team Member Name Role

Raymond Braselman Member

Collin Durrett Leader

Sammy Qasem Member

Brien Weydert Member

Emily Weaner Member

14

Functional and Non-functional Requirements

Functional Requirements: 1. Maintain Tasks: 1.1 The system will allow users to manually add their personal activities (like class, meetings, exercise, etc.) by utilizing the Events tab. Users will be asked to enter the event title, time, date, and respective priority. 1.2 The system will require users to prioritize the activities that they submit to the application on a scale of importance that ranges from High Priority to a Low Priority. A red dot will symbolize a High Priority event, a yellow dot will symbolize a Medium Priority event, and a green dot will symbolize a Low Priority event. All events that sync from a user’s Moodle Calendar will automatically be set as a High Priority. All events that sync from a user’s Google Calendar will require the user to manually modify the priority by clicking on the event in the Calendar tab. If the user does not specify a priority level for an event either synced from Google Calendar or manually entered, the system will automatically prioritize the event as a Low Priority event. 1.3 The system will perform an algorithm that formulates a personal schedule for each user. The algorithm will consider time and priority when formulating a schedule. The system will perform this algorithm when the user presses submit on the Events tab when adding a new event, or when an existing event is modified. 1.4 The system will allow users to modify tasks by double clicking on an event in the Calendar tab. The event is then displayed in the Events tab allowing the user to edit the information as desired. 1.5 The system will allow users to delete tasks by clicking on an event in the Calendar tab. The user then will use the iPhone’s built in swipe function over the event. The system will then display a delete button for the user to click. 2. Browse Tasks: 2.1 The system will allow users to browse tasks needed to be completed by using either a daily, weekly, or monthly tab viewable within the Calendar Tab. 3. Send Pop-up Notification: 3.1 The system will allow users to decide whether or not they would like to receive a Pop-up notification for each event entered and synced into the system. This is handled by a toggle switch located on the Events screen. By default this function is set to off.

15

3.2 The system will send the user a Pop-up Notification an hour before each event stating the event will begin in an hour. 4. Update Calendars: 4.1 The system will automatically update and sync information from the user’s Moodle Calendar and Google Calendar at 2:00 A.M. local time as long as the user has entered their login information on the Login screen. The Login screen appears when the user opens the application for the first time. Nonfunctional Requirements: 1. Security: 1.1 A user’s personal information will be kept private and secure through data encryption. The

system will not have the ability to export information to any third party applications or websites.

2. Performance: 2.1 The application will be available 24 hours a day and 365 days per year. 2.2 The system will be able to sync with Moodle and Google calendars in under a minute once the user enters his or her login information. 3. Operational: 3.1 The system will operate on an iOS platform. 4. Cultural and Political: 4.1 The application will conform to all privacy laws and must obtain permission from Google to utilize information from the Google Calendar application.