Periodically I get asked about bringing business rules into the Rational Unified Process or RUP. RUP and the Enterprise Unified Process are designed to apply UML and best practices in a formal way.
They do not formally manage business rules but consider them part of Use Cases or of requirements. To design
Several changes are typically required:
Found an error or have a suggestion? Let us know and we'll review it.
Business rules are easy to verify as they are close to the business. Rules management encourages constant monitoring and this improves software quality. Business users can really give you feedback on rules in a way they could never do with code.
Traditional software systems can be “brittle” – small changes can break them. Decision services built with usiness rules are expected to change and can be updated individually even in 24x7 environments.
While business rules should not be managed like requirements, they should be managed in parallel with them. Rule management provides a means of managing "requirements" as explicit business rules, throughout and beyond application development.
Decision Services separate business logic into re-usable, manageable components.
If “a picture is worth a 1000 words” then business rules could be worth many lines of code. Business rules and their interrelationships can be visualized and management more easily than code, resulting in more of the application being managed more visually.
Suggest a Correction
No comments yet. Be the first to comment!