Browse Prior Art Database

Symptom diagnosis of defects in S/W applications deployed in production environment, leveraging heatmap of relationship between Object uids and Functions. Disclosure Number: IPCOM000199819D
Publication Date: 2010-Sep-17
Document File: 4 page(s) / 281K

Publishing Venue

The Prior Art Database


Disclosed is a process to map symptomatic defects of a Widows™ based application to causal entities within the source code of that application. The process will map Object ids from an application which has figured in defects (symptomatic) to functions in the stack trace which actually cased this defect (during Functional Verification Testing (FVT)). This matrix will result in one or more heat maps which a support engineer can interpret to diagnose a reported defect from a production environment. The solution will help a support (Level 2,3) engineer to zero in on the cause of a problem in a software application (in production), using historical data of symptomatic data points (object uids) to causality (functions in the stack trace which causes the problem). This historical data has been captured during the FVT cycle of the software application. The existing solutions are generally homegrown cheat sheets which support organizations have to help them zero in on problem tickets raised. The shortcoming of these approaches are that they never really are a connect between data collected from FVT testing which is handed down to support along with the code (Final production code of the particular version), for support. There is a treasure of information related to every defect which is reported and fixed during the FVT cycle, which can be used by the L2,L3 teams. If the set of tools, straddling Change and release management and Functional testing / FVT testing mandate for this data to be captured and render them in a format which support teams can interpret to faster zero in on the causality of issues, it will help support (especially support engineers who are new on this application).

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 4

Symptom diagnosis of defects in S/W applications deployed in production environment , leveraging heatmap of relationship between Object uids and Functions .

The novelty we claim is the capturing the historical relationship between the symptom of a defect to its cause and rendering it in a format consumable.

When a defect is reported, it is generally discovered based on a test case, a functional testing tool, or a tester can easily report the last few GUI objects (or functionality) which were engaged before the failure occurred. Also the stack trace of this defect will show path where this defect was injected and rendered. Both these data points can be pared to get specific object UID to failure function mapping, which will be captured in a spread sheet. This spread sheet will be later analysed to build a heat map which can be an artifact along with the codebase which is provided to the support team to support this product after is is GAed.


This could result in
a) Localizaton representation of defect inducing functions
b) Easier symptom to cause mapping for Support engineers.
c) Easier ramping up of new support engineers on this S/W application

Fundamental concepts of the invention


a) A functional testing tool
b) Object uids for Windows™ Graphical User Interface elements (which is available in the functional testing tool)

c) Function names from stack traces
d) A process to build a heat map of function names to object uids in the application s/w.

e) Configuration management tool


During application development - FVT cycle
Figure 1 depicts the work flow during the application development
a) A test engineer has to capture the stack of object uids which were involved in the failure of a particular test

b) This should be a part of the defect raised in the change management system.
c) The developer who fixes this defect has to capture the stack trace and has to associate the functions which were involved at the core of the defect.

d) These two data points are captured in the CRM system
e) A to...