|
Size: 1183
Comment:
|
Size: 2686
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = SB Pattern language for datamodels = | #pragma keywords meta-data, meta data, pattern-language. PatternLanguage, Pattern language, patterns, Patterns = SB Pattern language for Data-models = |
| Line 3: | Line 4: |
| == Patterns == [[Navigation(children)]] |
Christopher Alexander writes the following regarding the features of his patterns~-[http://www.patternlanguage.com/archive/ieee/ieeetext.htm link]-~''':''' |
| Line 6: | Line 6: |
| '''''Name''''':PageTitlewritten in[http://en.wikipedia.org/wiki/CamelCase 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.'''''Context''''': Where in the process does this pattern apply, eg. overall planning or minute details. remember to include relevant patterns inline in the context description. | ~+´´+~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. ~+,,+~ |
| Line 8: | Line 8: |
| '''''Description of pattern''''': What does this pattern cover, the general subject no problems no solutuions, just a description of the covered subject | [http://en.wikipedia.org/wiki/Pattern_language Wikipedia] skriver om patterns: |
| Line 10: | Line 10: |
| '''''Problem description''''':'''''' | ~+´´+~A pattern language is a structured method of describing good design practices within a field of expertise. It is characterized by[citation needed] |
| Line 12: | Line 12: |
| '''''Solution''''': Observe that most people consider chocolate to be the best part of the chocolate chip cookie. Also observe that too much chocolate may prevent the cookie from holding together, decreasing its appeal. Since you are cooking in small batches, cost is not a consideration. Therefore, use the maximum amount of chocolate chips that results in a really sturdy cookie. | 1. Noticing and naming the common problems in a field of interest, 2. Describing the key characteristics of effective solutions for meeting some stated goal, 3. Helping the designer move from problem to problem in a logical way, and 4. Allowing for many different paths through the design process. ~+,,+~ |
| Line 14: | Line 17: |
| '''''Consider next''''': NutRatio or CookingTime or FreezingMethod | Our goal is to let patterns become a generative tool for making Data-model, you as a user are encouraged to augment and add patterns as you create your data-models. ---- == Pattern structure == '''''Grade''''': from 0(zero) to 2(two) stars. -** '''''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. '''''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''''': '''''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. ---- [[Anchor(ExsistingPatterns)]] [[PageList(GuidelinesForNewDatamodel/PatternLanguage/)]] |
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] skriver om 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 Data-model, you as a user are encouraged to augment and add patterns as you create your data-models.
Pattern structure
Grade: from 0(zero) to 2(two) stars. -**
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.
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:
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.