| Description : |
The system aims at the maintenance and management of the different Hotels that are available in the different parts of the world. It mainly takes care of the Hotel management at the core area of the database. The system provides the information regarding the different Hotels that are available and their status specific to availability. The database also manages the atomic information regarding the different units that are available under one Hotel and the architectural details of the Unit facilities that are available. Each unit is well furnished and is well designed for the basic flexibility of the tourists who are expected to stay. 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 Units maintenance is automated for proper management of the availability status of the units or the scheduled expected date of their availability in near future. The system provides the facility for booking of the required available units as per the number that is available.
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.
The entire project has been develped keeping in view of the Distributed client server computing technology in mind.The specification have been normalized upto 3NF to eliminate all the anomalies that may arise due to the database transactions that are executed by the actual administration and users.The user interfaces are browser specific to give distributed accessability for the overall system.The internal database has beeb selected as Oracle 8i.The basic constructs of the tablespaces, clusters and indexes have been exploited to provide higher consistency and reliability for the data storage.The oracle 9i was a choice as it provides the constructs of high level reliabiity and security.The total front end was dominated using HTML standards applied with the dynamism of JAVA server pages. Thecommunicatin client was designed using servlets and JSP’s. At all proper levels high care was taken to check that the system manages the date consistency with proper business validations.The database connectivity was planned using the Java DataBase Connectivity,the authorization and authorization was cross checked at all stages.The user level accessabiity has been restricted into two zones the administrative and the normal user zone.
The Bean components have been implemented for proper reusability and authenticity. The standards of security and date portative mechanism have been given a big choice for proper usage. The application takes care of different modules and their associated reports which re produced as per the applicable strategies and standards that are put forwarded by the administrative staff..
The entire project has been develped keeping in view of the Distributed client server computing technology in mind.The specification have been normalized upto 3NF to eliminate all the anomalies that may arise due to the database transactions that are executed by the actual administration and users.The user interfaces are browser specific to give distributed accessability for the overall system.The internal database has beeb selected as Oracle 8i.The basic constructs of the tablespaces,clusters and ridexes have been exploited to provide higher consistency and reliability for the data storage.The oracle 8i was a choice as it provides the constructs of high level reliabiity and security.The total front end was dominated using HTML standards applied with the dynamism of JAVA server pages. Thecommunicatin client was designed using servlets. At all proper levels high care was taken to check that the system manages the date consistency with proper business validations.The database connectivity was planned using the Java DataBase Connectivity,the authorization and authorization was cross checked at all stages.The user level accessabiity has been restricted into two zones the administrative and the normal user zone.
System Analysis Concentration:
Before planning a replacing for a new system it is essential to have through knowledge about the existing system along with estimation of how lost computes can be used to make its operations more effective.
System analysis is the process of collecting and interpreting facts, disposing problem and use the information about the existing system, which is also called as system study.
System analysis is about understanding situation but not solving the problem.
System analysis is performed to determine whether a not it is feasible to design and information system laved on the policies and plans of an organization. To determine the user requirements and to eliminate the weakness of the present system a few general requirements are concerned.
GENERAL REQUIREMENTS:
The new system should be cost effective
To improve productivity and service and service.
To enhance user interface.
To improve information presentation and durability.
To upgrade systems reliability, availability and flexibility.
To address human factors for better and uses acceptance.
PROBLEM IN THE CURRENT SYSTEM:
The 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.
Feasibility ReportTECHINICAL FEASIBILITY:
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point in time, not too many detailed design of the system, making it difficult to access issues like performance, costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technical analysis.
Understand the different technologies involved in the proposed system:
Before commencing the project, we have to be very clear about what are the technologies that are to be required for the development of the new system.
Find out whether the organization currently possesses the required technologies:
Is the required technology available with the organization?
If so is the capacity sufficient?
OPERATIONAL FEASIBILITY:
Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project:
Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.
Are the current business methods acceptable to the user? If they are not, Users may welcome a change that will bring about a more operational and useful systems.
Have the user been involved in the planning and development of the project? Early involvement reduces the chances of resistance to the system and in General and increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible.
ECONOMIC FEASIBILITY:
Economic feasibility attempts 2 weigh the costs of developing and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system.
A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of reference to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of information, better employee morale.
a) Technical Description
Databases: The total number of databases that were identified to build the system is 10.The major part of the Databases is categorized as Administrative components and the user components. The administrative components are useful is managing the actual master data that may; be necessary to maintain the consistency of the system. The administrative databases are purely used for the internal organizational needs and necessities. The user components are designed to handle the transactional state that arise upon the system whenever the general client makes a visit onto the system for the sake of the report based information. The user components are scheduled to accept parametrical information for the user as per the systems necessity.
GUI’s
For the flexibility of the user, the interface has been developed in graphical user interface mode. The normal interface is applied through browser.
The GUI’s at the top level has been categorized as:
1) Administrative user interface.
2) Customer or general user interface.
The administrative user interface concentrates on the consistent information that is practically, pact of the organizational activities and which needs proper authentication for the data collection. The interfaces help the visitors with all the transactional states like Data insertion, Data deletion and Data updating with the data search capabilities. The general user interface helps the users upon the system in transactions through the required services that are provided upon the system. The general user interface also helps the ordinary user is managing their own information in a customized manner as per their flexibilities.
Feasibility
(i) Technical Feasibility
The system is self-explanatory and does not need any entire sophisticated training. The system has been built by concentrating on the graphical user interface concepts; the application can also be handled very easily with a novice user. The overall time that a user needs to get trained is less than 15 minutes.
The system has been added with features of menu driven and button interaction methods, which makes him the master as he starts working through the environment. As the software that was used for developing this application are very economical and are readily available is the market the only time that is lost by the customer is just installation time.
Time Based:
In this world of busy schedule with which the industrial professionals are getting through this kind of system is a boon for the kind of information they can readily access at the tip of their fingers. The Tourist, who intends to make a visit to the specific choice of his place, need not enquire about the details taking the entire pin physically. The Tourist can just get himself connected to the site at his own desk with the respective URL that has been allocated for him and can make a wide variety of choices for the accommodations that are available in the central repository of the existing database. The User can have the information of all the units that are practically registered along with the facilities that are available with respect to every unit. The guest is given free hands to register his information as per the practical requirements of the site, such that he can be tracked and provided services at the demand that is raised by him.
The Guest once registered can make multiple visits upon the site as per his requirements and enquire for the units availability and the status of his previous bookings, if any.
The Administrators can make easy accessibility of the system from virtually anywhere in this world, which facilitates the scope of global or remote administration possible. All the consistent transactions are facilitated by the administrators only with proper authorization and authentication.
Cost Based:
If the physical system is established through a manual process. There is much need of stationary that has to be managed and maintained as files, the overall system once implemented as a intranet based web application not only saves the time but also eliminates the latency that can exist within the system, and saves the cost of stationary that is an unforeseen overhead within the system.
The base administrative staff at the level of the strategic decision-making is greatly relieved for the extensive data search. The administrators are greatly benefited by this system, as they need not collect all that information that is accessible by only selects that information which is more important for them. The administrative standards of the system become more economical as there is no need of stationary exchange within the organization. As the information governed upon the system maintains statistics related to information that is collected, the overall system can be used for forecasting analysis in the research process.
In the manual process of the Web Based Accommodation Upholding and Maintenance System, the information search and storage needs extra manpower assignment, which potentially costs the organization in the perennial investment of funds for the sake of the salaries. The information interrelations among different areas of the system should be handled carefully else the latency upon the overall process of the system increases leading to inconvenience.
SOFTWARE REQUIREMENT SPECIFICATION REQUIREMENT SPECIFICATION:
The software, Web Based Accommodation upholding Maintenance System, which is designed for administrating & automating all the major activities that are carried out by the Tourists and the Accommodation providing outlets as specific requirements arise upon the system.
INTRODUCTION
Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system.
Scope: This Document plays a vital role in the development life cycle (SDLC) As it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
Developers Responsibilities Overview:
The developer is responsible for:
Developing the system, which meets the SRS and solving all the requirements of the system?
Demonstrating the system and installing the system at client's location after the acceptance testing is successful.
Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.
Conducting any user training that might be needed for using the system.
Maintaining the system for a period of one year after installation.
Functional Requirements
Inputs: The major inputs for Integration of Web based Accommodation Upholding Maintenance System can be categorized module -wise. Basically all the information is managed by the software and in order to access the information one has to produce one's identity by entering the user-id and password. Every user has their own domain of access beyond which the access is dynamically refrained rather denied.
Output: The major outputs of the system are tables and reports. Tables are created dynamically to meet the requirements on demand. Reports, as it is obvious, carry the gist of the whole information that flows across the institution.
This application must be able to produce output at different modules for different inputs.
Performance Requirements:
Performance is measured in terms of reports generated weekly and monthly.
Intended Audience And Reading Suggestions
The document is prepared keeping is view of the academic constructs of my Bachelors Degree / Masters Degree from university as partial fulfillment of my academic purpose the document specifies the general procedure that that has been followed by me, while the system was studied and developed. The general document was provided by the industry as a reference guide to understand my responsibilities in developing the system, with respect to the requirements that have been pin pointed to get the exact structure of the system as stated by the actual client.
The system as stated by my project leader the actual standards of the specification were desired by conducting a series of interviews and questionnaires. The collected information was organized to form the specification document and then was modeled to suite the standards of the system as intended.
Document Conventions:
The overall documents for this project use the recognized modeling standards at the software industries level.
ER-Modeling to concentrate on the relational states existing upon the system with respect to Cardinality.
The Physical dispense, which state the overall data search for the relational key whereas a transactions is implemented on the wear entities. Unified modeling language concepts to give a generalized blue print for the overall system.
The standards of flow charts at the required states that are the functionality of the operations need more concentration.
|
