Note that classes bankAccount and checkingAccount are abstract. (What does that mean?) The other accounts are not abstract. bankAccount: Every bank account has an account number, the name of the owner, and a balance. Some operations common to all types of accounts are retrieve account owner's name, account number, and account balance; make deposits; withdraw money, and create monthly statement. Some of these will be pure virtual. (What does this mean?) checkingAccount: A checking account is a bank account. Therefore, it inherits all the properties of a bank account. Because one of the objectives to a checking account is to write checks, include a pure virtual function writeCheck to write a check. serviceChargeChecking: A service charge checking account is a checking account. Therefore, it inherits all the properties of a checking account. For simplicity, assume this type of account does not pay any interest, allows the account holder to write a limited number of checks each month, and does not require a minimum balance. Include appropriate named constants, instance variables, and functions in this class. noServiceChargeChecking: A checking account with no monthly service charge is a checking account. Therefore, it inherits all the properties of a checking account. Furthermore, this type of account pays interest, allows the account holder to write checks, and requires a minimum balance. highInterestChecking: A checking account with high interest is a checking account with no monthly service charge. Therefore, it inherits all the properties of a no service charge checking account. Furthermore, this type of account pays higher interest and requires a higher minimum balance than the no service charge checking account. Lots to think about above... Why are pure virtual functions and abstract classes used here? What are pure virtual functions and abstract classes used here? How is a "pure virtual function" different from a plain "virtual function"? What might partial definitions of the following look like, and why? bankAccount and checkingAccount serviceChargeChecking, noServiceChargeChecking and highInterestCheckin
Note that classes bankAccount and checkingAccount are abstract. (What does that mean?) The other accounts are not abstract.
bankAccount: Every bank account has an account number, the name of the owner, and a balance. Some operations common to all types of accounts are retrieve account owner's name, account number, and account balance; make deposits; withdraw money, and create monthly statement. Some of these will be pure virtual. (What does this mean?)
checkingAccount: A checking account is a bank account. Therefore, it inherits all the properties of a bank account. Because one of the objectives to a checking account is to write checks, include a pure virtual function writeCheck to write a check.
serviceChargeChecking: A service charge checking account is a checking account. Therefore, it inherits all the properties of a checking account. For simplicity, assume this type of account does not pay any interest, allows the account holder to write a limited number of checks each month, and does not require a minimum balance. Include appropriate named constants, instance variables, and functions in this class.
noServiceChargeChecking: A checking account with no monthly service charge is a checking account. Therefore, it inherits all the properties of a checking account. Furthermore, this type of account pays interest, allows the account holder to write checks, and requires a minimum balance.
highInterestChecking: A checking account with high interest is a checking account with no monthly service charge. Therefore, it inherits all the properties of a no service charge checking account. Furthermore, this type of account pays higher interest and requires a higher minimum balance than the no service charge checking account.
Lots to think about above...
- Why are pure virtual functions and abstract classes used here?
- What are pure virtual functions and abstract classes used here?
- How is a "pure virtual function" different from a plain "virtual function"?
- What might partial definitions of the following look like, and why?
- bankAccount and checkingAccount
- serviceChargeChecking, noServiceChargeChecking and highInterestChecking


Trending now
This is a popular solution!
Step by step
Solved in 3 steps with 1 images









