We will start to dive deep into how to structure code using Design Patterns, also mentioned by Toke. We will learn different patterns, when to use it and if it is always a good thing that design patterns exists. We will try out different patters in detail and classify them into different categories.
We will also take a look at the other side: Anti Patterns / Code Smells. We will look at some Anti Patterns and look at what we need to be aware of when designing our software. We will try to see how we dismantle classic Anti Patterns to help us heighten our quality.
We will end the lecture by looking at some different metrics for Code Quality.
Tutorial Session
Mandatory Reading
- Gang of Four Design Patterns Introduction
- Gang of Four Design Patterns
- Read the main article and familiarize yourself with at least two patterns from each category
- Structured Testing: A Testing Methodology Using the Cyclomatic Complexity Metric Page 7 - 30
- Code Smell
- When and Why Your Code Starts to Smell Bad
Extra Material
- A Complexity Measure - T. J. McCabe
- A SUPER nice write-up of Code Smells
- Much better walkthrough of Design patterns
Materials (Slides, etc.)
- Slides will be published after the lecture