IT System Design for Publicit-e Pty. Ltd.

The assignment involves designing an IT system for Publicit-e Pty. Ltd., which includes creating use case descriptions and diagrams, as well as a class diagram for the system and its sub-systems. The system is designed to improve company operations by streamlining processes and enhancing communication among stakeholders. The assignment also requires considering the company's vision and mission statements in the design of the IT system.

IT

Table of Contents
INTRODUCTION...........................................................................................................................1
Pictorial model of organisation....................................................................................................1
Organisational chart.....................................................................................................................1
Stakeholder chart.........................................................................................................................2
Vision statement..........................................................................................................................3
Mission statement........................................................................................................................3
System vision statement..............................................................................................................3
CONCLUSION..............................................................................................................................17
REFERENCES..............................................................................................................................18

INTRODUCTION
It is important to break a large system into sub system so that it becomes easy to store, edit,
delete, etc. data and information. There can be various sub system in organisation depending on
its structure. However, each sub system consists of different features and work differently. A sub
system is centrally connected to database (Isberg and et.al., 2017). This report will describe
about sub system of CRMS of Publict e Pty ltd. Also, it will show organisational and stakeholder
chart, mission and vision statement, etc. Moreover, in this there will be diagrams such as use
case, class diagram, etc.
Pictorial model of organisation
An organisational chart represents structure of organisation. It shows top to bottom flow of
responsibility in systematic way. It becomes easy to identify who reports to whom. It is
important to develop chart so that operations are run smoothly. In Publicit-e Pty. Ltd. there are
basically 3 operations. So, each operation require chart which is defined below :-
1

Organisational chart
2

Stakeholder chart
Stakeholder analysis diagram
3

Vision statement
A vision statement is roadmap which indicates company growth. It provides direction to
organisation regarding what they want to become. So, vision statement of Publicit-e Pty. Ltd. is
as follows :-
Becoming leader in CRM services
Mission statement
It represents why a company exists, its goals, products and services offered, etc. (Dumais
and et.al., 2016) The mission statement makes it easy to identify organisation customers,
operational area, etc. Publicit-e Pty. Ltd. mission statement is as follows :-
For any advice, consult us
System vision statement
It describes technology growth of company and types of system used in it. Also, it shows
services offered through technology. Publicit-e Pty. Ltd. statement is as follows :-
High technology, high growth
User stories
The two user stories are described below :-
Story 1
User User story Acceptance criteria
Customer If a customer search for
product in CRM system. The
system will notify by showing
details. So, a lead will be
added in CRM
Lead acceptance
Story 2
User User story Acceptance criteria
Salesperson A salesperson wants to check
status of lead in CRM. The
Status checked
4

system will allow to log in and
sending request to user.
User goal table
The above two user stories their goals are identified below :-
Role Action Goal
Customer Searching product details Purchasing product
Salesperson Checking status of lead Changing status
Use case descriptions
Use case moderator
Use case name Moderator assign to user group
Actor  Administrator
 Moderator
5

Condition Administrator click on the group and select the
assign moderator
Brief description Moderator has performed the function to assign
the task for every group member where each
one control the processing of operations.
Flow of events  Moderator login their accounts.
 Show up group members
 Select to assign
 List the existing goals
Precondition The group members must register with system
to perform task.
Exceptional condition It should be used at least one goals in the
system.
Use case of customer
6

Use case name Customer entering details
Actor  Admin
 Customer
Condition Customer register by log in and entering
details.
Brief description Customer has requested for product by
searching details and information where admin
is providing details.
Flow of events  Registering of customer details
 Requesting for product
 Placing order
 Doing payment
Precondition The customer must log in to system to request
7

for product
Exceptional condition Customer should do a transaction of product
Use case of salesperson
Use case name Sales person
Actor  Sales person
 Staff
Condition Salesperson log in to check status of lead
Brief description Salesperson has checked status of lead with
staff to generate lead.
Flow of events  Log in system
 Checking status
 Sending request for lead generation
8

 Assigning lead
Precondition Salesperson must log in to system
Exceptional condition It must check lead and change status.
Use case of company user
Use case name Company user
Actor  User
 Customer
Condition User has to collect data and information of
customer.
Brief description Company user has generated lead by sending
mails and recording data. The data is
9

maintained and processed.
Flow of events  Generation of lead
 Edit, delete data
 Taking customer feedback
 Maintaining data
Precondition User must have information of customer
Exceptional condition User is required to store data
Use case of customer service provided by staff
Use case name Customer service
Actor  Staff
 Customer
 Admin
10

Condition Customer send request for new service
Brief description Customer has requested for new service by log
in to system and staff is checking and
managing it
Flow of events  Sending request
 Checking service
 Communicating with staff
 Solving queries
Precondition Customer must log in to system.
Exceptional condition Customer is to request for at least one service.
Use case of system user
Use case name System user
Actor  System user
11

 Customer
Condition User log in into account to manage process
Brief description System user has able to manage process of
delivering services to customer and scheduling
it.
Flow of events  Log in
 Checking details
 Managing process
 Completion
Precondition User must long in into system to manage
product
Exceptional condition The user must manage one or more product.
Use case of quote manage
12

Use case name Quote manage
Actor  Customer
 Salesperson
Condition Salesperson send quote to customer
Brief description Salesperson has sent quote to customer
regarding product and negotiating contract with
them.
Flow of events  Quote requesting
 Sending contract to customer
 Approving contract
 Completion
13

Precondition Quote is to be sent to customer
Exceptional condition Salesperson is used to receive or sent one quote
to customer.
Use case of event management
Use case name Managing event
Actor  User
14

 Staff
Condition User creates event in system and add details.
Brief description User has performed function of creating event
and adding details. The staff updates details
and send confirmation message.
Flow of events  Creation of event
 Adding details
 Sending and receiving messages
 Confirmation
Precondition User must create event in system
Exceptional condition Staff should add details of event and send
message.
Use case of exporting contact list
15

Use case name Exporting contact list
Actor  User
 Admin
 Moderator
Condition Moderator has send contact list to user and
admin.
Brief description The moderator export contact list and
directories to admin and saving details of it.
Flow of events  Selection of contact list
 Modifying list
 Maintaining and saving details
Precondition Moderator must have access to manage contact
16

list
Exceptional condition Moderator is required to select one or two
contact list.
Use case of complaint
Use case name Making complaint
Actor  Customer
 Admin
 user
Condition Customer makes complaint related to product
Brief description Customer has made complaint of product to
admin and company user.
Flow of events  Permission to complaint
17

 Making complaint
Precondition Customer must log in to system
Exceptional condition Customer is required to interact with company
user
Class diagram for a System
18

Class diagram for sub-system or an individual entity user
CONCLUSION
It can be concluded that Publicit-e Pty. Ltd. requires dividing their operations into different
departments. This can be done by improving IT system and process. However, there are several
stakeholders engaged as well in company. The vision and mission statements of company are
related to offering high quality services. A new IT system is designed where use case description
and diagrams are designed.
19