Browse Prior Art Database

Dynamic notification to simplify identification of an issue and recommend a solution

IP.com Disclosure Number: IPCOM000235803D
Publication Date: 2014-Mar-25
Document File: 2 page(s) / 26K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method for dynamic notification of an issue and a solution is disclosed.

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

Page 01 of 2

Dynamic notification to simplify identification of an issue and recommend a solution

Disclosed is a method for dynamic notification of an issue and a solution.

Often, when an issue is identified, it may be difficult to identify and analyze the issue without having to reach out to various personnel in order to identify a root cause of the issue and provide detailed information to resolvers.

The following is an example scenario:

User's of a product are reporting problems to a forum or technical support.

Tech support has to reach out to development team for assistance
Development team has to run debug methods, read through user issue documentation

just to identify which classes/methods are contributing to issue.

Existing Solutions: Monitors of the forum or technical support engineers manually determine the root cause of the problem by searching technical notes based on information provided by user and either provide a solution or create a defect if no solution exists.

Drawbacks: Time consuming for support engineer or monitor interacting with user and user information to determine the cause of the issue and must be repeated by development team in order to identify which classes/methods are consumed by the root cause of the issue.

The disclosed method identifies an issue and recommends a solution based on various unstructured data and information sources.

The following is an example embodiment:

Information is acquired regarding a product Feature during the development phase


A.

of a component.

During an Agile development process, a "Story" is created that describes a


1.

specific product feature/component.

The system identifies entities and interrelates the information based on


2.

unstructured data associated with Story, such as description of feature, image tags, links to other sources
System identifies source code created/updated pertaining specifically to the


3.

Feature when checked into source repository

System identifies entities based on defects created during test scenarios and also links them to the source code.

System links classes/methods/data sources to the Feature by identifying each class as an entity and the feature as its Annotator.

System creates a knowledge network of entities that can correlate multiple Features (ex: future features that update existing classes)

System stores entities and network

4.

Feature is released to users/beta, etc.


B.

Users report issues regarding released Feature.


C.

System identifies issue and conducts analysis on available sources...