Sprint 0
Here is the current (deployed) version of the Storefront Calendar website.
Regular meetings will be held in BA 3200 every Monday and Wednesday at 4 pm -- 5:30 pm.
Meeting minutes will be posted on their own page.
Due Date: Mon Nov 18 Demo Date: Sat Nov 30
Facebook group: https://www.facebook.com/groups/646276602073948/
For day-to-day group communication.
Gmail account: nettilling@gmail.com
To be used to communicate with the Product Champion and collaboratively edit documents.
GitHub repository: https://github.com/CSC301H-Fall2013/Storefront-Calendar
GitHub webpage: http://csc301h-fall2013.github.io/Storefront-Calendar
Every team member is obligated to attend group meetings whenever possible, and be on time for them.
Team members must keep in contact with the group by checking all group forums on a regular basis. The Facebook group should be monitored (we all have smartphones), and members should contribute if they can help with an issue. The GMail account should be checked whenever a conversation/reply is expected.
Members should ask for help from group mates whenever a problem cannot be solved alone.
We, as a group, are obligated to meet all deadlines. We should communicate with the product champion whenever more information / clarification is needed about the product. Finally, we should work together to fully implement the product and aim for a high grade! ^_^
Our project for this class is to create an online event booking system for the East Scarborough Storefront. The Storefront consists of two buildings in East Scarborough. Their main goal as a company is to provide non-profit organizations in Scarborough rooms for which they can rent out to hold events for the public.
We are creating a system to allow administrators and front desk staff at the East Scarborough Storefront to view the current schedule and make room bookings on behalf of clients. A login will be required for all users of the system, and the type of user will determine which operations are possible (e.g. front desk staff should be able to make tentative bookings, but only administrators can confirm them). If there is time, we may add functionality that allows the Storefront’s clients to request tentative bookings, which must then be approved by an administrator; however this feature is not considered strictly necessary by the Storefront’s administrators.
Three views would be accessible to the users: month, day and map. The month view would show what days over a month a specific room would be available. The day view would show the rooms that are booked on each day. Finally there would be a map view, which would show a blue print of the rooms which would allow the user to interact with the rooms.
Technologies we will need:
- HTML5 and CSS3 for presentation, Javascript for user interaction
- PHP on the server for dynamic content generation and database management
- CodeIgniter Framework to make PHP coding cleaner
- MySQL to manage the client database and booking database
- Ubuntu Linux Server running on Windows Azure for test-deployment
- Users will access the site through the usual web-browsers
| User Type | Name | Links |
|---|---|---|
| Administrator | Nobarun | odt pdf |
| Front Desk Staff | Shane | odt pdf |
| Client | Tanya | odt pdf |
| Number | User Story |
|---|---|
| #1 | As a client, I want to be able to book events from any place that has internet and at anytime, so that I do not need to go or contact storefront to place a booking. |
| #2 | As a client, I want to see the storefront room's layout, so that I can plan number of attendees and room arrangement for the event. |
| #3 | As a client, I want to book same event for multiple times, so that I do not need to submit same booking requests at multiple times. |
| #4 | As a client, I want to notify the storefront management about materials that I need for the events, so that the storefront management can prepare materials on the day. |
| #5 | As a client, I want to get notification when my booking request is confirmed, so that I can stop worrying about the place and move on with other planning. |
| #6 | As a client, I want to get notification when my booking request is cancelled, so that I look for other dates or places |
| #7 | As a client, I want to see available rooms on certain day to book, so that I can plan event.s day and attendee according to availability. |
| #8 | As a client, I want my username and password are stored in my computer, so that I don.t have to type the username and password every time to login into the application. |
| #9 | As a client, I want to be able to change my personal information like phone numbers, on the fly, so that I don.t have to contact the administration every time I want to make change about my personal information. |
| #10 | As a client, I want my subordinates able to book the events but I.ll confirm the booking request before sending the request, so that I can give booking tasks to my subordinates. |
| #11 | As a public user, I want to see all upcoming events in one place, so that I can easily spot an event that might interest me. |
| #12 | As a public user, I want to see detailed information about certain events, so that I can plan my schedule properly |
| #13 | As a front desk in storefront, I want to easily access all clients’ information at first time. So when clients call me, I should fast get into database without any time consuming. |
| #14 | As a front desk in storefront, I want to booking system is available for me. So when clients call me, I should book events for them. |
| #15 | As a front desk in storefront, I want to cancel booking system also available for me. So when clients call me, I should cancel the event for them. |
| #16 | As a front desk in storefront, I want to able to put or cancel the people in the waiting. So I can actually do something if the event is full and clients want to do something else. |
| #17 | As an administrator, I can add a client with their details through an administrator dashboard, so that I can quickly add clients while meeting with them. |
| #18 | As an administrator, I can modify/update client details through any interface that shows the client's name in the application, so that the workflow is fluid and intuitive. |
| #19 | As an administrator, I can distinguish between booking requests and confirmed bookings in the calendar, so that I can have a good general overview of the schedule. |
| #20 | As an administrator, I can see and distinguish any booking times that have a waiting queue, so that I can identify the times that are important to handle if someone requests a cancel. |
| #21 | As an administrator, I can confirm or deny bookings on the calendar page without leaving the calendar view, so that I can quickly go through all the requests. |
| #22 | As an administrator, I can add bookings manually, so that I can add bookings for any clients that come in personally or phone me. |
| #23 | As an administrator, I can shift/move around scheduled (tentative or confirmed) bookings from the calendar view, so that I can visually (which results in efficiency) reschedule bookings when needed. |
| #24 | As an administrator, I can accept all requests that have no conflicting requests, so that I have more time for other tasks in the office. |
| #25 | As an administrator, I can see a map of the building and the interior and identify the spaces that are currently occupied, so that I can see the status quo of the buildings. |
| #26 | As an administrator, I can add an email for email notifications on the administrator settings page, so that I can get notifications for any events that happen. |
| #27 | As a user, I would like to be able to logon to the website. |
| #28 | As a developer, I need to build a basic framework for the website so I can then start implementing the user stories. |
Our first implemented user story is #28:
As a developer, I need to build a basic framework for the website so I can then start implementing the user stories.
To implement this story, we set up cloud services at Windows Azure. Then, we installed a Ubuntu Linux Server virtual machine and set up a user database. Finally, we created a basic website that will allow users to register and log in. In the next sprints, we will continue to build functionality into this website.
Here is the current (deployed) version of the Storefront Calendar website.
For testing purposes:-
Username : testing
Password : testing