Hotel Management System Essay

The following sub divides of the Softwargon Requirements unique(predicate)ations (SRS) document condense an overview of the wide-cut SRS.1.1 PurposeThe Software Requirements Specification (SRS) leave alone provide a small description of the requirements for the Hotel counseling dust (HMS). This SRS result stand for a nab understanding of what is to be expected of the HMS to be constructed. The clear understanding of the HMS and its mapfulity provide allow for the correct parcel to be developed for the end exploiter and go aside be utilize for the development of the prox stages of the project. This SRS leave alone provide the foundation for the project. From this SRS, the HMS squirt be designed, constructed, and finally tested.This SRS leave behind be utilise by the software engineers constructing the HMS and the hotel end substance abusers. The software engineers ordain use the SRS to amply understand the expectations of this HMS to construct the appropriate software. The hotel end users bequeath be able-bodied to use this SRS as a test tosee if the software engineers will be constructing the governance to their expectations. If it is non to their expectations the end users can specify how it is not to their liking and the software engineers will qualifying the SRS to fit the end users needs.1.2 range of mountainsThe software product to be produced is a Hotel counselling dodging which will automate the major hotel operations. The prototypic sub trunk is a Reservation and appointment System to keep track of reservations and populate availability. The second sub establishment is the Tracking and Selling nutrient System that charges the accredited room.The third sub trunk is a General Management run and alter Tasks System which gene consec numbers reports to audit all hotel operations and allows modification of sub arrangement breeding. These ternion sub arrangements functionality will be described in concomitant in voi ce 2-Overall Description. There are two en users for the HMS. The end users are the hotel mental faculty (client service representative) and hotel managers. Both user suits can access the Reservation and engagement System and the Food Tracking and Selling System. The General Management System will be restricted to management users.The Hotel Management Systems objectives is to provide a dodging to manage a hotel that has increased in size to a total of 100 suite. Without automation the management of the hotel has exit an unwieldy task. The end users day-to-day jobs of managing a hotel will be alter by a considerable amount through the automated corpse. The dodging will be able to handle many services to orchestrate care of all guests in a quick manner. The agreement should be user appropriate, easy to use, provide easy recovery of errors and nurture an general end user noble subjective satisfaction.1.3 Definitions, Acronyms, and Abbreviations.SRS Software Requirements SpecificationHMS Hotel Management SystemSubjective satisfaction The overall satisfaction of the strategy overthrow users The people who will be actually using the system 1.4 OverviewThe SRS is organise into two main sections. The first is The OverallDescription and the second is the Specific Requirements. The Overall Description will describe the requirements of the HMS from a general high aim perspective. The Specific Requirements section will describe in detail the requirements of the system.2 The Overall DescriptionDescribes the general factors that affect the product and its requirements. This section does not state specific requirements. Instead it provides a background for those requirements, which are defined in section 3, and makes them easier to understand.2.1 Product PerspectiveThe HMS is an independent standalone system. It is totally self contained.2.1.1 computer hardware InterfacesThe HMS will be primed(p) on PCs throughout the hotel.2.1.2 Software InterfacesAl l databases for the HMS will be configured using Oracle 8i. These databases include hotel rooms and nodes information. These can be modified by the end users. The room database will include the room numbers and if they are vacant or occupied. The customers information database will contain all the information of the customer such as first frame, last name, number of occupants, dish outed room, default room rate(may be changed), visit number, whether or not the room is guaranteed, credit notification number, stay number, automated cancellation sequence, expected check in date and while, actual check in date and time, expected check out date and time, amount owed by customer, and abbreviated customer feedback.2.2 Product FunctionsReservation and Booking SystemAllows for pillow slip in customer informationHas a default room rate that is adjus evadeIncludes a description field for the changed rateWhen a customer checks in, the room number will be changed to occupied in thed atabase skill to modify a reservationWhen no rooms are in stock(predicate) and a customer would like to extend their reservation their information will be placed in a database and when there are rooms usable the first customer on the list will view as the room When a customer checks out the amount owed is displayedIf the internal quantify states that is a customers time to have checked out and customer has not checked out, adds an extra night to amount owed and provides a report Records that room is vacantRecords paymentAllows for space to write customers feedbackTracking and Selling Food SystemTracks all meals purchasedCharges the current room as necessaryGeneral Management Services and Automated Tasks SystemReports retortd to audit hotel occupancy, future occupancy, room revenue, and food revenue riddance reports listing exceptions to the normal costAllows addition, deletion and modification of information on rooms and rates, circuit card items and prices, user profiles Cr eation of users and assigning passwords2.3 user Characteristicseducational level of HMS computer software LowExperience of HMS software noneTechnical Expertise Little2.4 Apportioning of RequirementsThe audio and visual alerts will be deferred because of low importance at this time.2.5 Assumptions and Dependencies The system is not necessary to save pay offd reports. Credit card payments are not included3 Specific RequirementsThis section contains all the software requirements at a level of detail, that when combined with the system context diagram, use cases, and use case descriptions, is sufficient to enable designers to design a system to satisfy those requirements, and testers to test that the system satisfies those requirements.3.1 External InterfacesThe Hotel Management System will use the standard arousal/output devices for a personal computer. This includes the following KeyboardMouseMonitor newspaperman3.1.1 User InterfacesThe User Interface Screens are described in table 1.Table 1 Hotel Management User Interface ScreensScreen human bodyDescriptionLoginLog into the system as a CSR or coach-and-fourReservationRetrieve button, modify/save reservation, cancel reservation, modify reservation, change reservation, adjust room rate, consent payment type/credit card Check-inModify room stay (e.g., new credit card), sign in customer (with or without a reservation), adjust room rate, special requests, accept payment type/credit card CheckoutCheckout customer, generate billHotel PaymentAccept payment for room and food room Service/RestaurantCreate order, modify order, view order, cancel order, generate meal bill Customer RecordAdd or update customer go insAdminister RoomsAvailability and ratesAdminister UserCreate, modify, and cut users change passwordAdminister MealsCreate, modify, and delete meal items and pricesReportsSelect, view, save, and delete reports3.1.2 Software InterfacesThe system shall interface with an Oracle or find database.3.1.3 Hardware InterfacesThe system shall run on a Microsoft Windows based system.3.1.4 Communication InterfacesThe system shall be a standalone product that does not require any colloquy interfaces.3.2 Functional RequirementsFunctional requirements define the fundamental actions that system must(prenominal) perform. The functional requirements for the system are divided into three main categories, Reservation/Booking, Food, and Management. For move on details, refer to the use cases.1. Reservation/Booking1.1. The system shall destroy reservations.1.2. The system shall record the customers first name.1.3. The system shall record the customers last name.1.4. The system shall record the number of occupants.1.5. The system shall record the room number.1.6. The system shall display the default room rate.1.6.1. The system shall allow the default room rate to be changed. 1.6.2. The system shall require a comment to be entered, describing the reason for changing the default room rate. 1.7. T he system shall record the customers visit number.1.8. The system shall display whether or not the room is guaranteed. 1.9. The system shall generate a unique confirmation number for each reservation. 1.10. The system shall automatically cancel non-guaranteed reservations if the customer has not provided their credit card number by 600 pm on the check in date. 1.11. The system shall record the expected check-in date and time. 1.12. The system shall record the expected stoppage date and time. 1.13. The system shall check-in customers.1.14. The system shall allow reservations to be modified without having to reenter all the customer inforamtion. 1.15. The system shall check customers.1.15.1. The system shall display the amount owed by the customer. 1.15.2. To retrieve customer information the last name or room number shall be used 1.15.3. The system shall record that the room is empty.1.15.4. The system shall record the payment.1.15.5. The system shall record the payment type.1.16. The system shall charge the customer for an extra night if they checkout after 1100 a.m. 1.17. The system shall mark guaranteed rooms as must pay after 600 pm on the check-in date. 1.18. The system shall record customer feedback.2. Food2.1. The system shall track all meals purchased in the hotel (restaurant and room service). 2.2. The system shall record payment and payment type for meals. 2.3. The system shall bill the current room if payment is not made at time of service. 2.4. The system shall accept reservations for the restaurant and room service. 3. Management3.1. The system shall display the hotel occupancy for a specify termination of time (days including past, present, and future dates).3.2. The system shall display projected occupancy for a period of time (days). 3.3. The system shall display room revenue for a specified period of time (days).3.4. The system shall display food revenue for a specified period of time (days).3.5. The system shall display an exception report , showing where default room and food prices have been overridden.3.6. The system shall allow for the addition of information, regarding rooms, rates, menu items, prices, and user profiles.3.7. The system shall allow for the deletion of information, regarding rooms, rates, menu items, prices, and user profiles.3.8. The system shall allow for the modification of information, regarding rooms, rates, menu items, prices, and user profiles.3.9. The system shall allow managers to assign user passwords.3.3 Nonfunctional RequirementsFunctional requirements define the needs in harm of performance, logical database requirements, design constraints, standards compliance, reliability, availability, security, maintainability, and portability.3.3.1 Performance RequirementsPerformance requirements define acceptable reply times for system functionality. The load time for user interface screens shall publication no longer than two seconds. The log in information shall be verified at heart five s econds. Queries shall return results within five seconds.3.3.2 reproducible Database RequirementsThe logical database requirements include the retention of the following data elements. This list is not a complete list and is designed as a starting line point for development.Booking/Reservation SystemCustomer first nameCustomer last nameCustomer addressCustomer phone numberNumber of occupantsAssigned roomDefault room rateRate descriptionGuaranteed room (yes/no)Credit card number chit numberAutomatic cancellation dateexpect check-in dateExpected check-in timeActual check-in dateActual check-in timeExpected check-out dateExpected check-out timeActual check-out dateActual check-out timeCustomer feedbackPayment received (yes/no)Payment typeTotal BillFood ServicesMealMeal typeMeal itemMeal orderMeal payment (Bill to room/Credit/Check/Cash)3.3.3 Design ConstraintsThe Hotel Management System shall be a stand-alone system running in a Windows environment. The system shall be developed usin g coffee and an Access or Oracle database.3.3.4 Standards configurationThere shall be consistency in variable names within the system. The graphical user interface shall have a consistent tint and feel.3.3.5 ReliabilitySpecify the factors required to establish the required reliability of thesoftware system at time of delivery.3.3.6 AvailabilityThe system shall be available during normal hotel operating hours.3.3.7 SecurityCustomer Service Representatives and Managers will be able to log in to the Hotel Management System. Customer Service Representatives will have access to the Reservation/Booking and Food subsystems. Managers will have access to the Management subsystem as well as the Reservation/Booking and Food subsystems. Access to the various subsystems will be protected by a user log in screen that requires a user name and password.3.3.8 MaintainabilityThe Hotel Management System is being developed in Java. Java is an object oriented programming language and shall be easy to maintain.3.3.9 PortabilityThe Hotel Management System shall run in any Microsoft Windows environment that contains Java Runtime and the Microsoft Access database.4 Change Management ProcessChanges to this document may be made after grace from the project manager and the client approval officer.5 Document Approvals5.1 police squad One Approval____________________________________Sandra Busik/Reita Sikka Date5.2 Team Two Approval____________________________________Lisa Ferrett Date6 Supporting InformationA system context diagram as well as use cases and use case descriptions have been developed in separate documents.