course_outline
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| course_outline [2012/01/12 20:55] – jonathan | course_outline [2012/04/04 14:23] (current) – jonathan | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| **Tuesday**: | **Tuesday**: | ||
| - | **Thursday**: | + | **Thursday**: |
| **Required reading**: //A rational design process: How and why to fake it//, Parnas and Clements [[http:// | **Required reading**: //A rational design process: How and why to fake it//, Parnas and Clements [[http:// | ||
| Line 20: | Line 20: | ||
| ===== Week 3 January 16===== | ===== Week 3 January 16===== | ||
| - | Start at section 3, Dictionary | + | 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//, | ||
| + | |||
| + | ===== Rest of the syllabus===== | ||
| + | |||
| + | * Function tables (Parnas tables). Dell keyboard. Completeness, | ||
| + | * 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.1326401740.txt.gz · Last modified: by jonathan
