Image, you nailed it on the head..
One of the big problems in enterprise level applications is that once your architecture is down, changes are very hard and very expensive to make and test. Regression testing will eat you alive if you make widesweeping infrastructural changes, so usually once your product architecture is down, it stays that way except through gradual 'small' changes to minimize impact. Change too much, and you probably broke 20 things you didnt mean to impact. So make small, frontside changes.
The way that changes will usually happen is that someone identifies a bug, a change request is initiated, a developer investigates the issue, codes the fix, unit tests it, pushes it out to integration testing, then QA, the CAT (Test server for EQ), then up to production. Along each step you're testing with multiple test cases, and in big cases, huge numbers of test cases to verify you havent broken or change anything you didnt intend too.
If they're smart, they'll carry the lessons learned on the design and all the things that can't change in EQLive because it's now 'etched in stone' , and apply those design principles to EQ2...
__________________
Quitters never win, and winners never quit, but those who never win and never quit are idiots.
|