Differences

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

--- start [2011/10/24 20:23] – jonathan
+++ start [2012/02/06 20:47] (current) – jonathan
@@ Line 10: / Line 10: @@
 % - Requirements Document + Presentation (due Nov 30)
-% - Design Document + Presentation (due Jan 31)
+% - Prototype code (some core functionality) (due Jan 31)
-% - Prototype code (some core functionality) (due Feb 14)
+% - Design Document + Presentation (due mid reading week)
 % - Testing Document + Presentation (due Feb 28)
@@ Line 18: / Line 18: @@
 % - Evaluation of final code (due Apr 2)
-% - Final version of all three documents (due Apr 2)
+% - Final version of all three documents. User manual and deployment information. (due Apr 2)
 % - Final presentation (due Apr 2)
@@ Line 27: / Line 27: @@
 ===== Meetings =====
-All meetings are 3:30 - 5:00
   * 14 September 2011: Kickoff meeting
@@ Line 35: / Line 33: @@
   * 24 October 2011. Present detailed scenarios using realistic data of interactions between departmental advisors, faculty coordinator, SIS and RO. Present conflict cases and mitigation as well as non-conflict cases where no issues arise.
   * Nov 7th 2011. Present mathematical model of conflicts. Precise details of input including scheduling constraints and fields required from RO databases.
-  * 14 November 2011. Initial version of RD.
+  * 14 November 2011. Present revised mathematical model of conflicts.
   * 28 November 2011
-  * 19 December 2011
+  * December 5, 2011: Submission and persentation of complete Requirements Document.
+  * 20 December 2011: 3.30pm. Present revised RD.
+  * Monday Jan 9, 12.30pm to 2pm. Revised RD and initial design
+  * Monday Jan 23, 12.30pm. Add complete tests to the requirements document. Prototype code e.g. displaying data from Excel file,selecting subsets of meets, etc.
+  * Monday Jan 30, 1pm. Prototype core functionality including reading in Excel file, displaying it, selecting subsets of meets and displaying conflicts.
+  * Monday Feb 6. 12.30pm. (a) GUI up and running sufficient to demo to customer. (b) Scenarios to put to users, especially concurrent updates and role of admin.
+   *Monday Feb 13, 12.30m. Meeting with customers to discuss scenarios and get their feedback on actual implementation on **server**. To Do List Linked to requirements. Gap View and Saving Scenarios. Unit tests and one click installtion.
+    *To Dos: Gaps, Users/Passwds, Generate Excel out, Saving scenarios, concurrency, snapshots, code working on server
+===== Testing (TA)=====
+**(15%) Tuesday Feb 14 Code prototype test**. Student team will have the code to be tested installed on the server and meet with the TA for a block of time. TA will test the prototype. Run all functional tests from RD. Add new functional tests to check corner cases. Try out various scenarios on the actual code with the intention of crashing the system. Inspect code to search for problems.
 ===== Resources=====