Vision Document by HC120807025159

VIEWS: 0 PAGES: 8

									                     Vision Document
                 For Hotel Reservation System (HRS)

                              Version 1.1




Submitted in partial fulfillment of the requirements of the degree of MSE




                            Cem Oguzhan
                        CIS 895 – MSE Project
                        Kansas State University
                                                Table of Contents

1. Introduction ................................................................................................................. 3
1.1.    Motivation ........................................................................................................... 3
2. Project Overview ....................................................................................................... 3
2.1 Introduction ............................................................................................................... 3
2.2 Goal ........................................................................................................................... 4
2.3 Purpose...................................................................................................................... 4
3. Requirements Specification ....................................................................................... 4
3.1 Main Requirements ................................................................................................... 4
3.2 External Interfaces Requirements ............................................................................. 4
3.3 Critical Use Cases Requirements .............................................................................. 5
3.2.1 Use Case 1: Search Room Requirements............................................................... 5
3.2.2 Use Case 2: Login Requirements ........................................................................... 5
3.2.3 Use Case 3: Apply for an Account Requirements ................................................. 5
3.2.4 Use Case 4: Generate Report Requirements .......................................................... 6
3.2.5 Use Case 5: Create Account Requirements ........................................................... 6
3.2.6 Use Case 6: Edit Account Requirements ............................................................... 6
3.2.7 Use Case 7: Make a Reservation Requirements .................................................... 6
3.2.8 Use Case 8: Cancel a Reservation Requirements .................................................. 6
3.2.9 Use Case 9: Add / Update Hotel Information Requirements ................................. 7
3.2.10 Use Case 10: Add / Update Room Information Requirements ............................ 7
3.2.11 Use Case 11: Approve / Disapprove Travel Agent Account Requirements ........ 7
3.2.12 Use Case 12: Generate Report Requirements ...................................................... 8
3.4 Performance Requirements ....................................................................................... 8
3.5 Assumptions.............................................................................................................. 8
3.6 Constraints ................................................................................................................ 8
3.7 Environment .............................................................................................................. 8
1. Introduction

   1.1. Motivation
   Internet has become available almost anywhere. Now, we can research, shop, play games, and
   communicate with others around the world without leaving our computers. For many businesses, the
   Internet has become very crucial for their daily operations. It has become one of the most important
   marketing tools, which generates revenue for many businesses.

   Behind the scenes of web sites are web developers. The developer’s responsibility is to ensure that a
   user get the best possible experiences while surfing web-sites. Recently, web development tools have
   greatly improved. One of these tools is the Microsoft .NET framework. Today, the .NET framework
   makes it possible to create complex Web applications easier and faster than ever before.

   The motivation of the Hotel Reservation System (HRS) is to develop a web application that helps
   online customers and travel agents to make a reservation without leaving their place or making a phone
   call and save valuable time. In addition, as a developer I want to learn and gain experience developing
   application on the .NET framework.

2. Project Overview




                                        Figure 1. Overview of HRS


   2.1 Introduction

   The HRS is a hotel chain reservation system. There are two types of users. These are online customers
   and travel agencies. The hotel reservation system will provide service to on-line customers and travel
   agents. On-line customers and travel agents can make searches, reservations and cancel existing
   reservation on the hotel reservation’s web site. The travel agent will take ten percent commission for
   each reservation it’s made. There is an administrator to maintain the HRS system. The administrator
   can add a new hotel and rooms, or update the hotel and room properties and approve or disapprove a
   travel agent’s account request to be a member to the HRS. Also, the administrator can generate
   monthly report for occupancy rate of each hotel.

       Figure1 shows a high level of the HRS system. The HRS system will interact as follow:
       1. Client sends HTML form inputs over a network
       2. Internet Information Server (IIS) receives HTML form inputs
       3. IIS Web Server
                a. Processes inputs
                b. If required, it queries the database and retrieves data
       4.   IIS Web server sends back processed output as a web page over a network
       5.   Client receives the output as a web page

   2.2 Goal
   To provide a web site that can allow a user to search and reserve a hotel room or cancel his/her
   reservation over the internet at any time.

   2.3 Purpose
   To learn and gain experience developing applications on the .NET framework.

