Context Navigation

Changes between Version 26 and Version 27 of cs222-2017-fall

Timestamp:: Sep 27, 2017, 9:29:48 AM (8 years ago)
Author:: chenli
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

cs222-2017-fall

-              v26
+              v27
 ''Prerequisites:'' CS 122A "Introduction to Data Management" and (ICS53 - "Principles in System Design" or CS143A - "Principles of Operating Systems").  Please don't attempt this class without the required background!  Doing so has not proven to be a great idea for students historically. :-)
 === Grading Breakdown ===
+Midterm Exam: 25% [[BR]] Final Exam: 25% [[BR]] Four-Part Programming Project: 50%
+Midterm Exam: 25% [[BR]]
+Final Exam: 25% [[BR]]
+Programming Projects: 50%
 This mixture of grading criteria for CS222 is intended to give equal "excelling opportunities" to both thinkers and do-ers. It's also intended to avoid overly weighting either team-based performance or individual performance. '''This is a hands-on project class, so expect to put a significant effort into your projects.''' The exams will be comprehensive with respect to the course material and will also ping you individually with respect to project knowledge, so be sure that you and your project partner make design decisions together. The two exams will be closed-book, but you may bring an 8.5"x11" two-sided cheat sheet to each exam if you like.
 …
 ----
 === Notice about Projects ===
  * Students should work on parts 2-4 of the project in teams of up to two students. Not more than two students are allowed in a team. Please let us know about your group by following the instructions that will be provided via Piazza when the time comes to do so. (In general, you should keep a close eye on Piazza all throughout the quarter!)
  * Students who strongly prefer to work alone for one reason or another may do so by requesting permission from the instructor — although it’s not advisable, and you will not get any “discount” on the assignment requirements if you opt to take this path.
  * ''Students are allowed to add attributes, methods, and classes, as long as the public signatures provided in the codebase are kept and implemented.'' [[BR]] We will be testing your code by calling the methods that are declared in the signatures.
  * Students also have the freedom to use other open-source libraries or packages (e.g., Gtest and Boost) to implement and test their code. Just please make sure that you: (1) get the okay from a Reader before using any additional packages; (2) list such packages clearly in your project document; and (3) write your makefile correctly so that your project can still be built by calling the 'make' command.
+ * Students can work on projects 2-4 in teams of up to two students. Not more than two students are allowed in a team. Please let us know about your group by following the instructions that will be provided via Piazza when the time comes to do so.
+ * The projects are doable by individuals, which can be more challenging but rewarding.
+ * Students are allowed to add attributes, methods, and classes, as long as the public signatures provided in the codebase are kept and implemented. We will be testing your code by calling the methods that are declared in the signatures.
+ * Students also have the freedom to use other open-source libraries or packages (e.g., Gtest and Boost) to implement and test their code. Just please make sure that you: (1) get the okay from us before using any additional packages; (2) list such packages clearly in your project document; and (3) write your makefile correctly so that your project can still be built by calling the 'make' command.
 === Project Late Policy ===
 …
 === Cheating Policy ===
 Cheating is an area where the instructor for this course has absolutely no patience or sympathy whatsoever. You are all here to learn, and cheating defeats that purpose and is unfair to your fellow students. Students will be expected to adhere to the UCI and ICS Academic Honesty policies (and should see http://www.editor.uci.edu/catalogue/appx/appx.2.htm#academic and http://www.ics.uci.edu/ugrad/policies/index.php#academic_honesty to read their details). Any student found to be cheating or aiding others in cheating will be academically prosecuted to the maximum extent possible — so you will fail the course with no option for a second chance. This policy will be strictly adhered to; no exceptions will be possible regardless of the impact it may have on your studies, your work plans, your visa status, or anything else. Don’t cheat and you won’t have issues. Just say ''no'' to cheating!
+Cheating is an area where the instructor for this course has absolutely no patience or sympathy whatsoever. You are all here to learn, and cheating defeats that purpose and is unfair to your fellow students. Students will be expected to adhere to the UCI and ICS Academic Honesty policies (and should see http://www.editor.uci.edu/catalogue/appx/appx.2.htm#academic and http://www.ics.uci.edu/ugrad/policies/index.php#academic_honesty to read their details). We run a software package to search for cheating cases in projects.  Any student found to be cheating or aiding others in cheating will be academically prosecuted to the maximum extent possible — so you may fail the course with no option for a second chance. This policy will be strictly adhered to; no exceptions will be possible regardless of the impact it may have on your studies, your work plans, your visa status, or anything else. Don’t cheat and you won’t have issues. Just say ''no'' to cheating!
 === C/C++ Resources ===
 …
 === Final Exam ===
+Tuesday, December 12, 2017, 10:30 a.m. - 12:30 p.m [[BR]]Closed books, Closed notes. You can bring an A4-sized "cheat sheet."  The exam will cover all materials taught in this quarter, with a more emphasis on those after the midterm.
+Tuesday, December 12, 2017, 10:30 a.m. - 12:30 p.m [[BR]]
+Closed books, Closed notes. You can bring an A4-sized "cheat sheet."  The exam will cover all materials taught in this quarter, with a more emphasis on those after the midterm.