This course introduces the perspectives and methods of computer science. Symbolic information is represented as data, whether it be numbers, text, or images. Automated processes for operating on the data are represented by general procedures, known as algorithms. Those algorithms are written in a particular notation (a programming language) as programs. Students will learn how to carry out these tasks and how to think about computation in terms of general patterns, such as hierarchical composition or the use of interchangeable components with consistent interfaces.
Louis Yu will be the classroom instructor. Max Hailperin will be the lab instructors. For information regarding our availability, please see our contact info.
All course materials will be available through my World Wide Web page. The URL for this course is http://homepages.gac.edu/~lyu/teaching/mcs178-s14/.
Our textbook is Python Programming in Context by Bradley N. Miller and David L. Ranum. I recommend that you order a copy in advance, either through the Book Mark or through another seller of your choice. the Book Mark cannot be counted on to have a copy on the shelf if you don't pre-order.
There are two editions of this book, the first and second editions. The second edition has had errors fixed and a few technical items updated. As such, it will provide the smoothest experience. However, the differences in the first edition, are minor and we can definitely help you work through its little glitches. You are likely to be able to get a better price on a used copy of the first edition. For this reason, we suggested the Book Mark stock the first edition. For a list of corrections to the first edition of the textbook, please see http://pycontext.blogspot.com/.
You are expected to read the relevant Chapters specified in the schedule before each lecture, as the lectures are meant to supplement your reading (note that lectures are NOT substitutes for reading). After each lecture I will assign practice problems from the corresponding Chapter in the textbook. Finishing these exercises will renforce your understanding of the material and be very helpful in preparing for the tests and the final.
Attendance, both physical and mental, is required. I reserve the right to lower your
grade if I feel you are missing or showing up late too often.
Should you need to miss a class or lab for any reason, you are still responsible for
the material covered in there. This means that you will need to make sure
that you understand the reading for that day, that you should ask another student
for the notes from that day, and that you make sure that you understand what was covered.
If there is a project due that day, you should be sure to submit it (electronically) on time (thus, do not leave your project to the last minute). You do not need to explain why you missed a class
unless there is a compelling reason to do so.
If you have influenza-like symptoms (temperature over 100 with headaches, sore throat,
or cough), please call Health Service. If they say that you stay home, you should do so,
and I request (but do not require) that you email me.
In the course of the semester, you will complete 10 projects. In each case, I will indicate what I expect of you.
A project report that meets those expectations is due before the start of class on the date specified. If you submit
the report late, your grade will drop one point per day late or fraction thereof.
If you are too sick to complete a report on time, you will not be penalized. However, you need to talk to me or email me as soon as possible, and provide the necessary doctor's note. Other circumstances will be evaluated on a case-by-case basis. In general, you should talk to me or email me (asap) around the time of the incident.
On Tuesdays and Thursdays, we will meet in the OHS 326 computer lab. One or more of those lab days will be
provided for you to work on each project. However, you will often need to spend additional time on the project
outside of class.
In general, the projects will be posted 3 days before we start working on it in the corresponding lab. I expect you to read and understand the project before we start working on it. Please do not wait until the lab starts to read the project description (thus wasting precious lab time).
Some of the lab days are not for project work. Instead, the syllabus lists a topic from the textbook with the prefix
"In lab:". On these days, I will be covering material from the book, somewhat like on a class day, but in an
environment where I can ask each of you to try things out on your individual computers. For each of these days where a textbook topic
is covered in lab, the same topic is listed on the following class day. We will have this extra class time to go over
the topic some more if you need it. Any remaining time will be available for us to talk about topics that are not in
the textbook.
In class, you will be given exercises to work on in groups of two or three. You will practice writing programs by hand (without the help of a computer). This will also help you preparing for the tests and the final (as similar time constraint per question will be applied to the in-class exercises). These exercises will be given at random times and collected for grading. At the end of the semester, 4 in-class exercises will be chosen at random to count towards your final grade. There will not be any make-up for in-class exercises; thus class attendance is important.
If a group have trouble finishing a in-class exercise within the given time. They may choose to work on it at home and hand it in before the start of the next lecture. In that case, a penalty of one point will be applied to the late submission.
After lecture, you will be given exercises to work on individually at home. These problems are designed to help you further understanding the class materials at your own pace. The homework exercises are due before the start of the next lecture. At the end of the semester, 4 homework exercises will be chosen at random to count towards your final grade. There will not be any make-up for homework exercises.
There will be two in-class tests during the semester and a final exam as scheduled by the registrar. If you have a
conflict with a testing time, please contact me as soon as possible to make an alternative arrangement.
Tests will be closed-book and mostly closed-notes. You may, however, use a single 8 1/2 by 11 sheet of paper with
hand-written notes for reference (written on both sides of the sheet are OK).
You will earn up to 440 grade points for your work on projects, in-class exercises, homework exercises and tests, divided as follows. Each of the 10 projects will be graded on a scale of 20 points, totaling 200 points. Each in-class exercise is worth 5 points, and 4 of them will be chosen at random, totaling 20 points. Each homework exercise is worth 5 points, and 4 of them will be chosen at random, totaling 20 points. Each of the two tests that happens during the semester, in class, will be graded on a scale of 50 points, for 100 more points. The remaining 100 points will come from the comprehensive final exam. Your course grade will be recorded as follows:
| A: 408-440 | B+: 379-393 | C+: 335-349 | D+: 291-305 | F: 0-261 |
| A-: 394-407 | B: 364-378 | C: 320-334 | D: 262-290 | |
| B-: 350-363 | C-: 306-319 |
Please point out any arithmetic or clerical error I make in grading, and I will gladly fix it. You may also request
reconsideration if you feel I have been especially unjust.
As noted above, I reserve the right to lower your grade if I feel you are missing or showing up late too often to
classes or labs.
Finally, this semester we are using Moodle (http://moodle.gac.edu/) to keep track of your scores. The pro of doing so is that you know your score for a component as soon as it is graded. This will give you a pretty good idea of your current standing going into a test or an exam. Please see The Guide for Checking Your Grades Using Moodle for the general updating schedule and the instructions for checking your scores using Moodle.
Any substantive contribution to your project report by another person or taken from a web site or publication should be properly acknowledged in writing (by citing the source). Failure to do so is plagiarism and will necessitate disciplinary action.
The same standards regarding plagiarism apply to team projects as to the work of individuals, except that the author is now the entire team rather than an individual. Anything taken from a source outside the team should be be properly cited.
As a guideline for collaboration, it is ok for students to get together in small groups to go over material from the lectures and text, solve problems from the text, study for exams, and discuss the general ideas and approaches to projects. However, work to be turned in, including projects and homework exercises, must be done independently. This means that the work you or your team turns in must represent only your own work. It must not be based on help from others or information obtained from sources other than those approved by the instructors (e.g., the text, web pages linked from the course web page, and materials provided in the lectures). Effective learning is compromised when this is not the case.
Accordingly, you should never read or copy another student's code or solutions, exchange computer files (or pieces of papers with solutions written on them), or share your code/solutions with anyone else in the class until after both parties have submitted the assignment. Under no circumstances may you or your team hand in work done by someone else under your own name.
One additional issue that arises from the team authorship of project reports is that all team members must stand behind all reports bearing their names. All team members have quality assurance responsibility for the entire project. If there is irreconcilable disagreement within the team it is necessary to indicate as much in the report.
As a student at Gustavus you are expected to uphold the Honor Code and abide by the Academic Honesty Policy. A copy of the honor code can be found in the
Academic
Bulletin and a copy of the academic honesty policy can be found in the
Academic Polices section of the
Gustavus Guide.
Section 504 of the Rehabilitation Art of 1973 and the Americans with Disabilities Act (1990) work together to ensure "reasonable accommodation" and non-discrimination for students with disabilities in higher education. A student who has a physical, psychiatric/emotional, medical, learning, or attentional disability that may have an effect on the student's ability to complete assigned course work should contact the Disability Services Coordinator in the Advising Center, who will review the concerns and decide with the student what accommodations are necessary. Disability Services Coordinator Laurie Bickett (6286) can provide further information.
The Writing Center has on staff a part-time tutor with professional training in ESL/ELL instruction. Students can schedule work with this tutor by contacting the Writing Center. Students may bring their instructor's documentation concerning their ELL status. Where it is appropriate, faculty may choose to allow such students more time to complete either in- or out-of-class writing assignments. For further information, contact the Academic Advising Office.