Part1 (50 Points) Assume that the Certificates of Deposits (CDs) offered by various banks are compounded annually. The final value of the CD is computed using the following formula: FinalValue = InitialDeposit * (1 + r)t, where t is the number of years the CD is invested, and r is the interest rate in decimal form. If the interest rate is 4%, then r = 0.04. Create a package named cs520.hw2.part1 and complete the following by writing the appropriate classes under this package. Create a “procedural style” program that meets the requirements below. Create a class named BankingProceduralStyle and test the final value of two different CDs as specified below. BankA offers 3 year CDs with an interest rate of 4%. BankB offers 4 year CDs with an interest rate of 3%. You have $5000 to invest and considering the above two options. Use the variables for initial deposit, bank name, bank interest, and bank term (# of years) – one set of variables for the first CD and a different set of variables for the second CD. a. Compute the final value of the CD from BankA and display the results to the console. b. Compute the final value of the CD from BankB and display the results to the console. c. Using the if-else construct, check which option is better in terms of the final values and display the results to the console. A sample output with the values above is shown below. Note that your program should not hard code the input values in the calculations of the final value and should only use the variables in the calculations.

Overview You are a senior software developer on a team of software developers who are responsible for a large banking web application. Your manager has learned that there has been a number of unauthorized uses of one of the company's systems. The other developers spent a lot of time tracing the issue, and they narrowed it down to some SQL queries running in the database that were modified from the queries created by the application. It allowed a hacker to get more data back than they were entitled to, including passwords. The other developers have tried a few things, but they don't know how to prevent it. Following some guidance from an older testing guide, the developers were able to replicate the problem in a standalone test case including a standalone in-memory SQLite database. Doing this allowed them to reliably reproduce the SQL injection attack. However, they don’t know what to do next to prevent it from happening in the future. They came to you for help. You will learn to do the following: Anticipate when a possible SQL injection attack is about to occur  Write code to prevent a suspected SQL injection attack Decide how to react when there is an attempted SQL injection attack Protect your code from SQL injection attacks Prompt This assignment presents code that creates an in-memory database and runs a number of queries with and without SQL injection, always dumping the results to the console. You need to modify the run_query() function to detect a potential SQL injection attack, prevent it, and display that information to the console. The specific type of SQL injection attack is the “OR value=value;” attack, and you must defend against that specific attack with value being any allowed SQL literal (numeric or quoted string). The following are a few key notes: The source code has been commented using TODO to explain the detailed rules you must follow. There may be more than one way to solve this problem. It is key to demonstrate that your implementation prevents the SQL injection attack and displays the information to the console. Do not forget that you can leverage capabilities provided by the standard C++ library to help you achieve success. Please comment on any changes you make in the code to explain the logic, formulas, or data types you are adding. You will also create a brief written summary of the approach taken, why it will stop the SQL Injection Attack, any issues you encountered, and how you resolved those issues. Specifically, you will prepare the following: SQL injection defensive coding solutions C/C++ program functionality and best practices A summary of your process in a Word document that contains a screenshot of the application console output