Differences

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

--- start [2009/09/11 19:40] – jonathan
+++ start [2009/10/18 22:30] (current) – jonathan
@@ Line 1: / Line 1: @@
 ~~NOTOC~~
 ====== CSE4312  ======
+**Fall 2009: CSE4312 -- Software Requirements Engineering**
+← Please read the forum regularly for course updates.
 ===== Lecture Times =====
   * Tuesdays & Thursdays 4pm-5.30pm in [[ https://w2prod.sis.yorku.ca/Apps/WebObjects/cdm.woa/6/wo/ykEtFliJz2In8ytoE6nNZw/9.1.8.9.7.0.0| CC 208, Calumet College]]
+===== Learning outcome =====
+Students should be able to
+  * Elicit Goals and Requirements from Stakeholders (in the Problem Domain)
+  * 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 Goal models, UML models and mathematically specified  models for validating requirements (especially for safety/mission-critical software).
+A work-intensive project (divided into 3 phases) 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]] or [[https://wiki.cse.yorku.ca/lab/sel/tutorial:start|Spin]]). See 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).
 ===== Suggested texts =====
-There is no required textbook. Attendance at all lectures is obligatory as that is where the main material needed will be covered.
+Attendance at all lectures is obligatory as that is where the main material needed will be covered. If you Login at (see bottom of this page), you can access additional information such as notes and slides (on the SVN). There is no required textbook.
 A suggested text is: [[http://i.f.alexander.users.btopenworld.com/reviews/lamsweerde.htm|Requirements Engineering: from system goals to UML models to software specifications]], Axel van Lamsweerde Wiley, 2009 ISBN 0470012706 (paper, 682 pages). You may purchase this book through the York University Bookstore or from [[http://www.amazon.ca/Requirements-Engineering-System-Software-Specifications/dp/0470012706|Amazon]]. ([[http://i.f.alexander.users.btopenworld.com/|Reviews of books on requirements engineering]]). Highlights from the text (we will cover some, but not all of this, in class) include:
@@ Line 17: / Line 38: @@
   * Numerous examples from running case studies in a variety of domains, including security– and safety–critical ones. Rich set of problems and exercises at the end of each chapter together with bibliographical notes for further study.
-In addition
-  * you will be using the [[https://wiki.cse.yorku.ca/lab/sel/tutorial:start|Spin model checker]] for doing mathematical requirements analysis and verification.
-  * 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).
-===== Learning Outcome =====
-Students should be able to
-  * Elicit Goals and Requirements from Stakeholders (in the Problem Domain)
-  * Write a precise, structured, consistent **User Requirements Document**
-  * Determine/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: know some modelling methods and tools for requirements analysis including Goal models, UML models and mathematically specified  models for validating requirements (especially for safety/mission critical software).
-A work-intensive project (divided into 3 phases) will allow students apply their knowledge to a small but non-trivial example.