Software Development: Online Accommodation Booking System

This report discusses the development of an Online Accommodation Booking System (OABS) for the Australian tourism sector. It includes use cases, state chart diagram, sequence diagrams, activity diagram, class diagram, requirement verification, and development using prototyping method.

Running head: SOFTWARE DEVELOPMENT
Software Development
Name of the Student:
Name of the University:
Author Note

1
SOFTWARE DEVELOPMENT
Table of Contents
Introduction................................................................................................................................2
Use Cases...................................................................................................................................2
Use Case Descriptions................................................................................................................3
State Chart Diagram...................................................................................................................4
Sequence Diagrams....................................................................................................................6
Activity Diagram........................................................................................................................8
Class Diagram..........................................................................................................................11
Requirement verification..........................................................................................................11
Use of wireframe prototyping methods in OABS................................................................11
Development of OABS using prototyping method..............................................................12
Conclusion................................................................................................................................13
Bibliography.............................................................................................................................14

2
SOFTWARE DEVELOPMENT
Introduction
The report has been used here for the discussion of the Online Accommodation
booking system. The system is being developed for the Australian tourism sector. The people
who are travelling would be benefitted by this application. The details for the development of
the system has been described in the report. The models for the development has been
designed in the report. The report further focuses on the Adding new hosts to the system.
Other processes have also been described that would be able to provide a clear idea about the
functions that are to be performed by the application.
Use Cases
The use cases identified for the Online Accommodation booking system are described
below:
Use case Description
Add new host The administrator would be accept the registration of the youth or the host
registration. This would enable them to add a new host in the system.
Register on the
application
The hosts and the youths would be able to register into the system.
Book Rooms The system would be able to provide the room booking options to the youth.
Make Payments The youths would be able to make payments for the booking that they have
created.
Receive Payments The hosts would be able to receive the payment for the booking made by the
youths.
Use Case Descriptions
The use case description of the“add new host by the admin” has been provided below:

3
SOFTWARE DEVELOPMENT
Use case number UC3
Use case name Add New Hosts
Primary actors Administrators
Secondary actors Hosts
Description The administrator would be accept the registration of the youth or the host
registration. This would enable them to add a new host in the system.
Pre-conditions Application for registration
Post-conditions Provide information about their accommodation
Process flow Actor System
1. Get registration notification
2. Add the details in to the system
1. Send notification about the
registration
2. Store the details of the hosts into
the system
Exceptions 1. An exception may occur if the details of the hosts are not appropriate.
2. Another type of exception might occur if the details of the
accommodations are not placed correctly in the system.
The use case description of the case “Book a reservation by youth” is provided below:
Use case number UC8
Use case name Book a reservation
Primary actors Youth
Secondary actors Host, Administration
Description The system would be able to provide the room booking options to the youth.
The room booking information are provided to the youth by the system and
the payment for the rooms are made by the youth.
Pre-conditions Search for the rooms

4
SOFTWARE DEVELOPMENT
Post-conditions Proceed to payment
Process flow Actor System
1. Search rooms
2. Select the rooms
3. Make payment
1. Display rooms
2. allocate the rooms
3. forward the payments
Exceptions 1. An Exception condition is which would be taking place if there is a room
unavailable according to the requirements of the youth.
2. Another exception occurs when there are some problems with the
payment gateway for the youth and payment is declined by the bank
servers.
State Chart Diagram
The state chart diagram for adding a host to the system by an admin is provided
below:

5
SOFTWARE DEVELOPMENT
The state chart diagram for booking a room by a traveller/youth is provided below:
Sequence Diagrams
The system sequence diagram for adding a host to the system by the admin is
described below:

6
SOFTWARE DEVELOPMENT
The classes used in this diagram are the Host and Accommodations. The verification
of the classes are described with the domain model diagram provided below:
The system sequence diagram for booking a room by youth is described below:

