AGL BACKSTAGE MANAGER

Will, Omar, Kyle, Anastasia, Greg

- Project Description - Why is this needed? - What are we solving?

- Requirements - Easy to understand by end-users - Provide all the needed casting information for

directors - Make producing a show easier and more

intelligent

SUMMARY

Website flow

• Was determined from the requirements specified by the client • Reflects user permissions

• Will guide work priorities

and help with the test cases

4

User Permissions

• There are three types of users:

1. 1. Regular users can view and edit profile, view shows, auditions, and calendar for the show

2. 2. Sub-admin have same permissions as regular users and admin, except they cannot create, edit, or delete data in DB

3. 3. Admin can create, delete, and edit all the data

5

Database design

• Database Schema

• User( uID:int, email :string, fullname:string, auth:int, password:string, picture:img, ...)

• Shows( showID :int, showname:string, stagemanager:string, actorlist:array, perfdates:string)

6

Security consideration

• What does the customer need?

• Password encryption

• - One-way encryption into the database

• - Hashed and salted

• - md5 is unsecure. We are using bcrypt

• - php password_hash() function

7

Security consideration

• SQL Injections

• - Prepared statements: separating user

• input from SQL logic

• - Also built into php

Log In Page

Edit Profile

View Profile

View Profile - 2

Search Database

Use Cases - Actors - Create, edit profile - Check show - Director - Create show, add schedule, add actors -Stage Manager - Checking calendar for conflicts -Costume Designer - Look at measurements -Administrator - Remove accounts, create sub-admin accounts

14

Problems

• - Learning how to use Bluehost

• - Integrating a calendar

• - Working with actors, changing requirements

• - Making a clean user interface/flow

15

Questions!

• Questions?