ProjectTwoRequirements.pdf.docx

12/1/2020 Project Two Guidelines and Rubric - CS-210-H2418 Programming Languages 20EW2

12/1/2020 Project Two Guidelines and Rubric - CS-210-H2418 Programming Languages 20EW2

You are asked to collaborate with Airgead Banking, one of Chada Tech’s clients. Airgead Banking is well known in the community. They open sponsor schools and have recently decided to partner with the local high school to develop a program that will teach students the concepts of fiscal responsibility (such as living within their means and spending less than they make) via an interactive system. The initial focus for this project will be on investing and the power of compound interest. You will develop an applica on that allows users to see how their investments will grow over me. Airgead Banking has provided you with a list of functional requirements that describe what they need their application to do.

Direc ons

1. Review the Airgead Banking App Functional Requirements, located in the Supporting Materials sec on. Create pseudocode or a flowchart to plan your coding project. Outline your code step-by-step so that you can use it as a guide when coding. This will be submitted along with your zipped application.

a. Do not write code yet. You will do that in Step 3. For this step, write your thoughts in English of what the program should do.

b. Do not be concerned with syntax, just list statements, each describing a single ac on. c. List all steps.

d. Use proper naming conventions.

e. Keep it simple—use only one statement per line.

2. Develop an object-oriented programming (OOP) application using secure and efficient C++ code. Make sure that your application:

a. Meets all specifications listed in the Airgead Banking App Functional Requirements

b. Follows best practices described in the Airgead Banking Standards document c. Includes in-line comments

3. When your solution is finished, zip your project including all components (CPP, H, and any other files used).

4. Upload your zipped project file and pseudocode or flowchart to the project submission area.

What to Submit

Pseudocode or Flowchart

Submit a pseudocode or flowchart that clearly outlines your program logic step-by-step.

Investment Code

Submit your zipped project files, including all components (CPP, H, and any other files used). Be sure to include in-line comments.

You will write, test, and run your code using an integrated development environment (IDE). Review this tutorial to learn how to save and export files from your IDE. Important: Do not change the names of any class files.

Project Two Rubric

Criteria

Exemplary (100%)

Proficient (85%)

Needs

Improvement

(55%)

Not Evident (0%)

Value

Pseudocode or

Flowchart

N/A

Pseudocode or flowchart effectively plans, organizes, and sequences program flow (100%)

Shows progress toward proficiency, but with errors or omissions; areas for improvement may include using proper shapes for flowcharts, etc.

(55%)

Does not attempt

criterion (0%)

10

Error Handling

N/A

Code effectively validates user input

(100%)

Shows progress toward proficiency, but with errors or

Does not attempt

criterion (0%)

20

i i

for improvement may include input validation for positive numbers,

etc. (55%)

User Interface

N/A

Console contains all required input elements (100%)

Shows progress toward proficiency, but with errors or omissions; areas for improvement may include enabled input boxes, etc. (55%)

Does not attempt

criterion (0%)

25

Balance and

Earned Interest

Charts

N/A

Charts display correct balances and earned interest by year with and without additional monthly input

(100%)

Shows progress toward proficiency, but with errors or omissions; areas for improvement may include accurate earned interest calculations, etc.

(55%)

Does not attempt

criterion (0%)

25

Industry

Standard Best

Practices

Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner

(100%)

Uses industry standard best practices such as in-line comments and appropriate naming conventions to

enhance readability and maintainability

(85%)

Shows progress toward proficiency, but with errors or omissions; areas for improvement may include naming conventions or inline comments

(55%)

Does not attempt

criterion (0%)

20

Total:

100%

https://learn.snhu.edu/d2l/le/content/569970/viewContent/10537038/View 1/4

https://learn.snhu.edu/d2l/le/content/569970/viewContent/10537038/View 1/4