summaryrefslogtreecommitdiffstats
path: root/C++/OOP/INSTRUCTIONS
diff options
context:
space:
mode:
authormsglm <msglm@techchud.xyz>2023-01-14 05:31:48 -0600
committermsglm <msglm@techchud.xyz>2023-01-14 05:31:48 -0600
commit9d53d8857eaa1c9405894a88ca75bc4657e42f35 (patch)
treeeb1efc1d028b949dd83bb710c68be8eff58f26e7 /C++/OOP/INSTRUCTIONS
downloadschool-code-9d53d8857eaa1c9405894a88ca75bc4657e42f35.tar.gz
school-code-9d53d8857eaa1c9405894a88ca75bc4657e42f35.tar.bz2
school-code-9d53d8857eaa1c9405894a88ca75bc4657e42f35.zip
Inital CommitHEADmaster
Diffstat (limited to 'C++/OOP/INSTRUCTIONS')
-rw-r--r--C++/OOP/INSTRUCTIONS43
1 files changed, 43 insertions, 0 deletions
diff --git a/C++/OOP/INSTRUCTIONS b/C++/OOP/INSTRUCTIONS
new file mode 100644
index 0000000..8c199c2
--- /dev/null
+++ b/C++/OOP/INSTRUCTIONS
@@ -0,0 +1,43 @@
+ Covert your Project 5 - Structs program to be object-oriented.
+Create a program that uses a class with array variables that do the following:
+
+ Get 3 sets of employee information for the below via the keyboard - no input file this time:
+ First Name
+ Last Name
+ Job Title
+ Employee Number
+ Hours Worked
+ Hourly Wage
+ Number of Deductions Claimed
+ Determine if the employee is entitled to overtime (see videos for explanation of overtime)
+ Determine tax rate based on deductions claimed (see videos for explanation of deductions)
+ Determine gross pay, taxes withheld, and netpay
+ Output all information to the screen, but only output overtime if the employee has it
+ Determine the highest and lowest paid employees. Output the name and salary of both
+
+Assignment Notes:
+
+ No structs please. Make your all of variables as private in the class to show me you understand how to do this
+ You may use vectors or array variables to store the employee data
+ You should not ask the user for their tax rate, gross pay, net pay, or taxes withheld. Your program should do this for the user.
+ I expect to see functions for steps 1 - 6 above
+
+General Notes:
+Be sure to use comments in your program: Name, Program Description, Date and anywhere else in the program you deem necessary.
+If you are stuck, I will help you!
+Grading Rubric:
+
+ If you do not include comments at the top of the program (name, program description, date), you will lose 15 points
+ If your program is not object-oriented, you will lose up to 80 points (OOP is the goal of this assignment)
+ If your program does not use functions, you will lose up to 60 points (depending on the number of functions missing)
+ If your program does not compile (run), then I will give a grade of 0/100. But will give you the change to repair for points back (some points are better than none)
+ If your program is late (within 48 hours of the due date), you will lose 25 points
+ If your program is late beyond the 48 hour due date, I will typically still accept it, but you will lose far more points. Depends on when you turn it in
+ If you use global variables in your program, I will deduct 5 points for each used
+ If your program is not formatted nicely (code all over the place, ugly), you will lose up to 25 points depending on the extent
+ If your program stops working when I run it, you will lose points. The exact amount depends on the severity of the error
+ If your program still has your friend's name on it, I will send you a message asking you to try harder while giving you a 0/100
+ If your program looks like a a professional programmer wrote it, I will write to you to ask if you want a job. Well, maybe not. But, I will ask about the code
+ This is just a list of typical issues I run into when grading to give you some idea of where your points go. Points can be taken off for other reasons.
+
+