Software Engineering Assignment 2

This document provides the use case descriptions and sequence diagram for the add new host and book reservation functionalities in the OABS system. It also includes a prototype, hardware and software specifications, and references.

1
Coursework Assignment Header
Student Name : --------------------------------------------------------------------------
Student Number : ------------------------------------------------------------------------
Teaching Staff Name : -----------------------------------------------------------------------
Trimester : T12019
Unit Code : MN507
Unit Title : Software Engineering
Assignment type : Group
Assignment title : Assignment 2
Weighting : 20%
Total marks : 70
Date/time : Friday 30th
May 2019, 5pm (Week11)
Submission Mode

Table 1 below show use case description of add new host.
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. Fail to add new host due
to host failing to book and withdraws.
Triggering Event The Admin wants to add new host on system
Actors Host,admin and OABS
Purpose To Add new host on OABS System.
Overview and Description The use case describe the way admin uses
AOBS system to add new host.
Type Study, software design and developing needs.
Stakeholders Youth, Australia government , Host and
organizer
Pre-Conditions OABS is operational, The host has register
on OABS and provide all details on
system.Admin login on system
Post-Conditions The admin has added Host on system
Special Requirements
Flow of Events
Actor Action System Response
Host register on system and create
account..Admin login on AOB system and
adds new host. After adding Host 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 add option on admin
side. The system accepts add host details and
stores them in database. System records login
details of both admin and host.
Alternate Flow of Events/Exceptional Conditions
Host and admin Authenticate, Host register
and admin add host. Host details are
successful recorded in system database
Incorrect username and password.Wrong
registration details of host.Admin cannot add
host..

Figure 1 below shows sequence diagram
Figure 1 above demonstrates steps taken for admin adds to new host.
Step 1
Host Registers on OABS system by entering personal details
Step 2.
OABS validates registration details .Then a verification message is send back to hot can be in
form of email or sms.
Step 3.
Host can login on system by providing username and password.
Step 4
Admin login on system on admin panel.
Step

Admin interface of adding new host is displayed.
STEP 5
Customer receives a notification of successfully added on system.
Assumptions.
Admin is already registered.
System is online and running.
Table 2 below show use case description of Book reservation.
Use Case Description
Use Case Name Book a reservation
Scenario Success Scenario: Youth book a reservation
Failure Scenario: Fail to book because
reserve are not available all are booked. Fail
to book because youth does not have enough
money. Fails to book because Host refused
booking. Fail to book because admin rejected
registration on system.
Triggering Event The Youth wants to book Reservation
Actors Youth, Host,admin and OABS
Purpose To book Reservation on OABS System.
Overview and Description The use case describe the way Youth uses
AOBS system to register and book
reservation.
Type Study, software design and developing needs.
Stakeholders Youth, Australia government , Host and
organizer
Pre-Conditions OABS is operational, The youth register and
makes advance payment and provide all
details on system. Host and Admin login on
system.
Post-Conditions The Youth has booked a reservation.
Special Requirements
Flow of Events

Actor Action System Response
Youth and Host already have accounts on
system. Youth login on system and book a
reservation. Host logins on system and
accepts booking.
System Authenticate youth, admin and host.
The system displays the book reservation
option for youth to book reserve. System
display accept book option for host to accept
booking. System records transaction in
database
Alternate Flow of Events/Exceptional Conditions
Host and youth Authenticated, Youth book
reservation on system and Host accepts book
reservation.
wrong username and password. Wrong book
reservation detail and host refuse book
reservation.
Figure 2 below show state chart diagram

Figure 3 below shows activity diagram

Figure 4 below show class diagram
Prototype.
Prototype will be web based and mobile based.
Prototype will have a dashboard where a user can navigate and select different functionalities
they want.
Prototype will have forms for registration.
Hardware specification
Processor will use Intel
System will run on computer and phones.
System will be supported by standalone server.
Computer using windows 7 and above.

Software specification.
System will run on android platform and windows operating system.
Reference.
Reference.
(1).Thomas M. Connolly and Carolyn E. Begg .Database systems a practical approach to Design,
implementation and management. 6th Ed, vol 3 .Harlow, Essex, England: Addison-Wesley Pearson
Education Limited, 2015, pp, 109 -111
(2).Pressman, Simenon .Software Engineering. Practitioner’s Approach. 8thEd vol 6. Inc., 1221 Avenue
of the Americas, New York, McGraw-Hill, 2017.pp, 399-450.
(3).Lethbridge, M Timothy. Object-Oriented Software Engineering: Practical Software Development
Using UML and Java 3ndEd ,VOL 6. New York, McGraw-Hill.2016,pp, 200-300.