oliverwoodings / deliverable-2 Goto Github PK

The departmental timetables should have the ability to remove a module from the database.

Take on board the loughborough house style:

• New header background
• Hover colour schemes
• Table styling
• Gradients need reworking
• JQuery UI needs a new theme

When hovering over a pending request in the table, the option to cancel the request should appear. This would remove it from the table and also delete the request from the Database.

Area where the user can specify which kind of room they require for the request. Should contain dropdown for park selection, dropdown for room type, input area for number of rooms and an input area for a room preference. Room preference are, when clicked, should drop down a table of all rooms.

Need a way to move the Database from one round to another. i.e Round P to Round 1.

Needs to show the key recent activity in a list. Copy basic layout from prototype.
Types of notifications to be shown:

• Round begins
• Round ends
• Rooms allocated
• Allocation declined
• Request added
• Request edited
• Request cancelled
  Needs to show date, type, module, day and period for each one (where relevant)
  On click will link to relevant information

When hovering over a pending request in the table, the option to edit the request should appear. This would take the departmental timetabler back to the request page with the information pre-filled in allowing them to edit their original request.

Implementation of page design html structure

We were criticised for our week selection system so we need to rework it. Needs to allow for random week selection

Need to show rooms that have been failed by central admin and rooms that have been given a different room to the one requested.
Need to highlight failed rows red since they are more important.
On click they should take you to the room allocations page

The Search Box should have 2 main tabs: search by filters, and search by room.
Search By Filters tab - contains the park, room type, capacity and facilities filters.
Search By Room tab - allows selection of a building and/or room, if a building is selected, this should filter the room list.

This will be the main table that displays the responses. It should display all relevant information on first glance and expand to then show the extra information once a response is clicked.

Small circle on the left of the logout button that shows the curren round
On hover it should show the start and end dates
Follow Ben's design

We have module management but we also need course management

The departmental timetables should have the ability to add a module to the database.

This will display the results of a users search, should show the user if there are any room available in each slot, and if so how many. If there are no available rooms during a particular slot matching the users search then the timetable should make this clear.
Time slots should be click-able to allow user to see which rooms available.

ER diagrams for the information which is being managed and a data table structure for your ER design.

When a checkbox in the Search By Filter tab is selected this needs to update the table to show only those rooms that match the selected checkboxes, e.g. if OHP in facilities is checked, only rooms that have that facility should be displayed in the timetable.
When an item is selected from a dropdown menu, i.e. select room, this needs to filter the table to only show rooms that match those requirements.

As discussed in the meeting last week the template styling needs updating to match the more modern-looking pages on the Loughborough website, rather than the traditional ones.

The CSS for the prototype template was horrible and messy. It needs cleaning up and simplifying to make the code easier to work with

The departmental timetables should have the ability to edit a module in the database, to update the lecturers running the module and the module code/name.

Should contain checkboxes for the facilities for a request, and an input area for any special requirements for the request.

Styling needs to be changed a little to match the new modern styling of the framework

The Search Box should have three main sections for the departmental timetabler to use:
Find Module, which searches the table for a specific module and displays only that.
Additional Filters, which displays check boxes for Round, Part and Day.
Type selction, from here they can choose to display a certain type of response i.e Pending, Allocated...

The ERD needs to be implemented in PHP/SQL

The login page needs to hook into the main auth system - needs to link to the index.php?page=login

In the available rooms overlay users should be able to select one or more rooms. Needs to have a request room button which is easily seen in the overlay, once this is clicked it should pass the selected rooms to the make request page for completion of the request.

The Search Box should have 2 main tabs: search by filters, and search by room.
Search By Filters tab - contains the park, room type, capacity and facilities filters.
Search By Room tab - allows selection of a building and/or room, if a building is selected, this should filter the room list.

• Needs to show start and end date of round on hover
• Copy the design off the prototype
• Active round is larger and purple

Timetablers like different ways of working - need to make grid and timetable views etc

When hovering over a declined or failed response in the table, the option to resubmit the request should appear. This will then take the user to the request page and checks to see if the original request is available (i.e the room hasn't been taken) will then fill in the data, allowing them to resubmit.

When clicking on the titles in the table, the information should then be sorted by what title was clicked i.e if the departmental timetabler was to click on length, it would show all responses with length 1, then 2 ect...
This would reverse the ordering once clicked again.

Need to be able to allocate rooms to pending requests, reallocate rooms in requests and fail requests and then update the database with the correct status/response.

Listings of all of your PHP scripts. Use a maximum width of 80 characters and ensure that no lines wrap. Each script should be written so as to make it as easy as possible for it to be understood and altered by someone not familiar with the code, e.g. choose meaningful variable names, include appropriate comments etc. In particular, there should be an extended comment at the top of each script explaining what it does and explaining the contributions made by each member of the group.

On the header page, the departmental timetable should have the ability to change semester.

Need to implement the DB structure in PHP using OOP.

Re-modify styling in order to comply with the new house style agreed for the end user.

Re-modify styling to suit the new house style agreed for the system.

Get essential code for Module Page from the Prototype to give basic structure and look of page, so can be filled with PHP when database is working.

Footer needs to stick to bottom properly without causing scroll bars

An implementation of the auth class needs to be made to suit our login system

Each time slot will show the number of rooms available and number of rooms booked for that time. When clicked an overlay should open, displaying all available rooms for that time that meet the requirements entered by the user. For each room: room number, building, park, capacity, room type, facilities should be displayed, an image of the room, if available should also be displayed.

When a module is entered into the search box, the information in the table needs to be updated to display the relevant information.

When hovering over a reallocated response in the table, the option to decline the request should appear. By doing this, it releases the room to allow other timetablers to attempt to book the room and removes the information from the table.

Area for module selection should have an area for input and selection of a module, drop-down for the number of students, and a checkbox for whether the request is a priority or not.

Add PHP so database is pulled from and on button pushes edited in correct manner.

Need to make it easier for timetablers to make multiple requests

Requests have bookings - needs to be incorporated into our ERM
Also need to implement course and part entities

One page discussing the issues you have considered to make your system portable & accessible (e.g are you checking your html using the validator at http://validator.w3.org/ and also http://jigsaw.w3.org/css-validator/ . If appropriate, are you using generic fonts and are your sites accessible using http://www.etre.com/tools/accessibilitycheck/ ?).

When a checkbox is ticked, the information in the table needs to be updated to display the relevant information i.e if the departmental timetabler checks the pending box, then the table should only display the pending responses.