Topic: Design decision for adding Computer Models
I am developing a cost model tool for my work and I am thinking of using ruby on rails as the platform. My primary reason is that I want to be able to use the unit testing in Rails in order to speed up the validation part of the "Computer Models". Please note that models here refer to Computer Models that determine cost. I am not talking about objects.
One of the design decisions that I am facing is that these Computer Models will change over time. The tool must be able maintain the old models and be able to rerun them by the user. We also must be able to maintain the old inputs that went into the older models.
Now their are currently around 70 computer models that I am trying to integrate. Those 70 models use similar inputs. Thus model A and model B will have a similar input but are not exactly the same as they also will have different inputs.
So for the same class a couple different computer models will use similar inputs.
Like the following:
Now I am thinking of designing it as follows:
For every Computer Model I would have a Rails Model with a MySQL table. When I need to change a Computer Model I then add a Rails Model and another MYSQL Table. My current thinking is that this is the only way I can maintain the history.
I wanting to hear back from a few people about this choice. I also want to know if anyone has had a similar issue and what they did to solve the problem. Feel free to tell me I am off my head out of the clouds.
Thanks for any feedback,
Last edited by pkudrle (2007-02-27 12:30:22)