1 Assignment Information

2 Introduction

NOTE: read the whole assignment brief first before implementing it contains very important information

In this assignment you will be tasked with building an application that will schedule rooms for use. Your application will support a multitude of rooms and users. As there is potential for overlap in room bookings you will be expected to do validation here to prevent double bookings of rooms. Your application must be capable of the following

• The ability to add and delete rooms. You should not be able to add the same room twice nor should you be able to delete a room that currently has bookings.
• The ability to add and delete bookings for a room. A booking can only be made if it doesnt clash or overlap with other bookings for that room. It should be possible to view all the bookings for a given day on a room. They should be listed in order of time. When a room is viewed there should be a facility to delete that booking. (but only by the user who made the booking)

The score for your application will depend on:

1. How fully featured, complete, and robust your code is. Along with howwell your UI is thought out (80%)
2. How well documented is your code

5 Coding Brackets

1. Bracket 1
   • Get a working login and logout shell up and running
   • Create appropriate models for a User, Room, and Booking
2. Bracket 2
   • Build a UI that permits a user to add in a new room. Bracket Failure if the same room can be added twice
   • When a user logs in they should see the list of rooms that are available to book. Bracket Failure if not all rooms are shown
3. Bracket 3 Add in facilities for adding a booking to a room.
   • Bookings should be done on a seperate page Bracket Failure if not on a seperate page
   • Room bookings should be validated before they are accepted Bracket Failure if overlap is permitted or a booking can be made in the past
4. Bracket 4 Update the main UI to permit a user to query all rooms or a specific room for their own list of bookings.
   • Update the main UI to permit a user to query all bookings on a room.
5. Bracket 5 When the list of bookings for a user is shown there should be a delete button shown beside the booking.
   • When the delete button is clicked it should delete that booking Bracket Failure if the wrong booking is deleted When the list of bookings for a user is shown there should also be an edit button shown beside the booking.
6. Bracket 6 Editing should take place on a seperate page and the form should be prepopulated with the current data about the booking Bracket failure if neither attempted Clashes and past dates/times must be checked for when editing a booking.
7. Bracket 7 In the list of bookings on a room show the delete and edit buttons but only on the bookings owned by a user.
   • Modify the room listing facility to include a filter by date. It should only show the room bookings for all rooms that fall in that time range.
8. Bracket 8
   • UI design: well thought out UI that is easy and intuitive to use.