7
SOFTWARE DEVELOPMENT
The classes used in this diagram are the Host and Accommodations. The verification
of the classes are described with the domain model diagram provided below:

8
SOFTWARE DEVELOPMENT
Activity Diagram
The activity diagram for add new host process by the admin is provided below:

9
SOFTWARE DEVELOPMENT
The activity diagram for the full process of the OABS is described below:

10
SOFTWARE DEVELOPMENT

11
SOFTWARE DEVELOPMENT
Class Diagram
The class diagram developed for the entire system has been described in the diagram
provided below:
Requirement verification
For the verification of the requirements of the system to be developed for the client.
The OABS system would be making use of the prototyping model. The Wireframes
development have been done for the using the Storyboarding method to develop the
preliminary project and gather further information for the development of the system.
Use of wireframe prototyping methods in OABS
The prototyping method that is being implemented within the system includes the
wireframe method. The main reason behind using wireframe method is that it offers low
fidelity mock-up that is used for the purpose of serving 3 simple and exact purposes. The
wireframe method ensures that it has the ability to present the information on the page

12
SOFTWARE DEVELOPMENT
effectively. This also helps in providing an effective outline for the structure and layout. This
ensures that the system is able to provide overall description towards the users. The main
reason behind using a good wireframe is that it ensures simple way to handle the application.
The main reason behind using a prototype is that it is being treated as a barebones. These are
mainly used as a next step in the design of the product. Wireframes are considered as the
most convenient way of designing the prototype. Wireframe ensures that the users are
allowed to test digital product’s interaction. The functionality level can be made useful at the
time of usability testing of the developed OABS application. The main reason behind
resembling to this product is that it can be developed by saving time and efforts. The main
reason behind considering the wireframes prototype method is that it offers better digital
product. These are considered as the basic idea that can improve the product performance.
Prototypes are basically more visual representation of product. The best time to use
storyboard is the time when having an idea to communicate with the members. A storyboard
is mainly referred to a linear sequence that is used for the purpose of showing the user may
face challenges with an existing process or product.
Development of OABS using prototyping method
The application will ensure that the people can register within the application
effectively. The host will also be provided with the registration process. The application will
provide support towards the admin for rejecting youth registration. The main aim behind
developing this prototype for OABS is that it will ensure better way of managing the
payments. This is the responsibility of the host to choose appropriate payment system. The
system will also allow the user to search for the available loops. Thus with the help of the
developed prototype model it will become easy to manage the activities that are taking place.
The payment section needs to be developed in such a way that it can meet the needs of the
OABS services. Apart from this the developed prototype will allow the host to share and

13
SOFTWARE DEVELOPMENT
review the comments about the past visitors on social network. Admin needs to upgrade the
reserved hosts so that they can have active hosts on OABS when the available rooms run out.
Admin is allowed to cancel the room booking at any time as per their need. With the help of
the storyboard prototyping it will become easy to manage the activities. However the final
decision is of the Admin. They can refuse the decision at any time that is being shared by the
host. Admin can encourage the hosts with high ratings on their OABS website. The main
reason behind using the prototyping method is to ensure that each step is being explained
effectively without any errors. The prototype model will ensure a better performance and will
ensure that the users are able to interact directly. Thus the developed prototyping model will
help to analyse the main components of the system. The system components will ensure that
each sub functions are carried out successfully without much trouble.
In the developing the prototyping model using the method of storyboard and
wireframe it must satisfy some of the important specification so that all the requirement of
the proposed system can be verified. In this aspect the main requirement are which, those has
been asked by the clients. This project is development of online accommodation booking
system for the working holiday travellers. In this aspect while prototype of system is being
developed, some basic specification that the prototype model should have as functional
requirement are discussed in the following section. With that non-functional requirement of
the system will be discussed.
Functional Requirement:
 This prototype for the online accommodation booking system must be having three
