User Tools

Site Tools


course_outline

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
course_outline [2012/01/12 04:22] jonathancourse_outline [2012/04/04 14:23] (current) jonathan
Line 12: Line 12:
 ===== Week 2 January 9===== ===== Week 2 January 9=====
  
-Discuss Assignment 1. Complete Requirements/Mathematical Model. Discuss in detail the requirements document for the the return on investment calculator (this may take at least two weeks). This is in preparation for a large assignnment to be handed out next week.+**Tuesday**: Discuss Assignment 1. Complete Requirements/Mathematical Model. 
  
-**Required reading**: A rational design process: How and why to fake it, Parnas and Clements [[http://dl.acm.org/citation.cfm?id=9800\h|here]] (available online via the library).+**Thursday**: Discuss in detail the requirements document for the the return on investment calculator (this may take at least two weeks). This is in preparation for a large assignnment to be handed out next week. Slides on tabular expressions (due to David Parnas). Can check input for completeness and disjointness. 
 + 
 +**Required reading**: //A rational design process: How and why to fake it//, Parnas and Clements [[http://dl.acm.org/citation.cfm?id=9800|here]] (available online via the library)
 + 
 +===== Week 3 January 16===== 
 + 
 +Discussion of Assignment 1 - right margin justification. Discussed ambiguities and incompleteness in the specification. R-descriptions versus E-descriptions.  
 + 
 +ROI RD: Start at section 3, Dictionary. Mathematical Model for ROI. 
 + 
 +**Required Reading**: //Four Dark Corners of Requirements Engineering//, Zave and Jacskon. See SVN 
 + 
 +===== Rest of the syllabus===== 
 + 
 +  * Function tables (Parnas tables). Dell keyboard. Completeness, Disjointness and well-definedness. 
 +  * Unit testing tools for Java, C# and other languages. The V-diagram, Validation and Verification. 
 +  * Parnas on documentation and Jackson on Sofwtare Engineering. 
 +  * Structure of a requirements document. Context diagram. Atomic E and R-descriptions. Mathematical model. Links between atomic descriptions and Mathematical model. Acceptance tests. Tracability matrix. Developing acceptance tests from function tables as well as atomic descriptions. 
 +  * Requirements for safety critical systems. Fairness. Temporal logic. Modelchecking
course_outline.1326342130.txt.gz · Last modified: 2012/01/12 04:22 by jonathan

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki