|
Department of Computer Science |
||||
|
|||||
Course Objectives:
CS 159 introduces the tools of software development that have become valuable for creative problem solving in Engineering. We believe that it is important for future Engineering professionals to be able to function as part of a technical team and will require students to work in assigned teams for lab assignments. Educational research informs us that structured collaboration leads to increased learning gains for students participating in an introductory programming course.
CS 159 explores programming concepts in multiple computing environments and will require implementation of solutions in more than one programming language. Our goals are for you to recognize how programming concepts are common to a variety of programming languages and how those concepts can be used to solve a problem.
Pre-requisites/Preparation:
The University asks students to place 2-3 hours outside of class per week in preparation for each credit hour of a course. The key to success in this course requires preparation and taking initiative. The most successful students in previous offerings of CS 159 report habits such as reading the text, attending every lecture, and daily code writing that goes beyond the minimum of completing assignments.
Instructor: William Crum Office Location: HAAS G-26 |
Instructor Office Hours (HAAS G-26):
|
Additional TA Office Hours (HAAS G-24):
|
|
Midterm Exam #1 | Midterm Exam #2 | Final Exam | Academic Calendar |
Date: Tuesday October 5, 2010 Location: Loeb Playhouse |
Date: Wednesday November 10, 2010 Location: Loeb Playhouse |
Date and Location: TBA |
Last Day to Drop: |
Blackboard:
All relevant class information, updates, and announcements will be available on the CS 159 Blackboard site. Regular announcements will be posted on the "message of the day" which is visible when you log into your UNIX account. It is expected that you check both frequently for updates.
In the event of a major campus emergency, course requirements, deadlines, and grading percentages are subject to changes that may be necessitated by a revised semester calendar or other circumstances.
Course Required Materials:
Assignments:
Lab Assignments (12 total, 5 points each):
Lab assignments are to be completed collaboratively in your assigned lab groups and each of these lab assignments will be due 30 minutes prior to your next lab meeting.
Lab Quizzes (12 total, 5 points each):
At the end of every lab there will be an individual assessment of your knowledge related to the topics implemented in the most recent assignments. Knowledge of course standards and good programming practices will be evaluated throughout the semester.
Homework Assignments (7 total, 5 points each):
All assignments will be posted on Blackboard 10-14 days before they are due. |
Homework Assignment |
Due at 11pm on |
1 |
September 6 |
|
2 |
September 20 |
|
3 |
October 4 |
|
4 |
October 18 |
|
5 |
November 1 |
|
6 |
November 15 |
|
7 |
November 29 |
Lecture Quiz (50 total points possible):
Dates of in-lecture quizzes will not be made known in advance, you should assume a quiz will take place at each and every lecture meeting. Quizzes may take place at the start of lecture, in the middle, and/or at the end of lecture.
iClicker response pads are required to participate in lecture quizzes. You should bring your response pad to every lecture. Should your pad fail, or if you forget your pad, you may submit a written quiz using the form found in the back of your notes packet. You may only utilize this method once during the semester. Only the form provided in the current version of the packet will be accepted.
Exams (two midterms 100 points each, one final exam 150 points):
Exams will be individual assessments of your knowledge. Exams will consist of multiple-choice problems. You will notice from the point distribution of the course that we feel being competent on exams is very important. You need to be able to communicate intelligently with others, including supervisors, on this topic without needing to be in front of a computer to demonstrate what you know.
Lecture Policies:
You are expected to arrive to lecture on time and to remain attentive. Disruptive students will be excused from lecture and asked to meet with course staff before returning to class. Please silence your cell phone during lecture. Lecture seats will be assigned by section and group. Check Blackboard for your seat assignment.
Lab Policies:
CS 159 labs will meet weekly (see lab schedule). You are expected to attend and to participate in every lab this semester. All lab assignments (as described previously) will be completed in collaborative teams assigned by your lab instructor. These lab assignments will be due 30 minutes before the start of your next lab and may require that your team meet outside of lab to complete the assignment.
Because of our use of teaming, no points will be given to a student who is absent from, or late arriving to, a lab. If you are going to have a regular conflict with your lab time, please change sections.
Assignment | Points |
Homework |
35 |
Lab Tasks |
60 |
Midterms |
200 |
Final |
150 |
Lecture Quizzes |
50 |
Lab Quizzes |
60 |
Total: |
555 |
Grades:
Grade | Points Required |
A |
470 |
B |
415 |
C |
360 |
D |
305 |
An equivalent number of points to earn a C are needed to receive a Pass if taking the course Pass/No Pass. It is recommended that graduate students in the course elect this option (see your advisor).
The instructor
reserves the right to lower the minimum score required for each letter
grade. If such a move is made it will not be announced until after the final
exam. At no time during the semester will it be speculated on if this will
be done or "how much" any given cutoff will be lowered. You should
have no expectation that all cutoffs if moved will be moved by an equal
amount.
|
To request a re-grade on any assignment you must formally make your request in writing to the instructor during office hours. You have five days to appeal any grade from the day the assignment is returned to you. After that period the grades are frozen and no appeal will be considered.
A re-grade request must include the following:
Absences:
Only documented serious hardships will be considered for any make-up work.
If you have documentation of what you consider to be a serious hardship then you should contact the instructor in a timely manner during office hours. Any student who knows in advance of a coming absence must make a request for consideration one week prior to the planned absence.
Important Assignment Guidelines:
All assignments must abide by the programming and
documentation standards of the course. In ALL cases no credit will
be given for programs that do not compile (that is, execution is suppressed due
to compilation errors) or are un-testable (MATLAB). Programs that execute
and meet minimum assignment requirements but are not correct or complete will be
considered for partial credit. To receive full credit, your program must
produce correct results, be well-designed, be efficient, follow assignment
requirements, and adhere to course programming and documentation standards.
An assignment that is not submitted as expected cannot be considered for a grade. Only work submitted correctly prior to the assignment deadline can be considered for grading. Late work is not accepted. |
Resources and course staff may become heavily loaded as an assignment deadline nears. Waiting until the last minute to work on your project is dangerous! Our policy is NOT to extend deadlines unless campus resources (not your local ISP) are unavailable for an extended period near the deadline for an assignment.
ITaP’s Outage (scheduled and unscheduled) Notification
RSS Feed:
http://www.itap.purdue.edu/web/infrastructure/operations/change/unscheduled/unscheduled_RSS.xml
You are responsible for knowing how to use the technology utilized by the course, this includes but is not limited to UNIX and related course tools such as the assignment submission script.
|
Collaborative Learning/Teaming/Participating as a Member of a Technical Team:
Here are our expectations of you and your group:
CS 159 applies very strict set of criteria regarding academic integrity and the consequences for violating course policies are serious.
You are encouraged to discuss any CS 159 topic including ideas about how to complete assignments. But, under no circumstances will exchange of code via written or electronic means be permitted between teams for collaborative assignments or individuals for individual assignments. It is considered dishonest either to read another team's solution or to provide anyone with a copy of your work. Be very careful when working with others on individual assignments as this is generally discouraged. The work you submit must be your own original effort.
|
Every student is responsible for protecting his/her own work. Do not make the assumption that roommates, neighbors, significant others, or other "trusted" individuals would not take advantage of knowing your password, having access to your computer (use a password protected screen saver, logout when done), or finding a stray copy of your work left on a printer. You are responsible for such events that leave your work unprotected.
Do not make the mistake of thinking that superficial changes in a program (such as altering comments, changing variable names, or interchanging statements) will avoid detection. If you cannot do the work yourself, it is extremely unlikely that you will succeed in disguising someone else's work as your own. We are adamant that violations in any form will not be tolerated. Even the most trivial assignment is better not done than if you violate course integrity policies to complete it.
|
Assume that every submission you make during the semester will be analyzed by a software similarity service. This service will return the percentage of similarity between your solution and those submitted by others in the course. The service indicates the number of lines matched. You will be solving problems this semester that have no unique solution and your solution is expected to be uniquely yours. Concerns regarding any of our policies should be addressed during office hours.
The software service utilized is not for profit. The service does not retain your file. The course will retain your files for the purpose of record keeping for the current semester and may retain your files for similarity comparisons in future semesters. |
Minimum consequences for violating course policies will include:
Exceptions to the minimum consequences:
CS 159 Lab Schedule
|
|
Week of | Lab Assignment |
August 23 | Lab #0 |
August 30 | Lab #1 |
September 6 | Lab #2 |
September 13 | Lab #3 |
September 20 | Lab #4 |
September 27 | Lab #5 |
October 4 | Lab #6 |
October 11 | NO LAB |
October 18 | Lab #7 |
October 25 | Lab #8 |
November 1 | Lab #9 |
November 8 | Lab #10 |
November 15 | Lab #11 |
November 22 | NO LAB |
November 29 | Lab #12 |
December 6 | OPEN |
December 13 | Finals Week - No Lab |
CS 159 Topic Schedule |
||
Week of | Tuesday | Thursday |
August 23 | Introduction | UNIX and Chapter1 |
August 30 |
Chapter 1 & 2 |
Chapter 2 & 3 |
September 6 | Chapter 3 | Chapter 4 |
September 13 | Chapter 4 | Chapter 4 |
September 20 | Problem Solving Techniques | Problem Solving Techniques |
September 27 | Chapter 5 | Chapter 5 |
October 4 | Chapter 5 & 6 | No Lecture - Midterm #1 Compensation |
October 11 | No Lecture - October Break | Chapter 6 |
October 18 | Chapter 6 | MATLAB File I/O |
October 25 | MATLAB File I/O | Chapter 8 |
November 1 | Chapter 8 | Chapter 8 |
November 8 | Chapter 8 | Chapter 8 |
November 15 | Chapter 8 & 11 | Chapter 11 |
November 22 | No Lecture - Midterm #2 Compensation | No Lecture - Thanksgiving Break |
November 29 | Chapter 9 & 10 | Chapter 9 & 10 |
December 6 | Chapter 12 | Chapter 12 |
December 13 | Final Exam Week |
Course Syllabus Subject to Change with Notice