Syndicated from ebizQ
Adrian Marchis had a nice article on Use Case Recycling by Extracting Business Rules. Now making sure decisions are identified explicitly in use cases avoids one of the seven deadly sins of decision management and is something I think is critical. Indeed I wrote an article on the topic on the same network as Adrian’s – Using Decision Management to improve Requirements. I have also blogged before about the need to keep process, decisions (rules) and requirements nicely separated as one develops a specification and Scott Sehlhorst and I posted a slide deck on the topic too:
The bottom line is this:
- Look for decisions in your use cases
- Make them explicit
- Track but don’t embed the rules that drive them
This way your requirements will easily support decision management and business rules going forward.