Lesson details

• Teams brainstorm on explained patterns and make joint notes (anywhere).
• Teams select N most suitable patterns from the brainstorming, where N is the size of the team.
• Each team member takes one pattern, studies its details, and elaborates on its usage.
• Each team member reviews two proposals of pattern application. To do that, study the pattern deeply. It doesn't matter if the IS MU selects a proposal from a teammate. 
• Teams collect reviews on their proposals and reflect the feedback in the final patterns application proposal. Although each (corresponding) author is responsible for "its pattern", the finalization should be consulted, conducted, and agreed upon by all team members (and is submitted as a joint document).

Required output

• Until Tue. 25.10. noon, each student submits a proposal of one pattern application. A template for pattern application is hereafter. Submit the proposal to the 06 - Design patterns brainstorming I homework vault (odevzdávárna) in the IS MU. Name the file accordingly (follow the instructions in the template).
• Until Thu. 27.10. noon, each student writes two reviews. Focus primarily on the understandability of the description, then on the correctness of the application.
• Until Fri. 28.10. noon, each team submits a final proposal of patterns. Use the template below and submit it to the 08 - Design patterns brainstorming - final proposal homework vault (odevzdávárna).
• Expected patterns:
  • Composite: At least three proposals, at least one is different from the implementation of the Enterprise Segment.
  • Builder: At least one tree (step-by-step building of the Composite) plus at least one additional proposal (non-composite).
  • Strategy: At least two proposals (different from builder ;)