January 3, 2008
More and more I'm starting to pay attention to the discussions regarding DSLs (Domain Specific Languages). Specifically, I've been thinking about business rules as a sort of DSL. Scott Bellware and I have had many conversations about this. To me, how we define business rules is a good example of a Business DSL. A simple business rule example: Object Type: Case Rule Name/Description: Notify all queue members upon dispatch Start Event: Dispatch Cancel Events: Accept Conditions: None Action Title: Notify Queue Members Who to Notify: Current Queue Members Start Action: 0 minutes From: Event Creation Using: Elapsed Time Repeat Every: 4 hours Repeat for: 999 days Message: [Object Type] [Object ID] has been dispatched to queue [Current Queue]. Ayende had a recent post that touched on keeping DSLs under source code control, and testing DSLs. This got me to thinking about an issue we have in Clarify today. If…
Testing Business Rules
January 3, 2008
More and more I'm starting to pay attention to the discussions regarding DSLs (Domain Specific Languages). Specifically, I've been thinking about business rules as a sort of DSL. Scott Bellware and I have had many conversations about this. To me, how we define business rules is a good example of a Business DSL. A simple business rule example: Object Type: Case Rule Name/Description: Notify all queue members upon dispatch Start Event: Dispatch Cancel Events: Accept Conditions: None Action Title: Notify Queue Members Who to Notify: Current Queue Members Start Action: 0 minutes From: Event Creation Using: Elapsed Time Repeat Every: 4 hours Repeat for: 999 days Message: [Object Type] [Object ID] has been dispatched to queue [Current Queue]. Ayende had a recent post that touched on keeping DSLs under source code control, and testing DSLs. This got me to thinking about an issue we have in Clarify today. If…