|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Assignments
Programming exercises will consist of smaller problems
that help you build your problem solving skills towards solving larger
problems. We expect exercises to acquaint you with skills needed for projects
and exams. To reduce stress, these smaller exercises are worth a relatively
"small" percentage of the course score. We grade exercises based on your
success in completing the assigned task. Plus, we will not require you
to do all the exercises perfectly to get a perfect exercise score (see
Grading, above). Thus, as long as you make a sincere effort on most
of the exercises, you should get a good exercise score.
For written problems, you can download the assignments, provided below. We may also post problems during lecture, section, and on the website:
|
|
|
|
|
|
|
|
Thu 8/31 |
|
e1.txt | e1sol.txt |
| 2 |
|
|
Chapman Exercises: 2.1a-b, 2.2a-e, 2.5, 2.7a-i, 2.8a-b, 2.11. Do all work in an M-File. Include all output with your submission. Follow all rules listed below in the Submission Rules. | e2a_sol |
| 3 |
|
Thu 9/14 | Chapman 3.4 (pg 111) | e3sol.txt |
| 4 |
|
|
Do problems 1 & 2 from Project 3 (see Section 5 of the writeup). Yes, partners are allowed but you must work with the same partner that you will have for Project 3. | manualmethod.m |
| 5 |
|
|
Do problems 3 & 4 from Project 3 (see Section 5 of the writeup). Yes, partners are allowed but you must work with the same partner that you will have for Project 3. | exactmethod.m
lhsrhsmethod.m |
| 6 |
|
Tue 10/12 | This will either count as a makeup or bonus, depending on whether or not you missed an exercise so far. Do Chapman 7.1 & 7.2, pg 282. | 7.1)
c_sort1.m c_strcmp.m test_c_sort1.m 7.2) <coming> |
| 7 | Tue 10/17 | Thu 10/19 | Problem 2.13 (Java, p56). Use variable assignments for data -- do not obtain anything from user input for now. | |
| 8 | Tue 10/30 | Thu 11/2 | Draw the box scope diagrams for the code in lecture19.java. You will draw 3 diagrams for states of the code. The diagrams should represent the execution of all all code up to each line indicated in the file. Neatness counts! You may want to copy Part 1, which will be used for Part 2. Then, you may want to copy Part 2, which will be used for Part 3. | box1.pdf
box2.pdf box3.pdf |
| 9 | Tue 11/7 | Thu 11/9 | Draw the box scope diagrams for the point indicated in exercise9.java. You should try to predict the output before actually running the code. | exercise9.java
boxes.jpg |
| 10 | Thu 11/16 | Tue 11/21 | Chapman, problems 5.5, 5.12 | exercise10
DotProduct.java PolarToRect.java |
Back to Top
Quizzes
Sometimes these assignments will consist of in-class
pop quizzes, so we encourage you to attend lecture.
Back to Top
Grading
Each programming exercise will
receive one grade of usually 0-1 points. You must submit your own work,
though we encourage you to consult with classmates if you get stuck. That's
right - unlike projects, NO PARTNERS! Look here
for more information.
We allow you to miss 2 exercises and still receive a perfect exercise score.
Back to Top
For each exercise, you must do the following:
Note: Unless specified otherwise, submit work as hardcopy, not as e-mail or on disk!Staple or bind all sheets of paper. "Bind" means ring or folder, not twist-ties, string, or such nuisances. Submit entire code unless directed otherwise. Type all work and responses to discussion questions. Include a comment block that includes your name, ID, section, section instructor, exercise number, and date as the first lines of each program you submit. Ensure correct alignment of tab stops in programs with no "chopped" line of code.
Back to Top
Retrieving
Graded Exercises
Where's your work?
Look here if you wish to submit a regrade.Programs are usually graded in about 1 week. Due to lack of resources, we might need to restrict returning exercises in Carpenter.
Back to Top
Academic
Integrity
Respect academic integrity! Please review the Code and
notes for CS100
here.
Back to Top