Wells Fargo TM CMS (Treasury Management Customer Management System) MIS Group 12

Transcription

1 Wells Fargo TM CMS (Treasury Management Customer Management System) MIS Group 12 Group Members: Arindam Bhattacharya (Project Manager) Jose Romero Amer Homsi Ameen Syed Guled Dalmar

2 Table of Contents 1. Introduction 1.1. Executive Summary (Page 1) 1.2. Problem Statement (Page 2) 2. Existing System 2.1. Interface (Pages 3-6) 2.2. Architecture (Page 6) 2.3. Context Diagram (Page 6) 2.4. Use Case Diagram (Page 7) 2.5. Use Case Descriptions (Pages 7-10) 3. Proposed System 3.1. Interface (Pages 11-12) 3.2. Architecture (Page 12) 3.3. Context Diagram (Page 13) 3.4. Use Case Diagram (Page 13) 3.5. Use Case Descriptions (Page 14) 3.6. Data Dictionary (Page 15) 3.7. Data Model/Class Diagram (Page 16) 3.8. Object Behavior Model (Page 17) 3.9. Complete Class Diagram (Classes + Methods) (Page 18) Database Design (Page 19) Software Design (Page 20-22) System Controls (Page 23) Functional Specification Document (Page 23) 4. Project Management 4.1. Project Activities (Page 24) 4.2. Allocation of Activities to Team Members (Page 24-25) 4.3. Planned Timeline (Page 25) 4.4. Executed Timeline (Page 25) 4.5. Minutes of Project Meetings (Page 26) 5. Presentation link (Page 27)

3 Introduction 1.1. Executive Summary Treasury Management is a division within Wells Fargo Bank which specializes in providing solutions to customers related to Accounts Payable, Accounts Receivable, Information Reporting, Payroll Services, and liquidity management. In the Treasury Manager division, there is a sales team which plays a very important role overall, as it is the primary driver for building customer relationships and generating new sources of revenue for the division. Our focus for this project is on one of most commonly used systems in the Treasury Management Sales Department: The TM CMS (Treasury Management Customer Management System). Its primary function is to allow sales employees (TMSOs) with the ability to invite clients to industry events sponsored by Wells Fargo. The system was built approximately a decade ago by contractors who are no longer involved with the bank, resulting in improper maintenance of the system. The current system is very slow and inefficient, particularly with respect to creating new user accounts, which will be the primary focus of our project. Currently, adding a new user can take anywhere from minutes due to numerous manual data entry steps, as well as poor integration of related activities in the process of setting up a new TMSO account. We have improved the system by properly integrating all of the steps required to set up a new account, automating the entire data entry process by integrating the external data source from which data was previously pulled and manually entered into the CMS system, and eliminating unnecessary fields that were not consistently being filled out. 1

4 1.2. Problem Statement Problems in the current system, with regards to creating new user accounts: Administrators cannot directly make a new user account; they must first search for the account amongst existing user accounts and receive a failed search result before being allowed to make a new account Administrators are forced to fill out almost 20 fields manually, which is very inefficient; some of these fields are particularly time-consuming, such as a picking a manager from drop down menu with dozens of managers in no particular order Administrators have to look up the information for these new user accounts in an external database; this database (the HR database, in PeopleSoft) has no connection to the CMS system at all Several of the fields on the add new user form are optional, and are inconsistently filled out by admins, leading to great variance in the time required to set up new accounts, as well as inconsistent user account data Linking TMSO accounts to regions is not handled during the initial account setup; it requires traversing a separate set of links and menus, and manually scrolling through 60+ regions and hundreds of TMSOs Objectives of the project: Allow administrators direct access to add new user form Integrate the HR/PeopleSoft database into the CMS System to allow direct searches for employee data from within CMS Automate all of the data entry involved with new account creation after pulling data from HR/PeopleSoft database Eliminate unnecessary fields when creating new accounts Integrate and automate TMSO region-linking into new account creation process Scope of the project: Project should focus primarily on improving existing processes and functionalities, not adding new functionalities beyond those necessary to create a new account Development should mostly leverage existing tools and not require significant development of new databases or systems Project should not require significant manpower or resources to implement 2