3. Requirements Specification

   3.1 Main Requirements
       1. Based on 3-tier architecture. Figure 2 shows the 3-tier architecture.
       2. Use of Microsoft Visual Studio .NET IDE, ASP.NET, C #, MSSQL in developing the system.
       3. The final product will be run on Internet Information Server (IIS).
       4. Internet Explorer will be used as the main browser.




       Figure 2. 3-tier Architecture

   3.2 External Interfaces Requirements
       The external interfaces for the HRS will be written using ASP.NET Web Forms combined with
       the User Controls.
3.3 Critical Use Cases Requirements


                                                                                      Search   Room




                                                                                           Login




            User                                                                       Apply for an
                                                                                        Account
                       .
           «extends»       «extends»


                                                                                   Generate a Report




                                                                                     Create Account

 Travel Agent                  Customer




                                                                                       Edit Account




                                                                                    Make a Reservation




                                                                                          Cancel a
                                                                                         Reservation




Figure 3. Critical Use Case diagram for a User


    3.2.1 Use Case 1: Search Room Requirements
    Purpose: The purpose of this part of the application is to check an available room at the hotel.
    Inputs: The user will enter six inputs (city, state, country, check-in date, check-out date, and
    number of room) through the keyboard.
    Processing: The user inputs will be validated on the client side. The validation will verify that
    user enters a valid format into the required fields.
    Outputs: If the user inputs are not valid, the appropriate error message will be displayed. If the
    inputs are valid, the hotel(s) information’s will be displayed for the particular search.

    3.2.2 Use Case 2: Login Requirements
    Purpose: The purpose of this part of the application is to provide user authentication.
    Inputs: The user will enter two inputs (user name and password) through the keyboard.
    Processing: The system then checks user name and password to see if they are valid.
    Outputs: If the user name or password is not valid, the appropriate error message will be
    displayed and the user will need to re-enter the user name and password. If the user inputs are
    valid, the user’s requested secure web page, which requires login, will be displayed such as the
    confirm reservation web page.

    3.2.3 Use Case 3: Apply for an Account Requirements
    Purpose: The purpose of this part of the application is to allow travel agents to apply for an
    account for becoming a member of the HRS system. The travel agents can apply for an account,
    but they need to be approved by the administrator to become a member of the HRS system.
Input: The travel agent will enter required information. These are company name, address, city,
state, zip code, phone number, user name, password, and e-mail address over the request account
web form.
Processing: The system then checks user name to see if it is valid. If the user name already exists,
the travel agent needs to re-enter another user name. Otherwise, the travel agent information will
be saved into the database.
Output: For correctness, the travel agent inputs will be validated. If the travel agent inputs violets
any input format, the appropriate error message will be displayed. If the inputs are valid, the
confirmation web page will be displayed and an e-mail will be sent to the travel agent for
confirmation.

3.2.4 Use Case 4: Generate Report Requirements
Purpose: The purpose of this part of application is to provide a sales report to the travel agent.
Inputs: The travel agent will enter starting date and ending date of the report through the
keyboard.
Processing: The system checks the inputs to see if they are in correct format and valid.
Output: If the input is in correct format and valid, the sales report web page will be displayed. If
the input is not in the correct format or valid then the appropriate message will be displayed.

3.2.5 Use Case 5: Create Account Requirements
Purpose: The purpose of this part of the application is registration of a new customer which
allows to the customer to become a member of the HRS system.
Input: The customer will be entered some information, which is required by the HRS, over the
web form. These are first name, last name, address, city, state, zip code, phone number, user name,
password, e-mail address, credit card type, credit card number and expiration date.
Processing: The system then checks user name to see if it is valid. If the user name already exists,
the user needs to re-enter a new user name. Otherwise, the customer information will be saved in
appropriate format into the database.
Output: For correctness, the customer inputs will be validated. If the customer inputs violets any
input format, the appropriate error message will be displayed. If the customer inputs valid, the
confirmation web page will be displayed.


