Enterprise Decision Management - a Weblog

This introductory session covered patterns and was a useful recap. A pattern is a reusable solution to a recurring problem. Patternscan beat a high level (architectural pattern) or object oriented design level (design pattern) or indeed at any number of other levels or about other topics. Patterns have a number of elements:

• Name
• Synopsis
• Context/Problem Statement
  Some information about the drivers for this pattern
• Forces
  Why would you use the pattern
• Solution
  An explanation
• Consequences
  Pros and Cons
• Implementation
• Related Patterns
  Patterns combine into Pattern Languages of related patterns.

All of this got me thinking about EDM patterns - what are they? what can I say about them? This is my last post from the conference as I am off home tonight. If you live in the Washington DC or San Diego area, consider coming to the ITARC events there - more at www.iasahome.org.

Technorati Tags: architecture, pattern