Your user interface should be designed with the expectation of future functionality enhancements and it should establish a framework that will support this with minimal disruption to the users when this occurs.
SCJP (77%)
Originally posted by Simon Ingram:
Clearly if the user wants to add new functions, we must change the GUI but the instructions seem to hint that there is something the developer can do to minimise the impact of such requests - some kind of framework. My question is what framework? The MVC design should isolate the view from the database, such that a GUI enhancement does not affect the whole application. Is this what they mean?
Regards, George
SCJP, SCJD, SCWCD, SCBCD
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7 Personal blog
Originally posted by Simon Ingram:
Thanks, George! I had a feeling someone would say this. Problem is that I have an MV pattern, if such a thing exists. i.e. no explicit class acting as a controller. OK, I admit to feeling a bit guilty about it, but it seemed so easy to call methods on the database directly from the gui! In fact introducing a controller seems to complicate matters, but I am still left with an MV and not an MVC and a sneeky feeling that I may be in violation of the OO design rules. My question is, am I the only one?
By the way George, that was an interesting post you submitted about the cyclical dependencies. I had never heard of them before but they sure sound nice and scary!
regards,
Simon
Marco Tedone<br />SCJP1.4,SCJP5,SCBCD,SCWCD
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |