Information System - Requirements Elicitation and UML Modelling

This article discusses the requirements elicitation and UML modelling for an online dating system. It covers the major requirement gathering techniques, strategies formulation, user scenarios, functional requirements, use case descriptions, and more.

Running head: INFORMATION SYSTEM
Information System
Name of the Student:
Name of the University:
Author Note

1
INFORMATION SYSTEM
Table of Contents
Task 1: Requirements elicitation.....................................................................................................2
Answer to question number 1......................................................................................................2
Answer to question number 2......................................................................................................2
Task 2: Requirements specification and UML modelling...............................................................3
Answer to question number 3......................................................................................................3
Answer to question number 4......................................................................................................3
Answer to question number 5......................................................................................................4
Answer to question number 6......................................................................................................4
Answer to question number 7......................................................................................................5
Answer to question number 8......................................................................................................6
Answer to question number 9......................................................................................................7
Answer to question number 10....................................................................................................8
Answer to question number 11....................................................................................................8
Answer to question number 12....................................................................................................8
Bibliography....................................................................................................................................9

2
INFORMATION SYSTEM
Task 1: Requirements elicitation
Answer to question number 1
The major requirement gathering techniques are:
 Document Analysis
 Brainstorming
 Interface Analysis
 Observation
 Focus group
 Survey
 Interview
 Prototyping
 Reverse engineering
 Requirement workshop
However for the development of the proposed system only the Brainstorming, Document
Analysis, Requirement and Interface Analysis procedures should be done.
Answer to question number 2
The main strategies formulation would consists of the brainstorming sessions followed by
the Document Analysis, Requirement Workshop and Interface Analysis. The steps and method
that are to be followed are provided below:
Brainstorming: For the development of the system, a few brainstorming sessions should be held
as what additional features can be added to the system in addition to the existing requirements
provided by the organization. The brainstorming session would also define the possible paths for
the user to navigate through the system. The designing and the interface for the system are also
to be thought of in the brainstorming sessions.
Document analysis: The document analysis would provide the developers to study
documentation of other social networking websites so that they would get idea of procedures of
the system and this would help them to organize the process of the system accordingly. For
example the case studies regarding Facebook and the documentations available for the website
would be very useful in the development of the system (Facebook.com, 2018). The data from the

3
INFORMATION SYSTEM
brainstorming would be used in this session so that a clear strategy can be formulated for the
development of the application.
Requirement Workshop: In this session the developed ideas would be used and newer ideas
would be developed for the actualization of the system. The platform of system design and the
backend procedures that are to be thought of in this phase. The data would be very important as
this stage would help in finalizing the platform for development.
Interface Analysis: After the platform for the system has been decided the interface ideas of the
system is to be developed. The interface Analysis would help the developers to analyze the
interface of the system. In this process they can study the interface of the other dating
applications such as Tinder (Tinder, 2018). It help the developers to understand the navigation
and other front end features of the application.
Task 2: Requirements specification and UML modelling
Answer to question number 3
User Scenario one: The student of the Macquarie University is looking for a friend in the
campus and logs in to the system by using his eStudent Identification an after the student is
logged in he looks for possible matches. After the student finds a match he sends a request for
connection to the match. Since the user is a premium user he is able to send a message that is
included with the request. The user then logs out of the system after the completion of the
process.
User Scenario two: The manager logs into the system using the administrator Id and looks for
the notification that have arrived regarding the abuses in the system. He sees only a single case
registered and the follows up the case. He fetches the id of both the parties and investigates. He
feels that the complain is a genuine one and suspends the accused for three weeks.
Answer to question number 4
Students User Story: As a Student I would like to log in to the system by using my eStudent
Identification and obtain a list of matches according to my requirements. I would like to have the
option of filtering my search result. I would also like to select a particular person that fulfills m y
needs and also send a request for connecting with me. I would also like to upgrade my account to
a premium one and obtain additional benefits of the premium account. I would also like to have

4
INFORMATION SYSTEM
the option of downgrading my account to a lower level with less amount of facilities according to
my choice. After all the activities I should be able to log out of the system successfully.
Staff User Story: As a staff of the system I should be able to log into the MQ Notification
System using mu Staff identification and receive the notices about the abuses registered into the
systems and review the case. I would also like to approve the requests of the students to delete
their account directly. I should be able to both approve and reject the request of account deletion.
Manager User Story: As the manager of the system I would like of log in to the system and view
the cases registered into the system and view the list of reported abuses. I would like to have the
option of taking actions against the ones who are found guilty for the reported cases.
Answer to question number 5
The main functional requirements of the system are:
 Firstly there should be two types of account in the system. The students would only be
