Browse Prior Art Database

System and Method of Smart Code Update

IP.com Disclosure Number: IPCOM000238203D
Publication Date: 2014-Aug-08
Document File: 4 page(s) / 82K

Publishing Venue

The IP.com Prior Art Database

Abstract

This disclosure is to reduce human effort that when a development project is based on another project, the developerA need to revise the code when the base project has added some code enhancement. This disclosure provides a solution that when base project developerB wants to add some code enhancement to base project functionA, he will first provides code interface of the prototype to developerA. In this case, developerA can develop 2 versions of code: Version 1 without base project enhancement, version 2 with the new interface provided by developerB. After developerB deliver the code enhancement, the system will switch development project code to version 2 automatically. In addtion, for other programmers who have the same problem to replace the old code, the system can scan the code repository in current code stream. If the system find a Code Version1 match, then it will automatically replace it as Code Version2.

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

Page 01 of 4

System and Method of Smart Code Update

In current development style, there are often such cases: programmer A is programming and find he needs some enhancement like a new base function so programmer A can directly call the function. He will raise the enhancement requirement, meanwhile he might have some workaround as a temporary solution.

It usually takes some time to implement the requirement, as the implementer could be someone else, he may have other tasks of higher priority. The implementer could even be someone else in another team, so several communication cycles is mandatory. Requirement evaluation, decision making, test cycle after implementation, deliver would go for a long time. During this period, there are more other programmers come to find they need same enhancement in their code, as the enhancement is not ready, they will use A's temporary workaround, so this could lead to a situation that the temporary workaround is distributed in many places, in lots of source code files.

After the requirement is ready, people need to find all those distributed workaround and manually modify them to call the new function. This is time consuming. It's not efficient. Especially when there are several programmers having the same problem. All of them need to modify their code based on the new method/class.

The purpose of our invention is to reduce human effort to do the code replacement and add more automation. Before implementer write the enhancement, he will provide a prototype. Only one programmer need to be aware of this future change and define a replacement model telling in future how to replace the workaround with the new enhanceme...