Docstoc

PHASE – I

Document Sample
PHASE – I Powered By Docstoc
					    GetAwayCheap.com
              PHASE – I

             Baqir Raza Qureshi
                Najeh Adib
              Yevgeniy Geltser

CSE 255 – Introduction to Database Systems
          Prof. Steve Demurjian
        University of Connecticut
Introduction


  1.1Purpose of Document


  The project in this document is to develop an online system that integrates all aspects of
  traveling. It is primarily being designed to cater for travel agency market as being the
  primary customer but also has the ability to let home and business users directly use the
  system.


  1.2 Scope


  The system to be made in this project is a travel reservation system, which is provided via
  the Internet. It will allow customers and travel agencies to search for and reserve for
  flights, hotels, car rentals, cruises and trains. The system will be linked to external
  databases so as to get information about flight availability, payment processing, car rental
  reservations… etc.


  1.3 Overview:


  This document is to specify the conceptual and functional requirements to build an online
  travel management system. All the requirements mentioned in the document is to
  facilitate a better understanding and realization of the system.


  The document will provide an overview of the product, including basic functionalities of
  the system, such as booking for flights, hotel room reservation, car rental etc. Each user
  of the system will be introduced. Assumptions and requirements for future expansion will
  also be included in this section.




                                                                                               2
Next the document will explain the specific requirements, which contains all detailed
functional requirements as well as presenting the ER-diagram along with use case
diagrams, activity diagrams and state diagrams.


After the description of the functional requirements of the system, non-functional
requirements of the system will be discussed. These will include concerns for standard
compliance, design difficulties if any and system limitations.


2      Overall Description


2.1 Product Perspective


The system will be an independent product suitable to be used by travel agencies as well
as public consumers for making travel plans. It contains of a website being supported by
a relevant database. The functioning of this system requires interaction with external
databases such as the banking system for credit card processing, flight reservation
systems such as SABRE etc, car rental agencies.
In order to avoid redundancy in data only relevant information of the customer is kept in
the system database and rest is requested by interacting with external databases such as
getting the information about flight availability are requested from external databases
rather then keeping it in the local databases.


Interaction with banking system is required so that the customers can pay for fares and
charges through the website. Any change in the information will be cascaded down to the
banking system database so as to keep the integrity of the data


Interaction with the car rental databases, cruise ship databases and hotel reservation
databases are needed for booking rooms and providing different transportation modes to
the users.




                                                                                            3
2.2 System Users:


       Travel Agents
       Home Users
       Business Users
       Government Users
       Hotel Personnel
       Cruise Ship Personnel
       Car Rental Company Personnel
       Security Personnel
       System Administrators
       Database Administrator


2.3 Assumptions for ER-D:


   Each User must have a unique user ID
   Each User must have a unique access level defined
   A home user or a business user may or may not use a travel agent for making
    reservations
   A user will have one and only one registration profile per user id
   A user can have zero or more bookings
   A booking (vehicle/flight/room/cruise) can be for one and only one user
   A booking (vehicle/flight/room/cruise) will have one status (confirmed/cancelled) at
    any given time
   A booking status can be for many different bookings (vehicle/flight/room/cruise)
   We are assuming that all customers reside within the same country but this may
    however change
   Lodging ID must be unique
   A lodging facility can have one and only one star rating




                                                                                           4
   A room must belong to a lodging facility
   A lodging facility can have one and only one type
   A lodging type can have zero or more lodging facilities
   A room can have one and only one type
   A room type can have zero or more rooms
   A room number must be unique
   A room booking can be for one and only one room
   A room can have zero or more bookings
   A vehicle booking can be for one and only one vehicle
   A vehicle can have zero or more bookings
   A vehicle can be of one and only one type
   Vehicle booking id must be unique
   A vehicle type can have zero or more vehicles
   A vehicle can be owned by one and only one company
   A rental company can own one or more vehicles
   A vehicle can be of one and only one model
   A vehicle model can have zero or more vehicles
   A flight id should be unique
   A flight booking can be for one and only one flight leg
   A flight leg can have zero or more bookings
   A flight leg has one and only one type of aircraft
   A flight booking is for one and only flight travel class
   A flight travel class has zero or more flight bookings
   A type of aircraft can be flown on zero or more flight legs
   Cruise booking id must be unique
   Cruise id must be unique
   A cruise booking can be for one and only one cruise leg
   A cruise leg can have zero or more cruise bookings
   A cruise travel class can have zero or more cruise bookings




                                                                  5
   A cruise booking can be for one and only one cruise travel class
   Train seat number must be unique
   Train station must be unique
   A train booking can be for one and only one train
   A train can have zero or more train bookings
   A train can have zero or more train schedules
   A train schedule is for one and only one train and a train station
   A train station can have many trains with different schedules
   A train booking can be for zero or more seats
   A train seat can have one and only one booking




                                                                         6
1.4 Use-Case Diagrams:
1.4.1 Flights




                            Figure 1.4.1: Flights Use-Case Diagram


1.4.1.1    Use-Case Scenario: Search Flights
Actors
   Guest Users
   Registered Users (Home and Business)
   Travel Agents


Conditions
   Users must have Internet connection(s).




                                                                     7
   Users must have general knowledge of surfing the internet.
   Users must know the URL of the website


Use Case Description:
   Users of the system, including registered/non-registered users are able to create
    profiles, search flights book flights, modify reservations, edit profile, and view
    profiles.
   Travel Agents have the same ability as registered users.
   The user and travel agent will have the same interface with regards to all scenarios.


1. User must choose the option of searching flights, and then enter the following required
flight information:
       User enters their departure and arrival location
       User has the option of choosing a specific date range and time, or to search all
        dates
       User has the option of choosing the number of travelers, adult or children.
       User has the option of choosing between a round trip, or one way ticket


2. The system will respond by returning a list of possible flights available listed in the
order of lowest price fair to highest price fair.
   The results return will include the airline, flight number, price for that flight, and
    departure, time of arrival, and the duration of flight


Alternative Options:
                      If the user has left out some information the system will return a
                       error message outlining what information is to be entered.
                      If the time is too close to the time of departure of the flight available,
                       the system will return an error message saying it is too close to the
                       time of departure.




                                                                                                8
                           If a flight is not available, system will return an error message saying
                            a flight is not available on that day.


    3. Users will then get the option to either create a profile, or to log in to an existing
profile.
              Users will be able to modify/view his profile
              Users will be able to modify their reservation
              Users can then specify their preferences (i.e. kosher meals, pregnancy, handicap
               etc…)




    Constraints:
           Once user formally fills out a profile, then he/she is known as a registered user




1.4.1.2           Use-Case Scenario: Book a flight
Actors
          Registered Users
          Travel Agents


Conditions
          Users must be registered in the system
          Users must have already check the availability of flights


Use-Case Description:
For the user/travel agent to book a flight, they need a user login, and a current profile within
the system.
          Users provide their login ID and a valid password
          Users choose their itinerary (after checking their availability of flights)




                                                                                                   9
      Users choose their seat
      Users enter additional passenger details
           o If shipping address and billing address is different
           o Users special requests
           o Users enter their credit card information


1. A page with confirmation will appear, and a confirmation email will be sent to the users.


Alternative Options
      If login ID is not valid, system will return an error message.
      If user password is not valid, system will return an error message
      If user has not filled in all mandatory fields, the system will require the user to refill
       the errant fields




Constraints:
Users may only pay by credit card.




1.4.1.3        Use-Case Scenario: Modify Reservation


Actors:
      Registered Users
      Travel Agents


Conditions:
Registered Users and Travel Agents have the ability and option to modify a current existing
reservation.




                                                                                                10
Description
Users are able to change the date of reservation and cancel bookings online.


        Users log in
               o Enter login ID and password
        Users may choose to cancel or modify reservation
        If users choose cancel, the reservation record will be deleted.
        If users choose ”modify”, users may only change the date of the flight.
               o Modification of flight number, date, and time (if available)
               o Modification of seat assignment


Constraints:
none



1.4.1.4           Use-Case Scenario: View Profile
Actors


        Registered Users (Home and Business)
        Travel Agents
        Personnel (Security, Airline, and Government)


Conditions:


Airlines personnel can access the traveler profiles of the individuals (only registered) Similar
access will be given to government personnel working for (embassies, state departments
etc…) and security personnel who utilize travel profiles to insure the safety of individuals as
they travel.


Use Case Description:




                                                                                              11
        Personnel and Travel Agents can access the system to vie customer profiles for
         specific reasons
        Personnel have the ability to search/view profiles


1. User must choose the option of searching profiles, and then enter the following required
flight information:
        Can search by entering user name, address, ss# etc… (personal info)
        Can search by entering flight number, departure/ arrival time etc..
        Can search by flight to/from specific locations (and/or countries)


2. The system will respond by returning a list of possible profiles matching all
available/possible search records.
        The results return will include the name, customer ID#, history of flight record, and
         duration of leave


Alternative Options:
                           If the user has left out information the system will return an error
                            message outlining what information is to be entered.
                           If the user has left out information but the system can return a
                            profile, then the system will return all possible profile searches.
                           If a profile matching the search query is not available, and there are
                            no system matches, the system will return an error message saying a
                            profile is not available.




1.4.1.5         Use-Case Scenario: View Profile
Actors


        Airline Database Administrator




                                                                                                   12
Conditions:
Airline Database Administrators are there to maintain the database. Although they will
technically have access to all functionalities available for all users, the database
administrator’s role is to maintain information so that it is up and running 24 hrs a day, 7
days a week. Thus his “technical” role is just to maintain data, and nothing else.


Use Case Description:
      Airline Database Administrator can add, delete, search, and query any valid data
       entry
      Airline Database Administrator can delete profiles, and registered users.
      Airline Database Administrator can modify user names and information.




1. Airline Database Administrator must login with a special ID allocated under his name.
Users provide their login ID and a valid password
      Airline Database Administrator log’s in.


Alternative Options
      If login ID is not valid, system will return an error message.
      If Airline Database Administrator password is not valid, system will return an error
       message
      Airline Database Administrator has access to master default login/password
Constraints:
None




                                                                                               13
                               Figure 1.4.2: Hotels Use-Case Diagram




1.4.2 Hotels


1.4.2.1         Use-Case Scenario: Search Lodging Availability
Actors
        Guest Users
        Registered Users (Home and Business)
        Travel Agents


Conditions
        Users must have Internet connection(s).




                                                                       14
      Users must have general knowledge of surfing the internet.
      Users must know the URL of the website


Use Case Description:
      Users of the system, including registered/non-registered users are able to create
       profiles, search hotels for availability, modify reservations, edit profiles, and view
       profiles.
      Travel Agents have the same ability as registered users.
      The user and travel agent will have the same interface with regards to all scenarios.


1. User must choose the option of searching hotels for vacancies, and then enter the
following required information:
          User enters their arrival location and preferred check in time
          User has the option of choosing a specific date range and time, or to search all
           availabilities
          User has the option of choosing the number of rooms needed, number of people
           per room, and type of traveler (adult or children. )
          User has the option of searching by specific Hotel type (resort, casino etc..) or by
           the number of Stars allocated to the hotel


2. The system will respond by returning a list of possible room vacancies within each hotel,
in the order of lowest price vacancy to highest price vacancy.
      The results return will include the room type, price, check in time (time availability of
       room) , departure check out time (based on user dates) , and the duration of stay.


Alternative Options:
                           If the user has left out specified search query information, the system
                            will return an error message outlining what information is to be
                            entered.




                                                                                                15
                         If the time of check in is too close to the current time, the system
                          will return an error message saying it is too close to the time of
                          check in to find a vacancy.
                         If a vacancy within a specified hotel is not available, the system will
                          return an error message saying a flight is not available on that day.


3. Users will then get the option to either create a profile, or to log in to an existing profile.
            Users will be able to modify/view his profile
            Users will be able to modify their current reservation (after user is validated
             through login)
            Users can then specify their preferences (i.e. double beds, single, king size,
             Jacuzzi etc…)




Constraints:
Once user formally fills out a profile, then he/she is known as a registered user




1.4.2.2         Use-Case Scenario: Book a Room
Actors
        Registered Users
        Travel Agents


Conditions
        Users must be registered in the system
        Users must have already check the availability of vacancies


Use-Case Description:
For the user/travel agent to book a vacancy, they need a user login, and a current profile
within the system.



                                                                                                     16
      Users provide their login ID and a valid password
      Users choose their time of arrival/check in (after checking their availability of
       vacancies)
      Users choose their preferences:
           o King size bed, double zse beds
           o Occupancy preferences
           o Number of travelers
      Users enter additional passenger details
           o If shipping address and billing address is different
           o Users special requests (ie extra pillows
           o Users enter their credit card information to confirm booking


1. A page with confirmation will appear, and a confirmation email will be sent to the users.


Alternative Options
      If login ID is not valid, system will return an error message.
      If user password is not valid, system will return an error message
      If user has not filled in all mandatory fields, the system will require the user to refill
       the errant fields.


Constraints:
Users may only pay by credit card.




1.4.2.3 Use-Case Scenario: Modify Reservation


Actors:
      Registered Users
      Travel Agents




                                                                                                17
Conditions:
Registered Users and Travel Agents have the ability and option to modify a current existing
reservation within the lodging system.


Description
Users are able to change the date of reservation and cancel bookings online.


        Users log in
            o Enter login ID and password
        Users may choose to cancel or modify reservation (within a certain time frame
         without penalty)
        If users choose cancel, the reservation record will be deleted.
        If users choose “modify”, users may only change the arrival date or check in time.
            o Modification of room size, date, and check in time
            o Modification of occupancy, and number and type of traveler


Constraints:
none



1.4.2.4         Use-Case Scenario: View Profile
Actors
        Registered Users (Home and Business)
        Travel Agents
        Personnel (Security, and Government)


Conditions:


Registered users can access their profiles (only registered). Similar access will be given to
government personnel working for (embassies, state departments etc…) and security
personnel who utilize travel profiles to insure the safety of individuals as they travel.



                                                                                                18
Use Case Description:
      Personnel and Travel Agents can access the system to view customer profiles for
       specific reasons
      Personnel have the ability to search/view profiles


1. Personnel must choose the option of searching profiles, and then enter the following
required flight information:
      Can search by entering user name, address, ss# etc… (personal info)
      Can search by entering, arrival check in time
      Can search by specific locations (and/or countries)


2. The system will respond by returning a list of possible profiles matching all
available/possible search records.
      The results return will include the name, customer ID#, history of lodging record, and
       duration of stay


Alternative Options:
                         If the user has left out information the system will return an error
                          message outlining what information is to be entered.
                         If the user has left out information but the system can return a
                          profile, then the system will return all possible profile matches.
                         If a profile matching the search query is not available, and there are
                          no system matches, the system will return an error message saying a
                          profile is not available.
Constraints:
None




                                                                                                 19
1.4.2.5         Use-Case Scenario: View Profile


Actors


        Hotel Database Administrator


Conditions:


Hotel Database Administrators are there to maintain the database. Although they will
technically have access to all functionalities available for all users, the database
administrator’s role is to maintain information so that it is up and running 24 hrs a day, 7
days a week. Thus his “technical” role is just to maintain data, and nothing else.


Use Case Description:
        Hotel Database Administrator can add, delete, search, and query any valid data entry
        Hotel Database Administrator can delete profiles, and registered users.
        Hotel Database Administrator can modify user names and information.




1. Airline Database Administrator must login with a special ID allocated under his name.
Users provide their login ID and a valid password
        Airline Database Administrator logs in.


Alternative Options
        If login ID is not valid, system will return an error message.
        If Airline Database Administrator password is not valid, system will return an error
         message
        Airline Database Administrator has access to master default login/password
Constraints:
None



                                                                                                20
                               Figure 1.4.3: Flights Use-Case Diagram



1.4.3 Cars


1.4.3.1         Use-Case Scenario: Search Car Availability
Actors
        Guest Users
        Registered Users (Home and Business)
        Travel Agents


Conditions
        Users must have Internet connection(s).
        Users must have general knowledge of surfing the internet.



                                                                        21
      Users must know the URL of the website


Use Case Description:
      Users of the system, including registered/non-registered users are able to create
       profiles, search car rental companies for availability of rental car, to modify
       reservations, to edit profiles, and to view profiles.
      Travel Agents have the same ability as registered users.
      The user and travel agent will have the same interface with regards to all scenarios.


1. User must choose the option of searching car rental companies for vacancies, and then
enter the following required information:
          User enters their arrival location and preferred pickup time
          User has the option of choosing a specific date range and time, or to search all car
           rental availabilities
          User has the option of choosing the number of cars needed, type of car needed,
           make/model, year etc..
          User has the option of searching by specific Car rental company


2. The system will respond by returning a list of possible car availabilities within each
company, in the order of lowest price vacancy to highest car availability.
      The results return will include the car type, price, pickup time (time car will be ready
       to pickup) , time and date car must be returned, and the duration of keep.




Alternative Options:
                        If the user has left out specified search query information, the system
                         will return an error message outlining what information is to be
                         entered.




                                                                                               22
                         If the time of pickup is too close to the current time, the system will
                          return an error message saying it is too close to the time of pickup to
                          find a car.
                         If the car availability within a specified company is not available, the
                          system will return an error message saying the car is not available on
                          that day.


3. Users will then get the option to either create a profile, or to log in to an existing profile.
            Users will be able to modify/view his profile
            Users will be able to modify their current reservation (after user is validated
             through login)
            Users can then specify their preferences (i.e. car make, model, type, color, year…)




Constraints:
Once user formally fills out a profile, then he/she is known as a registered user




1.4.3.2         Use-Case Scenario: Rent a Car
Actors
        Registered Users
        Travel Agents




Conditions
        Users must be registered in the system
        Users must have already check the availability of cars within the system




                                                                                                     23
Use-Case Description:
For the user/travel agent to rent a car, they need a user login, and a current profile within the
system.
      Users provide their login ID and a valid password
      Users choose their time of pickup (after checking their availability of vacancies), and
       time of return
      Users choose their preferences:
           o Car make
           o Car model
           o Car type
           o Car color
           o    Year
      Users enter additional passenger details
           o If shipping address and billing address is different
           o Users special requests (i.e. handicap access)
           o Users enter their credit card information to confirm booking


1. A page with confirmation will appear, and a confirmation email will be sent to the users.


Alternative Options
      If login ID is not valid, system will return an error message.
      If user password is not valid, system will return an error message
      If user has not filled in all mandatory fields, the system will require the user to refill
       the errant fields.
Constraints:
Users may only pay by credit card.




                                                                                                24
1.4.3.3         Use-Case Scenario: Modify Reservation


Actors:
        Registered Users
        Travel Agents


Conditions:
Registered Users and Travel Agents have the ability and option to modify a current existing
reservation within the lodging system.


Description
Users are able to change the date of reservation and cancel bookings online.


        Users log in
            o Enter login ID and password
        Users may choose to cancel or modify reservation (within a certain time frame
         without penalty)
        If users choose cancel, the reservation record will be deleted.
        If users choose “modify”, users may only change the pickup time or return time.
            o Modification of car type, date, pickup time etc..




Constraints:
none
1.4.3.4         Use-Case Scenario: View Profile
Actors
        Registered Users (Home and Business)
        Travel Agents
        Personnel (Security, and Government)




                                                                                           25
Conditions:


Registered users can access their profiles (only registered). Similar access will be given to
government personnel working for (embassies, state departments etc…) and security
personnel who utilize travel profiles to insure the safety of individuals as they travel.


Use Case Description:
      Personnel and Travel Agents can access the system to view customer profiles for
       specific reasons
      Personnel have the ability to search/view profiles


1. Personnel must choose the option of searching profiles, and then enter the following
required flight information:
      Can search by entering user name, address, ss# etc… (personal info)
      Can search by entering, pickup drop off time
      Can search by specific locations (and/or countries)


2. The system will respond by returning a list of possible profiles matching all
available/possible search records.
      The results return will include the name, customer ID#, history of lodging record, and
       duration of stay


Alternative Options:
                         If the user has left out information the system will return an error
                          message outlining what information is to be entered.
                         If the user has left out information but the system can return a
                          profile, then the system will return all possible profile matches.
                         If a profile matching the search query is not available, and there are
                          no system matches, the system will return an error message saying a
                          profile is not available.




                                                                                                 26
1.4.3.5          Use-Case Scenario: View Profile
Actors
        Car Rental Database Administrator
Conditions:
Car Rental Database Administrators are there to maintain the database. Although they will
technically have access to all functionalities available for all users, the database
administrator’s role is to maintain information so that it is up and running 24 hrs a day, 7
days a week. Thus his “technical” role is just to maintain data, and nothing else.


Use Case Description:
        Car Rental Database Administrator can add, delete, search, and query any valid data
         entry
        Car Rental Administrator can delete profiles, and registered users.
        Car Rental Administrator can modify user names and information.




1. Car Rental Database Administrator must login with a special ID allocated under his name.
Users provide their login ID and a valid password
        Car Rental Administrator logs in.


Alternative Options
        If login ID is not valid, system will return an error message.
        If Car Rental Database Administrator password is not valid, system will return an
         error message
        Car Rental Administrator has access to master default login/password


Constraints:
None




                                                                                               27
Activity Diagrams




                    28
Conclusion:


This phase required a lot of thinking and analysis but it will go a long way in making this
system. This has provided the group with good exercise into how to model this system and
will be helpful when implementing the system.




                                                                                              29

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:11/26/2011
language:English
pages:29