Differences

This shows you the differences between two versions of the page.

--- start [2013/02/06 16:10] – bil
+++ start [2015/03/20 17:38] (current) – bil
@@ Line 1: / Line 1: @@
 ~~NOTOC~~
-====== CSE 2311  ======
+====== EECS 2311  ======
-===== CSE 2311 Announcements  =====
+===== EECS 2311 Announcements  =====
+<html><!--
+  * **March 5, 2013**: Course evaluations will take place at the beginning of lecture on March 27.
   * **February 6, 2013**: You can book the classroom for a team meeting. Email boze@cse.yorku.ca with your requested timeslot(s).
   * **January 14, 2013**: The teams have been rearranged. Click on Teams on the sidebar to see the changes.
-  * **January 8, 2013**: Both the lectures and the labs for this course will take place in LAS 1006C. For the first lecture, the instructor will be at the originally assigned room (CB 120) at 11:30 and will then move to LAS 1006C at 11:35 or so. The first lecture will start around 11:45 in LAS 1006C.
+--></html>
-  * **December 19, 2012**: The lab session on January 7 will not take place. The course will start with the lecture on January 9.
+  * **March 20, 2015**: Important dates have been updated due to the labour disruption.
-  * **December 19, 2012**: This webpage was just created. Information will be added to it by the first lecture.
+  * **March 4, 2015**: Midterm grades are now posted. Click on Grades on the sidebar.
+  * **January 7, 2015**: The team meetings after the lecture will take place in LAS 2002.
+  * **January 5, 2015**: The lectures for this course will take place in LAS 1002, not CB 120.
+  * **December 28, 2014**: The lab session on January 5 will not take place. The course will start with the lecture on January 7.
+  * **December 28, 2014**: This webpage was just created. Information will be added to it by the first lecture.
+===== EECS 2311 Learning Outcomes  =====
+Upon successful completion of the course, students should be able to:
+  * Describe the requirements of a large software system.
+  * Select appropriate system elements for a high-level design description.
+  * Derive and implement test cases at the unit and system level.
+  * Produce a detailed user manual for an interactive system.
+  * Implement a large software system from scratch.