Authors: <Carl Che>, <Severin Field>, <Alex Nguyen>
Our calendar will give you a daily rundown of what assignments are due, what classes you have, and any other events that you have at the beginning of each day. We will store information for each day using the singleton pattern to save configuration files. We will also handle recurring events with the visitor design pattern, which will visit each day and see if it is applicable for a given change and we will use this design pattern for modifying day objects. Lastly, we will use the abstract factory design pattern to handle types of events such as quizzes, homework due dates, class schedules, etc. We will incorporate it all into either a simple daily message delivered with http requests to a php backend system or if we have enough time an interactive web app with html and css. The back end of our program will be written in C++ and store yearly information in text files.
Create a class schedule Create events View of upcoming events View of class schedule reminder(email) Visualization of the calendar (either in console or HTML web app if enough time) Knows when there's a federal holiday coming up
As a user, I should be able to create a class schedule for a quarter. As a user, I should be able to create events such as quizzes and exams. As a user, I should be able to see a calendar of upcoming events As a user, I should be able to see my full class schedule for the quarter. As a user, I should receive a reminder / email when an event is coming up. As a user, i should be able to visually see the calendar As a user, I should be informed when a holiday is coming up
- It helps students manage their school schedule and quiz/exam times for students to be successful.
- Provides a simple way for students to enter their schedule of classes for a quarter and reads it back
- Provides better time management for students.
- We are in need of a calendar program or app that is customized for school work.
- C++
- We will use PHP, HTML, and CSS to make a simple web calendar GUI if we have enough time and have already completed a planner which incorporates all 3 of our design patterns.
- Input: Students’ schedule, daily specific tasks.
- Output: Text based configuration file.
-
Composite: We chose the composite pattern because it allows us to have a composition of similar objects inside of one object. These are going to be events inside of a day (inside of a the planner / plan class). The leafs are going to be quizzes, tests and custom events and the composite is going to be the plan. Lastly, the event class is going to be the component of the composite. This will make handling of various type of events easier and we don’t see any major drawbacks with this pattern.
-
Singleton: Singleton is a design pattern that fits perfectly with our needs of reading and writing to a configuration file for the needs of saving calendar items. The singleton instance can also be used as a global object. All of the operations that relate to adding/removing/modifying calendar items can be operated on this single object, as well as being saved to storage/write to file when needed.
-
Decorator: We chose this design pattern to allow the users to create custom events that can be differentiated by color to allow the user to see the importance of one event to another. It is giving the user the freedom to add events that are not specific to school work. One drawback is having too many events would clutter the calendar with bright visuals making it difficult to know what is prioritized.
This is our current class diagram. We use the singleton pattern in writing to and from files. We will have a text file when necessary for events like quizzes or custom events that need long descriptions. Our plan class is a composition of events such as quizzes or class that someone has, and here we use the composite pattern where event is the composite. Lastly, we use the decorator pattern to decorate custom events and give them attributes like the color (they will show as a different color in a GUI) or priority (how important or urgent is this event).
This screenshot shows the creation of a quiz object.
This screenshot shows the creation of a class and inputting its recurrence.
This screenshot shows the output and the loading of data to a file named winter2020
This screenshot demonstrates how the FileIO writes events to files, in this case, winter2020.txt
Usage is through CLI, we did not have time to write a script that emails you when an event is coming up, however, implementation would be simple given the code we've built. We planned on making a web GUI with HTML and CSS to show the calendar and write PHP on the website to send an email at the beginning of each week running printSchedule() on each event that takes place that week. We have not implemented that yet because we didn't have enough time and ran into segmentation faults and various other issues with our code.
We used Googletest and were each responsible for testing our own classes and methods.
