User Tools

Site Tools


start

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
start [2014/09/14 16:08] jonathanstart [2014/10/02 00:56] (current) jonathan
Line 1: Line 1:
 ~~NOTOC~~ ~~NOTOC~~
-====== EECS4312  Fall 2014: Software Requirements Engineering======+====== EECS4312  Fall 2014: Software Engineering Requirements======
  
-**Fall 2014: CSE4312 -- Software Requirements Engineering**+**Fall 2014: CSE4312 -- Software Engineering Requirements**
  
 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</del> BC215. However, some of Thursday lectures will be in the Prism Lab -- LAS 1002. Precise details to follow at this location.
     * There will be an informal lab/tutorial every Thursday in LAS1002 from 1pm to 2.30pm     * There will be an informal lab/tutorial every Thursday in LAS1002 from 1pm to 2.30pm
- 
  
  
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 (function tables)  that specify the mathematical relation between the monitored variables and events and the controlled variables
     * 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 suite of 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.1410710918.txt.gz · Last modified: 2014/09/14 16:08 by jonathan

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki