Systems Modelling Assignment

Systems Modelling
1

Contents
INTRODUCTION...........................................................................................................................3
TASKS.............................................................................................................................................3
Pictorial Model of organization...................................................................................................3
High level of organizational chart...............................................................................................4
Stakeholder chart.........................................................................................................................4
System vision statement..............................................................................................................5
Domain Model class diagram......................................................................................................5
Two User stories complete with statement and acceptance criteria............................................6
User Goal Table for two user stories identified...........................................................................6
Use Case diagrams:......................................................................................................................7
CONCLUSION..............................................................................................................................19
REFERENCES..............................................................................................................................20
2

INTRODUCTION
A system modelling help to develop abstract model of the system, and each model
representing the different view or objective of that system. Publicit-e Pty.Ltd. using Customer
relationship management manage interaction of company with all current and potential
customers, and analysis record about customers history with a company and according to data
analysis company improve the relationship with the customers, and always focus on customer
relationship and improving sales growth.
TASKS
Pictorial Model of organization
Figure:1
3

High level of organizational chart
Figure: 2
Stakeholder chart
A stakeholder is a part of organization who take interest in organization like shareholder,
investors, employees and clients etc., clients are those whose pay for product and seek
effectively delivery, developers responsible for the product quality it works on development,
designing, quality and testing of product (Singh, Sharma and Saxena, 2016). Stakeholder can
affect by firms’ decisions, policies and objective, they also affect the organization, because they
are investors and give financial support. Stakeholder actively involved in project's works, and
internal part of project's organization.
4
Stakeholder
Employees Investors Client/ customer
Software
developer
Marketing
manager
banks
Personal Investors

Company Vision
Publicit-e Pty.Ltd. vision is providing quality services to customers and maintaining good
relationship with customers. It also wants to improve the brand image of company (Septian,
Alianto and Gaol, 2017).
System vision statement
The vision of CRM is built customer equity, improve the long-term relationship, it helps to
become customer oriented therefore customer defection rate reduce. CRM helps to provide good
service to the customer and develop effective customer relations (Iqbal and Bajwa, 2016).
Domain Model class diagram
Figure 1 Class Diagram
Class diagram is based on the unified modelling language that describe overall structure of
system by showing the process of classes. It can be representing the attributes, operations and its
relationship among objects.
Data dictionary:
 Entities: client, salesperson, contract, manager, moderator, company_user,
Administrator_Staff.
5

 Attributes: id, name, address, phone_no, age etc.
Two User stories complete with statement and acceptance criteria.
1. Adding a new company user to customer relationship management system: Adi is an
employee of Publicit-e Pty company where he is going to open the CRM system where it
provide facilities for adding new user details in it. System Administatrors have a power to
provide access where Adi is directly open web services. He login their accounts with the
help of username and password. In this way, it also entered their own personal
information in the system (El AhmarLe Pallec and Gerard, 2016). Afterwards, it
completing the process of system where informations are automatically save in system.
Admin has a power to modify, update, delete and create new data.
Acceptance Criteria: The primary criteria of Adi to easily access the information and
secure their data or information for long times in CRM system. In case, if mismatch the
data then admin fill the required fields in proper manner.
2. Adding new employee to moderator/ salesperson group: The Publicit-e Pty firm has a
new employee named Adi. Manager assign as a sales group but it required the
membership in the customer relationship management system (Backet, 2016). In this
way, Adi easily login their account and select the group that will be involved. It will get
membership in particular group.
Acceptance Criteria: The basic criteria are that when it requires for identifying the
correct group as per requirement. Administrator is necessary to maintain the customer
relationship management system in proper manner.
User Goal Table for two user stories identified.
S.No Users Actor Description Goals
1.  Employee
 Administrator
Adding a new
company user to
customer relationship
management system.
Successfully adding
the details of user in
the CRM system
2.  Moderator/ Adding new
employee to
Successfully add or
select the group of
6

Salesperson
 Administrator
 Manager
moderator/
salesperson group:
departments.
Table: 2
Use Case diagrams:
Negotiation relationship
7

Description
Use case name Negotiation relationship
Participant Actors  Administrator
 Moderator/ salesperson
 Client
 manager
Brief Description The Use case is based on the negotiation
relationship between client and company
administrator where different actors’
participants for providing offers related
contract, quotation requests.
Flow of Events  Administrator create, modify and
update the details of client
 User login the account to check
particular assign work.
 Manager send the request of contract to
client regarding quotation interactions
and other offers.
 Admin select to assign the moderator/
salesperson to record information of
client.
Exit condition The use case mainly ends when user group
click on apply button.
Table: 3
8

Assign Moderator to user groups
Descriptions:
Use case name Assign Moderator to the user group
Participant Actors  Administrator
 Moderator
