CSE 221 is a 4-unit core graduate subject with lectures based on paper discussions, homeworks, a final, and a term project. The purpose of this course is to teach computer software system structures from a design point of view. We will look at different structuring techniques, and we will examine their usage in both important historical systems and in modern systems. In addition to learning about different system structures and different operating systems, you will learn:
Prereqs: CSE 120 or equivalent undergraduate course and programming experience with C/C++ for the project.
|Varun Gargfirstname.lastname@example.org||B240A||N/A||Tue 2:00-3:00pm and Wed 3:00-4:00pm (or by appointment)|
|Alex C. Snoerenemail@example.com||EBU3b 3114||822-2289||Mon 3:00 - 4:00pm (or by appointment)|
All homework assignments must be completed individually. The term project is a group effort. You must write all solutions and code that you submit, excepting code written by your group members for the term project. You may discuss the assignments with others, but you may not copy answers or code from another student or make your code available to others (e.g., by posting to a public GitHub repo). Exams will be individual effort.Each student is responsible for knowing and abiding by UCSD’s academic integrity standards and Student Conduct policies. Any student violating UCSD's Academic Dishonesty or UCSD's Student Conduct policies will earn an 'F' in the course and will be reported to their college Dean for administrative processing. Committing acts that violate Student Conduct policies that result in course disruption are cause for suspension or dismissal from UCSD.
Charles Elkan's academic honesty guidelines developed for CSE 130 explicitly spell out many of your reponsibilities, and must be adhered to. If you have any questions, please ask.
Don't cheat. It's not worth it.
Last updated: 2016-11-21 10:59:46 -0800 [validate xhtml]