Date
|
Lecture
|
Title
|
Slides
|
Readings
|
---|---|---|---|---|
Tue. 17.02. |
1 | Programming capability test | ||
Tue. 24.02. |
2 | Introduction; A Basic Architecture Example | ![]() ![]() ![]() ![]() |
|
Tue. 03.03. |
3 | Modularity and reusability; Abstract Data Types |
![]() ![]() ![]() |
|
Tue. 10.03. |
4 | Modularity and reusability; Abstract Data Types |
![]() ![]() ![]() |
|
Tue. 17.03. |
5 | Design by Contract |
![]() ![]() ![]() |
|
Tue. 24.03. |
6 | Design patterns 1: behavioral (observer, event library) |
![]() ![]() ![]() |
|
Tue. 31.03. |
7 | Design patterns 2: behavioral (visitor, strategy, state, chain of responsibility, command, notion of componentization) |
![]() ![]() ![]() |
|
Tue. 07.04. |
8 | Design patterns 3: creational (factory, builder, singleton), structural (bridge, composite, decorator, facade, proxy) |
creational![]() ![]() ![]() structural ![]() ![]() ![]() |
|
Tue. 14.04. |
9 | Easter holidays | ||
Tue. 21.04. |
10 | Exception handling |
![]() ![]() ![]() | |
Tue. 28.04. |
11 | Using UML for software architectures |
![]() ![]() ![]() |
|
Tue. 05.05. |
12 | Software architecture styles |
![]() ![]() ![]() |
|
Tue. 12.05. |
13 | Design for reuse |
![]() ![]() ![]() |
|
Tue. 19.05. |
14 | Design for reuse and concurrent programming |
Design for reuse:![]() ![]() ![]() Concurrent programming: ![]() ![]() ![]() |
|
Tue. 26.05. |
15 | Exam |
Note: Slides in red are non-finalized versions.