GUI vs Green Screen

[jim_oberholtzer@xxxxxxx]

     The one problem that has escaped all but one of the posts I have read 
     here is the design.  If we professionals in the field are doing the 
     proper job of requirements gathering, functional and detail design, 
     (yes there are three distinctly different things to do) the user 
     interface becomes a mute point and will be described in the design.  
     Cost of ownership, education, (educate people, train monkeys), 
     performance, and the like are all factored into the business decision 
     for the application.
     
     I am designing a report distribution system that requires the 
     Internet, and a browser as a delivery vehicle.  I am still not 
     designing a GUI interface.  The user will still need to hand enter 
     parameters, passwords and the like.  While the browser can be a GUI, 
     it's not required.
     
     Because I use Client Access or Netsoft to access my AS/400, and those 
     applications run under windows, I am not using a GUI interface, merely 
     multitasking.  Windoze does not make me more efficient, just more 
     expensive.
     
     Remember, we cannot be entranced by the technology simply because we 
     can do it.  The scientists could clone a human if they wanted to, but 
     is it the right thing.  While that analogy might sound a little far 
     off, its really not.  Use what is needed, not what is way cool.
     
     
     Jim Oberholtzer
     Information Builders
     jim_oberholtzer@ibi.com
     630/971-6700 x302

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---