Build a Website

# Ruby Assignment ## Scenario Your team is working with a local record label. As part of an modernization push update the company would like a Rails app or a Single-Page app backed by a ruby RESTful API for booking recording sessions at the studio. Your job is to prototype the application over several iterations. Acceptance criteria will be provided for each iteration. ## Your Deliverable This is not a design assignment. While the app should be usable, it needn't look pretty. If you wish to use something like Twitter Boostrap that's perfectly acceptable. This exercise is not designed to take a long time. How much time you spend is totally up to you. With that said, your code should be of good quality: something that could easily be used as a base for a more complex production application. The application should be well documented and tests should be written for applicable code. Please submit the project as a git repo. You should complete as many iterations as you feel you can accomplish in the given timeline. Iterations should be easily identifiable in the git history. Assume that we will be running a MySQL instance for the database. ### Iteration 1 Build a prototype application which allows a user to book a recording session at the studio. Users should be able to supply a band name, a contact name, a contact number, and provide comments for any additional details/requests regarding their session. **Acceptance criteria** * Recording sessions are 2 hour 45 minutes long, separated by 15 minutes. * The studio is closed for lunch from 12pm to 1pm daily. * Only one user may book a given recording session. * The studio is open for bookings from 9am to 9pm every week day. * Users should have some mechanism to see if a session is already booked. * Users should be able to cancel a booking. * The studio should have some mechanism to see what sessions are booked along with details of the booking. ### Iteration 2 The prototype has been approved by the studio. As the studio has grown they now have 3 recording rooms. Please extend the application to support multiple bookings per session to accommodate the new rooms. **Acceptance criteria** * The application should support up to 3 bookings per session. * The studio should have some mechanism to change the booking limit per session. * Users should not be able to book more than 1 booking in a given session. * Users should have some mechanism to see how many bookings, which recording rooms, remain on a given session. ### Iteration 3 The studio would like to add some constraints to the booking process. **Acceptance criteria** * Users should have some mechanism to log in and see current and previous bookings. * The studio should have some mechanism to set certain sessions to: needs approval. * The studio should have some mechanism to approve or deny booking requests. * Users should be able to search for available bookings by room name. * Users should not be able to book more than 2 sessions in a given day. * Users should have some mechanism to see the status of their current bookings. * Bookings can't be canceled when they start less than an hour from the current time.