allowed to avail the special privileges if their accounts are premium ones. The up
gradation facility should also be provided in the system so that students can upgrade their
accounts anytime they want to. They should also be allowed to downgrade their account
in case they no longer have the need for the premium account.
 Secondly, the Dating should have the notification facilities where the system would be
notifying the user and the staffs of the system in case some events take place in the
system. The system should provide the user with an immediate notification.
Answer to question number 6
The functional requirements of the system are:
User Interface: the User Interface and navigation in the system should be implemented
efficiently so that the users does not face any problems in the system
Data Integrity: the data of the system should be stored safely so that the user data is not leaked
out so that it is secures the privacy of the users.

5
INFORMATION SYSTEM
Answer to question number 7
1 MUDS Data Store
1
Macquarie
University Dating
System
students
Staffs
Manager
2
MQ Notification
System
3
MQ Financial
Services System
6
Send Request
7
Recieve Notification
8
View complains
9
Take diciplinary
Action
10
Admin Notification
11
Upgrade services

6
INFORMATION SYSTEM
Answer to question number 8
Students
LogIn
eStudent Login
Admin Login
Staff
Manager
View matches
Send Request
Send Request with a Messgae
Send Gifts
Delete account
Delete Account Confirmation
Check Notification
Staff Notification
Manager Notification
Review Notification
Diciplinary Actions

7
INFORMATION SYSTEM
Answer to question number 9
Use Case description 1:
Use Case Id UC4
Use Case Name View Match
Description The students would be able to view their matches
Actors The Student
Precondition The student should be logged in
Post condition The student would be able to send request
Basic Course 1.login
2.verify
3.view list
Alternate Course Not Applicable
Use Case description 1:
Use Case Id UC6
Use Case Name Send Request Message
Description The students would be able to send message with the request
Actors The student
Precondition The profiles should be matched
Post condition The profiles would be able to exchange messages
Basic Course 1. view list
2. match profile
3. Send request message
Alternate Course 1. upgrade account
2. view list
3. match profile
4. Send request message

8
INFORMATION SYSTEM
Answer to question number 10
logIn()
upgradeService()
upgradeAccount()
sendRequestMessage()
forwardMessage()
Notification
SequenceDiagram_1
MUDS MQNS MQFSS
Student
Answer to question number 11
0..1
0..*
0..1
0..*
Compaitibility
-
-
-
user1
user2
matchStatus
: int
: int
: boolean
Student
- eStudent : int
Staffs
+
-
-
StaffsId
Name
Salary
: int
: String
: float
Profile
#
+
+
eStudent
Name
Picture
: int
: String
: String
Manager
#
#
#
StaffId
Name
Salary
: int
: String
: float
Answer to question number 12
Open Account Upgrade Account
Downgrade Account
Account Deleted

9
INFORMATION SYSTEM
Bibliography
Contreras, B. and Krauss, S.S., 2017. MDG Profile for CAST: UML Extension for CAST
(Causal Analysis based on STAMP).
Decker, M.J., Swartz, K., Collard, M.L. and Maletic, J.I., 2016, October. A tool for efficiently
reverse engineering accurate UML class diagrams. In Software Maintenance and Evolution
(ICSME), 2016 IEEE International Conference on (pp. 607-609). IEEE.
Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
Facebook.com. (2018). Facebook – log in or sign up. [online] Available at:
https://www.facebook.com/ [Accessed 5 Apr. 2018].
Imran, M., Haque, I., Rahman, M. and Asfat, K., 2018. E-commerce System (MIK Online Shop)
(Doctoral dissertation).
Kaslow, D., Anderson, L., Asundi, S., Ayres, B., Iwata, C., Shiotani, B. and Thompson, R.,
2015, March. Developing a CubeSat Model-Based System Engineering (MBSE) Reference
Model-interim status. In Aerospace Conference, 2015 IEEE (pp. 1-16). IEEE.
Tinder. (2018). Tinder | Swipe. Match. Chat.. [online] Available at: https://tinder.com/ [Accessed
5 Apr. 2018].