5 Existing System 2.1. Interface Home page for administrators; contains search for new user link at top: Search interface; shows search results after failed search and add new user link: 3

6 Add new user (TMSO) screen: HR/PeopleSoft database; used to fill out TMSO information to create new account: 4

7 Linking a TMSO to a Region; first screenshot shows region selection, second screenshot shows how to add TMSO to a region: 5

8 2.2 Architecture 2.3 Context Diagram 6

9 2.4. Use Case Diagram 2.5 Use Case Descriptions Use Case Name: Primary Actor: Stakeholder: Normal flow of events: Exceptional flows: Login to CMS System Administrator, TMSO, Client TM CMS System 1. User clicks on login link on homepage. 2. User enters username and password information. 3. CMS System verifies username and password information. 4. Based on user type, CMS System grants access to appropriate system tools and resources. 3a. If username and/or password are incorrect, CMS System generates an error screen and reprompts user for information. 7

10 Use Case Name: Primary Actor: Stakeholder: Normal flow of events: Exceptional flows: Search for TMSO in CMS Users Database Administrator TM CMS System 1. User clicks on "Search Users" link on homepage. 2. User enters CMS user search criteria, and presses "Search" button. 3. CMS system fails to find TMSO account in Users database, and displays "no results found" as well as "add new user" link. 4. Administrator clicks on "Add New" link, and system calls Add New TMSO use case. 3a. If TMSO is already in system, administrator verifies information and does not create new account. Use Case Name: Primary Actor: Stakeholder: Normal flow of events: Exceptional flows: Add New TMSO Administrator TM CMS System 1. Administrator clicks on "Add New User" link in "Search Results" screen after failed CMS user search for TMSO account data. 2. System generates "Add New User" screen, which displays all TMSO data to be filled out. 4. Administrator manually enters in values for each field for new TMSO account based on HR database information. 5. Administrator clicks "Save Changes" button, and system creates new TMSO account. 6. Administrator executes Link TMSO to Region use case to assign a region to new TMSO. 5a. If user presses "Cancel", clear all fields, do not create new user, and return to homepage. 8

11 Use Case Name: Primary Actor: Stakeholder: Normal flow of events: Exceptional flows: Use Case Name: Primary Actor: Stakeholder: Normal flow of events: Exceptional flows: Link TMSO To Region Administrator TM CMS System 1. Administrator clicks on "Link TMSO to Region" on homepage. 2. Administrator goes to HR (PeopleSoft) database and finds new TMSO's manager, and looks up manager's region information. 3. Administrator scrolls through list of all regions (60+ regions) to find the link for TMSO's manager's region in CMS system and clicks on it. 4. Administrator manually finds new TMSO's account from list of all TMSOs, and adds it to the list of TMSOs assigned to the selected region. 5. Administrator clicks "Save Changes" button, and system creates new user account. Invite Client to Event TMSO TM CMS System 1. TMSO searches for event using event search criteria. 2. TMSO selects appropriate event from list of event search results. 3. TMSO searches for client using client search criteria. 4. TMSO adds client to invitation list for event. 5. TMSO repeats steps 3 and 4 for as many clients as he or she would like to invite to the event. 6. TMSO clicks "invite" button to record invitations. 9

12 Use Case Name: Primary Actor: Stakeholder: Normal flow of events: Exceptional flows: Compile and Distribute Invitations Event Manager TM CMS System 1. Event manager searches for event using event search criteria. 2. Event manager selects appropriate event from list of event search results. 3. Event manager pulls up list of all invited clients for the selected event, and sends out a batch invitation using client address information. 3a. If there are no invited clients, event manager marks event as "no invitations". 10

