Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

Interfaces Expand / Collapse
Author
Message
Posted Wednesday, April 22, 2009 9:10 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 9:30 AM
Points: 33,062, Visits: 15,177
Comments posted to this topic are about the item Interfaces






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #702880
Posted Thursday, April 23, 2009 5:43 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 1, 2009 6:37 AM
Points: 9, Visits: 17
I'm surprised at your comment about voice recognition software. My wife is a medical transcriptionist who uses Dragon Naturally Speaking with nearly 100% accuracy. I think the misconceptions about Dragon are because most people aren't aware what's involved with putting a system together. If you just install the software and start dictating there will be errors. The system needs to be "trained" by feeding it dictation and correcting the errors. It really does learn. Dragon is also hardware dependent. You need a fast system with plenty of RAM and a GOOD microphone and sound card. There's no question that a properly trained voice recognition system with appropriate hardware will outperform manual typing, particularly with something repetitive such as filling forms.
Post #703058
Posted Thursday, April 23, 2009 6:19 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, July 17, 2014 2:15 PM
Points: 1,788, Visits: 594
I've found that data entry errors are not hardware/software dependent so much as they are user influenced. My company teached people to use software such as Dragon Dictate and Viavoice and with suffucient training we've seen people with 95% accuracy. I've also seen people with a keyboard have terrible accuracy. We've suffered with finding errors in our data and most of it tracks to specific users. Some people are not good at data entry not matter what hardware/software configuration they use. You must have a mind set to sit at a desk and key all day.
Just like not everyone can be a good programmer or a good DBA; you have to enjoy what you are doing.
If you could take the human element out of data entry then you could reduce errors.
Ah a technocracy!
Post #703077
Posted Thursday, April 23, 2009 6:58 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, December 2, 2013 6:30 AM
Points: 346, Visits: 691
This topic has two main thrusts, voice input and data validation.

Voice recognition as a general input device will never work. Ever. In certain domains it's a perfect fit--such as giving short commands (a few words) when your hands are busy (driving, for example). In that domain there's simply nothing better.

But general computer input? Nope.

I experimented with a PERFECT V/R input system. It could convert text as fast as I spoke, it understood context at a human level, and also knew exactly what was going on.

In case you haven't guessed the "V/R input system" was a person. :) You can't get better VR than that! My girlfriend at the time was curious about V/R so we tried experiments where we alternated as "input system".

Worked flawlessly. There were some serious problems tho.

1) Input speed. Typing for a skilled typist is simply faster. I can cruise all day long at 50 WPM, and hit bursts of 80. No one talks that fast. :) Inputing numbers via voice is clumsy and error prone and signaling end of field can be tricky. Not to mention the arbitrary punctuation in programming languages.

2) Accuracy. Even a "perfect" system (a human) can be confused by context, pity the poor computer!

3) Your voice gets tired. Speaking for hours at a time? Egads.

4) You bother others around you. Phone centers are one thing, but for work requiring quiet concentration? Say developing an application? :) Or a library? Not to mention programming languages are not suited for VR.

Given 3 and 4 alone VR for general purposes is a bust. And can you imagine entering a password via voice? :) 'Nuff said.

Now on to data validation in general.

When you have people in the mix there are going to be problems. The best approach I've found is to catch the error as soon as possible. Simple things like not putting letters in a numeric field have pretty much been covered. Then there's boundry checking, and drop down lists--well, you know the drill.

Back in the punch card days (and yes, I'm dating myself :)) critical data input was done *twice*, by two different people. If the records didn't match they were rejected and sent back for input again. Obviously that's horribly expensive but it is effective.

Keeping people out fo the loop as much as possible is really the only answser. Don't double-enter data, don't have redundant data. SPOT, all the way. :)

Of course once data's in it really needs to be verified--especially addresses. We found this out the hard way at work...

Post #703110
Posted Thursday, April 23, 2009 7:00 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, August 4, 2009 6:49 AM
Points: 18, Visits: 21
I think voice recognition has it's place. Even in Star Trek, they don't use voice for everything. Things like queries (computer, where is Capt Pickard) or running simple things (Computer, start Word :) ).