Brief Description The use case is performed the actions where
admin provide assign the responsibilities of
moderator for particular task completion.
Flow of Events  Administrator control the user group of
moderators.
 User login the account to check
particular assign work.
 Moderator also checking the list of
existing moderators.
 Admin select to assign the moderator.
Exit condition The use case mainly ends when user group
9

click on apply button.
Table: 4
Use case of maintain quotation process by manager
Descriptions:
Use case name Maintain quotation process by manager
Participant Actors  Administrator
 Manager
Brief Description The use case is performed the actions where
admin provide assign the responsibilities of
manager and maintain the process of quotation
in proper manner.
Flow of Events  Administrator assign the power of
manager where it will maintain the
quotation interaction process.
 User login the account to check
10

particular assign work.
 Admin record the request of quotation
through manager.
 Admin select to assign the manager.
Exit condition The use case mainly ends when user group
click on apply button.
Table :5
Use case of Successfully generate Quote status
11

Use case name Successfully generate Quote status
Participant Actors  Manager
 Company user
Brief Description The use case is performed the actions where
manager will generate the process of quote so
that they are forwarding to the users where it
can be verified in proper manner.
Flow of Events  Administrator assign the power of
manager where it will maintain the
quotation interaction process.
 User login the account to check
particular assign work.
 Admin record the request of quotation
through manager.
 Admin select to assign the manager.
Exit condition The use case mainly ends when user group
click on apply button.
Table: 6
12

Use case of confirmation process of quote status
Description:
Use case name Successfully generate Quote status
Participant Actors  client
 Manager
Brief Description The use case is performed the actions where
manager will generate the process of quote so
that they are forwarding to the users where it
can be verified in proper manner.
Flow of Events  Administrator assign the power of
manager where it will maintain the
quotation interaction process.
 client login the account to check
response of manager
 it also records the request of quotation
through manager.
 Manager provide confirmation to the
13

client.
Exit condition The use case mainly ends when user group
click on apply button.
Table: 7
Use case of communication between salesperson and client
14

Description:
Use case name Coordination between salesperson and client
Participant Actors  client
 Salesperson
Brief Description The use case is performed the actions where
manager will generate the process of quote so
that they are forwarding to the users where it
can be verified in proper manner.
Flow of Events  Salesperson will generate
communication between client.
 It provides the better services and
establish contract between them.
 client login the account to check
response of salesperson
 it also records the request of quotation
through manager.
 Manager provide confirmation to the
client.
Exit condition The use case mainly ends when user group
click on apply button.
Table: 8
15

Use case for manage process of assign
Description:
Use case name Maintain process of assign
Participant Actors  Administrator staff
Brief Description The use case is performed the actions where
manager will generate the process and give
permission to new users.
Flow of Events  Admin will generate communication
between client.
 It also assigns the task of staff
members.
 Admin provide the login facilities
where user check details.
16

 it also records the request of quotation
through manager.
 Setup the specific permission to
moderator and other users.
Exit condition The use case mainly ends when user group
click on apply button.
Table: 9
Use case of client take services and perform actions.
17

Description:
Use case name Client take services and perform actions
Participant Actor  client
Brief Description The use case is performed the actions where
client will participate to search details.
Flow of Events  Client can login the account to search
details about the services.
 It also chooses the specific services
 Admin provide the login facilities
where user check details.
 it also records the request of quotation
through manager.
 Setup the specific permission to client
where they can view status of services.
Exit condition The use case mainly ends when user group
click on apply button.
Table: 10
18

CONCLUSION
From the above discussion it has been concluded that CRM played impotent role for
organization growth. It helps to build strong customer relationship, increase sales, improve
customer service and increase profit of organization.
19

REFERENCES
Book and Journals
Back, S., et.at., 2016. Evolutionary Test Case Generation from UML-Diagram with
Concurrency. In Advances in Computer Science and Ubiquitous Computing (pp. 674-
679). Springer, Singapore.
El Ahmar, Y., Le Pallec, X. and Gerard, S., 2016. Empirical Activity: Assessing the Perceptual
Properties of the Size Visual Variation in UML Sequence Diagram.
Iqbal, U. and Bajwa, I.S., 2016, August. Generating UML activity diagram from SBVR rules. In
2016 Sixth International Conference on Innovative Computing Technology (INTECH)
(pp. 216-219). IEEE.
Septian, I., Alianto, R.S. and Gaol, F.L., 2017. Automated test case generation from UML
activity diagram and sequence diagram using depth first search algorithm. Procedia
computer science. 116. pp.629-637.
Singh, M., Sharma, A.K. and Saxena, R., 2016. Formal Transformation of UML Diagram: Use
Case, Class, Sequence Diagram with Z Notation for Representing the Static and Dynamic
Perspectives of System. In Proceedings of International Conference on ICT for
Sustainable Development(pp. 25-38). Springer, Singapore.
20

21