|
Size: 2778
Comment:
|
Size: 2910
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 21: | Line 21: |
| For patterns there is a PatternTemplate try to use this and look at templates by others to let yourself be inspired. |
|
| Line 25: | Line 27: |
| '''''Name''''': PageTitle written in CamelCase or [:Page title:Page_title] written with underscore as the delimiter, you are encouraged to use the underscore for legibility reasons, '''AND match''' it to the heading of the pattern. Try to think of a descriptive, but not to long name. | '''''Name (and grade)''''': PageTitle written in CamelCase or [:Page title:Page_title] written with underscore as the delimiter, you are encouraged to use the underscore for legibility reasons, '''AND match''' it to the heading of the pattern. Try to think of a descriptive, but not to long name. |
SB Pattern language for Data-models **
Christopher Alexander writes the following regarding the features of his patterns[http://www.patternlanguage.com/archive/ieee/ieeetext.htm link]:
´´First, it has a moral component. Second, it has the aim of creating coherence, morphological coherence in the things which are made with it. And third, it is generative: it allows people to create coherence, morally sound objects, and encourages and enables this process because of its emphasis on the coherence of the created whole. ,,
[http://en.wikipedia.org/wiki/Pattern_language Wikipedia] says about patterns:
´´A pattern language is a structured method of describing good design practices within a field of expertise. It is characterized by[citation needed]
- Noticing and naming the common problems in a field of interest,
- Describing the key characteristics of effective solutions for meeting some stated goal,
- Helping the designer move from problem to problem in a logical way, and
Allowing for many different paths through the design process. ,,
Our goal is to let patterns become a generative tool for making the Data-model, you as a user are encouraged to augment and add patterns as you create your data-models.
For patterns there is a PatternTemplate try to use this and look at templates by others to let yourself be inspired.
Pattern structure
Grade: from 0(zero) to 2(two) stars. -** the grade is appended to the pattern Name
Name (and grade): PageTitle written in CamelCase or [:Page title:Page_title] written with underscore as the delimiter, you are encouraged to use the underscore for legibility reasons, AND match it to the heading of the pattern. Try to think of a descriptive, but not to long name.
Context: Where in the process does this pattern apply, eg. overall planning or minute details. remember to include relevant patterns in-line in the context description.
Description of pattern: What does this pattern cover, the general subject no problems no solutions, just a description of the covered subject. This text is entered in Bold Font
Problem description: Describe what the goal of this pattern is.
Solution: What is the encouraged approach to solving the problem of this pattern? This text is entered in Bold Font
Consider next: What options do the use of this pattern bring about, what path does it send the user along. How does it interact with other patterns. Include in-line references to likely patterns which can influence the product along with this pattern.