Online Accommodation Booking System

This report discusses the development of an online accommodation booking system, including its stakeholders, software types, and attributes. It covers the system's functional and non-functional requirements, as well as its use cases and actors.

ONLINE ACCOMMODATION BOOKING SYSTEM.
[Student Names]
(School Name)
(Professor Name)
(Date)
Table of Contents
ONLINE ACCOMMODATION BOOKING SYSTEM..........................................................................................3

Stakeholders............................................................................................................................................3
Software types.............................................................................................................................................4
Software attributes......................................................................................................................................5
a. Maintainability.................................................................................................................................5
b. Dependability and security..............................................................................................................5
c. Efficiency..........................................................................................................................................6
d. Acceptability........................................................................................................................................6
Requirement analysis..................................................................................................................................6
Requirement collection tools..................................................................................................................6
Verification and Validation..........................................................................................................................7
Functional Requirements............................................................................................................................8
Non Functional Requirements.....................................................................................................................8
System modeling.........................................................................................................................................9
Reference..................................................................................................................................................12

ONLINE ACCOMMODATION BOOKING SYSTEM.
Introduction
The online information access has become very essential in the current computing error especially in the
business entity where the customers and the services provider are able to interact and also make the
payments .
This report is about the online accommodation booking system that is used by the hosts who provides
the rooms for accommodation, the students who register and book for rooms to be accommodated and
the system administrator who is responsible of managing the system where he approves the students
and the hosts registrations and also can cancel the student bookings.
This system has been developed to improve the service delivery to students and also adding more
clients to the hosts.
Stakeholders
The online accommodation booking system is a system that is used by various users and they are able to
perform some respective functions according to the privileges given to them.
Below are the various stakeholders of the OABS system.
The youths.
The youths are one of the target stakeholders who are the customers and below are some of their roles.
a. To make online registration.
b. Searching of and booking the rooms.
c. Making group booking.
d. Selecting the travel dates.
e. Making payments for theirs accommodations.
f. Cancelling the bookings made.
g. Sharing the reviews comment about the past host.
The system administrators.
The system administrator is the other stake holder who is responsible managing the system and the
data in the system, however below are his roles.

a. Approving or rejecting the youths and hosts registration.
b. Sending private messages to the hosts and the youths.
c. Putting the hosts to the reserved lists.
d. Upgrading the reserved host to the active hosts.
e. Canceling the room bookings.
f. Promoting the hosts on the OABS website.
The hosts.
The hosts is the other stakeholder and he has various roles as well ,below are the hosts role.
a. Registering on the OABS website.
b. Providing their accommodation facilities information .
c. Receiving the payments through the website.
d. Sharing the reviews comments about their past visitors.
The rooms attendants.
The room attendants are the other stakeholders who prepares the rooms for the accommodation,
below are some of their roles.
a. Issuing the room to the youths.
b. Cleaning the rooms and making beds.
c. Retrieving the room from the students.
The host accountant.
The host accountants are the other stake holder that has the following roles.
a. Receiving the payments from the youths.
b. Making the balance sheet accounts for the hosts.
Software types
There are various method that are used in the system acquisition depending on the customer needs and
system specifications , among the types of software are the generic and the customized system
acquisition process as discussed below.

Generic software.
The generic type of software is referred to the general purpose applications and it is meant to provide
variety of uses ,for instance the Microsoft excel is used to perform many tasks like making calculations
and plotting of graphs.
Below are some example of generic software:
a. Ms Word processors: it is used in production of the essay, letter and curriculum vitae.
b. Ms publisher: This is used in the production of calendars, poster and cards .
c. Ms excel: This is used to do some calculation and plotting of graph.
Customized software.
The customized software is referred to as the tailor made software and this is mainly developed for a
specific company or organization or other types of businesses.
However this software is designed and developed for one customer where the specifications and
requirements of customer are fully accommodated and implemented.
However these software can be designed to perform some functions which can be contents
managements, inventories managements, human resources managements and among others.
Below are some customized software’s features:
a. They have specific designs: this software is only developed for a specific users or customers.
b. Incorporation of features: The software can have some features related to other software
applications.
c. It has flexibility: this software is highly flexible to accommodate all uses.
d. Easy to upgrade: The system can be upgraded if new features are required.
e. Developed using standard developments tools: The software is developing using some of
the tools which are standardized.
Therefore for this system I recommend the system to be acquired using the customized software
acquisition process which will enable the system to be developed and all functionalities are
implemented, however the generic software is not the best process to acquire the software since none
can be able to fit all the requirements.

Software attributes
In the software design there are some specific attributes that measures the successful software and they
includes the following:
a. Maintainability
The successful systems are said to be maintainable if they have high probability of being repairable in
any given environment within a given period of time and also the system should have short repair time.
b. Dependability and security
For every successful system there is dependability and security ,this is measured by ensuring that the
system ha s ability to resisting any accidental or deliberated intrusion attempts.
c. Efficiency
A successful system is required to be efficient such that the ratios of the output to the input used by
the users correlates
d. Acceptability
A successful system should be acceptable to all the users ,this is achieved by the implementation of all
the required user requirements to achieve all the system functionalities.
Requirement analysis
In this OABS website system development process the first important thing is to correct and gather all
the system requirements where the information is gathered from all the three major stakeholders who
includes the youths , hosts and the administrators [6] .
There are various tools and techniques that are set to collect and analyze the system requirements as
discussed below.
Requirement collection tools.
Below are the various tools and techniques used to collect the system requirements.
a. Use of questionnaires.
This is a tool or technique of collecting the required information where and it is administered to the
target group of people ,however this consists of structured or open ended type of questions and the
respondent select or fill in the questionnaires independently.

