INCEPTION PHASE PRESENTATION

1
INCEPTION PHASE PRESENTATION

• WITH
• Reservation Management System

RMS
2
TEAM RMS!

• Jordan Duguay
• (Project Manager /DBA)
• Jason Skibo
• (Project Developer)
• Hyojeong Kim
• (Project Developer /DBA)
• Ray Valcourt
• (Network Engineer /Project Developer )
• Andy Ramdass
• (Network Engineer /Project Developer )

3
Objective

• To provide an overview of the Reservation
  Management System
• Provide a status report
• Introduction to the project
• Brief look at MS Project Schedule
• A unique Vision
• Risks and how they will be mitigated
• Sample GUIs
• Class Diagram
• RMS Repository

4
What is RMS?

• The Reservation Management System will allow the
  restaurant patrons and the restaurant staff to
  place reservations into a database allowing for a
  more efficient system.

5
STATUS REPORT

• We have completed the following
• GUIs
• All diagrams
• Documentation is all up to date
• Vision statement
• Team dynamics and chemistry are excellent
• We are ready to move on to the next Phase.
• RMS Status Report

6
Purpose

• The purpose of our system is to automate the
  existing reservation system already in place in
  restaurants. The following system will allow us
  to
• Broaden our client base by allowing people to
  view the restaurant and book reservations online.
• People will be allowed to order food in advance
  allowing the kitchen to be prepared ahead of
  time.
• Total purchase will be shown in advance for
  pre-ordered items.
• People will be allowed to order rooms, seating
  areas, or special arrangements for certain
  occasions.
• Existing customers will be able to bring up their
  information from previous visits.
• Parking arrangements can be made in advance if
  requested (handicapped).

7
Jason Skibo

• What can RMS Do?
• A High level summary!

8
High Level Summary of Features (Critical)

• Add a reservation (Host / Hostess)
• Host/Hostess must be able to add a reservation
  to the system.
• Add customer to a table (Host / Hostess)
• Host/Hostess must be able to add new customer
  information, name, phone number and address, etc.
  to the system.
• Delete a reservation (Host / Hostess)
• Host/Hostess must be able to delete a
  reservation in case it was cancelled.
• Remove a customer from a table (Host / Hostess)
• Host/Hostess must be able to delete a customer
  from a table.
• Modify a reservation (Host / Hostess)
• Host/Hostess must be able to modify reservation
  information that is changed.

9
High Level Summary of Features (Continued)

• Send a confirmation e-mail to the Home user (Host
  / Hostess)
• System must be able to send a confirmation
  e-mail to the home user that is information of
  reservation .
• Add a reservation (Home user)
• User must be able to add a reservation to the
  system.
• Bring up previous reservation (Home user)
• User must be able to query previous reservation
  information.
• Remove a reservation (Home user)
• User must be able to delete a reservation that
  is reserved.
• Modify a reservation (Home user)
• User must be able to modify a reservation that
  is changed.

10
GUIs (Critical)

• Start Screen

11
GUIs (Critical)

• Main Menu Screen (Host / Hostess)

12
GUIs (Critical)

• Add Reservation Screen (Host / Hostess)

13
GUIs (Critical)

• Modify Reservation Screen (Host / Hostess)

14
GUIs (Critical)

• Add/Remove Customer to/from Table Screen (Host /
  Hostess)

15
GUIs (Critical)

• Delete a Reservation Screens (Host / Hostess)

16
GUIs (Critical)

• Add a reservation (Home user)

17
GUIs (Critical)

• Modify a reservation (Home user)

18
GUIs (Critical)

• Delete a reservation (Home user)

19
GUIs (Critical)

• About Screen

20
Class Diagram
21
RMS REPOSITORY
22
Jordan Duguay

• RMS Use Case Diagram
• Brief look at MS Project Schedule

23
Use Case Diagram

• This diagram shows our critical use cases for
  release 1 and 2 of our system
• Release 1 will be a standalone version used by
  the host / hostess at the restaurant while
  Release 2 will be used by home users over the
  internet.
