This course's web presence has a public side which you are viewing as well as a private side managed through CSU's Canvas system. General information concerning lectures, schedule, assignment posting, etc. are managed through the public side. Student specific information such as grading, quizzes, etc. are managed through Canvas.
Important syllabus clarifications and elaborations are included below under Addendum (last updated 2/2/2016).
The prerequisite for CT310 is CS200.
This text is available through the CSU bookstore. The author also maintains a textbook related website.
Here are the formally graded elements of the course and associated weighting:
|Lecture and Online Notes||5 %|
|Recitation Participation||5 %|
|Recitation Excercises / Homeworks||10 %|
|Final Exam||15 %|
Semester grades are determined by the weighted sum of points earned in each of these areas. The total points for each area are normalized so that the expected top score for the semester is 100. The cutoff between an A- and a B+ is typically 90 points. Likewise, the cutoff between a B- and a C+ is 80 points. The cutoff between a C and D is typically 70 points. While this is the typical grading procedure, the instructor reserves the right to shift a cutoff down, i.e in the students favor if the instructor feels such a change is justified.
Video and Audio for lectures will be recorded and posted to the CT 310 course progress page. Students are strongly encouraged to avoid falling into a habit of not attending lectures and relying solely upon the recordings. Lectures work best for all concerned when students participate. In addition, students must be prepared for the reality that lecture capture may fail. Students will be introduced to an online note taking capability associated with CT 310 and all students will be asked to contribute and graded in part based upon those contributions.
Homeworks and exams will always be done individually and grades assigned on an individual basis. There is a required weekly recitation which will at time include excercises started in recitation that will constitute that week's homework. Attendance and associated performance on these excercises/homeworks contributes to a portion of the semester grade.
Projects will be done by teams (pairs) of students, and grades will be assigned jointly. However, the instructor reserves the right to assign unequal credit to members of a team if circumstances warrant. Project teams will be assigned at the discretion of the instructor.
A word about grading and Canavs. Points assigned for specific assignments as displayed by Canvas are to be trusted and considered the official course record. However, Canvas attempts to project point totals during the semester. These projections are problematic and students are stronly encouraged to be careful reading too much into these projections: they are in no way binding and at times out-and-out misleading.
Midterm and Finals: Make-up exams are only given for extraordinary circumstances (e.g., illness, family emergency) with appropriate documentation. Students must consult with the instructor as soon as possible, preferably before the start of the exam. Course examination dates are listed in the syllabus; be aware of them and plan accordingly.
Homeworks and Projects: Unless otherwise specified, programming assignments are to be submitted electronically. This may be accomplished through Canvas or through a web spider capturing a copy of a project website. Specifics will be included in each major assignment. Always check the assignment page for due dates; normally, programming assignments are due at 11:55 PM on the due date. Late assignments submitted within 48 hours of the time required will receive a 10% late penalty. Electronic submission is closed 48 hours after assignments are due; students not having submitted programs receive an automatic zero on the assignment.
|First in class midterm||Friday February 26th|
|Second in class midterm||Friday April 1st|
|Final Exam||Tuesday May 10th 7:30AM to 9:30AM|
The midterms and final exam will be administered electronically using Cnavas. The will be conducted in CSB 110 with a possibility of some students being asked to use a different room due to capacity limits. Details will be made available in advance of the exams. The exams will be proctored and will be given during the designated times. They will not be available outside these times and places. While no change to the midterm dates is anticipated, the instructor reserves the right to change these dates with a weeks notice.
Lectures in this course are about communication and interaction; all students taking this course are expected to participate actively. Participation, at a minimum, includes asking and responding to questions. Students will also be asked to contribute to online notes that accompany each lecture. Contribution to the online notes will be counted as a portion of the lecture participation grade.
Attendance at lectures will be recorded. However, there are no specific points assigned for lecture attendance. Generally, the fact that students who actively participate in lecture earn more points through the work in the course is sufficient motivation. Attendance at the weekly recitation is required and points will be awarded for attendance. Excercises introduced in recitation and the completed as homework will generally be graded.
All students are expected to conduct themselves professionally. We (the instructors and GTAs) assume you are familiar with the policies in the student information sheet for the department. Additionally, you are computing professionals, albeit perhaps just starting. You should be familiar with the code of conduct for the primary professional society, ACM. You can read the ACM Code of Conduct HERE.
We work to maintain an environment supportive of learning in the classroom and laboratory. Towards that end, we require that you be courteous to and respectful of your fellow participants (i.e., classmates, instructors, GTAs and any tutors). In particular:
As announced in class on February 1st, failure to maintain proper file permissions on all PHP files may be viewed as providing your own work to other students. In other words, a violation of the CSU Academic Integrity Policy. Therefore, at all times, be aware of file permissions while working on the CS Department Unix Machines and confirm that you and only you can read your php files. (2/2/2016)