Introduction and course organization
This only applies for software design patterns
Main goal: Identifying and applying patterns in different situations and contexts.
You are responsible for presenting a pattern you have chosen!
Things you can consider for your presentation
Please send the slides after your presentation to me
This is just a suggestion. It's okay when you have a different structure.
Based on the GoF (see E. Gamma, R. Helm, R. Johnson, J. Vlissides: Design Patterns. Elements of Reusable Object-Oriented Software. Addison-Wesley, 1995) pattern description structure.
Things you can consider for the discussion
Presentation
After grading, you will get a detailed description of how your note is compiled.
Things I will consider:
Date | Topic |
---|---|
13/10/23 | Introduction and organization |
20/10/23 | Final submission for pattern. Session is cancled. |
27/10/23 - 02/02/24 |
Presentations & discussions |
These topics are starting points. You can either chosse an pattern listed here or you can add your own one. In this case, please contact me in advance.
Source: E. Gamma, R. Helm, R. Johnson, J. Vlissides: Design Patterns. Elements of Reusable Object-Oriented Software. Addison-Wesley, 1995
Source: M. Richards, N. Ford: Fundamentals of Software Architecture: An Engineering Approach. A Comprehensive Guide to Patterns, Characteristics, and Best Practices
Source: Prof. Walter Kriha and previous semesters
The more we mange to discuss the different patterns, the more interessting the course will be!
If you have any questions about your topic, grading, presentation etc.: ask me anytime
Prof. Dr. Tobias Jordine
Room 322