Re: HR/Payroll Systems

[Trevor Perry <trevor@xxxxxxxxxx>]

Or, we P's could engage someone with UI experience?

I have seen too many badly configured/designed iSeries Access sessions and
badly designed websites by P's, and by P's who claim they know something
about design, or sell products that provide a UI function. P's are not
taught UI, so we really should (a) learn it, or (b) get help.

CUI certainly works best for character stuff - such as data entry. And sure,
there is some of that in our world. That issue, though, is a different
argument. We should be modernizing the APPLICATION to replace the
human-error prone and inefficient data entry function. As Mike Ryan said:
EDI, or using XML data streams, or web services. How about bar codes, RFID,
OCR? Modernization means our applications should be improving - not staying
in the last century where we had banks of data entry operators. We lost
cards and card readers - the day of the data entry operator is close to its
end.

At that point, CUI is moot.

Ultimately, CUI or GUI, it is all about the User Experience. Our
applications should be designed for the optimal experience for the user. Can
you tell me that sitting at a desk performing a data entry function prone to
carpal tunnel is a user experience desired by anyone?




On 1/11/08 1:15 PM, "Mike Cunningham" <mcunning@xxxxxxx> wrote:

> Very true. We P's should always think like U's when creating software. I guess
> the bottom line is this string is that the solution has to fit the problem. In
> some cases GUI works best (usually, but not always the infrequent user), in
> others CUI works best (usually, but not always the heads down data entry
> tasks.). Sometimes a mix is best. Windows is GUI but how many people to you
> know who do a "Start", "Run" in windows instead of the point and click you way
> through lots of icons to find the program you want to run.