INFOSYS 220 Assignment 2: System Proposal and Use Case Modelling

This assignment presents a comprehensive requirements definition report for a system proposal, focusing on use case modeling within the INFOSYS 220 course at the University of Auckland. The document begins with functional requirements, detailing services, payment options, staffing roles, and system reminders. It then outlines non-functional requirements related to usability and performance. User stories are provided from the perspectives of corporate clients and case consultants, followed by a use case model and detailed documentation for creating a service request (UC001). The documentation includes preconditions, success and failure post-conditions, normal, alternate, and exception flow steps, along with non-functional requirements. An activity diagram is also included. References are provided at the end of the document.

INFOSYS 220
ASSIGNMENT 2
USE CASE MODELLING
Semester 1 2019 Individual Assignment Template
1. REQUIREMENTS DEFINITION REPORT
Functional Requirements:
1. Service
1.1 A client should be able view accommodations on the basis of criteria given.
1.2 A client should be able to register on the proposed system.
1.3 A client should be able to submit rental service details such as furniture rental,
monthly expenditure, housing rental, etc.
1.4 A client should be able to provide housing preferences.
1.5 A client should be able to send queries/suggestions to the company.
1.6 A staff can update details of properties / accommodations.
2. Payment
2.1 A client should be able to make payment in the current system via payment gateway.
2.2 The proposed system should allow users to make payment through different options.
3. Staffing
3.1 An admin staff should be able to manage all the requests of the clients.
3.2 A staff should be able to assign a case consultant to required corporate case.
3.3 A staff should be able to add, remove or update a property in the system.
4 Others?
4.1 The system should be able to send reminders to respective users.
4.2 System administrators should be able to initiate backups and overwrite the access
control lists.
Non-functional Requirements:
1. Operational / Usability?
INFOSYS 220 Assignment 2 |
Page 1 of 8

1.1 An user can request for the service through web or mobile interface.
1.2. Success/failure messages should be displayed appropriately at respective steps.
1.3. The interface of the application should be easy-to-use and must have low learning
curve.
1.4. Previous and next button should be present on the system screens.
2. Performance?
2.1 Response time should be less than 5 seconds
2.2 At any point of time, system should be able to handle any number of requests.
2.3 The proposed system will be accessible to any browser or underlying hardware.
2.4 The client should be provided with the confirmation messages when a request is
posted successfully.
2.5 Once the payment is made, the system should generate an invoice of the respective
payment.
4. Cultural and Political?
4.1 No special cultural and political requirements are anticipated.
INFOSYS 220 Assignment 2 |
Page 2 of 8

2. USER STORIES
Corporate client
As a Corporate client, I want to register so that I can submit my house rent or other renting
services.
As a Corporate client, I want to manage payments so that no overdue is charged on my
employees.
As a Corporate client, I want to manage the quotations so that budget remains under control.
As a Corporate client, I want to confirm corporate case so that compulsory details are not missed
out.
Case consultant
As a case consultant, I want to manage all queries so that timely responses can be sent to the
customers.
As a case consultant, I want to manage all the cases assigned to me so that I can update the case
information for the team.
(Ghai and Kaur, 2012)
INFOSYS 220 Assignment 2 |
Page 3 of 8

3. USE CASE MODEL
INFOSYS 220 Assignment 2 |
Page 4 of 8

4. USE CASE DOCUMENTATION
USE CASE # UC001 Priority: 1
Goal in Context Create service request
Trigger event &
Type
Personal client wants to request for a moving service
Primary actor(s) &
Secondary actor(s)
Primary actor – Client
Secondary actor – System
Related use cases -
Preconditions Client has valid username and password and is logged in the
proposed system.
Success post
condition
Client has successfully posted a new moving service request.
Failure post
condition
Client is unable to post a new request.
NORMAL FLOW
steps (NF) Action
1. Client clicks on “Post request” URL.
2. System displays a form with details – Arrival location,
destination location, number of persons to move, arrival date and
a “Submit” button.
3. Client enters the information and clicks on the submit button.
4. a. Success – System generates an unique case number and
displays it to the user.
ALTERNATE
FLOW steps (AF) Action
4b Client does not enter all mandatory information, system displays
error message – “Please enter all information”
Client enters alphabetic letters in Number of persons to move”,
the system displays “Please enter numeric values ”. (Hudda,
Mahajan and Chopra, 2016)
EXCEPTION Action
INFOSYS 220 Assignment 2 |
Page 5 of 8

FLOW steps (EF)
NA
Non-functional
requirements
The system should provide prompts for every next step and the
font size and color should facilitate the user experience.
INFOSYS 220 Assignment 2 |
Page 6 of 8

5. ACTIVITY DIAGRAM
REFERENCES
INFOSYS 220 Assignment 2 |
Page 7 of 8

Ghai, S. and Kaur, J. (2012). Analysis of User Requirements Gathering Practices in Agile and Non-
Agile Software Development Team. International Journal of Computer Applications, 58(8),
pp.13-18.
Hudda, S., Mahajan, R. and Chopra, S. (2016). Prioritization of User-Stories in Agile Environment.
Indian Journal of Science and Technology, 9(45).
INFOSYS 220 Assignment 2 |
Page 8 of 8