1.1 Background Information
A hotel is an establishment that provides lodging paid on a short-term basis. The provision of basic accommodation, in times past, consisting only of a room with a bed, a cupboard, a small table and a washstand has largely been replaced by rooms with modern facilities For the purpose of this work a guest house is (also guesthouse) is a kind of lodging. In some parts of the world a guest house is similar to a hostel, bed and breakfast, or inn whereas in other parts of the world (such as for example the Caribbean), guest houses are a type of inexpensive hotel-like lodging and a hotel is a commercial establishment providing lodging, meals, and other guest services, both of which can be used interchangeably
For this Project I would be using The Covenant University Guest House as my case study The Covenant University Guest house has 80 rooms which are divided into three categories; Executive deluxe rooms, mini suits and standard rooms. All rooms have intercoms, internet services and satellite television, it has a standard restaurant serving continental and national dishes,24hours room service, a mini mart, a gymnasium, laundry service with modern dry cleaning equipment, 3 large halls for exhibitions and conferences and a large secure cark park The Covenant University Guest house has 5 departments namely: 1. Housekeeping department 2. Laundry department 3. F&B(Food and Beverage) department 4. Accounting department 5. Front office department
Front office is a business term that refers to a company's departments that come in contact with clients, including the marketing, sales, and service departments
In the hotel industry, the front office welcomes guests to the accommodation section: meeting and greeting them, taking and organizing reservations, allocating check in and out of rooms, organizing porter service, issuing keys and other security arrangements, passing on messages to customers and settling the accounts.
At the Covenant University Guest house the 2 major functions of the front office are communication and accounting. The front office consists of the receptionist, porters and the head of the department among other staff. The department handles a number of operations categorized into guest management (reservation, registration, occupancy services, checkout and history) and guest accounting (establishment of credit, posting charges, night auditing and settlement of accounts) this project will focus mainly on room management, guest management and reservation
1.2 Statement of the Problem
According to Frederick W. Daily, one of the initial decision to be made is how the records of the company are to be managed and kept accurately to ensure the success of the business (choosing the right business record-keeping system, n.d., para1). In the Covenant University Guest house, client information, registration, room details, billing records are all kept and managed manually.
This type of record keeping leads to high rise in paper work which then leads to slow data exchange, scattered client data and difficulty in data storage and retrieval hence making the system time consuming [1].
1.3 Significance of project
The main purpose of this work is to reduce data duplication and data inaccuracy, hence reducing the paper work, minimal redundancy and increase in speed and ease of access to information * It also demonstrates how information technology can be used to improve performance levels of employees * It also validates the debate supporting E-reocord-keeping of manual record-keeping.
1.4 Aim
The aim of the project is to design and develop a web-based data management system for hotels and guest houses to solve the setbacks of data access difficulties, duplicated information and data insecurity that many face today due to manual data collation. This will result in reduced paper files and easy access to useful information by automating the client services, postings of charges and settlement of account process by them.
1.5 Methodology
My primary data sources are the administrative and technical staff at the Covenant University Guest house
The software development model use the waterfall model with feedback, this allows for partitioning and control of different phases
The system consists of a web application written in php hosted on an apache http server for the hotel reservation model and gust interface with the system, with msql adopted as the relational management system
The development moves from conception through to design, implementation, testing, setting up, troubleshooting and ends up at implementation and maintenance, with each phase acting as a milestone and advancing in strict order without any overlap or reapting steps(sven el al.,2009)
1.6 Thesis Organization
This report is made up of five chapters. In this section a brief description of each chapter is given below:
Chapter One: Chapter One contains the general background information of the project, the statement of the problem as related to the project, the motivation behind and significance, the aims and objective, the methodology that will be used in developing the project successfully.
Chapter Two: in this chapter existing literatures where reviewed, to see the previous works that had been done and make comparisms between previous system and show the advancements in my system.
Chapter Three: This chapter depicts an overview of system analysis and design. It contains different drawings that give a graphical picture of the system.
Chapter Four: This describes the implementation of the system. i.e. the technology employed in developing the system, the programming language chosen to develop the system, the database type chosen, the system requirement and testing of the system.
Chapter Five: This is chapter is the concluding chapter of the project. It gives a brief summary of what has been presented in the previous chapters. Also, it mentions the achievements of the thesis and finally ends with recommendations for further investigations.
CHAPTER TWO
LITERATURE REVIEW
2.1 Introduction
Hotels
A hotel is an establishment that provides lodging paid on a short-term basis. The provision of basic accommodation, in times past, consisting only of a room with a bed, a cupboard, a small table and a washstand has largely been replaced by rooms with modern facilities, including en-suite bathrooms and air conditioning or climate control. Additional common features found in hotel rooms are a telephone, an alarm clock, a television, a safe, a mini-bar with snack foods and drinks, and facilities for making tea and coffee. Luxury features include bathrobes and slippers, a pillow menu, twin-sink vanities, and jacuzzi bathtubs. Larger hotels may provide additional guest facilities such as a swimming pool, fitness center, business center, childcare, conference facilities and social function services. The word hotel is derived from the French hôtel (coming from hôte meaning host), which referred to a French version of a townhouse or any other building seeing frequent visitors, rather than a place offering accommodation
Hotel management is a globally accepted career field and academic field of study. Degree programs such as hospitality management studies, a business degree, and/or certification programs formally prepare hotel managers for industry practice.
Most hotel establishments consist of a General Manager who serves as the head executive (often referred to as the "Hotel Manager"), department heads who oversee various departments within the hotel, middle managers, administrative staff, and line-level supervisors. The organizational chart and quantity of job positions varies by hotel size, function, and is often determined by hotel ownership.
2.2 Document management systems
A document management system (DMS) is a computer system used to track and store electronic documents. It is usually capable of keeping track of the different versions modified by different users (history tracking). The term has some overlap with the concepts of content management systems. It is often viewed as a component of enterprise content management (ECM) systems and related to digital asset management, document imaging, workflow systems and records management systems.
2.2.1 History
Beginning in the late 1970s, a number of vendors began developing software systems to manage paper-based documents. These systems dealt with paper documents, which included not only printed and published documents, but also photographs, prints, etc.
Later developers began to write a second type of system which could manage electronic documents, i.e., all those documents, or files, created on computers, and often stored on users' local file-systems. The earliest electronic document management (EDM) systems managed either proprietary file types, or a limited number of file formats. Many of these systems later became known as document imaging systems, because they focused on the capture, storage, indexing and retrieval of image file formats. EDM systems evolved to a point where systems could manage any type of file format that could be stored on the network. The applications grew to encompass electronic documents, collaboration tools, security, workflow, and auditing capabilities.
These systems enabled an organization to capture faxes and forms, to save copies of the documents as images, and to store the image files in the repository for security and quick retrieval (retrieval made possible because the system handled the extraction of the text from the document in the process of capture, and the text-indexer function provided text-retrieval capabilities).
While many EDM systems store documents in their native file format (Microsoft Word or Excel, PDF), some web-based document management systems are beginning to store content in the form of html. These policy management system[2]. require content to be imported into the system. However, once content is imported, the software acts like a search engine so users can find what they are looking for faster. The html format allows for better application of search capabilities such as full-text searching and stemming[3].
2.2.2 Components of a Document management system [4]:
Document management systems commonly provide storage, versioning, metadata, security, as well as indexing and retrieval capabilities
Table 2.2.2 Components of a Document management system Topic | Description | Metadata: | Metadata is typically stored for each document. Metadata may, for example, include the date the document was stored and the identity of the user storing it. The DMS may also extract metadata from the document automatically or prompt the user to add metadata. Some systems also use optical character recognition on scanned images, or perform text extraction on electronic documents. The resulting extracted text can be used to assist users in locating documents by identifying probable keywords or providing for full text search capability, or can be used on its own. Extracted text can also be stored as a component of metadata, stored with the image, or separately as a source for searching document collections. | Integration: | Many document management systems attempt to integrate document management directly into other applications, so that users may retrieve existing documents directly from the document management system repository, make changes, and save the changed document back to the repository as a new version, all without leaving the application. Such integration is commonly available for office suites and e-mail or collaboration/groupware software. Integration often uses open standards such as ODMA, LDAP, WebDAV and SOAP to allow integration with other software and compliance with internal controls. | | | Indexing: | Indexing tracks electronic documents. Indexing may be as simple as keeping track of unique document identifiers; but often it takes a more complex form, providing classification through the documents' metadata or even through word indexes extracted from the documents' contents. Indexing exists mainly to support retrieval. One area of critical importance for rapid retrieval is the creation of an index topology. | Storage: | Store electronic documents. Storage of the documents often includes management of those same documents; where they are stored, for how long, migration of the documents from one storage media to another (hierarchical storage management) and eventual document destruction. | Retrieval: | Retrieve the electronic documents from the storage. Although the notion of retrieving a particular document is simple, retrieval in the electronic context can be quite complex and powerful. Simple retrieval of individual documents can be supported by allowing the user to specify the unique document identifier, and having the system use the basic index (or a non-indexed query on its data store) to retrieve the document. More flexible retrieval allows the user to specify partial search terms involving the document identifier and/or parts of the expected metadata. This would typically return a list of documents which match the user's search terms. Some systems provide the capability to specify a Boolean expression containing multiple keywords or example phrases expected to exist within the documents' contents. The retrieval for this kind of query may be supported by previously built indexes, or may perform more time-consuming searches through the documents' contents to return a list of the potentially relevant documents. | Distribution: | A published document for distribution has to be in a format that can not be easily altered. As a common practice in law regulated industries, an original master copy of the document is usually never used for distribution other than archiving. If a document is to be distributed electronically in a regulatory environment, then the equipment tasking the job has to be quality endorsed AND validated. Similarly quality endorsed electronic distribution carriers have to be used. This approach applies to both of the systems by which the document is to be inter-exchanged, if the integrity of the document is highly in demand. | Security: | Document security is vital in many document management applications. Compliance requirements for certain documents can be quite complex depending on the type of documents. For instance, in the United States, the Health Insurance Portability and Accountability Act (HIPAA) requirements dictate that medical documents have certain security requirements. Some document management systems have a rights management module that allows an administrator to give access to documents based on type to only certain people or groups of people. Document marking at the time of printing or PDF-creation is an essential element to preclude alteration or unintended use. | Workflow: | Workflow is a complex process and some document management systems have a built-in workflow module. There are different types of workflow. Usage depends on the environment to which the electronic document management system (EDMS) is applied. Manual workflow requires a user to view the document and decide whom to send it to. Rules-based workflow allows an administrator to create a rule that dictates the flow of the document through an organization: for instance, an invoice passes through an approval process and then is routed to the accounts-payable department. Dynamic rules allow for branches to be created in a workflow process. A simple example would be to enter an invoice amount and if the amount is lower than a certain set amount, it follows different routes through the organization. Advanced workflow mechanisms can manipulate content or signal external processes while these rules are in effect. | Collaboration: | Collaboration should be inherent in an EDMS. In its basic form, a collaborative EDMS should allow documents to be retrieved and worked on by an authorized user. Access should be blocked to other users while work is being performed on the document. Other advanced forms of collaboration allow multiple users to view and modify (or markup) a document at the same time in a collaboration session. The resulting document should be viewable in its final shape, while also storing the markups done by each individual user during the collaboration session. | Versioning: | Versioning is a process by which documents are checked in or out of the document management system, allowing users to retrieve previous versions and to continue work from a selected point. Versioning is useful for documents that change over time and require updating, but it may be necessary to go back to or reference a previous copy. | Searching: | Searching finds documents and folders using template attributes or full text search. Documents can be searched using various attributes and document content. | Publishing: | Publishing a document involves the procedures of proofreading, peer or public reviewing, authorizing, printing and approving etc. Those steps ensure prudence and logical thinking. Any careless handling may result in the inaccuracy of the document and therefore mislead or upset its users and readers. In law regulated industries, some of the procedures have to be completed as evidenced by their corresponding signatures and the date(s) on which the document was signed. Refer to the ISO divisions of ICS 01.140.40 and 35.240.30 for further information.[5][6] The published document should be in a format that is not easily altered without a specific knowledge or tools, and yet it is read-only or portable.[7] | Reproduction: | Document/image reproduction is key when thinking about implementing a system. It's great to be able to put things in, but how are you going to get them out? An example of this is building plans. How will plans be scanned and scale be retained when printed? |
2.3 Hotel reservation systems Hotel reservation system is also commonly known as the central reservation system, it is a computerized system that stores and distributes information of a hotel, resort, or other lodging facilities. A CRS is mainly an assistance for hoteliers to manage all of their online marketing and sales, where they can upload their rates & availabilities to be seen by all sales channels that are using a CRS. Sales Channels may include conventional travel agencies as well as online travel agencies. A hotelier using a central reservation system easing his/her tasks for online distribution, because a CRS does everything to distribute hotel information to the sales channels instead of the hotelier.
Main modules that is present in a CRS: * Reservations * Profiles * Groups and Blocks * Rate and Inventory Control * Administration * Reporting * Global Distribution Interface * PMS Interface
2.3.1 Information commonly stored in a CRS * Room Types * Rate plans architecture * Room Rates & conditions (guarantee, deposit, customized cancellation rules, Minimum Length Of Stay, Maximum Length Of Stay, Closed to Arrival, Arrival not allowed, departure not allowed...) * Room inventories * Generic hotel information (address, phone number, fax number) * Distribution content (descriptions, amenities, pictures, videos, local attractions...) are stored in the CRS or in a Content Management System (Lanyon, VFM leornardo, Pegs ODD) * Reservation information * Geo-code information * Nearby IATA cities and airports
2.4 Review of existing similar systems
2.4.1 Hotelier hotel management systems
Hotel Management System is an ideal software solution for Hospitality Industry that can be used at hotels, motels, inns, resorts, lodges, hostel, military guest houses, ranch, suites, apartments, medical centers and bed, breakfast operations. Hotelier Hotel Management System is a comprehensive software suite consisting of integrated modules for various aspects of hotel management. The software is often referred to as Property Management System in the Hotel industry. Hotelier includes all the features required in a Hotel Management Software, Hotel Reservation Software, Hotel Reception Software (Front Office), Call Accounting, Hotel Point of Sales (Restaurant, Bar, Room Service, House Keeping or any other outlet), Inventory Management System and Hotel accounting software. In our lodging software all modules are tightly integrated and all hotel programs are included in one price, meaning all modules are included at no additional cost regardless of your hotel size. It was developed in Microsoft.Net technology, it Is compatible with all versions of Windows operating system and it also uses firebird data management system which is free so there is no additional licensing investment needed.
Hotelier is hospitality software designed for full service luxury inns, bed, breakfasts, and resorts. It emphasizes the highest level of individual guest services through its comprehensive features seamlessly integrating rooms, dining, and retail, with information contained in reservations till back office general ledger.
Features of Hotelier hotel management systems: * Accommodation management * Reservation system * Stock management * House keeping * Creation of various reports and statistics * Online reservation
2.4.2 Covenant University Guest House Hotel Management System
This system is a web based system that was developed to automate the activities involved in guest reservation and booking, management of guest data and hotel information systems.
The following are the main functions of the covenant university guest house web based hotel management system: * Online/offline reservation * Guest check in * Guest check out * View reservation
2.4.3 Comparison of existing systems Each of the above mentioned systems consist of integrated modules of various aspects of hotel management, it was observed that they all incorporated the reservation module and the check-in/check-out module being there primary component. With exception to the Hotelier management system the other two are web based applications both written in php will the hotelier was written in Microsoft Visual basic as a standalone desktop application.
It was also observed that the Covenant University Guest House Management System and the web based Management System for the Covenant University guest house are both subject to network downtime but that isn’t a major challenge for the Hotelier management system
Table 2.4.3 Comparison of existing systems | Hotelier management system | Covenant University Guest House Hotel Management System | Web based management system for Covenant University Guest House | Web Based | | X | X | Windows | X | | | Accounting | X | | X | Front Office | X | X | X | Room feature classification | X | X | X | Instant help desk | | | X | Room availability | X | | X | Accounting and Report generation | X | X | X |
2.5 CONCLUSION
A broad knowledge in understanding the subject area has been achieved. It has brought about clarity in the subject area and broadened the knowledge in Hotels and Hotel Management Systems.
A review of existing Hotel Management Systems and what they do was looked upon. This helped to improve on the methodology that would be used and also add new features to the upcoming project.
CHAPTER THREE
SYSTEM ANALYSIS AND DESIGN
3.1 Introduction
3.2 System analysis
System analysis is the study of a business problem domain from development and specification of the business requirements and priorities for solution. System design on the other hand is the structuring of a methodological computer based solution for business requirements identified in the analysis of the system [8].
In this chapter, the system designed will fashion the technical blue print and specification required to implement the final solution. It will consist of every specification that gives the system its form and structure including the design of the user interface, data and processes [9].the blue print will be used to implement required database, program, user interface and networks for the information system [10]
3.3 System Architecture
The system will be laid out in a 3-tier architecture consisting of a web application, an apache http web server and MySQL database server.
The web application written in php and hosted on an apache http server will be used to implement the guest management, room management, booking and guest reservation modules in addition to oracles MySQL Relational Database Management System (RDBMS) will be implemented in the web application
3.4 System Requirement
3.4.1 User Requirement * The system must be able to generate reports for guest occupying history, billing history, room occupancy and room statistics * Front desk office should not be allowed to perform add or edit user accounts
3.4.2 Functional Requirement * The system must be integrated to a report generation library. * The system must include a friendly Graphics User Interface * Access to the users accounts management module should be limited to the “systems administrator” only
3.4.3 Non Functional Requirements * System should dynamically select the location of the database it wishes to connect to
3.5 System Module
3.5.1 Unified Modeling Language (UML)
Unified Modeling Language (UML) is a standardized, general-purpose modeling language in the field of software engineering. The Unified Modeling Language includes a set of graphic notation techniques to create visual models of object-oriented software-intensive systems.
The Unified Modeling Language was developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in the 1990s. It was adopted by the Object Management Group (OMG) in 1997, and has been managed by this organisation ever since. In 2000 the Unified Modelling Language was accepted by the International Organization for Standardization (ISO) as industry standard for modelling software-intensive systems. The current version of the UML is 2.4.1 published by the OMG in August of 2011.
Modelling
It is important to distinguish between the UML model and the set of diagrams of a system. A diagram is a partial graphic representation of a system's model. The model also contains documentation that drives the model elements and diagrams (such as written use cases) [11].
UML diagrams represent two different views of a system model: * Static (or structural) view: emphasizes the static structure of the system using objects, attributes, operations and relationships. The structural view includes class diagrams and composite structure diagrams.
Example of static UML: * Class Diagram * Component Diagram * Object Diagram * Profile Diagram * Deployment Diagram * Dynamic (or behavioural) view: emphasizes the dynamic behaviour of the system by showing collaborations among objects and changes to the internal states of objects. This view includes sequence diagrams, activity diagrams and state machine diagrams.
Examples of Dynamic UML: * Activity Diagram * Communication Diagram * Sequence Diagram * User Case Diagram * Timing Diagram
3.5.2 Use Case Diagrams
It is a simple representation of the user’s interaction with the system; a use case diagram can portray the different types of users of a system and the various ways that they interact with the system. This type of diagram is typically used in conjunction with the textual use case and will often be accompanied by other types of diagrams as well.
Fig 3.5.2 Use Case Diagrams
3.5.3 Proposed Flow Chart
Fig 3.5.3 Proposed Flow Chart
3.5.4 Activity diagram
In the design of a system, the activities of the user can be shown with the use of an activity diagram. The activity diagram captures the actions and there results, it is mainly performed in the implementation phase
Fig 3.5.4 Activity diagram
3.6 Database description
A database is defined as a collection of interrelated files, whereas a file is a collection of similar records.
Types of Database
There are several types of databases including the relational database. Hierarchal database and network database, but for this project the relational database will be used.
The tables are used to store data in rows and columns, the fields (attributes) are represented in columns while the records in rows.
The project will implement MySQL relational database management system with the database consisting of the following tables: * Admin_login: the administrators details are saved here, administrator name and password * Check_in: the customer number and the room numbers are saved here * Contacts: the guest are registered here before checkin occurs * Customers: the customer number, customer name, duration, email and phone number are saved here * Laundry: the costing of the laundry department is registered here * Login: the user’s details are saved here, user name, password and title * Room: room number, room type and room rate are saved here.
Table 3.6.1 Admin_login Table Structure
Table 3.6.2 Check_in Table Structure
Table 3.6.3 Contacts Table Structure
Table 3.6.4 Customers Table Structure
Table 3.6.5 Laundry Table Structure
Table 3.6.6 Login Table Structure
Table 3.6.7 Room Table Structure
3.7 Relational Database
Fig 3.7 Relational Database
3.8 CONCLUSION
This chapter represents an overview of the Web based management system for hotels with appropriate diagrams that help to capture the scope of work of the project. It also describes the connections and interactions of the various software components used to establish the website for full working capability.
CHAPTER FOUR
TESTING AND IMPLEMENTATION
4.1 Introduction
Design and implementation is concerned basically with the schedule of events and list of requirements needed to put the new system to use. In this chapter the implementation codes are produced from the modules of the design phase. This is the longest phase of the design model [13]
4.2 System Requirements
In order to achieve the stated objectives of the system some requirements are necessary, they can be classified into 2; hardware and software requirements
4.2.1 Hardware requirements * Pentium 3 (950mhz) processor or higher * 14”color monitor * 16bit video graphic adapter(VGA) * Modem/Ethernet card/LAN port * Keyboard and mouse * Uninterrupted power supply
4.2.2 Software Requirements * Microsoft Windows/Linux/Mac operating systems * MySQL v5.1.30 or higher * Phpv2.0 * Apache web server
4.3 Implementation Tools Used
The design of the project comprise only of a web application which is structured into a 3-tier architecture (the front-end, the middle-ware and the back-end)
4.3.1 The Web Application
It consists of a graphic user interface (GUI), this application implements the room management, guest management, billing and other modules of the system. The implementation tools used are listed below.
4.3.2 Front-End * Adobe Dream Weaver CS6 IDE
The Adobe Dream Weaver is an IDE used to assist computer programmers with creation and design of web applications * Hypertext Mark-up Language(HTML) and Cascading Style Sheet(CSS)
Html is the authoring software language used on the web. HTML alongside CSS are used in structuring the different components of the web document
4.3.3 Middle-ware * Apache HTTP Server
The web server on which the php module is installed * PHP
Is used in this work as the server side script language, to interpret requests from clients, process and interact with the backend and other process needed for a successful transaction
4.3.4 Back-End * MySQL Relational Database Management System
The MySQL RDMS provides functionality to the database server
Fig 4.4.1 on this page the user of the system can choose to login as a user or an administrator depending on the users job/ description
Fig 4.4.2 Login_user interface
In Fig 4.4.2 the users logs into the system by putting his user name and password that have been previously assigned to him by the administrator, when the user enters his details in and logs in the system will reach into the database the ensure the details submitted are authentic and if they are it will grant the user access to pages his level of clearance grants him access to (job description)
Fig 4.4.3 Login-administrator interface
Fig 4.4.4 Front-desk interface
In Fig 4.4.4 this page only the front-desk officer can gain access to this page, this is the home page for all activities in this department
Fig 4.4.5 Check-in/out interface
In Fig 4.4.5 the front desk officer can manage room activities, update customer details, book in customers and generate billing reports
Fig 4.4.6 Book-in Interface
In Fig 4.4.6 this interface is used to book the customers into the hotels, assignment of room keys and customer numbers€
Fig 4.4.7Add-room interface
Fig 4.4.8 Update room billing interface
In Fig 4.4.8 the costing of the room can be update.
Fig 4.4.9 Customer billing
In Fig 4.4.9 The system calculates the bill and brings it out multiplying the duration of the customer by room rate
And it goes further to generate a receipt
Fig 4.4.10 Register new Guest interface
In Fig 4.4.10 before you check the customer in the guest details are first registered into the system database.
Fig 4.4.11 View contacts in Database interface
In Fig 4.4.11 this interface allows the user see all the contacts available in the database
Fig 4.4.12 Edit contacts in database interface
In Fig 4.4.12 this interface grants the user access to alter and modify data previously submitted into the database.
Fig 4.4.13 Administrator Home interface
Fig 4.4.14 Register new user interface
In Fig 4.4.14 here the administrator registers new users, during login the users are granted access to the pages that relate to their job title.
4.5 CONCLUSION
This chapter has discussed the various implementations and testing of the entire system. All the entire units and sub system of the system as a whole were tested properly.
CHAPTER 5
SUMMARY, CONCLUSION AND RECOMMENDATIONS 5.1 SUMMARY
In developing a system, the developer must fully understand what the problem is and understand the people for which the system is being design for in order for the system to communicate effectively with the users. The Web Based Management System for Hotels can be used in most standard hotels and guest houses.
The project was aimed at the design and development of a Web Based Management for the Covenant University Guest House to solve the setbacks of data access difficulties, duplicated information and data insecurity at the Covenant University Guest House and these targets have ben met
5.2 CHALLENGES AND CONSTRAINTS There is almost no substantial product that has benefits or functions well without disadvantages or constraints. Therefore, in spite of the above mentioned achievements, there were some challenges encountered. 1. Learning the programming language was time-intensive and very draining in terms of combining it with school work and school activities. Errors developed during programming the system for functionality could not be initially and easily debugged due to new level of exposure to programming. 2. The project is very bulky and is meant to be robust, and as such many aspects needed to be taken into consideration. Analyzing the project was a handful of work in terms of taking into consideration all user groups required to make use of the system. 3. The Web Based Management System for Hotels cannot be accessed without the Intranet as it is not a standalone application.
5.3 RECOMMENDATIONS
This research work is made open to future reviews and enhancements due to the constraints during the course work, certain features cab still be incorporated in the system, some of these features include: * POS(Point Of Sale) integration * Inventory Management * Online booking * Mobile alert system for customer check out data notification
Reference
[1] Maconi, S. (2012) Front Desk Automation System For the Covenant University Guest House, Nigeria: Covenant university.
[2] Baez Casillas, Sixto. (2004) Hotels. Ed. Compañía Continental S. A. Mexico. Mexico Page 15
[3] Flahery, John E. (2001) Peter Drucker. Modern Management Essence. Prentice Hall. Mexico. Page 121
[4]International Organization for Standardization. "01.140.40: Publishing". http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=40&.(2005)
[5]International Organization for Standardization. "35.240.30: IT applications in information, documentation and publishing". http://www.iso.org/iso/catalogue_ics_browse?ICS1=35&ICS2=240&ICS3=30& (2005)
[6]OnSphere Corporation. "SOP Document Management in a Validated Environments". http://www.avidoffice.com/docushare/dsweb/Get/Document- [7] Chiavenato, Adalberto (2004) Human Talent Management. The new role of human resources in organizations. Ed.McGraw Hill. Bogotá. Colombia. Page 18
McIvere, F.(2010), Development of Online Hotel Management System( A case study of the Covenant University Guest House) Nigeria: Covenant university.
[8]Sven,C., Florian, D. Peter, d. and Maristella, M. (2009), Engineering web applications. New York: Springer [9]Fredrick ,W.D(2004) Choosing the right business record keeping system retrieved from: http://www.nolo.com/legal-encycleopedia/choosing-the-right-business-record-keeping-32277.html [10]Garson, G.D.(1999), Information technology and computer applications in public administration and trends
[11]Beynon-Davis, P.(2009)
The “language” of informatics: the nature of information systems. International Journal or information Management.29(2),92-103 [12]Aggarual, A. (2010), A project report on the Hotel Management System. Harayana, India:S.A Jain (PG) College [13] Ulke, Ricardo (2005) Free software advances in the region, and becomes an option for our country. ABC
Color. 18th June 2005. Asunción. Paraguay.At www.abc.com.py/inform
