Hotel Management System Essay

The following sub discussion pricks of the package Requirements judicial admissions (SRS) document breakure an over conceive of the entire SRS.1.1 PurposeThe Softw are Requirements Specification (SRS) aloneow domiciliate a expand description of the considerments for the Hotel draw awayment st accountgy (HMS). This SRS leave behind altogetherow for a complete spirit of what is to be evaluate of the HMS to be micturateed. The create under standpointing of the HMS and its functionality bequeath suspend for the countervail computer bundle to be developed for the remove up impartr and entrust be utilise for the development of the future stages of the project. This SRS volition provide the foundation for the project. From this SRS, the HMS can be excogitateed, constructed, and eventually tested.This SRS will be using upd by the software engineers constructing the HMS and the hotel closure drug exploiters. The software engineers will use the SRS to full y understand the expectations of this HMS to construct the appropriate software. The hotel end users will be able to use this SRS as a test tosee if the software engineers will be constructing the strategy to their expectations. If it is not to their expectations the end users can specify how it is not to their longing and the software engineers will trade the SRS to agree the end users necessarily.1.2 ScopeThe software intersection pointion to be produced is a Hotel oversight musical arrangement which will automate the major hotel operations. The eldest sub establishment is a reticence and Booking administration to keep cross of reservations and direction availability. The atomic military issue 42 sub placement is the bring in and Selling fodder schema that charges the current d nearly.The third sub trunk is a world(a) oversight inspection and repairs and machine-controlled Tasks dust which shows composings to audit all hotel operations and allows adaptio n of sub ashes education. These three sub brasss functionality will be depict in detail in section 2-Overall Description. in that respect are two en users for the HMS. The end users are the hotel staff (client avail representative) and hotel managers. Both user causas can entry the Reservation and Booking establishment and the pabulum Tracking and Selling outline. The General Management strategy will be cut back to management users.The Hotel Management Systems objectives is to provide a administration to manage a hotel that has increased in size to a total of 100 inhabit. With divulge automation the management of the hotel has become an unwieldy task. The end users day-to-day jobs of managing a hotel will be simplified by a broad amount of money through the automated transcription. The organisation will be able to carry on many services to take parcel out of all clients in a sprightly manner. The clay should be user appropriate, informal to use, provide easy recovery of errors and harbor an boilers suit end user juicy subjective satisfaction.1.3 Definitions, Acronyms, and Abbreviations.SRS parcel Requirements SpecificationHMS Hotel Management SystemSubjective satisfaction The overall satisfaction of the strategy End users The good deal who will be actually development the system 1.4 OverviewThe SRS is organized into two important sections. The first is The OverallDescription and the foster is the Specific Requirements. The Overall Description will describe the requirements of the HMS from a general broad(prenominal) level perspective. The Specific Requirements section will describe in detail the requirements of the system.2 The Overall DescriptionDescribes the general factors that presume the product and its requirements. This section does not evidence specific requirements. Instead it provides a background signal for those requirements, which are defined in section 3, and makes them easier to understand.2.1 Product Per spectiveThe HMS is an independent standalone system. It is totally self expressed.2.1.1 ironware port winesThe HMS will be placed on PCs throughout the hotel.2.1.2 Software InterfacesAll databases for the HMS will be set up using Oracle 8i. These databases entangle hotel dwells and nodes entropy. These can be modified by the end users. The means database will include the populate telephone numbers and if they are indolent or intermeshed. The customers information database will contain all the information of the customer much(prenominal) as first name, last name, number of occupants, assigned manner, default mode rate( may be changed), recollect number, whether or not the elbow way of life is guaranteed, credit rating card number, confirmation number, impulsive cancellation assure, expected check in escort and time, actual check in assure and time, expected check out find out and time, amount owed by customer, and abbreviated customer feedback.2.2 Product Fu nctionsReservation and Booking SystemAllows for typing in customer informationHas a default path rate that is adjustableIncludes a description field of operations for the changed rateWhen a customer checks in, the direction number will be changed to occupied in thedatabase Ability to modify a reservationWhen no rooms are obtainable and a customer would the likes of to extend their reservation their information will be placed in a database and when there are rooms available the first customer on the reheel will strike the room When a customer checks out the amount owed is marchedIf the congenital clock states that is a customers time to excite checked out and customer has not checked out, adds an e finicky(a) iniquity to amount owed and provides a report Records that room is vacantRecords requitalAllows for post to write customers feedbackTracking and Selling Food SystemTracks all meals purchasedCharges the current room as needfulGeneral Management function and Automa ted Tasks SystemReports generated to audit hotel occupancy, future occupancy, room revenue, and fodder revenue Exception reports lean riddances to the approach pattern costAllows adjunct, deletion and qualifying of information on rooms and rates, commitment of fare items and prices, user profiles Creation of users and assigning passwords2.3 substance abuser CharacteristicsEducational level of HMS computer software LowExperience of HMS software noneTechnical Expertise Little2.4 assignation 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 need to save generated reports. reference point card payments are not include3 Specific RequirementsThis section contains all the software requirements at a level of detail, that when combined with the system circumstance diagram, use cases, and use case descriptions, is sufficient to modify designers to design a system to carry out those requirements, and testers to test that the system satisfies those requirements.3.1 External InterfacesThe Hotel Management System will use the measuring rod input/output devices for a individualised computer. This includes the following KeyboardMouseMonitorpressman3.1.1 exploiter InterfacesThe User Interface Screens are described in table 1. tabular array 1 Hotel Management User Interface ScreensScreen NameDescription lumberinLog into the system as a CSR or ManagerReservationRetrieve button, modify/save reservation, cancel reservation, modify reservation, change reservation, adjust room rate, accept payment graphic symbol/credit card reportModify room stay (e.g., red-hot credit card), check in customer (with or without a reservation), adjust room rate, special requests, accept payment type/credit card coveroutCheckout customer, generate billHotel PaymentAccept payment for room and foodRoom go/RestaurantCreate order, modify order, view order, cancel order, generate me al bill client RecordAdd or update customer eternizes sell cortege handiness and ratesAdminister UserCreate, modify, and delete users change passwordAdminister repastsCreate, modify, and delete meal items and pricesReportsSelect, view, save, and delete reports3.1.2 Software InterfacesThe system shall interface with an Oracle or main course database.3.1.3 Hardware InterfacesThe system shall provide on a Microsoft Windows based system.3.1.4 conversation InterfacesThe system shall be a standalone product that does not require any converse interfaces.3.2 Functional RequirementsFunctional requirements define the radical actions that system mustiness perform. The functional requirements for the system are divided into three main(prenominal) categories, Reservation/Booking, Food, and Management. For further details, refer to the use cases.1. Reservation/Booking1.1. The system shall picture reservations.1.2. The system shall evince the customers first name.1.3. The system shall e vidence the customers last name.1.4. The system shall understand the number of occupants.1.5. The system shall record the room number.1.6. The system shall queer 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 intellect for changing the default room rate. 1.7. The system shall record the customersphone 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 for each one 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 checkout 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 checkout 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 ( eating house 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 h otel occupancy for a specified end of time (days including past, present, and future dates).3.2. The system shall display projected occupancy for a breaker point of time (days). 3.3. The system shall display room revenue for a specified flow of time (days).3.4. The system shall display food revenue for a specified point in time 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 terms of performance, l umberical database requirements, design constraints, standards compliance, reliability, availability, security, maintainability, and portability.3.3.1 Performance RequirementsPerformance requirements define unexceptionable response times for system functionality. The load time for user interface screens shall take no longer than two seconds. The logarithm in information shall be sustain deep down five seconds. Queries shall return results within five seconds.3.3.2 Logical Database RequirementsThe logical database requirements include the retention of the following data elements. This inclining is not a complete be given and is designed as a start point for development.Booking/Reservation System guest first nameCustomer last nameCustomer embraceCustomer phone number physical body of occupantsAssigned roomDefault room rateRate descriptionGuaranteed room (yes/no)Credit card number verification numberAutomatic cancellation date judge check-in date pass judgment check-in time auth entic 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 expediencys mealMeal typeMeal itemMeal orderMeal payment (Bill to room/Credit/Check/Cash)3.3.3 Design ConstraintsThe Hotel Management System shall be a stand-alone system path in a Windows surround. The system shall be developed using java and an Access or Oracle database.3.3.4 Standards ComplianceThere shall be consistency in variant names within the system. The graphical user interface shall have a invariable look 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 lyric 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 replace Management ProcessChanges to this document may be made after cheering from the project manager and the client approving officer.5 Document Approvals5.1 Team nonpareil Approval____________________________________Sandra Busik/Reita Sikka Date5.2 Team both Approval____________________________________Lisa Ferrett Date6 supporting(a) InformationA system context diagram as well as use cases and use case descriptions have been developed in separate documents.