The document discusses various design patterns and their applications, particularly in email spam filtering systems, with a focus on multiple spam detection algorithms and report generation methods. It outlines two mini seminars that will cover best practices, development principles, and the integration of Mylyn with project management tools. The emphasis is on enhancing task-oriented interfaces, traceability, and effective code review processes.

1. Design PatternsStrategy

2. Adapter

3. Decorator

4. Chain of responsibility

5. Design PuzzleMini seminār #1 followup

6. Application: Email spam filtering system. Both HTML and Text formats should be supported.Multiple spam recognition algorithms are present and several could be used simultaneously.Multiple weekly report approaches should be supported: XML, HTML files on filesystem;+ email  with report attachment.Mini seminar #1:Pattern puzzle

7. Pick up to 2-3 design patterns to review next timeQuestion to audience

9. Best practices: Mylyn & Atlassian connectors(Mini Seminar #2)Leonid M.

10. Development processValues & Principles: Brainstorming?

11. Practices: Brainstorming

12. ESWIJI project on the mapMylynTying it all together (in context if ESWIJI project)Mini seminar #2: Agenda

13. Brainstorming: Values?

14. Brainstorming: Practices?

15. ESWIJI project on the mapUse tools not brains

16. Easify & Delegate Mylyn

17. Code change – is change request - Mylyn enables task focused interface, coding against a task is a MUSTBug tracking systemsMylyn to “anything” connector (unified interface)Issue & document linkingCommit is linked against task

18. Task context is linked to the issue