This document describes a dashboard and reporting system created by a Capstone team for an insurance agency. The system gathers sales data and provides visualization tools and reports to help producers track performance against goals and allow managers to oversee the agency. It was designed to eliminate manual data tracking and provide current information centrally. The team believes the system could benefit a real insurance agency if implemented.

1.
Dashboard
for
Insurance
Agencies
Capstone
Design
Project
Submitted
By:
Stefanie
Boros
Amra
Iskander
Pallavi
Khadamkar
Namita
Nair

2. 2
EXECUTIVE
SUMMARY
This
report
has
been
prepared
by
the
members
of
our
Capstone
team
as
part
of
the
Capstone
project
for
the
MSIS
program
at
Santa
Clara
University.
Our
team
was
successfully
able
to
draw
upon
our
collective
experiences
in
the
program
in
order
to
design,
create
and
complete
a
cloud-­‐based
system
that
provides
sales
data
to
an
insurance
agency.
Our
system
provides
a
Dashboard
and
Reporting
capabilities
as
well
as
Goal
Setting.
Though
the
system
has
not
actually
been
implemented
in
a
real-­‐world
setting,
it
could
easily
provide
great
value
to
an
insurance
agency.
The
system
focuses
on
gathering
the
sales
data
and
providing
tools
to
make
the
data
meaningful
with
minimal
effort.
The
Producer
is
responsible
for
selling
the
insurance
policies
to
the
Clients
and
he
or
she
has
certain
goals
that
are
set
for
him
or
her
by
Management
every
year.
Our
system
provides
up-­‐to-­‐date
visualization
of
where
each
Producer
stands
at
a
given
time
with
regard
to
new
business,
retention
as
well
as
other
measurements.
A
Manager
is
able
to
check
on
any
of
the
Producers
as
well
as
the
agency
as
a
whole.
Both
the
Producer
and
Management
are
able
to
run
reports
to
display
new
business,
retention
and
a
combination
of
both,
with
Management
having
additional
reporting
tools
to
measure
the
quality
of
the
book
of
business
and
Carrier
statistics.
Beyond
that,
Management
has
the
ability
to
set
goals
for
each
Producer.
There
is
no
longer
a
need
for
manual
Excel
spreadsheets
or
calculations.
All
of
the
most
important
information
is
readily
available
with
the
most
current
data.
The
final
deliverables
include
the
specifications
and
design
of
the
project,
testing
details,
potential
implementation
information,
future
enhancements
and
the
working
system.
Our
team
is
incredibly
proud
of
our
final
product
and
feels
confident
that
it
could
benefit
a
typical
insurance
agency
if
given
the
opportunity
to
be
implemented.
Our
system
was
heralded
by
a
real
insurance
agency
Vice
President
as
being
able
to
“become
an
integral
part
of
our
insurance
agency
operations
and
will
certainly
help
us
to
achieve
our
revenue
goals
and
take
us
to
the
next
level”.

3. 3
TABLE
OF
CONTENTS
I.
Introduction
Background…………………………………………………………………………………………………….……….5
Proposed
Solutions………………………………………………………………………………………………….6
System
Actors………………………………………………………………………………………………………….6
Business
Needs
and
Scope………………………………………………………………………………………..7
II.
Project
Planning
Project
Staffing………………………………………………………………………………………………………..9
Project
Timeline……………………………………………………………………………………………………...9
Project
Methodology……………………………………………………………………………………………..13
Risks…………………………………………………………………………………………………………………….13
Assumptions……………………………………………………………………………………………………...…14
Dependencies……………………………………………………………………………………………………….15
Project
Deliverables…………………………………………………………………………………………...…15
III.
Analysis
Design
Requirements
Definition……………………………………………………………………………………….16
Use
Cases……………………………………………………………………………………………………………...21
Data
Flow
Diagrams…………………………………………………………………………………...…………34
Data
Dictionary…………………………………………………………………………………………………….47
IV.
Design
Phase
Architecture
Design……………………………………………………………………………………………...56
Program
Design……………………………………………………………………………………………………63
Database
Design…………………………………………………………………………………………………...69
V.
Implementation
Phase
Testing………………………………………………………………………………………………………………...70
User
Guide…………………………………………………………………………………………………………144

4. 4
VI.
Conclusion
Success
Criteria………………………………………………………………………………………………….162
Future
Enhancements………………………………………………………………………………………...162
VII.
Appendix
Letter
from
Lighthouse
Management…………………………………………………………………..164

5. 5
I. Introduction
Background
This
project
was
conceived
to
solve
real
problems
in
a
simulated
environment.
While
it
is
possible
for
our
system
to
be
useful
to
insurance
agencies,
we
have
not
actually
been
contracted
to
create
this
system
for
use
in
a
real
business.
We
were
fortunate
enough
to
have
access
to
a
Vice
President
at
an
insurance
agency,
who
provided
us
with
guidance
throughout
the
process
so
that
our
finished
product
represents
the
needs
of
an
actual
client.
We
were
also
provided
with
data
to
use
made
up
of
fictitious
information
to
help
us
understand
real-­‐world
insurance
policies.
Lighthouse
Group
is
an
insurance
agency
located
in
West
Michigan
with
24
offices
in
the
region.
They
provide
services
to
over
5,000
clients
offering
Property
&
Casualty,
Benefits
and
Life
insurance.
Management
holds
several
meetings
throughout
the
year
to
keep
abreast
of
goals
with
the
Producers
as
well
as
the
insurance
Carriers
that
they
work
with,
though
much
of
the
data
is
gathered
manually
or
through
excel.
They
have
a
main
system
that
houses
all
of
the
quoting
and
policy
details
but
it
is
not
efficient
in
providing
the
figures
that
the
company
needs
to
effectively
run
the
business
and
maintain
the
goals
they
marked
at
the
beginning
of
the
year.
An
all
too
common
theme
is
for
Management
to
come
up
with
expectations
of
the
Producers
and
organization
as
a
whole
in
January,
only
to
realize
in
December
that
they
are
missing
key
targets.
With
Lighthouse
having
to
rely
on
Excel
spreadsheets
and
manual
reports,
they
are
not
only
doing
extra
work,
but
they
are
likely
going
to
miss
important
data
such
as
where
revenue
is
compared
to
the
goals
set
or
what
Niches
are
proving
to
be
most
profitable,
either
by
accident
or
because
it
is
too
much
effort
to
get
the
information.
The
main
policy
system
that
they
use
is
full
of
policy
data,
but
it
is
not
designed
to
input
targets,
provide
visualization
of
business
data
or
generate
reports.
A
comparable
system
with
a
provider
such
as
salesforce.com
is
extremely
expensive
(sometimes
at
$1,500
per
seat
per
year)
and
not
an
option
for
a
company
like
Lighthouse.
Though
the
tools
it
could
provide
would
help
solve
the
problem,
the
cost
just
is
not
feasible
for
them.

6. 6
Proposed
Solution
As
with
any
sales
organization,
there
are
always
ways
that
they
can
improve
their
profitability
and
our
system
will
assist
in
increasing
visibility
of
their
targets
and
sales
measures.
The
dashboard
system
serves
two
main
purposes.
The
first
is
to
give
the
Producers
and
Management
a
snapshot
of
where
they
are
at
toward
their
goals
year-­‐to-­‐date.
This
lets
them
know
with
the
click
of
a
button
where
they
stand
and
will
be
an
integral
part
of
their
keeping
on
track
throughout
the
year.
The
second
aspect
of
the
system
is
the
reporting
element.
At
any
time,
Management
can
run
a
detailed
report
with
a
variety
of
specifications
to
get
up-­‐to-­‐date
information
and
statistics.
The
main
objective
of
the
system
is
to
allow
the
members
of
the
company
to
keep
their
fingers
on
the
pulse
of
the
vital
pieces
of
information
that
inform
them
of
where
they
are
and
where
they
need
to
go.
These
measurements,
and
the
knowledge
of
them,
are
what
can
make
or
break
a
company.
A
note
from
our
contact,
Mike
Boros
(see
Appendix
A),
highlights
the
usefulness
and
necessity
of
a
system
such
as
the
one
we
created.
System
Actors
• Lighthouse
Group
Management
-­‐
There
is
a
Manager
for
each
Department
(Property
&
Casualty,
Benefits
and
Life),
and
an
overall
Manager
for
the
organization.
Each
Manager
is
responsible
for
the
performance
of
the
Producers
in
their
department.
• Lighthouse
Group
Producers
-­‐
The
Producers
are
the
employees
responsible
for
selling
insurance
policies
to
the
clients.
They
act
as
advisors
to
the
client
and
guide
them
to
find
the
right
insurance
coverage
with
the
right
Carrier
for
the
company.
They
have
goals
set
for
them
by
their
Manager
and
have
to
meet
certain
criteria
each
year.
• Lighthouse
Group
Account
Managers
-­‐
The
Account
Managers
are
responsible
for
assisting
the
Producers
in
servicing
the
Clients.
They
complete
the
data
entry
for
the
Producers
and
act
as
the
first
line
of
contact
with
their
accounts.

7. 7
Business
Needs
and
Scope
There
were
different
features
we
thought
about
adding
but
ultimately
settled
on
the
scope
for
sales
tracking,
reporting
and
goal
setting.
Since
our
model
agency,
Lighthouse,
uses
their
main
system
to
provide
prospecting
and
financial
tools,
we
did
not
go
down
those
paths.
We
considered
a
customer
service
element
that
would
help
the
Producer
keep
track
of
important
dates
and
contacts,
but
thought
that
adding
this
feature
might
go
beyond
the
bounds
that
a
6-­‐month
project
would
allow.
Our
main
concern
is
thus
on
what
written
accounts
Lighthouse
Producers
have
in
their
book
of
business
and
what
the
goals
were
for
the
current
year.
A
big
concern
for
Management
is
accountability
and
the
present
state
of
the
agency.
Our
system
provides
this
and
will
allow
Management
to
not
only
stay
on
top
of
their
Producers
but
also
to
identify
areas
that
need
immediate
attention.
We
were
able
to
identify
the
key
solutions
that
would
provide
Lighthouse
with
the
most
benefit:
• Goal
Setting
and
Tracking
-­‐
An
element
of
the
system
that
is
currently
only
available
to
Lighthouse
through
a
manually
entered
Excel
spreadsheet
is
goal
setting
and
tracking.
Each
Producer
has
a
sales
goal
that
is
set
at
the
beginning
of
the
year.
In
order
to
move
past
unsophisticated
methods
of
tracking,
it
is
important
to
integrate
the
ability
for
Lighthouse
to
enter
specific
goals
each
year
for
the
Producers
and
then
be
able
to
keep
the
status
of
these
goals
at
the
forefront.
o Example:
A
Producer
has
a
goal
set
by
Management
of
$100,000
in
new
business
for
the
year.
The
system
will
show
this
goal
and
compare
it
to
the
new
business
that
was
entered
for
that
Producer
in
the
year.
• Visibility
of
Sales
Performance
-­‐
The
main
system
that
Lighthouse
is
currently
using
to
house
client
information
is
effective
in
storing
the
data,
but
does
not
allow
Lighthouse
employees
to
easily
view
important
statistics
and
up-­‐to-­‐date
sales
figures.
It
is
incredibly
important
for
the
Producers
and
Management
to
know
where
they
stand
in
certain
areas
at
any
given
time.
For
example,
a
Producer
will
want
to
see
how
much
business
they
have
written
up
to
that
date
and
Management
is
going
to
want
to
see
how
the
agency
is
performing
overall,
perhaps
with
the

8. 8
percentage
of
new
business
accounts
that
were
written.
With
the
Dashboard
aspect
of
our
system,
an
employee
can
log
on
and
view
their
latest
data,
based
on
their
custom
settings.
Having
this
information
available
with
just
a
simple
login
will
ensure
that
the
Producers
and
Management
remain
informed
with
the
most
accurate
sales
data
possible.
o Example:
Management
can
view
their
Dashboard
at
any
given
moment
and
can
see
how
much
new
business
the
company
has
written
as
well
as
the
retention
percentage
of
existing
accounts.
• Useful
Analysis
of
Information
-­‐
Using
the
information
gathered
and
stored
in
the
system,
Lighthouse
can
gain
insights
and
identify
patterns
that
can
inform
Management
to
make
data-­‐
driven
business
decisions
and
leverage
it
for
its
competitive
advantage.
As
trends
and
relationships
in
the
data
are
uncovered,
Management
can
ask
new
questions
and
iterate
on
the
process
until
the
business
goal
is
met.
o Example:
Management
can
view
the
amount
of
new
business
for
a
certain
niche
(such
as
Agriculture
accounts)
and
discover
if
the
accounts
seem
to
be
profitable
and
should
be
pursued
more
heavily
in
the
future.
• Provide
Accurate
and
Timely
Reporting
Tools
-­‐
Often,
Lighthouse
relies
on
numerous
offline
Excel
spreadsheets
owned
by
different
departments
to
understand
where
the
company
is
standing
in
terms
of
business
performance.
This
antiquated
method
is
inefficient
and
impedes
fast
decision
making
for
the
business.
With
the
new
system,
reporting
tools
are
available
for
Management
to
gain
accurate
and
timely
charts
in
order
to
help
them
plan
for
the
future.
o Example:
The
system
will
allow
for
a
wide
variety
of
reports
to
be
produced,
but
an
important
element
of
the
business
is
to
run
reports
for
the
Carriers
that
they
work
with.
The
Carriers
want
to
know
how
much
new
business
and
retention
they
have
with
Lighthouse
compared
with
the
goals
they
have
agreed
upon.

9. 9
II.
Project
Planning
Project
Staffing
Name Role Responsibilities
Stefanie
Boros Team
Member
&
Business
Analyst
Lead
Formed
the
idea
for
the
project
and
identified
the
appropriate
users,
their
needs
and
what
functionalities
were
important
for
the
system
to
have.
Amra
Iskander Team
Leader
&
Product
Management
Lead
Managed
the
system
development
timelines
and
developed
the
system
functionalities
for
Producer
and
Management.
Pallavi
Khadamkar Team
Member
&
Technical
Lead
Managed
and
implemented
the
security
and
session
management
features
for
the
system
and
facilitated
the
integration
of
the
codes.
Namita
Nair Team
Member
&
Technical
Lead
Implemented
system
functionalities
for
account
managers
and
designed
and
deployed
the
overall
system
architecture
on
the
cloud.
Yasin
Ceran Capstone
Advisor Gave
appropriate
guidance
for
the
direction
of
the
project
and
frequent
feedback
on
the
progress
made.
Project
Timeline
The
team
knew
the
importance
of
project
planning
and,
with
the
guidance
of
our
advisor,
Professor
Ceran,
set
up
as
realistic
a
timeline
as
possible
in
order
to
maintain
a
steady
and
forward-­‐
moving
pace.
No
matter
how
skilled
a
team
or
how
impressive
a
product
is,
without
proper
planning,
there
is
only
a
recipe
for
disaster.
We
made
sure
that
we
considered
all
of
the
important
milestones
for
the
project
as
well
as
set
realistic
but
ambitious
deadlines
to
keep
us
on
track.
Phase Deliverables Activities Duration Actual
Initiation Project
Overview Introductory
Meeting Start
date:
1/7/2015
End
date:
1/7/2015
Start
date:
1/7/2015
End
date:
1/7/2015

10. 10
System
Concept
Development
Define
Scope
and
Boundaries
Develop
System
Boundary
Document
Start
date:
1/8/2015
End
date:
2/5/2015
Start
date:
1/8/2015
End
date:
2/5/2015
Planning Create
Project
Management
Plan
Chalk
Out
the
Plan
of
Actions Start
date:
2/6/2015
End
date:
2/28/2015
Start
date:
2/6/2015
End
date:
2/28/2015
Create
Schedule
for
Requirement
Gathering
Identify
Proper
Configurations
Required
to
Set
Up
Individual
Systems
(PCs)
Requirement
Analysis
Analyze
user
requirements
Identify
user’s
needs Start
date:
1/22/2015
End
date:
2/28/2015
Start
date:
1/22/2015
End
date:
2/28/2015
Create
requirements
definition
document
1.
The
document
would
capture
technical
solution.
2.
Number
of
hours
needed
to
accomplish
the
task.
3.
The
go
live
date
time.
Design Create
Design
Documents
Create
architecture
diagram
identifying
the
following
parameters:
Start
date:
1/22/2015
Start
date:
1/22/2015

11. 11
1.
Users
2.
Application
Interface
3.
Database
layer
End
date:
3/31/2015
End
date:
3/31/2015
Define
the
system
flow.
1.Create
use
cases,
data
flow
diagrams
and
structure
charts
to
chalk
out
the
user
and
application
interaction.
Create
a
prototype
of
the
entire
new
screens/user
interface
using
programming
language
and
review
for
approval.
Development Setup
Environment
Install
Apache
Server Start
date:
4/1/2015
End
date:
4/30/2015
Start
date:
4/1/2015
End
date:
4/30/2015
Install
mySQL
server
Check
database
connectivity
Implement
multi-­‐user
case
Coding Start
development
of
user
interfaces
as
per
requirements
Start
Date:
4/8/2015
End
Date:
4/30/2015
Start
Date:
4/1/2015
End
Date:
5/15/2015

12. 12
Code
review Create
a
standard
checklist
for
code
review.
Start
Date:
4/22/2015
End
Date:
4/30/2015
Start
Date:
5/16/2015
End
Date:
5/23/2015
Conduct
code
review
to
make
it
compliant
as
per
the
checklist.
Testing Create
test
plans Create
unit
test
plans
inclusive
of
positive
and
negative
test
cases
based
on
the
functional
requirement
document
Start
Date:
5/1/2015
End
Date:
5/8/2015
Start
Date:
5/1/2015
End
Date:
5/8/2015
Perform
testing
on
development
environment
Perform
manual
testing
based
on
the
test
plan
Start
date:
5/8/2015
End
date:
5/22/2015
Start
date:
5/9/2015
End
date:
5/22/2015
In
case
of
failure
of
any
test
case,
redevelop
the
screen
and
execute
all
test
cases
again
unless
the
system
passes
all
of
them
Implementation Deployment Deploy
all
necessary
modified
or
newly
created
interfaces
on
the
production
server.
Start
date:
5/15/2015
End
date:
5/29/2015
Start
date:
5/23/2015
End
date:
6/6/2015
Test
the
changes
on
production
environment
Execute
all
test
cases
on
production
environment
to
check
the
new
interfaces
are
intact
and
running
as
expected

13. 13
Project
Methodology
In
our
project,
we
used
a
combination
of
methodologies
to
help
us
manage
the
process
and
complete
our
development
work.
• Waterfall
-­‐
At
the
start
of
the
project
and
throughout
the
project,
we
used
a
sequential
design
process
known
as
the
waterfall
methodology
to
execute
our
development
work
in
different
phases.
The
project
went
through
a
phase
of
conception
where
we
gathered
the
business
needs
of
the
project.
At
this
stage
we
communicated
intensely
with
the
Lighthouse
team
to
understand
the
user
needs.
We
moved
on
to
the
analysis
and
design
stage
where
we
translated
the
requirements
gathered
into
physical
and
logical
design
documents
to
scope
out
the
system
requirements
further.
From
that,
we
started
the
code
implementation
stage
and
began
testing
once
the
different
components
of
the
program
were
integrated.
Once
the
system
was
implemented
on
the
cloud,
the
team
rigorously
tested
the
system
to
ensure
it
was
robust.
• Rapid
Prototyping
-­‐
In
the
process
of
managing
the
project
using
the
waterfall
methodology,
we
created
software
prototypes
of
the
system
at
the
design
and
analysis
stage.
This
is
to
ensure
that
it
matches
the
requirements
that
we
have
gathered.
We
also
used
the
prototype
to
gather
feedback
from
the
users
so
that
we
can
improve
the
system
to
make
it
as
user-­‐friendly
as
possible.
• Scrum
-­‐
When
it
came
to
developing
the
code
for
the
system,
we
used
Scrum
to
schedule
priorities
for
each
sprint.
The
team
met
on
a
weekly
basis
to
select
the
tasks
and
scope
out
the
estimated
time
needed
to
complete
these
tasks.
In
these
meetings,
the
team
discussed
the
functionalities
and
identified
how
the
development
work
would
be
carried
out.
The
team
lead
would
send
out
the
sprint
tasks
to
the
entire
team.
At
the
end
of
each
sprint,
status
updates
were
sent
out
to
track
the
team’s
progress.
Risks
• Technical
Risks
-­‐
The
hardware
must
satisfy
at
least
the
standard
system
requirements
such
as:
o Computer
and
Processor:
1
gigahertz
(GHz)
or
faster
x86
or
x64
bit
processor
with
SSE2
instruction
set

14. 14
o Memory
(RAM):
1
gigabyte
(GB)
RAM
(32-­‐bit);
2
gigabytes
(GB)
RAM
(64-­‐bit)
o Hard
Disk:
3.0
gigabytes
(GB)
available
o Display:
Graphics
hardware
acceleration
requires
a
DirectX10
graphics
card
and
a
1024
x
576
or
higher
resolution
monitor
o Operating
system:
Windows
operating
system
o .NET
version
3.5,
4.0
or
4.5
• Project
Risks
o Any
changes
in
requirements
could
delay
the
proposed
timeline
o The
Capstone
team
may
need
to
spend
time
learning
new
technologies
that
may
be
necessary
to
use
to
develop
the
system
o Scope
creep
-­‐
Increase
in
development
time
will
result
in
insufficient
time
for
testing,
giving
rise
to
unknown
bugs
o Limited
access
to
Lighthouse
resources
Assumptions
• Technical
Assumptions
o MySQL
database
will
be
compatible
or
need
minimal
development
effort
to
interface
it
with
Apache
server
and
other
open
source
codes
o There
is
no
OS
preference
and
will
be
compatible
with
Windows
and
MAC
Operating
Systems
o Connection
to
the
server
is
always
readily
available
• Project
Assumptions
o The
new
system
will
be
implemented
by
June
2015
o The
new
system
will
be
a
prototype
o Lighthouse
will
take
responsibility
of
implementing
the
system
if
they
choose
to
adopt
the
new
system
o The
new
system
will
be
designed
on
the
capability
of
easy
configuration
and
minimal
customization
effort
to
implement

15. 15
Dependencies
• Wi-­‐Fi
connectivity
for
the
team
to
complete
the
project
on
schedule
• Access
to
the
database
• Dependency
on
Capstone
MSIS
management
for
regular
feedback
and
verification
of
the
project
progress
and
for
necessary
information
and
documentation
related
to
the
system
and
database
• Access
to
an
up
and
running,
available
server
Project
Deliverables
The
team
has
provided
a
complete
and
functioning
system
as
well
as
this
report,
including
analysis
and
design
cases,
diagrams
and
charts,
test
cases
and
a
user
manual.

16. 16
III.
Analysis
Design
Requirements
Definition
Functional
Requirements
–
Process
Oriented
Account
Manager
1.
Search
for
existing
records
1.1
The
system
will
allow
Account
Managers
to
search
for
records
by
Company
Name,
Effective
Date,
Zip
Code
on
the
homepage.
1.2
The
system
will
display
a
maximum
of
5
search
results
of
the
last
added/searched/edited
records
on
the
homepage.
2.
Edit
existing
records
2.1
The
system
will
enable
Account
Managers
to
edit
existing
policy
or
line
of
business
(LoB)
information.
2.2
The
system
will
enable
Account
Managers
to
add
a
new
LoB.
2.3
The
system
will
enable
Account
Managers
to
delete
a
LoB.
3.
Renew
existing
records
3.1
The
system
will
enable
Account
Managers
to
select
the
renewal
button
on
the
homepage.
3.2
The
system
will
enable
Account
Managers
to
change
the
effective
and
expiration
dates.
3.3
The
system
will
enable
Account
Managers
to
modify
the
LoB
information.
4.
Cancel
existing
records
4.1
The
system
will
enable
Account
Managers
to
select
the
cancellation
button
on
the
homepage.
4.2
The
system
will
enable
Account
Managers
to
enter
the
cancellation
date.
5.
Delete
existing
records
5.1
The
system
will
enable
Account
Managers
to
select
the
delete
button
on
the
homepage.
5.2
The
system
will
verify
if
the
account
should
be
deleted.
6.
Add
new
records
6.1
The
system
will
enable
Account
Managers
to
enter
the
policy
information.
6.2
The
system
will
validate
the
policy
information
entered.

17. 17
6.3
The
system
will
store
the
policy
information
in
the
connect_lob_client
datastore.
6.4
The
system
will
enable
Account
Managers
to
enter
the
LoB
information.
6.5
The
system
will
validate
the
LoB
information
entered.
6.6
The
system
will
store
the
LoB
information
in
the
LoB
data
store.
Producer
1.
Display
goals
set
for
each
Producer
on
the
dashboard
1.1
The
system
will
display
goals
specific
to
the
Producer
on
the
goal
dashboard.
2.
Update
actual
results
2.1
The
system
will
calculate
the
actual
results
of
each
goal
and
display
the
values
against
the
goal
set
to
track
performance
progress.
3.
Display
charts
3.1
The
system
will
calculate
and
display
cross-­‐sold
policies
by
number
of
accounts.
3.2
The
system
will
calculate
and
display
niche
breakdown
by
revenue.
3.3
The
system
will
calculate
and
display
niche
breakdown
by
commission.
3.4
The
system
will
calculate
and
display
niche
breakdown
by
number
of
accounts.
3.5
The
system
will
calculate
and
display
new
business
per
month.
4.
Display
Newsfeed
updates
4.1
The
system
will
display
newsfeed
updates
when
a
client
account
is
added,
renewed
or
cancelled.
4.2
The
system
will
enable
Producers
to
click
on
the
update
to
view
the
record
details.
5.
Run
reports
5.1
The
system
will
enable
Producers
to
select
pre-­‐defined
reports
and
parameters
to
generate
reports.
Management
1.
Display
goals
set
for
company-­‐wide
and
each
Producer
1.1
The
system
will
display
the
goals
specific
to
the
company
on
the
goal
dashboard.
1.2
The
system
will
display
the
goals
specific
to
each
Producer
on
the
goal
dashboard.
2.
Update
actual
results

18. 18
2.1
The
system
will
calculate
the
actual
results
of
each
goal
and
display
the
values
against
the
goal
set
to
track
performance
progress
for
the
entire
company.
2.2
The
system
will
calculate
the
actual
results
of
each
goal
and
display
the
values
against
the
goal
set
to
track
performance
progress
for
each
Producer.
3.
Display
charts
3.1
The
system
will
calculate
and
display
cross-­‐sold
policies
by
number
of
accounts
for
the
entire
company
and
for
each
Producer.
3.2
The
system
will
calculate
and
display
niche
breakdown
by
revenue
for
the
entire
company
and
for
each
Producer.
3.3
The
system
will
calculate
and
display
niche
breakdown
by
commission
for
the
entire
company
and
for
each
Producer.
3.4
The
system
will
calculate
and
display
niche
breakdown
by
number
of
accounts
for
the
entire
company
and
for
each
Producer.
3.5
The
system
will
calculate
and
display
new
business
per
month.
4.
Run
Reports
4.1
The
system
will
enable
Management
to
select
pre-­‐defined
reports
and
parameters
to
generate
reports.
5
Set
goals
5.1
The
system
will
enable
Management
to
set
company
wide
book
of
business
and
retention
goals.
5.2
The
system
will
calculate
new
business
goals
based
on
the
book
of
business
and
retention
goals.
5.3
The
system
will
calculate
each
Producer’s
recommended
book
of
business,
retention
and
new
business
goals
based
on
each
Producer’s
historical
performance
over
two
years.
5.4
The
system
will
calculate
new
Producers’
recommended
book
of
business,
retention
and
new
business
goals
based
on
a
typical
Producer’s
historical
performance
over
two
years.
5.5
The
system
will
enable
Management
to
edit
recommendations.
5.6
The
system
will
store
the
new
goals
set
in
the
Producer
data
store.

19. 19
Functional
Requirements
–
Process
Oriented
1.
The
system
will
contain
client
information.
2.
The
system
will
contain
LoB
information.
3.
The
system
will
contain
department
information.
4.
The
system
will
contain
carrier
information.
5.
The
system
will
contain
login
information.
6.
The
system
will
contain
niche
information.
7.
The
system
will
contain
producer
information.
8.
The
system
will
contain
LoB
history
information.
9.
The
system
will
contain
information
on
the
roles
of
each
employee.
10.
The
system
will
contain
policy
information.
Nonfunctional
Requirements
1.
Operational
1.1
The
system
should
run
on
any
internet-­‐connected
device
with
a
web
browser.
1.2
The
system
should
be
able
to
work
on
any
web
browsers.
2.
Performance
2.1
The
system
should
support
50-­‐100
concurrent
users.
2.2
The
system
should
be
updated
with
changes
made
to
the
database
immediately.
2.3
The
system
will
be
backed
up
through
the
cloud
every
night.
3.
Security
3.1
Passwords
will
be
encrypted
in
transmission
to
and
from
the
database.
3.2
Users
will
be
prompted
to
change
their
passwords
every
6
months.
3.3
Passwords
set
will
be
checked
for
their
strength
following
the
digit,
character,
upper
case,
lower
case
and
at
least
8
characters
standards.
3.4
Users
are
not
allowed
to
use
previous
3
passwords
used
when
users
are
resetting
or
changing
their
passwords.

20. 20
3.5
Data
in
flight
will
be
secured
through
https
implementation
between
the
web
server
and
database
server
in
the
cloud.
3.6
Users
can
log
in
from
another
location
when
a
session
is
in
use
and
the
system
will
log
the
user
out
from
the
previous
session
and
continue
the
new
session
in
the
new
location.
3.7
The
system
will
end
the
session
and
wipe
out
any
data
that
is
not
saved
if
the
session
is
idle
for
20
minutes.
3.8
No
user
can
access
the
data
of
another
user,
other
than
Management.
4.
Cultural
and
Political
4.1
The
system
will
adopt
the
Lighthouse
logo
and
color
scheme.
4.2
The
system
will
run
on
Amazon
Web
Service
(AWS)
cloud.
4.3
Customer
personal
information
is
protected
in
compliance
with
the
Data
Protection
Act.

21. 21
Use
Cases
Login
Use
Cases
Use
Case
Name:
ALL
–
Login
Actor:
All
Users
Description:
This
use
case
describes
how
a
user
would
be
able
to
log
in
to
the
system.
Trigger:
User
wants
to
log
in.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
user
has
the
credentials
and
access
to
the
system.
Normal
Course: Information
for
Steps:
1. Go
to
login
page
2. System
accepts
username
from
the
user
3. System
accepts
password
from
the
user
4. System
validates
the
user
5. System
retrieves
username
from
the
login_info
datastore
6. System
retrieves
password
from
the
login_info
datastore
7. System
matches
the
username
against
the
7.1. Password
7.2. System
updates
the
login_status
to
1
in
the
login_info
datastore
8. System
checks
the
user
role
of
the
logged
in
person
9. System
retrieves
the
role_ID
of
the
record
from
login_info
datastore
10. System
redirects
the
user
to
the
admin
homepage
if
the
role_ID
is
1
11. System
redirects
the
user
to
the
producer
homepage
if
the
role_ID
is
2
12. System
redirects
the
user
to
the
management
homepage
if
the
role_ID
is
3
13. System
updates
the
login_info
datastore
14. System
updates
the
session_ID
in
login_info
datastore
I:
Username
I:
Password
I:
Username
I:
Password
O:
login_status
I:
role_ID
O:
session_ID
Postconditions:
• User
is
logged
in
to
the
system.
• DataStore
is
updated
with
the
login_status
and
session_ID.
Inputs Source Outputs Destination
Username
Password
Username
Password
role_ID
User
User
login_info
Datastore
login_info
Datastore
login_info
Datastore
login_status
session_ID
login_info
Datastore
login_info
Datastore

22. 22
Use
Case
Name:
ALL
-­‐
Forgot
Password
Actor:
All
Users
Description:
This
use
case
describes
how
a
user
would
be
able
to
change
their
password
if
they
forgot
it.
Trigger:
User
forgets
password.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
user
has
the
credentials
and
access
to
the
system.
Normal
Course: Information
for
Steps:
1. Go
to
login
page
2. If
session
already
exists
on
one
browser
2.1. System
3. Enter
email
address
into
field
4. Click
on
“Generate
Password”
5. Check
email
and
click
on
the
link
to
change
password
6. Enter
email
ID,
temporary
ID
(given
in
the
email),
new
password
and
confirm
password
7. Select
“submit”
8. Log
out
or
continue
into
system
Postconditions:
• Password
is
updated
in
the
database.
Inputs Source Outputs Destination

23. 23
Account
Manager
Use
Cases
Use
Case
Name:
Account
Manager
-­‐
Add
Client
Actor:
Account
Manager
Description:
This
use
case
describes
how
an
Account
Manager
would
add
a
new
client.
Trigger:
Producer
writes
a
business
and
notifies
the
Account
Manager
to
add
it
to
the
system.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Producer
has
given
the
Account
Manager
the
complete
information
to
enter.
• The
Account
Manager
has
the
credentials
and
access
to
the
system.
Normal
Course: Information
for
Steps:
1. Account
Manager
receives
Client
information
from
the
Producer
2. Log
in
to
system
3. In
the
Home
Page
click
on
‘Add
New
Record’
button
3.1
Input
Client
Information
3.2
Input
Line
of
Business
3.3
Click
on
submit
3.4
May
have
multiple
Lines
of
Business
3.4.1
Click
“submit”
after
entering
each
Line
of
Business
4.
Display
Line
of
Business
Information
5.
Update
Line
of
Business
Information
5.1
Change
values
in
the
form
5.2
Click
on
Update
to
update
the
values
I:
Producer’s
Client
Info
I:
Client
Information
O:
Line
of
Business
Info
Postconditions:
• The
system
updates
the
database
with
Client
information.
• The
system
notifies
the
Producer
selected
via
news
feed
on
their
Dashboard
of
the
addition.
• Updated
information
will
be
reflected
in
reports.
Inputs Source Outputs Destination
Producer’s
Client
Info
Client
Information
User
User
Line
of
Business
Info client
data
store
connect_lob_client
data
store

24. 24
Use
Case
Name:
Account
Manager
-­‐
Edit
Client
Actor:
Account
Manager
Description:
This
use
case
describes
how
an
Account
Manager
would
edit
an
existing,
active
Client
by
either
adding
another
Line
of
Business,
changing
policy
information
and/or
existing
Line
of
Business
information
or
adding/editing
loss
information.
Trigger:
Producer
notifies
the
Account
Manager
to
make
changes
to
a
Client
in
the
system.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Producer
has
given
the
Account
Manager
the
complete
information
to
enter.
• The
Account
Manager
has
the
credentials
and
access
to
the
system.
Normal
Course: Information
for
Steps:
1. Account
Manager
receives
Client
information
from
the
Producer
to
be
edited
2. Log
in
to
system
3. In
search
bar,
enter
name
of
Client
and
search
3.1
Search
first
by
full
name
3.2
Try
partial
name(s)
if
unsuccessful
4.
Select
“Edit”
next
to
the
Client
and
Term
being
edited
5a.
If
adding
Line
of
Business
5a.1
Select
“Add
Line
of
Business”
5a.2
Enter
Line
of
Business
details
5a.3
Select
“Add
LoB”
5a.4
Update
appropriate
fields
5a.5
Update
appropriate
fields
5a.6
Once
all
information
is
updated,
select
“Update”
5b.
If
editing
Account
information
5b.1
Update
appropriate
fields
5b.2
Once
all
information
is
updated,
select
“Update”
5c.
If
deleting
a
Line
of
Business
5c.1
Select
“Delete”
next
to
LoB
to
be
deleted
5c.2
A
confirmation
message
shows
5c.3
Click
“Ok”
to
delete
the
LoB
6.
Go
back
to
search
page
or
log
out
I:
User
info
I:
Search
info
I:
Line
of
business
info
O:
Line
of
business
info
I:
Account
info
O:
Account
info
Postconditions:
• The
system
updates
the
database
with
Client
information.
• Updated
information
will
be
reflected
in
reports.
Inputs Source Outputs Destination
User
info
Search
info
Line
of
business
info
Account
info
User
User
connect_lob_client
data
store
client
data
store
Line
of
business
info
Account
info
Account
info
connect_lob_client
data
store
client
data
store
client
data
store

25. 25
Use
Case
Name:
Account
Manager
-­‐
Renew
Client
Actor:
Account
Manager
Description:
This
use
case
describes
how
an
Account
Manager
would
renew
an
existing,
active
Client
by
either
adding
another
Line
of
Business,
changing
policy
information
and/or
existing
Line
of
Business
information
or
adding/editing
loss
information.
Trigger:
Producer
notifies
the
Account
Manager
to
make
changes
to
a
Client
in
the
system.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Producer
has
given
the
Account
Manager
the
complete
information
to
enter.
• The
Account
Manager
has
the
credentials
and
access
to
the
system.
Normal
Course: Information
for
Steps:
1. Account
Manager
receives
Client
information
from
the
Producer
to
be
edited
2. Log
in
to
system
3. In
search
bar,
enter
name
of
Client
and
search
3.1
Search
first
by
full
name
3.2
Try
partial
name(s)
if
unsuccessful
4.
Select
“Renew”
next
to
the
Client
and
Term
being
edited
5.
If
editing
Line
of
Business
information
5.1
Update
appropriate
fields
5.2
Once
all
information
is
updated,
select
“Renew”
6.
Go
back
to
search
page
or
log
out
I:
Line
of
business
Information
O:Line
of
business
Information
Postconditions:
• The
system
updates
the
database
with
Client
information.
• Updated
information
will
be
reflected
in
reports.
Inputs Source Outputs Destination
Line
of
business
Information User Line
of
business
Information connect_lob_client
data
store
lob_history
data
store

26. 26
Use
Case
Name:
Account
Manager
-­‐
Delete
Client
or
LoB
Actor:
Account
Manager
Description:
This
use
case
describes
how
an
Account
Manager
would
delete
an
existing,
active
Client
or
Line
of
Business.
Trigger:
Producer
notifies
the
Account
Manager
to
delete
the
Client
or
Line
of
Business
in
the
system.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Producer
has
given
the
Account
Manager
the
complete
information
to
enter.
• The
Account
Manager
has
the
credentials
and
access
to
the
system.
Normal
Course: Information
for
Steps:
1. Account
Manager
receives
Client
information
from
the
Producer
to
be
deleted
2. Log
in
to
system
3. In
search
bar,
enter
name
of
Client
and
search
3.1
Search
first
by
full
name
3.2
Try
partial
name(s)
if
unsuccessful
4.
If
deleting
entire
Client
4.1
Select
“Delete”
next
to
desired
Client
and
Term
4.2
A
confirmation
message
is
shown
4.3
Click
“Ok”
5.
Go
back
to
search
page
or
log
out
I:
Policy
information
Postconditions:
• The
system
updates
the
database
with
Client
information.
• Updated
information
will
be
reflected
in
reports.
Inputs Source Outputs Destination
Policy
information User

27. 27
Use
Case
Name:
Account
Manager
-­‐
Cancel
Client
Actor:
Account
Manager
Description:
This
use
case
describes
how
an
Account
Manager
would
cancel
an
existing
Client.
Trigger:
Producer
notifies
the
Account
Manager
that
a
Client
has
cancelled
their
policy
and
it
needs
to
be
updated
in
the
system.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Producer
has
given
the
Account
Manager
the
complete
information.
• The
Account
Manager
has
the
credentials
and
access
to
the
system.
Normal
Course: Information
for
Steps:
1. Account
Manager
receives
Client
information
from
the
Producer
to
be
cancelled
2. Log
in
to
system
3. In
search
bar,
enter
name
of
Client
and
search
3.1
Search
first
by
full
name
3.2
Try
partial
name(s)
if
unsuccessful
4. Enter
the
cancellation
date
5. Select
“Cancel”
next
to
the
Client
being
cancelled
6. Confirm
cancellation
7. Policy
is
cancelled
8. Go
back
to
search
page
or
log
out
I:
Client
info
I:
Line
of
business
info
O:
Client
info
Postconditions:
• The
system
updates
the
database
with
Client
information.
• Updated
information
will
be
reflected
in
reports.
Inputs Source Outputs Destination
Client
info
Line
of
business
info
User Client
information connect_lob
client
data
store
lob_history_data
store

28. 28
Use
Case
Name:
Account
Manager
-­‐
Sign
Up
User
Actor:
Account
Manager
Description:
This
use
case
describes
how
an
Account
Manager
would
add
a
new
user
to
the
system.
Trigger:
New
employee
is
hired
as
either
an
Account
Manager,
Producer
or
Manager.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Account
Manager
has
the
complete
information
to
enter.
Normal
Course: Information
for
Steps:
1. Account
Manager
receives
sign
up
information
from
the
new
employee
2. Log
in
to
system
3. Select
“Sign
Up”
4. Fill
in
user’s
email,
password
then
confirm
the
password
5. Select
“Submit”
6. Go
back
to
search
page
or
log
out
I:
Username/password
I:
Sign
up
info
O:
Sign
up
info
Postconditions:
• The
system
updates
the
database
with
sign
up
information.
• The
DB
Administrator
will
assign
the
appropriate
role
to
the
user
in
the
Roles
database.
Inputs Source Outputs Destination
Username
Password
Sign
up
info
Account
Manager
Account
Manager
Account
Manager
Sign
up
info Login_Info
database

29. 29
Producer
Use
Cases
Use
Case
Name:
Producer
-­‐
Dashboard
Actor:
Producer
Description:
This
use
case
describes
how
a
Producer
would
utilize
the
dashboard
by
viewing
latest
updates
in
news
feed,
selecting
various
filters
for
charts
and
viewing/printing
the
charts.
Trigger:
Producer
wants
to
view
dashboard
data.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Producer
has
the
credentials
and
access
to
the
system.
• The
datastores
are
available
and
online.
Normal
Course: Information
for
Steps:
1. Log
in
to
system
2. The
system
updates
forecasted
and
actual
book
of
business,
retention
rates
and
new
business
3. The
system
checks
for
any
latest
additions
or
changes
to
new
and
existing
clients
and
displays
the
status
to
the
client
account
4. The
producer
selects
recently
updated
link
in
news
feed
to
view
client
details
5. The
system
will
display
client
data
6. The
Producer
selects
back
to
return
to
the
dashboard
7. The
system
will
update
and
display
cross-­‐sell
pie-­‐chart
8. The
system
will
update
and
display
niche
pie
chart
by
different
filters
8.1
Producer
selects
“Number”,
“Premium”
or
“Revenue”
to view
different
charts
8.2
Depending
on
the
selection,
“Number”,
“Premium”
or “Revenue”,
different
charts
will
be
displayed
9. The
system
will
update
and
display
new
business
chart
I:
User
info
O:
Producer
info
O:
News
feed
status
I:
Client
record
O:
Client
record
I:
Previous
dashboard
details
O:
Cross-­‐sell
info
O:
Niche
info
I:
Type
of
niche
info
O:
Niche
charts
O:
New
business
info
Postconditions:
• Actual
performance
on
goals
dashboards
are
updated.
• News
feeds
are
updated.
• Cross-­‐sell,
niche
breakdown
and
new
business
charts
are
updated.
Inputs Source Outputs Destination
User
info
Client
record
Previous
dashboard
details
Type
of
niche
info
Producer
Producer
Producer
Producer
Producer
info
News
feed
status
Client
record
Cross-­‐sell
info
Niche
info
Niche
charts
New
business
info
Producer
database
Line
of
Business
database
Client
database
Department
database
Niche
database
Niche
database
Line
of
Business
database

30. 30
Use
Case
Name:
Producer
-­‐
Reporting
Actor:
Producer
Description:
This
use
case
describes
how
a
Producer
would
run
a
report.
Trigger:
Producer
wants
to
generate
a
report.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Producer
has
the
credentials
and
access
to
the
system.
• The
datastores
are
available
and
online.
Normal
Course: Information
for
Steps:
1. Log
in
to
system
2. Go
to
Reporting
tab
3. System
displays
reporting
interface
4. Select
type
of
report
from
dropdown
menu
5. Select
start
date
6. Select
time
range
(depending
on
report
type)
7. Select
data
to
be
included
in
the
report
8. Run
report
9. Report
is
generated
I:
User
info
I:
Report
menu
O:
Report
parameters
I:
Report
type
I:
Date
info
I:
Time
interval
I:
Report
filters
I:
Report
activity
O:
Report
info
Postconditions:
• Report
will
be
generated
based
on
filters
selected.
Inputs Source Outputs Destination
User
info
Report
menu
Report
type
Date
info
Time
interval
Report
filters
Report
activity
Producer
Producer
Producer
Producer
Producer
Producer
Producer
Report
parameters
Report
info
Client,
Line
of
Business,
Niche
databases
Producer

31. 31
Management
Use
Cases
Use
Case
Name:
Management
-­‐
Dashboard
Actor:
Management
Description:
This
use
case
describes
how
Management
would
utilize
the
dashboard
by
selecting
various
filters
for
charts
for
either
a
specific
producer
or
the
agency
as
a
whole.
Trigger:
Management
wants
to
view
dashboard
data.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Manager
has
the
credentials
and
access
to
the
system.
• The
datastores
are
available
and
online.
Normal
Course: Information
for
Steps:
1. Log
in
to
system
2. Select
to
view
data
for
a
specific
producer
or
the
agency
from
dropdown
menu
3. The
system
updates
forecasted
and
actual
book
value,
retention
rates
and
new
business
for
specific
Producer
or
the
agency
4. The
system
will
update
and
display
cross-­‐sell
pie-­‐chart
for
specific
Producer
or
the
agency
5. The
system
will
update
and
display
niche
pie
chart
by
different
filters
5.1
Management
selects
“Number”,
“Premium”
or
“Revenue”
to view
different
charts
5.2
Depending
on
the
selection,
“Number”,
“Premium”
or “Revenue”,
different
charts
will
be
displayed
or
specific Producer
or
the
agency
6. The
system
will
update
and
display
new
business
chart
for
specific
Producer
or
the
agency
I:
User
info
I:
Producer
info
O:
Producer
info
O:Cross-­‐sell
info
O:
Niche
info
I:
Type
of
niche
info
O:
Niche
charts
O:
New
business
info
Postconditions:
• Actual
performance
on
goals
dashboards
are
updated
for
specific
Producer
or
the
agency.
• Cross-­‐sell,
niche
breakdown
and
new
business
charts
are
updated
for
specific
Producer
or
the
agency.
Inputs Source Outputs Destination
User
info
Producer
info
Type
of
niche
info
Management
Management
Management
Producer
info
Cross-­‐sell
info
Niche
info
Niche
charts
New
business
info
Producer
database
Department
database
Niche
database
Niche
database
Line
of
Business
database

32. 32
Use
Case
Name:
Management
-­‐
Reporting
Actor:
Management
Description:
This
use
case
describes
how
Management
would
run
a
report.
Trigger:
Management
wants
to
generate
a
report.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• The
Management
has
the
credentials
and
access
to
the
system.
Normal
Course: Information
for
Steps:
1. Log
in
to
system
2. Go
to
Reporting
tab
3. System
displays
reporting
interface
4. Select
type
of
report
from
dropdown
menu
5. Select
start
date
6. Select
time
range
(depending
on
report
type)
7. Select
data
to
be
included
in
the
report
8. Run
report
9. Report
is
generated
I:
User
info
I:
Report
menu
O:
Report
parameters
I:
Report
type
I:
Date
info
I:
Time
interval
I:
Report
filters
I:
Report
activity
O:
Report
info
Postconditions:
• Report
will
be
generated
based
on
filters
selected.
Inputs Source Outputs Destination
User
info
Report
menu
Report
type
Date
info
Time
interval
Report
filters
Report
activity
Management
Management
Management
Management
Management
Management
Management
Report
parameters
Report
info
Client,
Line
of
Business,
Niche
databases
Management

33. 33
Use
Case
Name:
Management
-­‐
Goal
Setting
Actor:
Management
Description:
This
use
case
describes
how
management
would
set
goals
for
a
producer.
Trigger:
It’s
the
beginning
of
the
year
and
management
wants
to
set
goals
for
his/her
producers.
Type:
External
Preconditions:
• The
system
is
online
and
available.
• Management
has
the
credentials
and
access
to
the
system.
• The
datastores
are
available
and
online.
Normal
Course: Information
for
Steps:
1. Log
in
to
system
2. Go
to
Goal
Setting
tab
3. Management
enters
book
of
business
and
retention
goals
for
entire
company
4. System
calculates
new
business
goal
based
on
book
of
business
and
retention
goals
entered
5. System
calculates
book
of
business,
retention
and
new
business
goals
for
each
producer
6. Management
accepts
the
goals
or
make
changes
to
them
7. Goals
set
are
saved
I:
User
info
I:
Goal
menu
I:
Goal
amount
O:
New
business
value
O:
Goal
info
I:
Goal
modification
O:
Goals
set
Postconditions:
• Dashboard
data
will
be
updated
to
reflect
goals
where
applicable.
• Goals
are
saved
in
the
producer
datastore.
Inputs Source Outputs Destination
User
info
Goal
menu
Goal
amount
Goal
modification
Management
Management
Management
Management
New
business
value
Goal
info
Goals
set
Management
Management
Producer
datastore

34. 34
Data
Flow
Diagrams

35. 35

36. 36

37. 37

38. 38

39. 39

40. 40

41. 41

42. 42

43. 43

44. 44

45. 45

46. 46

47. 47
Data
Dictionary
• Data
Structures
Client
datastore
-­‐
The
Client
datastore
will
store
information
on
each
Client
such
as
Client’s
name,
email,
zip,
SIC
Code
and
updates
to
be
displayed
on
the
newsfeed
of
a
Producer’s
dashboard.
Client
ID
Client
Name
Email
Zip
Display
Newsfeed
Niche
ID
SIC
Code
Connect
Line
of
Business
(LoB)
Client
datastore
-­‐
The
Connect
Line
of
Business
(LoB)
Client
datastore
will
contain
policy
information
on
each
Client
such
as
premium,
commission,
losses,
effective
and
expiration
dates.
Connect
ID
Client
ID
Carrier
ID
LoB
ID

48. 48
Producer
ID
Premium
Commission
Losses
As
of
Date
Effective
Date
Expiration
Date
LoB
Status
LoB
datastore
-­‐
The
LoB
datastore
will
contain
LoB
information
that
is
associated
with
each
Client
record.
LoB
ID
LoB
Name
Carrier
datastore
-­‐
The
Carrier
datastore
will
contain
Carrier
information
details
such
as
Carrier
name.
Carrier
ID
Carrier
Name

49. 49
Niche
datastore
-­‐
The
Niche
datastore
will
contain
information
on
Niche
details
such
as
the
range
of
SIC
codes
and
Niche
names.
Niche
ID
Starting
Number
Ending
Number
Niche
Name
Department
datastore
-­‐
The
Department
datastore
will
contain
Department
information
such
as
Department
name.
Department
ID
Department
Name
Producer
datastore
-­‐
The
Producer
datastore
has
information
on
the
goals
set
for
each
Producer
including
book
of
business
value
and
retention
rates.
Producer
ID
Producer
Name
Book
Value
Retention
Rate
Last
Updated

50. 50
Department
ID
Roles
datastore
-­‐
The
Roles
datastore
has
information
on
each
user’s
role
in
the
agency
to
direct
each
user
to
the
homepage.
Roles
ID
Role
Name
LoB
History
datastore
-­‐
The
LoB
History
datastore
contains
information
on
previous
Client
account
records
when
a
Client
has
been
updated
as
renewed
or
cancelled.
LoB
History
ID
Client
ID
Carrier
ID
LoB
ID
Producer
ID
Premium
Commission
Losses
As
of
Date
Effective
Date

51. 51
Expiration
Date
LoB
Status
Department
ID
Timestamp
Login
Info
datastore
-­‐
The
Login
info
datastore
stores
all
employees’
information
such
username,
current
and
old
passwords
and
sessions.
User
ID
Username
Email
Roles
ID
Current
Password
Temporary
Password
Old
Password
1
Old
Password
2
Login
Status
Session
ID
Password
Date

52. 52
• Data
Elements
# Data
Element Description Data
Type Base/Derived Data
Element
Owner
1 Client
ID Identify
client
record int(5) Base Client
datastore
2 Client
Name Name
of
client varchar(25) Base Client
datastore
3 Email Client’s
email varchar(25) Base Client
datastore
4 Zip Client’s
zip
code int(5) Base Client
datastore
5 Display
Newsfeed
Checks
for
any
updates
for
a
client
account
and
display
updates
on
news
feed
varchar(255) Base Client
datastore
6 Niche
ID Identify
niche int(5) Base Client
datastore
7 SIC
Code Classifies
industry
by
standard
codes
int(4) Base Client
datastore
8 Connect
ID Identify
policy
information
with
client
account
int(5) Base Connect
LoB
Client
datastore
9 Client
ID Identify
client
record int(11) Base Connect
LoB
Client
datastore
10 Carrier
ID Identify
carrier
information
int(5) Base Connect
LoB
Client
datastore
11 LoB
ID Identify
LoB
information int(10) Base Connect
LoB
Client
datastore
12 Producer
ID Identify
producer
information
int(5) Base Connect
LoB
Client
datastore
13 Premium Premium
information
for
client’s
LoB
float(5) Base Connect
LoB
Client
datastore
14 Commission Commission
information
for
each
policy
sold
float(255) Base Connect
LoB
Client
datastore
15 Losses Losses
written
for
each
policy
issued
by
a
carrier
float(5) Base Connect
LoB
Client
datastore

53. 53
16 As
of
Date Losses
written
at
that
particular
time
date Base Connect
LoB
Client
datastore
17 Effective
Date Inception
date
of
the
policy
date Base Connect
LoB
Client
datastore
18 Expiration
Date
Expiration
date
of
the
policy
date Base Connect
LoB
Client
datastore
19 LoB
Status Identify
if
LoB
is
new,
renewed
or
canceled
varchar(255) Base Connect
LoB
Client
datastore
20 Last
Edited Identify
when
the
client
information
was
edited
date Base Connect
LoB
Client
datastore
21 LoB
ID Identify
LoB int(5) Base LoB
datastore
22 LoB
Name Information
on
type
of
LoB
varchar(255) Base LoB
datastore
23 Carrier
ID Identify
carrier int(11) Base Carrier
datastore
24 Carrier
Name Information
on
type
of
carrier
varchar(255) Base Carrier
datastore
25 Niche
ID Identify
niche int(10) Base Niche
datastore
26 Starting
Number
Classify
SIC
Code
according
to
standard
industry
practice
int(5) Base Niche
datastore
27 Ending
Number
Classify
SIC
Code
according
to
standard
industry
practice
int(5) Base Niche
datastore
28 Niche
Name Information
on
type
of
niche
varchar(50) Base Niche
datastore
29 Department
ID
Identify
department int(11) Base Department
datastore
30 Department
Name
Information
on
type
of
department
varchar(255) Base Department
datastore
31 Producer
ID Identify
producer int(5) Base Producer
datastore
32 Producer
Name
Producer
name varchar(25) Base Producer
datastore

54. 54
33 Book
Value Book
value
goal
set
for
producer
int(15) Base Producer
datastore
34 Retention
Rate
Retention
rate
goal
set
for
producer
int(5) Base Producer
datastore
35 Last
Updated Displays
when
goals
was
last
updated
date Base Producer
datastore
36 Department
ID
Identify
department int(5) Base Producer
datastore
37 Roles
ID Identify
role int(4) Base Roles
datastore
38 Role
Name Information
on
type
of
role
for
each
employee
varchar(255) Base Roles
datastore
39 LoB
History
ID
Identify
past
LoB
records int(11) Base LOB
History
datastore
40 Client
ID Identify
client int(5) Base LOB
History
datastore
41 Carrier
ID Identify
carrier int(5) Base LOB
History
datastore
42 LoB
ID Identify
LoB int(5) Base LOB
History
datastore
43 Producer
ID Identify
producer int(5) Base LOB
History
datastore
44 Premium Premium
information
for
client’s
LoB
int(25) Base LOB
History
datastore
45 Commission Commission
information
for
each
policy
sold
int(25) Base LOB
History
datastore
46 Losses Losses
written
for
each
policy
issued
by
a
carrier
int(25) Base LOB
History
datastore
47 As
of
Date Losses
written
at
that
particular
time
date Base LOB
History
datastore
48 Effective
Date Inception
date
of
the
policy
date Base LOB
History
datastore
49 Expiration
Date
Expiration
date
of
the
policy
date Base LOB
History
datastore
50 LoB
Status Identify
if
LoB
is
new,
renewed
or
canceled
varchar(255) Base LOB
History
datastore

55. 55
51 Department
ID
Identify
department int(5) Base LOB
History
datastore
52 Timestamp Identify
timestamp
of
record
timestamp Base LOB
History
datastore
53 User
ID Identify
user int(11) Base Login
Info
datastore
54 Username Name
of
user varchar(255) Base Login
Info
datastore
55 Email Email
address
of
user varchar(255) Base Login
Info
datastore
56 Roles
ID Identify
role int(4) Base Login
Info
datastore
57 Current
Password
Stores
current
password
of
user
varchar(255) Base Login
Info
datastore
58 Temporary
Password
Stores
temporary
password
of
user
varchar(255) Base Login
Info
datastore
59 Old
Password
1
Stores
old
password
1 varchar(255) Base Login
Info
datastore
60 Old
Password
2
Stores
old
password
2 varchar(255) Base Login
Info
datastore
61 Login
Status Identify
if
session
is
active int(1) Base Login
Info
datastore
62 Session
ID Identify
session varchar(255) Base Login
Info
datastore
63 Password
Date
Date
password
is
created date Base Login
Info
datastore

56. 56
IV.
Design
Phase
Architecture
Design
• Multi-­‐Tenant
Architecture
The
system
supports
a
multi-­‐tenant
architecture.
We
evaluated
numerous
options
such
as:
o Using
a
domain
website
hosting
service
o Setting
up
the
system
in
the
cloud
o Using
a
laptop
as
a
local
host
server
and
distributing
the
laptop’s
IP
In
our
analysis,
we
decided
to
configure
a
cloud-­‐based
system
because
of
the
numerous
advantages
it
offers.
The
advantages
of
using
a
cloud-­‐based
environment
are
that
it
provides
high
computing
performance,
scalability
to
our
system
fairly
quickly
and
provides
added
security
features
such
as
backup
and
recovery
of
data,
archiving
of
data
and
disaster
recovery.
In
addition,
the
cloud-­‐
based
environment
has
a
transaction
management
capability
built
in
that
ensures
a
transaction
is
successful
when
a
block
of
MySQL
statements
is
executed
successfully.
With
this
automated
transaction
management
functionality,
any
failure
in
a
statement
should
cause
the
system
to
be
‘rolled
back’
to
its
pre-­‐existing
state.
This
prevents
any
data
linkage
or
corruption
problems.
The
system
is
hosted
using
the
Amazon
Elastic
Compute
Cloud
[EC2],
which
is
a
web
service
that
provides
Elastic
computing
capacity.
The
system
is
implemented
using
a
three-­‐tier
architecture
with
web
server,
app
server
and
a
database
server.
The
application
server
is
configured
of
Amazon
Linux
AMI.
The
database
server
is
implemented
using
Amazon
Relational
Data
Store,
which
are
instances
of
MySQL
running
on
EC2
platform.
The
database
can
be
accessed
and
managed
through
by
both
SSHing
through
the
terminal
and
through
MS
Workbench.
We
use
the
On-­‐Demand
DB
Instances
let
the
organization
pay
for
compute
capacity
by
the
hour
with
no
long-­‐term
commitments.
This
frees
the
organization
from
the
costs
and
complexities
of
planning,
purchasing,
and
maintaining
hardware
and
transforms
what
are
commonly
large
fixed
costs
into
much
smaller
variable
costs.
Currently
the
system
uses
the
AWS
Free
Tier
for
Amazon
RDS
offer
provides
free
use
of
Single-­‐AZ
Micro
DB
instances
running
MySQL,
PostgreSQL,
Oracle
("Bring-­‐Your-­‐Own-­‐License
(BYOL)"
licensing
model)

57. 57
and
SQL
Server
Express
Edition.
The
free
usage
tier
is
capped
at
750
instance
hours
per
month.
Customers
also
receive
20
GB
of
database
storage,
10
million
I/Os
and
20
GB
of
backup
storage
for
free
per
month.
• Why
EC2?
o Elastic
capacity
-­‐
The
capacity
of
the
servers
can
be
increased
or
decreased
as
per
need
and
the
payment
can
be
made
according
to
the
usage.
This
eliminates
the
purchase
of
large
and
expensive
hardware
devices.
o Regions
and
availability
zones
-­‐
The
instances
can
be
launched
in
separate
regions
according
to
the
location
of
the
organization.
Each
Region
has
multiple
availability
zones
and
by
launching
the
application
in
multiple
availability
zones,
the
application
is
protected
from
failure
from
a
single
location.
o Storage
-­‐
The
Amazon
Elastic
Block
Storage
provides
instances
with
persistent,
block
level
storage.
They
are
essentially
hard
disks
that
can
be
attached
to
a
running
instance.
Amazon
Simple
Storage
Service
stores
the
backed
up
data.
The
system
backs
up
the
data
once
per
day.
o Security:
§ Security
Groups
-­‐
The
security
groups
provided
by
Amazon
controls
the
access
to
instances.
The
security
group
for
web
servers
only
allows
access
from
hosts
over
TCP
on
ports
80
and
443
and
from
instances
in
the
App
Servers
security
group
on
Port
22(SSH)
for
direct
host
management.
The
security
group
for
the
app
servers
allows
access
from
the
Web
Servers
security
group
for
web
requests,
and
from
the
corporate
subnet
over
TCP
on
port
22
(SSH)
for
direct
host
management.
The
user’s
support
engineers
could
log
directly
into
the
application
servers
from
the
corporate
network,
and
then
access
the
other
instances
from
the
application
server
boxes.
The
DB
Servers
security
group
permits
only
the
App
Servers
security
group
to
access
the
database
servers.
§ Encrypted
data
storage
-­‐
Customers
can
have
the
data
and
objects
they
store
in
Amazon
EBS,
Amazon
S3,
Glacier,
Redshift,
and
Oracle
and
SQL
Server
RDS
encrypted

58. 58
automatically
using
Advanced
Encryption
Standard
(AES)
256,
a
secure
symmetric-­‐key
encryption
standard
using
256-­‐bit
encryption
keys.
• Why
RDS?
o Scalable
storage
-­‐
You
can
scale
the
computer’s
and
storage
resources
available
to
the
organization’s
database
to
meet
your
application’s
needs
using
the
Amazon
RDS
API
or
the
AWS
Management
Console.
With
Amazon
RDS
Provisioned
IOPS
storage
with
Amazon
RDS
for
MySQL,
Oracle,
or
PostgreSQL,
the
organization
can
provision
and
scale
the
storage
up
to
3TB
and
IOPS
to
up
to
30,000.
Note
that
maximum
realized
IOPS
will
vary
by
engine
type.
In
addition,
for
the
MySQL,
PostgreSQL,
and
Amazon
Aurora
database
engines,
one
can
also
associate
one
or
more
read
replicas
with
your
database
instance
deployment,
enabling
you
to
scale
beyond
the
capacity
of
a
single
database
instance
for
read-­‐heavy
workloads.
o Rapid
Provisioning
and
High
Availability
-­‐
Amazon
RDS
has
multiple
features
that
enhance
reliability
for
critical
production
databases,
including
automated
backups,
DB
snapshots,
automatic
host
replacement,
and
Multi-­‐AZ
deployments.
Amazon
RDS
runs
on
the
same
highly
reliable
infrastructure
used
by
other
Amazon
Web
Services.
o Security
-­‐
The
data
at
rest
is
encrypted
by
default.
Providing
customized
encryption
by
using
Amazon
Key
Management
System
can
further
extend
it.
Automatic
backups
can
be
created
using
snapshots
of
the
database
within
any
desired
time
interval.
• Encryption
In
designing
the
security
of
our
system,
we
made
sure
that
the
username
and
password
of
each
user
is
encrypted
to
protect
against
any
malicious
attacks.
We
evaluated
multiple
encryption
algorithm
techniques
and
narrowed
it
down
to
MD5,
SHA1
and
CRYPT.
MD5
to
provide
the
first
layer
of
password
protection.
MD5
is
vulnerable
to
collision
attacks
because
decryption
applications
are
now
available
online
to
crack
passwords.
Therefore,
we
added
SHA1
as
an
extra
encryption
security
layer
to
ensure
that
the
passwords
are
not
easily
decrypted
by
undesired
users.
In
recent
times,
new
hacking
technology
has
popped
up
to
decrypt
SHA1.
MD5
and
SHA1
were
used
because
they
are

59. 59
industry
standards
and
provide
some
level
of
password
security.
In
order
to
strengthen
the
password
security,
CRYPT
was
added
as
the
third
and
final
layer
to
prevent
any
possible
threat
of
password
decryption.
The
reason
we
decided
to
use
three
different
encryption
techniques
is
because
used
together,
they
provide
a
stronger
mechanism
to
thwart
off
any
hackers
from
breaking
the
system.
For
the
attackers,
it
would
require
a
large
amount
of
resources
such
as
time
and
computing
resources
for
brute
force
cracking.
• Session
Management
Since
HTTP
is
a
stateless
protocol,
we
implemented
session
management
capabilities
to
link
the
authentication
and
access
control
of
the
system
available
to
users.
We
assigned
a
unique
session
ID
every
time
a
user
logs
into
the
system
and
this
sets
up
the
authenticated
session
for
every
data
request
to
the
web
server.
The
session
ID
binds
the
user
authentication
credentials
to
the
web
server
and
appropriate
access
controls
set
by
the
system.
The
system
allows
only
one
user
to
be
logged
in
on
one
browser
at
a
time.
The
system
invalidates
the
previous
machine
session
when
same
user
tries
to
log
in
to
new
machine.
This
implementation
makes
sure
that
the
already
running
session
on
the
previous
machine
is
destroyed
and
new
session
is
established
on
the
other
so
that
his
account’s
dashboard
is
visible
only
to
him
or
her.
In
order
to
secure
the
application,
we
also
implemented
a
time
limit
with
the
session.
When
the
user
has
been
idle
for
20
minutes,
the
user
will
automatically
be
logged
out
and
will
need
to
re-­‐enter
login
credentials
to
sign
into
the
system. As
an
extra
security
layer,
we
ensured
that
the
session
ID
is
not
predictable
by
using
a
method
of
generating
random
IDs.
The
session
ID
cannot
be
easily
reproduced
and
is
of
a
sufficient
length
so
that
a
brute
force
method
cannot
be
used
to
hack
into
the
system
within
the
timeframe.
To
implement
“remember
me”
functionality
on
the
web
browser,
we
utilized
HTML5
Local
Storage
capabilities
to
store
named
key/value
pairs
locally,
on
the
client-­‐side.
Similar
to
cookies,
the
data
persists
after
a
user
navigates
from
the
application,
closes
or
exits
from
his
or
her
browser
tab.
It
allows
a
user
to
store
data
as
big
as
5MB
unlike
cookies
that
provide
4096
bytes
of
storing

60. 60
allowance.
Cookies
are
usually
used
with
Javascript
on
server-­‐side,
and
if
anyone
manages
to
hack
the
cookie
file
and
change
its
content,
the
security
is
compromised.
But
in
our
system,
the
data
is
never
transferred
to
a
remote
web
server
and
stays
on
user’s
machine
so
there
is
a
less
possibility
of
unwanted
people
getting
access
to
the
system.
o The
system
avoids
data
exchange
between
two
different
users
by
not
allowing
them
to
login
on
the
same
machine
simultaneously.
o The
system
allows
one
user
to
be
logged
in
from
number
of
machines.
As
a
security
measurement,
the
system
logs
out
the
user
from
the
previous
machine
if
they
try
to
access
the
last
viewed
page
on
the
previous
machine.
• Model
View
Controller
(MVC)
Architecture
In
line
with
industry
standards,
we
adopted
the
MVC
architecture
to
split
the
code
in
three
modules
-­‐
model,
view
and
controller.
In
our
model
component,
we
managed
the
data,
rules
and
logic
of
the
system.
The
model
component
includes
logic
for
updating
the
database
by
the
Account
Manager,
updating
the
dashboards
for
Producer
and
Management
with
relevant
information
and
the
rules
for
password
setting
and
management.
The
controller
module
contains
the
commands
that
are
sent
to
add,
edit
and
delete
Client
information,
set
goals,
run
reports,
display
Client
updates
on
the
news
feed
and
update
passwords.
Finally,
the
view
component
provides
the
interface
pages
to
Account
Managers,
Producers
and
Management
after
retrieving
information
from
the
model.
The
MVC
architecture
provides
a
huge
advantage
to
be
ease
of
code
reuse.
In
addition,
the
MVC
approach
uses
the
principle
of
view/decoupling
techniques,
which
is
useful
in
creating
multiple
views
to
a
model
to
provide
different
representations.
This
is
especially
useful
as
the
system
evolves
down
the
road
to
include
different
end
user
perspectives.

61. 61
• Data
Integrity
Data
integrity
is
an
integral
aspect
in
ensuring
that
our
system
provides
the
most
accurate
and
error-­‐free
information
to
users
consistently
throughout
the
entire
life
cycle
of
the
data.
Therefore,
we
have
implemented
data
integrity
rules
in
the
following
form:
o At
data
entry
level
such
as
selecting
Carrier,
LoB,
we
have
implemented
drop
down
menus
with
pre-­‐populated
options
to
prevent
any
data
entry
mistakes.
o In
addition,
when
entering
data
such
as
date
for
effective,
expiration
dates
and
as
of
date,
we
have
implemented
a
date
picker
and
ensured
that
the
expiration
date
is
always
larger
than
the
effective
date
picked.
Again,
this
helps
reduce
any
human
error
that
can
occur
when
entering
data.
o We
have
also
implemented
data
validation
rules
such
as
ensuring
only
10
digits
are
entered
for
telephone
numbers,
5
digits
are
entered
for
zip
codes.
o For
the
Producer
and
Management
dashboards,
we
provided
drop
down
menus
for
charts,
report
filters
to
address
any
human
errors.
o In
the
goal
setting
view
on
the
management
dashboard,
we
have
implemented
some
data
validation
checks
such
as
making
sure
the
retention
rates
entered
is
between
1-­‐100.
In
addition,
the
system
throws
an
error
if
either
the
retention
rate
or
book
of
business
value
is
not
entered.
• Role-­‐Based
Security
Management
As
the
data
available
in
the
system
is
sensitive
and
is
not
available
for
viewing
by
every
single
employee,
we
implemented
role-­‐based
access
control
to
restrict
the
system
access
only
to
authorized
users.
By
assigning
individual
roles
(role_ID),
we
assigned
special
privilege
and
permission
rights
to
the
users
performing
those
operations.
Account
Managers
are
assigned
role_ID
1
which
allows
them
to
create,
read,
edit,
delete
and
renew
clients.
In
addition,
account
managers
have
the
permission
to
sign
up
new
employees
and
create
their
credentials
to
access
the
system.
However,
the
database
administrator
instead
of
the
Account
Managers
will
assign
the
roles
of
new
users
from
the
back-­‐end.

