CRM System Design: Use Cases, Diagrams, and Test Plans

This project focuses on modeling a Customer Relationship Management (CRM) system. The assignment begins by creating use cases, including a detailed use case diagram for maintaining staff details, outlining actors, stakeholders, preconditions, postconditions, and the flow of activities. The project then progresses to develop an activity diagram to visualize the system's control flow and a sequence diagram to illustrate object interactions. Finally, a comprehensive test plan is created to assess the CRM system's functionality, specifically focusing on testing login, staff addition, and database checking processes. The test plan includes test cases, short descriptions, test conditions, test data, and expected outputs for each scenario, ensuring the CRM system's reliability and effectiveness.

SYSTEM AND
MODELLING
1

Contents
INTRODUCTION...........................................................................................................................3
MAIN BODY..................................................................................................................................3
CONCLUSION..............................................................................................................................13
2

INTRODUCTION
A system model is basically representing the different aspects of CRM system and its
environment. It is mainly considered as a process of developing the abstract model of system
with each model generate multiple perspectives. It will develop uses cases of customer
relationship management system on the basis of system functionality. Furthermore, it also creates
test plan to check their overall functionality of CRM.
MAIN BODY
1. Create Use Cases of Customer relationship management system.
Use Case-1
Figure 1 Use Case Diagram
3

Use case Description:
Use Case Name Maintain staff details
Triggering event
Brief Description The use case is based on maintain staff details by administrator that can
update, modify the data as per requirement. Admin assigns the job of
each staff members and maintain information in proper manner.
Actors Main actors involved are:
 Staff
 Administrator
 Manager
Related use cases  Maintain Job Scheduler use case
 Management of staff role
 Track staff data
Stakeholders Main stakeholders involved are:
 Staff
 Manager
 End users of the system
Preconditions  Administrator views the details of staff with the help for system.
 Manager creates individual database for storing information of
employee in proper manner.
Post conditions  When information of staff members changes by manager for
updating individual tables.
 Manager delete the database of individual table for each staff
members.
 Staff view the status in their system.
Flow of Activities Actor Action System Response
4

 Enter user name and
password
 Update staff details
 Capture / track data
 Check staff qualification
 View status
 Check staff experience
 Login into the system
 Save staff details
 Filter qualified data
 View leads
 Assign leads to the staff members
5

2. Activity Diagram
It is basically generating the flow of control in system and also refer to include use cases
executions. It is another type of UML diagram that describe dynamic aspects of system and
represent the flow of activities in step by step manner.
Activity-1
Figure 2 Activity diagram
6

3. Sequence Diagram
It refers to the interaction diagram that mainly describe how group of objects work
together in proper manner. It mainly used for designer to understand the actual requirement of
new system and also analyse the documents of existing system.
Sequence-1
Maintain Staff details Sequence diagram
Figure 3 Maintain Staff details Sequence diagram
7

4. Test plan of use cases
The test plan is basically derived according to the requirements, detailed design
specifications and its functional specification. It mainly determined the test details that
associated with the test cases.
Test plan to maintain staff details
S. No. Test case Short Description Test condition Test Data Expected
Output
1. Login Check the correct
username and
password of staff
members.
If staff members are
not adding correct
details, it will
generate error
message.
Grant
Access to
the main
application.
Staff
successfully
login the
system to
check
details.
2. Add staff
name
Ensure that new staff
members added to
the system.
If new staff
members already
added so that it will
generate error
messages.
Test the staff
name and
generate
confirmation
message of
changes
should be
displayed
Data is in
the form
altered and
submit
easily.
When click
on database
that generate
successfully
messages.
3. Checking for
creating
database
Test the database
when manager create
individual database
and assign specific
job role to each staff
Whenever the
database is created,
manager assign the
job task of each staff
members
Test the
database of
individual
staff tables.
Database
has been
successfully
created and
manager can
view the
8

members. team.
Table: 3
CONCLUSION
In above discussion, it has been successfully designed use cases, Activity and sequence
diagram of customer relationship management system. It can be determined the functionality of
system with the help for creating test plans.
9

10