Trusted Components: Reuse, Contracts and Patterns
|
General info: | News | Course description | Grading | Course books | Downloads | Further reading | Wiki |
Lectures: | Subjects and Slides |
26.01.2007 | Added link to the paper regarding model checking. |
22.01.2007 | Added slides for model checking. |
15.01.2007 | Added slides for abstract interpretation. |
10.01.2007 | Added Arnout's pattern-componentization library. |
08.01.2007 | Added project evaluation assignment and slides for program analysis. |
07.01.2007 | Added example codes for exercise "from pattern to components". |
03.01.2007 | Added a link to Reuse Contracts and ETL3 (login: Talkitover, pass: etl3). Updated schedule. |
20.12.2006 | Added slides for design pattern to component and test case design exercise. |
11.12.2006 | Added slides for lecture on testing. |
06.12.2006 | Added a link to the wiki and corrected Schedule. |
27.11.2006 | Corrected Schedule. |
27.11.2006 | Added project description. |
27.11.2006 | Added the links to the axiomatic semantics. Previous slides were covering the first part of the course. Added exercises. |
16.11.2006 | Created the trusted component mailing list. If you did not receive an e-mail, please send an e-mail to Manuel. |
15.11.2006 | Added links to material for exercises. |
13.11.2006 | Added slides for exercise on components evaluation. |
09.11.2006 | Added slides for first lecture including link to assigned reading. |
08.11.2006 | Added slides from project description and exercise on metrics. |
03.11.2006 | Added slides from Andreas Zeller. |
01.11.2006 | Added a link to Eiffel Tutorial, updated slightly the text. |
29.09.2006 | Page up and running. |
Web page at the computer science department: 251-0239-00 (3G)
Trusted Components are reusable software elements accompanied with a guarantee of quality. They should be equipped with contracts describing their abstract properties. The course explores the various facets of this notion. Topics include: the notion of software quality; library design; the notion of design pattern, and whether patterns can be turned into components ("componentization"); program correctness and axiomatic semantics; testing; techniques of program analysis, model checking, abstract interpretation; proof-carrying code.
About Eiffel and O-O programming:
About Program Analysis:
Day |
Time |
Room |
Monday | 9:00-11:00 | RZ F21 |
Wednesday | 10:00-11:00 | RZ F21 |