CIS-5200: Sales Management System Development for CPM Company

Desklib provides past papers and solved assignments. This project details the redesign of a sales management system for CPM.

CIS-5200

Abstract
This assessment is about the new system of CPM company which is situated in Australia and it is
a sales and marketing company. A new sales management system is being developed which is
introduced by taking care of all the problems which are faced by the users in the old system. In
last assessment the requirements are identified through various techniques and an As-Is diagram
was developed according to the system which is developed but now some problems are also
rectified in this assessment and To-Be process will be generated in the document which
continues the old process and adds some new processes to that system. A time management plan
and changeover plan is also generated for this process (Maraseni, et al., 2019).
2

Table of Contents
Abstract............................................................................................................................................2
Introduction......................................................................................................................................4
Time Management Plan...................................................................................................................5
“To Be” Process...............................................................................................................................8
Comparing “As Is” and “To Be” Process........................................................................................9
Entity Relationship Diagram.........................................................................................................10
Data Normalization........................................................................................................................12
Testing...........................................................................................................................................13
Training..........................................................................................................................................15
System Changeover.......................................................................................................................17
Report to Top Management...........................................................................................................18
Conclusion.....................................................................................................................................19
References......................................................................................................................................20
Table of Figures
Figure 1: Work Break Down Structure............................................................................................5
Figure 2: To-Be Process Diagram...................................................................................................8
Figure 3: As Is and To Be Process...................................................................................................9
Figure 4: Entity-Relationship Diagram.........................................................................................10
3

Introduction
CPM is a sales and marketing company of Australia. Now it is facing some issues in their sales
and marketing system so the problems can be enhanced using the application of sales and
marketing. All the requirements and problem statements are identified for the system and
implemented into the new system but this system is also facing some issues for the sales process.
So the new processes will be added into the system. For this process, a time management plan
will be developed and with the help of the E-R diagram and “To Be” process diagram the new
system will be developed. In last the changeover and top to report management plan will be
generated.
4

Time Management Plan
This is basically a plan of scheduling activities which are performed in a day to day basis and
every activity or task is specified with a particular time. If planning of time management is good,
then it will help in managing the work efficiently in a given period of time. This plan is placed at
the starting of the project as it is an important element for managing the project. In the time
management plan, all the activities will be included from starting to end so the tracking of time
as per activity will be easy (Kerzner & Kerzner, 2017).
Figure 1: Work Break Down Structure
5

S.
No.
Activity
Name
Description Schedule Plan Action Status
Start End
1. Initialization In this phase, all the
problems are
identified in the
present system so the
solutions can be
identified in the new
system.
05-
05-
2019
07-
05-
2019
Initialization is the very
starting phase of the
project so all the
requirements from the
old system are
identified.
Done
2. Planning for
project
This phase is for
planning the project,
the old and new
requirements, and
scheduling of all the
activities.
07-
05-
2019
12-
05-
2019
This phase will be done
in the presence of all the
authorities who are
related to the system and
make a plan for the
project.
Done
3. Feasibility
Analysis
The requirements
which are identified in
earlier stages are
checked on the basis
of the feasibility as we
can implement it in
our project or not
(Nicholas &
Steyn, 2017).
12-
05-
2019
15-
05-
2019
The feasibility analysis
can be done through
various techniques and
help of the developer
and experts.
Done
4. Identifying
Stakeholders
In this phase all the
stakeholders are
identified for the new
system, so they can be
responsible for all the
activities.
15-
05-
2019
19-
05-
2019
Stakeholders can be
defined with the help of
organization roles and
every stakeholder has its
own responsibility
towards the project.
Done
5. Designing In this stage, all the
requirements are
implemented as a
prototype design or
blueprint of the
application so it can be
analyzed for practical.
19-
05-
2019
25-
05-
2019
Designing can be done
with the help of various
tools and techniques
using the requirements
of the system.
Done
6. Development This phase is fully
based on the practical
implementation of the
project. The developer
implements the design
25-
05-
2019
10-
06-
2019
In this stage, the
practical will be
implemented by the
developer of the project.
Done
6

using programming
languages.
7. Testing The system will be
tested on the basis of
different criteria to
identify the
compatibility with the
real world.
10-
06-
2019
17-
06-
2019
The system will be
tested manually or using
automation and risks
will be removed.
Done
8. Project
Deployment
After all the risk
removal the project is
going live so the users
can use this
application for their
convenience.
17-
06-
2019
20-
06-
2019
The project can be
deployed using various
deployment plans.
Done
9. Documentati
on
The documentation
will cover all the
processes which took
place in the whole
project for completion.
20-
06-
2019
22-
06-
2019
Documentation creates
an instruction all
development phase of
the phase.
Done
10. Maintenance After deployment, the
application should be
maintained for regular
updates and bugs
removal.
22-
06-
2019
24-
06-
2019
Maintenance should be
done from the date of
deployment to the date
of ending the contract.
Done
11. Required
Updating in
application
Some updates are
required in the
application or
requirements are
changed then it should
be updated.
24-
06-
2019
25-
06-
2019
Updates should be bug-
free and applied for all
the devices that are
running or not running
the application
Running
7

“To Be” Process
Figure 2: To-Be Process Diagram
In the AS-IS diagram made in the previous report, it depicts the current scenario of CPM. Such
as the process defined in the diagram includes that the customer will make contact with the
company first and the meeting will be decided. Further, the customer will take a decision
regarding the purchase. In the process, the CPM is lacking the storage of details regarding the
meeting and customer’s information. Therefore, a process diagram known as the “To-Be”
diagram has been made using a business process model and notation. The diagram is the
advanced version of “As-Is” diagram, as more processes such as data storage and processing are
added. This stage will lead to the customer sales transaction, hence before the transaction can
occur, it will be getting stored first (Pliego, et al., 2015).
8

Comparing “As Is” and “To Be” Process
Figure 3: As Is and To Be Process
The “As Is” diagram is creating using the fact-finding techniques and the stakeholders of the
organization in the last assessment. This “As Is” diagram helps in understanding the business
processes in detail and it also helps in identifying the issues of CPM organization. This diagram
is divided into three modules as one is customer, second is the sales department and the last one
is account management department. All the processes are connected with each other. In this
diagram, the sales data is not being stored in the application so this is the problem which is
identified in “As Is” process of CPM sales and marketing system.
In “To Be” process diagram all the processes are involved of “As Is” process as they are present
in the old system. So making a new system the problem is identified in the sales department so in
this diagram the process to data stored can be added into the sales department after the process of
order fulfillment. So after saving the data of sales the customer can process their transaction and
get the verification from the accounts department so the transaction details can be displayed on
customer view. This is the enhanced process of “As Is” diagram.

Entity Relationship Diagram
Figure 4: Entity-Relationship Diagram
ER diagram shows the relationship present between different entities present in the database
systems. In order to achieve the database desired to make the changes possible, the entities
identified in the system are Customer, Invoice, Service record an option. The entities invoice and
Customer will be connected as the invoice will include the details of a customer. The entity
service records will be maintaining the Option entities. Primary keys in the ER diagram are used
to indicate the keys that will be able to identify each record present in a certain table. At the
10

ending of each entity, some functions have been placed which would be performed by each
entity, such as customer will be able to login into the system and options entity can add a new
option into the system. This feature will not allow any unauthorized access for safety purposes
(Zhang, et al., 2017).
11

Data Normalization
Normalization is done in the database to remove the redundancies present in the table. There are
three types of normalized forms. In order to remove the repetition of data from the tables, the
3NF form is used (García, et al., 2015). The entities defined in the diagram above will be
represented and stored in the database using tables; hence for each entity, a table schema is
prepared:
Table- Invoice
Attribute Attribute data type Property
Invoice_ID Varchar Primary key
Purchase_info Text -
Final_price Integer -
Service_records Varchar -
Options Varchar -
Table- Customer
Attribute Attribute data type Property
C_ID Varchar Primary key
C_Name Text -
C_Address Varchar -
C_EmailID Varchar -
Table- Service Record
Attribute Attribute data type Property
Service_ID Varchar Primary key
Item_name Varchar -
Item_price Integer -
Item_quantity Varchar -
Iterm_year Year -
Dealer_name Varchar -
Manufacturer_name Varchar -
Table- Option
Attribute Attribute data type Property
Option_Code Varchar Primary key
Price Integer -
Description Text -
12