ITECH2002 - SYSTEMS MODELLING Name of student Name of university Author's note: Fully developed use case description 1 2 Fully developed use case description 2 3 Activity diagram 1 5 Activity diagram

Running head: ITECH2002 – SYSTEMS MODELLING
ITECH2002 – SYSTEMS MODELLING
Name of student
Name of university
Author’s note:

1
ITECH2002 – SYSTEMS MODELLING
Table of Contents
Fully developed use case description 1..........................................................................2
Fully developed use case description 2..........................................................................3
Activity diagram 1..........................................................................................................5
Activity diagram 2..........................................................................................................6
System sequence diagram 1...........................................................................................7
System sequence diagram 2...........................................................................................8
Screen design.................................................................................................................9
Test plan.......................................................................................................................11
Bibliography.................................................................................................................15

2
ITECH2002 – SYSTEMS MODELLING
Fully developed use case description 1
Use Case name Record ticket
Scenario Manual tickets are added to the issues that have been raised by the gigsters
and approved by the hub administrators
Brief description When the gigsters faces the issues with any device or any applicance, the
gigsters raises the issues and forwards to the hub administrators. The hub
administrators verifies the issues and then creates the ticket for that issue.
This ticket is then assigned with the appropriate individual for resolving the
issue.
Actor Administrator
Related use case Issue raised, ticket approved
Trigger Gigsters raises an issue that has been by them
Primary Scenario 1. The record has been approved by the administrator after proper
verification.
2. The record ticket has been successfully created and then an individual
has been assigned for resolving the issue.
3. If any outside help is required, then the outside help is contacted and
then issue is resolved
Stakeholders Gigsters, manager, administrator
Pre-Conditions Gigsters has raised an issue in the system
Post-Conditions The system provides the successful notification of issue resolving.

3
ITECH2002 – SYSTEMS MODELLING
Exception
conditions
None
Flow of activities Actor System
1. Gigsters login into the system
2. Gigsters raises the issues in the
company
3. Hub administrator receives the
notification of the raised issue
4. Hub administrator then creates
the work ticket upon successful
verification of the issue raised by
the gigster
1. System verifies the gigster
credentials and then provides the
access to the system
2. System receives the details of the
issue
3. System displays the list of all the
details of raised issues
4. System successfully creates the
work ticket and assigns any
particular individual
Fully developed use case description 2
Use Case name Assign food supplier for hub
Scenario The manager of the company assign the food supplier for the hub that has
been created recently.