• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Future Proof Design?

 
Daniel Haupt
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I'm about to finish my assingment and I'm just wondering if anyone had take care of a future proof design.

The B&S Assignment says something of "Your user interface should be designed with the epectation of future functionality enhancements, and it should establish a framework that will support this with minimal disruption to the user when this occurs". Is this already done by using the model view control pattern or must I think a little bit deeper in this?

Another part of the assignment says "Bodgitt & Scarper wants to move into Internet-based marketing, and hopes to be able to provide their services directly to customers over the web." Have I to think about enterprise patterns, e.g. ValueList to prevend a loading overhead working with lists of tenthousand and more records?

How important are these issues according to the marking process of the assignment?

Thanks for your answers

Daniel
 
mohamed sulibi
Ranch Hand
Posts: 169
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hiz;

i think you are right MVC for client interface is what the instruction mean.

Regards.
Mohamed darim.
 
Jean Robillard
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Daniel, when you say MVC, are you talking about Swing's MVC or your own? If it's former, it won't be useful if we move to a web-based system later. you'll have to throw out Swing UI and its assocated model and controller altogether. So, you can't just swap out Swing UI "view" and institute JSP.

But then, implementing our own version of MVC without using Swing's MVC is very unnatural and it'll not be the right use of Swing. It will result in a bloated code just to skirt around the normal Swing usage.

I think all we can do is to make sure that the changes to the lower layer (e.g. business layer and DB layer) will be minimized. Put as little business logic as you could (or none at all) in the UI layer.
 
rinke hoekstra
Ranch Hand
Posts: 152
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I didn't do much with "future proof design". There are many contradicting requirements.
The requirements also state that the code should be simple and straightforward, understandable by a junior programmer. I felt that MVC for such a simple program is much overkill, and NOT a simple and straightforward design.

Also my assignment says this:
"The IT director does not anticipate much reuse of the first Java technology system, but intends to use that system as a learning exercise before going on to a web based system."
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic