Itech2002 Systems Modelling

Running head: ITECH2002 SYSTEMS MODELLING
Assignment 2 – Dynamic Modelling, Screen Design and Test Plans
Name of the Student
Name of the University
Author’s Note

1
ITECH2002 SYSTEMS MODELLING
Fully Developed Use Case Text 1
Use Case
Diagram:
Hub Access sub system for Hub management system
Scenario: Meals at hub
Triggering event: The restaurant is needed to be registered and they are needed to be
authorised or have good experience with other hubs or personally.
Brief Description: The preferred supplier of food is needed to be selected from the
vicinity of the hub and the details of the quote, types of food returned,
price, hours of availability, supply period and delivery requirement.
For ordering food the order is assessed by the admin for generating
order for the food supplier.
Actor: Admin, food supplier, Information system
Stakeholders: Food Supplier, Administrator, System
Preconditions: The food supplier should be in the vicinity of the hub and registered
with the information system for maintaining authorization.
Post conditions: The administrator assess the order for generating it for the food
supplier and if the order is found not acceptable it is revised or lapses
it.
Flow of Activities Actor System
Cafes/Restaurants The menu and the service area is
recorded along with the details
of the restaurant for registering
with the information system.
Contract and agreements on the
payment terms are also needed
to be recorded.
Admin The opportunity is needed to be
discussed and authorization of
the food delivery partner is
maintained.
A notification is accessed by the
admin in case of any food order
and generates order for the food
suppler.

2
ITECH2002 SYSTEMS MODELLING
If the order is not accepted
changes are suggested to the
gigsters.
Excepted
Condition
1. Payment condition for processing order
2. Bank server unavailability and delay in payment
Fully Developed Use Case Text 2
Use Case
Diagram:
Hub Access sub system for Hub management system
Scenario: Checking contract terms and conditions
Triggering event: Payment is made to the personnel agencies by analysing the service
cost, rate agreed and employee working hour cost. Payment
transaction is generated and email alert is created for reviewing and
authorizing the payment.
Brief Description: The payment is authorized before sending it to the supplier bank
account and for clearing the payment the condition and contract terms
are needed to be reviewed by the administrator.
Actor: Client, Admin, System
Stakeholders: Account Manager, Personal Agencies, Employee
Preconditions: Personal agencies are needed to be registered with the information
system and provide base service for closing the tickets. The work that
are needed to be carried and the rate of agreement of working is also
needed to be recorded.
Post conditions: The payment is needed to be authorized by checking the conditions
and contract made by the personal agencies for disbursing the
payment.
Flow of Activities Actor System
Personal Agencies The personal agencies provide
service and interacts with the
gigsters.

3
ITECH2002 SYSTEMS MODELLING
The system should have all the
details about the rate agreed and
work needed to be carried.
Admin A payment transaction is created
and a checking is made for the
actual records and interaction
with gigsters.
Employee The record of employee is
checked along with working
hours and the work being carried
out at the rate agreement.
Excepted
Condition
1. Base amount and service is needed to be recorded
2. The payment transaction is needed to be available
3. The details of the service and the rate at which the work is
carried is needed to be available.
4. The bank server problem causing error in payment processing.