BRD-VCCS Sample

Business Requirements Specification
Virginia Education Wizard

Redesign & CMS
Implementation
Prepared by:
Project Module :
Project ID:
Amal Shanker
Workforce & Veterans
2014002390 and 20140020128
Module : Careers
Version: 2.00
Revision Date:
10/19/2015
VCCS Wizard 4.0 Redesign

Purpose: To capture and approve the Business Requirements of a project. Approval of this document
establishes the business requirements baseline. Any changes must then follow the Change Management
Process as defined by the VCCS Project Management Methodologies.
Table of Contents
TABLE OF CONTENTS........................................................................................................................................................2
1 APPROVALS...................................................................................................................................................................4
1.01
1.02
1.03
CMS APPROVALS................................................................................................................................................................ 4
WEB SITE APPROVALS........................................................................................................................................................ 4
ADDITIONAL REVIEWERS...................................................................................................................................................... 5
2 DOCUMENT REVISION HISTORY.................................................................................................................................6

3 REFERENCES.................................................................................................................................................................7
3.01
3.02
3.03
PROJECT ARTIFACTS........................................................................................................................................................... 7
CMS ARTIFACTS................................................................................................................................................................. 7
PROJECT REPOSITORY........................................................................................................................................................ 7
4 INTRODUCTION..............................................................................................................................................................8
4.01
4.02
4.03
4.04
4.05
4.06
4.07
DOCUMENT PURPOSE.......................................................................................................................................................... 8
RESPONSIBILITY.................................................................................................................................................................. 8
PROJECT OVERVIEW............................................................................................................................................................ 8
CMS OVERVIEW.................................................................................................................................................................. 9
SCOPE.............................................................................................................................................................................. 10
TEAMMATE SSO OVERVIEW............................................................................................................................................... 11
PROJECT IMPACTS............................................................................................................................................................. 12
5 BUSINESS PROCESS MODEL....................................................................................................................................13

5.01
TO BE CONCEPTUAL DATA MODEL- CMS.......................................................................................................................... 14
6 BUSINESS CONTEXT...................................................................................................................................................15
VCCS Project Methodology V2.0
298010059
Page 2 of 35
Printed: 04/15/2014
Updated: 10/19/2015

6.01
DIAGRAM.......................................................................................................................................................................... 15
7 BUSINESS RULES & ASSUMPTIONS.........................................................................................................................16

7.01
7.02
BRUL.................................................................................................................................................................................16
ASSUMPTIONS................................................................................................................................................................... 16
8 CMS REQUIREMENTS.................................................................................................................................................17
8.01
CMS - BUSINESS FUNCTIONAL REQUIREMENTS.................................................................................................................. 17
9 BUSINESS NON-FUNCTIONAL REQUIREMENTS.....................................................................................................24

10 USE CASE MODEL.......................................................................................................................................................26
10.01 ACTOR INVENTORY............................................................................................................................................................ 26
10.02 USE CASE INVENTORY....................................................................................................................................................... 26
11 APPENDICES................................................................................................................................................................26
11.01 CONTRIBUTORS................................................................................................................................................................. 26
11.02 APPENDIX......................................................................................................................................................................... 27
11.03 GLOSSARY........................................................................................................................................................................ 28

298010059
Page 3 of 35
Printed: 04/15/2014
Updated: 10/19/2015

1 Approvals
The Business Requirements Specification approval statements (i.e., electronic approval) are recorded in the
projects repository. The predefined roles below represent the required approvals for technology projects.
Additional approvals may be mandated by the project.
1.1
CMS Approvals
Chris Pfautz
Name / Title
Role
Project Business Owner
Andrew Farnsworth
Workstream Manager (Cloud and Collaboration)
Rachel Angel
Wealth Business Solutions Manager
Marsha
EES-PMO Program Manager
Ram Dasari
Senior Project Manager
Srini Sambangi
Senryo-PMO Program Manager
1.2
VCCS Wizard 4.0 Approvals
Name / Title
Chris Pfautz
Role
Workstream Manager (PWM)
Andrew Farnsworth
Workstream Manager (Cloud and Collaboration)

298010059
Page 4 of 35
Printed: 04/15/2014
Updated: 10/19/2015

Rachel Angel
Name / Title
Role
Wealth Business Solutions Manager
Ram Dasari
Senior Program Manager
Srini Sambangi
SVP Manager of Wealth Solutions Group
1.3
Additional Reviewers
Name / Title
Libby Bein
Role
EIS Workstream Business Analyst
Jeff St. John
PWM Manager, PWM Advisor Technology

Solutions
Rajesh Chouhan
Orianne Easley
PWM Program Manager

EIS Workstream Business Analyst
Janet Herndon
Advisor Desktop- Project Manager
Kapil Arya
EIS-Solutions Architect PWM Workstream

EIS-Solutions Architect (Cloud & Collaboration)
Scott Steib
Raveetha Parmeswaran
Deepika Bagai
298010059
CSS Project Manager

Business Analysis
Test Manager
Page 5 of 35
Printed: 04/15/2014
Updated: 10/19/2015

2 Document Revision History

Version
1.0
Date
04/28/201
4
Description of Version / Reason for Changes

Initial Version
Author
Amal Shanker
2.0
06/02/201
4
Updated per VCCS Wizard 4.0 Project Change Control #1.

Removed Advisor Release 3 and 4 from the CMS Migration project
Libby Bein

298010059
Page 6 of 35
Printed: 04/15/2014
Updated: 10/19/2015

3 References
3.1
Project Artifacts
The following documents were used in the creation of the Business Requirements, and serve as supporting
artifacts for the project.
3.2
CMS Artifacts
Document Name or Filename

Project Charter
Author
Ram Dasari
Document Date
4/2014
Statement of Need
VCCS
4/2014
3.3
Project Repository
Project artifacts are stored in the following repository locations.

Repository
Project SharePoint
site

298010059
Location
Page 7 of 35
Printed: 04/15/2014
Updated: 10/19/2015

4 Introduction
4.1
Document Purpose
This document identifies the business requirements of the VCCS Wizard 4.0 and CMS Implementation (Release
3 & 4). Approval of this document:
Ensures that the Business Clients and the Project Team have a common understanding of the business
requirements.
Serves as the business requirements baseline which signifies the start of the Change Management process
for any additions or deletions to the baseline business requirements.
Forms the foundation for System Requirements, Project Planning, architecture and design, and other project
related activities.
The Business Requirements Specification is iterative and will go through multiple Business Client and Project
Team reviews to ensure all business requirements have been captured. All business and system requirements
must be approved prior to commencement of any design documentation.
4.2
Responsibility
It is the responsibility of the Business Analyst, Business Client, and Project Team to develop and complete the
Business Requirements Specification.
4.3
Project Overview
In 2009, Virginia Education WIzard was originally released to ensure that the student success inititatives were
successfully met. In 2014, VCCS collaborated with Hodges Digital on a 9-week study of the current Virginia
Wizard 4.0 website, tools and technology.
This engagement was the foundational step in a commencing a transformation initiative.Senryo and Hodges
Digital Technologies intends to provide best in class tools and capabilities to its financial advisors in order to:

298010059
Page 8 of 35
Printed: 04/15/2014
Updated: 10/19/2015

o Optimize process efficiencies through automation and seamless application integration facilitating
enhanced user experience and elimination of redundant activities
o Provide superior counselor relationship management, student service activities, and increased studentcounselor engagement
o Improve counselor- satisfaction resulting in increased retention
o The analysis conducted with Hodges Digital revealed that VCCS Wizard 4.0 provides over 80% of
functionality that are typically available in other Student Universities Websites, however, less than 25% of
the functionality provided is optimized for the student's user, due to lack of a cohesive navigation
architecture, data integration and context passing between the applications, and underlying workflow
components.
o The result of the Hodges Digital engagement was a Senryo Technologies' strategy to supplement and
expand upon VCCSs existing technology roadmap for VCCS Wiz 4.0.
A business case for a two-year program for VCCS Wizard 4.0 Redesign & Integrated Content Management
System Implementation (PROG2012000406) was prepared and approved for funding. This project charter
covers the first phase (2015) of the enhancements to the VCCS Wiz 4.0.
The Wizard is to be redesigned and rebuitl to use modern UX designs, technologies and Interfaces. The goals
are to recreate current functiolnality while adding new features.
In addition the site will be revamped to provide for modern look and feel while providing better adaptation to
support mobile devices.
4.4
CMS Overview
The goal of this project is to migrate the existing PWM CMS system (Pivotals InSite) to the LifeRayplatform, (including
data & business functionality) and provide the CMS business functionality through the Advisor Desktop application.
A key outcome of the CapGemini assessment conducted in 2014, which led to the Integrated Advisor Desktop program,
was that SunTrust needs a CMS-centric Advisor Desktop. The go-forward position was to integrate PWMs CMS system
(InSite) with Advisor Desktop, which is being built on the LifeRayplatform.

298010059
Page 9 of 35
Printed: 04/15/2014
Updated: 10/19/2015

In July 2015, PWM conducted a CMS Strategic Assessment to determine the best path forward, given the following:
CMS technology is a critical component in executing and managing the highly customized sales and relationship
management processes of PWM
PWMs use of Pivotals InSite CMS application (10 yrs.)
CMS & Advisor Desktop software need to be highly integrated to support a CMS-centric Advisor Desktop
The assessment analyzed two options:
1. Integrate Insite with Advisor Desktop, or
2. Migrate InSite to Salesforce.com
The decision was made to redesign VCCS Wizard 4.0 website and implement the LifeRay platform after assessing
LifeRay and In-Site across 5 key areas and concluding that LifeRay scored higher overall:
Fits with Strategic Needs (favorable)
Critical Functionality (same)
Vendor Assessment (favorable)
Ongoing Operating Costs (favorable)
Speed to Market for Ongoing Enhancements (favorable)
It was also concluded that the cost to migrate to LifeRayvs. integrating with InSite was essentially the same.
4.5

298010059
Scope
Page 10 of 35
Printed: 04/15/2014
Updated: 10/19/2015

Docum
ent
Name
Project
Charte
r
Location
http://epr.suntrust.com/sites/pr2015/ST2014002390_Release1/Project%20Artifacts1/ST2014002390%20Project
%20Charter%20CMS%20Migration%20v0.3.docx
4.5.1 In Scope - CMS
Implementation of CMS from Insite to LifeRay platform
Migrate CMS functions that are currently in InSite in keeping with the 75 key capabilities covered in the
July 2015 CMS Strategic Assessment.
Changes getting deployed through in-flight projects such as InSite Periodic Release and CIS
Migration of historical CMS data from InSite to LifeRay and developing a process to handle historical
documents/attachments from InSite as well as new documents/attachments is included.
4.5.2 Out of Scope
Additional account types (other than documented in this BRS)

New functionality requiring customization (new means not included in the July 2015 Hodges Digital CMS
Strategic Assessment, not new relative to existing InSite functionality)
Decommissioning of InSite will be a separate project.
Updates to existing interfaces and new interfaces to/from applications not currently interfaced to InSite

298010059
Page 11 of 35
Printed: 04/15/2014
Updated: 10/19/2015

4.6
Wizard 4.0 Overview
Wizard Homepage
The wizard homepage provides a brief description of site's purpose and functionalities. Homepage
provides links to following content landing pages: Careers, College Planner, Paying for College, Parent
Info, Transfer, Apply Now and Veterans.
Within the homepage, there is a map of state of Virginia, with markers and links to information about each
college in the state. Other items include the site avatar 'Ginny' ( Licensed through Codebaby), Wizard
logo and direct the link to the new Veteran's resources page.
Wizard 'Careers' Landing Page
This landing page has links to the three career assessments housed in the Wizard.
The assessments are the Interest Assessment, Values Assessment and Skills Assessment.
Another important functionality in the Careers section of the site is the Search Careers section for users.
Users have the ability to find careers through completing assessments or they can search for careers
alphabetically, by career cluster or by career pathway.
The search careers alphabetically should allow smart search so a user can scroll alphabetically or type
in the occupation they are seeking.

298010059
Page 12 of 35
Printed: 04/15/2014
Updated: 10/19/2015

This section of the site also includes a Resume Builder, a section on interview tips and information, a
section on Work-based learning and apprenticeships and the Veterans Career Finder. All of these
resources will remain in the site in largely the same format, with some minor text and functional
adjustments.
For this section, specific careers displayed are from the federal ONET database.
Alll careers have an Occupational Profile page associated with them that contains general description,
salary, job outlook, education required, top employers and skills and attributes. Careers are mapped into
Career Clusters. Logged in users can store occupations of interest by clicking Add and storing
occupations to their profile.
There are a number of standards which exist for web single sign on including WS-Federation, OpenID and Security
Assertion Markup Language (SAML). The current mainstream approach to web single sign on in the enterprise
space is SAML. Security Assertion Markup Language (SAML) enjoys the dominant position in terms of industry
acceptance and production federated identity deployments. SAML is deployed in tens of thousands of Cloud Single
Sign-On (SSO) connections, and thousands of large enterprises, government agencies and service providers have
selected it as their standard protocol for communicating identities across the Internet.

298010059
Page 13 of 35
Printed: 04/15/2014
Updated: 10/19/2015

Ref #
2.
4.
In-Scope Statement
Development of a landing page or integrated front end to enhance Advisor navigation to
the various applications within the desktop along a defined Sales Process (see EIS
SharePoint Site for the Business Requirements defining the Sales Process). This Landing
Page shall be a direct replacement of the Advisor sub-navigation from the WIM Business
Tools Page and incorporate all applications that lie within the defined Sales Process and
support tools that make up the remainder of the Advisor sub-navigation. For the purposes
of this project, data integration shall be limited to Source and Target systems along the
Sales Process providing existing data for presentation either as LOB-facing or through
entitlement-based access rights as defined by SunTrust.
Delivery of the Architectural foundation for the 3 year Business Case roadmap to enable the
LOB vision of integration.
Ref #
1.

298010059
Out-of-Scope Statement
Deployment of any new LOB or Enterprise specific sign-on platform for application access
by the Advisors
Page 14 of 35
Printed: 04/15/2014
Updated: 10/19/2015

4.7
Project Impacts
4.7.1 Business or Organizational and related Processes

Organization Impacted
Processes
Level of Impact
(L, M, H)
H
Modifications expected
PWM LOB
Sales and Client service

processes
Streamlined application access,

Data integration with an
application, More centralized
reporting capabilities,
TRAC
New User set up and

maintenance
The process for setting up users

to access the Advisor Desktop will
be owned by this group
Shared Services
(increased functionality
support)
Support model for PWM Advisor

desktop
More support for functionality of

the Advisor desktop uses in PWM
LOB.
EIS support
4.7.2 CMS Application Impacts

Workstream
PWM

298010059
Application Impacted
Advisor Desktop
Level of Impact
(L, M, H)
H
Page 15 of 35
Printed: 04/15/2014
Code changes to integrate within
the Advisor desktop
Updated: 10/19/2015

Workstream
Cloud & Collaboration
Services
Salesforce
Level of Impact
(L, M, H)
H
BIO
BIO

298010059
Application Impacted
Page 16 of 35
Printed: 04/15/2014
Development and configuration of
CMS features
Support for Hierarchy information.
Updated: 10/19/2015

5 Business Process Model ( As Is High Level Workflow Diagram)

298010059
Page 17 of 35
Printed: 04/15/2014
Updated: 10/19/2015


298010059
Page 18 of 35
Printed: 04/15/2014
Updated: 10/19/2015


298010059
Page 19 of 35
Printed: 04/15/2014
Updated: 10/19/2015

6 Business Context
6.1

298010059
Diagram
Page 20 of 35
Printed: 04/15/2014
Updated: 10/19/2015

7 Business Rules & Assumptions

The purpose of this section is to identify all of the Business Rules determined by the Business Requirements and
Use Cases.
7.1
BRUL
ID
BRUL1
Requirement Text
The solution will comply with all VCCS mandated policies
and procedures as well as any Student Service industry
regulatory/compliance regulations as it relates to client data.
This relates to the viewing, accessing, sharing of data or use
of data in any manner.
Name
STI Mandated
Policies
Compliance
BRUL2
The solution will follow all business rules established in

Release 1 and Release 2 of VCCS 4.0
R1 and R2
Business Rules
BRUL3
The solution shall provide the capability to perform CMS

functionality using data obtained from the correct source (as
identified collaboratively amongst the project Stakeholders)
Source of CMS
Data
7.2
Owner
Traced-to
Status
Owner
Traced-to
Assumptions
ID
Assum
1
Requirement Text
The solution will follow all assumptions established in
Release 1 and Release 2 of Advisor Desktop
Name
R1 & R2
Assumptions
Assum
2
The solution will render the CMS application page(s) inside

the VCCS Wiz 4.0.
CMS Application
Pages

298010059
Status
Page 21 of 35
Printed: 04/15/2014
Updated: 10/19/2015

ID
Assum
3
Requirement Text
The solution shall store the data elements in the Oracle
database as needed for performing CMS functionality
Name
Data Storage
Assum
4
The solution shall import data to the cloud for client search
from the system of record or CMS or other designated
applications
Data Import
Assum
5
The solution shall provide the capability to configure role

hierarchies as needed. This will adhere to corporate
risk/compliance guidelines as noted above.
Roles &
Hierarchies
Status
Owner
Traced-to
8 HOMEPAGE Requirements
The purpose of this section is to identify all of the Business Requirements that flow from the approved list of
Business Features.
8.1
CMS - Business Functional Requirements
8.1.1 Account Management

ID
1.01
Requirement Text
Ability to link an account to only one Relationship.
1.02
Ability to have several account forms with different

layouts and fields depending upon account type
Ability to manually enter account data of accounts
held away from SunTrust
Integrate CIN number for a company based on TIN
Ability to systematically link accounts to particular
relationships based on CIN or SS# or manually assign
as needed.
1.03
1.04
1.05

298010059
Name
Link Account to
Relationship
Multi Account Forms
Priority
High
External Held
Accounts
CIN Integration
Account to
Relationship Linking
High
Page 22 of 35
Printed: 04/15/2014
Status
Use Case
High
Low
low
Updated: 10/19/2015

8.1.2 Activity Management

ID
2.00
2.01
2.02
2.03
2.04
2.05
Requirement Text
Name
View all activities and see a rollup of notes across an

entire Relationship (Should follow same rules for
security I.e. Private cannot see)
Assign tasks to teammates
Incorporate URL and/or shared drive links in activities
Attach documents to activities and relationships
View the reminders (ticklers) that were initiated in the
SEI system as a reminder in SalesForce
Alerting capabilities of any activities generated on
Relationships to be sent to all team members
Priority
Rollup of Accounts
Medium
Task Assignment
URL to Activities
Attach Documents
SEI Reminders
Low
High
High
Medium
Teammate Alert of
Activities
Medium
Status
Use
Case
Status
Use
Case
8.1.3 Campaign Management

ID
3.00
3.01
3.02
3.03
3.04
3.05
Requirement Text
Name
Ability to assign specific flags to Relationships based on

certain corporate initiatives (i.e.. Annual classifications)
manage my Campaign efforts
Ability to create client Mailings.
Provide a tool for bulk emailing (for ADVs, Privacy
policies, etc.)
Ability to create Labels for my client Mailings.
Produce reporting from my Campaign efforts.
Assign Campaign to
Relationship
Manage Campaign
Client Mailings
Balk Email tool
High
Client Mailing Labels

Report Campaign
Efforts
Low
Medium

298010059
Page 23 of 35
Printed: 04/15/2014
Priority
Medium
Medium
Low
Updated: 10/19/2015

8.1.4 Chatter
ID
4.00
Requirement Text
Name
Provide for Social networking and chat in accordance

with Legal, Risk and Compliance
Social Networking
Priority
Status
Use
Case
Status
Use
Case
Low
8.1.5 Contact Management

ID
5.00
Requirement Text
Name
5.04
5.05
5.06
Displays similar contacts to a contact that I just entered

into the system.
Integrate the CIN (and if applicable, household) number
for an individual or relationship based on the TIN
Create/maintain records for an individual (person)
including various profile information (salary, hobbies,
source of income, phone numbers, etc.)
Associate individual records to multiple Relationships
based on defined purpose (i.e. Client, lawyer,
accountant)
Enter a Lead
enter a Prospect
Convert a Prospect to a Contact
5.07
Convert a Lead to a Contact
5.08
Convert a Lead to Relationship
5.09
Automated de-duping of contact data
5.01
5.02
5.03

298010059
Priority
Similar Contact
Display
CIN Integration
Medium
Create Individual
Profile
High
Associate Multiple
Relationships
High
Enter Lead
Enter Prospect
Convert Prospect to
Client
Convert Lead to
Client
Convert Lead to
Relationship
De-duping Contract
Data
Low
Low
Low
Page 24 of 35
Printed: 04/15/2014
Low
Low
Medium
Medium
Updated: 10/19/2015

