1. Sport Booking System Team: Double-D

2. Team Members Team Leader Matthew Sayer - s3199258 Programmers Tim Alford - s3201188 Matt Dennett - s3200053 Designers Earl McMillan - s3167514 Byron Patterson - s3165841

3. Project Management

4. Timeline RMIT WEEKS Week 5Week 6Week 7Week 8Week 9Week 10Week 11Week 12 Design Documents User Interface Wireframes Logo E.R. Diagram Database Schema Sitemap Use Cases Project Proposal Risk Management Document Project Timeline Design Static Screens Images Style Sheets Programming User Authenication Search Screens Session Management Database Create Database Create Tables Populate with dummy data Create queries for PHP

5. Risk Management Plan RiskLikelihoodImpactMitigation Strategy Central area for setting up database not provided on time. PossibleModerate Set up temporary database in case in one student’s directory, or elsewhere. Milestone not reached on time.PossibleHighFactor in slack time to all milestones. Team member out of action due to sickness/other reason. PossibleModerate Equal load balance of work to account for missing team member with minimal impact on other members. Accidental loss of code/filesPossibleHigh SVN version control provides option of restoring previous versions of project in case of data loss. Team members overwriting each other’s changes LikelyModerate SVN prevents unwanted overwriting of other changes, allows merging of multiple changes of a file. Lack of communication between team membersLikelyModerateRegular team meetings, facebook events and team wiki to facilitate communication and provide constant updates.

6. Database Diagrams

9. Screen Mock-ups

12. Programming/Data Flow

15. Current Progress

16. Questions?