Phoenix Rising wrote: > > Here's where agile practices come into play, and where the "rub" is: I > had an entire system finished and ready to go. Then management > stepped in, and for the third time in two months, changed it all. > Four user types got expanded to 9, and instead of 4-8 sub parts for > each user calculated differently, that got expanded from 4-15. The > changes were so sweeping that there was no way to simply "modify" > existing code. I had to start over again from scratch. >
Agile practices aside, it sounds like you want to develop a "computation engine" that can represent an arbitrary formula (it IS management driven after all) out of some number of components. Your key issue would be a decent UI for defining these nodes and how they fit together to create formulas. Calculations become a relatively simple DFS tree traversal. Node = [Constant] or [object method call] or [Operator, Node, Node] Back in the day, I did this with variant record types, and built such an engine which could compute bills from utility rate structures, or formulate deposition rates of different types of particulates from incinerators. Just food for thought. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
