CS 158 introduces the tools of software development that have become essential for innovating and creative problem solving in the disciplines of Science and Engineering. Educators and employers agree that it is important for future professionals 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.

• Collaboration is a requirement of the course. You will be assigned to your teams by your lab instructor.

CS 158 satisfies the College of Science Teamwork and Collaboration Experience degree requirement. The Principles portion of the Collaboration requirement must be fulfilled prior to enrolling in CS 158 or while concurrently taking CS 158. The SCI 210 course is an option for students attempting to complete both portions of this requirement during the same term. Please see your academic advisor for more information on this important degree requirement.

Pre-requisites/Preparation:

The University expects students to place 2-3 hours outside of class per week in preparation for each credit hour of a course. It is critical to being successful in this course that you investing in preparation and take initiative on assignments and review of course materials. The most successful students in previous offerings of CS 158 report habits such as reading the text, attending every lecture, reviewing material made available on-line, and daily code writing that goes beyond the minimum of completing assignments.

• CS 158 does have a co-requisite of ENGR 132.
  • Authorized equivalent courses or consent of instructor may be used in satisfying the course co-requisite.
• What does the co-requisite imply? ENGR 132 as a co-requisite would imply that you are (1) enrolled in a course that will expose you to the fundamentals of MATLAB or (2) have had some previous programming experience in a language such as C, C++, or JAVA. Most students in CS 158 will be enrolled ENGR 132 and will be introduced to writing programs in MATLAB using structured programming constructs.

Course Staff:

• Please visit during office hours for any administrative concerns regarding the course.
• Note that the phone number and e-mail address of the instructor are not listed above. If you have a concern that is important to you it is expected that you make the effort to visit William Crum's office hours.

Important Dates:

• Please make your travel arrangements accordingly. The final exam may be on Saturday December 15th from 3:20 - 5:20pm. Requests for alternative exam offerings will not be considered for reasons not outlined by the regulations of the university.

Blackboard Learn:

All relevant class information, updates, and announcements will be available on the CS 158 Blackboard site. On Blackboard you will find a course Twitter feed which will be used regularly to send reminders, notices, and assignments hints related to the course. Regular reminders 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 necessitate a revised semester calendar or other circumstances.

• In case of campus emergency, check Blackboard, do not email or call course staff.

• The instructor reserves the right to revise the syllabus with notice.

Course Required Materials:

• Computer Science, A Structured Programming Approach Using C, Forouzan and Gilberg, THIRD EDITION, ISBN: 0-534-49132-4
• Programming Applications for Engineers Course Packet (Fall 2012 edition)
• iClicker response pad (either version is compatible with CS 158). You must register your clicker with every class each semester. See the CS 158 Blackboard Learn site to register.

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.

• Collaborative groups are expected to communicate who will submit the assignment, when the assignment will be submitted, and how each successful submission will be reviewed to the satisfaction of all participating group members.

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 current assignments. Knowledge of course standards and good programming practices will be evaluated throughout the semester.

• The best way to prepare for lab quizzes is to actively participate with your team during the lab session including co-operating on both the written problems and the development of the programming problem solution.

Teaming Paper(1 total, 20 points):

End of term reflection paper related to your collaborative teaming experience in CS 158.

• Undergraduates in the College of Science using CS 158 this term to satisfy the collaborative experience requirement will incorporate their understanding of teaming principles with an emphasis on the Kolb Learning Styles into the reflection paper.
• All students will reflect on their collaborative experiences in CS 158 and the influence collaboration had on developing your understanding of programming and how you might have developed in your preparation as a future scientific or engineering professional.
• Full details on this assignment will be made available on and submission will be made through Blackboard Learn. The deadline for this assignment will be Friday November 30, 2012 at 11:00pm.

Homework Assignments(7 total, 5 points each):

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. Your iClicker must be registered by visiting the course Blackboard site. Visit ITaP in HSEE Library if you cannot read your clicker’s serial number. Should your pad malfunction, or if you forget your pad, you may submit a written quiz using only 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

• Please review the academic integrity policies regarding the misrepresentation of identity as it relates to participating in a lecture quiz for another student.

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 concepts and the interpretation of code. Note from the point distribution of the course that we feel being successful on exams is very important.

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 resuming course activities. Please silence your cell phone during lecture.

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.

• Groups are expected to communicate regarding the completion and submission of each lab programming assignment. Only one effort submitted by the group will be considered for grading. This is left to the descretion of the lab instruction as to which submission will be considered the official submission.

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.

• Any student missing more than two labs (unexcused) will receive a failing grade for the course. We feel that you must be present in lab as you are expected to function as part of a team. Secondly, you are receiving one credit (of the three for the course) based on the laboratory component of the course.

Grading:

Grades:

• 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 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.

Re-grade Request Policy:

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:

