comgt
cee oh em gee tee - "commgitt"
Login to access.
User: pw: ?

User Interfaces

plain i/f - e.g. terminal-based (command line interface, CLI), GUI - Graphical User Interfaces

 

  Old School New School
Human-Machine
  • Text-based terminal (e.g. VT100 - remember this...?!), Command Line Interface (CLI)
  • Proprietary command language
  • Proprietary software, e.g. PC-based that need installation before use
  • Graphical User Interface (GUI),
  • Web-based,
  • Use of standard web browsers  w/o any need for install of proprietary applications
Machine-Machine
  • Proprietary protocols
  • Often with weak security ('security' often depending simply on not anyone knowing the details of the protocol; but easy to listen and learn...)
  • Standardized protocols, e.g. FTP, HTTP, SNMP, XML;
  • HTTPS, SNMPv3, ... for better security

 

Another section has a good article around contents of web sites, details to consider when designing web user-interfaces - Repeat Customers: It is All About the Experience (INTRANET only).

 

Importance of Ease-of-Use

On traditional phone vs. computer-based telephony (like Skype) - Ease-of-Use.

Why the Desktop Phone Isn’t Going Away Anytime Soon

Internet Telephony magazine, July 2008, pg. 12

If you’re a very mobile knowledge worker, you may have a Blackberry and a laptop equipped with a telephony or unified communications (UC) client. The laptop with a headset is effectively your phone wherever you have broadband connectivity. When in the office, your desk phone’s primary use may be as a speakerphone. So why not connect a USB speakerphone (e.g. LG Nortel USB phone 8501) to your docking station, and use your PC click-to-call capabilities? If you get a call while your PC is (re-)booting, many UC systems allow you to concurrently ring your cell phone, so you won’t miss any calls. It’s business as usual. This is a perfectly workable solution for highly mobile knowledge workers like myself.

Here’s my three reasons why this may not be for everyone:

#1 Ease of use: users are comfortable with the familiar look and feel of a phone, including use of a handset, hands-free operation, and numeric key pad. IP phones with multi-line (and even color bit-mapped displays) and USB ports have taken this to new levels. IP phones can support corporate dashboards; directories with click-to-call; confer- ence managers with simplified chairman controls; push-to-talk capabilities; zone paging; and visual voicemail. They can support security, weather and IT alerts, travel advisories and company announcements. Finally, the phone, whether wired, cordless or wireless, can be converged with the desktop PC to provide a unified experience.

#2 Reliability/quality: Users want to avoid voice quality impacts during PC background activities, booting and rebooting (e.g. due to security patches) and lack of operation during power failures. They may say, “I want/need a phone to do my job”. While the PC platform is getting better every year, we’re not there for many environments! That said, the PC is a critical business tool – answering the phone while your PC is not available doesn’t necessarily allow you to conduct business in any meaningful way.

#3 Cost: A traditional phone’s TCO is about a few dollars/day, orders of magnitude less than a PC. Basic SIP phones have brought the cost points close to those of analog sets. Also, the costs of moves, adds and changes come down with IP telephony. But, isn’t the incremental cost for IP telephony on a PC close to zero? The answer is not necessarily – what about the cost of headsets which have a relatively limited life expectancy? So the question is generally less about ‘should you invest in phones?’ and more about what’s the right functionality/price, given UC, mobility needs, PC functionality and most importantly job roles and the people that do these jobs.

Tony Rybczynski (News - Alert) is Director of Strategic Enterprise Technologies at Nortel (www.nortel.com). He has over 20 years experience in the application of packet network technology.

####

See also CSS

References

Updated 2009-04-10