types of user access so that all the functionality of the system remains active and
requirements can be satisfied. These users of the online accommodation booking
system are the youths, hosts and admins. Here both of the youth and host can register

14
SOFTWARE DEVELOPMENT
to the system while admin will be responsible for approving or rejecting the
registration request of hosts and youth.
 One of the main functional requirement of system the system is that it must be able to
take bookings from the youths. For this prototype of the system must have an user
interface through which users will be able to navigate different types of
accommodations that is offered by the hosts. Through this youths will be able to find
their suitable accommodations. In the user interface there should be a section through
which youths will be able to select the dates of accommodation.
 In the booking section the prototype also need to provide the functionality of group
booking. For this the prototype of the system must be capable of taking multiple
bookings from a single user at same time. Any type of booking can be cancelled by
the admin of this prototype system.
 As the youths are booking accommodations from the hosts for a certain period of
time, the prototype of the system must consist a payment feature. Thus there will be
secured online payment gateway for the youth during the booking sessions through
which they will be able pay hosts the accommodation fee.
 The admin of the prototype will be able to send private messages to both of the host
and youths.
 This prototype system will also have a functionality of cancellation of booked rooms.
Both of the host and the user will be cancel their bookings but for this both of them
follow some rules. After the cancellation, this prototype must refund to the respective
youth automatically.
 Any type of decisions taken by the host can be refused by admin of the prototype
system and for that there must be a feature in the system.

15
SOFTWARE DEVELOPMENT
 This system prototype must consist the feature of reviewing and commenting feature.
While youths will be able to comment about the hosts the host will be able to share
those comments and review of the youths. Here admin will be having the functionality
of promoting the host with the high ratings in the OABS website.
Non-Functional Requirement:
 The system prototype must be usable in nature such that users does not face any type
of issues while using the system.
 The prototype also need to be reliable in nature such that it does not become unstable
at any moment of operations especially at the moment of transactions.
 The prototype also must be well performing and for that it need to optimize. If the
performance of the prototype is low then users of the system will not be interested to
using the system due to the performance issue.
 This prototype is also need to be cost-effective in nature. If the cost of the prototype is
too much higher then there is no meaning of building the prototype.
Conclusion
For conclusion, it can be said that the development of the OABS has been described
efficiently in this report. In addition to this the requirement gathering process has been
described using the prototyping wireframe model. The description of the model and the
requirements gathered from the model has been described efficiently in the report. Hence,
this report provides the complete information required for the development of the OABS for
the Australian tourism sector.

16
SOFTWARE DEVELOPMENT
Bibliography
[1] Abrahamsson, P., Bosch, J., Brinkkemper, S. and Mädche, A.. Software Business,
Platforms, and Ecosystems: Fundamentals of Software Production Research (Dagstuhl
Seminar 18182). SchlossDagstuhl-Leibniz-ZentrumfuerInformatik. , 2018
[2] Anwar, S., Mohamad Zain, J., Zolkipli, M.F., Inayat, Z., Khan, S., Anthony, B. and
Chang, V. From intrusion detection to an intrusion response system: fundamentals,
requirements, and future directions. Algorithms, 10(2), p.39. , 2017.
[3] Klotins, E., Unterkalmsteiner, M. and Gorschek, T., June. Software engineering
knowledge areas in startup companies: a mapping study. In International Conference of
Software Business (pp. 245-257). Springer, Cham. , 2015
[4] Kolen, P. EE 330 Fundamentals of Engineering Electronics. , 2017.
[5] Moaveni, S. Engineering fundamentals: an introduction to engineering. Nelson
Education. , 2016.
[6] Samarasinghe, S. Neural networks for applied sciences and engineering: from
fundamentals to complex pattern recognition. Auerbach publications. , 2016.
[7] Spichkova, M., Liu, H., Laali, M. and Schmidt, H.W. Human factors in software
reliability engineering. arXiv preprint arXiv:1503.03584. , 2015.