|
Department of Computer Science |
||||
|
|||||
Course Objectives:
CS 158 introduces the tools of software development that have become essential for creative problem solving in Science and Engineering. Educators and employers agree that it is important for future Scientists and Engineers to be able to function as part of a technical team and CS 158 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.
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, taking initiative on assignments, and regular review of course materials. The most successful students in previous offerings of CS 158 report habits such as reading the text, attending every lecture, and daily code writing that goes beyond the minimum of completing assignments.
Supplemental Instruction:
There are Supplemental Instruction (SI) student sessions available for this course. These student groups are open to anyone enrolled in this course who would like to stay current with the course material and understand it better. Attendance at these sessions is voluntary, but for the maximum benefit you should attend regularly. Time and locations for the study sessions can be found on-line: http://www.purdue.edu/si.
Students who attend these interactive sessions will find themselves working with peers as they compare notes, demonstrate and discuss relevant problems and important concepts, and share study and test-taking strategies.
Instructor: William Crum Office Location: HAAS G-26 |
Instructor Office Hours (HAAS G-26):
|
Additional TA Office Hours (HAAS G-25):
|
|
Please visit during office hours for any administrative concerns regarding the course.
Midterm Exam #1 | Midterm Exam #2 | Final Exam | Academic Calendar |
Date: February 26, 2014 Location: Hall of Music |
Date: April 8, 2014 Location: Hall of Music |
Date: Location: |
Last Day to Drop: |
Blackboard Learn (mycourses.purdue.edu):
All relevant class information, updates, and announcements will be available on the Blackboard Learn site. This includes a course Twitter feed which will be used regularly to send reminders, notices, and hints related to the course.
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 programming 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 introduced in lecture and implemented in the most recent assignments. Knowledge of course standards and good programming practices will be evaluated throughout the semester.
Teaming Paper (1 total, 20 points):
End of term reflection paper related to your collaborative teaming experiences in CS 158.
Homework Assignments(7 total, 5 points each):
All assignments will be posted on Blackboard Learn 10-14 days before they are due. Please review the course policies as they relate to academic integrity found later in this document. |
Homework Assignment |
Due at 11pm on |
1 |
January 27 |
|
2 |
February 10 |
|
3 |
February 24 |
|
4 |
March 10 |
|
5 |
March 31 |
|
6 |
April 14 |
|
7 |
April 28 |
Lecture Quiz (60 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. Your iClicker must be registered by visiting the course Blackboard Learn site. Visit ITaP in HSEE Library (main floor) if you cannot read your serial number. 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 course notes packet will be accepted
Pre-lecture quizzes will be posted on Blackboard Learn throughout the semester along with an accompanying video demonstration. The availability of new demonstrations and quizzes will be announced in lecture.
Lecture Policies:
|
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 covering programming concepts, best programming practices, lab and homework assignments, and the interpretation of code. Note from the point distribution of the course that being successful on exams is very important.
Lab Policies:
CS 158 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. 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 | 60 |
Lab Quizzes | 60 |
Teaming Paper | 20 |
Total: |
585 |
Grades:
Grade | Points Required |
A |
495 |
B |
435 |
C |
375 |
D |
315 |
|
To request a re-grade on any assignment you must 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 as circumstance for any potential make-up of missed work.
If you have documentation of what you consider to be a serious hardship then you must contact the instructor in a timely manner during office hours when you are able to resume participating in class. Any student who knows in advance of an 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. Programs that execute and meet minimum assignment requirements but are not logically correct or complete may 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.
|
Resources and course staff may become heavily loaded as an assignment deadline nears. Waiting until the last minute to work on your project is discouraged! Course policy is NOT to extend deadlines unless campus resources (not your local ISP) are widespread and unavailable for an extended period near the deadline for an assignment.
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.
Be sure your account is set-up correctly as introduced during the first lab meeting of the semester.
|
CS 158 applies very detailed set of criteria that is enforced rigorously related to academic integrity. The consequences for violating course policies are serious.
You are encouraged to discuss any CS 158 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 access to your work (or that of another student). 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 and not the result of unacceptable, even if unintentional, collaboration.
|
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, log out when done), or finding a stray copy of your work left on a printer or your desk. 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 are unable to complete the work yourself, it is extremely unlikely that you will succeed in disguising the work of another 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. Additionally, the service indicates the number of lines matched among submissions. 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 prior to the deadline of an assignment.
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:
Collaborative Learning/Teaming/Participating as a Member of a Technical Team:
Here are our expectations of you and your group:
CS 158 Lab Schedule |
|
Week of | Lab Assignment |
January 13 | Account Set-Up Exercises |
January 20 | Lab #1 |
January 27 | Lab #2 |
February 3 | Lab #3 |
February 10 | Lab #4 |
February 17 | Lab #5 |
February 24 | OPEN* |
March 3 | Lab #6 |
March 10 | Lab #7 |
March 17 | Spring Break |
March 24 | Lab #8 |
March 31 | Lab #9 |
April 7 | Lab #10 |
April 14 | Lab #11 |
April 21 | Lab #12 |
April 28 | OPEN* |
May 5 | Finals Week |
CS 158 Topic Schedule |
||
Week of | Tuesday | Thursday |
January 13 | Introduction | UNIX and Chapter 1 |
January 20 | Chapters 1 and 2 | Chapter 2 |
January 27 | Chapter 3 | Chapter 3 |
February 3 | Chapter 4 | Chapter 4 |
February 10 | Chapter 4 | Chapter 4 |
February 17 | Chapter 5 | Chapter 5 |
February 24 | Chapter 5 | No lecture midterm compensation |
March 3 | Chapter 6 | Chapter 6 |
March 10 | Chapter 6 | Chapter 6 |
March 17 | Spring Break | |
March 24 | Chapter 7 | Chapter 7 |
March 31 | Chapter 8 | Chapter 8 |
April 7 | No lecture midterm compensation | Chapter 8 |
April 14 | Chapter 8 | Chapter 8 |
April 21 | Chapter 11 | Chapter 11 |
April 28 | Chapter 9 & 10 | Chapter 9 & 10 |
May 5 | Final Exam Week |
Course Syllabus Subject to Change with Notice