But for a lot of things, driving the ship, controlling the engine room - they still use keypads.

I think that will always be - at least until we find a way to get our thoughts directly into the computer. Until then, I think we'll always be able to type faster than we can speak.

My two cents.
Post #703111
Posted Thursday, April 23, 2009 7:17 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 10:03 AM
Points: 1,849, Visits: 2,010
I suppose the only problem I really have with keyboards is that the keys for your left hand slant the wrong way. Considering how narrow keyboards are compared to how wide a person's shoulders are, your arms are natrually positioned like / \
but almost all keyboards are layed out like \ \. I can live with the key arrangement, it's OK, I don't necessarily think Dvorak keyboard layouts are the answer, although I've barely ever used them.

The real answer of building better interfaces will be with building smarter systems that can give the user fewer choices, like how modern UIs have drop down combo boxes instead of simple prompts where the user had to remember a bunch of codes and symbols to type in manually. But for long messages or strings of text there will always be the need to type it out character by character on a keyboard.
Post #703135
Posted Thursday, April 23, 2009 7:53 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, February 6, 2014 12:59 PM
Points: 801, Visits: 1,962
I do a lot of DC work. I prefer ADC whenever possible. Take, for example, a fuel delivery person. I know which fueling station is being serviced because of the GPS coordinates when the truck pump is switched on. I have level sensors in each tank. I know the level at turn on and at turn off. It's a simple matter of comparison to know how much fuel was dispensed at each delivery. I know arrival and departure times from Geo-fencing. What is hard to determine is what fuel grade got pumped into which station tank. I still have a manual data entry screen on the truck OBC to help out the driver when her sensor net fouls up.

We have been working with RFID for a while in warehouse environments. I can tell where every forklift is in a warehouse. If I tag all the boxes and pallets I can then sense what is being picked up and put down. The backup to RFID is barcoding and the backup to that is keying. I want to play with VR in warehousing.

I used to do software for dentists. Periodontal charting is a great candidate for VR. There are only 33 teeth with 6 pockets each. The depth is on a limited scale. The readings are taken in a specific order.


ATB

Charles Kincaid

Post #703199
Posted Thursday, April 23, 2009 8:08 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: 2 days ago @ 7:01 AM
Points: 740, Visits: 1,892
Most interfaces are doomed to irrelevance (if not failure) because they are more 'gee wiz' than practical. Touch screens (except for special apps like ATMs and kiosks) work best for simple menu selections, but often require you to hold your arm in an unnatural position. Gesture based systems may great demos, but are often too vague for realworld stuff. VR has potential in a number of areas where context and distraction is limited (would you rather work in a roomfull of people typing, or a roomful of people dictating to their computers?)

A good interface needs to be fast, unambiguous, not physically tiring, and simple.


[BTW am I the only person who HATES laptop touch pads? They slow me down enormously, and are very fatiguing. I can't imagine doing any serious work with one of those)


...

-- FORTRAN manual for Xerox Computers --
Post #703229
Posted Thursday, April 23, 2009 8:17 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, January 22, 2014 9:48 AM
Points: 202, Visits: 3,531
I am undecided when it comes to typing out full text if I can speak faster than type however I am pretty certain that an individual skilled in 9 key can easily input data faster than dictating it. I think the input environment will dictate speed which will be the ultimate deciding factor. Field workers such as sales personnel and insurance claims reps will greatly appreciate dictation where accountants probably would opt for an old fashioned keyboard.
Post #703239
Posted Thursday, April 23, 2009 8:35 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, February 6, 2014 12:59 PM
Points: 801, Visits: 1,962
jay holovacs (4/23/2009)
[BTW am I the only person who HATES laptop touch pads? They slow me down enormously, and are very fatiguing. I can't imagine doing any serious work with one of those)


You are NOT alone. Every work with a laptop that had the Joy-mouse button in the center of the keyboard? A little red stud that stuck up between the keys. Push it toward the Q row and it moves the cursor up. Push it toward the Z row and it moves the cursor down. Left is toward A and right is toward L. It's slow but much more precise than the pad.


ATB

Charles Kincaid

Post #703255
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse