BRD-VCCS SAMPLE.docx

Virginia Education Wizard Redesign & CMS ImplementationPrepared by: Amal ShankerProject Module : Workforce & VeteransProject ID: 2014002390 and 20140020128Module : CareersVersion: 2.00Revision Date: 10/20/2015

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.

Bus

ines

s R

equi

rem

ents

Spe

cific

atio

n

VCCS Wizard 4.0 RedesignBusiness Requirements Specification

Table of ContentsTABLE OF CONTENTS......................................................................................................................................................21 APPROVALS.................................................................................................................................................................4

1.01 CMS APPROVALS..................................................................................................................................................................41.02 WEB SITE APPROVALS...........................................................................................................................................................41.03 ADDITIONAL REVIEWERS........................................................................................................................................................5

2 DOCUMENT REVISION HISTORY...............................................................................................................................63 REFERENCES.............................................................................................................................................................. 7

3.01 PROJECT ARTIFACTS.............................................................................................................................................................73.02 CMS ARTIFACTS...................................................................................................................................................................73.03 PROJECT REPOSITORY...........................................................................................................................................................7

4 INTRODUCTION........................................................................................................................................................... 84.01 DOCUMENT PURPOSE.............................................................................................................................................................84.02 RESPONSIBILITY.....................................................................................................................................................................84.03 PROJECT OVERVIEW..............................................................................................................................................................84.04 CMS OVERVIEW....................................................................................................................................................................94.05 SCOPE.................................................................................................................................................................................104.06 TEAMMATE SSO OVERVIEW.................................................................................................................................................114.07 PROJECT IMPACTS...............................................................................................................................................................12

5 BUSINESS PROCESS MODEL..................................................................................................................................135.01 TO BE CONCEPTUAL DATA MODEL- CMS............................................................................................................................14

6 BUSINESS CONTEXT................................................................................................................................................ 156.01 DIAGRAM.............................................................................................................................................................................15

7 BUSINESS RULES & ASSUMPTIONS.......................................................................................................................167.01 BRUL.................................................................................................................................................................................167.02 ASSUMPTIONS......................................................................................................................................................................16

VCCS Project Methodology V2.0 Page 2 of 30 Updated: 10/20/2015document.docx Printed: 04/15/2014


8 CMS REQUIREMENTS............................................................................................................................................... 178.01 CMS - BUSINESS FUNCTIONAL REQUIREMENTS....................................................................................................................17

9 BUSINESS NON-FUNCTIONAL REQUIREMENTS...................................................................................................2410 USE CASE MODEL.....................................................................................................................................................26

10.01 ACTOR INVENTORY..............................................................................................................................................................2610.02 USE CASE INVENTORY.........................................................................................................................................................26

11 APPENDICES..............................................................................................................................................................2611.01 CONTRIBUTORS....................................................................................................................................................................2611.02 APPENDIX............................................................................................................................................................................2711.03 GLOSSARY...........................................................................................................................................................................28



1 ApprovalsThe Business Requirements Specification approval statements (i.e., electronic approval) are recorded in the project’s repository. The predefined roles below represent the required approvals for technology projects. Additional approvals may be mandated by the project.

1.01CMS ApprovalsName / Title Role

Chris Pfautz Project Business OwnerAndrew Farnsworth Workstream Manager (Cloud and Collaboration)Rachel Angel Wealth Business Solutions ManagerMarsha EES-PMO Program ManagerRam Dasari Senior Project ManagerSrini Sambangi Senryo-PMO Program Manager

1.02VCCS Wizard 4.0 Approvals

Name / Title RoleChris Pfautz Workstream Manager (PWM)Andrew Farnsworth Workstream Manager (Cloud and Collaboration)Rachel Angel Wealth Business Solutions ManagerRam Dasari Senior Program ManagerSrini Sambangi

SVP Manager of Wealth Solutions Group



1.03Additional Reviewers


Name / Title RoleLibby Bein EIS – Workstream Business AnalystJeff St. John PWM Manager, PWM Advisor Technology SolutionsRajesh Chouhan PWM Program Manager

Orianne Easley EIS – Workstream Business AnalystJanet Herndon Advisor Desktop- Project ManagerKapil Arya EIS-Solutions Architect PWM Workstream

EIS-Solutions Architect (Cloud & Collaboration)Scott Steib CSS Project ManagerRaveetha Parmeswaran Business AnalysisDeepika Bagai Test Manager


2 Document Revision History

Version Date Description of Version / Reason for Changes Author1.0 04/28/2014 Initial Version Amal Shanker2.0 06/02/2014 Updated per VCCS Wizard 4.0 Project Change Control #1. Removed

Advisor Release 3 and 4 from the CMS Migration projectLibby Bein



3 References

