|
|
|
|
|
|
|
|
|
|
Other times by appointment and whenever I'm in! |
|
On-Line Schedule: The current and frequently updated course schedule can be found on line.
Catalog Description: An introduction to computer programming in an object-oriented style for practical application. Topics include class definition, basic program constructs, basic data structures, interactive user interfaces, and encapsulation.
Prerequisites: none.
Learning Outcomes: To expose you, the student, to basic programming design practices that will be applicable to all fields of study. During the semester we will build several “worlds”, small 3-D graphical programs that can be viewed in a web page. The idea behind creating "worlds" is to uncover the “magic” of applications that are used on a daily basis in academia and personal computer use. By the end of the course you should have a familiarity with the power of programming and be able to create your own worlds. You will also be prepared to take Computer Science I.
Required Texts:
Accommodations: Southwestern University will make reasonable accommodations for persons with documented disabilities. Students should register with the Office of Academic Success, located in Cullen Hall 336. Professors must be officially notified by the Access and Academic Resource Coordinator that documentation is on file at least two weeks before the accommodation is needed.
Grading Policy :
| 2 or 3 in-class exams, major projects | 25% |
| Final exam | 25% (must pass to pass course) |
| Labs , Exercises, and Quizzes | 50% |
|
|
Letter | Numeric | Letter | Numeric |
|
||
| 97-100 | A+ | 93-96 | A | 90-92 | A- | ||
| 87-89 | B+ | 83-86 | B | 80-82 | B- | ||
| 77-79 | C+ | 73-76 | C | 70-72 | C- | ||
| 67-69 | D+ | 63-66 | D | 60-62 | D- | ||
| below 60 | F |
Attendance Policy: Attendance in class is strongly recommended and will be taken every class day. Students are responsible for all material and assignments given in class whether they are present or not. It is the responsibility of the student to obtain notes, assignments, etc. for any missed class from a fellow student. ATTENDANCE IS MANDATORY FOR ALL EXAMS. Absolutely no makeup exams will be given. . If student missed one in-class exam, the grade on the final exam will substitute for it. If a student does not miss any exams, the final grade will substitute for the lowest exam grade (if it is higher). If a student has already missed an exam, subsequent missed exams will result in zeroes. A student must pass the final examination to pass the course.
Homework Assignments: All homework is due at the beginning of the class period in which it is due (at 1:00 and not at 1:05, for example). I understand that occasionally bad things happen (illnesses, accidents, deaths) and I would like to hear if you are having problems that are preventing you from completing your assignments. However, I will under no circumstances make any special arrangements after the fact (that is, after the homework is due). Unless you are unconscious at the hospital, you must email me or speak to me before an assignment is due for me to accept it late. Approved late projects are subject to a 10 point per day late penalty.
Honor code: In a nutshell: you
violate the honor code when
you represent someone else's work as your own. In general,
written
homework (including any programming assignments that are pencil/paper
and
not implemented) are to be completed independently. Homework
program
specifications may be discussed at a very high level with other
students,
but details, coding and execution must be individual. Aiding
each
other in tracking down a bug in your program after all code has been
specified
and implemented is fine. I expect your programs to differ
from each
other in significant ways. Group programming assignments
should be
worked on together with other group members. You may discuss
your
algorithms and concept with other groups, but you may not share
code.
I do reserve the right to ask you about your programs to ensure that
you
fully understand the coding and details of the implementation.