The best practises says Business rules should be documented in a seperate document. is this right
I have seen use cases with business rules being done. Is trhis correct
what should be the right format for business rules.
Hello sraaj,
There is no one right way when it comes to business rules. Or any form of requirement for that matter.
Here are some questions to help you think through how to manage this content;
As for the phrasing of business rules; there is no current recommended best way, although if you search the internet (eg the business rules group) you'll see some guidelines. The general guidance is specific, and unambigous, but plain user oriented langauge.
Hi Sraaj,
Its a good idea to list your business rules in a separate register. This is because the relationship between business rules and use cases is many to many, so if you put them in your use case you're in danger of having to update the one rule in multiple places. You will need to link your business rule to the use case(s) it is associated with. A modelling tool will make this easier for you. Doing it just using ms word is trickier and can potentially make your document harder to read. Bit of a trade off between best modelling practice and readability.
If you keep them in a separate document that will make it even harder to read unless you can automate pulling the business rule into the use case document.
Kimbo
Sraaj, Business rules govern the system's behaviour; and usecases capture this behaviour. Example one business rule could influence 1 or more use cases; or one use case satisfies 1 or more business rules. From an ERD perspective, it’s a many to many relationship, which is resolved with an RTVM (requirements traceability verification matrix) that links the use cases with business rules. It also has the added benefit, that when a business rule changes, you know which use cases are affected, and if a use case (behaviour) changes, You'll check to see if it still satisfies the business rule constraints. So you best practice assertion is correct! yes, keep them separate! warm regards, K
Sraaj,
Business rules govern the system's behaviour; and usecases capture this behaviour.
Example one business rule could influence 1 or more use cases; or one use case satisfies 1 or more business rules. From an ERD perspective, it’s a many to many relationship, which is resolved with an RTVM (requirements traceability verification matrix) that links the use cases with business rules. It also has the added benefit, that when a business rule changes, you know which use cases are affected, and if a use case (behaviour) changes, You'll check to see if it still satisfies the business rule constraints.
So you best practice assertion is correct! yes, keep them separate!
warm regards,
K
yes ,
Business Rules be in a seperate document.
its such a good idea........
brought to you by enabling practitioners & organizations to achieve their goals using: