Soapbox

Behold, the UI

Wednesday/08/08 2007 | Full Story

Workgroups require more than software that achieves tasks. They also demand that the user interface sparkles; that the software directs them to get their work done in a pleasing way. This reality places a burden on developers.

During a rigorous validation and verification (V&V) review of a FileMaker system, I was struck by the number of details checked by the quality assurance staff. Great attention was focused almost exclusively on mathematical calculations and data protection.

However, the reviewers had far greater difficulty determining the validity of requirements relating to "ease-of-use" and "intuitive interface". These requirements were listed along side the logic expectations of the system.

I'm convinced that workgroup systems fail to live up to their potential due to poor user interfaces more often than for logical problems. People won't use a system if the interface intimidates them. Even when the logic of a solution works as advertised, they will find another way to solve their problems if the system lacks a meaningful experience to accomplish the given task.

The bulk of my professional career was spent in printing and publishing, an industry upon which the intangibles of good design became both an art and a science. Millions of dollars are spent every day to assure that a page design moves people to action.

Graphic designers are trained not only in digital creation, but in how people interact with a design. Advertising agencies establish focus groups to determine if the outcome of a specific ad will lead to results. Editors watch readers "eye travel" to determine if graphic elements on a page keep the reader in the story for as long as possible.

These same principles apply to good user interfaces.

Every organization has a personality. Every workgroup projects its own identity. The toolsets they employ must conform to these dynamics for real work to be accomplished. When workgroup software is incompatible to the character, disposition or expectaions of a team, it will fail...despite the fact that it delivers an accurate result for an equation or provides access to valuable data.

While these thoughts are really nothing new to experienced technology consultants, I am reminded, again, of how much rigor must be placed on the interface of a project. If a client cannot express an objective standard to measure the effectiveness of a user interface, then it is our job to state such standards.

Where are the tools to measure user interface guidelines? To this date, the best series of practical, measurable user interface rules are found in Alan Cooper's "About Face" series. I would encourage anyone with a passion for effective software to scoop up one of his books, today.

On a more immediate, practical level, the next time you pick up a brochure or magazine, keep track of where your eyes travel as you scan, then read, its content. Now, take that same approach to your user interface. Ask yourself if the user's eye moves to where you want when entering data or prompting an action. What roadblocks did the interface impose on the user when initiating an action? Ask yourself how your UI can be validated as an objective quality component to the system you've created.

Even as the V&V process completes for another of Entellic's workgroup projects, I am challenged to achieve the ultimate interface that inspires people to maximize their efforts.

Will the REAL requirement please stand up?

Sunday/01/07 2007 | Full Story

When developers reflect their understanding of a client's requirements in language that supersedes words, results are faster and more accurate. Rapid prototyping, using fourth-generation desktop tools can make it happen.

Do you remember the old television show "To Tell the Truth"? In the show, one person was selected because of an interesting vocation or experience. Then, that person and two impostors would attempt to convincingly answer celebrities questions in hopes that they would be chosen as the real person of interest.

Within every data-driven project, one of the greatest struggles is discovering its real requirements. Each person in an organization offers a different idea of the requirements. Or, more likely, people have difficulties in articulating more than just an overview of the requirements that will make or break a project.

Entellic understands this difficulty. Gathering the details takes more than just asking questions off of a checklist. In most cases, requirements are learned by onsite observation and collection of sample input and output documents. Assuring that the real requirements are captured means repeating them back in the form of a requirements document.

Yet, as fourth-generation database technologies become more robust, another way of gathering requirements is taking shape: In some cases, rapid prototyping can be effective. With tools like FileMaker® in the hands of experts, there are cases in which the data dictionaries, workflow, and basic interfaces can be fleshed out in a matter of days...in the same amount of time it would take to create a requirements document.

The inherent value of rapid prototyping is apparent:

People think visually. The ability to see the the project requirements assists them in communicating what they really want.

Developers are usually better at communicating in tables, interfaces, and processes than they are in sentences and paragraphs. Rapid prototyping allows database programmers to quickly manifest what they think a client wants. Words don't stand in the way.

A foundation is laid. If a project's intent is accurately portrayed in the prototype, some development tasks are already accomplished, ready to be built upon. When you recognize that the lifespan for many data projects is less than three years, this fraction of development time can hold costs down.

Of course, rapid prototyping is not intended to replace all pre-development documentation. And, it can be a total waste of time if the interpretation of a client's needs is completely missed in the prototype development. Even worse, it can foster laziness by developers and analysts.

Yet, even with these risks, the advent of desktop database development tools lends itself to move forward with this method of communicating requirements. Even a well-written requirements document can lead to disappointing results and rework due to human communication limitations. We believe that people really do think in pictures more than words. They know it when they see it. We believe rapid prototyping should be attempted.

What do you think? Send us an email with your experiences, biases, or ideas. Is this the way to make the real requirements stand up?

Watch for additional thoughts on rapid prototyping in future posts.

The power of bar code scanning devices

Tuesday/10/17 2006 | Full Story

Capturing data without keyboard entry limits errors and increases speed. Entellic's Nathaniel Hein mastered the programming aspects of bar code scanners, enabling Entellic clients to customize data capture for their systems.

Last year, Entellic installed a point-of-sale system for a college bookstore that incorporated Symbol™ bar code scanners. This experience with the scanners prompted us to find new ways to use the technologies beyond retail operations.

A short while ago, a government client was seeking a way to eliminate data entry into their document tracking systems. Bar code readers were the logical choice. The result: Now, as paper records are delivered to clerks, a small bar code label is immediately affixed to the margin. Every time an activity with a document takes place, such as check-in or check-out of records during various technical review processes, the bar code is scanned to record the activity: This process creates a virtual audit trail without a number of entry steps.

And, more importantly, when the final document is ready for archive as a PDF, the document is named properly during the conversion process by scanning the barcode as its title. The bar code scanner is used to make each document process less cumbersome and error-free.

This is just one inexpensive way to automate what was once a clumsy manual entry process.

That same organization is currently incorporating bar code scanning into their inventory control operations. But, this inventory is not typical. Containers of radioactive material are moved from control areas. Therefore, the error rate for these movements must be "zero."

Entellic assisted the organization by creating several bar code applications that are uploaded into several industrial-grade batch scanning units. The applications administer remote data capture operations in a tightly-controlled, linear process. Upon docking the scanner, the data is uploaded as a batch into a FileMaker™ application. This application, named MoveControl, evaluates the data for errors. Three things occur as a result of the evaluation:

The operator is released to make the sensitive container movement from one inventory control area to another.

Live data is synchronized to the primary container tracking systems, allowing administrators to have a "live" portal into container movement activity.

An "audit trail" is created to demonstrate compliance to procedures for all container movements.

call Entellic

, today.