ITECH2002: Systems Modelling

Running head: ITECH2002: SYSTEMS MODELLING
ITECH2002: Systems Modelling
Name of the Student
Name of the University
Author’s Note

1
ITECH2002: SYSTEMS MODELLING
Use Case Description1:
Use Case
Diagram:
Hub Access sub system for Hub management system
Scenario: Technical assistance
Triggering event: Preferred supplier is selected from the supplier list by scanning the
service contract and payment terms.
Brief Description: The details of the supplier is needed to be inputted in the database and
hiring and payment are needed to be handled individually. A
notification is needed to be sent in the form of email with the details of
job location and details. The admin have the option to add general
comment.
Actor: Supplier, Admin, System
Stakeholders: Client, Admin, System
Preconditions: The supplier is needed to be registered with the hub management
system and should have the needed specialization, skill and
availability.
Post conditions: The supplier should pass the interview conducted by the admin for
becoming enlisted in the supplier list.
Flow of Activities Actor System
Client Needs technical assistance from
a preferred supplier for getting
their problem solved.
The supplier information is
needed to be available with
details and ratings.
Supplier The budget of the project is
approved by the account
manager based on the payment
made by the client.
Admin Identifies the resources and skill
needed for solving the issue
System The system stores the data and
updates the status of the event
Excepted 1. The supplier does not have the essential resource available

2
ITECH2002: SYSTEMS MODELLING
Condition
2. Supplier is not a valid member
3. Delay in response due to internet connectivity issue
Use Case Description2:
Use Case
Diagram:
Hub Access sub system for Hub management system
Scenario: Food supplier order acceptance
Triggering event: The food order is booked by gigsters and is needed to be approved by
the manager for getting it delivered.
Brief Description: The order placed by the gigsters is assessed by the administrator for
generating the order for the food supplier. The food is delivered by the
administrator via the meal room and a notification is sent to the
gigster. The details of the restaurant/café is needed to be recorded and
a contract and payment terms is needed to be prepared.
Actor: Account Manager, DeptManager, Dispatcher
Stakeholders: Client, Admin, System
Preconditions: Gigsters have given order from the list of food delivery partner
registered with the system.
The client have booked the system and completed the payment process
and provided all the details of the event i.e. venue, no of peoples
needed to be served, etc.
Post conditions: The budget of the event is available to the coordinator and he can view
the details of the customer for finding the resources required for
organizing the event.
Flow of Activities Actor System
Client Provide all the information about
the event and complete payment
of the event
The details are needed to be
inputted in the information
system as requisition and

3
ITECH2002: SYSTEMS MODELLING
available to the all the admin
staffs
Account Manager The budget of the project is
approved by the account
manager based on the payment
made by the client.
Coordinator Analyses the resources needed
for conducting the event and
arranges the resources
Department Manager The requisition of resources is
approved by the department
manager by analysing the
availability
System The system stores the data and
updates the status of the event
Excepted
Condition
1. The service is not offered by the organization
2. Customer is not a valid member
3. Payment incomplete due to bank server unavailability