Chapter 3



Chapter 33.1 Software Requirement Specification3.1.1 Introduction To develop the Online Hotel Reservation, the work is started by gather information about the topic. The technology such as software and hardware needed to develop the study are decided. To gather requirements of this study, discussion is held within supervisor and hotel staffs.After studying and analyzing the flow of the current system of hotel, the proponents would like to recommend the following: the system proves to be fast accurate convenient, efficient and reliable for the process of reservation. The proponent developed an online reservation system suitable for the hotel; the system could save time, effort in filling and monitoring.Hotel reservation system plays a great role and has a potential effect on day to day performance measures, this type of system have highly evolved from decades due to high demand for their use, effective and efficiency in any given institutions. Due to the rapid change of technology the use of such system has become a necessity to any given high learning institution for better performance and be used with quite a large number of users at the same time but it can save time, resources and creates awareness of the evolving technology.? 3.1.1.1 Goals and Objectives3.1.1.1.2 Goals The goal of the current system is to develop a Hotel reservation system to replace the computerized Hotel reservation. The purpose of the document is to describe requirements for the Online Hotel Reservations Software that will serve as a foundation for the final product. It is important that an agreement of these requirements be reached so that everyone’s expectations will be met. This document uses written descriptions as well as various types of modeling diagrams to illustrate the high level structure of the application. Although some of these diagrams may seem to convey similar information they typically do so from an alternate perspective. This gives different stakeholders a view of the requirements that is better suited to their area responsibility.A web based solution will be delivered so that users the system with their favorite browser. By designing around a standardized language like JAVA the application will run on the most popular computer platforms connected to the internet will allow employees to more easily share information.The Hotel Reservation System Software is intended to provide a computer based system that will assist in managing in a guest. Many typical functions involved in operating a hotel will be automated through software to improve the operational workflow within a facility, for instance maintaining a guest rooms to be check in. in addition, tasks like processing invoices and printing guests reports will be available within the program to minimize the time that administrative staff must spend creating these documents. This requirements Specification will describe these as well as many other features of the software in greater detail.3.1.1.2 Statement of Scope The initial stage of project development is to find of system requirements and define project scope. Scope or boundary of project is important to anticipate the time of completion. By a clearly defines scope, specified time will be assigning to develop each module in the application. From here can conclude that, virtual tour on hotel room needing more using digital video camera. Other module my need less time for completion. By well-organized tasks and duration, the application will develop on time, within scope and fulfill all the system requirements.After defining the project scope, the matters that will considered in doing the research are time, resources, technology and skills. The unavailability of the time during the project development, such as several tasks that need to be handle in one time need to be consider when building the schedule. The resources availability, such as expertise, reference books or internet online also needs to be considered. The lack of technology and skills in the developer will also affect the schedule planning.3.1.1.3 Software ContextThere are many key component of hotel reservation. But the ability of their hotel reservation to remain in the business will be dictated in their ability to manage, development projects would be severe risk of missing deadlines, escalating budgets and a low-quality system. As a conduct a project study, our system provides the structure, method, controls and checklist needed to ensure successful development.In this project, the application developed is called online hotel reservation, which is web-based application. This onlined reservation application is accessible through internet and local area network. The programming languages and software involved in this project are identified.For the project facilities, laser printer is required to print the project documentation. Scanner is using to scan pictures that are needed to place in this document.3.1.1.4 Major ConstraintsThe hotel Reservation System will use Microsoft which requires a web server supporting this technology.3.1.2 Usage Scenario3.1.2.1 User ProfilesThe following definitions describe the actors in the system. Admin An admin has the responsibility for registering a new customer and also he can access the system including the viewing and changing password. StaffThe staff can only view the system if client/customer got check in and check out and also the information of the guest’s. System The system refers to the computer hardware and software that controls all application. Its accepts user input ,display user output, and web server thru internet.3.1.2.2 Use CaseThe following is how the guest reserves to the hotel:1. Log onto system2. Display available rooms3. Reserve for the room Available3.1.2.2.1 Use-Case Diagram3.1.2.2.1 Reception of user-case diagramCheck in DateModifyReservationModifyCustomerUpdateCustomerRoomReserved Room CategoryCheck Out DateFigure 1.Reception of User-caser DiagramFigure 1.Reception of User-caser Diagram. This figure represents the transaction between the admin and the costumer 3.1.2.2.2 Use-Case Description Use-CaseSearch available roomGoal: Reception search for available roomActors: Reception SystemPreconditions:The reception must insert the check in and checkout dateTriggers: The reception clicks the button "SearchBasic Scenario:1. The reception specify the check in and checkout date. 2. The reception adds room type. 3. Reception clicks on the button "Search". 4. The system will show the available rooms with their type on the determined dates. 5. The reception chooses the rooms the customer prefers depends on the floor and the view and clicks the button "Booking". 6. System will take the reception to the booking details page.Post Conditions:The reception searched for the available rooms.Use-CaseBooking DetailsGoal:Insert the booking details.Actors:Reception SystemPreconditions: The reception must be done with the room search.Triggers:Reception click the button "Save"Basic Scenario:1. Check in date, check out date. 2. The reception fill the Guest Details "First and Last Name, Address, Email, Telephone Number and finally the guest identification number". 3. Then the reception must fill the guest credit card information "Credit card number, credit card holder name and the credit card expire date". 4. Then the reception clicks on "Save" to save all the information on the database. 5. The system will check the information before saving it in case the receptions forget to insert any of the important information.Post Conditions:The receptions have completed the booking details.Use-CaseRemainder EmailGoal:Send a remainder email to the guest to date before the check in date.Preconditions:Reception must be able to access the system via a web browser; booking details must be in the database.Triggers:Reception clicks button "Remainder Email".Basic Scenario:1. The reception clicks to view a list with the entire guest who will check in after two days. 2. The reception clicks "Send" to send a remainder email to each guest.Use-CaseChange Guest InformationGoal:Alter properties such as telephone number or email of the guest.Actors: Reception SystemPreconditions:Reception must be able to access the system via web browser.Triggers:The reception clicks the button "Change Guest Properties".Basic Scenario:Basic Scenario: 1. Reception clicks the button to initiate change guest properties process. 2. System prompts the administrator to a guest by searching using the guest identification or viewing a list of guest. 3. System displays the guest properties. 4. System alters the guest properties. 5. System displays the home page.Post Conditions:A room has been altered with the system.Use-caseCustomer SearchGoal:Modify a customer information.Preconditions:The customer information should be on the database.Triggers:The reception searches for customer by his ID or view all the customer list.Basic Scenario:1. After the reception search's for a customer his information will upper on the page "First and Last name, address, telephone number, and his email". 2. Modify the customer information.Post Conditions:The customer details will be modified. 3.1.2.3 Special Usage ConsiderationsBilling fees cannot be change.3.1.2.4 Activity Diagrams The following activity diagrams show the actions that occur during particular use-case. Figure 2. Activity Diagram for Online Hotel Reservation System.3.1.3. Data Model Description3.1.3.1 Data ObjectsGuest Data ObjectCostumerID A unique identifier assigned to the costumer.Form displays of a units/rooms occupancy status presentation that gives the ability to select a free unit and make a reservation by one clickName The costumer’s name.Birthdate The child’s birth date.Special Needs Any special needs such as housekeeping food and others.Status indicates if the customer is check in or in waiting ments a customer comment about the hotel.Employee Data ObjectUserID A unique number assigned to the employee.Password The employee’s Password used to log on to the computer system.FirstName The employee first name.LastName The employee’s last name.Hotel Room Data ObjectHotelRoomID A unique number for the hotel room.Hotel RoomNO. The hotel room number.Phonenumber The phone number of the hotel room.Check In Data ObjectGuestID the identifier number of the guest.RegisteredDate The date that the guest registeredCheck INDate The date that the guest check in.Check Out Data ObjectGuestID The identifier number of the guest.RegisteredDate The date that the guest registeredCheck OutDate The date that the guest check out.Confirmation Data ObjectConfirmationID A unique identifier for the confirmation.GuestID The identifier number of the guest.EmailAdd Sends the confirmation check into the hotel.3.1.3.2 RelationshipsIn order for a guest have an account with the hotel they must have been check in to the hotel. Since a guest can have a multiple guest a one too many relationship exists. It is also true that a guest cannot exist alone in the hotel system. In the general all guest must have registered for the hotel. A guest will receive a confirmation for the GuestId. A guest will pay in advanced bill using their credit cards. However after their check in they should pay their bill the two data object cannot exist alone.The Hotel Room can hold up depend to their reservation. They cannot be reserved it if they has a guest at that day. A one to one relationship exists because a hotel room will have at most waiting list and each list can only be used for a single Hotel Room.An employee may add multiple events to their daily reminder list so one-to-many relationship exists. Since the employee may not need to be reminded of anything it is possible for an employee to exist without a daily reminder, but a daily reminder must be assigned to a specific employee.Each time an employee edits a record it will be recorded in the change data object. Most employees will make multiple changes so there is a one-to-many relationship between employee and the change data objects. An employee may not any change and can therefore exist alone. However, a change object must be associated with an employee and therefore cannot exist alone3.1.3.3 Complete Data ModelThe relationships between the data objectsFigure 3. Relationship diagram for the Hotel Reservation system.3.1.4 Functional Model Description3.1.4.1 Class Diagramfigure4. Online Hotel Reservation class diagram3.1.4.2 Software Interface Description 3.1.4.2.1 External Machine Interfaces The software will be capable of printing invoices and reports on a local or network printers3.1.4.2.2 External System Interfaces The Online HR system will communicate with a web server on the internet through a high speed network connection such as DSL, cable, or T1 line 3.1.4.2.3 Human InterfaceWeb pages shall permit complete navigation using the keyboard alone, in addition to using mouse and keyboard combinations3.1.4.3 ReportsInventory of ReportsLayout of ReportsData Dictionary of Reports3.1.5 Behavioral Model Description3.1.5.1.1 Description for Software Behavior 3.1.5.1.1 EventsGuest Class EventsGuest’s reservation roomGuest check inGuest check outGuest billAdministration Class EventsAdministration is hiredAdministration logs onto the systemAdministration logs off of the systemAdministration gets promotedAdministration is no longer employed3.1.5.1.2 StatesGuest StatesDescriptionReserved The guest has been sign in to a hotel request.Check InThe guest has arrived in the hotel.Check OutThe guest left the hotel.Administration DescriptionOn LineThe employee has logged on to the system. Off LineThe employee has logged off the system.VacantReservedOccupiedRoom number entered when customer check inRm No entered when customer checks inFive hrs. past check inCustomer check outRm. no. enteredRROOMoom Statechart3.1.5.2 State chart DiagramFigure 3. Room State ChartFigure 4. Scheduler State chart3.1.6 Restrictions, Limitation, and ConstraintsThe system shall integrate within the existing LAN structure and with the existing system, such as the database management system.All JAVA codes shall conform to the Java standard.All server side code shall be written in java Eclipse.3.1.7 Validation CriteriaSoftware validation will ensure that the system responds according to the users expectations; therefore it is important that the end users be involved in some phases of the test procedure. All tests will traced back to the requirements.3.1.7.1 Classes of TestsUnit testing will be conducted on all of software subsystem including:Daily remindersViewing and editing informationViewing and printing reportsLogging on to the systemReserve for the room hotelViewing and printing invoicesAcceptance testing will be conducted at the Guest’s Site.3.1.7.2 Expected Software ResponseThe software should display an appropriate error message when a value outside the accepted limits is entered.The software should not be capable of deleting a guest record even if they withdraw from the hotel.3.1.7.3 Performance BoundsThe system shall support up to infinite simultaneous users against the website/web server at any given timeThe system will provide access to the database management system with a latency of no more than 20 seconds. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download