This site will work and look better in a browser that supports web standards, but it is accessible to any browser or Internet device.
Download PDF (A4)
We see a need to start creating design patterns as a basis for a complete pattern language in the domain of e-learning. These patterns should incorporate good design in order to make that design explicit based on features in systems already made and on research (see issue about asteriks).
Our suggestion for a pattern description format is a variation of the Alexandrian template that contains the following structure:
Give a name that:- covers the content (problem & solution)- is meaningful- gives rise to associations that are related to the described problem & solution
We have chosen to divide our patterns into pedagogical, organizational, or technical categories. Combinations are possible.
Should present the key elements in this pattern.
Detailed description of the problem area.
Explain: What makes this problem a problem? Why is it important to solve the problem?
Good practices that shows how the stated problem can be solved.
Which questions related to this unsolved problem would you like to be answered in the near future?
Description of type of context (e.g. audience, organisation) the solution is applicable to .
General description of critical success indicators/factors that influence use/implementation of the solution (e.g. needed roles, type of resources), resources needed to solve the problem.
Consequences of use, implementation issues, other remarks.
URL's and other documentation.
Design patterns and/or Research patterns.
The authors of the pattern.
Date of completion of pattern.
People or organizations which have been helpful with the construction
of the pattern.
Patterns constituing a complete pattern language.