1 / 13

CSCE 312 Computer Organization

CSCE 312 Computer Organization. Lecture 0: Course Administration EJ Kim ejkim@cse.tamu.edu Department of Computer Science and Engineering 338B Bright 979-845-3660 http://courses.cse.tamu.edu/e jkim/312. CSCE 312: Computer Organization. Class Schedule

elliot
Download Presentation

CSCE 312 Computer Organization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSCE 312 Computer Organization Lecture 0: Course Administration EJ Kim ejkim@cse.tamu.edu Department of Computer Science and Engineering 338B Bright 979-845-3660 http://courses.cse.tamu.edu/ejkim/312

  2. CSCE 312: Computer Organization • Class Schedule • Lectures TR 11:10AM ~ 12:25PM ETB 1020 • Labs • CSCE312-501 M04:10 pm-05:50 pmRDMC 111H • CSCE312-502 M10:20 am-12:00 pmRDMC 111C • Instructor: EJ Kim • Office Hour: MW 2:30PM ~ 3:30PM. • Office: HRBB 338B • TA: Hyunjun Jang (338C) • Email: hyunjun@cse.tamu.edu

  3. CSCE 312: Computer Organization • Books • Computer Systems: A Programmer’s Perspective, Randal Bryant and David O’Hallaron, Prentice Hall, 2011 (2nd edition) • Digital Design, Frank Vahid, John Wiley & Sons, 2011 (2nd edition) • Optional Reference • The C Programming Language, 2nd Ed. (ANSI C version) or later, Kernighan & Ritchie, Prentice Hall • Helpful in learning the operating system and programming environment

  4. Course Overview • The goal of this course is to introduce the fundamental organization and structure of computer systems. • Topics include: • Computer systems (overview) • Data representation • Machine language • Processor architecture • Memory hierarchy • Linking • Exception control flow • Virtual memory • System level I/O

  5. Programmer Perspective • Traditional Computer Organization courses are presented in a bottom-up (hardware-oriented) fashion • We will take a top-down approach, that is, a software-oriented or “programmer’s perspective” of computer systems

  6. Prerequisites • CSCE 221 • Mastery of data structures including list, stack, and queue • Familiarity with recursion • Some knowledge of complexity analysis

  7. Grading • Homework 15% • Labs 20% • Quizzes 25% • Final Exam 25% • Project 15% • No midterm

  8. Assignments • Homework assigned ~bi-weekly • Mix of individual and team assignments, which will include programming exercises and problems from your textbooks • Assignments will be due at the beginning of the class

  9. Programming • Computing platform: Linux • Programming languages: C and Y86 Assembly • All programming must follow the JDE Coding Standard (see the course Web page, http://www.cse.unl.edu/~goddard/Courses/CSCE310J/StandardHandouts/JdeCodingStandardV3.pdf) • Program correctness is assumed…

  10. Quizzes • Five quizzes will be given and no midterm • 25 minutes in length • Format • Brief explanation of concepts based on the reading assignment for pending lecture • Questions on material already discussed in class

  11. Homework • Late home work will have penalty @ 25% per day • Genuine difficulties must be discussed with instructor and TA • Do not cut classes to do your homework

  12. Earning Grades in this Course • Want to get an “A” grade? • Attend all classes, do homework, do reading, do labs, do projects, participate in class • Want to get a “D” grade (or worse)? • Skip class, skip assignments, do not do reading, do not be attentive or avoid taking notes in the class, do not study

  13. Summary • Read syllabus on course details • We shall study computer organization from a programmer’s perspective • A lot of work in the class • Key knowledge about the hardware/software interface

More Related