Jump to content

Software analysis pattern

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Huygens 25 (talk | contribs) at 00:21, 1 February 2007 (Page creation, missing examples, development of the concept, etc.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)


Software analysis patterns or simply analysis patterns are conceptual models, which capture an abstraction of a situation that can often be encountered in modelling. An analysis pattern can be represented as "a group of related, generic objects (meta-classes) with stereotypical attributes (data definitions), behaviors (method signatures), and expected interactions defined in a domain-neutral manner" say Purao, Storey and Han (2003)[1].

Martin Fowler defines a pattern as an "idea that has been useful in one practical context and will probably be useful in others"[2]. He further on explains the analysis pattern, which is a pattern "that reflects conceptual structures of business processes rather than actual software implementations".

Examples

Event

Figure 1: Event analysis pattern

Martin Fowler describes this pattern as one that "captures the memory of something interesting which affects the domain"[3].

See also

References

  1. ^ Purao, Sandeep (2003). "Improving Analysis Pattern Reuse" (PDF). Information Systems Research, Vol. 14, No. 3: pp. 169-290. ISSN: 1526-5536. Retrieved 2007-01-31. {{cite journal}}: |pages= has extra text (help); Cite journal requires |journal= (help); Unknown parameter |coauthors= ignored (|author= suggested) (help); Unknown parameter |month= ignored (help)
  2. ^ Fowler, Martin (1996-11-27). Analysis Patterns: Reusable Object Models. Addison-Wesley. ISBN 0201895420.
  3. ^ Fowler, Martin. "Accounting Patterns" (PDF). Analysis Pattern. Retrieved 2007-01-31.

Further reading