ECE 2035: Programming for Hardware/Software Systems
Klaus, Room 2456
MWF 11:05 - 11:55 am
Professor Linda Wills
Office: Klaus Room 3310
|Common ECE2035 Web Site||Exam Schedule|
DESCRIPTION: This course presents execution and storage mechanisms used to support high level programming languages and operating systems. This design-oriented course describes how complex mechanisms are created using operations and storage defined in an instruction set architecture. Assembly language examples illustrate key course concepts. Lecture material is reinforced by design projects that require C programming and MIPS assembly language programming, focusing on performance and storage resource requirements on hardware platforms.
PREREQUISITES: ECE 2030 or ECE 2020
IN-CLASS EXAMS: There are three in-class exams. They are closed-book, closed-note. Calculators are not allowed on the exams. Each exam focuses on the material covered since the last exam. However, due to the cumulative nature of the material, all exams are comprehensive (i.e., they may draw on all material covered in the class thus far.) Each in-class exam contributes 13.33% of the overall grade.
FINAL EXAM: The final exam covers all material covered in
the class. It is a closed-book, closed-note exam and calculators are
not allowed. The final exam contributes 25% of the overall grade.
TENTATIVE EXAM SCHEDULE:
Exam 1: Wednesday, 21 September 2016
Exam 2: Friday, 21 October 2016
Exam 3: Wednesday, 16 November 2016
TENTATIVE EXAM SCHEDULE:
Final Exam: Wednesday, 14 December 2016, 8 a.m.
check the Registrar Website for changes
MISSED EXAM POLICY: Exams are taken at the scheduled class time or at the scheduled final period. A missed exam will be recorded as a zero. Family emergencies and extreme medical emergencies are handled specially.
ASSIGNMENTS: Multiple homeworks and projects are assigned throughout the semester. Homeworks are assigned more frequently, while projects have longer timeframes and are weighted more heavily. The homework assignments and projects are to be completed and submitted individually. The total homework and project grade contributes 35% of the overall class grade. Note that an assignment might be due the week before final exams.
GRADING: The final grades are determined based on totals earned during the class.
Total points = .40 (in-class exam average) + .35 (assignment grade) + .25 (final exam)
Grades are assigned as follows (assuming a passing project average): [90-100] = A, [80-90) = B, [70-80) = C, [60-70) = D, [0-60) = F.
TEXTBOOK: Patt and Patel, Introduction to Computing Systems, 2nd edition, 2004.
ASSIGNMENT INFRASTRUCTURE: To perform the assignments, you need the following:
ACADEMIC HONESTY: Although students are encouraged to work together to learn the course material, graded class work must be completed individually. Specifically, while you are permitted to discuss the homework and project assignments and algorithms with other students in the class, you must design, write, and debug your solutions individually. You should not share code, debug code, or discuss its performance with anyone. Once you begin implementing your solution, you must work alone.
All exams are to be completed individually with no collaboration or interaction during the exam period.
All conduct in this course will be governed by the Georgia Tech honor code. Additionally, it is expected that students will respect their peers and the instructor such that no one takes unfair advantage of anyone else associated with the course. Any suspected cases of academic dishonesty will be reported to the Dean of Students for further action.
ATTENDANCE: Since class lectures include material that is not included in the book, class attendance is required. If a class is missed, a student should make arrangements to get notes from other students. The importance of regular class attendance and good note taking cannot be understated.
The use of electronic devices, including laptops, cell phones, netbooks, and audio players, are prohibited during class lectures (except to take notes) and exams.
HEALTH POLICY: It is important that everyone try to avoid spreading germs and sharing illnesses with others during the semester. If you are sick, please communicate with the professors, TAs, and fellow students through skype, email, or phone rather than in person.
Questions and comments to Linda Wills
last revised at on 19 August 2016.