|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Assignments
Programming assignments will help you build your problem
solving skills. We will have approximately 1 assignment per week for a
total around 10. You can download the assignments, provided below:
|
|
|
|
|
week of 9/4 |
|
|
2 | during lecture
Mon 9/18 or Tue 9/19 |
Chapter 2: Problems 1-20 | project2.mws |
3 | during lecture
Mon 9/25 or Tue 9/26 |
Chapter 3: Problems 1-21, all parts | project3.mws |
4 | during lecture
Wed 10/4 or Thu 10/5 |
Chapter 4: Problems 1-16, all parts | project4.mws |
5 | during lab
Wed 10/18 or Thu 10/19 |
Chapter 5: Problems 1-9, all parts | project5.mws |
6 | 11/3
see assignment for details |
Use this: project6.mws | project6sol.mws |
7 | 11/10 for bonus points
11/15 and 11/16 (in lab) see assignment for details |
Use this: project7.mws | project7sol.mws |
8 | 12/4
Worth 20 points |
Use this: project8.mws | project8sol.mws |
Back to Top
Grading
Each programming project will receive
one grade composed of three parts:
You can score 0-5 on both correctness and style which yields a total of 10 points per assignment. Note: for the first half of the course, the projects will usually consist of just correctness points. For example, you might receive a score of C4 and S4 for one project where you satisfy a majority of the requirements of the assignment. Graders might assign bonus points to reward additional/exceptional work. Look here for more information. We record your score in the form C/S/B. For instance, a 3/4/1 indicates a score of C3, S5, and 1 bonus point.correctness (C) style (S) bonus (B)
If you work with a partner, both you and your partner will receive the same grade for that assignment. See below for information about having partners.
Back to Top
To reduce stress, we will not require you to do all the assignements perfectly to get a perfect project score (see Grading, above). Most students will get at least 7/10 Thus, as long as you make a sincere effort on most of thework, you should get a good assignment score.
Back to Top
Back to Top
For each project you must do the following:
Back to TopUnless otherwise specified, do all work in Maple! Print all your work as hardcopy, such as programs, output, and discussion answers. Do not include disks or e-mail, though we may ask for these forms later in the semester. Staple or bind together 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 the following comment block with your information filled in at the top of each program:
Name: your name Partner: partner's name ID: your ID ID: partner's ID Lecture: your lecture's day, time Lecture: partner's lecture's day, time Date: due date Assignment: number and title
Look here if you wish to submit a regrade.Projects are usually graded in about 1 week. We return graded assignments in lecture/lab. You may retrieve unclaimed assignments from the consultants at Carpenter Lab at the end of the week in which they were returned in sections.
Back to Top
Partners
We encourage you to work with a partner on the programming
projects. (Why, or why not? Look here.)
If you work with a partner, you must adhere to the following
rules:
If you have any questions, please do not hesitate to ask the staff.You can have only one partner for each project. You cannot have different partners for different parts of the project. You can pick a different partner for each project. You and your partner receive the same correctness and style grade for the entire project. You and your partner may attend different sections. You must submit only one project with both your names, IDs, signatures, and section information, as specified in the Submission Rules. You cannot take your exams with a partner. You should avoid "divorcing" partners before submitting your project. Why? What if your partner submits a duplicate version of your programs? All the graders will see is an academic violation, so be careful.
Back to Top
Back to Top