This is my first post (i think) and I was wondering if I could have a opinion from you all.
Today, the system I'm working on has a terrible design for business logic. The application is basically a bunch of formula "calculators" for every different client. All of them have their input/outputs and logic on it. The problem is that every single calculator is derived from a big superclass with some common procedures (and eventually subclasses overrided them ).
Well I really want to refactor this crap. I was thinking of the Interpreter pattern which I could take the similiarities of the calculators and mount its complexity based on those simple procedures.
It would look like a tree:
However, I don't want to reinvent the wheel and possibly somebody else has come across this problem. I just need to know if there is a framework, standard, pattern, whatever... to solve this problem.
I was wondering if I could have a opinion from you all.
Today, the system I'm working on has a terrible design for business logic. .
If it ain't broke ...
Retired horse trader.
Note: double-underline links may be advertisements automatically added by this site and are probably not endorsed by me.
Valdir Mendes
Greenhorn
Joined: Jan 05, 2008
Posts: 8
posted
0
It wouldn't be a problem if I had to create more 20 of those
I've seen Drools the business rules engine as an alternative, but I might create more complexity than simplicity. Anybody with Drools experience to share thoughts (or any other business rule engine)?
Strategy and/or template pattern come to mind when I read this.
But I agree that you should make sure about the value you'd get from redesigning this system. If it's a new 'calculator' every day then I'm sure you can get whoever it is that decides to at least consider something more flexible. If it's a new one every year ... (or any other period of time that is considered 'long'
0
).
