Comp 220 i lab 3 bank account lab report and source code
Upcoming SlideShare
Loading in...5
×
 

Comp 220 i lab 3 bank account lab report and source code

on

  • 51 views

COMP 220 iLab 3 Bank Account Lab Report and Source Code ...

COMP 220 iLab 3 Bank Account Lab Report and Source Code
COMP 220 iLab 2 Resistor Lab Report and Source Code
COMP 220 iLab 1 Two-Dimensional Arrays Lab Report and Source Code
COMP 220 Entire Course
COMP 220 iLab 4 Composition Lab Report and Source Code
COMP 220 iLab 5 Lab Report and Source Code
COMP 220 iLab 6 Overloaded Operators Lab Report and Source Code
COMP 220 iLab 7 Polymorphism Lab Report and Source Code

Statistics

Views

Total Views
51
Views on SlideShare
51
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Comp 220 i lab 3 bank account lab report and source code Comp 220 i lab 3 bank account lab report and source code Document Transcript

  • TO Buy the Tutorial Visit Our Website This lab introduces you to writing a C++ program to implement the concept of class inheritance using different types of bank accounts as a model. In this lab, you will create a base class, called CBankAccount, and two additional classes (each derived from CBankAccount), called CSavingsAccount and CCheckingAccount. You will then test the operations of each class in function main() to simulate the transactions of both a checking account and a savings account. Deliverables Submit a single Notepad file containing the source code for all the files of the lab to the Dropbox for Week 3. Your source code should use proper indentation and be error free. Be sure that your last name and the lab number are part of the file name: for example, YourLastName_Lab3.txt. Each program should include a comment section that includes (minimally) your name, the lab and exercise number, and a description of what the program accomplishes. Submit a lab report (a Word document) containing the following information to the Dropbox for Week 3. Include your name and the lab or labexercise number. Specification: Include a brief description of what the program accomplishes, including its input, key processes, and output. Test Plan: Include a brief description of the method you used to confirm that your program worked properly. If necessary, include a clearly labeled table with test cases, predicted results, and actual results. Summary and Conclusions: Includea summary of what the lab demonstrated and any conclusions drawn from the testing of the
  • lab program. Provide a UML diagram showing the base and the derived class relationships, access specifiers, data types, and function arguments. Answers to Lab Questions: Answer any and all of the lab questions included in the lab steps. Summary: Write a statement summarizing your predicted and actual output. Identify and explain any differences. Conclusions: Write at least one nontrivial paragraph that explains, in detail, either a significant problem you had and how you solved it or, if you had no significant problems, something you learned by doing the exercise. Each lab exercise should have a separate section in the lab-report document. Your lab grade is based upon the formatting of your source code; the use of meaningful identifiers; the extent of internal documentation; the degree to which an exercises’ specifications are met; and the completeness of your lab report. iLABSTEPS STEP 1: Create the Multifile Project and the Main (Base) Class Create a new project that consists of the base class BankAccount. The BankAccount class should contain, at minimum, the following members. It should contain data members to store a bank customer's balance and account number. These should be of different and appropriate data types. It should have function members that do the following: set the account number; return the account number; return the account balance; deposit money into the account; and withdraw money from the account. STEP 2: Create the CheckingAccount Class Derived From the BankAccount Class The class CheckingAccount should contain, at a minimum, the following members.
  • It should contain a data member to keep track of the number of withdrawal transactions made on the account. Whenever a withdrawal is made, this number should be incremented. Override the base class, withdraw-money function, and add the capability to deduct transaction fees from an account using the following guidelines. The checking account is allowed three free transactions. For each successful withdrawal transaction past the three free transactions, there will be a service fee of 50 cents per transaction. The service fee should be deducted from the account balance at the time the transaction is made. If there are insufficient funds in the account balance to cover the withdrawal plus the service fee, the withdrawal should be denied. The function should return a value to indicate whether the transaction succeeded or failed. Transaction fees should be deducted only from successful transactions, but the transaction count should be incremented in either case. STEP 3: Create the SavingsingAccount Class Derived From the BankAccount Class The class CheckingAccount should contain, at a minimum, the following members. It should contain a data member to hold the daily interest rate. The daily interest rate can be calculated from a yearly interest rate by dividing the annual rate by 365. It should contain a data member to keep track of the number of days since the last transaction or balance inquiry. This should be updated using a randomnumber generator (reference Lab 1) that will return a value representing the number of days between 0 and 7, inclusive. We will assume that this bank is open every day of the year. It should contain a data member to hold the interest earned since the last transaction or balance inquiry. It should contain a function member to set the annual interest rate. Utilize the base-class functions for both withdrawal and deposit operations for the savings account. Override the baseclass-balance inquiry function to add calculating and adding interest to the account based on the daily interest rate, the current balance of the account, and the number of days since the last balance inquiry. This should be called only when a balance inquiry is made, not when a deposit or withdrawal transaction or an account number inquiry is made. If there are insufficient funds in the account balance to cover a withdrawal, the withdrawal should be denied. The number of days since the last transaction or balance inquiry and the interest calculations should still be made. A value should be returned to indicate whether a
  • withdrawal transaction succeeded or failed. It should contain a function member to return the interest earned since the last transaction or balance inquiry. It should contain a function member to return the number of days since the last transaction or balance inquiry. STEP 4: Test Program Operation All data-input and data-display operations (cin and cout) should be done in the function main() test program. The test program should create one checking account and one savings account with initial balances of $100 each using the functions defined in the class definitions. The test program should also assign a unique, five-digit account number to each account and assign an annual interest rate of 3% for the savings account. The test program should then display a menu that allows the user to select which option is to be performed on which account, including the following. Make a deposit and specify the amount to a selected or an entered account. Make a withdrawal and specify the amount to a selected or an entered account. Return the balance of a selected or an entered account. For deposit transactions, withdrawal transactions, and balance inquiries, the updated balance and any fees charged or interest earned should also be displayed. For the savings account, the number of days since last transaction should be displayed. Exit the program. Each account operation should display the account number and the account type. Lab Questions Please answer all the lab questions in the text file that is to be turned into the Dropbox. You are not required to copy the question text into your document, but all answers should be listed with the question number they answer. Were any base-class functions called or overloaded in either of the derived classes? If so, list which class and which function, and explain why they were either called or overloaded. Were any derived-class functions not explicitly called by the test program? If so, list which class and function, and explain why this was done. Which access attribute was used for each of the classes derived from the base class? Why was this access attribute chosen?