13 Proposed System 3.1 Interface New admin homepage; note add new user link at top, which removes need to search for user in CMS database every time before creating new account: Current CMS Admin Menu Proposed CMS Admin Menu Renamed link label to read Search only Added new link to Add new users on the Admin menu. 11

14 Add New User screen; provides option to search for TMSOs in HR database directly from CMS interface, and auto-fills relevant fields for creating new users: 3.2 Architecture 12

15 3.3 Context Diagram 3.4 Use Case Diagram 13

16 3.5 Use Case Descriptions Note: I have only listed use case descriptions for new use cases and changes to old use cases. All other use cases are the same as in the existing system (which is outlined in section 2), and some use cases from existing system are not used in proposed improved system. Use Case Name: Primary Actor: Stakeholder: Normal flow of events: Exceptional flows: Add New TMSO Administrator TM CMS System 1. Administrator clicks on "Add New User" link in Admin homepage. 2. System generates "Add New User" screen. 3. Administrator executes Search for new TMSO information in HR database use case. 4. System automatically fills out all of the fields required to create new TMSO account, including the region field, which is set to the TMSO s manager s region. 5. Administrator verifies information (fields are greyed out, so admin cannot change data), and clicks "Save changes" to create new TMSO account. 5a. If user presses "Cancel", clear all fields, do not create new user, and return to homepage. Use Case Name: Primary Actor: Stakeholder: Normal flow of events: Exceptional flows: Search for new TMSO info in HR database Administrator TM CMS System 1. Administrator clicks on magnifying glass in "Add New User" screen. 2. System generates "Search for employee data" screen. 2. Administrator enters HR database search criteria to find new TMSO data. 3. Administrator selects correct employee from HR database search results. 4. System returns to "Add New User" screen. 5a. If user presses "Cancel", clear all fields, do not create new user, and return to homepage. 14

17 3.6 Data Dictionary Login Info = username + password Employee = first name + last name + employee type Employee type = [manager TMSO] TMSO = first name + last name + username + (password) + + (phone number) + (TMSO ID) + manager + (security level) Manager = manager ID + first name + last name + region Security level = [None Low Medium High] Region = region name + geographic area + authorized TMSOs Geographic area = {zip code} Authorized TMSO = {TMSO} Event = event name + date + time + location + invited clients Invited clients = {client} Client = company name + address + representative name + address CMS user search = (first name) + (last name) + (login ID) + client search results HR database search = (first name) + (last name) + (login ID) + HR database search results Event search = (event name) + (date) + (time) + (location) + Event search results Client search = (company name) + (address) + (representative name) + ( address) + client search results CMS user search results = 0{TMSO} Event search results = 0{Event} Client search results = 0{Client} HR database search results = 0{Employee) 15

18 3.7 Data Model Class Diagram 16

19 3.8 Object Behavior Model/Sequence Diagram for Add New User Use Case 17

20 3.9 Complete Class Diagram With Methods 18

21 3.10 Database Design 19

22 3.11. Software Design/Method Specifications 1. Method Name: AuthorizeLogin() Class name: Login Clients: Administrator, TMSO, Event Managers Associated Use Cases: Log In to CMS System Description: Authenticates username and password and grants access to the system. Arguments: Username and password Type of Value Returned: Access to system granted or denied Pre-Conditions: N/A Post-Conditions: Valid users are allowed to use CMS system resources. Pseudo-code: For each user account in system Compare provided username + password against stored username + password for current account If username and password match Grant appropriate access to CMS system based on user type Else move on to next user account If no user accounts match provided username + password Display error message and re-prompt for username and password 2. Method Name: AddNewUser() Class name: TMSO Clients: Administrators Associated Use Cases: Add New TMSO Description: Generates add new user form, and allows user to search for employee to auto-fill fields. Arguments: N/A Type of Value Returned: N/A Pre-Conditions: N/A Post-Conditions: Allows user to search for employee data in HR database. Pseudo-code: If Administrator presses add new user button Generate add new user screen with appropriate fields If Administrator presses magnifying glass icon Bring up HR database search screen Else If Administrator clicks save changes without selecting a user Display error message Else Do Nothing End If End If 20

