Menu
In my project I need to create a business object validation layer that will take my object and run it against a set of rules and return either pass or fail and it's list of failure reasons. I know there are quite a few options out there for accomplishing this.
From Microsoft:
Open Source:
Has anyone had any particularly great successes or failures with any of these technologies (or any that I didn't list) or any opinions on what they feel is best suited for business rules validation.
Edit: I'm not just asking about generic validations string length < 200, zip code is 5 digits or 5+4 but assume that the rules engine would actually be leveraged.
835
The guidelines on general principles of process validation mentions four types of validation: A) Prospective validation (or premarket validation) B) Retrospective validation. C) Concurrent validation.
Business logic tier validation assumes existing data is valid. The business logic tier employs validation logic when it needs to create or change data, but it assumes that data already in the table is valid.
What Is Market Validation? Market validation is the process of determining if there's a need for your product in your target market. Validating your business idea can enable you to reasonably predict whether people will buy your product or service, and whether your business will be profitable.
Data validation should occur in two locations: The point where data is acted upon, for example validating input parameters to an SQL query. General validation at the point where data is submitted, for example in a web application some validation should occur on the client.
The code-versus-rules-engine decision is a matter of trade-offs, IMHO. A few examples are:
(Features vary across the various rule engines.)
117
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