62. 62
Managers
are
assigned
role_ID
2
which
gives
them
access
to
the
company’s
and
each
Producer’s
goals,
actual
performance,
charts
and
reports.
Management
also
has
special
rights
to
set
goals
for
the
company
and
each
Producer.
Producers
are
assigned
role
ID_3.
They
only
have
access
to
their
own
dashboard
where
they
can
view
their
own
goals,
actual
performance,
charts
and
reports.
They
are
not
able
to
view
other
Producers’
dashboards.
• Password
Security
Management
In
order
to
thwart
off
any
malicious
attacks
from
undesirable
sources,
we
have
implemented
several
password
management
rules
that
are
in
line
with
standard
practices:
o The
system
does
not
allow
the
user
to
use
last
3
passwords
used.
o The
system
warns
the
user
to
change
the
password
if
it
is
about
to
expire
in
a
week’s
time.
o The
system
does
not
allow
the
user
to
login
if
the
password
is
more
than
6
months
old.
o Every
password
is
encrypted.
o Passwords
must
contain
one
special
character,
upper
case
letter,
digit
and
must
be
at
least
8
characters
long.

63. 63
Program
Design
• Structure
Chart

64. 64

65. 65

66. 66

67. 67

68. 68

69. 69
Database
Design
• Entity
Relationship
Diagram

70. 70
V.
Implementation
Phase
Testing
The
system
was
tested
at
several
stages
during
the
implementation
phase.
We
began
with
exhaustive
unit
testing
on
individual
modules.
We
then
integrated
the
code
on
a
local
host
and
continued
testing
on
different
machines.
When
everything
was
working
as
expected,
we
deployed
onto
the
cloud
and
re-­‐tested
with
simultaneous
users.
Each
level
of
testing
was
documented
in
test
cases.
• Test
Cases
-­‐
Producer
Test
Case
ID: P01 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Goal
display Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
goals
set
for
each
producer
is
reflected
on
producer
dashboard
when
he
or
she
logs
in
Dependencies Goals
will
only
be
reflected
if
management
sets
the
goals
Step Test
Steps Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
Notes
1 Management
logs
in
to
his
or
her
dashboard
to
enter
book
of
business
goals
for
entire
Numerical
data
from
0
onwards
Management
should
be
able
to
enter
numerical
data

71. 71
company
2 Management
logs
in
to
his
or
her
dashboard
to
enter
retention
rate
goals
for
entire
company
Numerical
data
from
0
to
100
Management
should
be
able
to
enter
retention
rate
data
3 Management
accepts
and
saves
goals
recommended
per
producer
Click
save Goals
are
saved
4 Producer
logs
in
to
his
or
her
dashboard
and
goals
that
were
set
by
management
are
displayed
Book
of
business,
retention
rate
and
new
business
goals
Goals
specific
to
producer
are
displayed
5 Repeat
steps
for
each
producer
Test
Case
ID: P02 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Sales
performance
tracked
Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
sales
performance
for
each
producer
is
reflected
on
producer
dashboard
when
he
or
she
logs
in

72. 72
Dependencies Sales
performance
will
only
be
reflected
if
account
manager
enters
or
updates
client
accounts
Step Test
Steps Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
Notes
1 Enter
a
new
client
entry
Client
data
New
entry
added
to
the
databased
2 Modify
client
entry
to
renew
or
cancel
Client
status
data
Client
status
to
reflect
new
status
3 Producer
logs
in
to
his
or
her
dashboard
and
performance
for
book
of
business
to
be
updated
with
new
entries
or
modifications
Book
of
business,
retention
rate
and
new
business
should
be
updated
to
the
progress
chart
in
the
form
of
a
percentage
change
5 Repeat
steps
for
each
producer
Test
Case
ID: P03 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Display
newsfeed
Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
whenever
a
client
account
is
added
or
its
status
is
modified
to

73. 73
reflect
if
it
is
renewed
or
canceled,
the
new
status
displays
on
the
producer’s
news
feed
Dependencies Client
status
updates
will
only
be
reflected
if
account
manager
enters
or
updates
client
accounts
Step Test
Steps Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
Notes
1 Enter
a
new
client
entry
Client
data New
entry
added
to
the
database
2 Modify
client
entry
to
renew
or
cancel
Client
status
data
Client
status
to
reflect
new
status
3 Producer
logs
in
to
his
or
her
dashboard
and
client
status
is
displayed
on
news
feed
Client
status
data
New,
canceled
or
renewed
client
accounts
are
displayed
after
10
seconds
of
logging
in
5 Producer
clicks
on
client
name
to
view
record
Click
client
name
Client
record
to
be
displayed
6 Producer
clicks
on
back
to
return
to
the
dashboard
Click
on
back
button
Producer’s
dashboard
to
be
displayed
Test
Case
ID: P04 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
06/10/2015

74. 74
Date:
Module
Name Display
charts
Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
the
different
charts
-­‐
cross
sell,
niche
breakdown
and
new
business
for
each
producer
is
updated
and
reflected
on
producer
dashboard
when
he
or
she
logs
in
Dependencies Charts
will
be
updated
and
displayed
if
account
manager
enters
new
client
accounts
or
updates
existing
client
accounts
with
renewal
or
cancellation
info
Step Test
Steps Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
Notes
1 Enter
a
new
client
entry
Client
data New
entry
added
to
the
database
2 Existing
client
account
modified
Client
data Database
modified
3 Producer
logs
in
to
his
or
her
dashboard
and
cross-­‐
sell
chart
updated
with
latest
client
updates
Client
data Display
cross-­‐sell
charts
breakdown
computation
5 Niche
chart
by
premium
updated
with
latest
client
updates
Client
data Display
niche
chart
by
premium
breakdown
computation
6 Producer
selects
niche
chart
Revenue
dropdown
selection
Display
niche
chart
by
premium

75. 75
by
revenue breakdown
computation
7 Producer
selects
niche
chart
by
revenue
Number
of
accounts
dropdown
selection
Display
niche
chart
by
number
of
account
breakdown
computation
8 New
business
chart
updated
with
latest
client
updates
Client
data Display
new
business
chart
per
month
breakdown
computation
Test
Case
ID: P05 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Generate
reports
Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
the
reports
are
generated
specific
to
the
producer
when
he
or
she
selects
different
report
parameters
Dependencies
Step Test
Steps
Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
Notes
1 Enter
report
parameter
Start
date Date
is
reflected
2 Enter
report
parameter
Type
of
report
-­‐
new
Report
filters
-­‐
Client,
Niche,
Effective
Date,

76. 76
business
report
Premium,
Commission,
Carrier,
Revenue
to
be
checked
3 Enter
report
parameter
and
run
report
query
Period
-­‐
Annually
Report
data
for
a
year
from
start
date
to
be
displayed
specific
to
the
producer
only
5 Enter
report
parameter
and
run
report
query
Period
-­‐
Quarterly
Report
data
for
3
months
from
start
date
to
be
displayed
specific
to
the
producer
only
6 Enter
report
parameter
and
run
report
query
Period
-­‐
Monthly
Report
data
for
1
month
from
start
date
to
be
displayed
specific
to
the
producer
only
7 Enter
report
parameter
Start
date Date
is
reflected
8 Enter
report
parameter
Type
of
report
-­‐
retention
report
Report
filters
-­‐
Client,
Niche,
Effective
Date,
Premium,
Commission,
Carrier,
Revenue
to
be
checked
9 Enter
report
parameter
and
run
report
query
Period
-­‐
Annually
Report
data
for
a
year
from
start
date
to
be
displayed
specific
to
the
producer
only
10 Enter
report
parameter
Start
date Date
is
reflected
11 Enter
report
parameter
Type
of
report
-­‐
combined
Report
filters
-­‐
Client,
Niche,
Effective
Date,

77. 77
report Premium,
Commission,
Carrier,
New/Renewal,
Revenue
to
be
checked
12 Enter
report
parameter
and
run
report
query
Period
-­‐
Annually
Report
data
for
a
year
from
start
date
to
be
displayed
specific
to
the
producer
only
13 Enter
report
parameter
Start
date Date
is
reflected
14 Enter
report
parameter
Select
any
report
Report
filters
-­‐
Client,
Niche,
Effective
Date,
Premium,
Commission,
Carrier,
New/Renewal,
Revenue
to
be
checked
15 Select
other
report
filters
Check
other
report
filters
Report
filters
to
be
updated
with
selected
report
filters
16 Enter
report
parameter
and
run
report
query
Select
any
time
period
Report
data
for
a
year
/
a
quarter
/
a
month
from
start
date
including
report
filters
selected
to
be
displayed
specific
to
the
producer
only

78. 78
• Test
Cases
-­‐
Management
Test
Case
ID: P01 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Goal
setting
and
display
Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
goals
set
for
entire
company
and
each
producer
is
reflected
on
management
dashboard
when
he
or
she
logs
in
Dependencies Goals
will
only
be
reflected
if
management
sets
the
goals
Step Test
Steps Test
Data Expected
Result Actual
Result
Status
(Pass/Fail)
Notes
1 Management
logs
in
to
his
or
her
dashboard
to
enter
book
of
business
goals
for
entire
company
Numerical
data
from
0
onwards
Management
should
be
able
to
enter
numerical
data
2 Management
logs
in
to
his
or
her
dashboard
to
enter
book
of
business
goals
for
entire
company
Alphabets Management
should
not
be
able
to
enter
numerical
data
3 Management
Numerical
Management

79. 79
logs
in
to
his
or
her
dashboard
to
enter
retention
rate
goals
for
entire
company
data
from
0
to
100
should
be
able
to
enter
retention
rate
data
4 Management
logs
in
to
his
or
her
dashboard
to
enter
retention
rate
goals
for
entire
company
Numerical
data
over
100
A
window
pops
up
prompting
management
to
enter
values
from
0
to
100
5 Management
selects
calculate
Calculate
button
New
business
value
and
goal
recommendations
for
each
producer
is
displayed
6 Management
accepts
and
saves
goals
recommended
per
producer
Click
save Goals
are
saved
7 Management
edits
goals
and
saves
goals
Click
save Goals
are
updated
for
each
producer
and
saved
to
the
database
8 Management
logs
in
to
his
or
her
dashboard
and
goals
that
were
set
by
are
displayed
Book
of
business,
retention
rate
and
new
business
goals
Goals
for
entire
company
producer
are
displayed
9 Management
selects
producer’s
name
Book
of
business,
retention
rate
and
new
business
goals
Goals
specific
to
the
producer
are
displayed

80. 80
Test
Case
ID: P02 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Sales
performance
tracked
Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
sales
performance
for
each
producer
is
reflected
on
management
dashboard
when
he
or
she
logs
in
Dependencies Sales
performance
will
only
be
reflected
if
account
manager
enters
or
updates
client
accounts
for
each
producer
Step Test
Steps Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
Notes
1 Enter
a
new
client
entry
Client
data
New
entry
added
to
the
databased
2 Modify
client
entry
to
renew
or
cancel
Client
status
data
Client
status
to
reflect
new
status
3 Management
logs
in
to
his
or
her
dashboard
and
performance
for
book
of
business
to
be
updated
with
new
entries
or
modifications
Book
of
business,
retention
rate
and
new
business
should
be
updated
to
the
progress
chart
in
the
form
of
a
percentage
change
5 Management
selects
producer
name
to
view
Book
of
business,
retention
rate
and
new

81. 81
performance
for
that
producer
business
should
be
updated
to
the
progress
chart
in
the
form
of
a
percentage
change
for
that
specific
producer
Test
Case
ID: P03 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Display
charts
Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
the
different
charts
-­‐
cross
sell,
niche
breakdown
and
new
business
for
each
producer
is
updated
and
reflected
on
management
dashboard
when
he
or
she
logs
in
Dependencies Charts
will
be
updated
and
displayed
if
account
manager
enters
new
client
accounts
or
updates
existing
client
accounts
with
renewal
or
cancellation
info
Step Test
Steps Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
Notes
1 Enter
a
new
client
entry
Client
data New
entry
added
to
the
database
2 Existing
client
account
modified
Client
data Database
modified

82. 82
3 Management
selects
‘all’
or
specific
producer
name
Charts
are
updated
with
data
for
entire
company
or
specific
producer
4 Management
logs
in
to
his
or
her
dashboard
and
cross-­‐sell
chart
updated
with
latest
client
updates
Client
data Display
cross-­‐sell
charts
breakdown
computation
5 Niche
chart
by
premium
updated
with
latest
client
updates
Client
data Display
niche
chart
by
premium
breakdown
computation
6 Management
selects
niche
chart
by
revenue
Revenue
dropdown
selection
Display
niche
chart
by
premium
breakdown
computation
7 Management
selects
niche
chart
by
revenue
Number
of
accounts
dropdown
selection
Display
niche
chart
by
number
of
account
breakdown
computation
8 New
business
chart
updated
with
latest
client
updates
Client
data Display
new
business
chart
per
month
breakdown
computation
Test
Case
ID: P04 Test
Designed
By:
Amra
Iskander
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015

83. 83
Module
Name Generate
reports
Test
Executed
By:
Test
Title Test
Execution
Date:
Description Verify
that
the
reports
are
generated
when
management
selects
different
report
parameters
Dependencies
Step Test
Steps
Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
Notes
1 Enter
report
parameter
Start
date Date
is
reflected
2 Enter
report
parameter
Type
of
report
-­‐
new
business
report
Report
filters
-­‐
Client,
Niche,
Effective
Date,
Premium,
Commission,
Carrier,
Revenue
to
be
checked
3 Enter
report
parameter
and
run
report
query
Period
-­‐
Annually
Report
data
for
a
year
from
start
date
to
be
displayed
specific
to
the
producer
only
5 Enter
report
parameter
and
run
report
query
Period
-­‐
Quarterly
Report
data
for
3
months
from
start
date
to
be
displayed
specific
to
the
producer
only
6 Enter
report
parameter
and
run
report
query
Period
-­‐
Monthly
Report
data
for
1
month
from
start
date
to
be
displayed
specific
to
the
producer
only
7 Enter
Start
date Date
is

84. 84
report
parameter
reflected
8 Enter
report
parameter
Type
of
report
-­‐
retention
report
Report
filters
-­‐
Client,
Niche,
Effective
Date,
Premium,
Commission,
Carrier,
Revenue
to
be
checked
9 Enter
report
parameter
and
run
report
query
Period
-­‐
Annually
Report
data
for
a
year
from
start
date
to
be
displayed
specific
to
the
producer
only
10 Enter
report
parameter
Start
date Date
is
reflected
11 Enter
report
parameter
Type
of
report
-­‐
combined
report
Report
filters
-­‐
Client,
Niche,
Effective
Date,
Premium,
Commission,
Carrier,
New/Renewal,
Revenue
to
be
checked
12 Enter
report
parameter
and
run
report
query
Period
-­‐
Annually
Report
data
for
a
year
from
start
date
to
be
displayed
specific
to
the
producer
only
13 Enter
report
parameter
Start
date Date
is
reflected
14 Enter
report
parameter
Select
any
report
Report
filters
-­‐
Client,
Niche,
Effective
Date,
Premium,
Commission,
Carrier,
New/Renewal,
Revenue
to
be
checked

85. 85
15 Select
other
report
filters
Check
other
report
filters
Report
filters
to
be
updated
with
selected
report
filters
16 Enter
report
parameter
and
run
report
query
Select
any
time
period
Report
data
for
a
year
/
a
quarter
/
a
month
from
start
date
including
report
filters
selected
to
be
displayed
specific
to
the
producer
only
• Test
Cases
-­‐
Account
Manager
Test
Case
ID: P01 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High)
:
High Tes
t
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Compan
y
Name
Input
Test
Executio
n
Date:
06/11/2015
Description Verify
the
company
name
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
Step Test
Steps
Test
Data Expected
Result Actual
Result
Status
(Pass/Fail)
1 Click
on
Click
on
Add
New
Record
Add
Pass

86. 86
Add
New
Record
button
button Page
is
displayed New
Recor
d
Page
is
displa
yed
2 Do
not
enter
any
value
in
the
field
Empty
value
Invalid
company
name.
Invalid
compan
y
name. Pass
3 Enter
only
special
characters
for
company
name !@#$!
Invalid
company
name.
Invalid
compan
y
name. Pass
5
Enter
only
spaces
Invalid
company
name.
Invalid
compan
y
name. Pass
Test
Case
ID: P02 Test
Designed
By: Namita
Nair
Test
Priority
(Low/Medium/High):
Medium Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By: Namita
Nair
Test
Title Email
Input Test
Execution
Date:
06/11/2015
Description Verify
the
email
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name.
Step Test
Data Expected
Result Actual
Result
Status
(Pass/Fail)
1 Do
not
enter
any
value
in
Empty
value
Email
name
cannot
be
Email
name
cannot
be
Pass

87. 87
the
field empty. empty.
2 Enter
only
special
characters
for
email !@#$!
Invalid
email
address.
Invalid
email
address. Pass
3 Enter
only
spaces
in
the
field
Invalid
email
address.
Invalid
email
address. Pass
5 Enter
email
with
trailing
spaces namu.nair@gmail.com
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
Enter
only
numbers 12344
Invalid
email
address.
Invalid
email
address. Pass
Enter
a
combination
of
numbers
and
symbols 123@@#
Invalid
email
address.
Invalid
email
address. Pass
Enter
a
combination
of
characters,
special
characters
without
‘.com’ namu.nair123_@
Invalid
email
address.
Invalid
email
address. Pass
Test
Case
ID: P03 Test
Designed
By: Namita
Nair
Test
Priority
(Low/Medium/High):
Medium Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By: Namita
Nair
Test
Title Zip
Code
Input
Test
Execution
Date:
06/11/2015
Description Verify
the
Zip
Code
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name
and
email..

88. 88
Step Test
Data Expected
Result Actual
Result
Status
(Pass/Fail)
1 Do
not
enter
any
value
in
the
field Empty
value
Zip
Code
cannot
be
empty.
Zip
Code
cannot
be
empty. Pass
2 Enter
only
special
characters !@#$!
Invalid
Zip
Code.
Invalid
Zip
Code. Pass
3 Enter
zip
code
with
trailing
spaces 95053
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
Zip
Code.
Invalid
Zip
Code. Pass
6 Enter
characters abscd
Invalid
Zip
Code.
Invalid
Zip
Code. Pass
7 Enter
combination
of
characters
and
numbers abcd@
Invalid
Zip
Code.
Invalid
Zip
Code. Pass
8 Enter
combination
of
special
characters
and
numbers @2234
Invalid
Zip
Code.
Invalid
Zip
Code. Pass
9 Enter
combination
of
special
characters
and
characters 12@ww
Invalid
Zip
Code.
Invalid
Zip
Code. Pass
10 Enter
zip
code
with
greater
than
5
numbers 123456
Invalid
Zip
Code.
Invalid
Zip
Code. Pass
11 Enter
zip
code
with
less
than
5
numbers 1234
Invalid
Zip
Code.
Invalid
Zip
Code. Pass

89. 89
Test
Case
ID: P04 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title SIC
Code
Input Test
Execution
Date:
06/11/2015
Description Verify
the
SIC
Code
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email
and
zip
code.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1 Do
not
enter
any
value
in
the
field Empty
value
SIC
Code
cannot
be
empty.
SIC
Code
cannot
be
empty. Pass
2 Enter
only
special
characters !@#$! Invalid
SIC
Code. Invalid
SIC
Code. Pass
3 Enter
zip
code
with
trailing
spaces 0001
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces Invalid
SIC
Code. Invalid
SIC
Code. Pass
6 Enter
characters abscd Invalid
SIC
Code. Invalid
SIC
Code. Pass
7 Enter
combination
of
characters
and
numbers abcd@ Invalid
SIC
Code. Invalid
SIC
Code. Pass
8 Enter
combination
of
special
characters
and
numbers @2234 Invalid
SIC
Code. Invalid
SIC
Code. Pass
9 Enter
combination
of
special
characters
and
characters 12@ww Invalid
SIC
Code. Invalid
SIC
Code. Pass
10 Enter
SIC
code
with
123 Invalid
SIC
Code. Invalid
SIC
Code. Pass

90. 90
greater
than
4
numbers
11 Enter
SIC
code
with
less
than
4
numbers 12345 Invalid
SIC
Code. Invalid
SIC
Code. Pass
Test
Case
ID: P05 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Niche
Name Test
Execution
Date:
06/11/2015
Description Verify
the
SIC
Code
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
and
SIC
Code.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1 Do
not
enter
any
value
in
the
field Empty
value
Invalid
Niche
Name
Invalid
Niche
Name Pass
2 Enter
only
special
characters
for !@#$!
Invalid
Niche
Name
Invalid
Niche
Name Pass
3 Enter
Niche
Name
with
trailing
spaces 95053
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5
Enter
only
spaces
Invalid
Niche
Name
Invalid
Niche
Name Pass

91. 91
6 Enter
combination
of
characters
and
numbers abcd@
Invalid
Niche
Name
Invalid
Niche
Name Pass
7 Enter
combination
of
special
characters
and
numbers @2234
Invalid
Niche
Name
Invalid
Niche
Name Pass
8 Enter
combination
of
special
characters
and
characters 12@ww
Invalid
Niche
Name
Invalid
Niche
Name Pass
Test
Case
ID: P06 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Effective
Date Test
Execution
Date:
06/11/2015
Description Verify
if
Effective
Date
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code
and
Niche
Name.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
effective
date
Invalid
effective
date Pass
2
Enter
only
special
characters !@#$!
Invalid
effective
date
Invalid
effective
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass

92. 92
5 Enter
only
spaces
Invalid
effective
date
Invalid
effective
date Pass
6 Enter
characters abscd
Invalid
effective
date
Invalid
effective
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
effective
date
Invalid
effective
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
effective
date
Invalid
effective
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
effective
date
Invalid
effective
date Pass
Test
Case
ID: P07 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Expiration
Date Test
Execution
Date:
06/11/2015
Description Verify
if
Expiration
Date
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name
and
Effective
Date.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)

93. 93
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass
6 Enter
characters abscd
Invalid
expiration
date
Invalid
expiration
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
expiration
date
Invalid
expiration
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
expiration
date
Invalid
expiration
date Pass
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass
Test
Case
ID: P07 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015

94. 94
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Expiration
Date Test
Execution
Date:
06/11/2015
Description Verify
if
Expiration
Date
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name
and
Effective
Date.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass
6 Enter
characters abscd
Invalid
expiration
date
Invalid
expiration
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
expiration
date
Invalid
expiration
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
expiration
date
Invalid
expiration
date Pass

95. 95
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass
Test
Case
ID: P08 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Department-­‐LoB
Input
Test
Execution
Date:
06/11/2015
Description Verify
the
Expiration
Date
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name,
Effective
Date
and
Expiration
Date.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass

96. 96
6 Enter
characters abscd
Invalid
expiration
date
Invalid
expiration
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
expiration
date
Invalid
expiration
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
expiration
date
Invalid
expiration
date Pass
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass
Test
Case
ID: P09 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Premim Test
Execution
Date:
06/11/2015
Description Verify
if
the
premium
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name,
Effective
Date
,
Expiration
Date,
department
and
LoB.

97. 97
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$! 0 0 Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
Premium. Invalid
Premium. Pass
6
Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P10 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Commission Test
Execution
Date:
06/11/2015
Description Verify
if
the
commission
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name,
Effective
Date
,
Expiration
Date,
department,
LoB
and
commission.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)

98. 98
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$! 0 0 Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe 0 0 Pass
6 Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P10 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Losses Test
Execution
Date:
06/11/2015
Description Verify
if
the
losses
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name,
Effective
Date,
Expiration
Date,
department,
LoB,
commission
and
premium.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$! 0 0 Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe 0 0 Pass

99. 99
6
Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P11 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Losses Test
Execution
Date:
06/11/2015
Description Verify
if
the
commission
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name,
Effective
Date,
Expiration
Date,
department,
LoB,
commission
and
premium.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$! 0 0 Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe 0 0 Pass
6
Enter
only
numbers 12344 12344 12344 Pass

100. 100
Test
Case
ID: P11 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Producer Test
Execution
Date:
06/11/2015
Description Verify
if
the
producer
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name,
Effective
Date,
Expiration
Date,
department,
LoB,
commission,
premium
and
losses.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Enter
producer
belonging
to
Property
and
Casualty
to
Life
department
Producer:
Vidal
Sassoon
Department:
Life
The
producer
Vidal
Sassoon
belongs
to
the
department
Property
and
Casualty
The
producer
Vidal
Sassoon
belongs
to
the
department
Property
and
Casualty Pass
2
Enter
producer
belonging
to
Property
and
Casualty
to
Benefits
department
Producer:
Vidal
Sassoon
Department:
Life
The
producer
Vidal
Sassoon
belongs
to
the
department
Property
and
Casualty
The
producer
Vidal
Sassoon
belongs
to
the
department
Property
and
Casualty Pass
4
Enter
producer
belonging
to
Benefits
department
to
Life
Producer:
John
Frida
Department:
Life
The
producer
John
Frida
belongs
to
the
department
Benefits
The
producer
John
Frida
belongs
to
the
department
Benefits Pass
5
Enter
producer
belonging
to
Life
department
to
Benefits
Producer:
Max
Factor
Department:
Benefits
The
producer
Max
Factor
belongs
to
the
department
Life
The
producer
Max
Factor
belongs
to
the
department
Life Pass

101. 101
6
Enter
producer
belonging
to
Life
department
to
Property
and
Casualty
Producer:
Max
Factor
Department:
Property
and
Casualty
The
producer
Max
Factor
belongs
to
the
department
Life
The
producer
Max
Factor
belongs
to
the
department
Life
Pass
Test
Case
ID: P12 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title As
of
Date Test
Execution
Date:
06/11/2015
Description Verify
if
the
As
of
Date
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Add
New
Record’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name,
Effective
Date,
Expiration
Date,
department,
LoB,
commission,
premium,
losses
and
producer.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Enter
only
special
characters !@#$!
Invalid
As
of
Date
Invalid
As
of
Date Pass
2 Enter
characters abscd
Invalid
As
of
Date
Invalid
As
of
Date Pass
4
Enter
combination
of
characters
and
numbers abcd@
Invalid
As
of
Date
Invalid
As
of
Date Pass
5
Enter
combination
of
special
characters
and
numbers @2234
Invalid
As
of
Date
Invalid
As
of
Date Pass
6
Enter
combination
of
special
characters
12@ww
Invalid
As
of
Date
Invalid
As
of
Date Pass

102. 102
and
characters
Test
Case
ID: P13 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title LoB-­‐Producer Test
Execution
Date:
06/11/2015
Description Verify
if
the
LoB
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Update
Property
and
Casualty
with
Life
Producer
Department:
Property
and
Casualty
Producer:
Max
Factor
Max
Factor
belongs
to
the
Department
Life
Max
Factor
belongs
to
the
Department
Life Pass
2
Update
Property
and
Casualty
with
Benefits
Producer
Department:
Property
and
Casualty
Producer:
John
Frida
John
Frida
belongs
to
the
Department
Benefits
John
Frida
belongs
to
the
Department
Benefits. Pass
4
Update
Life
with
Property
and
Casualty
Producer
Department:
Life
Producer:
Vidal
Sassoon
Vidal
Sassoon
belongs
to
the
Department
Property
and
Casualty
Vidal
Sassoon
belongs
to
the
Department
Property
and
Casualty Pass
5 Update
Department:
Vidal
Sassoon
Vidal
Sassoon
Pass

103. 103
Benefits
with
Property
and
Casualty
Producer
Benefits
Producer:
Vidal
Sassoon
belongs
to
the
Department
Property
and
Casualty
belongs
to
the
Department
Property
and
Casualty
6
Update
Life
with
Benefits
Producer
Department:
Life
Producer:
John
Frida
John
Frida
belongs
to
the
Department
Benefits
John
Frida
belongs
to
the
Department
Benefits Pass
Update
Benefits
with
Life
Producer
Department:
Life
Producer:
Max
Factor
Max
Factor
belongs
to
the
Department
Life
Max
Factor
belongs
to
the
Department
Life
Test
Case
ID: P14 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Premium
Update Test
Execution
Date:
06/11/2015
Description Verify
if
the
premium
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$!
Invalid
Premium.
Invalid
Premium. Pass

104. 104
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
Premium.
Invalid
Premium. Pass
6
Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P15 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Premium
Update Test
Execution
Date:
06/11/2015
Description Verify
if
the
premium
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$!
Invalid
Premium.
Invalid
Premium. Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
Premium.
Invalid
Premium. Pass

105. 105
6
Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P16 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Commission
Update
Test
Execution
Date:
06/11/2015
Description Verify
if
the
commission
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$!
Invalid
Commission.
Invalid
Commission. Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
Commission.
Invalid
Commission. Pass
6 Enter
only
numbers 12344 12344 12344 Pass

106. 106
Test
Case
ID: P17 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Losses
Update Test
Execution
Date:
06/11/2015
Description Verify
if
the
losses
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$! Invalid
Losses. Invalid
Losses. Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe Invalid
Losses. Invalid
Losses. Pass
6
Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P18 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair

107. 107
Test
Title As
of
Date
Update
Test
Execution
Date:
06/11/2015
Description Verify
if
the
As
of
Date
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value Pass
2
Enter
only
special
characters !@#$!
Invalid
As
of
Date.
Invalid
As
of
Date. Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
As
of
Date.
Invalid
As
of
Date. Pass
6
Enter
only
numbers 06/06/2014 06/06/2014 06/06/2014 Pass
Test
Case
ID: P18 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Check
if
client
appears
on
the
login
page
Test
Execution
Date:
06/11/2015
Description The
updated
policy
appears
on
the
home
page.

108. 108
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
A
new
client
has
been
added Company
‘Company’
appears
on
the
homepage
‘Company’
appears
on
the
homepage Pass
Test
Case
ID: P19 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Delete
Policy Test
Execution
Date:
06/11/2015
Description Delete
policy.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result Actual
Result
Status
(Pass/Fail)
1 Press
delete
in
the
table Umbrella
‘LoB
has
been
deleted’
and
return
to
Add
Client
Record
Page
‘LoB
has
been
deleted’
and
return
to
Add
Client
Record
Page Pass

109. 109
Test
Case
ID: P20 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Company
Name
Update
Test
Execution
Date:
06/11/2015
Description Verify
the
company
name
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
Step Test
Steps Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1 Click
on
Edit
Policy
button
Click
on
button
Edit
Policy
Page
is
displayed
Edit
Policy
Page
is
displayed
Pass
2 Do
not
enter
any
value
in
the
field Empty
value
Invalid
company
name.
Invalid
company
name. Pass
3 Enter
only
special
characters
for
company
name !@#$!
Invalid
company
name.
Invalid
company
name. Pass
5
Enter
only
spaces
Invalid
company
name.
Invalid
company
name. Pass

110. 110
Test
Case
ID: P21 Test
Designed
By: Namita
Nair
Test
Priority
(Low/Medium/High):
Medium Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By: Namita
Nair
Test
Title Email
Update
Test
Execution
Date:
06/11/2015
Description Verify
the
email
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
The
user
must
also
enter
a
valid
company
name.
Step Test
Data Expected
Result Actual
Result
Status
(Pass/Fail)
1 Do
not
enter
any
value
in
the
field Empty
value
Email
name
cannot
be
empty.
Email
name
cannot
be
empty. Pass
2 Enter
only
special
characters
for
email !@#$!
Invalid
email
address.
Invalid
email
address. Pass
3 Enter
only
spaces
in
the
field
Invalid
email
address.
Invalid
email
address. Pass
5 Enter
email
with
trailing
spaces namu.nair@gmail.com
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
Enter
only
numbers 12344
Invalid
email
address.
Invalid
email
address. Pass
Enter
a
combination
of
numbers
and
symbols 123@@#
Invalid
email
address.
Invalid
email
address. Pass
Enter
a
combination
of
characters,
special
characters
without
‘com’ namu.nair123_@
Invalid
email
address.
Invalid
email
address. Pass

111. 111
Test
Case
ID: P22 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
Medium Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Zip
Code
Update Test
Execution
Date:
06/11/2015
Description Verify
the
Zip
Code
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
The
user
must
also
enter
a
valid
company
name
and
email..
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1 Do
not
enter
any
value
in
the
field Empty
value
Zip
Code
cannot
be
empty.
Zip
Code
cannot
be
empty. Pass
2 Enter
only
special
characters !@#$! Invalid
Zip
Code. Invalid
Zip
Code. Pass
3 Enter
zip
code
with
trailing
spaces 95053
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces Invalid
Zip
Code. Invalid
Zip
Code. Pass
6 Enter
characters abscd Invalid
Zip
Code. Invalid
Zip
Code. Pass
7 Enter
combination
of
characters
and
numbers abcd@ Invalid
Zip
Code. Invalid
Zip
Code. Pass
8 Enter
combination
of
special
characters
and
numbers @2234 Invalid
Zip
Code. Invalid
Zip
Code. Pass
9 Enter
combination
of
special
characters
and
characters 12@ww Invalid
Zip
Code. Invalid
Zip
Code. Pass

112. 112
10 Enter
zip
code
with
greater
than
5
numbers 123456 Invalid
Zip
Code. Invalid
Zip
Code. Pass
11 Enter
zip
code
with
less
than
5
numbers 1234 Invalid
Zip
Code. Invalid
Zip
Code. Pass
Test
Case
ID: P23 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title SIC
Code
Update Test
Execution
Date:
06/11/2015
Description Verify
the
SIC
Code
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
The
user
must
also
enter
a
valid
company
name,
email
and
zip
code.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1 Do
not
enter
any
value
in
the
field Empty
value
SIC
Code
cannot
be
empty.
SIC
Code
cannot
be
empty. Pass
2 Enter
only
special
characters !@#$! Invalid
SIC
Code. Invalid
SIC
Code. Pass
3 Enter
zip
code
with
trailing
spaces 0001
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces Invalid
SIC
Code. Invalid
SIC
Code. Pass
6 Enter
characters abscd Invalid
SIC
Code. Invalid
SIC
Code. Pass

113. 113
7 Enter
combination
of
characters
and
numbers abcd@ Invalid
SIC
Code. Invalid
SIC
Code. Pass
8 Enter
combination
of
special
characters
and
numbers @2234 Invalid
SIC
Code. Invalid
SIC
Code. Pass
9 Enter
combination
of
special
characters
and
characters 12@ww Invalid
SIC
Code. Invalid
SIC
Code. Pass
10 Enter
SIC
code
with
greater
than
4
numbers 123 Invalid
SIC
Code. Invalid
SIC
Code. Pass
11 Enter
SIC
code
with
less
than
4
numbers 12345 Invalid
SIC
Code. Invalid
SIC
Code. Pass
Test
Case
ID: P24 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Niche
Name
Update
Test
Execution
Date:
06/11/2015
Description Verify
the
SIC
Code
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
and
SIC
Code.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1 Do
not
enter
any
value
in
the
field Empty
value
Invalid
Niche
Name
Invalid
Niche
Name Pass

