B. A. Martin
(Adjunct Associate Professor)
COURSE: CST112 -- Introduction to Programming CREDITS: 4 MEETINGS: Monday & Wednesday 9:30-11:10am / Room H209 (Caumsett Hall, Grant Campus) Tuesday & Thursday 1:30-3:10pm / Room R219 (Riverhead Bldg., Ammerman Campus) PREREQUISITE(S): MAT007 or equivalent (Required)
Recommended: Prior computing experience or CST111
CST112 and MAT107 are corequisities for students in the Information Technology curriculum.
OFFICE HOURS: Before or after class and by appointment. EMAIL:: email@example.com DEPT. SECRETARY: 851-6770
This course introduces fundamental programming principles to beginners.
Emphasis is placed on algorithm development, structured programming techniques, flowcharting, coding, debugging and libraries.
It discusses programming concepts such as variables, conditionals, loops, functions, objects, and arrays.
Program output may include graphical elements with images, animation and visualization.
The course is designed as a place where many ideas and techniques can mix and is therefore appropriate for a wide audience that includes programmers, as well as people interested in graphical design or analytic fields (science, mathematics, economics, etc.).
-- A Beginner's Guide to Programming
Images, Animation, and Interaction"
by Daniel Schiffman
(Morgan Kaufmann Series in Computer Graphics) [Paperback];
Although computer lab time may be scheduled each week during class time, students should be aware that additional lab time outside of class will be necessary to complete the requirements of this course. Students should plan to spend an additional 3 to 6 hours per week using other computers (such as those in the computer lab).
For coding assignments, grading will be based not only on whether the code compiles correctly and performs the assigned tasks, but also upon its organization, clarity, and -- most of all -- "readability". These and other aspects of programming practices, as well as adherance to "coding standards" (to ensure testability, maintainability, etc.) will be introduced and discussed in the textbook and in class.
"Any fool can write code that a computer can understand.
Good programmers write code that humans can understand."
Remember that computer source code is not some sort of "private communication" only with the computer, kept secret from others. Instead, source code should be thought of as intended for "publication", meant for the eyes of others of humans! In a code review, colleagues often examine a "rough draft" or a "work in progress" in order to help with problems, make suggestions, etc. -- and perhaps also to learn something new.
ATTENDANCE POLICY: Attention is directed to the following statement of college policy.
Consequently, each student in this course is strongly advised to make standing arrangements with another individual student to take detailed notes, collect handouts, relay announcements, etc., in the event 'e doesn't show up at class. While you are encouraged to contact the instructor for advice before (or after) missing a class, it is more effective to have your "buddy" take detailed notes, and the student remains responsible for "all that transpires in class".
Find a "buddy" to cover for you!
Do it now, not after missing a class.
This instructor does not give credit for mere attendance, nor is credit lost for absence. While attendance is not a direct factor in grading, it may indirectly affect the "participation" component.
College policy defines "Excessive Absence or Lateness" as "more than the equivalent of one week of class meetings". While attendance is not a component of grading policy for this class, a student missing more than one week of consecutive classes - without making any contact with the instructor - may be removed from the class roster and disenrolled.
SCCC STUDENT CODE OF CONDUCT
... Although not all-inclusive, the following actions, activities or behaviors are expressly prohibited:
Any student guilty of the above may receive a failing grade in that class, be dismissed from class and/or be referred to the Dean of Students for further discipline proceedings.
Also, please note:
For additional statements required in course outlines, Click here