23 3. Method Name: EmployeeSearch() Class name: HR Database Search Clients: Administrators Associated Use Cases: Search for TMSO info in HR Database Description: Allows user to search for employee data in HR Database, and returns appropriate results for given search criteria. Arguments: Search criteria; some combination of first name, last name, and login ID Type of Value Returned: Data from HR Database for single employee. Pre-Conditions: User is coming from add new user screen. Post-Conditions: Returns employee data to be used in filling out add new user screen fields. Pseudo-code: Do while there are still records to examine Compare current record fields to provided search criteria If provided criteria match corresponding record fields Determine region by linking current record to corresponding manager record Return all relevant information, including region BREAK Else move to next record End Do If no records match provided criteria Show no matching results; please search with different criteria screen End If 4. Method Name: CreateNewAccount() Class name: TMSO Clients: Administrators Associated Use Cases: Add New User Description: Use the information provided by HR database to verify and instantiate new account. Arguments: Relevant employee data from HR database (see data dictionary for all fields required for TMSO ) Type of Value Returned: New use account for TMSO. Pre-Conditions: Data provided is that of a valid employee account from HR database. Post-Conditions: New employee account is ready for TMSO to use for inviting clients. Pseudo-code: Check to make sure account does not already exist in System Check to make sure account is that of a TMSO Link account to region using manager s region information Create new TMSO user account with data provided from HR database search 21

24 5. Method Name: VerifyAccountIsTMSO() Class name: Employee Clients: Administrators Associated Use Cases: Add New User Description: Use the information provided by HR database to verify and instantiate new account. Arguments: Relevant employee data from HR database (see data dictionary for all fields required for TMSO ), particularly employee type Type of Value Returned: True/False verification of TMSO account type. Pre-Conditions: Data provided is that of a valid employee account from HR database. Post-Conditions: Valid accounts will continue to be processed for new TMSO accounts in CMS System. Pseudo-code: If the employee type data retrieved for the HR Database is not equal to TMSO Return false and display error message and instruct user to search again Else return true to indicate account is of a valid type ( TMSO ) 22

25 3.12 System Controls 1. The system will require a login ID and password for all users (Admins, TMSOs, and Event Managers) to ensure only authorized employees are allowed to access system. 2. If the admin chooses an employee that already has an account in the CMS users database when searching for employee data in the HR database, the System will show an error message and give admin option to pull up the existing account information for viewing and verification purposes instead. 3. If the admin chooses an employee that is not a TMSO in the HR database, the System will give an error message and allow the admin to search again for a different user. 4. The admin cannot change the fields that are auto-filled after choosing an employee from the HR database, to ensure that the data is consistent between the HR database and the CMS users database. 5. System will automatically fill out region information (instead of going through Link TMSO to region ) when employee data is retrieved from HR database to avoid errors in manual entry and ensure consistency across HR and CMS user databases. 6. The system will no longer retrieve or fill out non-mandatory fields when creating new accounts; previously, some admins were filling out these fields but the majority were leaving them blank. This will ensure consistency for all new TMSO accounts moving forward. 7. System disables invitation to event for events after the invitation deadline has passed, to prevent accidental invitations to events that have already occurred Functional Specification Document 1. Administrators will be able to search for existing CMS users. 2. Administrators will be able to create new users without any manual entry of data, simply by searching for the appropriate user in the integrated HR/PeopleSoft database. The necessary fields will be filled out automatically. 3. TMSOs will automatically be assigned to the correct region based on their manager s region information. 4. TMSOs will be able to view the appropriate events based their region assignment, and will be able to invite clients to these events accordingly. 5. Event managers will be able to compile the invitations set by TMSOs and distribute them using the information for the clients on file. 23

