Differences between revisions 15 and 26 (spanning 11 versions)
Revision 15 as of 2009-11-04 13:42:42
Size: 1919
Editor: eab
Comment:
Revision 26 as of 2009-11-04 15:07:59
Size: 2729
Editor: eab
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= SB Pattern language for Datamodels = = SB Pattern language for Data-models =
Line 6: Line 6:
~+´´+~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.
~+,,+~ 
~+´´+~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 9: Line 8:
Our goal is to let patterns become a generative tool for making Data-model, you as a user
== Patterns ==
[[Navigation(children)]]
[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]

   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. ~+,,+~


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 ==
Line 21: Line 31:
'''''Problem description''''''''''':'''''' '''''Problem description''''': Describe what the goal of this pattern is.
Line 25: Line 35:
'''''Consider next''''': What options do the use of this pattern bring about, what path does it send the user along. Include in-line references to likely patterns which will be influenced by this pattern choice.  '''''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] 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]

  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. ,,

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: 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.


GuidelinesForNewDatamodel/PatternLanguage (last edited 2010-09-30 08:30:49 by eab)