View Single Post
Old 03-15-2014, 10:52 AM   #26
phossler
Wizard
phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.phossler ought to be getting tired of karma fortunes by now.
 
Posts: 1,087
Karma: 447222
Join Date: Jan 2009
Location: Valley Forge, PA, USA
Device: Kindle Paperwhite
@theducks

Quote:
I may be up to 20% of the features.
No, I'd push you up to at least 50% I read all your posts

We did a big project from scratch at work, and they let the programmers basically design the UI.

Menus are loaded with jargon that doesn't translate well to 'user-speak'

'Update Table' instead of 'Create (thing)'
'Generate Report' instead of 'Display (thing)' (on screen)
'Submit Output' instead of 'Print Report'

I know that internally tables are being modified to have records added, modified , or deleted, I suggested it would be more intuitive if the UI was modeled on the 'Verb-Noun' format to address why the user sat in front of the KB:

User: "I want to update an existing project"

My very personal preference would be to have a 1st or 2nd level menu:

[Modify Existing Project]

instead of

[Table Maintenance], [Project Table], [Update]

Users come and go, but programs seem to last forever
phossler is online now   Reply With Quote