Several times I've run into business rules that I find embedded in code, that are so old, that no one can remember why they were implemented or what they could possibly mean to the business.
I'm thinking of encoding in some routines, a way to output the rules it's using on a periodic basis (like once a month?) so that business users are made aware of what the rules are, and can therefore comment on what they should be, or what should be removed. Anyone do this? Or have thoughts about what I'm proposing? _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