3.01Project ArtifactsThe following documents were used in the creation of the Business Requirements, and serve as supporting artifacts for the project.

3.02CMS ArtifactsDocument Name or Filename Author Document Date

Project Charter Ram Dasari 4/2014

Statement of Need VCCS 4/2014

3.03Project RepositoryProject artifacts are stored in the following repository locations.

Repository LocationProject SharePoint site



4 Introduction

4.01Document PurposeThis 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.02ResponsibilityIt is the responsibility of the Business Analyst, Business Client, and Project Team to develop and complete the Business Requirements Specification.

4.03Project 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:

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 student- counselor engagement

o Improve counselor- satisfaction resulting in increased retentiono 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 VCCS’s 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.04CMS Overview

The goal of this project is to migrate the existing PWM CMS system (Pivotal’s 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 PWM’s CMS system (InSite) with Advisor Desktop, which is being built on the LifeRayplatform.

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

PWM’s use of Pivotal’s 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.05Scope

Document

Name

Location

Project Charter

http://epr.suntrust.com/sites/pr2015/ST2014002390_Release1/Project%20Artifacts1/ST2014002390%20Project%20Charter%20CMS%20Migration%20v0.3.docx


http://epr.suntrust.com/sites/pr2013/ST2014002390_Release1/Project%20Artifacts1/ST2014002390%20Project%20Charter%20CRM%20Migration%20v0.3.docx

http://epr.suntrust.com/sites/pr2013/ST2014002390_Release1/Project%20Artifacts1/ST2014002390%20Project%20Charter%20CRM%20Migration%20v0.3.docx


4.05.01 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.05.02 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

4.06 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. 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 Veteran’s 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.

Ref # In-Scope Statement2. 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.

4. Delivery of the Architectural foundation for the 3 year Business Case roadmap to enable the LOB vision of integration.

Ref # Out-of-Scope Statement1. Deployment of any new LOB or Enterprise specific sign-on platform for application access by the Advisors

4.07Project Impacts

4.07.01 Business or Organizational and related ProcessesOrganization Impacted Processes Level of Impact

(L, M, H)Modifications expected

PWM LOB Sales and Client service processes H Streamlined application access, Data integration with an application, More centralized reporting capabilities,


http://epr.suntrust.com/sites/pr2010/ST2012001446_Release1/default.aspx


Organization Impacted Processes Level of Impact (L, M, H)

Modifications expected

TRAC New User set up and maintenance H The process for setting up users to access the Advisor Desktop will be owned by this group

Shared Services (increased functionality support)EIS support

Support model for PWM Advisor desktop

H More support for functionality of the Advisor desktop uses in PWM LOB.

4.07.02 CMS Application ImpactsWorkstream Application Impacted Level of Impact

(L, M, H)Modifications expected

PWM Advisor Desktop H Code changes to integrate within the Advisor desktop

Cloud & Collaboration Services

Salesforce H Development and configuration of CMS features

BIO BIO L Support for Hierarchy information.



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



6 Business Context

6.01Diagram



7 Business Rules & AssumptionsThe purpose of this section is to identify all of the Business Rules determined by the Business Requirements and Use Cases.

7.01BRUL ID Requirement Text Name Status Owner Traced-to

BRUL1 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.

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.02Assumptions ID Requirement Text Name Status Owner Traced-to

Assum1 The solution will follow all assumptions established in Release 1 and Release 2 of Advisor Desktop

R1 & R2 Assumptions

Assum2 The solution will render the CMS application page(s) inside the VCCS Wiz 4.0.

CMS Application Pages

Assum3 The solution shall store the data elements in the Oracle database as needed for performing CMS functionality

Data Storage

Assum4 The solution shall import data to the cloud for client search from the system of record or CMS or other designated applications

Data Import



ID Requirement Text Name Status Owner Traced-toAssum5 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

8 HOMEPAGE RequirementsThe purpose of this section is to identify all of the Business Requirements that flow from the approved list of Business Features.

8.01CMS - Business Functional Requirements

8.01.01 Account ManagementID Requirement Text Name Priority Status Use Case

1.01 Ability to link an account to only one Relationship. Link Account to Relationship

High

1.02 Ability to have several account forms with different layouts and fields depending upon account type

Multi Account Forms High

1.03 Ability to manually enter account data of accounts held away from SunTrust

External Held Accounts High

1.04 Integrate CIN number for a company based on TIN CIN Integration Low1.05 Ability to systematically link accounts to particular relationships

based on CIN or SS# or manually assign as needed.Account to Relationship Linking

low

8.01.02 Activity Management

ID Requirement Text Name Priority Status Use Case

2.00 View all activities and see a rollup of notes across an entire Relationship (Should follow same rules for security – I.e. Private cannot see)

Rollup of Accounts Medium




2.01 Assign tasks to teammates Task Assignment Low2.02 Incorporate URL and/or shared drive links in activities URL to Activities High2.03 Attach documents to activities and relationships Attach Documents High2.04 View the reminders (ticklers) that were initiated in the SEI system as a

reminder in SalesForceSEI Reminders Medium

2.05 Alerting capabilities of any activities generated on Relationships to be sent to all team members

Teammate Alert of Activities

Medium

8.01.03 Campaign Management


3.00 Ability to assign specific flags to Relationships based on certain corporate initiatives (i.e.. Annual classifications)

Assign Campaign to Relationship

High

3.01 manage my Campaign efforts Manage Campaign Medium3.02 Ability to create client Mailings. Client Mailings Medium3.03 Provide a tool for bulk emailing (for ADVs, Privacy policies, etc.) Balk Email tool Low3.04 Ability to create Labels for my client Mailings. Client Mailing Labels Low3.05 Produce reporting from my Campaign efforts. Report Campaign Efforts Medium

8.01.04 Chatter


4.00 Provide for Social networking and chat in accordance with Legal, Risk and Compliance

Social Networking Low



8.01.05 Contact Management


5.00 Displays similar contacts to a contact that I just entered into the system.

Similar Contact Display Medium

5.01 Integrate the CIN (and if applicable, household) number for an individual or relationship based on the TIN

CIN Integration Low

5.02 Create/maintain records for an individual (person) including various profile information (salary, hobbies, source of income, phone numbers, etc.)

Create Individual Profile High

5.03 Associate individual records to multiple Relationships based on defined purpose (i.e. Client, lawyer, accountant)

Associate Multiple Relationships

High

5.04 Enter a Lead Enter Lead Low5.05 enter a Prospect Enter Prospect Low5.06 Convert a Prospect to a Contact Convert Prospect to

ClientLow

5.07 Convert a Lead to a Contact Convert Lead to Client Low5.08 Convert a Lead to Relationship Convert Lead to

RelationshipMedium

5.09 Automated de-duping of contact data De-duping Contract Data Medium5.10 Display similar contacts to a contact that I just entered into the

system.Display Similar Contracts Medium

8.01.06 Data Import/Export


6.00 Load data via file in order to create records in the system Import From file Low6.01 Ability to import and export data via a file Import/Export Low



8.01.07 Document Management


7.00 Enable Document Management functionality Document Management Low7.01 Provide document storage capability Document Storage Low

8.01.08 Integration


8.00 Provide Advisor Desktop Integration Advisor Desktop Integration

Low

8.01 Ability to systematically link Relationships to CIS Household numbers or manually assign as needed.

Integrate Relationships to CIS Households

Low

8.01.09 Lead Management


9.00 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.

Manage Leads Medium

9.01 Ability to integrate with multiple "lead" sources and assign those to appropriate end user integrate from other sources., (Both referrals and system generated leads),

Multiple Lead Integration High

8.01.10 Mobile


10.00 Provide Mobile Capability that is compatible with Windows 8 platform and related devices

Mobile Capability Low




10.01 Utilize whatever internally sponsored Mobile technology available Mobile Application Integration

Low

8.01.11 Opportunity Management


11.00 Ability to create and manage multiple opportunities being worked for a relationship

Manage Multiple Opportunities

High

11.01 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.

Manage Sales Process Medium

8.01.12 Outlook Integration


12.00 Ability to use real Outlook integration (Calls, Tasks and emails) Outlook Integration Medium

8.01.13 Relationship Management


13.00 Manage client planning process (including the setting of the plan, reporting of past due plan and expectations, and presentation of plan)

Client Planning Process Medium

13.01 Manage relationships that are at risk of leaving the bank (reasons and actions taken to save)

At Risk Relationships Medium

13.02 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.)

Source of Records Identification

High

13.03 Provide ability to manage "enrollment process" of premier banking clients including the status and edit dates

Enrollment Process Management

High




13.04 Provide ability to merge Relationships and individual records under appropriate conditions and business rules

Merge Relationship Medium

13.05 Automate teammate assignment to Relationships based on account integration

Relationship Team Assignment

Medium

13.06 Ability to associate multiple Relationships to one another together with defined purpose (business connection, personal connection)

Multiple Relationships Association

High

13.07 Create and manage Relationships in customized manner (comingling households, business and personal accounts, etc.)

Customized Relationship Management

Medium

13.08 Preview complete Relationship Summary details (including overview of profile, client goals and expectations, accounts, activities and opportunities within a particular time frame)

Relationship Summary Details

Medium

13.9 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

Reassign Relationship Medium

13.10 See Contacts at the contact level. Contact Level View high13.11 Associate Contacts with Relationships Associate Contacts high13.12 See contacts at the Relationship level View Contacts High13.13 Provide 360 view of client based on linked account integration 360 Account View

IntegrationLow

13.14 Establish Relationship Teams: Establish Relationship Teams

Medium

13.15 see Relationship values at a Hierarchy Roll Up view Hierarchy Roll View Medium13.16 Assign a Wealth Band Service Level to a relationship Wealth Bank Service

