INFOSYS 220 Semester 2 2019 Assignment 2: Use Case Modelling

This document presents a comprehensive solution for INFOSYS 220 Assignment 2, focusing on requirement modeling, use case modeling, and system design. The assignment begins with a Requirement Definition Report, outlining both functional and non-functional requirements for the SMARTy-NZ system. Functional requirements detail features such as customer booking options, customer identification, single sign-on, loyalty program integration, remote check-in, event access, staff access to training information, and chatbot integration. Non-functional requirements address operational usability, performance, security, and cultural considerations. The document then provides user stories from the perspectives of customers and hotel staff, followed by a Use Case Model illustrating interactions between actors (customer, management, staff, chief) and the system. Detailed Use Case Documentation is presented for the "Create Booking" use case, including preconditions, success/failure post-conditions, normal, alternate, and exception flows, and non-functional requirements. An Activity Diagram visually represents the "Create Booking" use case. The assignment references relevant academic sources to support the analysis and design decisions.

INFOSYS 220
ASSIGNMENT 2
USE CASE MODELLING
Semester 2 2019 Individual Assignment Template
1. REQUIREMENTS DEFINITION REPORT
Functional Requirements:
1. The customer shall be able to choose between the two options as all-meal-inclusive or pay
as you dine at the time of booking.
1.1 The mix and match option shall be given to the customers
2. The customer identification shall be done using QR code/Mobile App
3. Single Sign-on feature for user access
4 Ability to join and subscribe to the loyalty program for the existing and new customers
4.1Allocation of reward points when an existing customer recommends a new one
4.2 The customers shall be able to use their reward points as Air NZ points at the time of
booking (Tang, 2016)
5. The customers shall be able to check-in remotely through kiosks or smart mobile app.
5.1 The automated alert shall be sent to the hotel staff as soon as a customer checks in
6. Ability to access updated customer schedule through the app
7. The customers and staff members of the hotel shall be able to access the event details
through app, kiosks, or via room
7.1 The customer shall be able to make reservations for the event
7.2 The customer shall be able to provide feedback on the event
8. The confirmed occupants list shall be accessible to the hotel staff
9. Hapu staff shall be able to access the training information from the system
10. Chatbots shall be integrated in the application for providing customer support and
services
11. The staff members shall be able to securely log in through biometric-based recognition
system using fingerprint scanning or voice recognition
12. The system shall allow the account updates within two hours of the meal/service
INFOSYS 220 Assignment 2 |
Page 1 of 9

12.1 The billing information shall be available and accessible via the system
13 The application shall allow the access to the personalized souvenir which shall be
collected at the time of check-out (Zhao, 2018)
Non-functional Requirements:
1. Operational / Usability
1.1The application shall be easy to navigate and access
1.2 The application shall have consistent layout
2. Performance
2.1Low response time
2.2 Low throughout time
3. Security
3.1User session management for security - SSO
3.2 Network security and safety
4. Cultural and Political
4.1 The system shall allow multi-lingual support with the ability to switch languages to the
user
2. USER STORIES
As a customer, I would like to easily check-in to the hotel through the application so that I don’t
have to wait at the hotel.
As a customer, I would like to access the event details so that I may enjoy the preferred events of
my choice.
As a customer, I would like to choose between the options at the time of booking so that I may be
able to select the best option as per my preferences (Hudda, Mahajan & Chopra, 2016).
As a customer, I would like to use the reward/loyalty points at the time of booking for overall cost-
savings
As a hotel staff, I shall have the details of the customers provided in time so that I may plan my
activities accordingly.
As a hotel staff, I would like to have the details of events and activities so that I may provide the
services accordingly.
As a staff, I shall be able to access the training information and details so that I may enhance my
INFOSYS 220 Assignment 2 |
Page 2 of 9

skills
As a hotel staff, I would like to securely log in to the system so that the information safety is always
maintained.
3. USE CASE MODEL
The use case model is the representation of the interaction of different types of users with the
system. It is developed in order to present the user goals and expectations from the system, user-
system interaction levels, and the system behaviour with the users. The use case model for
SMARTY-NZ management system is shown in the diagram below. There are four types of users
that are involved with the system as customer, management, staff, and chief. These users are termed
as actors and the use cases that are mapped with these users are referred as actions. The mapping of
these actions and actors is done for the system in the diagram represented below.
INFOSYS 220 Assignment 2 |
Page 3 of 9

