General
As a business rule developer, I tend to notice that a good amount of business rules projects tend to be linear across the business. What I mean by "linear", is that I tend to notice projects that share a good amount of similarity between one project and another, all within the same business application. For example, Business_A has 5 separate rules projects, Project1, Project2, etc...
That being said, at what point does reusability, extensibility and consistency play a part in enforcing a robust and fruitful rule application, beyond the scope of the current requirements and utilization? Does it come into play during architecture? Implementation? Or does it fall all the way back in the Iterative cycle to flush out the best place to implement a scalable project?
The Business Rules Cafe is a blog about technical, business and casual discussions that center around the Business Rules community, tools and methodologies.
The authors of the Cafe are daily busines and technical users of various enterprise rule engines. We invite you to comment on the posts and contribute to the growing user base of the business rules community. If you would like to contribute to the Business-Rules Cafe, feel free to send an email to us at anytime.