3.2.6 Use Case 6: Edit Account Requirements
Purpose: The purpose of this part of the application is to update of the customer’s account.
Input: Except user name, the customer allows to update his/her first name, last name, address,
city, state, zip code, phone number, password, e-mail address, credit card type, credit card number
and expiration date.
Processing: If the customer’s inputs valid then the customer information will be saved in
appropriate format into the database.
Output: For correctness, the customer inputs will be validated. If the customer inputs violets any
input format, the appropriate error message will be displayed. If the customer inputs valid, the
confirmation web page will be displayed.

3.2.7 Use Case 7: Make a Reservation Requirements
Purpose: The purpose of this part of the application is to reserve a room.
Input: The user already entered required data such as check-in and check-out date, when the user
was searching a room.
Processing: The related reservation data will be saved into the database.
Output: If the reservation is successfully completed then the reservation confirmation web page
will be displayed. Otherwise, the appropriate error message will be displayed.

3.2.8 Use Case 8: Cancel a Reservation Requirements
Purpose: The purpose of this part of the application is to cancel the reservation.
Input: The user will enter the reservation number through the keyboard.
Processing: The system checks the reservation number to see if it is valid.
Output: If the reservation number is valid then the user’s reservation information will be
displayed for canceling. Otherwise, the appropriate error message will be displayed.

                                                              Add / UpdateHotel
                                                                 Information




                                                             Add / Update Room
                                                                Information




                                                            Approve / Disapprove
                                                            Travel Agent Account
 Administrator




                                                               Generate Report


Figure 4. Critical Use Case for Administrator

3.2.9 Use Case 9: Add / Update Hotel Information Requirements
Purpose: The purpose of this part of the application is to add a new hotel or update information
on the existing hotel.
Input: The administrator will enter some data. These are hotel id, hotel name, address, city, state,
zip code, phone number, and star rating through the keyboard.
Processing: The system checks the inputs to see if they are in correct format and valid.
Output: If the inputs are in correct format and valid, the inputs will be saved into the database and
the confirmation web page will be displayed. If the input is not in the correct format or valid then
the appropriate error message will be displayed.

3.2.10 Use Case 10: Add / Update Room Information Requirements
Purpose: The purpose of this part of the application is to add a new room or update information
on the existing room.
Input: The administrator will enter some data. These are room number, price, bed type, smoking
type, handicap accessible or not through the keyboard.
Processing: The system checks the inputs to see if they are in correct format and valid.
Output: If the inputs are valid and in correct format, the inputs will be saved into the database and
the confirmation web page will be displayed. If the input is not in correct format or valid then the
appropriate error message will be displayed.

3.2.11 Use Case 11: Approve / Disapprove Travel Agent Account Requirements
Purpose: The purpose of this part of the application is to approve or disapprove of a new travel
agent account who wants to be a member to the HRS system.
Input: The administrator will analyze the travel agent information which is filled by the travel
agent.
Processing: The administrator will approve or disapprove the travel agent’s application.
Output: The administrator will inform the travel agent regarding its application by an e-mail.
         3.2.12 Use Case 12: Generate Report Requirements
         Purpose: The purpose of this part of the application to generate monthly report on total revenue
         and occupancy rate of each hotel.
         Input; The administrator will enter some data. These are hotel ID, starting date and ending date
         through the keyboard.
         Process: The system checks the inputs to see if they are in correct format and valid.
         Output: If the input is in correct format and valid, the report web page will be displayed. If the
         input is not in correct format or valid then the appropriate message will be displayed.

3.4 Performance Requirements
    The application will use client side validation for user inputs to reduce load of the web server. The
    application will use JavaScript to validate user inputs.

3.5 Assumptions
        The users have internet connection when ever he/she is using the HRS.

3.6 Constraints
        Since developing web applications on the .NET frame work is platform dependent, which is
         Windows, the final product will be deployed on IIS web server.

3.7 Environment
        The HRS will be written in C#.
        Microsoft Visual Studio .NET will be the development environment.
        The HRS will be tested on Windows XP platform

								
To top