Your SlideShare is downloading. ×
0
Portfolio Banking Project E-R
Portfolio Banking Project E-R
Portfolio Banking Project E-R
Portfolio Banking Project E-R
Portfolio Banking Project E-R
Portfolio Banking Project E-R
Portfolio Banking Project E-R
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Portfolio Banking Project E-R

1,100

Published on

Part 1 of a Financial Project

Part 1 of a Financial Project

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,100
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. .SQL Portfolio A Financial Project Name: Alan D. Arico Email: alan.arico@setfocus.com Phone: 630 898-2234 A new database is being developed for the financial services wing of the bank. Initial thoughts about the implementation was provided by the Senior DBA in the form of a column list with the requirement to produce a Visio Entity Relationship diagram in Third-Normal Form. 2/19/2009 1
  • 2. Table of Contents Bank Project Statement – p. 3 Other Criteria – p. 4 Provided Column List – p. 5 Designed Entities – p. 6 Entity-Relationship Diagram (Visio) – p. 7 2/19/2009 Alan.Arico@setfocus.com 2
  • 3. Bank Database Design Introduction: There are only two types of accounts at this time: Checking and Savings accounts. The provided column list should be separated into appropriate normalized entities (tables) with relationships between these entities defined. The most efficient choices as far as your primary key constraints and foreign key constraints, and picked the appropriate data types for each of the columns. Otherwise he might have to send you to SetFocus LLC to complete a RDBMS course they’ve used in the past for entry-level employees. Project Goals: Again, the goal is 3rd normal form, but in case denormalization is required for a valid business reason, it must be document as part of the submission. Several columns in the list may be redundant. 2/19/2009 3
  • 4. Other Criteria When an employee opens an account, performs a transaction on or reactivates an account there must be a record of which employee performed the action. Every person who opens a savings account does not get the same rate. Because the bank charges an overdraft fee, a record must be maintained on any transaction that causes an account to go into overdraft. Extra error information is required to be stored when a transaction fails. The bank uses this information for fraud detection and to diagnose periodic problems within their networks and applications. Customers have a user logins to allow them to access all of their accounts. If a user fails a login attempt, for instance because they have forgotten their password, a record of that failed attempt needs to be kept. The information for checking and saving accounts is very similar to each other as are the transactions that update those accounts. More than one customer is allowed on each account, and any transaction record should reflect which customer made the transaction.
  • 5. Column List DateOpened CustomerFirstName ErrorLogID AccountStatus CustomerMiddleInitial ErrorTime OpeningBalance CustomerLastName UserName CurrentBalance CustomerAddress1 FailedTransactionErrorID AccountID CustomerAddress2 FailedTransactionXML CustomerID City FailedTransactionErrorTime OverdraftAccountID State EmployeeID TransactionID Zipcode EmployeeFirstName FailedTransactionID Email EmployeeMiddleInitial TransactionTypeID SSN EmployeeLastName TransactionTypeName UserLogin EmployeeIsManager TransactionAmt UserPassword AccountReactivationLogID SavingsInterestRate UserSecurityQuestion ReactivationDate TransactionDate UserSecurityQuestionAnswer UserSecurityQuestion2 TransactionAmount HomePhone UserSecurityQuestionAnswer2 TransactionType WorkPhone UserSecurityQuestion3 OldBalance CellPhone UserSecurityQuestionAnswer3 NewBalance
  • 6. Designed Entities Categorized columns, Removed Duplicate Columns, *Primary Keys Added Account UserSecurityQuestions Employee TransactionType *AccountID *UserSecurityQuestionID *EmployeeID *TransactionTypeID CurrentBalance UserSecurityQuestion EmployeeFirstName TransactionTypeName AccountType UserSecurityQuestion2 EmployeeLastName AccountReactivationLogID AccountStatus UserSecurityQuestion3 EmployeeMiddleInitial UserSecurityAnswers Customer TransactionLog EmployeeIsManager *UserAnswerID *CustomerID *TransactionID UserLogins UserSecurityQuestionAnswer CustomerAddress1 TransactionType *UserLogin UserSecurityQuestionAnswer2 CustomerAddress2 TransactionDate UserName UserSecurityQuestionAnswer3 CustomerFirstName DateOpened UserPassword OverDraftLog CustomerLastName ReactivationDate LoginErrorLog OverdraftAccountID CustomerMiddleInitial TransactionAmount *ErrorLogID FailedTransactionLog City, State, Zipcode TransactionAmt ErrorTime *FailedTransactionID Email NewBalance SavingsInterestRates FailedTransactionXML, ErrorTime HomePhone, CellPhone OpeningBalance *SavingsInterestRateID FailedTransactionErrorType WorkPhone OldBalance SavingsInterestRate *FailedTransactionErrorID SSN FailedTransactionErrorTime
  • 7. Entity-Relationship Diagram (Visio) 2/19/2009 7

×