Systems Modelling Project: Analysis and Design of CRM System for Leads

This project focuses on systems modeling for a leads relationship management (CRM) system. It begins with user stories from the perspectives of a sales representative and a sales manager, outlining their needs and goals. The project then details user goal tables, defining tasks and interfaces for each role. Following this, it provides a comprehensive set of use case descriptions, including scenarios for registering, logging in, inputting and viewing lead details, deleting leads, and managing meetings. Each use case includes triggers, primary scenarios, alternative scenarios, exceptional scenarios, pre-conditions, and post-conditions. The project culminates in a use case diagram visually representing the system's functionality and a class diagram depicting the system's structure. The provided bibliography lists relevant research papers on CRM and customer relationship management.

Running head: SYSTEMS MODELLING
SYSTEMS MODELLING
Name of student
Name of university
Author’s note:

1
SYSTEMS MODELLING
Table of Contents
User stories.....................................................................................................................2
User story 1................................................................................................................2
User story 2................................................................................................................2
User goal table................................................................................................................2
User goal table 1.........................................................................................................2
User goal table 2.........................................................................................................2
Use case description.......................................................................................................3
Use case description 1................................................................................................3
Use case description 2................................................................................................4
Use case description 3................................................................................................4
Use case description 4................................................................................................5
Use case description 5................................................................................................6
Use case description 6................................................................................................7
Use case description 7................................................................................................8
Use case description 8................................................................................................9
Use case diagram..........................................................................................................10
Class diagram...............................................................................................................11
Bibliography.................................................................................................................12

2
SYSTEMS MODELLING
The chosen sub system for individual work component is the leads relationship
management. Leads could be described as the potential customers or the business clients of
the organisation who could be made into customer in the future.
User stories
User story 1
I am the sales representative of the company and I wish to use the system for storing
the details of the potential leads. All the leads are business clients and the customers who
could become our customers in the future.
User story 2
I am the sales manager and I wish to use the system for managing all the leads that are
collected by the sales team and conduct meeting with them constantly for satisfying all their
requirements.
User goal table
User goal table 1
User Goals Tasks Interfaces
Sales representative Generate potential
leads
Login into the
system
Record the leads
details
Business leads
Potential customers
User goal table 2
User Goals Tasks Interfaces
Sales manager Manage the gathered  Login into the Business leads

3
SYSTEMS MODELLING
leads system
 View list of the
leads
 Contact the leads
 Serve the leads
Use case description
Use case description 1
Use Case Register
Summary The new sales representative register in the system
Actor Sales representative
Trigger The sales representative inputs their personal details in the system
Primary Scenario The sales inputs all the details in the system
Successful registration
Alternative Scenario Registration delayed as there is a requirement of verification of details
Exceptional Scenario Registration failed due to input of wrong details
Pre-Conditions Registration successful and now the sales representative have their account
for storing details of leads

4
SYSTEMS MODELLING
Post-Conditions Details of sales representative stored in the system
Assumptions None
Use case description 2
Use Case Login
Summary The new sales representative login into the system
Actor Sales representative
Trigger The sales representative inputs their personal details in the system
Primary Scenario The sales inputs all the details in the system
Successful login
Alternative Scenario Registration delayed as there is a requirement of verification of details
Exceptional Scenario Login failed due to input of wrong details
Pre-Conditions Login successful and now the sales representative can view their account for
storing details of leads
Post-Conditions Login time and data stored in log file
Assumptions None

5
SYSTEMS MODELLING
Use case description 3
Use Case Input details of leads
Summary The sales representative inputs the details of gathered leads
Actor Sales representative
Trigger The sales representative inputs their leads details in the system
Primary Scenario The sales inputs all the details in the system
Details stored in the database
Alternative Scenario Lead already exists in the system
Exceptional Scenario Details cannot be stored as some of the mandatory fields are missing
Pre-Conditions Details successfully stored in the system
Post-Conditions Leads can now be viewed by the sales manager
Assumptions None
Use case description 4
Use Case View details of leads
Summary The sales representative prompts the system to view the details of gathered
leads

6
SYSTEMS MODELLING
Actor Sales representative
Trigger The sales representative prompts the system to view the leads details in the
system
Primary Scenario The sales login into the system
Views details of the leads
Alternative Scenario Leads cannot be viewed as lead is not approved by the manager
Exceptional Scenario System cannot display details as representative not authorised to view details
Pre-Conditions View the list of leads
Post-Conditions Leads are then approached by the sales manager
Assumptions None
Use case description 5
Use Case Delete leads
Summary The sales representative prompts the system to view the details of gathered
leads
Actor Sales representative
Trigger The sales representative prompts the system to delete the leads details from

7
SYSTEMS MODELLING
the system
Primary Scenario The sales login into the system
Views details of the leads
Deletes the details of leads
Alternative Scenario Leads cannot be viewed as lead is not approved by the manager
Exceptional Scenario System cannot display details as representative not authorised to view details
Pre-Conditions View the list of leads
Post-Conditions Leads deleted from the database
Assumptions None
Use case description 6
Use Case Login
Summary The new sales manager login into the system
Actor Sales manager
Trigger The sales manager inputs their personal details in the system
Primary Scenario The sales inputs all the details in the system
Successful login

8
SYSTEMS MODELLING
Alternative Scenario Input details again
Exceptional Scenario Login failed due to input of wrong details
Pre-Conditions Login successful and now the sales manager can view their account for
details of leads
Post-Conditions Login time and data stored in log file
Assumptions None
Use case description 7
Use Case View details of leads
Summary The sales manager prompts the system to view the details of gathered leads
Actor Sales manager
Trigger The sales manager prompts the system to view the leads details in the system
Primary Scenario The sales login into the system
Views details of the leads
Alternative Scenario Leads cannot be viewed as lead is not approved by the director

9
SYSTEMS MODELLING
Exceptional Scenario System cannot display details as manager not authorised to view details
Pre-Conditions View the list of leads
Post-Conditions Leads are then approached by the sales manager
Assumptions None
Use case description 8
Use Case Input meeting details with leads
Summary The sales manager prompts the system to input meeting details of gathered
leads
Actor Sales manager
Trigger The sales manager prompts the system to input the meeting details of the
leads in the system
Primary Scenario The sales login into the system
Inputs the meeting details and the progress details with each lead
Alternative Scenario Leads cannot be viewed as lead is not approved by the director
Exceptional Scenario System cannot display details as manager not authorised to view details

10
SYSTEMS MODELLING
Pre-Conditions Inputs the meeting details with the leads
Post-Conditions Leads are pursued for turning into customers.
Assumptions None
Use case diagram

11
SYSTEMS MODELLING
Class diagram
`