Differences

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

--- start [2011/11/03 01:20] – jonathan
+++ start [2012/12/14 03:11] (current) – jonathan
@@ Line 2: / Line 2: @@
 ====== CSE4312  ======
-**Fall 2011: CSE4312 -- Software Requirements Engineering**
+**Fall 2012: CSE4312 -- Software Requirements Engineering**
-← Please read the forum regularly for course updates.
+← Please read the **forum** regularly for course updates.
 ===== Lecture Times =====
-  * Tuesdays & Thursdays 4pm-5.30pm in CB120
+  * Tuesdays & Thursdays 4pm-5.30pm in CB122
+  * Guest lectures on UML by Dr. Jackie Wang, on Tuesdays Sep. 18, Sep. 25 and Oct. 2nd.
@@ Line 16: / Line 17: @@
 Students should be able to
   * Discover what problem must be solved and why
-    * Elicit Goals and Requirements from Stakeholders (in the Problem Domain)
+  * Elicit Goals and Requirements from Stakeholders (in the Problem Domain)
   * Evaluate/Analyze the elicited data for consistency and correctness
   * Develop/Write a precise, structured, consistent **User Requirements Document**
-  * Develop/Write a **System Specification Document** (in the Solution Domain)
   * Formulate Acceptance Tests and Traceability matrices for showing that the implemented software product satisfies the User Requirements Document
-  * Models: use some modelling methods and tools for requirements analysis including UML models and mathematically specified  models for validating requirements (especially for safety/mission-critical software).
+  * Models: use some modelling methods and tools for requirements analysis including
+    * Informal UML models such as use cases, sequence, state and class diagrams
+    * Mathematically specified  models for validating requirements (especially for safety/mission-critical software).
 A work-intensive project will allow students to apply their knowledge to a non-trivial example.
 In addition
-  * you will be a temporal logic model checker using the for doing mathematical requirements analysis and verification (either [[http://www.comp.nus.edu.sg/~pat/|PAT2]]. See Chapter 17 in the suggested text.
+  * you will be using a temporal logic model checker or doing mathematical requirements analysis and verification ([[http://www.comp.nus.edu.sg/~pat/|PAT2]] together with our own TTM plugin). See also Chapter 17 in the suggested text.
   * You will also need to know some of the UML diagrams (you may want to read UML distilled : a brief guide to the standard object, Martin Fowler, available from Steacie).