1. One EPIC Place Website Scheduler
Nicholas Agneta
Fall 2018
Adviser - Professor Pham

2. Business Context and Goals
One EPIC Place is a coworking space rental service located in New Paltz, New York. The co-founders Julie Robbins and Nicole Langlois rent out space in several different buildings to provide offices for individuals, groups, and classes to work, often alongside each other. They also provide classes about business management among other things.
Business website: “oneepicplace.com” but use a service called “YaRooms” for the actual reservations and bookings of the rooms.
YaRooms has a point system and 5 minute increments which is useful
YaRooms does not have many of the customizable features that they want such guest booking or the ability to run reports

3. Technical Requirements
Environment: Software is a website connected to a database
Processing:
Registration
User information including: full name, , password, occupation
Login
Uses registration information from the database
Profile Page
Users will be able to customize their pages and see other members information
Scheduler
Form-based, User can select start and end times as well as the room

4. Front-end components Front-end development
Client-side of the code. How the user interacts with the scheduler and other functions on the website
The client is how the user can communicate requests to the server and database
HTML / CSS / JavaScript

5. Back-end components Server-side programming
Creating and manipulating the server-side code. PHP is the main language we are using for the server
The sessions allow us to collect data and store them temporarily without having to make several calls to the database
The server acts as an intermediary between the client-side interface and the back-end database that is storing all of the information

6. Database Structure
Currently, we have created the tables with all of the key information OEP has provided to us.
In the future the database will include many more keys and connections, as well as additional data points as needed.
Work will also be done to streamline the the tables, so information is not duplicated within our database.

7. MySQL Database

8. Database Entries

9. Design

10. https://cs.newpaltz.edu/p/f17-08/v29

11. Architecture

12. Register Protocol

13. Login Protocol

14. Scheduler Protocol

15. View Schedule Protocol

16. Problems we overcame
The clickable calendar made in JavaScript returns a date, but passing variables from JavaScript to PHP is difficult and will need to be implemented in the future
Team member dropped out half-way through
The scope of the project was too large for one semester’s work
Especially because it had to be restarted from previous semesters

17. Future Work to be done Email Verification
Clickable JavaScript calendar
Option for recurring events
Membership tiers
Payment method and Point system
“ redirect

18. Thank you for listening!
Questions or Comments?
Thank you for listening!