114. 114
2 Enter
only
special
characters
for !@#$!
Invalid
Niche
Name
Invalid
Niche
Name Pass
3 Enter
Niche
Name
with
trailing
spaces 95053
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5
Enter
only
spaces
Invalid
Niche
Name
Invalid
Niche
Name Pass
6 Enter
combination
of
characters
and
numbers abcd@
Invalid
Niche
Name
Invalid
Niche
Name Pass
7 Enter
combination
of
special
characters
and
numbers @2234
Invalid
Niche
Name
Invalid
Niche
Name Pass
8 Enter
combination
of
special
characters
and
characters 12@ww
Invalid
Niche
Name
Invalid
Niche
Name Pass
Test
Case
ID: P25 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Effective
Date Test
Execution
Date:
06/11/2015
Description Verify
if
Effective
Date
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code
and
Niche
Name.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)

115. 115
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
effective
date
Invalid
effective
date Pass
2
Enter
only
special
characters !@#$!
Invalid
effective
date
Invalid
effective
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
effective
date
Invalid
effective
date Pass
6 Enter
characters abscd
Invalid
effective
date
Invalid
effective
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
effective
date
Invalid
effective
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
effective
date
Invalid
effective
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
effective
date
Invalid
effective
date Pass
Test
Case
ID: P26 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Expiration
Date Test
Execution
Date:
06/11/2015
Description Verify
if
Expiration
Date
entered
by
the
user
is
correct.

116. 116
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code,
SIC
Code,
Niche
Name
and
Effective
Date.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass
6 Enter
characters abscd
Invalid
expiration
date
Invalid
expiration
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
expiration
date
Invalid
expiration
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
expiration
date
Invalid
expiration
date Pass
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass

117. 117
Test
Case
ID: P27 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Expiration
Date Test
Execution
Date:
06/11/2015
Description Verify
if
Expiration
Date
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name
and
Effective
Date.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass
6 Enter
characters abscd
Invalid
expiration
date
Invalid
expiration
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
@2234
Invalid
expiration
date
Invalid
expiration
date Pass

118. 118
numbers
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
expiration
date
Invalid
expiration
date Pass
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass
Test
Case
ID: P28 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Department-­‐LoB
Input
Test
Execution
Date:
06/11/2015
Description Verify
the
Expiration
Date
entered
by
the
user
is
correct.
Dependencies The
Account
Manager
should
have
the
client
details
from
the
Producer,
should
have
logged
in
and
clicked
on
the
‘Edit
Policy’.
The
user
must
also
enter
a
valid
company
name,
email,
zip
code
SIC
Code,
Niche
Name,
Effective
Date
and
Expiration
Date.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass

119. 119
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass
6 Enter
characters abscd
Invalid
expiration
date
Invalid
expiration
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
expiration
date
Invalid
expiration
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
expiration
date
Invalid
expiration
date Pass
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass
Test
Case
ID: P29 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Premium
Update Test
Execution
Date:
06/11/2015

120. 120
Description Verify
if
the
premium
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$!
Invalid
Premium.
Invalid
Premium. Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
Premium.
Invalid
Premium. Pass
6
Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P30 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Premium
Update Test
Execution
Date:
06/11/2015
Description Verify
if
the
premium
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.

121. 121
Step Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$!
Invalid
Premium.
Invalid
Premium. Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
Premium.
Invalid
Premium. Pass
6
Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P31 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Commission
Update
Test
Execution
Date:
06/11/2015
Description Verify
if
the
commission
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$!
Invalid
Commission.
Invalid
Commission. Pass

122. 122
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
Commission.
Invalid
Commission. Pass
6 Enter
only
numbers 12344 12344 12344 Pass
Test
Case
ID: P32 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Losses
Update Test
Execution
Date:
06/11/2015
Description Verify
if
the
losses
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value 0 0 Pass
2
Enter
only
special
characters !@#$! Invalid
Losses. Invalid
Losses. Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe Invalid
Losses. Invalid
Losses. Pass
6
Enter
only
numbers 12344 12344 12344 Pass

123. 123
Test
Case
ID: P33 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title As
of
Date
Update
Test
Execution
Date:
06/11/2015
Description Verify
if
the
As
of
Date
entered
by
the
user
is
correct
in
the
editable
table
at
the
bottom
of
Add
New
Record
Page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value Pass
2
Enter
only
special
characters !@#$!
Invalid
As
of
Date.
Invalid
As
of
Date. Pass
4
Enter
only
spaces
in
the
field 0 0 Pass
5 Enter
characters weewe
Invalid
As
of
Date.
Invalid
As
of
Date. Pass
6
Enter
only
numbers 06/06/2014 06/06/2014 06/06/2014 Pass
Test
Case
ID: P34 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015

124. 124
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Check
if
client
appears
on
the
login
page
Test
Execution
Date:
06/11/2015
Description The
updated
policy
appears
on
the
home
page.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
A
new
client
has
been
edited Company
‘Company’
appears
on
the
homepage
‘Company’
appears
on
the
homepage Pass
Test
Case
ID: P35 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Delete
policy
Test
Execution
Date:
06/11/2015
Description Delete
policy.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Actual
Result Status
(Pass/Fail)

125. 125
Result
1
Press
delete
in
the
table Umbrella
‘LoB
has
been
deleted’
and
return
to
Add
Client
Record
Page
‘LoB
has
been
deleted’
and
return
to
Edit
Client
Record
Page Pass
Test
Case
ID: P50 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Expiration
Date Test
Execution
Date:
06/11/2015
Description Verify
if
Expiration
Date
entered
by
the
user
is
correct.
Dependencies A
policy
has
been
entered
and
the
renew
button
has
been
clicked.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass
6 Enter
characters abscd Invalid
expiration
Invalid
expiration
Pass

126. 126
date date
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
expiration
date
Invalid
expiration
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
expiration
date
Invalid
expiration
date Pass
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass
Test
Case
ID: P51 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Expiration
Date Test
Execution
Date:
06/11/2015
Description Verify
if
Expiration
Date
entered
by
the
user
is
correct.
Dependencies A
policy
has
been
entered
and
the
renew
button
has
been
clicked.

127. 127
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass
6 Enter
characters abscd
Invalid
expiration
date
Invalid
expiration
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
expiration
date
Invalid
expiration
date Pass
9
Enter
combination
of
special
characters
and
characters 12@ww
Invalid
expiration
date
Invalid
expiration
date Pass
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass

128. 128
Test
Case
ID: P52 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager Test
Executed
By:
Namita
Nair
Test
Title Department-­‐LoB
Input
Test
Execution
Date:
06/11/2015
Description Verify
the
Expiration
Date
entered
by
the
user
is
correct.
Dependencies A
policy
has
been
entered
and
the
renew
button
has
been
clicked.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Do
not
enter
any
value
in
the
field Empty
value
Invalid
expiration
date
Invalid
expiration
date Pass
2
Enter
only
special
characters
for !@#$!
Invalid
expiration
date
Invalid
expiration
date Pass
4
Enter
effective
date
with
trailing
spaces 06/06/2014
The
spaces
must
be
trimmed.
The
spaces
must
be
trimmed. Pass
5 Enter
only
spaces
Invalid
expiration
date
Invalid
expiration
date Pass
6 Enter
characters abscd
Invalid
expiration
date
Invalid
expiration
date Pass
7
Enter
combination
of
characters
and
numbers abcd@
Invalid
expiration
date
Invalid
expiration
date Pass
8
Enter
combination
of
special
characters
and
numbers @2234
Invalid
expiration
date
Invalid
expiration
date Pass
9 Enter
combination
12@ww Invalid
expiration
Invalid
Pass

129. 129
of
special
characters
and
characters
date expiration
date
10
Enter
expiration
date
less
than
effective
date
Effective
date:
01/01/2015
Expiration
date:
01/01/2014
Effective
date
cannot
be
longer
than
expiration
date
Effective
date
cannot
be
longer
than
expiration
date Pass
Test
Case
ID: P53 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Delete
policy
Test
Execution
Date:
06/11/2015
Description Delete
policy.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Press
delete
in
the
table Umbrella
‘LoB
has
been
deleted’
and
return
to
Renewal
Page
‘LoB
has
been
deleted’
and
return
to
RenewalRecord
Page Pass

130. 130
Test
Case
ID: P58 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Delete
policy
Test
Execution
Date:
06/11/2015
Description Delete
policy.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Press
delete
in
the
table Umbrella
‘LoB
has
been
deleted’
and
return
to
Cancel
Page
‘LoB
has
been
deleted’
and
return
to
CancelRecord
Page Pass
Test
Case
ID: P58 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Delete
policy
Test
Execution
Date:
06/11/2015

131. 131
Description Delete
policy.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Press
delete
in
the
table Umbrella
‘LoB
has
been
deleted’
and
return
to
Cancel
Page
‘LoB
has
been
deleted’
and
return
to
CancelRecord
Page Pass
Test
Case
ID: P59 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Expiration
Date
Test
Execution
Date:
06/11/2015
Description Verify
if
Expiration
Date
entered
by
the
user
is
correct.
Dependencies A
policy
has
been
entered
and
the
cancel
button
has
been
clicked.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
Insert
characters
in
the
search
bar ‘S’ Smith
Composites
Smith
Composites
Insert
number
the
search
bar ‘9’ 95053 95053

132. 132
Test
Case
ID: P58 Test
Designed
By:
Namita
Nair
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name Account
Manager
Test
Executed
By:
Namita
Nair
Test
Title Delete
policy Test
Execution
Date:
06/11/2015
Description Delete
policy.
Dependencies A
policy
must
be
successfully
inserted.
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Press
delete
in
the
table/
Search
Table Umbrella
‘LoB
has
been
deleted’
and
return
to
Cancel
Page
‘LoB
has
been
deleted’
and
return
to
CancelRecord
Page Pass
• Test
Cases
-­‐
Login
and
Session
Management
Test
Case
ID: P01 Test
Designed
By:
Pallavi
Khadamkar
Test
Priority
(Low/Medium/High):
Medium Test
Designed
Date:
06/10/2015
Module
Name Login Test
Executed
By:
Pallavi
Khadamkar
Test
Title Test
the
System
login
Page
Test
Execution
Date:
06/11/2015

133. 133
Description Test
the
System
login
Page.
Dependencies The
database
should
have
login_status
as
0
against
the
valid
user.
User
enters
valid
username
and
password.
Step Test
Data Expected
Result Actual
Result Status
(Pass/Fail)
1
Navigate
to
login
Page
2
User
enters
valid
username amahadik@g.com
3
User
enters
valid
password Amahadik123$
4
Click
on
Login
button
User
successfully
enters
the
system
User
successfully
enters
the
system Pass
Test
Case
ID: P02 Test
Designed
By:
Pallavi
Khadamkar
Test
Priority
(Low/Medium/High):
Medium Test
Designed
Date:
06/10/2015
Module
Name Login Test
Executed
By:
Pallavi
Khadamkar
Test
Title Verify
the
logs
with
valid/invalid
username
and
valid/invalid
password
Test
Execution
Date:
06/11/2015
Description Test
the
System
login
Page.
Dependencies User
enters
username
and
password.
The
database
should
have
login_status
as
0
against
the
valid
user

134. 134
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Navigate
to
login
Page
2
User
enters
valid
username amahadik@g.com
3
User
enters
an
invalid
password Amahadik1234$
User
should
be
redirected
to
the
page
indicating
the
error
invalid
username/password
User
should
be
redirected
to
the
page
indicating
the
error
invalid
username/password Pass
4
User
enters
a
blank
username
User
should
be
shown
a
pop
up
message
with
error
"This
field
is
required"
User
should
be
shown
a
pop
up
message
with
error
"This
field
is
required Pass
5
User
enters
username
without
@
sign amahadik
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address"
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address" Pass
6
User
enters
username
with
all
numbers 12345
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address"
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address" Pass
7
User
enters
username
with
a
space amahadi
k
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address"
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address" Pass
Test
Case
ID: P03 Test
Designed
By:
Pallavi
Khadamkar
Test
Priority
(Low/Medium/High):
Medium Test
Designed
Date:
06/10/2015

135. 135
Module
Name CheckLoginPassword Test
Executed
By:
Pallavi
Khadamkar
Test
Title Validate
the
user
Test
Execution
Date:
06/11/2015
Description Test
the
validation
of
the
user
Dependencies User
enters
valid
username
and
password.The
database
should
have
login_status
as
0
against
the
valid
user
Step Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1 Click
on
login
button
2
System
retrieves
the
row
against
the
valid
user
3
System
retrieves
the
login_status
value
4
If
the
login_status
is
logged
out
Login_status
=0
System
validates
user
System
validates
user Pass
5
System
retrieves
todays
date
6
System
retrieves
password_date
value
7 System
compares
2
dates
8
If
the
difference
is
a
week’s
time
or
less.
Test
Case
ID:
P05
Test
Designed
By:
Pallavi
Khadamkar
Test
Priority
(Low/Medium/High):
High
Test
Designed
Date:
06/10/2015

136. 136
Module
Name
CheckSessi
onExistanc
e
Test
Executed
By:
Pallavi
Khadamkar
Test
Title
Validate
the
user
Test
Execution
Date:
06/11/2015
Description
Test
that
the
Account
Manager
is
shown
his
home
Page
on
other
tab
when
he
is
already
logged
in
on
same
Browser
Dependencies
Already
logged
in
on
browser
as
an
Account
Manager.
The
database
has
login_status
as
1
against
the
valid
user.
Step
Test
Data
Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Open
new
tab
in
browser
and
click
on
login
link
HomePage_Acco
untManager
of
the
already
logged
in
user
HomePage_Acc
ountManager
of
the
already
logged
in
user
Pass
Test
Case
ID:
P06
Test
Designed
By:
Pallavi
Khadamkar
Test
Priority
(Low/Medium/High):
High
Test
Designed
Date:
06/10/2015
Module
Name
Forgetpassw
ord
Test
Executed
By:
Pallavi
Khadamkar
Test
Title
Email
is
sent
to
the
user
Test
Execution
Date:
06/11/2015
Description
Test
forget
password
module
Dependencies
User
forgets
his
password.
The
database
has
login_status
as
0
against
the
valid
user

137. 137
Step
Test
Data
Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Navigate
to
the
Login
Page
2
User
clicks
forget
password
link
User
is
prompted
to
enter
email
address
User
is
prompted
to
enter
email
address
Pass
3
User
enters
valid
email
address
pallavikhadamkar
@gmail.commailto
:pallavikhadamkar
@gmail.com
mailto:pallavik
hadamkar@gm
ail.com
mailto:pallav
ikhadamkar
@gmail.com
Pass
4
User
clicks
on
generate
password
link
System
sends
email
to
user
with
a
temporary
password
System
sends
email
to
user
with
a
temporary
password
Pass
Test
Case
ID: P07 Test
Designed
By: Pallavi
Khadamkar
Test
Priority
(Low/Medium/High):
High Test
Designed
Date: 06/10/2015
Module
Name Forgetpassword Test
Executed
By: Pallavi
Khadamkar
Test
Title Change
password
Test
Execution
Date: 06/11/2015
Description Test
forgetpassword
module
Dependencies User
receives
temporary
password
and
link
to
change
password.
The
database
has
login_status
as
0
against
the
valid
user.

138. 138
Step Test
Data Expected
Result Actual
Result
Status
(Pass/Fail)
1
Navigate
to
the
link
in
the
mail
System
prompts
user
to
enter
changed
password
System
prompts
user
to
enter
changed
password Pass
2
User
leaves
username
field
blank
User
should
be
shown
a
pop
up
message
with
error
"This
field
is
required"
User
should
be
shown
a
pop
up
message
with
error
"This
field
is
required" Pass
3
User
enters
username
without
@
sign Pallavikhadamkar
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address"
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address" Pass
4
User
enters
username
with
a
space Pallavi
Khadamkar
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address"
User
should
be
shown
a
pop
up
message
with
error
"You
must
enter
a
valid
email
address" Pass
5
User
enters
valid
username pallavikhadamkar@gmail.com
6
User
enters
valid
temporary
password
7
User
leaves
password
blank
Password
strength
value
is
type
password
Password
strength
value
is
type
password Pass

139. 139
8
User
enters
1
letter P
Password
strength
value
is
very
weak
Password
strength
value
is
very
weak Pass
9 User
enter
1
digit 2
Password
strength
value
is
weak
Password
strength
value
is
weak Pass
10
User
enters
1
digit
and
1
letter P2
or
2P
Password
strength
value
is
weak
Password
strength
value
is
weak Pass
11
User
enters
2
letters
and
1
digit
or
2
letters,1
digit
and
1
character P2e
or
P1@
Password
strength
value
is
better
Password
strength
value
is
better Pass
12
User
enters
one
lowercase,one
uppercase,
one
alphanumeric
character
and
one
digit
p1@D
or
p1@Ds
Password
strength
value
is
Medium
Password
strength
value
is
Medium Pass
13
User
enters
one
uppercase,
3
lowercase
letters,
2
digits
and
one
alphanumeric Pall12$
Password
strength
value
is
Strong
Password
strength
value
is
Strong Pass
14
User
enters
atleast
one
uppercase
letter
atleast
2
digits
and
atleast
one
alphanumeric
character
and
length
of
11
Pallavi123$,
Pallavie12$
Password
strength
value
is
Strongest
Password
strength
value
is
Strongest Pass
15
User
hits
Submit
button
User
is
prompted
confirming
his
password
change
User
is
prompted
confirming
his
password
change Pass
16
User
enters
invalid
username amahadik@g.com
Redirect
to
the
error
message
Redirect
to
the
error
message Pass
17 User
enters
Redirect
to
Redirect
to
Pass

140. 140
invalid
temporary
password
the
error
message
the
error
message
18
User
enters
different
passwords
in
new
password
field
and
confirm
password
field
New:
Pallavi123$
Confirm:
Pallavi234$
Redirect
to
the
error
message
Redirect
to
the
error
message Pass
Test
Case
ID: P08 Test
Designed
By:
Pallavi
Khadamkar
Test
Priority
(Low/Medium/High):
Low Test
Designed
Date:
06/10/2015
Module
Name SignUp
Password
Check
Test
Executed
By:
Pallavi
Khadamkar
Test
Title Verify
password
during
sign
up
Test
Execution
Date:
06/11/2015
Description Check
Strength
of
Password
during
Sign
Up
Dependencies User
is
not
already
present
in
the
Database
Step Test
Data Expected
Result
Actual
Result Status
(Pass/Fail)
1
Account
Manager
clicks
on
Sign
up
user
button
2
Account
manager
enters
Name

141. 141
3
User
enters
blank
Name
User
is
prompted
with
a
message
saying
“This
is
a
required
field”
User
is
prompted
with
a
message
saying
“This
is
a
required
field” Pass
Sign
up
button
is
disabled
4
User
enters
a
space
Pallavi
Khadamkar
User
is
allowed
to
enter
name
User
should
be
allowed
to
go
ahead Pass
Sign
up
button
is
disabled
5
User
leaves
Email
blank
Error
message
thrown
“Please
fill
out
this
field”
Error
message
thrown
“Please
fill
out
this
field” Pass
Sign
up
button
is
disabled
6
User
enters
email
Id
without
@
sign Pallavikhadamkar
Error
message
thrown
“Please
include
an
@
in
the
email”
Error
message
thrown
“Please
include
an
@
in
the
email” Pass
Sign
up
button
is
disabled
7
Click
sign
up
button
Redirected
to
a
page
saying
“Inserted
Successfully”
Redirected
to
a
page
saying
“Inserted
Successfully” Pass
Test
Case
ID:
P09
Test
Designed
By:
Pallavi
Khadamkar
Test
Priority
(Low/Medium/High
):
High
Test
Designed
Date:
06/10/2015
Module
Name
CheckLogi
nPasswor
d
Test
Executed
By:
Pallavi
Khadamkar
Test
Title
Validate
the
user
Test
Execution
Date:
06/11/2015
Description
Test
that
the
user
is
logged
out
from
Machine
1
when
logged
in
again
from
Machine
2.

142. 142
Dependencies
User
is
an
Account
Manager
and
viewing
HomePage_AccountManager
page
on
Machine
1.
The
database
has
login_status
as
1
against
the
valid
user.
Step
Test
Data
Expected
Result
Actual
Result
Status
(Pass/Fail)
1
Navigate
to
Login
Page
in
System
2
2
User
enters
valid
username
amahadik@g.co
mmailto:amaha
dik@g.com
mailto:amahad
ik@g.com
mailto:amaha
dik@g.com
Pass
3
User
enters
valid
password
Amahadik123$
4
If
the
login_statu
s
is
logged
in
Login_status
=1
System
redirects
the
user
prompting
with
an
error
message
“Please
hit
Continue
to
login
to
current
session”
System
redirects
the
user
prompting
with
an
error
message
“Please
hit
Continue
to
login
to
current
session”
Pass
5
User
hits
continue
link
User
is
redirected
to
Login
Page
User
is
redirected
to
Login
Page
Pass
6
User
enters
valid
username
in
System
2
amahadik@g.co
mmailto:amaha
dik@g.com
mailto:amahad
ik@g.com
mailto:amaha
dik@g.com
Pass
7
User
enters
valid
password
in
System
2
Amahadik123$
User
is
redirected
to
HomePage_Acc
ountManager.p
hp
in
System
2
User
is
redirected
to
HomePage_Ac
countManager
.php
in
System
2
Pass
8
User
hits
Add
new
Record
/Edit/
Delete/Can
cel/Renew
User
is
redirected
to
a
logout
screen
showing
him
message
“You
have
been
User
is
redirected
to
a
logout
screen
showing
him
message
“You
Pass

143. 143
button
on
System
1
screen
successfully
logged
out”
on
System
1
have
been
successfully
logged
out”
on
System
1
9
User
continues
with
new
session
on
System
2
Test
Case
ID: P10 Test
Designed
By:
Pallavi
Khadamkar
Test
Priority
(Low/Medium/High):
High Test
Designed
Date:
06/10/2015
Module
Name CheckSessionExistance Test
Executed
By:
Pallavi
Khadamkar
Test
Title Validate
the
user
-­‐
Manager
Test
Execution
Date:
06/11/2015
Description Test
whether
Manager
can
save
goals
in
the
first
system
when
logged
into
another
system.
Dependencies Manager
logged
into
two
systems.
Step Test
Data Expected
Result
Actual
Result
Status
(Pass/Fail)
1 Goals
tab
is
open
Goals
are
displayed
Goals
are
displayed Pass
2 Click
on
‘Save’
button
User
is
logged
out
User
is
logged
out Pass

144. 144
User
Guide
• Login
Enter
the
login
credentials
into
the
username
and
password
fields
to
get
access
the
system.
• Forgot
Password
The
user
can
change
his/her
password
by
clicking
on
the
Forgot
Password
link
at
the
bottom.

145. 145
The
user
is
redirected
to
the
change
password
screen
where
they
are
prompted
to
enter
the
username
and
click
on
‘Generate
password
and
send
link
through
mail’.
The
user
is
then
sent
an
email
with
a
temporary
password.
By
clicking
on
the
link,
the
person
is
redirected
to
resetpasssword_lighhouse
Page
where
the
user
enters
their
username
and
changed
password.

146. 146
When
the
user
hits
continue,
they
will
be
sent
a
confirmation
message
showing
that
the
password
is
changed
successfully.
The
confirmation
page
showing
that
the
password
was
changed
successfully.

147. 147
• Account
Manager
After
login,
the
Account
Manager
sees
the
Home
Page
dashboard
screen
that
shows
the
list
of
the
most
recently
added/
edited
client
policies.
o This
page
allows
the
Account
Manager
to
add
new
policies
using
‘Add
New
Record’
at
the
top
right
corner.
o Account
Manager
can
edit
the
existing
policy
by
clicking
on
‘Edit
’
button
next
to
it.
o Account
Manager
can
delete
the
existing
policy
by
clicking
on
‘Delete’
next
to
it.
o Account
Manager
can
renew
the
existing
policy
by
clicking
on
‘Renew’
next
to
it.
o Account
Manager
can
cancel
the
existing
policy
by
clicking
on
‘Cancel’
next
to
it.

148. 148
When
an
Account
Manager
choses
to
edit
the
policy,
they
are
shown
a
Policy
Information
view
where
they
can
change
the
fields
and
save
the
client
information
by
clicking
on
‘Save
Client
Data’.
o This
page
allows
the
Account
Manager
to
add
a
new
line
of
business
to
the
Client’s
policy
by
clicking
on
‘Add
Line
of
Business’.
The
Account
Manager
can
add
a
LoB
clicking
on
the
Department
and
selecting
a
Line
of
Business.
o The
Account
Manager
can
save
the
Client
record
by
clicking
on
‘Add
LoB’.

149. 149
When
Account
Manager
clicks
on
‘Save
Client
Data’
the
system
gives
a
confirmation
message
saying
the
client
record
is
saved.
Account
Manager
can
delete
the
policy
by
clicking
on
‘Delete
Policy’
at
the
bottom
right.

150. 150
After
clicking
on
‘Renew’
button
next
to
the
policy
on
the
HomePage_AccountManager.php,
the
Account
Manager
is
navigated
to
the
Renewal_AccountManager.php
page,
which
will
allow
them
to
renew
the
policy
by
clicking
on
‘Renew’
at
the
bottom
right.

151. 151
After
the
policy
is
renewed,
the
Status
of
the
Line
of
Business
is
changed
from
‘New’
to
‘Renewed’.
After
the
client
clicks
on
Cancel
policy
on
HomePage_AccountManager.php
he
is
redirected
to
the
Cancel_AccountManager
where
Account
Manager
can
cancel
the
policy
by
clicking
on
‘Cancel
Policy’
button.

152. 152
The
Account
Manager
is
prompted
to
confirm
if
he/she
really
wants
to
cancel
it.
After
the
user
clicks
on
Log
out
link
under
the
username
on
the
right
top
corner,
the
session
is
destroyed
and
the
user
is
logged
out.

153. 153
By
clicking
on
the
Sign
Up
User
link,
the
Account
Manager
can
sign
up
any
new
Account
Manager,
Producer
or
Manager.

154. 154
Account
Manager
can
fill
in
the
details
for
the
user
and
sign
them
up
in
the
system.
• Producer
After
login,
the
Producer
will
see
their
dashboard
including
their
Goals
and
News
Feed.
o The
Overall
Goals
section
will
show
where
the
Producer’s
book
of
business,
retention
rate
and
new
business
revenue
year-­‐to-­‐date
in
relation
to
the
goals
set
by
Management.
o The
News
Feed
allows
the
Producer
to
see
the
latest
activity
on
their
accounts.
By
clicking
the
Client’s
name,
the
Producer
will
be
able
to
view
the
updated
record.
o The
Producer
can
log
out
by
selecting
‘Log
Out’
from
the
dropdown
next
to
the
name.

155. 155
The
Producer
will
view
all
of
the
Client’s
details
based
on
the
most
recent
activity.
o To
return
to
the
homepage,
select
‘Back’.
Below
the
Goals
and
News
Feed
on
the
homepage
is
the
Chart
Area.
o The
Cross-­‐Sell
chart
shows
how
many
accounts
were
written
across
each
of
the
Departments.

156. 156
o The
Niche
chart
shows
the
breakdown
of
accounts
written
in
each
Niche.
The
Producer
can
select
to
view
by
Premium,
Revenue
or
the
Number
of
Accounts.
o New
Business
for
the
year
is
shown
by
month.
Producers
can
select
the
‘Reports’
tab
to
generate
a
custom
report.
o Select
the
desired
start
date,
report
period
and
time
period.
o Select
the
filters
to
include
in
the
output.
o Select
‘Run
Report’.

157. 157
The
report
will
pop
up
based
on
the
selected
parameters.
o Select
‘Close’
to
return
to
the
report
generator.
• Management
After
login,
Management
will
see
their
dashboard
including
the
Agency
Goals
displayed.
o The
Overall
Goals
section
will
show
the
Agency’s
book
of
business,
retention
rate
and
new
business
revenue
year-­‐to-­‐date.
o Management
can
log
out
by
selecting
‘Log
Out’
from
the
dropdown
next
to
the
name.
Management
has
the
ability
to
view
the
goals
for
any
Producer
by
selecting
their
name
from
the
dropdown
menu.

158. 158
o The
Overall
Goals
and
Chart
Area
will
now
reflect
the
figures
for
the
selected
Producer.
Below
the
Goals
on
the
homepage
is
the
Chart
Area.
o The
Cross-­‐Sell
chart
shows
how
many
accounts
were
written
across
each
of
the
Departments.
o The
Niche
chart
shows
the
breakdown
of
accounts
written
in
each
Niche.
Management
can
select
to
view
by
Premium,
Revenue
or
the
Number
of
Accounts.
o New
Business
for
the
year
is
shown
by
month.

159. 159
Management
can
select
the
‘Reports’
tab
to
generate
a
custom
report.
o Select
the
desired
start
date,
report
period
and
time
period.
o Select
the
filters
to
include
in
the
output.
o Select
‘Run
Report’.
The
report
will
pop
up
based
on
the
selected
parameters.
o Select
‘Close’
to
return
to
the
report
generator.

160. 160
Management
can
set
the
agency
and
Producer
goals
for
the
year.
o Management
enters
in
the
desired
overall
book
of
business
and
retention
rate.
o After
clicking
‘Calculate’,
the
required
new
business
to
meet
the
goals
will
appear.
Management
can
adjust
the
individual
goals
of
each
Producer.
o The
book
of
business
and/or
retention
rates
can
be
altered
manually
for
any
of
the
Producers
and
it
will
automatically
adjust
the
overall
goals.

161. 161
When
goals
reflect
desired
figures,
select
‘Save’
and
confirmation
of
set
goals
will
appear.

162. 162
VI.
Conclusion
Success
Criteria
Success
for
the
capstone
team
will
be
based
on
the
following
criteria:
• Team
Learning
-­‐
Upon
completion
of
the
project,
the
capstone
team
members
should
have
a
solid
understanding
of
the
following:
o Project
management
process
and
an
in-­‐depth
understanding
of
the
SDLC
o Learn
professional
communication
o Coordinate
between
multiple
teams
and
stakeholders
o Analyze
requirements
from
different
users
with
different
perspectives
o Manage
project
risks
effectively
o Deliver
quality
documents
consistently
• Sufficient
documentation
during
every
phase
of
project
implementation
and
during
the
handover
to
potential
future
users
&
project
team
members.
• The
satisfaction
of
SCU
Advisors.
• Team
Satisfaction
-­‐
In
addition
to
delivering
quality
work,
it
is
important
to
utilize
all
the
networking
opportunities
and
establish
strong
connection
with
the
staff.
• Individual
Commitment
-­‐
The
team
must
establish
the
culture
of
discipline
and
personal
accountability.
Team
members
must
take
ownership
of
their
respective
deliverables.
Future
Enhancements
There
were
so
many
other
paths
that
our
team
discussed
when
deciding
what
functionalities
to
include
in
our
system
but
we
ultimately
went
with
what
would
be
the
most
impactful
to
an
insurance
agency.
If
we
were
to
continue
working
on
the
system,
we
would
like
to
include
the
ability
to
track
and
train
new
Producers,
financial
transaction
management,
prospecting
tools
and
customer
service
reminders.
There
are
still
more
areas
we
could
cover,
but
these
would
likely
be
the
first
pieces
to
be
tackled.
The
new
Producer
tracking
and
training
element
would
consist
of
training
materials
as
well
as
weekly
checklists
to
be
filled
out
by
the
new
Producer
and
submitted
to
Management
for
review.

163. 163
The
Producers
have
to
make
a
certain
number
of
calls,
visits
and
other
prospecting
activities
in
order
to
get
the
ball
rolling.
Having
the
system
not
only
collect
this
information,
but
make
it
available
to
the
Manager
either
directly
in
the
system
or
in
a
report
would
greatly
benefit
both
the
Producer
and
Management.
Currently,
the
financial
transactions
are
housed
in
Lighthouse’s
main
system,
but
a
fully
functioning
system
would
not
be
complete
without
this
functionality.
It
would
track
payments
from
the
Client
and
Carrier
as
well
as
the
revenue
generated
by
a
Producer.
Bonuses
and
payroll
could
also
be
handled
in
the
system,
making
it
a
one-­‐stop
shop
for
employees
to
interface
with
their
Accounting
Department.
A
very
important
and
gaping
hole
in
the
system
currently
is
a
prospecting
tool.
This
piece
would
allow
for
the
tracking
of
prospects
in
the
system.
Any
potential
Client
that
gets
mailings,
calls
or
visits
can
be
tracked
here
as
well
as
if
the
Producer
quotes
the
business.
This
information
is
incredibly
important
for
the
Producers
and
Management
to
keep
track
of
year-­‐to-­‐year
on
the
activities
that
have
occurred
with
an
account.
It
can
also
keep
track
of
what
is
being
done
with
an
account
so
if
another
Producer
tries
to
solicit
the
same
account,
it
is
obvious
that
it
is
already
being
worked
on
by
a
different
Producer.
Again,
the
system
would
allow
Management
to
track
Producer
activity
as
well
as
run
reports.
Finally,
customer
service
is
an
important
part
of
the
agency’s
business.
It
is
extremely
important
to
keep
up
on
important
dates
as
well
as
to
provide
personalized
service
to
maintain
a
close
relationship
and
hopefully
keep
the
business
for
many
years.
This
element
of
the
system
would
remember
birthdays,
track
meetings
with
the
Client
and
provide
reminders
for
the
service
team
for
various
appointments.
Many
times,
the
relationship
the
Producer
and
Account
Managers
have
with
the
Clients
is
the
deciding
factor
when
it
comes
to
renewing
each
year.
If
we
were
able
to
design
and
implement
this
system
for
an
actual
company,
there
would
likely
be
other
small
details
to
change
or
enhance
to
customize
it
to
their
particular
needs.

164. 164
VII.
Appendix
Letter
from
Lighthouse
Management
There are many challenges facing agency owners and sales managers with
regard to managing sales people. Many have even referred to this as “herding cats” as it
relates to the many varying personalities and approaches to making a sale.
Obviously, at the end of the day, it is a matter of holding on to renewal revenue
and trying to grow organically at a rate of 12% and continually looking for acquisition
opportunities within a selected territory. Although new business growth is easy to
measure in terms of overall revenue to an agency, the difficulty lies in having to monitor
multiple sales people in different locations. This is also true for tracking new business
goals as each sales person has different goals based on their total book of business and
their experience level in the industry.
The challenge truly becomes making sure that each person is meeting their goals
and determining how they are getting there. In other words, is it new business directly,
cross – sold from a different department or an additional coverage added to an existing
account. By having a dashboard system that monitors this activity, it becomes much
more productive for not only the sales person being able to track what they’re writing, but
of equal importance is providing the sales manager a resource whereby they can
monitor multiple sales people to track their year-to-date results and determine if they are
on-track to meeting their annual goals.
With the creation of a Dashboard that reflects “real time” data, both the sales
person and sales manager can focus on the specifics of what activity needs to take
place in order for that person to get back on track or make adjustments to their business
plans. Instead of having to manually track the results, the dashboard will help the sales
people self-manage in order to stay on track. Truly a win-win situation.

165. 165
We are very excited to implement this system into our agency and look forward
to focusing on activities that will provide us with the greatest opportunities. There is no
doubt that this system will become an integral part of our agency operations and will
certainly help us to achieve our revenue goals and take us to the next level.
Michael J. Boros MBA, AAI
VICE PRESIDENT OF BUSINESS INSURANCE
D 616.455.9211 | P 800.344.3531 x7838
C 616.389.9167 | F 616.281.6218
4808 Broadmoor SE
Grand Rapids, Michigan 49512