Software Engineering Course Project Hotel Reservation Android App

Addis Ababa University
Addis Ababa Institute of Technology (AAIT)

Faculty of Electrical and Computer Engineering
Department of Computer Engineering
Software Engineering (ECEG-4201) Course Project
Semester 1, Year 2009 EC / 2016 GC
Report 1:- System Specification Document
Hotel Reservation Android App
For
Hotel Managers
Submitted by:
Biruk Tesfaw
ATR/4514/05
Bisratemichael Moges ATR/6015/05

Daniel G/Yohannes
ATR/3676/05
Dawit Samuel
ATR/1378/05
Yared Abera
ENR/1849/04
Submitted to:
Sahilu Wendeson
12 /12 /2016
Ethiopia, Addis Ababa
Software Engineering (ECEG 4201), Year 2009 EC/2016 GC
Individual Contributions Breakdown

Responsibility
Part 1: Functional
requirements
specification
Biruk
Tesfaw
30%
50%
Part 2:User Interface

Specification
Part 3: Domain Analysis
Part 4: Plan of work
Team Members and Contribution

Bisratemichael
Daniel
Dawit
Moges
G/Yohannes
Samuel
20%
20%
20%
10%
Yared
Abera
30%
50%
50%
50%
10%
10%
50%
Table of contents
Individual Contributions Breakdown ............................................................................................................. i
Table of contents .......................................................................................................................................... ii
List of Figures ............................................................................................................................................... iii
List of Tables ................................................................................................................................................ iv
1.
Functional Requirements Specification ................................................................................................ 1

a.
Stakeholders ..................................................................................................................................... 1
b.
Actors and Goals ............................................................................................................................... 1
c.
Use Case ............................................................................................................................................ 2
2.
I.
Description .................................................................................................................................... 2
II.
Use Case Diagram ......................................................................................................................... 6
III.
Sequence diagrams ................................................................................................................... 7
IV.
Traceability Matrix .................................................................................................................... 8
User Interface Specification .................................................................................................................. 9

a.
Preliminary Design ............................................................................................................................ 9
b.
User Effort Estimation ..................................................................................................................... 17
3.
Domain Analysis .................................................................................................................................. 20

a.
Domain Model ................................................................................................................................ 20

I.
Concept Definition ...................................................................................................................... 20
II.
Association Description............................................................................................................... 22
III.
Attribute Definition ................................................................................................................. 23
IV.
Traceability Matrix .................................................................................................................. 24
4.
Plan of work ........................................................................................................................................ 24
5.
Reference ............................................................................................................................................ 26
ii
List of Figures
Figure 1: Hotel Reservation App Use case .................................................................................................... 6
Figure 2: Customer Sequence Diagram ........................................................................................................ 7
Figure 3: Hotel Admin Sequence Diagram .................................................................................................... 7
Figure 4: System Admin Sequence Diagram ................................................................................................. 8
Figure 5:The search screen and The check-in screen ................................................................................... 9
Figure 6:Hotel Search Results ..................................................................................................................... 10
Figure 7:Room Search Result And Room Description ................................................................................. 11
Figure 8:Sign Up Page ................................................................................................................................. 12
Figure 9: Post Review Page ......................................................................................................................... 12
Figure 10: Payment Information ................................................................................................................. 13
Figure 11:Edit Profile................................................................................................................................... 13
Figure 12: Hotel Admin login page.............................................................................................................. 14
Figure 13:Edit Services Page ....................................................................................................................... 15
Figure 14: Special offers page ..................................................................................................................... 16
Figure 15: Domain Model Diagram ............................................................................................................. 20
iii
List of Tables
Table 1: Actors and Goals ............................................................................................................................. 1
Table 2: UC1 .................................................................................................................................................. 2
Table 3:Use Case 2 ........................................................................................................................................ 3
Table 4: Use Case 3 ....................................................................................................................................... 3
Table 5: Use Case 4 ....................................................................................................................................... 3
Table 6: Use Case 5 ....................................................................................................................................... 4
Table 7: Use Case 6 ....................................................................................................................................... 4
Table 8: Use Case 8 ....................................................................................................................................... 5
Table 9: Use Case 9 ....................................................................................................................................... 5
Table 10: Use Case 10 ................................................................................................................................... 5
Table 11: Traceability Matrix ........................................................................................................................ 8
Table 12: Concept Definition ...................................................................................................................... 21
Table 13....................................................................................................................................................... 23
Table 14....................................................................................................................................................... 24
Table 15....................................................................................................................................................... 24
iv
1. Functional Requirements Specification

a. Stakeholders
Hotels: They would like to use our system to manage and computerize hotels the hotel booking system.
As well as wanting to enable users to book hotel rooms online.
People who want to book hotel rooms: They could use the app to browse through the different hotels
found in the city. They could search through the different hotel rooms by names or by price.
Organizations that require services of the hotel: Organizations would like to book hotel rooms for their
guests. They will also want to view the different services given by the hotels which will be provided.
Advertisers: Organization that would like to advertise their products.
b. Actors and Goals

Actor
All Users
All Users
All Users
All Users
Signed Up User
Signed Up User
Signed UP User
Hotel Admins
Hotel Admins
System Admin
Goals
To look up for bookable rooms
To signup
Give Feedback
Pay Online
To Book Rooms
Manage personal account
Get preferences
Update Hotel Profile
Fetch Information
Add or Remove hotels
Use case
SearchInfo(UC1)
Signup(UC2)
GiveFeedback(UC3)
OnlinePayment(UC4)
BookRooms(UC5)
EditAccount(UC6)
Preferences(UC7)
UpdateProfile(UC8)
BrowseInforamtion(UC9)
AuthorizeHotels(UC10)
Table 1: Actors and Goals
System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

ATR/3676/05, Dawit ATR/1378/05, Yared ATR/1849/05
Hotel Reservation App
Addis Ababa, Ethiopia
1|Page
c. Use Case
I.
Description
Use Case UC-1:

Search Info
Related Requirements: REQ1,REQ2,REQ3
Initiating Actor:
All Users
Actors Goal:
To search for hotel rooms
Participating Actors:
System
Precondition:
App displays search page
Post condition:
Hotels rooms that satisfy the query are displays.
Failed End Condition: If the hotel is not found, it will show Sorry no hotels found, input correct hotel
name, and then returns to searching page.
Flow of Events for Main Success Scenario:
1,User clicks on searching button to enter searching page
2, System displays the searching page with the searching methods or keys, by price, by location etc.
3, User inputs the hotel name.
4, System searches for the hotel specified.
5, System displays the results.
6, User gets the required information, could then continue to book the hotel or exit app.
Flow of Events for Extension:
5(a) Information submitted does not exist.
<- System would display an error page, which reads Sorry no hotels found, input correct name and then
returns to start page.
Table 2: UC1
Use Case UC-2: Sign UP

Related Requirements: REQ7
Initiating Actor:
All Users that are not signed up
Actors Goal:
Create an account on the app
System
Precondition:
User does not have another account
Post condition:
User will have their own account and becomes a registered user
Failed End Condition:
If the user provides invalid information or already has an account
1, User clicks on the sign up button
2,System displays the details to fill for signing up, like personal information, email address, hello cash
account
3,User fills the information and clicks on the finish button
4, If successful the system displays successfully registered and returns to home page.
Flow of Events for extension:
3(a) information user submitted includes invalid cahracters.

2|Page

<-system would display an error page, which shows Please Input the correct Information and then
returns to 2.
3(b) The email user submitted has already been registered.
<-system display an error page, which shows The email has already been registered. Please re-sign up
and returns 2.
Table 3:Use Case 2
Use Case UC-3: Give Feedback

Initiating Actor:
All Registered Users
Actors Goal:
Submit feedback on hotel
System
Precondition:
User must be registered
Post condition:
Feedback would be posted
1,User logs in to account
2,Users clicks on hotel
3,User clicks on Reviews button and leaves feedback.
4,User clicks the post button to submit the review.
3(a)User clicks the cancel button
<-system would cancel the review
Table 4: Use Case 3
Use Case UC-4: Online Payment

Related Requirements: REQ5,REQ6
Initiating Actor:
Registered User
Actors Goal:
Pay Online
System
Precondition:
User must have a hello cash account
Post condition:
User will be able to able pay
Failed End Condition:
User will not be able to pay online
1,User logs in to system
2,User searches for hotel and selects preferred hotel
3,User selects services he would like to receive
4,User pays for the service
4(a) User doesnt have sufficient money
<-System will display Insufficient balance. And returns to 3.
3(a)User can cancel services he would like to purchase
Table 5: Use Case 4
Use Case UC-5:Book Rooms

3|Page

Initiating Actor:
Registered User
Actors Goal:
Book Rooms
System
Precondition:
User must be a registered user
Post condition:
User will book rooms
1,User logs in
2,User searches for available hotel rooms
3,User selects room
4,User books room
3(a) user pays online
Table 6: Use Case 5
Use Case UC-6:Edit Account

Initiating Actor:
Signed User
Actors Goal:
Edit account information such as paying information or paying account
System
Precondition:
User must be signed up
Post condition:
User edits account to their liking
1,User logs in to system
2,User clicks the edit account button
3,User edits account information such as paying information
3(a) User clicks on delete account
Table 7: Use Case 6
Use Case UC-8: Update Profile

Related Requirements:
REQ7,REQ4
Initiating Actor:
Hotel Admins
Actors Goal:
Update information on the hotel such as upcoming events, Hotel services,
New Hotel Packages
System
Precondition:
User must be authorized hotel admin
Post condition:
Hotels Services are updated
1,Hotel admin signs in to the system.
2,User clicks on update hotel
3,User clicks on services
4,User updates services to likings
5,User signs out
4(a) User updates new hotel packages

4|Page

Table 8: Use Case 8
Use Case UC-9: Browse Information

Initiating Actor:
Hotel Admin
Actors Goal:
Search for users information or use information in database for reports
System
Precondition:
User must be authorized hotel personnel
Post condition:
User will fetch data about their hotel
1,Hotel admin logs in to the system
2,Hotel admin clicks on users button
3,Hotel admin fetches information about user.
3(a)Hotel Admin fetches information for reports on the hotel
Table 9: Use Case 9
Use Case UC-10: Authorize Hotels

Initiating Actor:
System Admin
Actors Goal:
Authorize hotels who want to register to system
Hotel Admins
Precondition:
Hotel admin and system admin must have an agreement
Post condition:
Hotel will be inputted to the system
1,System admin logs in to the system at the system admins UI.
2.System admin creates profile of new hotel, inputs hotel name and initial password.
3,System admin logs out.
2(a) If hotel already has their own online system it will be integrated to the system.
Table 10: Use Case 10

5|Page

II.
Use Case Diagram
Figure 1: Hotel Reservation App Use case

6|Page

III.
Sequence diagrams
Figure 2: Customer Sequence Diagram
Figure 3: Hotel Admin Sequence Diagram

7|Page
Figure 4: System Admin Sequence Diagram
IV.
Req
REQ1
REQ2
REQ3
REQ4
REQ5
REQ6
REQ7
REQ8
MaxPW
TotalPW
Traceability Matrix
PW
5
4
3
3
3
2
2
1
UC1
X
X
X
UC2
UC3
UC4
UC5
UC6
UC8
UC9
X
UC10
X
X
X
X
5
10
UC7
2
2
X
1
1
3
5
6
3
X
1
1
X
X
2
4
3
5
X
5
8
3
5
Table 11: Traceability Matrix

8|Page
2. User Interface Specification

a. Preliminary Design
The default screen that the user will see is the search screen. In this screen the user first will specify the
hotel name or the city name in the search bar then by pressing the check-in button the user can set the
check-in date similarly the check-out date can be set in a similar manner ,furthermore the number of
room and guest can also be easily entered then finally the user will finish the process by pressing the
search button.
Figure 5:The search screen and The check-in screen
If the system finds a result matching the user request then it will display it and the user can browse
through the search results. Each option consists of the hotel name its star rating and also the price
The system also gives suggestion based on users past search history. The user can further select one
hotel and look through what service and amenities the hotel provides. Then they can browse through
the rooms by pressing the rooms button.

9|Page
Figure 6:Hotel Search Results
After pressing the Rooms button the user can view the available rooms in the hotel, just like before each
result contain the price of the room, then the user can select a room that suits them and proceed to
book the room by pressing the book button.

10 | P a g e
Figure 7:Room Search Result And Room Description
After the user pressed the book button then the user will be presented with the login screen, the user
will log into the account and proceed to the next stage. If the user doesnt have an account then the
user can sign up for an account.

11 | P a g e
Figure 8:Sign Up Page
The user also has the option to give feedback or review to the hotel they booked.
Figure 9: Post Review Page
Users can input their respective payment information

12 | P a g e
Figure 10: Payment Information
Users can also change their username,password and paymount account.
Figure 11:Edit Profile

13 | P a g e
The Admin Side

This is the index page for admin the admin, the admin must be logged-in in order to perform the
different services provided by the platform.
Figure 12: Hotel Admin login page
Once logged-in the admin can choose different actions like edit services & special offers, in edit services
the admin can change/update the service provided by the hotel.

14 | P a g e
Figure 13:Edit Services Page
In the special offers page the admin can change/update recent activity that the hotel will host
such as concerts, meetings or other offers.

15 | P a g e
Figure 14: Special offers page

16 | P a g e
b. User Effort Estimation

Use Case 1: SearchInfo
a.
b.
c.
d.
e.
Click search button on homepage

Type the hotel or city name in the input field
Input the number of guests
Input the number of rooms needed
Press the search button
Use Case 2:Signup

a. Click on the signup or create account button
----After completing data entry as shown below---b. Click submit button to finish
Data entry total
a. Click screen on user name text field
b. Input user name
c. Press on the next field
d. Input password
e. Press the next field
f. Input password again
g. Press the next field
h. Input email address
i. Press on the next field
Use Case 3: GiveFeedback
a. Log in to account
b. Click on hotel
c. Click on review button
----After completing data entry as shown below---d. Submit review
Data entry
a. Click on review field

17 | P a g e

b. Input review
Use Case 4:OnlinePayment

a. Click on log in to account
b. Click on hotel
c. Click on services to purchase
----After completing data entry as shown below---d. Click pay
Data Entry
a. Click on drop down service list
b. Click on service
c. Click on add service
Use Case 5:BookRooms

a. Click on Login to account
b. Click on search button
----After completing data entry as shown below---c. Click on book
Data Entry
a. Click on search field
b. Input hotel name
c. Click on number of rooms drop down list
d. Click on a number
e. Click on check in
f. Click on date
Use Case 6:EditAccount
a. Click on login
b. Click edit account
----After completing data entry as shown below---c. Click finish
Data entry
a. click on enter phone number

18 | P a g e

b. click on delete account
Use Case 8:UpdateProfile
a. press the user icon at the start screen
-----After completing data entry as shown below------b. press the done key to finish
a)
b)
c)
d)
e)
f)
g)
h)
Data entry
press the username text field
Change the username here
press the Change password Button
input the old password
press the New password Button
input the new password
press the change Account Button
input the new account details
Use Case 9:BrowseInforamtion
a. Click on sign in
b. Click on users list
c. View history on users
Use Case 10:AuthorizeHotels
a. Click on sign in
b. Click on add hotels
----After completing data entry as shown below---c. Click finish
Data entry
a. Click on hotel name
b. Input hotel name
c. Click on password
d. Input password
e. Click on next field
f. Input password again
g. Click on create hotel profile
The login details dont need to be filled every time after user is once logged in on the app. The app
will save the account login details.

19 | P a g e
3. Domain Analysis
a. Domain Model
I.
Concept Definition
The figure displayed below is a domain model diagram of our system. This Domain model
diagram was created with the use cases mentioned above in mind. We have also included a table
explaining the various concepts displayed in the image along with their associations.
Figure 15: Domain Model Diagram

20 | P a g e
Responsibility
key
concept
R1
Receive customer input about hotels
review
R2
make customer review available for hotel managers
review
R3
record customer that makes reservation
reservation
R4
record time of booking
reservation
R5
record room to be booked
reservation
R6
Gets booked by customer
room
R7
handles payment from customer
payment
R8
keeps record of payment transaction
payment
R9
keeps record of hotels location
hotel
R10 keeps record of hotels rating
hotel
R11 keeps description of hotel
hotel
R12 manages hotel information
hotel manager
R13 checks hotels reviews by customers
hotel manager
R14 sets events or offers to customers
hotel manager
R15 receive info from manager and notify customers via email
Event notifier
R16 creates hotels
System administrator
R17 authorizes hotel managers
System administrator
R18 take parameters from customer
search
R19 retrieve and display hotel information matching parameters
search
Table 12: Concept Definition

21 | P a g e
II.
Association Description
The below table describes the various associations defined in the domain concept diagram
concept pair
Association description
Association name
customer - reservation
a customer can make a reservation at

any given time
makes
payment - reservation
hotel reservation by customer will

involve payment, this association
signifies that
paid by
reservation - room
a room with status ( vacant/occupied )

is referenced in reservation
gets booked
room - hotel
a hotel has many rooms
has
hotel - hotel manager
a hotel is created and its data is

maintained by a hotel manager
creates/manages
hotel manager - system admin
a system administrator authorizes

hotel managers to create or make
changes to hotels
authorizes
customer - review
any customer has the option to write

reviews about hotels
write
hotel manager - review
hotel managers can view reviews about

their hotel
view
customer - event notifier
customers get notified of upcoming

offers and/or events
receive notice
hotel manager - event notifier
the hotel managers set events to notify

their customers of upcoming events
set
customer - search
customer can initiate a search of hotels
initiates

22 | P a g e
search - hotel
a customer initiated search will

retrieve data of hotels that match the
search criterion
retrieves information
Table 13
III.
Attribute Definition
Responsibility
Attribute
concept
R1
Receive customer input about hotels
Comment
R2
make customer review available for hotel managers
ShowManger
R3
record customer that makes reservation
User
R4
record time of booking
Date
R5
record room to be booked
Date
Reservation
R6
Gets booked by customer
status
room
R7
handles payment from customer
amount
R8
keeps record of payment transaction
record
R9
keeps record of hotels location
location
Review
Payment
R10 keeps record of hotels rating
KeepRecord
R11 keeps description of hotel
description
R12 manages hotel information
UpdateInfo
R13 checks hotels reviews by customers
CheckReview
R14 sets events or offers to customers
UpdateInfo
Hotel Manager
R15 receive info from manager and notify customers via email
description
Event notify
R16 creates hotels
CreateProfile
System Administrator
Hotel

23 | P a g e