26 Project Management 4.1 Project Activities This project involved two primary activities: 1. Project Report. We mostly worked on this individually, and everyone submitted their respective parts of the project to me. I reviewed their submissions for quality, made improvements, and put together the final project report. 2. Presentation. Jose put together the slides for the presentation, and we practiced before we recorded our presentation. 4.2 Allocation of activities to team members The following material in this section is the document I sent out to team members, allocating activities, setting deadlines, and expectations for the project: ************************************************************************************* This is how the work is split up: Team Member Document 1 Document 2 Document 3 Arindam Data Model Database Design Software Design Jose Interface Design Object Behavior Model Class Diagram Amer Controls Data Dictionary Functional Specs Document Ameen Process Model Problem Statement Guled Context Diagram Executive Summary Due dates for each document: Document 1: November 20 th Document 2: November 27 th Document 3: December 4 th Expectations: 1. Given that many of these documents are dependent on each other (for example, we cannot do database design without completed data model, process mode, and controls), it is very important that everything is completed BY THE DEADLINES SPECIFIED ABOVE. 2. I will not remind or hunt team members down to get the documents, and I will not accept late documents. If I do not have a document by the given date, I will do it myself to ensure the project is completed in a timely manner, and I will notify Prof. Raghunathan. 3. I expect a reasonable, honest effort to be made on each document. If the document you submit to me looks like it was thrown together in 5 minutes, you will not receive any credit from me on the final evaluation. I will discuss any work that I think is of unacceptable quality with Prof. Raghunathan directly so there is no dispute on the subject. 24

27 4. I will not test team members to make sure everyone understands how the system works. I had hoped to explain how the system works in person and scheduled several meetings, but not a single person came to any of the meetings. Accordingly, it is YOUR responsibility to ensure that you understand how the system works. If you have questions, you can me or try to set up a meeting with me or Jose, and we will do our best to clarify matters in person. If I do not hear from any of you with questions, I assume you understand how the system works from the document provided. ************************************************************************************* 4.3 Planned Timeline Although we did not have a formal planned timeline, the general plan was as follows: September: Choose a system, learn about the system October: Start work on project, complete analysis phase by end of month November: Finish project report, complete design phase and review final project report December: Put together and execute presentation 4.4 Execution Timeline September October: Unsuccessfully attempt to have several meetings; Jose teaches me about the system November: I put together document explaining system for remaining team members and allocate project report duties to everyone at start of month, along with deadlines December: Most of the work is done during this time; presentation is recorded 25

28 4.5 Meeting Notes Meeting 1 Date: September 7 th Invitees: Entire Group Attendees: Arindam Bhattacharya, Jose Romero Time: 4:45 PM Discussion: Choosing a system, settling on Jose s TM CMS System from work, learning the basics of the system Meeting 2 Date: September 28 th Invitees: Entire Group Attendees: Arindam Bhattacharya Time: 4:45 PM Discussion: Cancelled, as Jose was sick and nobody else showed up. Meeting 3 Date: October 8 th Invitees: Arindam Bhattacharya, Jose Romero Attendees: Arindam Bhattacharya, Jose Romero Time: 12:00 PM Discussion: Jose showed me the system in person, and I was able to learn hands-on how the system worked and what its issues were. Also discussion of how to improve the system. Meeting 4 Date: October 26 th Invitees: Entire Group Attendees: Arindam Bhattacharya Time: 3:00 PM Discussion: Cancelled, as Jose was sick and nobody else showed up. Meeting 5 Date: December 4 th Invitees: Entire Group Attendees: Entire Group Time: 8:30 PM Discussion: Recorded presentation. 26

29 Presentation Link Here is the link to our presentation on our project (about 12 minutes long): 27