Systems Modelling: Publicit-e Pty. Ltd. Report 2022

Running head: SYSTEMS MODELLING
Systems Modelling: Publicit-e Pty. Ltd.
Name of the Student
Name of the University
Author’s Note

1
SYSTEMS MODELLING
Fully Developed Use Case Text 1
Use Case
Diagram:
CRMS for Lead Relationship Sub system
Scenario: Inquiry for service
Triggering event: The customer should have access to the system and place their inquiry
about any product and service offered by the organization.
Brief Description: The input can be in the form of email or tender request for the
government and business organization for handling the event
management.
Actor: Client, Organization body, Email
Stakeholders: Client, Administrator, System
Preconditions: An event manager should have access of the event information that is
required by the client and the resources available with the
organization.
Post conditions: The administrator is responsible for replying to the customer inquiry
by getting the details of customer request and the availability of
service.
Flow of Activities Actor System
Client The identity of the client is
needed to be verified by
validation and authenticating the
customer account.
The inquiry of the client is
needed to be available to the
admin
Admin The admin should check the
availability of the service and
take feedback from the other
departments
A request is sent to the customer
for keeping on hold
If the limit is not reached the
service is allocated
Excepted 1. The service is not offered by the organization

2
SYSTEMS MODELLING
Condition
2. Customer is not a valid member
3. Payment incomplete due to bank server unavailability
Fully Developed Use Case Text 2
Use Case
Diagram:
CRMS for Lead Relationship Sub system
Scenario: Event look up
Triggering event: The event is booked by the client and it is needed to be managed and
completed successfully.
Brief Description: The account information is checked for finding the availability of
budget for conducting the event and a requisition is sent for getting the
resources needed for the event.
The input of the user is needed to be validated and email service is
needed to be used for sending and receiving email about the services
needed by the user.
Actor: Account Manager, DeptManager, Dispatcher
Stakeholders: Client, Admin, System
Preconditions: 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

3
SYSTEMS MODELLING
system as requisition and
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