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

Method and System to Suggest Changes to Source Code Based on Changes Performed in a Different Stream to Prevent/Correct Introducing Defects

IP.com Disclosure Number: IPCOM000247040D
Publication Date: 2016-Jul-29
Document File: 4 page(s) / 70K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to automatically determine when a problem is present not only in the directly associated software version, but also in different or previous versions. The method provides a unique way to create specific actions (i.e., work items) for developers to fix the problem in other versions.

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

Page 01 of 4

Method and System to Suggest Changes to Source Code Based on Changes Performed in a Different Stream to

Method and System to Suggest Changes to Source Code Based on Changes Performed in a Different Stream to

Prevent

Prevent/

//Correct Introducing Defects Correct Introducing Defects

Software systems can have many different concurrent versions. While the latest major version is available, fixpacks for previous versions, which contain some common code with the latest one, can also be available. To deal with this, software development organizations have complicated building systems that use streams or tagging to build different versions.

Software support groups receive customer calls to notify the company of a problem in the particular version the client is using . It is not common that a client has the chance or time to do testing on other versions to identify if the problem happens in others ; however, this is something that the development/support teams must do according to support guidelines.

Commonly, if a problem is reported in version x, the fix is not only included in version x but also in versions x+n, and the organization may also decide to provide fixes for versions x-n depending on the severity of the problem.

While a development/support team may have clear rules for which versions to fix, identifying whether the problem is actually present in other versions is a difficult task. A developer may run some testing to define if the problem is in other versions or may do a code comparison to identify if the code may be affected . However, both of these methods are dependent upon the developer's abilities and time available for executing these tasks; therefore, sometimes the problem is not detected and the bug is present in some versions, which affects clients and wastes time and money.

The novel contribution is a method to automatically determine when a problem is present not only in the directly associated software version, but also in different or previous versions. The method provides a unique way to create specific actions (i.e., work items) for developers to fix the problem in other versions.

The proposed system analyzes a source code change in a particular release stream to determine if that specific code is present in other streams and identify the related dependencies in order to suggest that the developer apply the changes to other streams . The system also checks the project schedule to create work items and send alerts to the developer to perform the delivery on time for the release.

The two main triggers for the analysis to be performed are:


Preventive - when new code in development


Corrective - when a defect is created and the developer determines that the defect may be present in other releases , and

1


Page 02 of 4

then requests that the system start the analysis

The implementation steps are:


1. A user finds a defect in a particular release

2. Developer debugs the code for the version in which defect was...