Comprehensive CRMS Subsystem Report for Publicit-e Pty Ltd Analysis

This report provides a comprehensive analysis of the CRMS subsystem of Publicit-e Pty Ltd, detailing its various components and functionalities. The introduction emphasizes the importance of breaking down large systems into manageable subsystems for efficient data management. The report includes a pictorial model of the organization, organizational charts illustrating the company's structure, and stakeholder charts identifying key stakeholders. It outlines the vision and mission statements, along with a system vision statement, to provide a clear direction for the company's growth and technological advancements. User stories are presented to illustrate user interactions within the system, followed by user goal tables and detailed use case descriptions for various system users, including administrators, customers, salespeople, and company users. Use case diagrams are provided to visually represent the interactions and processes involved in different scenarios, such as moderator assignments, customer detail entries, salesperson lead status checks, and event management. The report also includes class diagrams depicting the system and subsystem structures. The conclusion summarizes the need for departmentalization through improved IT systems and processes, emphasizing the role of stakeholders and the company's commitment to high-quality services. References to relevant literature are provided at the end.

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