Motel Recourses Tool


Title: Motel Recourses Tool
Objective:

  The system aims at the maintenance and management of the different accommodations that are available in the different parts of the world. It mainly takes care of the resort management at the core area of the database.
  The system provides the information regarding the different resorts that are available and their status specific to availability.
  The guests can visit the site and register themselves with the required information that is expected by the system. Each registered guest can raise a request for the unit bookings.
  The Guests are scheduled with the information of the availability of the units for they have requested the time.
  The system totally built upon the standards of Three Tier Architecture with Client, Business and Data Tiers associated as separate layers, with specification to high cohesion and loose Coupling Standards for easy maintenance.

Existing system:
Present system is presently is an undeveloped form and the manual process of the overall system is too clumsy and complicated. The clients in the real time consultancy system can be too thick and may need many resources to be used upon the system. If the system is developed, in a distributed over interface with centralized database is the only solution.

Proposed system:
The Automated system with 3-tier architecture can support issues like:
ü  The system maintains the different location that is available and registered in a central DB, which   leads easy accessibility and consistency.
ü  Each Accommodation available units and all the unit facilities are also available at the click of a mouse.
ü  The registration of new guest is online house new guest can make them they convenient for registration process on the basic of 24x7x365days.
ü  The Units can be booked by the registered guest irrespective of the Geographical barriers.
ü  The Guest is provided with up to minute information related to the unit availability and their status. From their convenient place.
The guests have information at their demand related to any unit status of their own unit booking status.

Study of the system:

To provide flexibility to the users, the interfaces have been developed that are accessible through a browser. The GUI’S at the top level have been categorized as
  1. Administrative user interface
  2. The operational or generic user interface

The ‘administrative user interface’ concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. These interfaces help the administrators with all the transactional states like Data insertion, Data deletion and Date updation along with the extensive data search capabilities.

The ‘operational or generic user interface’ helps the end users of the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information in a customized manner as per the included flexibilities.

Feasibility Study:

Feasibility Report:

Preliminary investigation examines project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All systems are feasible if they are given unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:
  • Technical Feasibility
  • Operation Feasibility
  • Economical Feasibility




Technical Feasibility:
The technical issue usually raised during the feasibility stage of the investigation includes the following:
  • Does the necessary technology exist to do what is suggested?
  • Do the proposed equipments have the technical capacity to hold the data required to use the new system?
  • Will the proposed system provide adequate response to inquiries, regardless of the number or location of users?
  • Can the system be upgraded if developed?
  • Are there technical guarantees of accuracy, reliability, ease of access and data security?


Operational Feasibility:
Proposed projects are beneficial only if they can be turned out into information systems, which will meet the organization’s operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: -
·       Is there sufficient support for the management from the users?
·       Will the system be used and work properly if it is being developed and implemented?
·       Will there be any resistance from the user that will undermine the possible application benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.

Economic Feasibility:
A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is economically feasible. It does not require any additional hardware or software. 

Functional Requirements:


Modules:
The system is proposed to have the following modules:
1. Accommodation Information Module
2. Units Information Module.
3. Bookings Information Module.
4. Guests Information Module.
5. Facilities Information Module.

1. ACCOMMODATION INFORMATION: This module maintains all the details of the Accommodation location that are available and the units that are available under each location along with their reference unit types.
2. UNITS INFORMATION: This module maintains the information regarding all the units that are registered as per specifications and their reference unit types. The module also takes care of the system from the unit facilities and reference unit facilities that are available.
3. BOOKING MODULE: This module maintains the information of all the booking of the units, as pet the guest requirements, it interpolate itself with the units station database and the specific registered guest who have raised the demand upon the booking.
4. GUEST MODULE: This module maintains the overall activities through which a guest is uniquely registered is the domain the module interpreter with the specific gender status and also centrally sets with interpretation through booking and registry to unit status.
5. FACILITIES MODULE: This module maintains the overall activities in the facilities that are available are provided for all or some of the specified units. This module helps in registering the reference unit facilities that may creep in into the system from time to time.
NUMBER OF VIEWS:
Administrative View
Guest View
Administrative View
This view is designed for interacting with the absolute Meta Data, which becomes the ultimate repository to maintain the consistency.
This view is accessible only to registered administrators who are recognized by the Watershed Development central Administration Department.
Guest View
 In this view the guest can view complete details of available accommodation list information

Non-Functional Requirements:

Software requirements:

•            Web Presentation                     :       HTML, CSS
•            Client – side Scripting              :       JavaScript
•            Programming Language           :       Java
•            Web based Technologies           :       Servlets, JSP
•            Database Connectivity              :       JDBC
•            Java Version                            :       JDK1.5
•            Backend Database                    :       Oracle 9i
•            Operating System                    :       Windows XP/LINUX
•            Web Server                             :       Tomcat 5.5
•            Browser                                           :       IE/Mozilla
                 

Hardware requirements:

·       Pentium processor        :       233 MHZ
·       RAM Capacity               :       128MB
·       Hard Disk                     :       20GB
·       CD-ROM Drive              :       32 HZ
·       Keyboard                    :       108 Standard
·       Mouse                          :       Optical
·       Monitor                        :       15’’ Color Monitor