aspose file tools*
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes minimal disruption to the users.... Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "minimal disruption to the users...." Watch "minimal disruption to the users...." New topic
Author

minimal disruption to the users....

Philipp Sushkin
Greenhorn

Joined: May 03, 2007
Posts: 2
"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."

hmmmmmmm... minimal disruption to the USERS (not programmers)

Should I use Java Web Start?
Maurizio Nagni
Ranch Hand

Joined: May 29, 2004
Posts: 75
no.... they just require a modular approach like a model-view or a clear decouple beetwen the server logic and the GUI logic etc..... and firt of all do it easy. Someone who has passed used a very essential structure (may be just one button) because the task is to fullfil the requirements but not to create the prototype for the database of the new millennium

bye
Maurizio
Philipp Sushkin
Greenhorn

Joined: May 03, 2007
Posts: 2
just cannot understand how "user disruption" concern with "model-view or a clear decouple beetwen the server logic".

What is wrong with java web start?


Another question:

I think DuplicateKeyException was specially introduced to suggest us how to build service layer (just look at extended search "name+location" and guessed compound primary key "name+location . As long as my low level "data access" system (Data.java) fixed with provided interface, all this features i will have to implement in service layer because i have NO DuplicateKeyException in my "data access" update function =>
in service layer it will be
lock ->
call service layer extendedFind(location+name)->
record found -> throw DuplicateKeyException
record not found->call "data access" level update(...)
unlock

What do you think?



P.S. amazing forum! =-)

B&S
Already decided:
- Transfer (value) object design pattern
- service layer (hiding locking from client, extended search, book/unbook, primary key support, etc...)
-VERY simple gui

P.P.S.
Excuse my english!
Lucy Hummel
Ranch Hand

Joined: Apr 07, 2005
Posts: 232
As mentioned already, I aggree that MVC and put a lot of or all business logic to the server are the two starting point to support minimal disruption to the users.


The topic if or/and how to throw DuplicateKeyException is already discussed serval times in this forum. I think mostly it was agreed not to throw a DuplicateKeyException.

Anyhow, it is your solution and as long as you can explain why you throw it and when, you are on the safe side.


----------------------------------<br />| SCJP, SCWCD, SCBCD, SCEA, SCJD |<br />----------------------------------
Jason Moors
Ranch Hand

Joined: Dec 04, 2001
Posts: 188
Hi Philipp,

Whilst it might be valid in a real world scenario to use Webstart to deploy your application, I would suggest in terms of this assignment that the requirement is asking you to think more about the user interface design.

"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."


For example how would you add additional functionality like create/delete records at a later stage without changing the way the user interacts with the application etc. Therefore you need to consider your navigation mechanism Menus, Buttons etc, how you layout components on the screen and how it will support future enhancement.

By defining a standard approach the aim should be that you can add additional functionality to the application without the users having to be completely re-trained.

Regards
Jason
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: minimal disruption to the users....