Research And Implementation Of Chain Hotel Room Management System Based On SSH

Nowadays, due to the more and more increasingly fierce competition in the hotelindustry and the goals of sharing the resource of customers, strengthening the brand’srelevance, attracting more customers and reducing the business risk, many small ormedium-sized hotels, whose managements are usually decentralized, tend to create or join in achain hotel management group, such as decorated with the same style, managed in a unifiedmode, and then manage their rooms by chain mode. Meanwhile, as a branch, every hotel canalso keep their independent to some extent yet, especially in the condition that one branchcan’t connect to the headquarters. At the moment, the hotel must work normally. After itconnects the headquarters smoothly, the operator in the branch sends the command ofsynchronization, and then the task is finished by the system. For this reason, there is importsocial and economic value to develop a room management system for the small and mediumscale chain hotel, whose every branch can work independently.After analyzing and comparing the merits and demerits of technique platform, functionalarchitecture and work flow, used to develop room management for a single hotel by domesticdevelopers, then discussing with related personnel and combining some experience of stayingat hotels in person, this paper sets the chain hotel room management system’s functionalrequirements, critical business processes and functional architecture and then design itsdatabase. Develop a chain hotel room management system in the integrated developmentenvironment of MyEclipse2014, combining Struts2, Spring Framework and Hibernate, thethree currently popular and famous open source frameworks in the platform of Java EE, andusing MS SQL Server2012and Tomcat7as its database and web server separately. ClearMVC layered architecture, loose coupling in the level of program, good reusability, highefficiency and good maintainability are its characteristics.On the whole, the system consists of two sub systems including headquarters and branch.They have their own databases. Take a chain hotel with N branches for example, N databasesin branch with the same relation schema and one in headquarters are needed. In general, everysubsystem program and its database should be installed in the same host to reduce theunnecessary community and improve response speed. When one branch fails to connect theheadquarters, it becomes a single version system automatically and works normally all thesame. By this way, avoid the branch subsystem’s pure dependency on external network andmake the two subsystems run independently.There are four user types for the branch subsystem, including its administrator, receptionist and cashier in its front desk and financial staff. These four roles feature clearresponsibility, reasonable division and balance load. The headquarters subsystem has two usertypes, including its administrator and the members of the chain hotel. Only the role ofmembers doesn’t need to login and use their interface directly to query the detail informationabout increasing or consuming their credits. The role of receptionist can know the branch canconnect the headquarters or not and there is necessity to be synchronized or not. If necessary,what he needs only to do is to click the hyperlink and the synchronization is executed by thesystem.Finally, the tests show that the system features rapid response, simple operation, conciseand direct cue words, friendly interface, stable operation. Meanwhile, the branch subsystem isinsensitive to the network with the headquarters. It realizes that the rooms of the chain hotel’sbranches can be executed normalization management at lower cost in every typical segment.