|
Date |
Announcements |
| 12/19 8p.m. |
Congratulations! 30% of the class earned an A, 24% earned a B, and 30% earned a C; the rest are D's or students not finishing the course. The median for the final was 75; I also experimented with a curve of 5 points, but that didn't change anyone's grade. And in another experiment, I compared the exact attendance count to a modified total by adding 5 free days. The goal was to explore if attendance alone would change anyone's grade, and it did not. (That had been the premise at the beginning of the semester.) |
| 9/20 |
Career Fair: http://cns.utexas.edu/careerservices/students/events/fairs/expo.html Career Services: http://cns.utexas.edu/careerservices/ |
| 9/19 |
Unix Tutorials: links to some Unix
Tutorials have been posted on the FAQ home page. |
| 9/07 |
Room change REVERTED: discussion
section that meets on Th 11-12 will now meet in the original room UTC
4.120. |
| 8/29 |
Welcome
Aboard! |
|
Course: |
Computer
Organization and Programming |
||||
|
Instructor: |
Chris Edmondson-Yurkanan I also have an email alias: "dragon" , does it stand for dragonslayer or dragon's lair? You decide Office Hours: Mon 11:05-12, Tue 2:15-3, Wed 1:30-2:30
or by appointment. |
||||
|
Teaching Assistants: |
Name |
e-mail |
Office Hours |
Location |
Discussion |
|
Divya P. Gulati |
dpgulati (at) cs dot utexas
dot edu |
Mon 1:30-2:30, Wed 11-12 |
PAI 3.22
|
56197 |
|
|
Prakash S. |
psramrak (at) cs dot utexas
dot edu |
Mon 4-5 |
PAI 3.22 |
56201 |
|
|
Proctor: |
Kang, Byung (byungkon5 (at)
gmail dot com) |
||||
|
Class Meetings: |
Section 1: MWF 10:00-11:00,
RLM 7.104 |
||||
|
Discussion Sections: |
#56197: TH 10:00-11:00, SZB
380 |
||||
|
Information |
|
||||
|
Required Reading: |
|
||||
|
Prerequisites: |
Generally, students must have
completed CS307 and CS315 (or their honors versions), with a grade of
at least C in each. Enrollment is limited to Computer Sciences majors. |
||||
Course Catalog: CS310 Course Objectives
To understand the basic operation of computing systems. Upon completing this course, students should have a high-level understanding of the role played by each major component of the system, including compiler, operating system, assembler, instruction set, and hardware.
Student Evaluation
Your performance in this class will be evaluated through
homework and
programming assignments, three exams, a few quizzes for pacing, and
participation. The weights of each of these
components is listed below:
| TOTAL |
1000 POINTS |
| Three
Exams: Ex1, Ex2, Final |
55% : 16, 19, and 20 |
| Your
Best Exam: |
7%: |
| Homework
& Programming Assignments |
30% (all are counted) |
| Three
short quizzes (in class) |
3%: |
| Attendance/Participation:
class lecture & discussion |
5%:
This is a new emphasis designed to help you succeed in the class:
-.5% per absence, up to 10 lectures or discussion sections. See details
below: |
ATTENDANCE at Lecture and
Discussion Section:
Many members of the CS Department have been discussing that
attendance can have a strong association with both exam performance and
overall course grade. Typically, without an attendance policy,
students who miss several lectures are much more likely to NOT pass the
course. Our goal is to help students balance their heavy course
loads and time demands, while appreciating the heavy cost to missing
lectures in courses. The attendance policy elsewhere has been
very successful and generally very well received by students.
Students will lose .5% of their final course grade for each
absence. Attendance will be taken at the beginning of each
lecture and discussion section. Students who are more than 5
minutes late will be counted at absent. If you know that you are
going to be late to a lecture or discussion section, please make prior
arrangements with your instructor or TA.
The attendance policy is intended to be both a strong incentive for
attendance and to help students be aware of the importance of
attendance and participation on academic performance in this
course.
EXAMS:
The first two midterms will last 2-hours and will be given in the evening. Make-up exams will be given ONLY for an official UT conflict, and you must submit a written make-up request with proof of conflict to the instructor one week before the exam. The exam schedule is as follows:
| NIGHT EXAM 1 |
Monday, October 9th,
7-9p.m. TAY 2.006 |
| NIGHT EXAM 2 |
Monday, November 13th, 7-9p.m. TAY 2.006 |
COMPREHENSIVE FINAL |
See the Course Schedule: Friday, December 15, 9-noon. TAY 2.006 |
Electronic Turnin: Your programming assignments will be
submitted
electronically using a UT CS LINUX turnin utility and thus will require
you to
use your CS departmental Unix account. We
will not be using the MicroLab
turnin. Do NOT email your assignments to the
teaching staff. The
programs will be graded on correctness, readability, style, and
documentation. All CS students who meet the prerequisites for
CS310 are
eligible for a CS departmental Microlab account and undergraduate Unix
account
NEW Procedures for getting Accounts:
Interaction with your TA
Feel free to attend any/all of the CS310 office hours and make
appointments with the team.
Your TA will conduct 50 min. discussion sections each Thursday to provide extra time for questions, to present additional examples of problem-solving techniques, to review the assignments, and to present new material.
The grading of assignments and tests will be shared among myself,
the TAs,
and the proctor, but your contact point for grades will be your
TA.
Assignments and tests will be returned by your TA. Any grading
problems
should be submitted in writing to your TA for resolution first, before
appealing to me. You have one week to turn in a written appeal, after
the TA
returns the assignment.
Classroom Distractions:
Academic Dishonesty Policy
You are free to discuss the course material with your classmates and
are
encouraged to form study groups, particularly for reading, quizzes, and
exams. Collaboration on
homework or programming assignments is absolutely not permitted...
unless I explicitly state
that you may work together with one person for a specific problem of an
assignment.
While helping a friend understand the wording of a homework question or programming assignment specification is permitted, helping a friend in any way to answer the question is NOT permitted. Students who work together too closely (e.g. design their solution together) should be aware that this is a form of cheating called COLLUSION and is subject to severe academic penalties. The penalty for academic misconduct is a failing grade in this course.
Both the University of Texas and the Computer Sciences
Department, believes that collusion and other academic dishonesty
warrants an F in the course.
Remember, each assignment in CS310 is only weighted 3-5% of the entire
course
grade, and the grading policy has partial credit. Given the significance of
collusion, do NOT turn in a single problem that was not solved by you,
and you alone.
The homework, programs, and exams must be the work of students turning them in. University policy will be followed strictly. (See the Dean of Students' policies on academic integrity) Acts that exceed the bounds defined by the approved collaboration practices will be considered cheating. Such acts include:
· Copying solutions, code, or programs from someone else or giving someone else your solutions, code, or programs
· Participation in a discussion group that develops a solution that everyone copies
We urge everyone in the class to take appropriate measures for protecting one's work. You must protect your files, homework solution sheets, etc. as deemed reasonable.
Studying for tests together is permitted and encouraged. Please come talk to me if you are unsure about how to work together with your friend in a legal, helpful manner. Remember, it is always ok to "work together" with your professor or TA!
Your Responsibilities in This Class:
· Your performance in this class will be determined by you! It will require a strong dedication to learning the material and may require a substantial time commitment to complete the programming assignments.
· You are expected to show up on time for lecture and discussion sections, with your cell phone turned off.
· You are responsible for all material posted to the class web site or emailed to your address that you registered with UTDirect. (To make this easy on you, we will not post required information any later than 48hrs before 'an assignment is due' or 'the exam date'). Ignorance of such material is no excuse.
· You are responsible for obtaining departmental Unix accounts, and learning the Unix operating system sufficiently well to meet the demands of the course. The CS department provides several sessions of a 1 hour introduction at the beginning of every semester.
· You are responsible for all material presented in lecture and in discussion sections. Note: lectures will include some material that is not available elsewhere. We advise you to attend all discussion sections so as not to miss out on material that will be covered in assignments and on exams.
· You are expected to attend the discussion section for which you are registered. This is important to allow all students equal access to the TAs. Furthermore, all assignments and exams will be returned in discussion sections by your TA.
· You are responsible for turning in your own work on all assignments. Unauthorized collusion is not allowed and constitutes a violation of the university's policies on academic integrity. See above guidelines for more information on what is or is not allowed.
· You are responsible for protecting your work from being copied by others.
· I support the CS code of Conduct for CS310 faculty, TAs, proctors, and students; I will adhere to the responsibilities it describes for faculty; please read and adhere to it as well.