Docstoc

Vision

Document Sample
Vision Powered By Docstoc
					              Airline Reservation System (ARS)




Vision

Version 2.1
               Airline Reservation System (ARS)            Version:     4
Vision                                                     Date: 1/1/2011
Vision.VIS




                                      Revision History

Date         Revision   Description                      Author
1/11/2010    1.0        Initial Version                  Mohammed & Abdulaziz
                    Airline Reservation System (ARS)            Version:     4
Vision                                                          Date: 1/1/2011
Vision.VIS

                                            Table of Contents


1.   Introduction                                                                1
     1.1     Purpose of the Vision Document                                      1
     1.2     Product Overview                                                    1

2.   User Description                                                            1
     2.1     User/Market Demographics                                            1
     2.2     User Profiles                                                       1
     2.3     Users Environment                                                   2

3.   Product Overview                                                            2
     3.1     Problem Statement / Business Opportunity                            2
     3.2     Product Perspective                                                 2
     3.3     Product Position Statement                                          2

4.   Product Features                                                            2
     4.1     System Functionality :                                              2
     4.2     Employee Functionality :                                            2
     4.3     Administrator Functionality:                                        2
     4.4     Customer Functionality:                                             3
                Airline Reservation System (ARS)                           Version:       4
Vision                                                                     Date: 1/1/2011
Vision.VIS


1.     Introduction
1.1    Purpose of the Vision Document
       The purpose of this document is to define the problem addressed by the Airline reservation
       system and to define high-level business requirements, user needs, and features for that system.
       This document also helps us to collect and analyse the ideas gathered for the project. This vision
       document will be subject to change, if more requirements are added to the project.
       This system is an application available on the World Wide Web, so we will use web development
       technologies and it will be interesting to learn these technologies.


1.2    Product Overview
       The goal of the project is to develop Airline Reservation System that provide reservation service
       and can be used by staff and customers. This helps the customers to search the availability and
       prices of various airline tickets. This project also covers various features like online registration
       of the users, modifying the details of the website by the administrator of the website, by adding,
       deleting or modifying the customer details, flights or packages information. This project has the
       special features that might distinguish it from other projects, the administrator can schedule the
       pilot and crew on flight , It will complex functions but will be done.

       In general, this website would be designed to perform like any other airline ticketing website
       available online.

2.     User Description
2.1    User/Market Demographics
       We can divide target users into two categories: expert (employee) and normal (customer).
       The first category must take intensive training on how to use and the difficulties that may be
       encounter him.
       The second category want easy interact with system, so steps should be orderly and the necessary
       instructions is ready.
2.2    User Profiles
       Customer — Anyone who register in the system and can use the functions of system. Before that,
       he must provide his personal information and credit card to pay his fees.
       Employee — Anyone who has permission to access to system and use certain functions. Before
       that, he must provide his personal information.
       Administrator — Someone who has permission to access to system and use certain functions.
       These functions like add group, cancel flight and manage it.
       User --- Anyone who can use system. It includes customer, employee and administrator.
       Staff --- Anyone who has membership in the company. It includes employee and administrator.




                                                   ARS
                  Airline Reservation System (ARS)                          Version:       4
Vision                                                                      Date: 1/1/2011
Vision.VIS

2.3       Users Environment
          This system is web-based system site that allows users to use their functions over the Internet.
