Patterns

From Elearning

In essence a pattern solves a problem. This problem should be one that recurs in different contexts. In teaching we have many problems such as motivating students, choosing and sequencing materials, evaluating students, and the like. [1]

The idea of treating design solutions as patterns comes originally from Architecture, and the work of Christopher Alexander. Patterns have long been a part of software engineering, and have recently been suggested by Peter Goodyear as a means of bridging the gap between pedagogical theory and teaching practice. [2]

Here, the aim is to develop a repository of teaching patterns that will allow university faculty and staff to effectively share their experience and know-how.

The patterns offered below are lightweight contextual responses to everyday teaching and educational design problems.

They are here to be tried, refined and added to by you.

Contents

List of Available Patterns

This page also lists available patterns available within the Test Tube.

  • Assessment map - Getting students to work on their assessment tasks ahead of the due-date.
  • Tutorial heaven - Getting students to complete the readings for tutorials, so as not to waste valuable face to face sessions.
  • One for all and all for one (OFA+AFO) - Combining individual tasks with group interaction.
  • Marker's shoes - Getting students to understand what's required of them for an assessment task.
  • Marker as editor - Encourage students to read your feedback on their assessments and reward them for responding.
  • Peer instruction - Make lectures more interactive and engaging by using MCQs and peer discussion
  • Spiral
  • Mistake

Adding patterns

"Is that a pattern I see before me?"

Often a pattern starts out as a hunch. You may be inspired by a certain experience of using a tool, or from reading a case study. In any case, if you find yourself asking this question,

  • jot down the outline of your idea on the discussion page associated with that tool or case-study, or
  • add your idea to the Pattern workshop. (This can be useful if you can't find an appropriate discussion page for your idea.)

Creating a new wiki page for your pattern

If you're feeling confident, simply start a new wiki page for your pattern. New pattern pages can be created by adding a wikilink to the list above. Once you've saved this page, the link will appear.

You may wish to use the Template:PatternPage, which can be copied and pasted to ease the creation of new pattern pages. Visit the template for instructions on how to use it.

Editing existing patterns

Feel free to modify any pattern page to reflect your teaching experience. If you have tried something similar, let us know. If you have concerns about using this pattern, speak up. If it helped you, tell us where, when and how.

Simply click on the edit tab at the top of the pattern to register or login, and then make whatever changes you want.

Don't worry too much about keeping the page in pristine condition. What's important is that you get your perspective somewhere on the pattern page (or on the associated discussion page). As the Wikipedians say, be bold!

Pattern Infobox

Test Tube : Pattern

This page describes an intuitive educational strategy.

Assessment map Tutorial heaven
OFA+AFO Marker's shoes
Marker as editor Peer instruction
For examples, see Case-Studies. For eLearning technologies, see Tools.


On the right hand side of each pattern, you'll see an infobox like the one on the right, allowing you to quickly move between available patterns.

Structure of a Pattern

This is the standard structure for a pattern, as presented on Fourteen Pedagogical Patterns, by Joseph Bergin

(Nb: this list needs editing! --Jtauber 17:41, 2 May 2007 (EST))

  1. Metaphorical Title
  2. Brief description
  3. Problem / Issue
  4. Audience Context
  5. Forces
  6. Solution
  7. Discussion / Consequences / Implementation
  8. Special Resources
  9. Related Patterns
  10. Example Instances
  11. Contraindications
  12. References / Comments


Alternative pattern structures

Christopher Alexander's original structure
  1. Picture (archetypal example of the pattern)
  2. Introductory paragraph setting the context
  3. * * * (beginning of the pattern)
  4. A headline in bold, describing the problem in brief
  5. Body of the problem - empirical background, evidence, examples
  6. The solution in bold, stated as an instruction on how to build the pattern
  7. Diagram of the solution
  8. * * * (end of main body of the pattern)
  9. Reference to smaller patterns required to implement this pattern
Modification of Alexander's structure by Markus Voelter

(http://www.voelter.de/data/pub/tp/html/index.html)

  1. Pattern name
  2. Problem description
  3. Solution outline, consequeces, drawbacks
  4. Examples and additional implementation information
Goodyear's (2005) modification of Alexander's patterns for Ed Design

(abstracted from the Discussion group pattern described there, in Figure 3)

  1. Title in bold
  2. Intro paragraph
    • Including patterns which this pattern may contribute to (i.e. parent patterns)
  3. * * * (beginning of the pattern)
  4. Lead paragraph, stating the problem or objective motivating this pattern
  5. Detail of the problem/objective
    • What the pattern should achieve
    • Risks/costs of not doing anything
    • Evidence/reference material
  6. Statement of the pattern, in the form of an instruction
  7. * * * (end of main body of the pattern)
  8. Paragraph listing the pattern required to implement this pattern
Personal tools