CS212: Course Information

Contents

0. Policies

You are responsible for the information in this document and the complete list of policies on the course website.

1. Course Description

2. Course Objectives

In CS212, you are expected to do the following:

• Improve your programming skills.
• Implement principles of software engineering, which include top-down and bottom-up design, software reuse, abstraction, and testing.
• Develop interpersonal and project management skills, which you need for later courses.
• Learn about the field of computer science.

To help you develop these skills, you will work on a large-scale project that we split into four assignments. The assignment is described below in Project. The course topics will be listed along with lecture notes at the Notes & Examples link.

3. When To Take CS212

CS212 is a one-credit project course that the computer science major requires. Students may either take CS212 simultaneously with CS211 or afterwards, though we recommend taking CS212 as a co-requisite. For more information, see CS211 Course Information.

4. Staff

5. Lecture

5.1 Requirements

You are expected to attend all lectures.

5.2 Registration Information

Note that there is no "ENGRD 212."

5.3 Conduct

We expect the following to improve the effectiveness of lecture for all students:

• You will arrive on time.
• You will not walk in front of the instructor at any time.
• You will turn off all cell phones, beepers, pagers, and any other device that will interrupt the lecture.
• You may use a portable computer, such as a laptop or PDA as long as you turn the volume off.
• You may not read the newspaper during lecture.
• You should raise your hand to ask a question, though if you're being missed, you should politely call out.

Generally, we prefer class participation, so please feel free to raise your hand to ask a question.

5.4 Lecture Notes

We put most of my files for lecture notes, corresponding readings, and examples at the Notes&Examples link, usually just before or after lecture. Not all material covered in lecture will necessarily be on-line. However, sometimes it's the reverse scenario, so you are responsible for this material.

6. Section

We will occasionally use sections. Specific dates will be announced on-line and in lecture.

7. Communication

You are responsible for the following forms of communication:

• Attending all classes, where we usually make announcements.
• Monitoring website announcements every day. Click on Home.
• Monitoring the newsgroup cornell.class.cs212. If you have trouble using the newsgroup, refer to the USENET Information document for help on accessing the newsgroup.
• Reading your e-mail, especially when dealing with emergencies and handling conflicts.

To reach a staff member, the best time is in office hours. Please post general questions on the newsgroup so that others can benefit from your question. We will usually copy important questions and answers in FAQ files at the Project link.

8. Project

8.1 General Information

You will have four homework assignments this semester. Each assignment contributes to an overall project that takes the semester to complete. So, each assignment is called a part, using the simple abbreviation of p. During lecture, we will usually give tips on anticipating the next part so that you can work ahead.

To achieve the course objectives, the project involves writing a compiler that translates one computer language (Bali) into another (Sam). Learning how to write the compiler will help to bridge the "gap" between introductory programming courses and more in-depth courses, such as CS312 and CS314. Consequently, the project will introduce you to computer architecture, assembly code, the Java Virtual Machine (JVM), compilers, and data structures. The four parts that have the following structure and goals:

• Part 1: Introduce SaM, stacks, postfix notation; practice with the Sam "computer".
• Part 2: Fix a buggy compiler. You will pitch your testing strategy in P2a and complete your work in P2b.
• Part 3: Extend your compiler to handle heap-allocated language features. You will pitch your design plans in P3a and complete your work in P3b.

8.2 Partners

Unless otherwise posted, you must follow these rules:

• You may work by yourself or with one or two partners for each assignment, except P1.
• You may not work with different partners for different parts of the same assignment.
• You may not change or drop partners once you have started working on the assignment.
• You may only divorce your partner(s) after you submit an assignment.
• You may not remove partners' names from an assignment unless you do not use each others' work.
• You may change partners for a new assignment.
• You share equal responsibility with your partner(s) for completing the assignment and all issues of Academic Integrity.
• You will share your assignment grade with your partner(s) for each assignment. Groups that feel that one or more partners have not equally contributed may state their case to the instructor, who may modify the individual grades for that assignment.

8.3 Submission

