System Requirements for Online Accommodation Booking System

Melbourne Institute of technology
School of Information Technology and Engineering
Software Engineering
(Group Assignment)
1. Student1 Name: -----------------------------------------------------------------------
2. Student2 Name: -----------------------------------------------------------------------
3. Student3 Name: -----------------------------------------------------------------------
Teaching Staff Name : -----------------------------------------------------------------------
Submission Date

INTRODUCTION
The purpose of this report is to determine system requirements through requirements
elicitation for an Australian online accommodation booking system (OABS). The report
examines the design processes for verification and validation of the system requirements by
using several modelling techniques to specify the requirements. Through these modelling
techniques, functional specifications, system implementation, design, integration and testing
plans are produced. The report concludes by proposing an appropriate prototyping tool for the
verification of the online accommodation booking system client's requirements.
Use case modelling
Use cases are used to describe the functional requirements of a particular system [1].
They describe the way the user will interact with the system and how the system will respond
[2]. Some of the use cases identified in the OABS are register user, search room, book room, pay
for reservation, cancel booking, share review comment, promote, refuse booking, approve
registration, send private message and finally upgrade host.
Use case description
i. Add new Host by admin
The use case description is where the properties of the use case are defined. Key properties
include flow of events, preconditions, and post-conditions [3]. Preconditions are the things that
must be in place before the use case action can begin. Post-condition on the other hand is what
comes in place when the use case ends successfully or unsuccessfully. A post-condition on
success shows what happens when the process completes successfully. A post-condition on
failure stipulates what happens when the process doesn’t complete successfully. Flow of events
stipulates the step-by-step action and relations between the actor and the system.
Use Case Description
Use Case Name Add new host
Scenario Success Scenario: Host is added
Failure Scenario: Fail to add new host because host failed

to provide correct registration details.
Triggering Event The Admin wants to add new host in the system
Actors Admin and OABS
Purpose To add a new host in the OABS System
Overview and Description The use case describes the way admin uses AOBS system
to add new host by approving or rejecting the host
registration
Pre-Conditions - OABS is operational,
- The host has registered in the OABS and has
provided all details in the system.
- Admin has logged into the system
Post-Conditions - The Host is successfully added into the system
- A failure message as to why the failure is sent to
Host
Flow of Events
Actor Action System Response
- Host registers into the system and creates
an account.
- Admin logins into the AOB system and
verifies the Host’s details.
- Host registration is either approved or
rejected.
- Admin can log out of system.
- Host is recorded on database of system.
- Host can now successfully login on
system and start using system service
System Authenticate both admin and host.
The system displays the approve option on
admin side. The system accepts add host
details and stores them in database. System
records login details of both admin and host.
Exceptional Conditions
Some Host details are missing or are incorrect, Admin reject the registration and a rejection
message is sent to the host.