Happy New Year everybody, Finished off another assignment last month. Hurray!
--- In [email protected], "Steve Jones" <[EMAIL PROTECTED]> wrote: > > On 04/01/2008, Eric Newcomer <[EMAIL PROTECTED]> wrote: > > In the area of integration, an interesting emerging trend has been the identification of > > common patterns. Using a DSL to implement an integration pattern greatly simplifies its > > use. People can express an integration pattern using a few DSL keywords. > > Now this could be good, but I think we often in IT focus on reducing > the 10% of software cost in development and ignoring the 90% of cost > in support. > Patterns are fun. I'm categorizing patterns into 4 levels: 1. Business level patterns: Common behavior on the way business people react to events 2. Integration level patterns: Common behavior on the way service provider such as an application/data source react to events. 3. Application level patterns: Common behavior on the way an application framework reacts to external events such as events from user interfaces. 4. Language level patterns: Java class patterns, etc. The good thing about using patterns is that I would be able to more fully know which "service" will be used when and in what manner. Note that I'm listing up "events" here and not trying to list up process flows. Not everything can be put into patterns but if it can, it often does lower initial development and support time and cost. Cheers, H.Ozawa