INFOSYS 220 Assignment 2 |
Page 4 of 9

4. USE CASE DOCUMENTATION
The use case description for the Create Booking use case is covered in the table below.
USE CASE # 1 Priority:
Goal in Context The customer shall be able to create the booking through the
system as per the preferred dates and food choices.
Trigger event &
Type
Customer access the system and logs in to the system
Primary actor(s) &
Secondary actor(s)
The customer is the primary actor for the use case and the system
is the secondary actor
Related use cases Join loyalty program, Check-in, Finalize Booking
Preconditions The system shall be connected to a network
The customer shall have a mobile device to access the
application
Success post
condition
The customer is provided with the invoice regarding the booking.
The departments receive the booking information as soon as the
customer makes the payment.
Failure post
condition
The invoice details are not provided to the customer due to
payment failure/system error.
NORMAL FLOW
steps (NF) Action
1. Customer
logs in to the
system
The system presents the welcome screen to the new/existing
customer.
2. The system
checks the
member
loyalty
program
status for
existing
customer
The reservation screen is displayed to the customer if he/she is
the member of the loyalty program
3. Customer
enters the
reservation
dates
The system presents the food facility options for the customer
4. The customer
provides the
food choices
by specifying
the dates for
mix and
match and
confirms
The system provides the final billing amount calculated on the
basis of the loyalty points and discounts applied.
5. Customer The system sends the information to all the departments to assign
INFOSYS 220 Assignment 2 |
Page 5 of 9

views the
invoice
chief, assign & receive whanau color.
ALTERNATE
FLOW steps (AF) Action
2. The system
checks the type of
member as the new
member
The reservation screen is shown to the new customer.
2. The system
checks the type of
member as existing
customer without the
membership for
loyalty program
The loyalty points are calculated for the customer
3. Customer enters
the reservation dates
The dates entered by the customer are not available and the
customer is asked to enter new dates
EXCEPTION
FLOW steps (EF) Action
1. Existing
Customer
enter
incorrect
customer
id/password
The system does not allow the customer to log in and is provided
with a message as invalid credentials
4.The food options
provided by the
customer are not
available.
The customer is provided with the information and is asked to
make new choices.
Non-functional
requirements
1. The system shall be secure – It shall authenticate the user
(customer) on the basis of the credentials provided and as
per the details entered.
2. The system shall be platform-independent – The user
shall be able to access the application on Apple as well as
Android platforms.
3. Performance – The entire process shall take place quickly
and the response time for each action shall be low.
INFOSYS 220 Assignment 2 |
Page 6 of 9

5. ACTIVITY DIAGRAM
Activity Diagram is a significant diagram under the Unified Modelling Language (UML). The
dynamic aspects of the system are developed and represented with the aid of the activity diagram.
The diagram is developed in the form of a flow chart which is used to represent the interaction of
different system activities and elements with each other. The activity diagram for the use case as
create booking is depicted below. There are a number of steps that are involved in this particular
activity and the representation of the same has been done.
INFOSYS 220 Assignment 2 |
Page 7 of 9

INFOSYS 220 Assignment 2 |
Page 8 of 9

REFERENCES
Hudda, S., Mahajan, R., & Chopra, S. (2016). Prioritization of User-Stories in Agile
Environment. Indian Journal Of Science And Technology, 9(45). doi:
10.17485/ijst/2016/v9i45/105069
Tang, A. (2016). Mobile App Monetization: App Business Models in the Digital Era. International
Journal Of Innovation, Management And Technology, 224-227. doi:
10.18178/ijimt.2016.7.5.677
Zhao, J. (2018). Hotel Management System Integration Services. Destech Transactions On
Economics, Business And Management, (eced). doi: 10.12783/dtem/eced2018/24001
INFOSYS 220 Assignment 2 |
Page 9 of 9