Take for example, two brokerage firms that have each developed similar on-line products to allow their clients to access their accounts anytime they want to.

The two companies, Reliable Brokerage and I-Broker, are employing the latest in Internet technology:  VisualAge for Java, servlets and IBM's WebSphere Application Server.

Both Reliable and I-Broker allow their customers to log into their site and access account information.  Users are able to view a portfolio of stocks, make trades and monitor the activity of various market indicators.

Within a month after going "live" with their solution, Reliable Brokerage is realizing ever-increasing volumes of user traffic.  I-Broker is experiencing just the opposite.  They are continually losing accounts and receiving complaints stemming from poor performance of their site.

Why, if both companies are employing the same technology and offering the same types of services would Reliable enjoy success while I-Broker is struggling to retain customers? The answer to this question is UniCycle for Java – Enterprise Edition.  It is a given that both companies rushed to get their solutions to the Internet and as a result both were bound to experience errors.

In the case of I-Broker, they had to rely on the end-user to report problems.  In most cases the customers did not have the time nor the inclination to play the role of trouble shooter for I-Broker.

The flip side of this scenario was the ability of Reliable Brokerage to capture important information during the development phases and communicate that information back to the developers before the solution was put into production.

Once Diagnostic Reports were created, fixes could be produced and a quality e-business application was released.