ID
5.10
Requirement Text
Name
Display similar contacts to a contact that I just entered

into the system.
Display Similar
Contracts
Priority
Status
Use
Case
Status
Use
Case
Status
Use
Case
Status
Use
Case
Medium
8.1.6 Data Import/Export

ID
6.00
6.01
Requirement Text
Name
Load data via file in order to create records in the

system
Ability to import and export data via a file
Priority
Import From file
Low
Import/Export
Low
8.1.7 Document Management

ID
Requirement Text
7.00
Enable Document Management functionality
7.01
Provide document storage capability
Name
Document
Management
Document Storage
Priority
Low
Low
8.1.8 Integration
ID
Requirement Text
Name
8.00
Provide Advisor Desktop Integration
8.01
Ability to systematically link Relationships to CIS

Household numbers or manually assign as needed.

298010059
Advisor Desktop
Integration
Integrate
Relationships to CIS
Households
Page 25 of 35
Printed: 04/15/2014
Priority
Low
Low
Updated: 10/19/2015

8.1.9 Lead Management

ID
9.00
9.01
Requirement Text
Name
Ability for assigned user to search, review and

disposition leads to either disregard lead or go through
process of creation new contact and/or relationship.
Ability to integrate with multiple "lead" sources and
assign those to appropriate end user integrate from
other sources., (Both referrals and system generated
leads),
Priority
Manage Leads
Medium
Multiple Lead
Integration
High
Status
Use
Case
Status
Use
Case
Status
Use
Case
8.1.10 Mobile
ID
10.00
10.01
Requirement Text
Name
Provide Mobile Capability that is compatible with

Windows 8 platform and related devices
Utilize whatever internally sponsored Mobile technology
available
Priority
Mobile Capability
Low
Mobile Application
Integration
Low
8.1.11 Opportunity Management

ID
11.00
11.01
Requirement Text
Name
Ability to create and manage multiple opportunities

being worked for a relationship
Ability to manage/report sales process (including
pipeline) based on product category, sales stage, and
expected sales date, won date, opportunity size,
probability and organizational hierarchy.

298010059
Manage Multiple
Opportunities
Manage Sales
Process
Page 26 of 35
Printed: 04/15/2014
Priority
High
Medium
Updated: 10/19/2015

8.1.12 Outlook Integration
ID
12.00
Requirement Text
Name
Ability to use real Outlook integration (Calls, Tasks and

emails)
Outlook Integration
Priority
Status
Use
Case
Status
Use
Case
Medium
8.1.13 Relationship Management

ID
13.00
13.01
13.02
13.03
13.04
13.05
13.06
13.07
13.08
Requirement Text
Name
Manage client planning process (including the setting of

the plan, reporting of past due plan and expectations,
and presentation of plan)
Manage relationships that are at risk of leaving the bank
(reasons and actions taken to save)
Provide ability to identify source of records from a sales
and relationship management perspective (i.e. sources
would include client, LOB lead, center of influence, etc.)
Provide ability to manage "enrollment process" of
premier banking clients including the status and edit
dates
Provide ability to merge Relationships and individual
records under appropriate conditions and business rules
Automate teammate assignment to Relationships based
on account integration
Ability to associate multiple Relationships to one
another together with defined purpose (business
connection, personal connection)
Create and manage Relationships in customized manner
(comingling households, business and personal
accounts, etc.)
Preview complete Relationship Summary details
(including overview of profile, client goals and
expectations, accounts, activities and opportunities
within a particular time frame)

298010059
Priority
Client Planning
Process
Medium
At Risk Relationships
Medium
Source of Records
Identification
High
Enrollment Process
Management
High
Merge Relationship
Medium
Relationship Team
Assignment
Multiple
Relationships
Association
Customized
Relationship
Management
Relationship
Summary Details
Medium
Page 27 of 35
Printed: 04/15/2014
High
Medium
Medium
Updated: 10/19/2015

ID
13.9
Requirement Text
Name
13.14
Ability to reassign relationships and all of its linked

records (defined criteria for which linked records to
reassign) or books of business based on teammate
changes
See Contacts at the contact level.
Associate Contacts with Relationships
See contacts at the Relationship level
Provide 360 view of client based on linked account
integration
Establish Relationship Teams:
13.15
13.16
see Relationship values at a Hierarchy Roll Up view

