When we design the new system, it will be providing the owners to receive and store reservations from customers through the internet, or by other booking methods and then record into the system. Because they also have a website, so we will to synchronize the website process such as cancel or making reservation, it will make the customers’ reservation much quicker to record into the system data. And when the customers make the reservation or check-in from the counter, we will to record all details of the customers, such as the customers’ name or business name, address, contact number, credit card detail, etc, it make the owners to know who has been lived and provide their detail when happen any emergencies. The new system also show the availability of each room or facilities to let staffs clearly to know the timetable, to let the staffs and owners know each room is available to register for customers and record the inventory on hand, to let the owners know when need to buy the goods and needs for the hotel, too .When the customers check-out, the system will calculate the total costs of each customer’s final account without manually, it will more efficiency and affectivity. We also provide the profit and lost statement, inventory statement, employees’ payroll statement and also the balance sheet, it is much easier when owners need to provide the financial detail for accountant.
Feasibility Analysis
Technical Feasibility
There is low level computer or administrative skills to use the new reservation system, and also repetitive tasks something like figuring out the total costs for customers. It’s easily solved by upgrade the current computer to run the new system. The new reservation system is feasible technically, though there is some risk. Happy Holidays Hotel risk regarding the familiarity with the technology in the new system is high. Until now, the Happy Holidays Hotel staffs has used paper to make bookings and timetables instead of her computer, so making this new system work mostly on the computer/internet will be a large difference. Laura Jones has admitted she struggles to learn new systems, hence why she is still using hard copy sheets. Laura Jones has learnt to update the site herself, but struggles with it. The Happy Holidays Hotel risk regarding familiarity with internet bookings is high. The Hotel has an existing website and an Internet Service Provider, and we could integrate the new booking system into this. Laura Jones struggles to update the website herself, and adding a new booking system to this would make things overly complicated at first. Laura and the staff would need a lot of training to use this new booking system. The compatibility of the new system with Happy Holidays Hotel’s current technical infrastructure should be good. Happy Holidays Hotel has already got a web system set up, so it shouldn’t be hard to integrate a reservation system into that. In the current system, much of the work is done as hard copies, but this has become too complicated with the new rooms and facilities. Laura Jones owns a computer that could be used instead of the hard copies. The new system would use this computer to produce reservations for the customers and timetables/itineraries for the staff.
Organisational Feasibility
The staffs’ skills are low, so the staffs need to learn how to use the new system, and the new system development staff, etc. It’s also need motivation for new reservation system acceptance. It shouldn’t be a huge problem in this case. In other way, the business can training more staffs like Betty who are good at drumming up the business to increasing the business profitable. Also the owners need to demonstrate the new plan for the business and why to input new system into the hotel, and how the new system will helping the hotel to growth, and we will provide the detail on the advantage of using new technology of the new system. On the organisation side of things, this project is low risk. The objective of the new reservation system aligns perfectly with that of the hotel; to increase the amount of customers and make it easier for them to book rooms/ facilities. The new system will make extensive use of the internet, giving customers a new way and easy to book reservations which will hopefully increase sales. This should be enough motivation for the staff to learn to use the new system, given the possibility of more customers. The customers, too, are expected to accept this new reservation system as it benefits them.
Resource Feasibility
The hotel needs physical space for the new reservation system and also need to create a network for the hotel. It shouldn’t be a problem. Staff will help with the development and running of the new system. The hotel also have their own private beach, they can use this advantage to create some special events or setting up some function of events to let the customers to choose, it will help the hotel to claim more customers to visit them. The resource feasibility for this new reservation system is not a risk or concern. There will be staff to help with the development and training regarding the new system, and software will need to be made or purchased. The website and internet service provider are already in use, so that helps. As far as physical space goes, the new system shouldn’t really take up much. If anything it will save space, as hard copies are no longer being used.
Economic Feasibility
The hotel currently wasting money on inefficient tasks and labour hours, they using huge papers on reservations and calculating the cost of customers’ final account. The new system will reduce the cost on spending papers and labours. Also the owners want to be fully booking on the weekend, so the hotel can have some promotion on weekend like discount or special function event, which I think it will increase the customers. So when the owners acceptance the new system into their hotel, it will help the business more efficient and effectively. On the economic side of things, this project isn’t expected to be too costly or a risk. The Happy Holidays Hotel already has a computer, an internet service provider and a website. They would have to pay for the system software and the conversion to this new system, as well as training for its use. However, there shouldn’t be many ongoing costs after this. The system will result in more customers with increased customer satisfaction, less operating costs, as well as lowering the amount of work the staff is expected to do in making reservations. Laura Jones is currently wasting money doing inefficient tasks that could be improved electronically.
Schedule Feasibility
The schedule feasibility is low risk. I don’t anticipate integrating the new system will take very long at all, as much of the functionality (website, ISP, etc) is already in place. The training staff feasibility risk is low too, the staffs can training on weekend or when they are not on duty, and the training sessions can be make for 1 hour per day and setting up for 2 sessions for a day, it wouldn’t crush the hotel work.
High Level Use Case Diagram
Case Description
Use Case Name: Customer makes a reservation.
Primary Actor: Customer
Short description: Customer contacts the Happy Holidays Hotel and makes a reservation.
Type: Essential
Interests:
- Customer wants to make a reservation
- Hotel Staff wants to have customers stay at their hotel.
Trigger: Customer makes a reservation by phone or through the website.
Events:
- Customer contacts the Hotel either by phone or through the reservation system offered on the website.
- Customer inquires about what rooms/facilities are available and when they want to rent them.
- Hotel staff tell them what’s available and when.
- Customer gives their credit card details.
- Provide bill to customers
- Accept to pay deposit
- All this information is
Major Inputs:
Major Outputs:
Use Case Name: Record reservation
Primary Actor: Staff
Short description: Staff record customers’ into reservation system
Type: Internal
Interests:
- Record the customers’ details
- Check the availability for customers
Trigger: Received the reservation by phone or website.
Events:
- Customers request the type of room/facilities
- Check the availability for customers from the reservation system.
- Record customers detail.
- System provides the bill and availability to staff.
- Accept to charge deposit from the credit card.
- System provides the receipt to staff.
- All this information is
Major Inputs:
Major Outputs:
Use Case Name: Process reservation
Primary Actor: Reservation System
Short description: Record customers’ detail and process the payment
Type: Internal
Interests:
- Record the customers’ details
- Pass the payment detail to credit card company
Trigger: Customers make reservation
Events:
- System received the request.
- Show the availability of room/facilities.
- Record customers’ personal & credit card detail.
- Provide the billing information.
- Accept to charge deposit from the credit card.
- System provides the credit card detail to Credit Card Company.
- Received the fund from Credit Card Company.
- Provide the receipt.
- Transfer information to Administrator.
- All this information is
Major Inputs:
Major Outputs:
Activity Diagram
Class Diagram
Context Diagram
Level 0 Data Flow Diagram (DFD)
Level 1 Data Flow Diagram (DFD)
Comparison and analysis
From the diagrams and information above, all is to improve the reservation system of the hotel business. In use case description, it is much easier to understand the current system work like, the case description provides all the input and output of reservation system of information that will be use, and also what the users can do and how the system responds. The case description actually is very simple to learn and use, it’s help the users know how the system operated, but the weakness of this diagram which is provide brief information of the system, not the details. The use case diagram helps the user to see the major processes taking place regarding the system, and which users are accessing and controlling these processes. The class diagram doesn't show data being exchanged as well as other diagrams; it tends to focus on the relationships between entities. This is helpful in that it allows us to see how entities in the system interact in relation to each other. Activity diagram shows the all events of the reservation system, this diagram is easier to make clients to understand the current system working, but the weakness which is lack if the information for advance use, it didn’t provide enough detail of the user’s needs. It is useful in that it shows the flow of events in the system, and allows us to see what could be improved or made more efficient. In context diagram, this diagram is the first DFD in every business process, and also shows all the external entities that information received or output information from the current system, but it does not consider what the external entities do with that information. It focuses entirely on the system and how the entities exchange data with it. The level 0 DFD is the current system of major process, it including all external entities and data stores that existed within the content diagram, and the level 1 DFD is the current process of the current main process in the level 0 DFD, it show how the information move and also shows more clearly information of each activities. This data flow diagram is particularly helpful in showing the way the system operates, as data is the key element in any system. The level 1 DFD takes it a step further by focusing on a certain process inside the level 0 DFD and expands on it, going into great detail regarding the information exchanged in the selected process. So the Data Flow Diagram is very useful for the current reservation system, it clearly define all information that enters or is release for the system. The DFD diagrams do show a great amount of information about data in the system, but it doesn’t go into detail regarding how this information Is exchanged and they can often be complicated or hard to understand.
So we will suggest the new system based building with the Data Flow Diagram, it will make the current business more efficiency and effectively.
Reference
Topic 3 Lecture note, Deakin Studies Online, 20th April 2009.
Topic 4 Lecture note, Deakin Studies Online, 10th May 2009.
Topic 5 Lecture note, Deakin Studies Online, 12th May 2009.
Jones, L. 2009, DSO discussion; , 28th April 2009.
Jones, L. 2009, DSO discussion; , 1st May 2009.
Jones, L. 2009, DSO discussion; , 1st May 2009.
Jones, L. 2009, DSO discussion; , 1st May 2009.
