start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
start [2014/09/14 16:10] – jonathan | start [2014/10/02 00:56] (current) – jonathan | ||
---|---|---|---|
Line 1: | Line 1: | ||
~~NOTOC~~ | ~~NOTOC~~ | ||
- | ====== EECS4312 | + | ====== EECS4312 |
- | **Fall 2014: CSE4312 -- Software | + | **Fall 2014: CSE4312 -- Software Engineering |
Please __**login**__ at the bottom of this page before proceeding. | Please __**login**__ at the bottom of this page before proceeding. | ||
Line 13: | Line 13: | ||
* Tuesdays & Thursdays 4pm-5.30pm | * Tuesdays & Thursdays 4pm-5.30pm | ||
* Tuesday lectures are to be held in SC303 | * Tuesday lectures are to be held in SC303 | ||
- | * Thursday lectures are to be held in CB120. However, some of Thursday lectures will be in the Prism Lab -- LAS 1002. Precise details to follow at this location. | + | * Thursday lectures are to be held in <del>CB120</ |
* There will be an informal lab/ | * There will be an informal lab/ | ||
- | |||
Line 27: | Line 26: | ||
* Identify the monitored variables and events and controlled variables | * Identify the monitored variables and events and controlled variables | ||
* Identify the environmental assumptions and constraints | * Identify the environmental assumptions and constraints | ||
- | * Describe the functional requirements using tabular expressions that specify the mathematical relation between the monitored variables and events and the controlled variables | + | * Describe the functional requirements using tabular expressions |
* Describe the non-functional requirements | * Describe the non-functional requirements | ||
* Prove that the functional requirements are complete, disjoint and well-defined | * Prove that the functional requirements are complete, disjoint and well-defined | ||
- | * Validate the functional requirements by proving that they preserve safety properties derived from such methods as hazards analysis | ||
* Provide a complete set of use cases and corresponding acceptance tests so that each requirement is a verifiable contract of customer needs | * Provide a complete set of use cases and corresponding acceptance tests so that each requirement is a verifiable contract of customer needs | ||
+ | * Validate the functional requirements by proving that they preserve safety properties (derived from such methods as hazards analysis) and prove that the use cases satisfy the function tables | ||
- | A work-intensive project will allow students to apply their knowledge to a non-trivial example. | + | A work-intensive project will allow students to apply their knowledge to a small but non-trivial example. |
===== Self-paced learning ===== | ===== Self-paced learning ===== |
start.1410711030.txt.gz · Last modified: 2014/09/14 16:10 by jonathan