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?

Read the entire "Reusability Across Rule Projects" post