• The original graded assignment that was returned to you (if applicable).
• The reason you believe a re-grade is warranted. What did the grader overlook in the first evaluation?
• Note: A re-grade is not an extended opportunity to complete an assignment. It is not a means to challenge posted policies or specific requirements for a given assignment, such as the acceptance of late work or the requirement to make good use of user-defined functions.

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 should 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.

• University policies on absence and absence reporting are available on-line: http://www.purdue.edu/odos/services/classabsence.php
• Do not expect course obligations to be altered for reason of personal travel.
• Make-up requests for medical reasons MUST be accompanied by a physician’s note stating the dates you were under their professional care and the date you were cleared to return to school/work.

All assignments must comply with the programming and documentation standards of the course. 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.

Resources and course staff will be in high demand with requests for assistance 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 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.

Academic Integrity:

CS 158 applies very strict set of criteria regarding academic integrity and the consequences for violating course policies are not worth the points lost by not completing the assignment.

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 a copy of your work. Be very careful when working with others on individual assignments as this is 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 copy of your work left in the open. You are responsible for circumstances 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. 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 your own. Concerns regarding any of the academic integrity policies should be addressed during office hours.

Minimum consequences for violating course policies will include:

• First offense, a zero for the assignment, a reduction of one letter grade at the end of the semester, AND a referral to the Office of the Dean of Students for disciplinary action.
• Second offense, a zero for the assignment, a failing grade for the course, AND a referral to the Office of the Dean of Students for disciplinary action.
  • Penalties for being found in violation from the Office of the Dean of Students will typically range from disciplinary probation, to probated suspension, to dismissal from the University.

Exceptions to the minimum consequences:

• Any violation on an exam will result in a failing grade for the course and a Dean of Students referral.
• Acts such as a misrepresentation of identity will result in a failing grade for the course and a Dean of Students referral. (This includes lecture quizzes.)
  • You MUST refuse to assist another student by participating for them in a lecture quiz. The consequences listed above, for most students, aren’t worth the risk of being caught and most would rather disappoint their “friend” by refusing to comply with their request.
  • A process is already in place to deal with requests for make-up work. Students missing lecture for unexpected circumstances are to bring their situation to the office hours of the instructor.

Collaborative Learning/Teaming/Participating as a Member of a Technical Team:

Here are our expectations of you and your group:

1. Make time to meet with your group regularly. There are 168 hours in a week, finding a common time for two or three people to meet should not be difficult. It is acceptable for part of the group to meet some of the time if everyone cannot attend every meeting. It is the responsibility of each individual to plan their contribution to the group effort accordingly.
   • A group may exclude the name of a member from the lab assignment header as a means of indicating a lack of satisfactory contribution to the group assignment.
2. Allow everyone an opportunity to express their ideas on how to approach an assignment. One benefit of collaborative teaming is that everyone brings a different idea to the group and the resulting effort should be a stronger one than if it was completed individually.
   • When a group member becomes unresponsive to requests to meet or to update the other members of the group then those contributing members must continue without unresponsive member to submit the assignment by the deadline.
3. All group members must be satisfied with the final submission. It is not acceptable for a group to submit an assignment that is not approved by all group members. "It is good enough" may be true for you but it is unfair for the others in the group who strive for the strongest grade possible.
   • Likewise, each group member must be satisfied with your contribution to the group effort.
4. Each group member must fully understand the entire assignment submitted. Do not start your group meetings by trying to delegate the tasks to the different group members. Everyone must understand and contribute to every aspect of the assignment and its development.
   • Assignments are an opportunity for you to demonstrate your knowledge of the programming concepts being utilized. Additionally, an assignment can be used to serve as a measure of what you don't know to assist you in your course preparation.
   • Groups that delegate work in an effort to complete the assignment as quickly as possible often find that their comprehension of course material to be less than desired.
5. Designate who will turn in the assignment, when it will be turned in, and how successful submission will be communicated with the rest of the group. Only one person from the group will submit the assignment. Set a goal to submit the assignment well in advance of the due date to avoid any last minute problems related to group communication.
   • All groups are encourage to exchange that work which was developed in lab before leaving. This can be accomplished by making a submission with the Purdue e-mail address of each group member in the assignment header. If a group member becomes unresponsive outside of class the remaining group members have in their possession the work completed in lab without the need to start over.
   • Previous students have reported that communication is essential to a successful collaborative experience both during the lab and outside when attempting to complete the weekly assignment.
6. You will work with the group assigned. There is no other option in this course. Please see us with concerns you may have with your group. Take a professional approach with your group experience as similar to what you may experience while participating in a professional experience.
   • Groups will be re-assigned after every four labs.
   • Future group assignments may take into consideration lecture attendance and assignment submission as an indicator of your interest in participating in the course. Active students in the course should not be burdened with partners who are not willing to stay current with course content.

Schedules:

• Labs will NOT meet during "open" weeks unless warranted by an extenuating circumstance.

Course Syllabus Subject to Change with Notice