start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
start [2009/09/14 01:11] – jonathan | start [2009/10/18 22:30] (current) – jonathan | ||
---|---|---|---|
Line 1: | Line 1: | ||
~~NOTOC~~ | ~~NOTOC~~ | ||
====== CSE4312 | ====== CSE4312 | ||
+ | |||
+ | **Fall 2009: CSE4312 -- Software Requirements Engineering** | ||
+ | |||
+ | ← Please read the forum regularly for course updates. | ||
+ | |||
===== Lecture Times ===== | ===== Lecture Times ===== | ||
* Tuesdays & Thursdays 4pm-5.30pm in [[ https:// | * Tuesdays & Thursdays 4pm-5.30pm in [[ https:// | ||
+ | |||
+ | ===== Learning outcome ===== | ||
+ | |||
+ | Students should be able to | ||
+ | * Elicit Goals and Requirements from Stakeholders (in the Problem Domain) | ||
+ | * Develop/ | ||
+ | * Develop/ | ||
+ | * 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 | ||
+ | |||
+ | 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:// | ||
+ | * 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 ===== | ===== Suggested texts ===== | ||
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. | * 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:// | ||
- | * 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) | ||
- | * Develop/ | ||
- | * Develop/ | ||
- | * 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 | ||
- | |||
- | A work-intensive project (divided into 3 phases) will allow students to apply their knowledge to a non-trivial example. | ||
- |
start.1252890678.txt.gz · Last modified: 2009/09/14 01:11 by jonathan