• Release 2 implements an e-mail server to send
  confirmation e-mails to the restaurant and ser as
  well

24
Use Case Diagram
25
MS Project Schedule

• WBS
• Completed Tasks
• GUIs
• All diagrams
• Documentation is all up to date
• Vision statement
• Unfinished Tasks
• Network setup
• Firewall and server software
• Repository and glossary
• Completion Dates
• We hope to have the network wired next week and
  the Jason is currently designing the repository
  locally so when the server is ready we can upload
  it.
• Once our network is wired we can begin to install
  the server operating system.

26
Hyojeong Kim

• List of Risk Evaluation and Mitigation

27
List of Risk Evaluation and Mitigation

• Business Risks
• Lack of project management
• Insufficient expertise in the key project areas
• Not aware of the requirements of the system
• Project management tools have not been developed
• Apply expert knowledge, skills, tools, and
  techniques to project activities

28
List of Risk Evaluation and Mitigation

• Technical Risks
• This type of system has never been implemented
  before
• Identify all possible problems that may arise
• The requirements of the system may changed
• Make the system a flexible as possible
• The system must not allow unauthorized
  individuals to access the database
• The system must be secure

29
List of Risk Evaluation and Mitigation
(Continued)

• Technical Risks (continued)
• The system must fit to performance standards
  established in the objective criteria
• Good system design/programming techniques
• The hardware that satisfies the system
  architecture should remain in production
• Before a decision is made for which hardware is
  to be used by the system
• Ensuring that all data is persisted
• Two copies of the database

30
RAY VALCOURT

• The Vision Statement

31
The Vision Statement

• Our group decided to split up the vision
  statement into 5 sections so that each of us
  would have to be included in its creation. We
  then came together with what each one of us had
  written and went over it together so that we were
  all in the same page when it came to or team
  vision.
• Heres a general sense of what we came up with
• Purpose The purpose of our system is to automate
  the existing reservation system already in place
  in restaurants.
• Problem/opportunities We are offering a system
  that will automate the task of taking
  reservations at restaurants plus add a few
  feature that will benefit customers and the
  restaurants themselves (i.e less wasted food
  because chefs will know what they need for the
  day)
• Target demographic High end restaurants in and
  around Winnipeg
• Some of the features of our system will include
  create a reservation, pre order food, reserve a
  parking spot and several others

32
The Vision Statement (Continued)

• A few of the constraints that we can foresee are
  that some of the users that are not familiar with
  computer or that dont have on may not be able to
  take advantage of the system. Also there might be
  issues with updating the system to reflect
  changes with the restaurant or menu if there is
  no one in house that can update it.
• We came up with a few quality ranges that we will
  try to adhere to like the following 2-5 second
  response time for the site, sending a
  confirmation e-mail to the customer, program easy
  to use and navigate, having a comprehensive help
  section and 24/7 avaiability
• We plan on releasing the system in 2 versions.
  The first will include the following components
  
• 1.       An interactive user interface.
• 2.       Database connectivity.
• 3.       Add, delete and modify reservation
  information.
• 4.       Add delete and modify customer
  information
• 5.       Advance food ordering
• 6.       Advance parking arrangements
• 7.       Advance seating arrangements
• The second release will also have
• 1. A home user presence.
• 2. Track customer information
• 3. View passed history

33
The system requirements

• Client
• Hardware and software needed
• Server
• Hardware and software needed

34
The documentation

• User manual
• Document that will allow users to find
  information on the basic functions of the system.
• On-line Help
• FAQ to address concerns a user might experience
  and a feedback link in order for the users to
  e-mail us with some comments
• Installation Guides
• Document of how to install the On-line
  Reservation System.

35
Conclusion

• Provided an overview of the Reservation
  Management System
• Provide a status report
• Introduction to the project
• Brief look at MS Project Schedule
• A unique Vision
• Risks and how they will be mitigated
• Sample GUIs
• Class Diagram

36
ANY QUESTIONS!