Starting from:
$30
CPT120-Assignment 3 Solved
For this assignment, assume that you are a freelance programmer creating a small tool or a utility program of your own choosing to add to your portfolio of Object Oriented (OO) Java applications. With this project you aim to demonstrate to potential employers or clients how you can:
1. Demonstrate OO concepts as taught in class and create a small tool or utility program using (exclusively) a limited set of fundamental code concepts (detailed in section 4.1 below) and,
2. You are able to analyse and evaluate in your code documentation (see requirements in section 4.2 below).
Note: You can turn your non-OO assignment 2 in to an OO oversion for this assignment, if you so prefer. As before, you must not just “throw in the concepts” to your program just because they need to be there; it should be clear from the code why a certain concept should be there and you must further explain these through your comments. You will also need debug your code on your own and document any issues, etc. You are given marks on your ability to fulfill all requirements of this document.
Develop this assignment in an iterative fashion (as opposed to completing it in one sitting
3. Learning Outcomes
This assessment is relevant to the following Learning Outcomes:
1. Demonstrate knowledge of basic concepts, syntax and control structures in programming
2. Devise solutions to simple computing problems under specific requirements
3. Encode the devised solutions into computer programs and test the programs on a computer
4. Demonstrate understanding of standard coding conventions and ethical considerations in programming.
4. Assessment details
Note: Please ensure that you have read sections 1-3 of this document before going further.
Your code must meet the following code requirements (section 4.1) and documentation requirements (section 4.2).
In places where this specification may not tell you how exactly you should implement a certain feature, the programmer (you) need to use your judgment to choose and apply the most appropriate concepts from class materials. Follow answers given by your “client” or “supervisor” (you instructor) under Canvas→Discussions→’Assignment 3’ when in doubt.
4.1) The following code requirements/concepts must be applied to demonstrate your knowledge of standard lesson materials and approaches; must refer to corresponding rows in the rubric (section 9) for full details.
C1) Multi-class object oriented relationships and code format.
C2) Object member variables.
C3) Constructors.
C4) Accessors, mutators and other methods.
C5) File reading and/or writing.
C6) Conditional execution and repetition.
4.2) Documentation requirements. Must refer to corresponding rows in the rubric (section 9).
D1. The code comments in this assignment must focus more on the analysis of your approaches and their evaluation instead of simply translating the Java code to English (see rubric in section 9 of this document; examples will also be given in lessons). Write comments before code blocks (e.g. before methods, loops, ifs, etc. where you can have { }) and important variable declarations.
D2. Explain any code requirements that you have not met and all bugs (situations that might cause the program to crash or behave abnormally) in the approximate locations they originate within your code. Bugs imposed by limitations in the lesson topics such as input type mismatches need not be corrected in code but they still must be documented, if they exist. If you do not have bugs, you must explicitly say that there are none. Tip: A good programmer knows the limits of their program
1. Demonstrate OO concepts as taught in class and create a small tool or utility program using (exclusively) a limited set of fundamental code concepts (detailed in section 4.1 below) and,
2. You are able to analyse and evaluate in your code documentation (see requirements in section 4.2 below).
Note: You can turn your non-OO assignment 2 in to an OO oversion for this assignment, if you so prefer. As before, you must not just “throw in the concepts” to your program just because they need to be there; it should be clear from the code why a certain concept should be there and you must further explain these through your comments. You will also need debug your code on your own and document any issues, etc. You are given marks on your ability to fulfill all requirements of this document.
Develop this assignment in an iterative fashion (as opposed to completing it in one sitting
3. Learning Outcomes
This assessment is relevant to the following Learning Outcomes:
1. Demonstrate knowledge of basic concepts, syntax and control structures in programming
2. Devise solutions to simple computing problems under specific requirements
3. Encode the devised solutions into computer programs and test the programs on a computer
4. Demonstrate understanding of standard coding conventions and ethical considerations in programming.
4. Assessment details
Note: Please ensure that you have read sections 1-3 of this document before going further.
Your code must meet the following code requirements (section 4.1) and documentation requirements (section 4.2).
In places where this specification may not tell you how exactly you should implement a certain feature, the programmer (you) need to use your judgment to choose and apply the most appropriate concepts from class materials. Follow answers given by your “client” or “supervisor” (you instructor) under Canvas→Discussions→’Assignment 3’ when in doubt.
4.1) The following code requirements/concepts must be applied to demonstrate your knowledge of standard lesson materials and approaches; must refer to corresponding rows in the rubric (section 9) for full details.
C1) Multi-class object oriented relationships and code format.
C2) Object member variables.
C3) Constructors.
C4) Accessors, mutators and other methods.
C5) File reading and/or writing.
C6) Conditional execution and repetition.
4.2) Documentation requirements. Must refer to corresponding rows in the rubric (section 9).
D1. The code comments in this assignment must focus more on the analysis of your approaches and their evaluation instead of simply translating the Java code to English (see rubric in section 9 of this document; examples will also be given in lessons). Write comments before code blocks (e.g. before methods, loops, ifs, etc. where you can have { }) and important variable declarations.
D2. Explain any code requirements that you have not met and all bugs (situations that might cause the program to crash or behave abnormally) in the approximate locations they originate within your code. Bugs imposed by limitations in the lesson topics such as input type mismatches need not be corrected in code but they still must be documented, if they exist. If you do not have bugs, you must explicitly say that there are none. Tip: A good programmer knows the limits of their program
1 file (187.4KB)