LevelHigh

13.17 Assign a Specialty Industry to a contact and/or a relationship Specialty Industry High13.18 Ability to segment relationships (Type, Source of Wealth, Vertical

Strategy, Business, Personal, Mixed)Segmentation Low

13.19 Provide ability to merge Contacts and associated records under appropriate conditions and business rules

Merge Contacts High



8.01.14 ReportsID Requirement Text Name Priority Status Use Case

14.00 Enable management reporting and oversight as well as teammate access through pre-defined portals

Management Reporting Low

8.01.15 Search


15.00 Provide users with all user-facing fields as a query and reporting option

Search Results Query Options

Medium

15.01 Provide users all visible fields on all forms as possible column in search results for ad-hoc reporting

Search Results Ad hoc Reporting

Medium

15.02 Ability to query the CMS database and export the results of that query

Export Query Results High

15.03 Ability to query the CMS database and be able to query off all customized or configured data points.

Data Point Query Medium

15.04 View or search all associated accounts in a relationship or across business

View associates accounts Medium

15.05 Create searches, save and share pre-defined search filters to another user

Sharing Saved Searches Medium

15.06 Ability to create "work lists" (known as Static Lists in InSite) Work Lists Medium

8.01.16 Workflow & Templates


17.00 Incorporate PWM's TIP process in system. Includes TIP form, complex approval workflow, email generation based on workflow, report and separate TIP security group.

Incorporate TIP Process Medium

17.01 Create mass mailing relationships with mail merge functions Mass Mailing Medium




17.02 Ability to send a referral to another CMS user Send Referral Medium17.03 Ability to generate a set of reminders based on set pre-defined best

practices (i.e. birth, death, onboarding of new client, etc.)Generate Reminders Medium

17.04 Ability to create and document activities (Calls, Tasks, emails, letters, Reminders, etc.)

Document Activities High

17.05 Ability to create follow up activities with cloning of existing data from previous activity

Follow Up Activities Medium

17.06 Receive alerts based on new accounts being integrated or opened within Relationships

Receive Alerts for New Accounts

Medium

17.07 Provide access or alerts to Relationships not contacted Access Not Contacted Alerts

Medium

17.08 Provide alerts such as "Birthday" reminders Reminder Alerts Medium17.09 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.

Annual Plan for Book of Relationship

Medium

17.10 Create an Activity Master Plan Template Activity Master Plan Template

Medium

17.11 Provide ability for users to see overview of all planned activities for relationships.

Oversee Planned Activities

Medium

17.12 Ability to set Relationship level alerts when opening records Set Relationship Levels Medium



9 Business Non-functional Requirements 9.01.01 Insite

ID Requirement Text Name Priority Status OwnerUser 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

Insite Retirement

Conversion of CMS functionality

9.01.02 Data IntegrationID Requirement Text Name Priority Status Owner

Calls to external systems



10Use 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.01 Actor InventoryList of all the actors included in the model.

Actor ID Actor Description Actor Name Traced-toACT01 Primary: User of the Advisor Desktop. This will include the

multiple types of Advisors in the PWM line of business.PWM Advisor

ACT02 This will be the system or function that loads data into the Salesforce environment

Data transmission Device

10.02 Use Case Inventory

10.02.01 List of all use cases Proposed for CMS

To be provided as part of the SRS



11 Appendices

11.01 Contributors

Name Title/Department ContributionOrianne Easley Business Analyst /Application Services Requirements Elicitation & DocumentationMaryann Miller Business Analyst /Application Services Requirements Elicitation & DocumentationLibby Bein Workstream Business Analyst /Lead

Business Analyst Advisor Desktop Program

BRS Review/Minor updates to final

11.02 Appendix

11.02.01 Account Type Inclusion Matrix

Account Type PriorityType In Release 1 or 2 of Advisor Desktop



Account Type PriorityAnnuity Y

CD/IRA Y

Commercial Loan Y

Consumer Loan Y

Investment (Trust & Brokerage) Y

Deposit Y

Mortgage Y

Cards (Credit Cards) N

Insurance N

Letters of credit N

Leases N

Student Loan N

11.03 Glossary

Term DescriptionCMS 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.


http://en.wikipedia.org/wiki/Service_provider

http://en.wikipedia.org/wiki/Identity_provider

http://en.wikipedia.org/wiki/Authorization

http://en.wikipedia.org/wiki/Authentication

http://en.wikipedia.org/wiki/Open_standard

http://en.wikipedia.org/wiki/XML

