Salesforce CRM System Proposal for Video Game Company Project
VerifiedAdded on 2022/08/23
|43
|6754
|18
Project
AI Summary
This project proposal outlines the development and implementation of a Salesforce CRM system for a video game company. It begins with an overview of the company's current situation, highlighting the need for a more integrated system to manage customer relationships, sales, marketing, and other key business processes. The proposal details the project's goals and objectives, prerequisites, and scope, including specific modules such as user control, client management, analysis, and sales tracking. The requirements section covers business, user, functional, and non-functional requirements, ensuring the CRM system meets the company's needs effectively. The proposal also discusses the selection of a software development methodology, comparing the waterfall and agile methods, and justifying the best-suited approach. The design phase includes system interface design, activity diagrams, UML diagrams, and an entity-relationship diagram. Unit testing is described with specific test cases for various modules. The proposal aims to provide the video game company with a functional CRM system to improve customer satisfaction, streamline operations, and enhance overall business performance.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
VIDEO GAME COMPANY CUSTOMER RELATIONSHIP
MANAGEMENT SYSTEM PROPOSAL
(Student’s name)
(Department of (department’s name), University of (University’s name)
E-mail: (Student’s Email address)
Abstract
The success of any organization is a satisfied customer. This is the reason why in
recent years a growing trend of focusing on the customer has increased and their
needs have prevailed over the past ten years. The major aim of this proposal is to
analyze the use of Customer Relationship Management (CRM) for a Video
Company and find out the main determinants of Salesforce CRM system
implementation. To the Video Game Company, a fully functional Salesforce CRM
implementation can be considered a competitive advantage. By using a functional
Salesforce CRM interconnected with the current system, Video Game Company
will be able to manage its business, its direct marketing, online sales, and its
overall profits effectively. It is also important to note that a functional Video Game
Company system leads to an integrated system referred to as funnel management
that in turn improves CRM, and later leads to sustainable business.
Contents
MANAGEMENT SYSTEM PROPOSAL
(Student’s name)
(Department of (department’s name), University of (University’s name)
E-mail: (Student’s Email address)
Abstract
The success of any organization is a satisfied customer. This is the reason why in
recent years a growing trend of focusing on the customer has increased and their
needs have prevailed over the past ten years. The major aim of this proposal is to
analyze the use of Customer Relationship Management (CRM) for a Video
Company and find out the main determinants of Salesforce CRM system
implementation. To the Video Game Company, a fully functional Salesforce CRM
implementation can be considered a competitive advantage. By using a functional
Salesforce CRM interconnected with the current system, Video Game Company
will be able to manage its business, its direct marketing, online sales, and its
overall profits effectively. It is also important to note that a functional Video Game
Company system leads to an integrated system referred to as funnel management
that in turn improves CRM, and later leads to sustainable business.
Contents
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
1. Introduction...............................................................................................3
1.0 Overview of Video Game Company........................................................3
1.1 Current situation....................................................................................3
1.2 Problem statement.................................................................................4
1.3 Overview of the Problem........................................................................4
1.4 Goals and Objectives..............................................................................5
1.5 Prerequisites..........................................................................................6
1.6 Project Scope.........................................................................................7
1.6.1 Modules scope..................................................................................7
2. Requirements............................................................................................8
2.0 Overview................................................................................................8
2.1 Business Requirements..........................................................................8
2.2 Functional Requirements.....................................................................10
3.3 Non-Functional requirements..............................................................14
3. Software Development methodology........................................................16
3.1 Overview of software methodology......................................................16
3.2 Waterfall methodology.........................................................................16
3.2.0 Advantages of the waterfall method.................................................18
3.2.1 Disadvantages of Waterfall methodology..........................................19
3.3 Agile software methodology.................................................................20
3.3.1 Advantages of agile software methodology......................................21
3.3.2 Disadvantages of agile software methodology..................................22
3.4 Best suited methodology......................................................................22
1.0 Overview of Video Game Company........................................................3
1.1 Current situation....................................................................................3
1.2 Problem statement.................................................................................4
1.3 Overview of the Problem........................................................................4
1.4 Goals and Objectives..............................................................................5
1.5 Prerequisites..........................................................................................6
1.6 Project Scope.........................................................................................7
1.6.1 Modules scope..................................................................................7
2. Requirements............................................................................................8
2.0 Overview................................................................................................8
2.1 Business Requirements..........................................................................8
2.2 Functional Requirements.....................................................................10
3.3 Non-Functional requirements..............................................................14
3. Software Development methodology........................................................16
3.1 Overview of software methodology......................................................16
3.2 Waterfall methodology.........................................................................16
3.2.0 Advantages of the waterfall method.................................................18
3.2.1 Disadvantages of Waterfall methodology..........................................19
3.3 Agile software methodology.................................................................20
3.3.1 Advantages of agile software methodology......................................21
3.3.2 Disadvantages of agile software methodology..................................22
3.4 Best suited methodology......................................................................22
4. Design......................................................................................................24
4.1 System interface design....................................................................24
4.1.0 Interface design...........................................................................24
4.2 Activity diagram...................................................................................25
4.3 UML diagram.......................................................................................26
4.4 Entity Relationship diagram (ERD)......................................................27
4.5 CRM system architecture design.........................................................28
4.6 Top Level context diagram...................................................................29
4.7 Graphical User Interface......................................................................29
5 Testing........................................................................................................31
5.1 Unit testing...........................................................................................31
5.1.0 Unit test 1: staff or administrator unit testing...............................31
5.1.1 Unit test 2: Add new promotion.....................................................33
5.1.2 Unit test 3: Add customer..............................................................34
Sources..........................................................................................................36
1.Introduction
1.0 Overview of Video Game Company
Video Game Company is one of the developers and publisher of
computer games. Most of the games developed by the company are well
designed and pleasing by most of the customers. The company is well
known for the production of high quality games. Video Games products are
4.1 System interface design....................................................................24
4.1.0 Interface design...........................................................................24
4.2 Activity diagram...................................................................................25
4.3 UML diagram.......................................................................................26
4.4 Entity Relationship diagram (ERD)......................................................27
4.5 CRM system architecture design.........................................................28
4.6 Top Level context diagram...................................................................29
4.7 Graphical User Interface......................................................................29
5 Testing........................................................................................................31
5.1 Unit testing...........................................................................................31
5.1.0 Unit test 1: staff or administrator unit testing...............................31
5.1.1 Unit test 2: Add new promotion.....................................................33
5.1.2 Unit test 3: Add customer..............................................................34
Sources..........................................................................................................36
1.Introduction
1.0 Overview of Video Game Company
Video Game Company is one of the developers and publisher of
computer games. Most of the games developed by the company are well
designed and pleasing by most of the customers. The company is well
known for the production of high quality games. Video Games products are
purchased via various mediums, one of the main platform used by the
customers is the online platform. Some customers use mobile platforms.
Also, it is important to note that not all games developed by the company
which is sold. Other products offered by the company are novels, comics,
apparel, and board games. Soon, the company will be looking forward to
producing movies that will be based on plots and characters during the
production of computer games. Over the past two sales Video Game’s sales
have been up to 42 percent. This section will highlight the current situation
at Video Game Company, problem statement, and overview of the current
issues at Video Game Company, goals and objectives, pre-requisite, and
scope of the project.
1.1 Current situation
Video Game Company is accepting proposals for the development and
implementation of a new Salesforce CRM system. Currently, the Video
Game Company uses an automated system, a mobile platform, and an online
system which even though it has proven to be effective, the system is unable
to manage several of its disconnected manual processes. Also, the current
systems is unable to fulfill all the needs of the company. In addition, the
current system is not able to manage to report nor is able to effectively
manager clients’ contacts, maintain activity management, and perform sales
tracking. This means that the company needs a friendlier program which is
able to meet all these needs and maintain the company competitiveness. In
addition to the stated needs, a Salesforce CRM will also assist staff with
customers is the online platform. Some customers use mobile platforms.
Also, it is important to note that not all games developed by the company
which is sold. Other products offered by the company are novels, comics,
apparel, and board games. Soon, the company will be looking forward to
producing movies that will be based on plots and characters during the
production of computer games. Over the past two sales Video Game’s sales
have been up to 42 percent. This section will highlight the current situation
at Video Game Company, problem statement, and overview of the current
issues at Video Game Company, goals and objectives, pre-requisite, and
scope of the project.
1.1 Current situation
Video Game Company is accepting proposals for the development and
implementation of a new Salesforce CRM system. Currently, the Video
Game Company uses an automated system, a mobile platform, and an online
system which even though it has proven to be effective, the system is unable
to manage several of its disconnected manual processes. Also, the current
systems is unable to fulfill all the needs of the company. In addition, the
current system is not able to manage to report nor is able to effectively
manager clients’ contacts, maintain activity management, and perform sales
tracking. This means that the company needs a friendlier program which is
able to meet all these needs and maintain the company competitiveness. In
addition to the stated needs, a Salesforce CRM will also assist staff with
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
workflow processes which include client and membership management, and
event registration.
1.2 Problem statement
The purpose of this document is to provide an overview of Salesforce
CRM system package and to propose an implementation for the American
Video Company. The paper will also document propose the major aspects
which needs to be included in the CRM system and the best implementation
methodology.
1.3 Overview of the Problem
Over the last few years, companies have witnessed a growth in
internet-based services. Also, most of the companies have shifted their focus
to be more of customer-oriented. As stated in the company profile, Video
Game Company is one of the leading developers in computer games with
over 42 percent sales. According to Vodafone (2012), one of the major
issues faced by lots of companies is losing their customers. This can also
happen to Video Game Company. There major reasons why customer
turnover can happen like wrong pricing, poor customer service, lack of
product knowledge, poor store atmosphere and many others. Another major
reason why a company can face customer turnover is that poor relationships
with clients which leads to an increased customer defection rate. The only
tool that any company can employ to avoid that customer defection rate is a
Customer Relationship Management (CRM). Video Game Company can
employ CRM to satisfy, acquire, and retain all its profitable customers.
event registration.
1.2 Problem statement
The purpose of this document is to provide an overview of Salesforce
CRM system package and to propose an implementation for the American
Video Company. The paper will also document propose the major aspects
which needs to be included in the CRM system and the best implementation
methodology.
1.3 Overview of the Problem
Over the last few years, companies have witnessed a growth in
internet-based services. Also, most of the companies have shifted their focus
to be more of customer-oriented. As stated in the company profile, Video
Game Company is one of the leading developers in computer games with
over 42 percent sales. According to Vodafone (2012), one of the major
issues faced by lots of companies is losing their customers. This can also
happen to Video Game Company. There major reasons why customer
turnover can happen like wrong pricing, poor customer service, lack of
product knowledge, poor store atmosphere and many others. Another major
reason why a company can face customer turnover is that poor relationships
with clients which leads to an increased customer defection rate. The only
tool that any company can employ to avoid that customer defection rate is a
Customer Relationship Management (CRM). Video Game Company can
employ CRM to satisfy, acquire, and retain all its profitable customers.
Video Game Company also desires to maintain the design of its
products and by efficiently managing all its activities. Also, the company
aspires to maintain activity management, manage reporting, and its client’s
contacts. Also, most companies are unable to break the barrier between
their departments and to have a clear view of their customers. This proposal
aims at solving all these issues faced by Video Game Company through an
integrated Salesforce CRM. The proposal takes advantage of the lots of
capabilities that CRM has which in turn lead to both customer satisfaction
and an enhanced working environment for all Vide Game’s Company
employees (1).
1.4 Goals and Objectives
There are major goals and objectives that CRM system will seek to
achieve. First, Salesforce CRM project will let the company create an
analysis of every activity carried out. For example, the company staff will be
in a position to create an analysis of all its clients buying trends, bar graphs
to show sales made within a month to enable tracking of sales. Second, the
Salesforce CRM system will have a client profile module. The profile will
include all clients’ data such as purchase history, contacts, habit analysis,
and clients’ demographic data. The Salesforce CRM system will also include
a promotion management module which will include creation, modification,
and delivery of promotion to customers. Besides, the promotion module will
be in a position to detect and respond to a customer based promotion (2).
Third, the Salesforce CRM system will integrate with the existing system
products and by efficiently managing all its activities. Also, the company
aspires to maintain activity management, manage reporting, and its client’s
contacts. Also, most companies are unable to break the barrier between
their departments and to have a clear view of their customers. This proposal
aims at solving all these issues faced by Video Game Company through an
integrated Salesforce CRM. The proposal takes advantage of the lots of
capabilities that CRM has which in turn lead to both customer satisfaction
and an enhanced working environment for all Vide Game’s Company
employees (1).
1.4 Goals and Objectives
There are major goals and objectives that CRM system will seek to
achieve. First, Salesforce CRM project will let the company create an
analysis of every activity carried out. For example, the company staff will be
in a position to create an analysis of all its clients buying trends, bar graphs
to show sales made within a month to enable tracking of sales. Second, the
Salesforce CRM system will have a client profile module. The profile will
include all clients’ data such as purchase history, contacts, habit analysis,
and clients’ demographic data. The Salesforce CRM system will also include
a promotion management module which will include creation, modification,
and delivery of promotion to customers. Besides, the promotion module will
be in a position to detect and respond to a customer based promotion (2).
Third, the Salesforce CRM system will integrate with the existing system
i.e. the online and mobile platform to provide better analysis and production
of reports
1.5 Prerequisites
Number Pre-requisite Description Completion
date
001 RFP release date Proposal
submission date
1st April 2020
002 Finalize
interviews
Interviews of the
proposal
3rd April 2020
003 Proposal for
award
Award of the
CRM system
design
5th April 2020
004 Initial meeting Meeting with all
stakeholders and
users to gather
system
requirements
7th April 2020
005 CRM system
design
Start the process
of system design
From 9th April
2020 top 5th May
2020
of reports
1.5 Prerequisites
Number Pre-requisite Description Completion
date
001 RFP release date Proposal
submission date
1st April 2020
002 Finalize
interviews
Interviews of the
proposal
3rd April 2020
003 Proposal for
award
Award of the
CRM system
design
5th April 2020
004 Initial meeting Meeting with all
stakeholders and
users to gather
system
requirements
7th April 2020
005 CRM system
design
Start the process
of system design
From 9th April
2020 top 5th May
2020
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
006 Training and
implementation
Start the process
of training staff
on how to use
the system
6th May 2020 to
10th May 2020
007 Launch date Launching of the
CRM system
11th May 2020
1.6 Project Scope
The scope of this project proposal is to deliver a Salesforce CRM to
Video Game Company to help alleviate some of its issues, eliminate
customer defection rate, and maintain the company current standards. The
Salesforce CRM modules will specifically include user control, client
management, analysis, promotion management, sales tracking, reports
management, and activity management.
1.6.1 Modules scope
Using the analysis module, the company will be in a position to
analyze its market easier. Where after analysis the company will be in a
position to tell its clients base and a list of clients. This analysis will show if
there is a decrease or an increase in customers. Other modules such as
activity management, the company will be in a position to produce a list of
activities to be carried out in a certain period. The report management
module will be producing reports. The sales tracking module will track all
implementation
Start the process
of training staff
on how to use
the system
6th May 2020 to
10th May 2020
007 Launch date Launching of the
CRM system
11th May 2020
1.6 Project Scope
The scope of this project proposal is to deliver a Salesforce CRM to
Video Game Company to help alleviate some of its issues, eliminate
customer defection rate, and maintain the company current standards. The
Salesforce CRM modules will specifically include user control, client
management, analysis, promotion management, sales tracking, reports
management, and activity management.
1.6.1 Modules scope
Using the analysis module, the company will be in a position to
analyze its market easier. Where after analysis the company will be in a
position to tell its clients base and a list of clients. This analysis will show if
there is a decrease or an increase in customers. Other modules such as
activity management, the company will be in a position to produce a list of
activities to be carried out in a certain period. The report management
module will be producing reports. The sales tracking module will track all
the sales the company has made, by generating a list of sales made and a
list of those areas where sales have decreased (3).
2.Requirements
2.0 Overview
With the Salesforce CRM system in place, the company will in a
position to plan, control, and schedule post-sales and pre-sales in the Video
Game Company. The system embraces all aspects with customers, sales,
marketing, filed service, and call center. The Salesforce CRM aim at
improving both the short and long performance of the company. The system
also aims at providing an effective response from the organization clients
which will better gauge the return on investment of Video Game Company.
The system maximizes customer satisfaction, revenue, and profitability by
implementing customer-centric processes. This section will highlight
business requirements, functional and non-function requirements for the
CRM system.
list of those areas where sales have decreased (3).
2.Requirements
2.0 Overview
With the Salesforce CRM system in place, the company will in a
position to plan, control, and schedule post-sales and pre-sales in the Video
Game Company. The system embraces all aspects with customers, sales,
marketing, filed service, and call center. The Salesforce CRM aim at
improving both the short and long performance of the company. The system
also aims at providing an effective response from the organization clients
which will better gauge the return on investment of Video Game Company.
The system maximizes customer satisfaction, revenue, and profitability by
implementing customer-centric processes. This section will highlight
business requirements, functional and non-function requirements for the
CRM system.
2.1 Business Requirements
Video Game Company, is looking to integrate CRM with its current
system; a system that will meet its needs with efficiency and ease. The
company has identified a CRM platform and recognized five major areas
that the system needs to address which are;
The Salesforce CRM system should integrate with the existing system
and able to fulfill all the needs of the company
Allow an improved management of the various disconnected manual
processes and the company automated processes
The Salesforce CRM system should have the ability to improve data
sharing, business process flows and reporting
The Salesforce CRM system should be in a position to efficiently
manage all its clients’ contacts
The system should be able to perform sales tracking
The system ought to be in apposition to maintain activity management
The Salesforce CRM system should be in a position to manage the
production of reports (4).
Other business requirements are:
Consolidating all clients’ contacts and the company information
A system that interacts with client contacts and report all the
organization activities
The Salesforce CRM system should enable access to 3rd party but
must be under contract
Video Game Company, is looking to integrate CRM with its current
system; a system that will meet its needs with efficiency and ease. The
company has identified a CRM platform and recognized five major areas
that the system needs to address which are;
The Salesforce CRM system should integrate with the existing system
and able to fulfill all the needs of the company
Allow an improved management of the various disconnected manual
processes and the company automated processes
The Salesforce CRM system should have the ability to improve data
sharing, business process flows and reporting
The Salesforce CRM system should be in a position to efficiently
manage all its clients’ contacts
The system should be able to perform sales tracking
The system ought to be in apposition to maintain activity management
The Salesforce CRM system should be in a position to manage the
production of reports (4).
Other business requirements are:
Consolidating all clients’ contacts and the company information
A system that interacts with client contacts and report all the
organization activities
The Salesforce CRM system should enable access to 3rd party but
must be under contract
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
All the controls must be based on permission and roles for remote and
internal
User requirements
The following are user requirement which has to be considered
The ability of the Salesforce CRM system to archive information
without archiving it
Ability to perform daily Salesforce CRM system functions as it was
before such inserting purchases, uploading products
Ability to hard delete as required by only the managers in the various
levels
Ability to control access of data, and workflow
A CRM system that is user friendly
A System that is easy to use and intuitive
Ability to integrate in future without reliance on experts
A Salesforce CRM system that has the ability to be extended (5).
2.2 Functional Requirements
In a CRM system, functional requirements describe the utilities of the
CRM system. A function is nothing but its behavior, outputs, and outputs.
Functional requirements assist in capturing the intended behavior of the
Salesforce CRM system. The major aim of functional requirements, in this
case, is to ensure that the Video Game Company system is performing as
required (as stated in the business requirement part of this proposal).
internal
User requirements
The following are user requirement which has to be considered
The ability of the Salesforce CRM system to archive information
without archiving it
Ability to perform daily Salesforce CRM system functions as it was
before such inserting purchases, uploading products
Ability to hard delete as required by only the managers in the various
levels
Ability to control access of data, and workflow
A CRM system that is user friendly
A System that is easy to use and intuitive
Ability to integrate in future without reliance on experts
A Salesforce CRM system that has the ability to be extended (5).
2.2 Functional Requirements
In a CRM system, functional requirements describe the utilities of the
CRM system. A function is nothing but its behavior, outputs, and outputs.
Functional requirements assist in capturing the intended behavior of the
Salesforce CRM system. The major aim of functional requirements, in this
case, is to ensure that the Video Game Company system is performing as
required (as stated in the business requirement part of this proposal).
Functional testing is more of testing correctness and the workflow of the
system (6).
Functional test 1: Login module functional test
Aim: This done to ensure that the various users’ role log in displays various
navigation menu
S/NO Description Expected result Result
1 Public role The navigation
menu having
logout, register,
home
Pass
2 The admin module Admin has to
login using
username and
password. The
navigation to the
CRM system
with home, user,
settings, and log
out features
Pass
3 Customer module login A client has to
login using the
required details
(The navigation
Pass
system (6).
Functional test 1: Login module functional test
Aim: This done to ensure that the various users’ role log in displays various
navigation menu
S/NO Description Expected result Result
1 Public role The navigation
menu having
logout, register,
home
Pass
2 The admin module Admin has to
login using
username and
password. The
navigation to the
CRM system
with home, user,
settings, and log
out features
Pass
3 Customer module login A client has to
login using the
required details
(The navigation
Pass
button contains
promotion,
settings, logout,
and the home
button
4 Video Company staff The staff
member has to
login using
username and
password (on the
navigation bar
will have the add
promotion,
generate report,
analysis, home)
Pass
Customer profiling and filtering: This functional requirement ensures
that customer profile and filtering is working well. Users who are
supposed to perform this even include the HR manager, sales
manager, and the company CEO. The customer profile page shows
customer details, customer’s behavior, and their transaction history
Product analysis functional test: This is there to ensure analysis of
product. Users of this function are the HR manager, sales team, CEO,
promotion,
settings, logout,
and the home
button
4 Video Company staff The staff
member has to
login using
username and
password (on the
navigation bar
will have the add
promotion,
generate report,
analysis, home)
Pass
Customer profiling and filtering: This functional requirement ensures
that customer profile and filtering is working well. Users who are
supposed to perform this even include the HR manager, sales
manager, and the company CEO. The customer profile page shows
customer details, customer’s behavior, and their transaction history
Product analysis functional test: This is there to ensure analysis of
product. Users of this function are the HR manager, sales team, CEO,
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
and staff member. This function requirement also ensures editing of a
promotion, updating a promotion
Select promotion target client: This functional requirement is there to
ensure that the Salesforce CRM system can filter a list of clients and
target then which have to be based on a certain promotion (7).
Sending promotion to a customer: This requirement is there to ensure
a staff member can send a promotion to a client who users certain
computer games. Also, a client is able to respond to a certain
promotion
Promotion performance: This functional requirement is there to
ensure that a sales manager can be in a position to check the
performance of a certain promotion.
Audit trail: This functional requirement is there to extract trails which
includes date, time and user on what updates there have entered
Custom queries which are based in categories of information: This
functionality is there to extract client contacts
Report generation: This function requirement is there to ensure the
production of both ad hoc and standard report
Client membership tracking: This functional requirement is there to
track client membership status. Also the functionality checks inactive
and active members, and membership information renewal
Customer interactions: This functional requirement is track notes of
communication by using data and user stamp
promotion, updating a promotion
Select promotion target client: This functional requirement is there to
ensure that the Salesforce CRM system can filter a list of clients and
target then which have to be based on a certain promotion (7).
Sending promotion to a customer: This requirement is there to ensure
a staff member can send a promotion to a client who users certain
computer games. Also, a client is able to respond to a certain
promotion
Promotion performance: This functional requirement is there to
ensure that a sales manager can be in a position to check the
performance of a certain promotion.
Audit trail: This functional requirement is there to extract trails which
includes date, time and user on what updates there have entered
Custom queries which are based in categories of information: This
functionality is there to extract client contacts
Report generation: This function requirement is there to ensure the
production of both ad hoc and standard report
Client membership tracking: This functional requirement is there to
track client membership status. Also the functionality checks inactive
and active members, and membership information renewal
Customer interactions: This functional requirement is track notes of
communication by using data and user stamp
Document management: This functional requirement is there to track
the company documents and saved reports
Online system integration: This functional requirement ensures
integration with the current system which has an online platform
Mobile platform integration: This functional requirement is there to
ensure Salesforce CRM system integration with the current mobile
platform
Client interactions: This functionality is there to ensure a detailed
tracking of client behavior and track the amount spent by the client
on certain products.
Social network integration: This functional requirement provides a
blog interface
Mobile access: This functionality is there to ensure the ability to
access the company database from an offsite location such as cloud-
based access (8).
Other functional requirements
Create and update user: This function ensures Video management is
working as required
Create and update role in a Salesforce CRM system: This functionality
ensures that the management role is working as required
Creating and updating the Salesforce CRM system page: This
functionality ensures that the CRM system page is working as
required.
the company documents and saved reports
Online system integration: This functional requirement ensures
integration with the current system which has an online platform
Mobile platform integration: This functional requirement is there to
ensure Salesforce CRM system integration with the current mobile
platform
Client interactions: This functionality is there to ensure a detailed
tracking of client behavior and track the amount spent by the client
on certain products.
Social network integration: This functional requirement provides a
blog interface
Mobile access: This functionality is there to ensure the ability to
access the company database from an offsite location such as cloud-
based access (8).
Other functional requirements
Create and update user: This function ensures Video management is
working as required
Create and update role in a Salesforce CRM system: This functionality
ensures that the management role is working as required
Creating and updating the Salesforce CRM system page: This
functionality ensures that the CRM system page is working as
required.
Changing user password: Ensuring that the Salesforce CRM system
user can change their password
Generating sales reports
Tracking sales by indicating sales volume in each section
Tracking the number of customers and customers trend
3.3 Non-Functional requirements
There several CRM non-functional requirements which are;
Scalability: This is the ability of the Salesforce CRM system to handle
the ever-growing amount by the act of adding resources to the
Salesforce CRM system
Manageability: The CRM system will be manageable and user-friendly
Security: The CRM system will be secure and free from attacks
Some of the security features for this Salesforce CRM system will
include:
User authentication
Pages permission
Change password
Groups’ management and creation
User management
Serviceability: The Salesforce CRM system will be used with ease with
any device, and component
Reliability: The Salesforce CRM system will perform according to the
sated functional requirements and its specifications
user can change their password
Generating sales reports
Tracking sales by indicating sales volume in each section
Tracking the number of customers and customers trend
3.3 Non-Functional requirements
There several CRM non-functional requirements which are;
Scalability: This is the ability of the Salesforce CRM system to handle
the ever-growing amount by the act of adding resources to the
Salesforce CRM system
Manageability: The CRM system will be manageable and user-friendly
Security: The CRM system will be secure and free from attacks
Some of the security features for this Salesforce CRM system will
include:
User authentication
Pages permission
Change password
Groups’ management and creation
User management
Serviceability: The Salesforce CRM system will be used with ease with
any device, and component
Reliability: The Salesforce CRM system will perform according to the
sated functional requirements and its specifications
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Availability: The Salesforce CRM system will be available 24/7
Capacity
Performance
Interoperability: The ability of a Salesforce CRM system to work in
various platforms
Usability (9).
Capacity
Performance
Interoperability: The ability of a Salesforce CRM system to work in
various platforms
Usability (9).
3. Software Development methodology
3.1 Overview of software methodology
Any successful projects have to be well managed. For an organization
to manage a project effectively, a project manager needs to choose the nest
software development methodology which will work best for the project in
question. It is important to note that all software methodologies have their
weaknesses and strengths and they exist for various reasons (10).
Software development methodology is defined to be an abstract
process which is used for the development of software which includes
activities such as coding, testing, maintenance, and requirement analysis.
The most general model is analysis, development testing, deployment,
maintenance, and retirement. There are many existing software
development methods such as waterfall, scrum, spiral or extreme
programming, and many others. This section will highlight waterfall and
agile software methodologies (11).
3.2 Waterfall methodology
Waterfall software type of methodology is a technique were customer
and stakeholders requests are before the kickoff of system development
where a serial project plan is created to house user requirements. There are
five phases of waterfall methodology;
1st phase: Requirements phase: One of the important feature of waterfall
methodology is that all clients’ requirements are gathered first. This allow
3.1 Overview of software methodology
Any successful projects have to be well managed. For an organization
to manage a project effectively, a project manager needs to choose the nest
software development methodology which will work best for the project in
question. It is important to note that all software methodologies have their
weaknesses and strengths and they exist for various reasons (10).
Software development methodology is defined to be an abstract
process which is used for the development of software which includes
activities such as coding, testing, maintenance, and requirement analysis.
The most general model is analysis, development testing, deployment,
maintenance, and retirement. There are many existing software
development methods such as waterfall, scrum, spiral or extreme
programming, and many others. This section will highlight waterfall and
agile software methodologies (11).
3.2 Waterfall methodology
Waterfall software type of methodology is a technique were customer
and stakeholders requests are before the kickoff of system development
where a serial project plan is created to house user requirements. There are
five phases of waterfall methodology;
1st phase: Requirements phase: One of the important feature of waterfall
methodology is that all clients’ requirements are gathered first. This allow
other phases to be planned without further user or stakeholder’s
involvement until the system is completed. Here all requirements are
gathered at this phase (12).
2nd phase: The design phase: This phase is broken down into physical and
logical design. The physical design sub phase is where all the theoretical
ideas and system schemas are made into concrete specifications. On the
other hand the logical sub-phase is where possible feasible solutions are
theorized and brainstormed (13).
3rd phase: Implementation phase: This is when a programmer or the system
designer assimilates the system specifications and requirements from the
previous two phases. Here the actual code is produced
4th Phase: Verification: Here all customer or client’s views of the system are
reviewed with the initial stated products. This phase is achieved by
releasing a complete system to the system (14).
5th phase: Maintenance: This is the final phase which involves discovering of
bugs, system errors, and inadequate features which occurred during
production. The system production team applies all fixes until the customer
is satisfied.
Figure one highlights the overall process of waterfall methodology
Figure 1: Waterfall software methodology
involvement until the system is completed. Here all requirements are
gathered at this phase (12).
2nd phase: The design phase: This phase is broken down into physical and
logical design. The physical design sub phase is where all the theoretical
ideas and system schemas are made into concrete specifications. On the
other hand the logical sub-phase is where possible feasible solutions are
theorized and brainstormed (13).
3rd phase: Implementation phase: This is when a programmer or the system
designer assimilates the system specifications and requirements from the
previous two phases. Here the actual code is produced
4th Phase: Verification: Here all customer or client’s views of the system are
reviewed with the initial stated products. This phase is achieved by
releasing a complete system to the system (14).
5th phase: Maintenance: This is the final phase which involves discovering of
bugs, system errors, and inadequate features which occurred during
production. The system production team applies all fixes until the customer
is satisfied.
Figure one highlights the overall process of waterfall methodology
Figure 1: Waterfall software methodology
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
3.2.0 Advantages of the waterfall method
To start with waterfall it relies on the development teams following a
sequence of steps. The methodology never moves forward until the previous
phase of the model has been completed; the methodology is better suited
with smaller projects. Second, the methodology is useful and predictable if
system functional requirements are fixed, clear, and well-documented. Also,
waterfall approach produces a more predictable end result for scope,
timeline, and budget (15).
Third, waterfall methodology focuses on a clear and defined set of
steps. Waterfall methodology is simple where each and every system project
goes through basic steps, requirement gathering, system design,
implementation, testing, deployment or delivery, and maintenance. Forth,
waterfall methodology determines the end goal very early; the major aim of
waterfall methodology is commit to an end goal; it keeps focus on the end
goal. Fifth, waterfall methodology transfer information well as compared to
To start with waterfall it relies on the development teams following a
sequence of steps. The methodology never moves forward until the previous
phase of the model has been completed; the methodology is better suited
with smaller projects. Second, the methodology is useful and predictable if
system functional requirements are fixed, clear, and well-documented. Also,
waterfall approach produces a more predictable end result for scope,
timeline, and budget (15).
Third, waterfall methodology focuses on a clear and defined set of
steps. Waterfall methodology is simple where each and every system project
goes through basic steps, requirement gathering, system design,
implementation, testing, deployment or delivery, and maintenance. Forth,
waterfall methodology determines the end goal very early; the major aim of
waterfall methodology is commit to an end goal; it keeps focus on the end
goal. Fifth, waterfall methodology transfer information well as compared to
other methodologies; the methodology emphasizes on a clean transfer of
information.
Other advantages of waterfall are;
It allows managerial and departmentalization control
Easy and simple to use and understand
All model phases are completed and processed at one time
The model is easy to manage due to rigidity (16).
3.2.1 Disadvantages of Waterfall methodology
Even though waterfall methodology is respected by lots of software
engineers, lately it has been faced with criticism. First it is viewed as an
obsolete model. The technique drawbacks becomes more apparent
depending on type, goals, and size of the project. Second, waterfall
methodology makes changes difficult. As shown by figure one, waterfall is
based on a number of steps which keeps the development team moving
forward. This makes it not to leave any room for unexpected changes or
project revision (16). In case of changes, the model ends the project. Third
it excludes the end or the stakeholder; users or the stakeholders are only
involved at the before the kickoff of the project and no other time until the
completion of the project. This is done to assist the internal team move
more efficiently and faster through the other phases and steps of the project
faster. Forth, the methodology delays the process of testing until it is
completion. For Salesforce CRM system, postponing the testing phase up to
the last minute for a CRM project can be very tricky (18).
information.
Other advantages of waterfall are;
It allows managerial and departmentalization control
Easy and simple to use and understand
All model phases are completed and processed at one time
The model is easy to manage due to rigidity (16).
3.2.1 Disadvantages of Waterfall methodology
Even though waterfall methodology is respected by lots of software
engineers, lately it has been faced with criticism. First it is viewed as an
obsolete model. The technique drawbacks becomes more apparent
depending on type, goals, and size of the project. Second, waterfall
methodology makes changes difficult. As shown by figure one, waterfall is
based on a number of steps which keeps the development team moving
forward. This makes it not to leave any room for unexpected changes or
project revision (16). In case of changes, the model ends the project. Third
it excludes the end or the stakeholder; users or the stakeholders are only
involved at the before the kickoff of the project and no other time until the
completion of the project. This is done to assist the internal team move
more efficiently and faster through the other phases and steps of the project
faster. Forth, the methodology delays the process of testing until it is
completion. For Salesforce CRM system, postponing the testing phase up to
the last minute for a CRM project can be very tricky (18).
Other disadvantages of the model are:
It does not allow much of system revision or reflection
High amount of uncertainty and risk
Poor model for ongoing and long projects
Once a system is on the testing phase it is very difficult to back to the
initial phase or change a certain requirement
It is not good for complex project such CRM system (19).
3.3 Agile software methodology
This is a software type of methodology that promotes continuous
iteration of software development lifecycle. The methodology emphasizes on
four major areas which are team and individual interactions of tools and
processes, responding to change over following a plan, customer
collaboration over contract negotiation, and working system over a very
comprehensive documentation (20). Agile software methodology follows a
six process flow which are concept where systems are prioritized and
envisioned. Second is inception where team members are identified and
funding of the project is put in place and later the initial requirements and
environments are discussed. Then there is construction or iteration where
development team works to deliver a working CRM system which has to be
based on the iteration requirements and client’s feedback. Release is the
fourth agile process where quality testing, external and internal training,
documentation development, and where the final release of the iteration
into system production. The fifth agile process flow is production where
It does not allow much of system revision or reflection
High amount of uncertainty and risk
Poor model for ongoing and long projects
Once a system is on the testing phase it is very difficult to back to the
initial phase or change a certain requirement
It is not good for complex project such CRM system (19).
3.3 Agile software methodology
This is a software type of methodology that promotes continuous
iteration of software development lifecycle. The methodology emphasizes on
four major areas which are team and individual interactions of tools and
processes, responding to change over following a plan, customer
collaboration over contract negotiation, and working system over a very
comprehensive documentation (20). Agile software methodology follows a
six process flow which are concept where systems are prioritized and
envisioned. Second is inception where team members are identified and
funding of the project is put in place and later the initial requirements and
environments are discussed. Then there is construction or iteration where
development team works to deliver a working CRM system which has to be
based on the iteration requirements and client’s feedback. Release is the
fourth agile process where quality testing, external and internal training,
documentation development, and where the final release of the iteration
into system production. The fifth agile process flow is production where
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
ongoing support of the system and lastly is retirement which is the end of
life activities which includes migration and notification.
It is important to note that agile methodology is dominated by
iterative process. Each and every iteration is two to four weeks in length. A
sample iteration process flow is visualized in five phases which are
requirements where definition of requirements is done. In addition it is at
this phase where stakeholder and customer feedback is done. Then there is
development where design and development of software based is done but
on defined requirements. Another phase is testing where external training
is done. Then there is delivery and feedback where integration of existing
system is done. Also it is here customer and stakeholder acceptance is done.
Figure two below details agile software development methodology (21).
Figure 2: Agile software development methodology
life activities which includes migration and notification.
It is important to note that agile methodology is dominated by
iterative process. Each and every iteration is two to four weeks in length. A
sample iteration process flow is visualized in five phases which are
requirements where definition of requirements is done. In addition it is at
this phase where stakeholder and customer feedback is done. Then there is
development where design and development of software based is done but
on defined requirements. Another phase is testing where external training
is done. Then there is delivery and feedback where integration of existing
system is done. Also it is here customer and stakeholder acceptance is done.
Figure two below details agile software development methodology (21).
Figure 2: Agile software development methodology
3.3.1 Advantages of agile software methodology
One of the benefits of agile technique is stakeholder engagement
which is during, after, and before after every sprint. By involving
stakeholders in each and every step means that there that frequent
interaction between project development team and the stakeholders. It is
also provide more changes for the design to clearly understand client’s
vision. It also delivers w working software frequently and early which in
turn increases stakeholders trust. Second, agile encourages transparency
which in turn provides an opportunity to organizational users to be involved
throughout the project (22). Third, the methodology enables before time
delivery of the project. Fourth, the methodology makes the cost of the
project predictable since each and every sprint has a fixed duration. Fifth,
agile methodology allows change this because the development team are
always focused on delivering an agreed to subset of system features during
each and every iteration. Lastly, the methodology focuses on business value
by allowing a client to determine the priority of features (23).
One of the benefits of agile technique is stakeholder engagement
which is during, after, and before after every sprint. By involving
stakeholders in each and every step means that there that frequent
interaction between project development team and the stakeholders. It is
also provide more changes for the design to clearly understand client’s
vision. It also delivers w working software frequently and early which in
turn increases stakeholders trust. Second, agile encourages transparency
which in turn provides an opportunity to organizational users to be involved
throughout the project (22). Third, the methodology enables before time
delivery of the project. Fourth, the methodology makes the cost of the
project predictable since each and every sprint has a fixed duration. Fifth,
agile methodology allows change this because the development team are
always focused on delivering an agreed to subset of system features during
each and every iteration. Lastly, the methodology focuses on business value
by allowing a client to determine the priority of features (23).
3.3.2 Disadvantages of agile software methodology
Agile software methodology has been deployed by many industries
with a very great success. For instance, NPR Company uses agile software
methodology to create new programming. Other people who have used agile
software methodology are John Deere to develop the latest machinery. Even
though agile software methodology is rich in features and has been widely
utilized it has disadvantages. First development teams have been side-
tracked because of lack of processes (24). Most are the times, developers
proceed without a clear vision of what their final product would be. Also,
long-term systems project usually suffer from incremental delivery which
results to lack of checks and balances. Third, the level of collaboration in
agile methodology can be very difficult to maintain at times; it usually
requires endless collaboration, greater commitment, and additional time.
Developers ought to commit availability of the software team members, user
involvement to ensure that the system meets expectations, and sign-off at
each phase so as to allow developers to move ahead (25).
3.4 Best suited methodology
To start with, agile software methodology is currently the primary
development software design and it is being used by over fifty percent of
organizations as compared to other software development methodologies.
For this case, agile software methodology is best suited this because it will
segment the project requirements and goals for success into smaller
incremental sprints. Second, with agile it will enable the Salesforce CRM
Agile software methodology has been deployed by many industries
with a very great success. For instance, NPR Company uses agile software
methodology to create new programming. Other people who have used agile
software methodology are John Deere to develop the latest machinery. Even
though agile software methodology is rich in features and has been widely
utilized it has disadvantages. First development teams have been side-
tracked because of lack of processes (24). Most are the times, developers
proceed without a clear vision of what their final product would be. Also,
long-term systems project usually suffer from incremental delivery which
results to lack of checks and balances. Third, the level of collaboration in
agile methodology can be very difficult to maintain at times; it usually
requires endless collaboration, greater commitment, and additional time.
Developers ought to commit availability of the software team members, user
involvement to ensure that the system meets expectations, and sign-off at
each phase so as to allow developers to move ahead (25).
3.4 Best suited methodology
To start with, agile software methodology is currently the primary
development software design and it is being used by over fifty percent of
organizations as compared to other software development methodologies.
For this case, agile software methodology is best suited this because it will
segment the project requirements and goals for success into smaller
incremental sprints. Second, with agile it will enable the Salesforce CRM
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
system development team to quickly deliver iterations which are lined up
with expectations of users (26). Third, Salesforce CRM system
implementation projects usually emphasize on available resources, time,
and requirements. Agile software methodology is able to flip these
assumptions to suit the needs to the project. Forth, by using agile software
methodology value of the project is created earlier thereby increasing
accuracy and visibility. In terms of visibility, agile software methodology has
a continuous visibility of the outcomes and progress. Fifth, in terms of risk,
with agile there is a continuous testing which means that each sprint, the
value, and outcome is visible (27).
with expectations of users (26). Third, Salesforce CRM system
implementation projects usually emphasize on available resources, time,
and requirements. Agile software methodology is able to flip these
assumptions to suit the needs to the project. Forth, by using agile software
methodology value of the project is created earlier thereby increasing
accuracy and visibility. In terms of visibility, agile software methodology has
a continuous visibility of the outcomes and progress. Fifth, in terms of risk,
with agile there is a continuous testing which means that each sprint, the
value, and outcome is visible (27).
4.Design
4.1 System interface design
This Salesforce CRM system will utilize the use of PHP programming
language meaning that it will store all the files in one folder named as CRM.
The folder will contain various files which will be CSS file, images, SRC file,
widget, log file, index.php, and template file. It is also important to note that
the Salesforce CRM system will be using nested to generate dynamic
content web pages (28).
4.1.0 Interface design
The home page which will be php format will have the following
layout as shown below
Interface layout
Header
Navigation Menu
Content
4.1 System interface design
This Salesforce CRM system will utilize the use of PHP programming
language meaning that it will store all the files in one folder named as CRM.
The folder will contain various files which will be CSS file, images, SRC file,
widget, log file, index.php, and template file. It is also important to note that
the Salesforce CRM system will be using nested to generate dynamic
content web pages (28).
4.1.0 Interface design
The home page which will be php format will have the following
layout as shown below
Interface layout
Header
Navigation Menu
Content
Footer
4.2 Activity diagram
4.2 Activity diagram
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
4.3 UML diagram
4.4 Entity Relationship diagram (ERD)
4.5 CRM system architecture design
This can be thought as a sub-system decomposition diagram. Here all
packages are stands for sub-system which have to be implemented. Some of
the sub-system that have to be implemented in this Salesforce CRM system
are back-up which is design to provide consistency and reliability (29).
Organization business logic will be the major part of the architecture. It will
be the brain of the Salesforce CRM system which generates reports,
provides communication, manages other modules, and makes calculation.
Then there is the forecast manager, this the module which provides
business forecasting with the assistance of business logic. Then there is the
authorization manager which is the part of the architecture which assists to
define authorization for the various types of uses. The encryption manager
as shown in the figure below is the security guard. On the other hand the UI
manager decides the type of user entered into the system (30).
This can be thought as a sub-system decomposition diagram. Here all
packages are stands for sub-system which have to be implemented. Some of
the sub-system that have to be implemented in this Salesforce CRM system
are back-up which is design to provide consistency and reliability (29).
Organization business logic will be the major part of the architecture. It will
be the brain of the Salesforce CRM system which generates reports,
provides communication, manages other modules, and makes calculation.
Then there is the forecast manager, this the module which provides
business forecasting with the assistance of business logic. Then there is the
authorization manager which is the part of the architecture which assists to
define authorization for the various types of uses. The encryption manager
as shown in the figure below is the security guard. On the other hand the UI
manager decides the type of user entered into the system (30).
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
4.6 Top Level context diagram
This will include four major internal areas which are data access
platform, data access components, business logic, and web services. The
external entities are;
Customer: views products
Administrator: controls the CRM systems
Company staff user: Controls clients contacts and gest reports from
the Salesforce CRM system
Moderator (31).
This will include four major internal areas which are data access
platform, data access components, business logic, and web services. The
external entities are;
Customer: views products
Administrator: controls the CRM systems
Company staff user: Controls clients contacts and gest reports from
the Salesforce CRM system
Moderator (31).
4.7 Graphical User Interface
Navigation GUI design general view is as shown below
The functional GUI design is shown below
Navigation GUI design general view is as shown below
The functional GUI design is shown below
5 Testing
After full design of the Salesforce CRM system, testing has to be done.
This is done to confirm that the system can handle the various situations.
After full design of the Salesforce CRM system, testing has to be done.
This is done to confirm that the system can handle the various situations.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Two forms of system testing which will be carried out which are; functional
and unit testing [31]. The Salesforce CRM system testing will be completed
by a number of actions to test the Salesforce CRM’s ability to perform the
various functions (32).
5.1 Unit testing
This is the first form of testing; where every unit of the system will be
done. Here the system analyst will input every possible input like the
correct input, wrong format, empty input and other possible input. This is
all done to verify the input as invalid or correct. The first unit testing to be
carried out will be user login module (33).
5.1.0 Unit test 1: staff or administrator unit testing
Aim: To ensure the CRM system login form is working as required
Description: Here there will be four possible scenarios which are;
Login with an empty password and username
Login with right username and empty password
Login with exact password and empty username
Login with the right username and accurate password
Table one below shows the expected results
and unit testing [31]. The Salesforce CRM system testing will be completed
by a number of actions to test the Salesforce CRM’s ability to perform the
various functions (32).
5.1 Unit testing
This is the first form of testing; where every unit of the system will be
done. Here the system analyst will input every possible input like the
correct input, wrong format, empty input and other possible input. This is
all done to verify the input as invalid or correct. The first unit testing to be
carried out will be user login module (33).
5.1.0 Unit test 1: staff or administrator unit testing
Aim: To ensure the CRM system login form is working as required
Description: Here there will be four possible scenarios which are;
Login with an empty password and username
Login with right username and empty password
Login with exact password and empty username
Login with the right username and accurate password
Table one below shows the expected results
Table 1: Unit testing one-login form validation
No Description Expected results Outcome
1 The right details i.e. correct
password and username
Successful login,
directed to CRM
homepage
Pass
2 The wrong details i.e. correct
password but wrong
username
Failed login (two
attempts remaining)
error message :
Wrong username or
password
Failed: 2 attempts
remaining
3 The wrong details i.e. correct
username but wrong
password
Failed login (two
attempts remaining)
error message :
Wrong username or
password
Failed: 2 attempts
remaining
4 The wrong details i.e. wrong
password but wrong
username
Failed login (two
attempts remaining)
error message :
Wrong username or
password
Failed: 2 attempts
remaining
5 The wrong details i.e. correct
password but empty
password
Failed login (two
attempts remaining)
error message :
Failed: 2 attempts
remaining
No Description Expected results Outcome
1 The right details i.e. correct
password and username
Successful login,
directed to CRM
homepage
Pass
2 The wrong details i.e. correct
password but wrong
username
Failed login (two
attempts remaining)
error message :
Wrong username or
password
Failed: 2 attempts
remaining
3 The wrong details i.e. correct
username but wrong
password
Failed login (two
attempts remaining)
error message :
Wrong username or
password
Failed: 2 attempts
remaining
4 The wrong details i.e. wrong
password but wrong
username
Failed login (two
attempts remaining)
error message :
Wrong username or
password
Failed: 2 attempts
remaining
5 The wrong details i.e. correct
password but empty
password
Failed login (two
attempts remaining)
error message :
Failed: 2 attempts
remaining
Wrong username or
password
6 The wrong details i.e. empty
password but wrong
username
Failed login (two
attempts remaining)
error message :
Wrong username or
password
Failed: 2 attempts
remaining
7 The wrong details i.e. empty
password but empty
username
Failed login (two
attempts remaining)
error message : Put in
credentials
Failed: Putting
login credentials
5.1.1 Unit test 2: Add new promotion
Aim: To ensure that a Video Company Staff input the correct details about a
certain promotion
Description: There are various scenarios where a staff enter invalid details,
empty details, and correct details (34). Table highlights the three possible
cases
No Description Expected Result Result
1 Insert the correct details
of promotion i.e. valid
date, valid start date,
valid content
Enter the
promotion title
and redirect to
client filtering
Pass
password
6 The wrong details i.e. empty
password but wrong
username
Failed login (two
attempts remaining)
error message :
Wrong username or
password
Failed: 2 attempts
remaining
7 The wrong details i.e. empty
password but empty
username
Failed login (two
attempts remaining)
error message : Put in
credentials
Failed: Putting
login credentials
5.1.1 Unit test 2: Add new promotion
Aim: To ensure that a Video Company Staff input the correct details about a
certain promotion
Description: There are various scenarios where a staff enter invalid details,
empty details, and correct details (34). Table highlights the three possible
cases
No Description Expected Result Result
1 Insert the correct details
of promotion i.e. valid
date, valid start date,
valid content
Enter the
promotion title
and redirect to
client filtering
Pass
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
page
2 Insert the empty details
of promotion i.e. empty
date, empty start date, no
content
Error message:
Enter all the
fields
Failed
3 Insert the wrong details
of promotion i.e. invalid
date, invalid start date,
no content
Error message:
Enter all the
fields
Failed
5.1.2 Unit test 3: Add customer
Aim: This module ensures the registration of a client
Description: This module has several functionalities which are registering
customer user customer, management of customer details. The table below
shows the whole of testing.
S/no. Description Expected result Result
1 Registering client details
with valid details that is
their valid names, valid
access code , valid I/C
number, and valid
password
Staff is re-
directed to the
CRM system
login
Pass
2. Registering a customer The staff Failed
2 Insert the empty details
of promotion i.e. empty
date, empty start date, no
content
Error message:
Enter all the
fields
Failed
3 Insert the wrong details
of promotion i.e. invalid
date, invalid start date,
no content
Error message:
Enter all the
fields
Failed
5.1.2 Unit test 3: Add customer
Aim: This module ensures the registration of a client
Description: This module has several functionalities which are registering
customer user customer, management of customer details. The table below
shows the whole of testing.
S/no. Description Expected result Result
1 Registering client details
with valid details that is
their valid names, valid
access code , valid I/C
number, and valid
password
Staff is re-
directed to the
CRM system
login
Pass
2. Registering a customer The staff Failed
with duplicate username,
duplicate valid access
code, and duplicate I/C
members gets an
error feedback
message
3 Registering a client with
empty username, empty
I/C number, and Access
Code, empty client details
Error message Failed
4 Registering a client with
valid I/C number, invalid
Access code, valid
username
Error message Failed
5 Registering customer
with invalid customer
details, valid I/C number,
and valid Access code
(35)
Error message Failed
duplicate valid access
code, and duplicate I/C
members gets an
error feedback
message
3 Registering a client with
empty username, empty
I/C number, and Access
Code, empty client details
Error message Failed
4 Registering a client with
valid I/C number, invalid
Access code, valid
username
Error message Failed
5 Registering customer
with invalid customer
details, valid I/C number,
and valid Access code
(35)
Error message Failed
Sources
1. Pan. Z, A case study: CRM adoption success factor analysis and Six
Sigma DMAIC application, Elsevier Press, Amsterdam, 2015.
2. Bhaskar. R, A customer relationship management system to target
customers at Cisco,Wiley Press, Chicago, 2016.
3. Beltman. R, Customer relationship management, John & Wiley Press,
Amsterdam, 2014.
4. Fjermestad N. C. R. Jr, Electronic Customer Relationship Management.,
1. Pan. Z, A case study: CRM adoption success factor analysis and Six
Sigma DMAIC application, Elsevier Press, Amsterdam, 2015.
2. Bhaskar. R, A customer relationship management system to target
customers at Cisco,Wiley Press, Chicago, 2016.
3. Beltman. R, Customer relationship management, John & Wiley Press,
Amsterdam, 2014.
4. Fjermestad N. C. R. Jr, Electronic Customer Relationship Management.,
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Taylor and Francis Press, Amsterdam,2015.
5. Schierholz .R, Mobile customer relationship management, Wiley Press,
NY, 2016.
6. Ahn. J, On the design concepts for CRM system, Industrial Management
& Data Systems, 2003.
7. Kumar. V, Customer Relationship Management : concept, strategy, and
tools, Springer Press, Chicago, 2014.
8. Rajola. F, Customer relationship management : organizational and
technological perspectives, Springer Press, London, 2011.
9. Hung. J, Critical factors of hospital adoption on CRM system:
Organizational and information system perspectives, Decision Support
Systems, Elsevier Press, Amsterdam, 2014.
10. Rittinghouse. M, Managing software deliverables : a software
development management methodology, Elsevier Press, Amsterdam,
2011.
11. Rababah. K, Customer relationship management (CRM) processes from
theory to practice, The pre-implementation plan of CRM system, 2017.
12. Wong. W and Cukic B, Adaptive control approach for software quality
improvement, 2013.
13. Xu.M, Gaining customer knowledge through analytical CRM, Industrial
management & data systems, Elsevier Press, Amsterdam, 2006.
14. Bassil, A simulation model for the waterfall software development life
cycle, 2015.
5. Schierholz .R, Mobile customer relationship management, Wiley Press,
NY, 2016.
6. Ahn. J, On the design concepts for CRM system, Industrial Management
& Data Systems, 2003.
7. Kumar. V, Customer Relationship Management : concept, strategy, and
tools, Springer Press, Chicago, 2014.
8. Rajola. F, Customer relationship management : organizational and
technological perspectives, Springer Press, London, 2011.
9. Hung. J, Critical factors of hospital adoption on CRM system:
Organizational and information system perspectives, Decision Support
Systems, Elsevier Press, Amsterdam, 2014.
10. Rittinghouse. M, Managing software deliverables : a software
development management methodology, Elsevier Press, Amsterdam,
2011.
11. Rababah. K, Customer relationship management (CRM) processes from
theory to practice, The pre-implementation plan of CRM system, 2017.
12. Wong. W and Cukic B, Adaptive control approach for software quality
improvement, 2013.
13. Xu.M, Gaining customer knowledge through analytical CRM, Industrial
management & data systems, Elsevier Press, Amsterdam, 2006.
14. Bassil, A simulation model for the waterfall software development life
cycle, 2015.
15. Robinson. C, Fundamentals of DevOps : Waterfall Software
Development, Skillsoft Corporation Press, London, 2011.
16. Balaji. M, Waterfall vs. V-Model vs. Agile: A comparative study on
SDLC, Skillsoft Corporation Press, London, 2010.
17. Sinnett. W, Agile vs. Waterfall , Packt Publishing Ltd, Birmingham ,
2018, pp 134-178.
18. Ingeno. J, Software Architect's Handbook : Become a Successful
Software Architect by Implementing Effective Architecture Concepts,
Packt Publishing Ltd, Birmingham , 2008.
19. Trivedi. S, A comparative study between iterative waterfall and
incremental software development life cycle model for optimizing the
resources using computer simulation, 2013.
20. Schmidt. C, Agile Software Development Teams., Springer International
Press, Chicago, 2013.
21. Huo. B, Software quality and agile methods, 2013.
22. Highsmith. A, Agile software development ecosystems, 2010.
23. Leau. Y, Software development life cycle AGILE vs traditional
approaches, 2017.
24. Highsmith. C, Agile software development: The business of innovation,
2018.
25. Bhalerao. K, Generalizing Agile software development life cycle, Wiley
Press, Chicago, 2019.
26. Kung. D, Object-oriented software engineering : an agile unified
Development, Skillsoft Corporation Press, London, 2011.
16. Balaji. M, Waterfall vs. V-Model vs. Agile: A comparative study on
SDLC, Skillsoft Corporation Press, London, 2010.
17. Sinnett. W, Agile vs. Waterfall , Packt Publishing Ltd, Birmingham ,
2018, pp 134-178.
18. Ingeno. J, Software Architect's Handbook : Become a Successful
Software Architect by Implementing Effective Architecture Concepts,
Packt Publishing Ltd, Birmingham , 2008.
19. Trivedi. S, A comparative study between iterative waterfall and
incremental software development life cycle model for optimizing the
resources using computer simulation, 2013.
20. Schmidt. C, Agile Software Development Teams., Springer International
Press, Chicago, 2013.
21. Huo. B, Software quality and agile methods, 2013.
22. Highsmith. A, Agile software development ecosystems, 2010.
23. Leau. Y, Software development life cycle AGILE vs traditional
approaches, 2017.
24. Highsmith. C, Agile software development: The business of innovation,
2018.
25. Bhalerao. K, Generalizing Agile software development life cycle, Wiley
Press, Chicago, 2019.
26. Kung. D, Object-oriented software engineering : an agile unified
methodology, McGraw-Hill Press, New York, 2013.
27. Flewelling. P, The Agile developer's handbook : get more value from
your software development : get the best out of the Agile methodology,
2014.
28. Humphrey, A displine of Software design, 2017.
29. Meister. D and Enderwick. T.P. , Human factors in system design,
development, and testing, Erlbaum Press, Amsterdam, 2014. pp 134-
178.
30. Ghezzi. M, Fundamentals of software engineering, Wiley Press,
Newyork, 2014.
31. Wohlin. W, Experimentation in software engineering, John & Wiley
Press, Chicago, 2017, pp 234-298.
32. Naik. P.T.K , Software testing and quality assurance: theory and
practice: Software testing, Wiley Press, Chicago, 2013, pp. 45-78.
33. Ullman. R, Quality Assurance for Computer Soft-ware, Chicago Press,
Chicago, 2014, pp. 109-130.
34. Anderson.K and Kerr C., Customer relationship management, Springer
Press, New York, 2013.
35. Foss. B, What makes for CRM system success—Or failure?: Journal of
Database Marketing & Customer Strategy Management, 2008, pp 134-
178.
27. Flewelling. P, The Agile developer's handbook : get more value from
your software development : get the best out of the Agile methodology,
2014.
28. Humphrey, A displine of Software design, 2017.
29. Meister. D and Enderwick. T.P. , Human factors in system design,
development, and testing, Erlbaum Press, Amsterdam, 2014. pp 134-
178.
30. Ghezzi. M, Fundamentals of software engineering, Wiley Press,
Newyork, 2014.
31. Wohlin. W, Experimentation in software engineering, John & Wiley
Press, Chicago, 2017, pp 234-298.
32. Naik. P.T.K , Software testing and quality assurance: theory and
practice: Software testing, Wiley Press, Chicago, 2013, pp. 45-78.
33. Ullman. R, Quality Assurance for Computer Soft-ware, Chicago Press,
Chicago, 2014, pp. 109-130.
34. Anderson.K and Kerr C., Customer relationship management, Springer
Press, New York, 2013.
35. Foss. B, What makes for CRM system success—Or failure?: Journal of
Database Marketing & Customer Strategy Management, 2008, pp 134-
178.
1 out of 43
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
![[object Object]](/_next/static/media/star-bottom.7253800d.svg)
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.