Melbourne Institute MN507: Group Report on OABS System Requirements

This report, prepared as a group assignment for the Software Engineering course (MN507) at Melbourne Institute of Technology, focuses on determining the system requirements for an Australian Online Accommodation Booking System (OABS) through requirements elicitation. The report employs use case modeling to describe functional requirements, detailing scenarios such as registering users, searching for rooms, and booking reservations. It then proceeds to design verification and validation processes by utilizing various modeling techniques, including System Sequence Diagrams (SSD), State Transition Diagrams, Activity Diagrams, and Class Diagrams, to specify the system requirements. The report also covers the production of functional specifications, system implementation considerations, design aspects, integration and testing plans. Finally, it concludes by recommending paper and pencil as the most appropriate prototyping tool for verifying the OABS client's requirements, emphasizing its ease of use and control over design details.

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.

System Sequence Diagram (SSD)
A sequence diagram is used to illustration the dynamic properties of a system. They
illustrate the messages that are passed between two modules in a system [4].
Fig 1 showing System Sequence Diagram (SSD) based on use case Add new host by admin
ii. Book a reservation by Youth
Use Case Description
Use Case Name Book a reservation
Scenario Success Scenario: Youth books a reservation
Failure Scenario: There no available rooms to book, The
youth does not have enough money for available room.
Triggering Event The Youth wants to book a reservation
Actors Youth
Purpose To book Reservation on the OABS system.
Overview and Description The use case describes the process involved when a youth
uses AOBS system to place a booking.
Pre-Conditions - OABS system is operational and there are some
available rooms

- The youth has registered in OABS system
- The youth registration has been approved by the
Admin
Post-Conditions Booking reservation is placed successfully.
Flow of Events
Actor Action System Response
- Youth registers into the system
- Admin approves the youth registration
- The youth logins into the system
- The youth searches for available rooms
- The youth selects for accommodation
dates
- The youth pays for the reservation
- The youth places the booking
- System Authenticate youth login
- The system displays the book reservation
option for youth to book reserve.
- System accepts the booking
Exceptional Conditions
 There are no available rooms for reservation
 The youth does not have sufficient fund to place a booking
 Host withdrawals booking
Other important use cases description
iii. Register user
Use Case Description
Use Case Name Register User
Scenario Success Scenario: Youth or Host provides registration
details
Failure Scenario: OABS is not online
Triggering Event The Youth or a host wants to register into the AOBS
Actors Youth/ Host
Purpose To book register into the OABS system.

Overview and Description The use case describes the process involved when a youth
or a host wants to register him/herself into AOBS system
Pre-Conditions - OABS system is online
- A host has an existing facility for accommodation
- Personal or facility details conforms to the OABS
requirements
Post-Conditions A host has no accommodation facility
Details are incomplete
Flow of Events
Actor Action System Response
- User opens the OABS online system
- User navigates to registration
- User provides necessary details
- Wait for Admin verification and
approval
- The system displays the registration
form.
- System accepts the registration details
Exceptional Conditions
 The OABS is faulty and is not online
 The user enters wrong formatted data and system rejects
iv. Search room
Use Case Description
Use Case Name Search for Room
Scenario Success Scenario: Youth searches for available rooms for
accommodation
Failure Scenario: OABS is not online
Triggering Event The Youth searching for available rooms
Actors Youth
Purpose To search either to view or book for any available rooms
Overview and Description The use case describes the process involved when a youth
wants to search either to view only or to search and place a

booking for available room
Pre-Conditions - OABS system is online
- Youth is registered and approved in the OABS
- Youth logs into the system
- There are already registered facilities with some
rooms
Post-Conditions There are no registered facilities in the system
The youth’s registration has not been approved yet
Flow of Events
Actor Action System Response
- Youth logs into OABS online system
- Youth searches for an available room
- System authenticates Youth login details
- System displays search results
Exceptional Conditions
 The OABS is faulty and is not online
 The youth’s registration is not yet approved by the Admin
v. Pay for reservation
Use Case Description
Use Case Name Pay for reservation
Scenario Success Scenario: Youth successfully pays for a
reservation
Failure Scenario: The youth’s account has insufficient
funds
Triggering Event The Youth wants to pay for a particular reservation
Actors Youth
Purpose To pay for a particular reservation
Overview and Description The use case describes the process involved when a youth
wants to pay for reservation in the AOBS system
Pre-Conditions - OABS system is online

- A youth’s account has sufficient fund
- The youth has search for available room
Post-Conditions The youth’s account has no sufficient funds
Flow of Events
Actor Action System Response
- Youth opens the OABS online system
- Youth searches for available rooms
- Youth authorises for payment
- The system displays the payment
information
- System accepts the payment
Exceptional Conditions
 The OABS is faulty and is not online
 The youth’s account has insufficient funds
State Transition Diagram
A state machine diagram is an activity UML diagram which illustrates distinct actions of
a part of designed system through finite state transitions. It is also used to describe the usage of
certain protocols for a part of the system.

Fig 2 showing State Transition Diagram for Book a reservation by youth
Activity Diagram
An activity diagram is a type of flow chart. It represents the flow of the business logic on
a system. It is used to detail a specific task and how the system will accommodate the individual
scenario of that particular task.

Fig 3 showing activity diagram for new host
Class diagram
A class diagram illustrates the inert structure of the main classes that are used to develop
a particular system. The most important attributes and methods of each class are illustrated in the
class diagram together with the optional indication of some other attributes like visibility. A class
diagram also illustrates the relationship that binds some of the classes in a system. The
relationships give a static view of the structural associations that have been designed to allow
communication and interaction among the classes. All these details about a class diagram
provide a very informative summary of many decisions about the system's organization.

Fig 4 showing AOBS class diagram
Assumptions made:
- A youth can belong to more than one group
- A group can make more than one reservation
- A facility can have one or more rooms but a room can have zero one reservation
Prototyping tool to verify the client requirements
Prototyping is essential to creating successful software and successful user experience.
Prototyping ensures success because it clearly depicts the software requirements by visualizing
them rather than describing them. Prototyping tools and techniques differ substantially.
However, selecting a prototyping tool is determined by the tool's ease of use, the speed at which
a developer can make refinements to an interface and see the interface in action again, extensive

control over prototype features, data collection capabilities, lifecycle support, team design,
version control and execution capabilities for the prototype [5]. These tools include paper and
pencil, facade tools, interface builders and online emulators.
The best tool for verifying user requirements for this project would be the paper and
pencil. Paper and pencil are prototyping tools with much strength. They are easy to use; they
allow extensive control over details of the design. It encourages team design because many
people can draw at the same time especially on blackboards and large sheets of paper. In
addition, different kind of information is capture and what is not captured can easily be
expressed with textual annotations.

REFERENCES
[1]. A. P. Sage, W. B. Rouse, Handbook of Systems Engineering and Management. New Jersey,
John Wiley & Sons, 2014.
[2]. D. Rosenberg, M. Stephens, Use Case Driven Object Modelling with UML Theory and
Practice: Theory and Practice. New York. Apress, 2008.
[3]. K. Bittner, I. Spence, Use Case Modelling. Boston, Addison-Wesley Professional, 2013.
[4]. B. Pernici, Advanced Information Systems Engineering: 22nd International Conference,
CAiSE 2010, Hammamet, Tunisia, June 7-9, 2010, Proceedings.
[5]. R. N. Taylor, J. Coutaz, Software Engineering and Human-Computer Interaction: ICSE '94
Workshop on SE-HCI: Joint Research Issues, Sorrento, Italy, May 16-17, 1994. Proceedings.