Harkins Audit Software Header
  home     products     services     support     company    

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Case Studies

Real-Time Program Audit from Harkin's Audit Software has helped people achieve great results. Here are three case studies showing different ways that our customers have used RTPA with great success in their own words. If you want to see more, click here to read testimonials regarding our products.

 Using RTPA To Enhance Software
 Fishman & Tobin, Inc.
Title: Harry Cicacio, Vice President Operations Key Benefits:
• Respond to your customers faster
• Reduce your IT backlog
Results:

The Situation: A programmer is given a task to add a new feature to the company's software environment.

  • Most companies have large backlogs of IT enhancements, leading to frustrated and unsatisfied customers (both internal and external).
  • IT departmens may be unable to make vendor-supplied software upgrades because of the difficulty of reintegrating prior enhancements.

The Problem: The enhancement process is often slow and tedious because the programmer has to learn and fully understand unfamiliar code before making the enhancement.

  • A typical company has 6 to 8 million lines of source code in production.
  • 80% of that source code is purchased from outside vendors.
  • The remaining 20% has been developed over many years by many programmers.
  • An individual programmer may have written less than 1% of a company's source code.

The Opportunity: Using RTPA, a programmer can dramatically reduce the time required to learn unfamiliar software, giving the programmer quick mastery over the code and saving time, money and energy.

Audit Strategy Benefit
Audit Labels, File I/O, External References, Branches and Conditional Operations to get an immediate overview of the actual flow of the unfamiliar program.
  • No need to step through source listings.
  • Shows actual flow - no guessing about conditions, branches, etc.
Audit individual variables to identify where key variables got changed.
  • No tedious breakpoints and stepping
  • Limit unintended consequences of changing code
Audit arithmetic operations to understand complex calculations
  • No guessing how a program calculates its results
  • Greater confidence in verifying changes
In their own words:
As for the RTPA Package, since its installation the IT Staff has been able to produce much quicker results with respect to enhancing our new Warehouse Management System. Prior to RTPA, our staff had to spend many days trying to understand how some of these extremely complex programs worked. In today's highly competitive marketplace along with the demands for Retailer Supply Chain Compliance, RTPA has provided Fishman and Tobin with a quick response IT solution. The learning curve has been significantly reduced and enhancements are made in hours rather than days.
In my opinion, dollar for dollar, RTPA is one of the best IT tools of the millennium!

  back to top

 Using RTPA to Find Bugs
 Jerry R. Hollo
Title: Senior Programmer/Analyst Key Benefits:
• Complete projects faster
• Fix system-critical problems faster
Results:

The Situation: A production system has an intermittent bug that results in a lost order or a system outage. A programmer must find and fix it quickly.

  • System downtime can cost thousands of dollars each hour
  • Mistakes can cause customer charge-backs or penalties
  • A single occurrence of a bug may cost as much as a programmer's annual salary

The Problem: The programmer may take hours or days tracking down the bug, and even then may not be able to find it.

  • Many failures are intermittent and are not quickly replicated in a test environment.
  • Repeated reviews of the source code's logic may not reveal where the bug occurs.
  • The bug may occur from a complex interaction between in-house programs and vendor-supplied software.

The Opportunity: Using RTPA, a programmer can dramatically increase the speed and likelihood of finding a bug, resulting in fewer failures and shorter system outages.

Audit Strategy Benefit
Engage the audit on a test system and allow it to run until the bug occurs.
  • Impractical to do on a stepper debugger.
  • Operates unattended - get other work done while waiting.
  • Review the audit in real time.
  • Easy to follow program execution from ABEND back to initiation.
Audit a unique variable (such as a customer number) to search the audit file.
  • Get an immediate answer to a long-standing problem.
  • Skip over the normal cases.
Audit the time of execution along with the source statements.
  • Match up the audit result with the time of the failure.
In their own words:
I have been programming for over 22 years on every IBM midrange system to date. Often finding a program bug can be very frustrating. Debug was a help but still requires much interaction with adding breakpoints and evaluating variable data. Recently, I had a couple of very difficult bugs to find in some very complex programs. Working in your Real Time Program Audit (RTPA) I found the compile and execute method of testing my programs to be so simple (remember KISS?) that by scanning through the resulting audit I found and fixed the bugs in a very short period of time, whereas, without RTPA I could have wasted hours if not days of time.

  back to top

 Using RTPA to Verify Development
 Accucheck
Title: Patrick Weaver Senior Programmer Key Benefits:
• Complete projects in less time
• Ensure high-quality results
Results:

The Situation: A programmer needs to develop a new piece of software to perform complex tasks.

The Problem: IT departments want to complete more projects in the same amount of time while maintaining or improving reliability and quality.

  • New software development may require novel solutions. Novel solutions require validation.
  • New software can behave erratically, requiring the programmer to track down exactly what's happening.

The Opportunity: Using RTPA, a programmer can dramatically reduce the time it takes to develop and validate new software, resulting in higher productivity and higher quality.

Audit Strategy Benefit
Audit conditional statements to validate reliable operation in "fence conditions"
  • Know that the code operates exactly as expected.
  • Reduce the need for "test functions"
Audit all source statements to find out where execution terminates unexpectedly
  • Much faster than stepper debuggers, no need to guess where to put the breakpoint.
  • Follow the failure back to the initiation.
  • No more guesses, fewer recompiles.
Audit all I/O.
  • Ensure that the data sets are being read accurately.
  • Ensure that you're using the right data sets.
In their own words:
I am working on one-time conversion programs to bring in and convert new business into our collection system. The conversion programs are tough because I'm often dealing with data I'm not familiar with and writing programs that only have a one time use. After converting about 1.2 million records in a test mode, we had about nine different type of problems with the converted data. I then took an example of each of the nine problems and put them in a library to isolate only problems records, ran all of the conversion programs through RTPA, and converted all of the problem records. The result was an audit of all of the bugs in our conversion programs. I then when down the list of problems solving each one systematically. Once I got to the end of the list, I was finished. It would have taken numerous debug sessions with many conditioned break-points at precisely the correct place in order to accomplish the same thing without RTPA.That analysis alone (to position the break-points) would have taken longer than the entire debug process with your product, and that's assuming I did not miss any of the needed lem records. The result was an audit of all of the bugs in our conversion programs. I then when down the list of problems solving each one systematically. Once I got to the end of the list, I was finished. It would have taken numerous debug sessions with many conditioned break-points at precisely the correct place in order to accomplish the same thing without RTPA.That analysis alone (to position the break-points) would have taken longer than the entire debug process with your product, and that's assuming I did not miss any of the needed break-points.

  back to top

home | products | support | company | news | sitemap | contact
Harkins & Associates, Inc.  ·  816 Daisy Lane  ·  West Chester, PA 19382  ·  610.431.1755
  Copyright ©2000 - 2009 Harkins & Associates, Inc. All Rights Reserved                                                   Terms of Use | Privacy Policy