R17 authorizes hotel managers
Authorize
R18 take parameters from customer
TakeInput
R19 retrieve and display hotel information matching parameters
SearchAndDisplay Search
Table 14
IV.
Traceability Matrix
Domain Model
Customer
Payment
Reservation
Review
Room
Hotel
Event Notifier
Search
Hotel Manager
System Admin
UC1
X
X
X
X
UC2
X
X
X
X
X
X
X
UC3
X
UC4
X
X
UC5
X
X
X
X
X
UC6
X
X
X
UC7
X
UC8
UC9
UC10
X
X
X
X
Table 15
4. Plan of work
We plan on tackling this project in 3 different parts. Namely Data Gathering, Website, App and
UI design and Website and App programing.
We have already done the first phase as we submitted the project proposal. It took us around
two weeks to gather the necessary information, such as systems that are widely applied, issues in the
current system, ways to solve this issues. Each of the 5 group members participated in collecting the
information. We collected information by directly going to hotels and observing the currently used
system. We also asked frequent hotel users questions on the current system, faults or problems they
have faced and what they would do to solve those issues. We then based our project on this collected
information.
We have started on Website, App and UI design after we finished gathering information. This
will take a lot of time as this will be an integral part in the development of the project. The UI design will
be done mainly by Bisrat and Daniel. They will be responsible in designing an easy on the eye graphics as
well as designing the system. They will be the ones who will discuss in detail about the UI design to the

24 | P a g e

other members. They will design the system on the user side (App), from the hotel admin side, the
receptionist and from the system admin side which are all websites.
This phase will be started as soon as the UI designers finish the design. This phase will be mainly
done by Biruk and Dawit while Yared designs the back end database. Those three will work very closely
in trying to achieve maximum efficiency. This will be done in 3 up to 4 weeks. The other members will
also be given some modules to program as this will be to vast to handle for two.
Alongside this phases or tasks, group members will be in continuous discussion on how to
progress and check on progresses made. Any alteration to be made on the project will be discussed and
changed accordingly.
Figure 26: Plan Of Work Timeline

25 | P a g e
5. Reference
1. Report 1, Prepared by: Yuanxi Li, Xiaoran Fan, Lun Li, Jingsong Yuan, Tian Xie
2. Slides on domain analysis, Supplied to us by Sahilu Wendeson

26 | P a g e

Software Engineering Course Project Hotel Reservation Android App

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Engineering Course Project Hotel Reservation Android App

Uploaded by

Copyright:

Available Formats

Addis Ababa University

Addis Ababa Institute of Technology (AAIT)

Bisratemichael Moges ATR/6015/05

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Individual Contributions Breakdown

Part 2:User Interface

Part 3: Domain Analysis

Part 4: Plan of work

Team Members and Contribution

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Functional Requirements Specification ................................................................................................ 1

Actors and Goals ............................................................................................................................... 1

Use Case ............................................................................................................................................ 2

Use Case Diagram ......................................................................................................................... 6

Sequence diagrams ................................................................................................................... 7

Traceability Matrix .................................................................................................................... 8

User Interface Specification .................................................................................................................. 9

Preliminary Design ............................................................................................................................ 9

User Effort Estimation ..................................................................................................................... 17

Domain Analysis .................................................................................................................................. 20

Domain Model ................................................................................................................................ 20

Concept Definition ...................................................................................................................... 20

Attribute Definition ................................................................................................................. 23

Traceability Matrix .................................................................................................................. 24

Plan of work ........................................................................................................................................ 24

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

1. Functional Requirements Specification

b. Actors and Goals

Table 1: Actors and Goals

System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Use Case UC-1:

Use Case UC-2: Sign UP

System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Use Case UC-3: Give Feedback

Use Case UC-4: Online Payment

Use Case UC-5:Book Rooms

System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Use Case UC-6:Edit Account

Use Case UC-8: Update Profile

System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Use Case UC-9: Browse Information

Use Case UC-10: Authorize Hotels

System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Use Case Diagram

Figure 1: Hotel Reservation App Use case

System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Figure 2: Customer Sequence Diagram

Figure 3: Hotel Admin Sequence Diagram

System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

Figure 4: System Admin Sequence Diagram

Table 11: Traceability Matrix

System Specification Document |Biruk ATR/4514/05, Bisratemichael ATR/6015/05, Daniel

Software Engineering (ECEG 4201), Year 2009 EC/2016 GC

2. User Interface Specification

Figure 5:The search screen and The check-in screen