An android calendar app designed for students!

Library:

• Android Week View library by alamkanak (Under Apache License)

myCalendar is an Android calendar app used for students to keep track of classes and events.

• Creating new Event: Static Event (can be periodic) - As a student, I want the app to statically schedule my events/activites so that I know when the events will be occur each week.

• Creating new Event: Dynamic Event (Non periodic, can locate a time for itself) - As a student, I want the app to dynamically schedule my events/activities so that the events can change to fit my needs

• Add finished event to finished List - As a student, I want the app to be keep a list of finished events so that I can look back on my finished list events to see what I have finished or so that I can reference what I have doe before.

• Show month view of calendar (Main View) - As a student, I want the app to show a month view so that I can see upcoming events in the month.

• Allow scroll to future and past month view of calendar (Main View) - As a student, I want the app to be able to swipe left and right to future and past months so that I am able to plan for upcoming events in future montsh or look back and referenece past events in past months.

• Opening existing event - As a student, I want the app to be able to open an existing event so that I can edit the details of the event.

• Updating existing event - As a student, I want the app to be able to update an existing event so that I can change the details of the event should they chagne.

• Deleting Event - As a student, I want the app to be able to delete an event so that I can edit my upcoming schedules in case I can no longer do/attend that event or no longer need/want to do/attend that event.

• All fields on page (e.g. text box, radio options, dropdown lists) should be aligned properly
• Numeric values should be right justified unless specified otherwise
• Enough space should be provided between field labels, columns, rows, error messages etc.
• All buttons on page should be able to perform correctly
• Each calendar view should be Scrollable
• Both date and time should be Scrollable
• Main calendar should have all events listed
• Event detail should be accessible when clicking on it
• Adding static event and having it allocated on the main calendar correctly
• Add in dynamic event, having it fill in the free time zone only before deadline
• Dynamic events should not overlapped with the static events
• Events should turn grey when user archived them
• Existing events are available for editing.
• Existing events are available for deleting
• we have the user login system existing calendar can be upload to cloud.
• Android client side can send HTTP POST request to the server for user information.
• Users can able to register or login. After login, data is automatically backed up in cloud, and user can download data from cloud by clicking "sync from cloud".

For our app, the functionality needs continuous testing and improvement. That's why we feel human testing is appropriate. There are many cases that we need to consider, and many different times we need to test for our algorithm.

Test Machine Name: Siyu Yang

Test Report, GUI Test:

• Delete both events at same time: only deletes first one

• Events should not be added in invalid time

• Archive usage for users (delete)

• allocate dynamic events according to the due date

• extra dynamic events after being edited

• add dynamic event even if it is conflicted with the static ones

• static events to be locked down in one day

• [Dynamic] tag shows twice after editing

• Not able to edit events after deleting all those events

• Need to remove static other day choices

• < 9am error no display >9am display

• If event has already happened, do not push to later on

• If cur > dynamic start, move on to next dynamic

• fix null password

• new feature: after hours if need to finish before deadline, else finish the next day

Week 1 & Week 2

• Learning and writing user stories (everyone)

Week 3

• Learning and Writing user stories (everyone)
• Prototyping UI (everyone)
• Look for libraries that can help us out with calendar view

Week 4- 5

• Integrated with Material View Calendar View Library
• Finished prototyping UI (everyone)
• Iterate over user stories to eliminate assumption (everyone)
• Working the ability to show month view of calendar, which is the main view (Kristine, Fang, Alex, William)
• Prototyping event self allocation algorithm (Scarlet, Steve)
• Prototyping Database (Zhiwei)
• Testing the main view.

Week 6

• Iterate over user stories to eliminate assumption (everyone)
• Finished working the ability to show month view of calendar and testing the main view (Kristine, Fang, Alex, William)
• Keep working on Database (Zhiwei) *Creating new Event: Static Event (can be periodic)
• Creating new Event: Dynamic Event (Nonperiodic, can locate a time for itself)
• Updating in database. (Kristine, Fang, Alex, William, Zhiwei)
• Prototyping and testing event self-allocation algorithm. (Scarlet, Steve)

Week 7

• Keep working on as well as testing Creating new event mechanism. (Kristine, Fang, Alex, William, Zhiwei)
• Integrate show month view with create new event view and create smooth transitions in between. (Kristine, Fang, Alex, William)
• add datepicker function
• Finishing event self-allocation algorithm. (Scarlet, Steve)
• Deleting event and updating deleted events in database. (Zhiwei)
• Updating UI using Material Design. (Kristine, Fang, Alex, William)

Week 8

• add finished event to finished List (Kristine, Fang, Alex, William, Zhiwei)
• renamed folder and added finished for events list fragment
• changed calendar class and improved naming and functionality
• Testing on basic features such as adding and deleting events. (everyone)
• added color field
• merge conflict

Week 9

• Add notification(Dropped)
• merge the Dynamic event algorithm with the front end
• merge the self allocation algorithm with the front end
• merge the event delete algorithm with the front end
• added freetimesort
• Testing on basic features
• back end algorithm update
• add Priorityqueue
• edit event handler
• fixed date picker and time picker in add event activity
• fix date formatting error
• merge conflict
• set event active after archiving it
• Finish product

Week 10

• Completed new login system and online database.
• Databackup in cloud and server system from scratch is completed.
• User data are automatically uploaded to the cloud and users are able to download data form cloud via sync button in the navigation drawer
• Final testing and maintenance.
• User scenario testing.
• Tested extreme scenarios.
• Finished GUI, Controller and Model unit testing.
• Product passed exhaustive testing.
• Updated README for final presentation

Week 11

• Presentation

Post-Final Works

• Added notification system.
• Modified login system for showing current user.