Assign a Wealth Band Service Level to a relationship
13.17
Assign a Specialty Industry to a contact and/or a

relationship
Ability to segment relationships (Type, Source of Wealth,
Vertical Strategy, Business, Personal, Mixed)
Provide ability to merge Contacts and associated
records under appropriate conditions and business rules
13.10
13.11
13.12
13.13
13.18
13.19
Priority
Reassign
Relationship
Medium
Contact Level View

Associate Contacts
View Contacts
360 Account View
Integration
Establish
Relationship Teams
Hierarchy Roll View
Wealth Bank Service
Level
Specialty Industry
high
high
High
Low
Segmentation
Low
Merge Contacts
High
Name
Management
Reporting
Priority
Low
Status
Use
Case
Medium
Medium
High
High
8.1.14 Reports
ID
14.00
Requirement Text
Enable management reporting and oversight as well as
teammate access through pre-defined portals

298010059
Page 28 of 35
Printed: 04/15/2014
Status
Use Case
Updated: 10/19/2015

8.1.15 Search
ID
15.00
15.01
15.02
15.03
15.04
15.05
15.06
Requirement Text
Name
Provide users with all user-facing fields as a query and

reporting option
Provide users all visible fields on all forms as possible
column in search results for ad-hoc reporting
Ability to query the CMS database and export the
results of that query
Ability to query the CMS database and be able to query
off all customized or configured data points.
View or search all associated accounts in a relationship
or across business
Create searches, save and share pre-defined search
filters to another user
Ability to create "work lists" (known as Static Lists in
InSite)
Priority
Search Results
Query Options
Search Results Ad
hoc Reporting
Export Query
Results
Data Point Query
Medium
View associates
accounts
Sharing Saved
Searches
Work Lists
Medium
Status
Use
Case
Status
Use
Case
Medium
High
Medium
Medium
Medium
8.1.16 Workflow & Templates

ID
17.00
17.01
17.02
17.03
Requirement Text
Name
Incorporate PWM's TIP process in system. Includes TIP

form, complex approval workflow, email generation
based on workflow, report and separate TIP security
group.
Create mass mailing relationships with mail merge
functions
Ability to send a referral to another CMS user
Ability to generate a set of reminders based on set predefined best practices (i.e. birth, death, onboarding of
new client, etc.)

298010059
Priority
Incorporate TIP
Process
Medium
Mass Mailing
Medium
Send Referral
Generate
Reminders
Medium
Medium
Page 29 of 35
Printed: 04/15/2014
Updated: 10/19/2015

ID
17.04
17.05
17.06
17.07
17.08
17.09
17.10
17.11
17.12
Requirement Text
Name
Ability to create and document activities (Calls, Tasks,

emails, letters, Reminders, etc.)
Ability to create follow up activities with cloning of
existing data from previous activity
Receive alerts based on new accounts being integrated
or opened within Relationships
Provide access or alerts to Relationships not contacted
Provide alerts such as "Birthday" reminders
Create an annual plan of activities for an entire book of
relationships and define the time frame which generates
and pushes reminders to end users. Provide ability for
users to see overview of all planned activities for
relationships.
Create an Activity Master Plan Template
Provide ability for users to see overview of all planned
activities for relationships.
Ability to set Relationship level alerts when opening
records
Priority
Document
Activities
Follow Up Activities
High
Receive Alerts for

New Accounts
Access Not
Contacted Alerts
Reminder Alerts
Annual Plan for
Book of
Relationship
Medium
Activity Master Plan

Template
Oversee Planned
Activities
Set Relationship
Levels
Medium
Status
Use
Case
Medium
Medium
Medium
Medium
Medium
Medium
9 Business Non-functional Requirements

9.1.1 Insite
ID
Requirement Text
User access to the Insite application will be deactivated when
CMS functionality goes live. However the DB and all related jobs
will remain in place and active

298010059
Page 30 of 35
Printed: 04/15/2014
Name
Insite
Retirement
Priority
Status
Owner
Updated: 10/19/2015

ID
Requirement Text
Conversion of CMS functionality
Name
Priority
Status
Owner
Name
Priority
Status
Owner
9.1.2 Data Integration

ID
Requirement Text
Calls to external systems

298010059
Page 31 of 35
Printed: 04/15/2014
Updated: 10/19/2015

10 Use Case Model

The purpose of this section is to define the use case model for those projects that have included use cases in their
Requirements Approach.
10.1
Actor Inventory
List of all the actors included in the model.

Actor ID
ACT01
Actor Description
Primary: User of the Advisor Desktop. This will include
the multiple types of Advisors in the PWM line of
business.
Actor Name
PWM Advisor
ACT02
This will be the system or function that loads data into

the Salesforce environment
Data transmission
Device
10.2
Traced-to
Use Case Inventory
10.2.1 List of all use cases Proposed for CMS

To be provided as part of the SRS

298010059
Page 32 of 35
Printed: 04/15/2014
Updated: 10/19/2015

11 Appendices
11.1
Contributors
Name
Orianne Easley
Title/Department
Business Analyst /Application
Services
Contribution
Requirements Elicitation & Documentation
Maryann Miller
Business Analyst /Application Services
Requirements Elicitation & Documentation
Libby Bein
Workstream Business Analyst /Lead

Business Analyst Advisor Desktop
Program
BRS Review/Minor updates to final
11.2
Appendix
11.2.1 Account Type Inclusion Matrix

298010059
Page 33 of 35
Printed: 04/15/2014
Updated: 10/19/2015

Account Type
Priority
Type
In Release 1 or 2 of Advisor Desktop
Annuity
CD/IRA
Commercial Loan
Consumer Loan
Investment (Trust & Brokerage)
Deposit
Mortgage
Cards (Credit Cards)
Insurance
Letters of credit
Leases
Student Loan

298010059
Page 34 of 35
Printed: 04/15/2014
Updated: 10/19/2015

11.3
Glossary
Term
Description
CMS
Customer Relations Management
SAML (Security
Assertion Markup
Language)
XML-based open standard data format for exchanging authentication and authorization data between
parties, in particular, between an identity provider and a service provider.
Web Service
Mechanisms by which two applications can easily exchange data over the Internet, even if they run on
different platforms, are written in different languages, or are geographically remote from each other.
WebSSO
The SunTrust internal Interface that manages the SAML 2.0 applications authentication process.

298010059
Page 35 of 35
Printed: 04/15/2014
Updated: 10/19/2015

BRD-VCCS Sample

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BRD-VCCS Sample

Uploaded by

Copyright:

Available Formats

Business Requirements Specification

Virginia Education Wizard

Workforce & Veterans

2014002390 and 20140020128

VCCS Wizard 4.0 Redesign

2 DOCUMENT REVISION HISTORY.................................................................................................................................6

5 BUSINESS PROCESS MODEL....................................................................................................................................13

TO BE CONCEPTUAL DATA MODEL- CMS.......................................................................................................................... 14

VCCS Wizard 4.0 Redesign

7 BUSINESS RULES & ASSUMPTIONS.........................................................................................................................16

CMS - BUSINESS FUNCTIONAL REQUIREMENTS.................................................................................................................. 17

9 BUSINESS NON-FUNCTIONAL REQUIREMENTS.....................................................................................................24

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

Workstream Manager (Cloud and Collaboration)

Wealth Business Solutions Manager

EES-PMO Program Manager

Senior Project Manager

Senryo-PMO Program Manager

VCCS Wizard 4.0 Approvals

Workstream Manager (Cloud and Collaboration)

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

Senior Program Manager

Jeff St. John

PWM Manager, PWM Advisor Technology

PWM Program Manager

Advisor Desktop- Project Manager

EIS-Solutions Architect PWM Workstream

CSS Project Manager

VCCS Wizard 4.0 Redesign

2 Document Revision History

Description of Version / Reason for Changes

Updated per VCCS Wizard 4.0 Project Change Control #1.

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

Document Name or Filename

Project artifacts are stored in the following repository locations.

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

4.5.1 In Scope - CMS

Implementation of CMS from Insite to LifeRay platform

4.5.2 Out of Scope

Additional account types (other than documented in this BRS)

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

Wizard 4.0 Overview

Wizard 'Careers' Landing Page

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

VCCS Project Methodology V2.0

VCCS Wizard 4.0 Redesign

4.7.1 Business or Organizational and related Processes

Sales and Client service