Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Performance Data Management Tool

IP.com Disclosure Number: IPCOM000051263D
Original Publication Date: 2005-Feb-10
Included in the Prior Art Database: 2005-Feb-10
Document File: 1 page(s) / 20K

Publishing Venue

IBM

Abstract

The Performance Data management Tool enables users to manage, analyze and compare performance test results ( e.g. response time measurements) in an efficient and effective manner using GUI selection menus .

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 62% of the total text.

Page 1 of 1

Performance Data Management Tool Overview

Performance testing of complex e-business systems involves the analysis of large volumes of performance test data input. Depending on the methods used, managing performance test data can be overwhelming and very cumbersome task. The Performance Data Management Tool is Java based application that simplifies the cumbersome task. The key components of this tool are:

Test execution results repository: enables the user to store and track the test run execution results in an organized fashion allowing for subsequent ordered groupings and results summarization and analysis.

Response time measurement analysis facility:enables the user to view response time results/measurements for a test run from different perspectives and enables the user to focus on transactions and business scenarios comprised of sets of transactions or even a specific business scenario.

Flexible output reporting facility:provides full flexibility on exporting the analyzed tables for a summary level reporting as well as a drill down to detail capability.

Application design highlights

The tool does not distinguish between projects. If there are two projects or more and the results from the test runs need to be separated, then two copies or more of the tool need to be installed, one for each project. The tool assumes each transaction name starts with the business scenario name followed by the Transaction name, the Underscore key is used to separate them. Example...