We will be using an on-line submission system called Course Management System (CMS). If you are working with partners, do not wait until the last minute to submit an assignment! Since your team may only submit one assignment, CMS requires that you and your partners form a group. Group formation requires that each member log into CMS in advance of the due date.

8.4 Late Policy

Generally, late assignments receive a 20-point penalty per day late. Once we post solutions, we will not accept any late assignments. If any of your partners has a university-excused conflict (see Conflicts, below), the remaining partners are still responsible for submitting the assignment on time and training the partner(s) who missed some of the work. If you work by yourself and have a university-excused conflict, you need to contact the instructor before the due date to make arrangements.

8.5 Conflicts/Illness

If you miss an assignment due date because of illness or another university-excused conflict, you must contact the instructor and provide documentation. If you miss more than one assignment, you are strongly encouraged to drop the course. In particular, if you miss Part 3, you should drop the course. Missing Part 4 due to a univeristy-excused conflict will likely result in an incomplete. See also the Late Policy, above.

8.6 Regrades

Regrades are generally due one week after the assignment grades are posted. We will post instructions for each part on the steps to take (sometimes using CMS's system, sometimes scheduling meetings with the staff). We offer similar advice, as given in CS211:

• We place the "burden of proof" on the student. So, in cases of requests for more points, you need to demonstrate how and why you deserve a higher grade.
• We allow "minor corrections" in some cases. For example, if fixing some punctuation or a few words demonstrates that your code really did work a lot better than we perceived, you might earn more points. However, we will usually apply a point deduction for such fixes, so only in extreme cases will you receive additional points.

8.7 Submission Format

Follow the CS211 format. Be sure to review all the submission specifications.

9. Exams

CS212 has no prelims and no final exam. We will likely give at least one in-class quiz to that test whether or not all members in a group have contributed equally to the project.

10. Academic Integrity

All students must follow the Code of Academic Integrity (AI) at all times. Unless posted, follow the rules as listed above in Project. The penalty for any violation of the code is severe. Refer to the rules that are posted below:

10.1 Notes

• The word you in the following statements refers to the phrase, you and your partner(s), if an assignment allows you to work with more than one person and that you have chosen to do so.
• The rules contained herein represent our implementation of the Department of Computer Science Code of Academic Integrity and the Cornell University Code of Academic Integrity.

10.2 Doing Homework

• You may discuss work with other students. Generally, discussing an algorithm, approach, or general form of code is acceptable. However, cooperation should never involve other students possessing a copy of all, or a portion of, your work, regardless of format.
• You may not remove your partner's name from an assignment unless you do not use each other's work.
• Unless otherwise posted, you must follow the rules for partners, which are listed above.
• When you are allowed to use additional resources (such as textbook examples and supplied code), you must credit them.

10.3 Submitting Homework

• When applicable, the programs and other work that you submit must generate the indicated output and/or results.
• Your name must not appear on more than one submission.

10.4 Contacting Students and Staff

• Contact a member of the course staff immediately if you suspect a violation of the Code of Academic Integrity.
• If you are suspected of a violation, we will send an e-mail notification. If your on-line listing shows a local address, we will mail an additional hardcopy of the notification. Refer to CIT's website http://whoiam.cornell.edu/ for updating your local address.

10.5 Penalties

• We assign penalties on a case-by-case basis.
• We hold you responsible in case of a violation.
• We may lower your grade, fail you in CS212, request Cornell University disciplinary action, or apply a permanent mark on your transcript.

11. Course Grades

Your final grade will be based on the assignments. All partners must contribute equally. If discrepancies arise, we will adjust course grades accordingly, as stated above in Project. The weights of each part are as follows:

E represents the university evaluation.

12. Reading And Textbooks

Other than course notes and assignments, there are no required readings for CS212. However, we might be interested in these resources:

• Programming for the Virtual Machine, J. Engel, Readin, Mass: Addison-Wesley, 2003.
• The Java Virtual Machine Specification, Second Edition, T. Lindholm & F. Yellin, Boston: Addison-Wesley, 1999.

See also the many references listed on CS211.

13. Software Requirements And Resources

Refer to the CS211 requirements.