b. Conducting interviews.
This is type of tool an technique that is used to collect information, however it is a better way compared
to the use of the questionnaires since it is appropriate to do the information validations. However the
interview is used to enable the information gathered to avoid miss-understandings and allow better
response evaluations.
c. Through brainstorming.
The brainstorm is a process of gathering the information through holding a discussion with group or
single shareholders of the system, however after the brainstorm process the various ideas are gathered
and reviewed and analyzed and if necessary are added as part of the system requirements.
d. The feasibility studies.
The feasibility study is a tool used to gather information where the existing system requirements are
analyzed and the requirements are them obtained from it and few changes are made.
Verification and Validation.
After the collection and selection of the system requirements those requirements require to be done
verification and validations ,however the requirement validation is a process that is interactively used
and is used in the entire project life-cycle [5].
However in the elicitations, analysis and specifications process the data collected is questioned in a
constant manner to check its validity, this will ensures the system requirements that are produced are
complete, consistent for the validation processes and system development.
Below are the two validation techniques that are used:
a. Reviews and inspections.
This is one of the processes that very rigorous where it consumes a lot of time since all the stakeholders
are represented .There is collaboration in the reviewing of the system requirements where the arising
issues are noted in the issues logs.

However some of the issues get resolved immediately and some are forwarded to the system specialist
to get more clarifications ,therefore the processes are interactive in nature and a series of iterations are
until the issues get resolved.
b. Prototyping .
This is another validation process that enables the system users and the developers be on agreement on
the requirements before the system is implemented.
The prototyping however is another way to do the validity tests and requirements completeness, this
process validates the system requirements through the provision of visual models to the system user.
After the validation the system developers decides the best approach of presenting the prototypes
according to the situation.
Functional Requirements
The OABS website system is used by various people and they use it to do some tasks ,however all these
abilities of the system are referred to the system requirements .
Below are some of the major systems requirements.
a. System should enable the youth to register and book for accommodation.
The system is used by the youths and then they make the booking stating their selected date.
b. The system should enable the hosts to register and provide information about accommodation.
The hosts access the system and then register in order to be able to provide the accommodations
information
c. The system should allow the youth to make the payments.
The student will use the system to make the payments to the hosts after making bookings of the rooms.
d. The system should enable the hosts to receive the payments.
The hosts will be able to receive the payments from the students who had booked the rooms for
accommodations [4] .

e. The system should allow the student to share reviews comments about the past host on social
network.
The students after using the accommodation of a certain host they can post the review comments and
rate them on a social media
Non Functional Requirements.
Below are some of the system non –functional requirements and they illustrates how the system quality
is and how it functions.
Below are some of the identified non-functional requirements:
a. Uptime .
The system uptime measures the amount of the time that the OABS website will be accessible ,and be
available to the users, however the system to be developed will be having more than 99% uptime hours
and thus no limitations of using the system.
b. Response time.
The system response time is the time that elapsed between the end of time when the OABS website will
be queried by the users and the beginning of the system response, however the OABS website will be
having a short response time of less than 20 seconds such that the system users will not note any
system delays.
c. Reliability.
The OABS website system will be highly reliable and the probability of it performing according to the
requirement is more than 99.9% and this is at any given time while being accessed using any of internet
connected device.
d. Security .
The OBAS website system will enforce security to the users information by setting the access control
using the usernames and passwords that prevents the unauthorized persons from accessing the system,
therefore all the information of the users is kept private and confidential, where the integrity is
enforced.

e. Usability.
The OBAS website system has no any limitation of use by the registered users however it will be
developed to ensure that it is effective, efficient and all the systems authorized users will use it and will
be fully satisfied [3] .
System modeling.
Below are some few use cases that are used in the OABS website system which summarizes the use
cases, their descriptions and the respective associated actors.
Use cases descriptions
Use cases Descriptions Actors
Registering in
system
In this use case the students and the hosts register into the
system and they are approved by the admin.
admin,host,student
Sharing review
comments
This use case where the student share reviews about the
previous hosts and the doctor review comment of the previous
student to the social media.
Host and student
Cancelling room
booking
This is the use case that allow the student cancel their bookings
and also the admin can cancel the booking of a certain student.
Admin and student
[1]

Use case diagram.
[2]
Searching and booking rooms
Making group booking
Selecting travel date
Paying for accommodation
Promoting hosts with high ratings
Sharing review comments
Providing accommodation
information
Promoting the services
Receiving payments
Withdrawing from OABS
Approving or rejecting registration
Sending private messages
Putting hosts on reserve list
Upgrading reserved hosts
Cancelling room booking
Registering in system
ONLINE ACCOMMODATION BOOKING SYSTEM

Conclusion.
The OABS website system implementation will be very efficient while being used by the target group this
is because of good collection of system requirements, the designing process and the development of the
entire system, therefore I recommend other similar companies to adopt the website system for better
services delivery.

Reference
[1] k. Daryl ,Use Cases: Requirements in Context. Boston:Addison-Wesley, 2012,pp. 51-368.
[2] D,Alan, Systems Analysis and Design. New Jersey: John Wiley & Sons, 2014,pp.10-698.
[3] A, Dennis , Systems Analysis and Design 5th Edition .New Jersey:Wiley,2012, pp.1-592.
[4] B,Wixom, Systems Analysis and Design 6th Edition .New Jersey:Wiley,2014,pp. 448.
[5] D, Tegarden, Systems Analysis and Design: An Object-Oriented Approach with UML 5th
Edition .Jersey: Wiley, 2015, pp. 546.
[6] D, Alan, Systems Analysis and Design with UML 4th Edition .New Jersey:Wiley, 2012, pp. 608.