I'm working on a presentation for October Rules Fest 2009
and wanted to bounce some ideas off the community on designing and organizing rules. I want to look at this from a top level perspective that would make sense to executives, not programmers.
These are three "rules" or guiding principles for designing rules:
- Simple rules
- Minimal rules
- Reusable rules
And here are three categories for organizing rules:
- Strategy rules
- Business rules
- System rules
What do you think? Can this list be any simpler... or is it missing anything?