ICS4U Assignments
Submitting your work to Google Classroom
Screen Size Limitations for your Assignments. Please read and follow this document.
Your program windows will be NO LARGER than 1000 pixels wide by 675 pixels high.
- Final Assignment - Airport Simulation - Assigned December 22nd, Due January 23rd.
You'll need to work on this at home too!(NOT over the Holiday Break). Worth 10% of final 30% of course. Late Marks will be deducted.
Sorting/Searching/Recursion Test Tuesday January 10th. Study Hints are Here
File IO Test Monday December 12th. Study Hints are Here
- Recursion Assignment - Due December 23rd a 2pm(extended from 12/22). Assigned on December 5th. This is a substantial assignment. Don't put it off. You'll need to work on this at home too!. Worth 20% of final 30% of course. Late Marks will be deducted.
Inspired by! Fred Flintsone!
Please name the project 'LastFirstRecursionA' for part A and 'LastFirstRecursionB' for part B. Submit them to the Classwork item by the due date.
Video of description of Part A
Here is Part A of the assignment. 'LastFirstRecursionA', where 'Last' is your Last Name and 'First is your First Name, and submit to the Classwork item by the due date. Global variables are NOT permitted in this assignment.
Here is Part B of the assignment. 'LastFirstRecursionB', where 'Last' is your Last Name and 'First is your First Name, and submit to the Classwork item by the due date. Global variables are NOT permitted in this assignment other than for GUI controls/components (ie. no global ArrayLists).
For timing estimates, perhaps 4 class days for Part A and 10 class days for Part B with all other work done in after-school homework time. These are just suggestions.
File Input/Output Assignment due November 11th, 2:10pm submitted as 'LastFirstFileIO' to the Classwork item where 'Last' is your surname and 'First' is your given name. The written responses are also due on the 11th, sent to your teacher's GAPPS email as an EMAIL response, NOT a GOOGLE DOC.
Object Oriented Programming Unit test - November 1 (Part A - Google Quiz) and November 3 (Part B - Programming)
Study hints are HERE
Coffee Klatch Assignment - Due Monday October 31st, 12:05pm, correctly packaged and submitted to classwork. Empty archives get a ZERO with no opportunity to resubmit. Do a re-import of your project into a DIFFERENT folder and test it to make sure it will import into your teacher's computer and run as you intend.
Starter Project is here. DOWNLOAD it. IMPORT it and use it. You may have to set 'Files of Type' to
'All files' to see it in the import dialog.
Video is here
Using the Formatted Print statement (printf).
Caesar Cipher Assignment is here - Due Tuesday October 4th by 2:45pm.
Review Unit Test - Thursday Sept 29th - in class time ON ROOM 305 Desktops. NO PERSONAL LAPTOPS.
DON'T BLOW THIS OFF .There are 21, 1 mark questions all multiple choice with ONE short answer entry.
Google Quiz format.
Short programming problem you will receive as an Email. You will reply with your java response.
No use of IDEs permitted. Test Hints are HERE.
Assignment - Java Challenge 0-5 Due date Wednesday September 28th at 2:10pm, submitted to the 'Java Challenge' Google Classroom classwork item. There may not be enough time in-class-only to complete this. You will probably have to work on it as homework as well.
The Demonstration Video is HERE
Your project will be created as, "LastFirstReviewAssignment" where 'Last' is your last name and 'First' is your first name. Example. For Frida Khalo, she would submit her project named, "KhaloFridaReviewAssignment".
The project will contain SIX(6) separate classes EXACTLY NAMED: 'PC0','PC1','PC2','PC3','PC4','PC5' (PC0 can just be the DEFAULT class)
Your teacher will run each FILE.
You will EXPORT the ONE PROJECT as a .zip file and submit it to the 'Review Assignment' in Google Classroom.
'RockPaperScissors' pseudocode GOOGLE SHEET - due Monday September 26th by 2:10pm, SHARED
WITH [email protected]
Pseudocode Guidelines for ICS at NHS
Clarification on Program PC3 - Basketball Stats
Arrays are NOT permitted in this problem's solution. They are not required.
For each player, the user will enter name, shots taken, shots made.
The average will be calculated and displayed for that player immediately.
After the last player information is entered and displayed, the best player will be displayed.
This means that you don't need to keep all the player name, shots taken, shots made data in arrays.
You just need to keep track of the current best player name and average.
No arrays required. Solutions submitted using arrays to store player/score data will get ZERO.
Clarification on Program PC4 - the Mountain Climber
If you look in the Notes section, you see the statement, "If the fatigue factor drops Nicholas' climbing distance below zero, he does not climb at all on that attempt."
That means his distance climbed is ZERO on that attempt.
The next point says, "Regardless of how far he has climbed, HE ALWAYS SLID D feet after a fall."
So on each term even if he climbs zero, he still falls.
So for the input of 25 10 1 50, the correct output is:
25 10 1 50
d=25.0
c=10.0
s=1.0
f=50.0
Attempt: 1 0.0 10.0 10.0 9.0
Attempt: 2 9.0 5.0 14.0 13.0
Attempt: 3 13.0 0.0 13.0 12.0
Attempt: 4 12.0 0.0 12.0 11.0 notice that since the climbing distance is now negative, he does not climb but he still falls.
Attempt: 5 11.0 0.0 11.0 10.0
Attempt: 6 10.0 0.0 10.0 9.0
Attempt: 7 9.0 0.0 9.0 8.0
Attempt: 8 8.0 0.0 8.0 7.0
Attempt: 9 7.0 0.0 7.0 6.0
Attempt: 10 6.0 0.0 6.0 5.0
Attempt: 11 5.0 0.0 5.0 4.0
Attempt: 12 4.0 0.0 4.0 3.0
Attempt: 13 3.0 0.0 3.0 2.0
Attempt: 14 2.0 0.0 2.0 1.0
Attempt: 15 1.0 0.0 1.0 0.0
Attempt: 16 0.0 0.0 0.0 -1.0
FAILURE ON ATTEMPT 16
-----------------------------------
When handing in an assignment, any diagnostic code that prints to the console should be removed prior to submission. It looks messy and unfinished. For any GUI projects, all console print statements should be removed prior to submission. An assignment is an opportunity for you to show your BEST work. Professional look and feel is part of that presentation. Communications marks will be deducted for diagnostic statements in submitted work.
Your projects/assignments will be TESTED on a standard install of Netbeans 8.2. You are responsible for assuring that your program runs as you expect it. Your teacher will not inform you if they are unable to run your program. DO TESTING LONG BEFORE YOUR PROJECT/ASSIGNMENT is due!
If the projects are not immediately openable from the associated programs/IDE, you will NOT receive full marks.
If you are doing a project at home and/or on your laptop, it is YOUR RESPONSIBILITY to get it into the appropriate Assignments submission item in Google Classroom by the due date.
Late Policy:
In compliance with Growing Success, you are given multiple and varied opportunities to demonstrate your learning. You are given AMPLE and GENEROUS in-class time to work on assignments on top of additional time outside of class you may need to complete assignments and submit them ON TIME.
Assignments submitted 1 to 4 days after the due date will receive a 5% deduction each day. So an assignment submitted 3 days after the published due date has 15% deducted from the assessed mark.
after 4 days, the assignment will be given a mark of 0%. This INCLUDES WEEKENDS.
Once the teacher has posted ANY marks for an assignment in TeachAssist, that is considered to be the 'zeros after today' marker (as long as the TeachAssist posting date is more than 4 days after the due date).
In ICS courses, 'Due Date' and 'Drop Dead Date' are the same.
Question: "May I use features in assignments/tests beyond those specified on the assignment rubrics/test questions?"
Answer: For tests, you will only receive marks for demonstrating your understand/use of concepts in the course curriculum. For assignments, you are welcome and always encouraged to explore concepts beyond those defined, but you will RECEIVE NO MARKS FOR THOSE EXTENDED CONCEPTS. They will not be evaluated in your fulfillment of rubrics. Assignments/ tests/quizzes are evaluated against the Ontario curriculum only.
Screen Size Limitations for your Assignments. Please read and follow this document.
Your program windows will be NO LARGER than 1000 pixels wide by 675 pixels high.
- Final Assignment - Airport Simulation - Assigned December 22nd, Due January 23rd.
You'll need to work on this at home too!(NOT over the Holiday Break). Worth 10% of final 30% of course. Late Marks will be deducted.
Sorting/Searching/Recursion Test Tuesday January 10th. Study Hints are Here
File IO Test Monday December 12th. Study Hints are Here
- Recursion Assignment - Due December 23rd a 2pm(extended from 12/22). Assigned on December 5th. This is a substantial assignment. Don't put it off. You'll need to work on this at home too!. Worth 20% of final 30% of course. Late Marks will be deducted.
Inspired by! Fred Flintsone!
Please name the project 'LastFirstRecursionA' for part A and 'LastFirstRecursionB' for part B. Submit them to the Classwork item by the due date.
Video of description of Part A
Here is Part A of the assignment. 'LastFirstRecursionA', where 'Last' is your Last Name and 'First is your First Name, and submit to the Classwork item by the due date. Global variables are NOT permitted in this assignment.
Here is Part B of the assignment. 'LastFirstRecursionB', where 'Last' is your Last Name and 'First is your First Name, and submit to the Classwork item by the due date. Global variables are NOT permitted in this assignment other than for GUI controls/components (ie. no global ArrayLists).
For timing estimates, perhaps 4 class days for Part A and 10 class days for Part B with all other work done in after-school homework time. These are just suggestions.
File Input/Output Assignment due November 11th, 2:10pm submitted as 'LastFirstFileIO' to the Classwork item where 'Last' is your surname and 'First' is your given name. The written responses are also due on the 11th, sent to your teacher's GAPPS email as an EMAIL response, NOT a GOOGLE DOC.
Object Oriented Programming Unit test - November 1 (Part A - Google Quiz) and November 3 (Part B - Programming)
Study hints are HERE
Coffee Klatch Assignment - Due Monday October 31st, 12:05pm, correctly packaged and submitted to classwork. Empty archives get a ZERO with no opportunity to resubmit. Do a re-import of your project into a DIFFERENT folder and test it to make sure it will import into your teacher's computer and run as you intend.
Starter Project is here. DOWNLOAD it. IMPORT it and use it. You may have to set 'Files of Type' to
'All files' to see it in the import dialog.
Video is here
Using the Formatted Print statement (printf).
Caesar Cipher Assignment is here - Due Tuesday October 4th by 2:45pm.
Review Unit Test - Thursday Sept 29th - in class time ON ROOM 305 Desktops. NO PERSONAL LAPTOPS.
DON'T BLOW THIS OFF .There are 21, 1 mark questions all multiple choice with ONE short answer entry.
Google Quiz format.
Short programming problem you will receive as an Email. You will reply with your java response.
No use of IDEs permitted. Test Hints are HERE.
Assignment - Java Challenge 0-5 Due date Wednesday September 28th at 2:10pm, submitted to the 'Java Challenge' Google Classroom classwork item. There may not be enough time in-class-only to complete this. You will probably have to work on it as homework as well.
The Demonstration Video is HERE
Your project will be created as, "LastFirstReviewAssignment" where 'Last' is your last name and 'First' is your first name. Example. For Frida Khalo, she would submit her project named, "KhaloFridaReviewAssignment".
The project will contain SIX(6) separate classes EXACTLY NAMED: 'PC0','PC1','PC2','PC3','PC4','PC5' (PC0 can just be the DEFAULT class)
Your teacher will run each FILE.
You will EXPORT the ONE PROJECT as a .zip file and submit it to the 'Review Assignment' in Google Classroom.
'RockPaperScissors' pseudocode GOOGLE SHEET - due Monday September 26th by 2:10pm, SHARED
WITH [email protected]
Pseudocode Guidelines for ICS at NHS
Clarification on Program PC3 - Basketball Stats
Arrays are NOT permitted in this problem's solution. They are not required.
For each player, the user will enter name, shots taken, shots made.
The average will be calculated and displayed for that player immediately.
After the last player information is entered and displayed, the best player will be displayed.
This means that you don't need to keep all the player name, shots taken, shots made data in arrays.
You just need to keep track of the current best player name and average.
No arrays required. Solutions submitted using arrays to store player/score data will get ZERO.
Clarification on Program PC4 - the Mountain Climber
If you look in the Notes section, you see the statement, "If the fatigue factor drops Nicholas' climbing distance below zero, he does not climb at all on that attempt."
That means his distance climbed is ZERO on that attempt.
The next point says, "Regardless of how far he has climbed, HE ALWAYS SLID D feet after a fall."
So on each term even if he climbs zero, he still falls.
So for the input of 25 10 1 50, the correct output is:
25 10 1 50
d=25.0
c=10.0
s=1.0
f=50.0
Attempt: 1 0.0 10.0 10.0 9.0
Attempt: 2 9.0 5.0 14.0 13.0
Attempt: 3 13.0 0.0 13.0 12.0
Attempt: 4 12.0 0.0 12.0 11.0 notice that since the climbing distance is now negative, he does not climb but he still falls.
Attempt: 5 11.0 0.0 11.0 10.0
Attempt: 6 10.0 0.0 10.0 9.0
Attempt: 7 9.0 0.0 9.0 8.0
Attempt: 8 8.0 0.0 8.0 7.0
Attempt: 9 7.0 0.0 7.0 6.0
Attempt: 10 6.0 0.0 6.0 5.0
Attempt: 11 5.0 0.0 5.0 4.0
Attempt: 12 4.0 0.0 4.0 3.0
Attempt: 13 3.0 0.0 3.0 2.0
Attempt: 14 2.0 0.0 2.0 1.0
Attempt: 15 1.0 0.0 1.0 0.0
Attempt: 16 0.0 0.0 0.0 -1.0
FAILURE ON ATTEMPT 16
-----------------------------------
When handing in an assignment, any diagnostic code that prints to the console should be removed prior to submission. It looks messy and unfinished. For any GUI projects, all console print statements should be removed prior to submission. An assignment is an opportunity for you to show your BEST work. Professional look and feel is part of that presentation. Communications marks will be deducted for diagnostic statements in submitted work.
Your projects/assignments will be TESTED on a standard install of Netbeans 8.2. You are responsible for assuring that your program runs as you expect it. Your teacher will not inform you if they are unable to run your program. DO TESTING LONG BEFORE YOUR PROJECT/ASSIGNMENT is due!
If the projects are not immediately openable from the associated programs/IDE, you will NOT receive full marks.
If you are doing a project at home and/or on your laptop, it is YOUR RESPONSIBILITY to get it into the appropriate Assignments submission item in Google Classroom by the due date.
Late Policy:
In compliance with Growing Success, you are given multiple and varied opportunities to demonstrate your learning. You are given AMPLE and GENEROUS in-class time to work on assignments on top of additional time outside of class you may need to complete assignments and submit them ON TIME.
Assignments submitted 1 to 4 days after the due date will receive a 5% deduction each day. So an assignment submitted 3 days after the published due date has 15% deducted from the assessed mark.
after 4 days, the assignment will be given a mark of 0%. This INCLUDES WEEKENDS.
Once the teacher has posted ANY marks for an assignment in TeachAssist, that is considered to be the 'zeros after today' marker (as long as the TeachAssist posting date is more than 4 days after the due date).
In ICS courses, 'Due Date' and 'Drop Dead Date' are the same.
Question: "May I use features in assignments/tests beyond those specified on the assignment rubrics/test questions?"
Answer: For tests, you will only receive marks for demonstrating your understand/use of concepts in the course curriculum. For assignments, you are welcome and always encouraged to explore concepts beyond those defined, but you will RECEIVE NO MARKS FOR THOSE EXTENDED CONCEPTS. They will not be evaluated in your fulfillment of rubrics. Assignments/ tests/quizzes are evaluated against the Ontario curriculum only.