ITECH2002 - Systems Modelling: Hub Management System Assignment 1

This report presents a system analysis and design for a Hub Management System, focusing on the documentation of functional requirements. It includes user stories, a user goal table, and detailed use case descriptions, illustrating the interactions between system actors such as administrators and gigsters. The report features a use case diagram that visually represents the system's functionalities, including registering complaints, managing meal requests, and handling work tickets. A domain class diagram outlines the system's structure, defining classes like gigsters, admins, and work tickets, along with their attributes and operations. The assignment demonstrates how to model a system using industry-standard techniques to specify system requirements and how different stakeholders contribute to the definition of requirements. The report concludes by summarizing the system analysis and design process, emphasizing the importance of use case scenarios and domain class diagrams in system development, and referencing relevant literature.

HUB MANAGEMENT
Contents
INTRODUCTION.......................................................................................................................................2
USER STORIES..........................................................................................................................................2
A USER GOAL TABLE................................................................................................................................3
USE CASE DESCRIPTION...........................................................................................................................3
USE CASE DIAGRAM................................................................................................................................4
DOMAIN CLASS DIAGRAM.......................................................................................................................5
CONCLUSION...........................................................................................................................................6

INTRODUCTION
Over the years, there have been developments in the field of business and entrepreneurship. The
increased number of client and diversity in their preferences has resulted in new niches in the
business environment. Traditional methods of handling the clients' requirements are becoming
incompetent as the number of clients and functionalities increase. Nonetheless, the advancements
in information technology have introduced a better solution. The development and
implementation of a software system and resources ensure effectiveness and efficiency of
resources. The proper implementation of information technology resources has made it possible
for organizations to meet their requirements and those of the clients (Dutta, Geiger & Lanvin,2015).
USER STORIES
A use case story shows a full cycle of interaction between the system and one or more actors in
the system (Hecht & Jablonski, 2011). The Hub Management subsystem has several Use-case
scenarios, one of them being recording a ticket automatically or manually or making meal
services.
a) Recording a Ticket
The administrator receives communication from a gigster complaint or information sent from a
sensor, this information is used to generate a work ticket assigned a state of ‘open’. The ticket is
then assigned to someone on the notification/ alert notice. The automatically generated tickets
can be picked deliberately by any of the notification-notice personnel. The administrator assigns
a manually generated ticket. Some of the tickets need outsourcing; the administrator selects a
registered party to handle the task. A work specification is generated and electronically sent to
the picked organization
b) Meals
The gigster starts by requesting a meal; this generates a notification sent to the administrator of
the Management Hub. The administrator has to examine the order request from the gigster if
acceptable or not. If not acceptable, the administrator sends an email requesting the gigster to
change the order. The gigster can choose to make the changes or leave the order to lapse. If the
request is acceptable, the administrator generates an order to the food supplier.

The administrator physically administer the delivered food to the gigster and notifies them of the
charges
A USER GOAL TABLE
AGENT GOAL TASK SUBJECT
System Recording
the work
tickets
The system records both the tickets generated
manually by the administrator and the ones
automatically generated by the system
Work ticket
Gigster Requesting
meal
The gigster makes a request to the administrator
requesting for a meal. If approved order is created if
not, the administrator sends an email requesting an
update. The gigster can decide to either make the
recommended alterations or let the request lapse.
Meal order
USE CASE DESCRIPTION
ACTOR USE CASE DESCRIPTION SUBJECT
Admin Facilitate
operations
Taking care of all the resources of the
system
Resources
System Generating
ticket
The system automatically generates
tickets
Tickets
Admin Generating
tickets
Register complains from gigster and
creates tickets
Tickets
Gigster Meal request Gigster sends a notification to the
admin for food orders
Meal
Gigster Correcting
request
Notifications from the admin on
changing the details on the meal
request if not acceptable
Email request
System Sending work
specification
Once the work specification has been
completed, the system sends the
specification to the out soured
Work specification

company
Sanjit and
Eric
Search for
café/restauran
t
When a new hub is developed, they
have to look for a preferred
café/restaurant that will supply the
meals
café/restaurant
Sanjit, Eric
and admin
Query They can query information on the
assets, resources and facilities in the
hub with respect to time and grouping
Hub
USE CASE DIAGRAM
The below diagram represent the use case of the Hub Management system for G!gM@n@g3rs
From the diagram above, the Use-case scenarios of the admin include (Voss, 2010):
 Register complaints from gigster and creates work tickets assign manually generated work
tickets
 Fill work details, resolution and close the ticket

 Receive meal request, once this is received, they can either send an email requesting a change
of the order or if acceptable, request the meal-provider
 Select out-sourced service vendors and generate work specifications
The Use-case scenarios for the gigster include:
 Raise complaints and alerts
 Make a food request and corrections
The Use-case scenarios for the Hub management sub-system include:
 Record and generate tickets
 Check contacts terms and conditions and generate payments transactions
The alert/notification team can assign themselves or be assigned a work ticket that they have to
attend to. This includes finding a resolution and giving comments for the raised ticket.
Eric and Sanjit also have a Use-case scenario of scout restaurants, select non-excluded applicants
and authorize payments
DOMAIN CLASS DIAGRAM
The following is a diagram representing the domain class diagram for the Hub Management
system

The class diagram consist of six classes, the attributes for all the classes except for the work
ticket class include (Ma, Zhan, & Yan2, 011):
 +User_name
 +User_ID
 +Email_address
 +Contact_number
 +Address
The attributes for the work ticket class include:
 +State
 +type
 +level
 +time_stamp
The operations for the gigster class include -raise complaints (), -make meal requests () and -
amending food requests (). Those for the admin class include -create work tickets (), -assign
tickets (), -select outsourcing companies (), -generate work specification (), -record work details

() and -check work ticket states (). The alert team’s class methods include -assign work ticket ()
and -attend to work tickets. The operations for the work ticket class include -create (), -delete ()
and -update (). The Hub system has its own operations, these include -record work tickets (), -
generate work tickets (), -send work specifications () and -generate payment transactions () while
the manager class’s operations include -scout for restaurants (), -select non-excluded applicants
() and -authorize payments ().
CONCLUSION
From the above report, the system analysis and design for the hub management system have been
documented. The use case scenarios help in identifying all the requirements for the proposed
system. On the other hand, the domain class diagram for the proposed system will help in
developing the system. This is because it has the vital information used in making classes in
object-oriented programing. The operations listed in the classes help in testing the system. The
attributes also show the variables required in the system.

References
Hecht, R., & Jablonski, S. (2011, December). NoSQL evaluation: A use case oriented survey. In 2011
International Conference on Cloud and Service Computing (pp. 336-341). IEEE.
Dutta, S., Geiger, T., & Lanvin, B. (2015). The global information technology report 2015. In World
Economic Forum (Vol. 1, No. 1, pp. P80-85).
Ma, Z. M., Zhang, F., & Yan, L. (2011). Fuzzy information modeling in UML class diagram and relational
database models. Applied Soft Computing, 11(6), 4236-4245.
Voss, C. (2010). Case research in operations management. In Researching operations management (pp.
176-209). Routledge.