3.        Product Overview
3.1       Problem Statement / Business Opportunity
          Rapid growth of the Internet make us think about building a system to provide services to trider
          as well as improving the level of services provided to them.
          The bank feels the need to improve services that provided to user because that will lead to
          increase the proportion of user and increase users` satisfaction.
3.2       Product Perspective
          This system will work with the most common Web browsers like Microsoft Internet Explorer and
          Firefox and Google chrome.
3.3      Product Position Statement
The Foreign Exchange Management System (FXMS) will allow users to have easy using of their functions in
the system.
4.        Product Features
          The functions of the product can be categorized under three categories that are for system,
          trader, employee and administrator.
          [Note: The use case diagram and use case template will be in independent document in appendix]
4.1       System Functionality :
      -   Check late payment: The system will check automatically at the deadline of each flight if
          customer pays his fees or not, if he does not pay it the system will send message (SMS) to
          remember him, and after 24 hour will do cancellation for his booking.
4.2       Employee Functionality :
      -   Login: Employee should use their Staff ID as a username and a password in order to log into the
          system and use its functionalities.
      -   Search : Employee can make search by different criteria: flights, booking number, passengers’
          name, time, date...etc.
      -   Booking : The Employee can also search for the flights available and book the place of the
          customer on the flight by selling a ticket.
      -   Cancel booking : If the customer has booking and he want to cancel his booking, the employee
          can cancel it.
      -   Modify booking : employee can modify booking for the customer if he has booking.
      -   Payment : Employee can make payment for the customer if the customer has booking.
      -   Check payment : Employee can check if customer pays his fees or not before do double payment
          or book place.
      -   Print boarding : Administrator can print boarding for customer before 24 hours of his flight.


4.3       Administrator Functionality:
      -   Login: Administrator should use their Staff ID as a username and a password in order to log into
          the system and use its functionalities.
      -   Search : Administrator can make search by different criteria: flights, booking number,

                                                     ARS
                   Airline Reservation System (ARS)                        Version:      4
Vision                                                                     Date: 1/1/2011
Vision.VIS

          passengers’ name, time, date...etc.
      -   Booking : The Administrator can also search for the flights available and book the place of the
          customer on the flight by selling a ticket.
      -   Cancel booking : If the customer has booking and he want to cancel his booking, the
          Administrator can cancel it.
      -   Modify booking: employee can modify booking for the customer if he has booking.
      -   Payment: Administrator can make payment for the customer if the customer has booking.
      -   Check payment: Administrator can check if customer pays his fees or not before do double
          payment or book place .
      -   Print boarding : Administrator can print boarding for customer before 24 hours of his flight.
      -   Schedule pilot and crew: Administrator can do scheduling of pilot and crew on the flight and
          airplanes.
      -   Manage flight: Administrator can add, cancel and modify the flight.
      -   Manage employee: Administrator can add, cancel and modify the employee. This for privilege to
          using the system not for the company.
4.4       Customer Functionality:
      -   Login: Customer should use their Staff ID as a username and a password in order to log into the
          system and use its functionalities.
      -   Search : Customer can make search by different criteria: flights, booking number, passengers’
          name, time, date...etc.
      -   Booking : The Customer can also search for the flights available and book the place on the flight
          by purchasing a ticket.
      -   Cancel booking : If the customer has booking and he want to cancel his booking, the employee
          can cancel it.
      -   Modify booking : Customer can modify information of his booking like time, date and
          degree..etc.
      -   Payment : Customer can pay his fees if he has booking.
      -   Check payment : Customer can check if he pays his fees or not before do double payment or
          book place.
      -   Print boarding : Customer can print boarding before 24 hours of his flight.



5         Nonfunctional requirements:
      -   Security:
          The system contains confidential data about users. Each customer can see only his own
          data.
      -   Speed:
          The system should support multiple users connecting at the same time. In rush periods, it
          is possible to have several hundreds of users connecting to the system from different
          places at the same time.
      -   Easy to use:
          The system should be easy to use and the steps must be orderly to make reservation easy.




                                                    ARS
             Airline Reservation System (ARS)   Version:     4
Vision                                          Date: 1/1/2011
Vision.VIS

5.     Use case diagram




                                          ARS
                Airline Reservation System (ARS)             Version:     4
Vision                                                       Date: 1/1/2011
Vision.VIS

5.1.1 Use case Specification

5.1.1.1 Login


       - Brief Description
       This use case describes how a user logs into the Airline Reservation System.

       - Flow of Events

                - Basic Flow
       This use case starts when the actor wishes to log into the Airline reservation
       system.
   1- The system requires the username and password of the actor.
   2- The actor enters his/her name and password.
   3- The system validates entered name and password and logs the actor into
      system.
              - Alternative Flows
              < First Alternative Flow >
       If the actor entered invalid username and password, system will display an
       error message. The actor can choose to either return to the beginning of the
       Basic Flow or cancel the login.
       - Special Requirements
              None.

       - Preconditions
             None.

       - Post Conditions
       < Post condition One >
       If the use case was successful, the actor is logged into the system. If not, the
       system state is unchanged.

       - Extension Points
             None.




                                             ARS
               Airline Reservation System (ARS)            Version:     4
Vision                                                     Date: 1/1/2011
Vision.VIS

5.1.1.2 Schedule pilots and crew

       - Brief description
       This use case allows administrator to schedules the pilots and crew on the
       flights

       - Flow of Events
             - Basic Flow
       1. This use case starts when the actor wishes to schedules the pilots and crew
       on the flights.
       2. The actor requires the schedule pilot and crew.
       The system will implement scheduling algorithm.

       - Special Requirements
              None.
       - Preconditions
              The A must be logged onto the system before this use case begins.
       - Post condition
       If the use case was successful, the new information will saved in database. If
       not, the database state is unchanged.

       - Extension Points
             None.




                                            ARS
             Airline Reservation System (ARS)             Version:     4
Vision                                                    Date: 1/1/2011
Vision.VIS

5.1.1.3 Employee management


       - Brief description
       This use case allows the admin to manage employee information in the
       Airline reservation system and ticketing system. This includes adding,
       modifying, and deleting employee from the system.
        - Flow of Events
              -Basic flows
       This use case starts when the admin wishes to add, update , and/or delete
       employee information in the system.
       1. The system requests that the admin specify the function he/she would like
       to perform (either add an employee, Update an employee, or Delete an
       employee)
       2. Once the admin provides the requested information, one of the sub flows
       is executed. If the admin selected “Add an employee”, the Add an employee
       sub flow is executed. If the admin selected “modify an employee”, the
       update an employee sub flow is executed. If the admin selected “Delete an
       employee”, the Delete an employee sub flow is executed.

        Add an employee
       The system requests that the admin enter the employee information. This
       includes:
       - Name
       -Date of birth
        - National number

       1- Once the admin provides the requested information, the system generates
       and assigns a unique id number to the employee. The employee is added to
       the system.

       2- The system provides the admin with the new employee id.
       Update an employee
       1-The system requests that the admin enter the employee id.
       2-The admin enters the employee id. The system retrieves and displays the
       employee information.


                                          ARS
             Airline Reservation System (ARS)             Version:     4
Vision                                                    Date: 1/1/2011
Vision.VIS

       3-The admin makes the desired changes to the employee information. This
       includes any of the information specified in the Add an employee sub-flow.
       4-Once the admin updates the necessary information, the system updates the
       employee record.


       Deleting an employee
       1. The system requests that the admin enter the employee id
       2. The admin enters the employee id. The system retrieves and displays the
       employee information.
       3. The system prompts the admin to confirm the deletion of the employee.
       4. The admin verifies the deletion.
       5. The system deletes the employee from the system.

       Alternative flows

        The employee Not Found
       If, in the Update an employee or Delete an employee sub-flows, employee
       with the specified id number does not exist, the system displays an error
       message. The admin can then enter a different id number or cancel the
       operation, at which point the use case ends.
        Delete Cancelled
       If, in the Delete an employee sub-flow, the admin decides not to delete the
       employee, the delete is cancelled, and the Basic Flow is re-started at the
       beginning.

       - Special Requirements
              None.
       - Pre-Conditions
              The admin must be logged onto the system before this use case
       begins.
       - Post-Conditions
       If the use case was successful, the employee information is added, updated,
       or deleted from the system. Otherwise, the system state is unchanged.

       - Extension Points
             None.


                                          ARS

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:20
posted:5/8/2011
language:English
pages:11