Teaching and Learning Activity Suggested Solutions

Module: Systems Analysis and Design 3 (HSAD300-1)

Week number (Date): 2 (26 August 2021)
Unit covered: Unit 2

Question 1
As a systems analyst at the University of Pretoria. The organization is seeking ways to improve its
service desk facility. The service desk makes use of calls to report IT related issues. Unfortunately,
these calls are not attended to timeously and as a result issues are not addressed without the ability
to track status of a query.

You decide to solve this problem through the introduction of a mobile application. This application
provides a platform for employees to log IT related queries to relevant departments, which is then
assigned to a technician.

Activity 2 is based on Unit 2 of the prescribed courseware for this module.

1.1 Draw up a context diagram for the intended application.

Suggested solution:

(Unit 2 Page 29: Study Guide)

1 HSAD300-1-Jul-Dec2021-TL-W2-PC-V.1_SS-17082021
1.2 Draw up a class diagram for the intended application

Suggested solution:

(Unit 2, page 155-157)

1.3 Draw up a swim lane and information flow diagram

Suggested solution:

(Unit 2, page 144,148,183-184)

2 HSAD300-1-Jan-Jun2021-TL-W2-PC-V.1_SS-23022021
Question 2
For virtually every application or artefact there exists functional and non-functional requirements.
Functional requirements could be described as the core operational objectives the proposed
system must perform. E.g. the system must generate a report.

While non-functional requirements deals with constraints, soft goals, and quality attributes of the
proposed system E.g. how soon must the report be generated, which is an issue of performance.

Required:
From the grid below find all the possible non-functional requirements and discuss briefly the found
non-functional requirements in relation to the application.

F T I N T W A W G I O Y H M D D
Q S G F I H I H J L O P V A H T
W P F H D E G J U B D C V G J R
E E E A H U I W B D N Y C Z D C
R R O M A H S E C U R I T Y R V
T F L W M Y C A T G I V D X F B
Y O T G W J A B B I M T U X T M
U R W H G O L V E I T M S W Y L
I M I T H T A E E G L C C R H P
O A S A I T B T R H J I A H B O
P N I N T O I G F F E N T I U I
P C H O M L L C D D D T W Y J K
O E F F I C I E N C Y I N Q M H
I L K J H F T G F D S V B A N N
A S D F G H Y V F E W S A X A A

Suggested solution:
• Performance
Considering it is a mobile application, it should be able to run on Android OS 4 and above.
User experience will be based on the specification application is running on.
• Efficiency
The application will process transaction as soon as changes are made by either user (Issue
logging by lecturer, and status changing by technician).
The application will send instant notifications to parties involved, therefore new incident ID
logged, and status notification by means of tracking number/ audit log is produced.
On resolution of a query, ID is sent to archive list for historical and referential purposes
• Security
User authentication and the use of OTP’s will secure access only to authorized persons
• Scalability
There should be a growth prospect, meaning there should be room for expansion of the
application, the growth prospect may require new criteria or functionality of not only the
lecturers but also the admin and support staff. Implementation of load-balancing depending
on demand.
3 HSAD300-1-Jan-Jun2021-TL-W2-PC-V.1_SS-23022021
 • Usability
The application will be user friendly, making use of interactive features. The application will
make use of menu’s and buttons to reduce the amount of typing by the user, this is to avoid
incorrect input from the user such as incorrect spelling.

4 HSAD300-1-Jan-Jun2021-TL-W2-PC-V.1_SS-23022021