c-h-fahy/gp3

booking management for fake cinema

gp3's Issues

2.8 any extra useful functionality, based on the brief but defined by you

3.1 Choice of colour scheme, design and layout, clear navigation

colour scheme is purple i think

5.3 Evidence of testing: test plans and results

2.2 allow or refuse entry to a screen depending on whether data keyed in by the user

2.7 display bookings affected by canceling a performance or closing a screen

if user is admin and performance exists:
select from bookings for performance
dump relevant fields onto page
delete all showings
delete performance
delete all bookings

2.6 login with a custom views of the interface based on user profile/role (director or member)

each user will have an ID, and in the database we can have something like "role" = member, usher, director...

on load select current logged in users role from ID from db.

if invalid; login
if valid: generate customer view then have if statements to add more sections to the page below

1.3 add a record to basic files using given data

2.5 prevent adding the same cinema/member/film more than once, even if id's different

SELECT film/cinema/ WHERE name=whatever

if exists throw error

2.1 ensure that bookings are accepted only correct conditions (e.g. member active, seats available)

1. user is valid member
2. performance exists
3. (total_seats_booked + seats_to_be_booked) is less or equal to total seats of the performance we got in 2

then insert booking to table and tell user it was valid
else tell the user what went wrong

2.4 display summary financial information for a performance, screen or film based on bookings

copy paste queries page

1.4 add a performance

allow admins to view select a cinema to create the performance at.
Then show a list of films and the available screens at the selected cinema so they select one, and let them enter the start and end date

Check if dates collide with any other showings on that screen at that cinema.

insert into database or report the error

Create ER Diagram

1.5 amend booking

user should have a list of bookings. if they select to amend it,
send request to delete booking and forward user to create booking page.

Create Tables and add entity relations

4.3 Powerpoint Slides

preliminary : view performance & booking data already stored in the database

5.2 Screen shots of your management of 2 sprints cycles, using Kanban

3.4 context sensitive on-line help is available

could have a "?" that you hover over to show text explaining it

redesign signup screen to be entered by staff and have title there

2.3 provide a log which records the result entry attempts and allow fexible access to data

change IDs on add and edit pages

5.4 Written evaluation of the prototype

500-1000 words against Nielsen’s and WCAG

1.2 display a selection of records from link files (performance, booking) using specified criteria

data fields must have names not FK ID

1.5 add a booking

user should be able to view performances and select one.

once they select what performance to book for, check they are a valid member, the performance is valid, and that there are enough seats available (see 2.1)

Add Sample Data

1.1 display a selection of records from basic files (cinema. screen, film, member) using specified criteria

1.- delete a booking

not in the UAT spec, but needed to alter booking. Could also be under 2.8 any extra useful functionality, based on the brief but defined by you.

when we recieve a request, check the booking exists, (check the member is the one who owns it or is staff?) then delete it from the database.