Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX: GUI, functionality enhancements, essablish a framework?

 
Peter Yunguang Qiu
Ranch Hand
Posts: 99
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
the instruction says:
"Your user interface shoud be designed with the expectation of future functionaliy enhancements, and it shoul establish a frame work that will support this with minimal disruption to the users when this occurs."
I am not clear with this statement. "establish a frame work,", means MVC? "future functionality enhancements", What functionality enhancements? GUI or database or other componets enhancements?
Peter
 
Javini Javono
Ranch Hand
Posts: 286
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
The first question to try to get a hold of is this:
"What future expansions to the application might be made?"
Any one know?
I simply implemented my user interface as tabbed panes.
So, future enhancements can be made in a new tabbed pane,
leaving my original tabbed pane alone until it was finally
removed. But, I can't say this answers the question
either correctly or totally.
Thanks,
Javini Javono
 
Jason Mowat
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I feel that if you implement the code so that you can easily add to it in the future, you will be satisfying the requirement. If you develop the application using the MVC pattern, you should satisfy that requirement.
I'm not sure implementing the tabbed panes is worth the effort. My personal focus was to implement what I am going to be marked on. Adding extra graphical "goodies" was not a priority for me. However, I know that my MVC design can easily be extended to include the addition, deletion, etc, of customers, and the GUI can be quickly extended to accommodate this. Furthermore, the model and controller components can be changed without adversely affecting the users.
With all of that being said, I would focus on providing a clean implementation on MVC and only build your GUI to accomodate the specific task. Resist the urge to do more than necessary, as you won't get any credit for it.
Just my 2 cents
Cheers,
Jason
 
Ken Krebs
Ranch Hand
Posts: 451
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Regarding possible future expansions:
Well for starters, how about the functionality that was put in the Data class but is not used by the gui, i.e. create and delete. Some more flexible searching would probably be added as well. And for good measure, the update of other contractor fields.
[ January 17, 2004: Message edited by: Ken Krebs ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic