IP Library Granted Patent US 12,210,487
Granted Patent B2
US 12,210,487 · App. 17/930,796 · Granted Jan 28, 2025

Method and system for real-time collaboration, task linking, and code design and maintenance in software development

Inventors: Vijay Madisetti (Johns Creek, GA); Arshdeep Bahga (Chandigarh, IN)
Assignee: Vijay Madisetti
G06F16/176G06F16/1815G06F16/182G06F40/169G06F40/289
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,210,487
App. No.
17/930,796
Granted
Jan 28, 2025
Kind
B2
Abstract

A real-time software development method including receiving a code file, generating a shadow code file including the code file content and a link to the code file, receiving an annotation to the shadow code file from a user, and saving the received annotation in the shadow code file as an annotation record, including annotation content, a time stamp, a creating user indication, a code line identifying at least one line of code comprised by the shadow code filed associated with the received annotation, and at least one of an action item and an assigned user. The annotation record does not change the content of the code file and can be viewed and edited by a plurality of users.

Claims (89)

1. A method for real-time collaboration in software development comprising:

receiving a code file as a code file type, the code file having content;

generating a shadow code file responsive to receiving the code file, the shadow code file being a file type other than the code file type and comprising:

the content of the code file; and

a link to the code file;

receiving an annotation to the shadow code file, defining a received annotation, the received annotation comprising annotation content; and

saving the received annotation in the shadow code file as an annotation record, the annotation record comprising:

the annotation content;

a time stamp;

an indication of an event that created the received annotation;

a code line identifying at least one line of code comprised by the shadow code filed associated with the received annotation; and

and at least one of:

an action item; and

an assigned user;

wherein the annotation record does not change the content of the code file; and

wherein the annotation record can be viewed and edited by a plurality of users.

2. The method of claim 1 further comprising:

receiving an indication of a change condition related to the code file;

determining the change to the content of the code file, defining changed content; and

appending at least one of the entire content of the code file and the changed content to the shadow code file, defining an appended code file.

3. The method of claim 2 wherein the change condition is at least one of a change to a threshold proportion of the code file, a change to a threshold number of lines of code of the code file, and creation of a new version of the code file.

4. The method of claim 3 wherein:

the change condition is creation of a new version of the code file;

the shadow code file comprises:

the content of each version of the code file; and

a link to each version of the code file.

5. The method of claim 2 wherein:

the code file comprises a plurality of code lines that have changed over time; and

the shadow code file comprises:

a first plurality of shadow code lines that correspond to each code line of the plurality of code lines of the code file as originally saved; and

a second plurality of shadow code lines comprised by the appended code file that correspond to the plurality of code lines of the code file saved subsequently to the code file as originally saved.

6. The method of claim 5 wherein:

the first plurality of shadow code lines comprises a first annotation;

the second plurality of shadow code lines comprises a second annotation; and

the second plurality of shadow code lines does not comprise the first annotation or a duplicate of the first annotation.

7. The method of claim 6 further comprising:

receiving a user input selecting the first annotation from a selecting user; and

displaying the first plurality of shadow code lines to the selecting user.

8. The method of claim 7 wherein the first annotation is associated with a first shadow code line of first plurality of shadow code lines, and wherein the first shadow code line corresponds to a code line of the plurality of code lines that has one of been modified and removed from the code file.

9. The method of claim 1 further comprising:

receiving a user input to open the code file; and

opening the shadow code file.

10. The method of claim 1 further comprising:

applying a hashing function to the shadow code file, generating a shadow code file hash value;

recording the shadow code file hash value to a smart contract; and

one of deploying the smart contract on a blockchain and recording the smart contract to a transaction sent to the blockchain.

11. A method for real-time collaboration in software development comprising:

receiving a code file as a code file type, the code file having content;

generating a shadow code file, the shadow code file being a file type other than the code file type and comprising:

the content of the code file; and

a link to the code file;

receiving an annotation to the shadow code file, defining a received annotation, the received annotation comprising annotation content;

saving the received annotation in the shadow code file as an annotation record, the annotation record comprising:

the annotation content;

a time stamp;

an indication of a creating user that created the received annotation;

a code line identifying at least one line of code comprised by the shadow code filed associated with the received annotation; and

and at least one of:

an action item; and

an assigned user;

receiving an indication of a change condition related to the code file;

determining if there has been a change to the content of the code file, defining changed content; and

upon determining there has been a change to the content of the code file, appending at least one of the entire content of the code file and the changed content to the shadow code file, defining an appended code file.

12. The method of claim 11 wherein:

the code file comprises a plurality of code lines that have changed over time; and

the shadow code file comprises:

a first plurality of shadow code lines that correspond to each code line of the plurality of code lines of the code file as originally saved; and

a second plurality of shadow code lines comprised by the appended code file that correspond to the plurality of code lines of the code file saved subsequently to the code file as originally saved.

13. The method of claim 12 wherein:

the first plurality of shadow code lines comprises a first annotation;

the second plurality of shadow code lines comprises a second annotation; and

the second plurality of shadow code lines does not comprise the first annotation or a duplicate of the first annotation.

14. The method of claim 13 further comprising:

receiving a user input selecting the first annotation from a selecting user; and

displaying the first plurality of shadow code lines to the selecting user.

15. The method of claim 14 wherein the first annotation is associated with a first shadow code line of first plurality of shadow code lines, and wherein the first shadow code line corresponds to a code line of the plurality of code lines that has one of been modified and removed from the code file.

16. The method of claim 11 further comprising:

receiving a user input to open the code file; and

opening the shadow code file.

17. The method of claim 11 further comprising:

applying a hashing function to the shadow code file, generating a shadow code file hash value;

recording the shadow code file hash value to a smart contract; and

one of deploying the smart contract on a blockchain and recording the smart contract to a transaction sent to the blockchain.

18. The method of claim 11 wherein the change condition is at least one of a change to a threshold proportion of the code file, a change to a threshold number of lines of code of the code file, and creation of a new version of the code file.

19. The method of claim 18 wherein:

the change condition is creation of a new version of the code file;

the shadow code file comprises:

the content of each version of the code file; and

a link to each version of the code file.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2022
From: BAHGA, ARSHDEEP
To: MADISETTI, VIJAY
Reel/Frame 061192/0700 →
Continuity (12)
Continuation In Part 17645832 · Dec 23, 2021
Continuation In Part 16948255 · Sep 10, 2020
Continuation 16948254 · Sep 10, 2020
Provisional Application 63393991 · Aug 1, 2022
Provisional Application 62899172 · Sep 12, 2019
Provisional Application 62901881 · Sep 18, 2019
Provisional Application 62969693 · Feb 4, 2020
Provisional Application 62989773 · Mar 15, 2020
Provisional Application 62993733 · Mar 24, 2020
Provisional Application 62994306 · Mar 25, 2020
Provisional Application 63023292 · May 12, 2020
Related Publication 20230177015A1 · Jun 8, 2023
References Cited (9)
US 20030110296A1 · Kirsch · 2003 [cited by examiner]
US 20030145312A1 · Bates · 2003 [cited by examiner]
US 20090265641A1 · Gibson et al. · 2009 [cited by applicant]
US 20110153362A1 · Valin et al. · 2011 [cited by applicant]
US 20130054636A1 · Tang · 2013 [cited by examiner]
US 20140059051A1 · Graves, Jr. · 2014 [cited by examiner]
US 20190114166A1 · Lakshmanan · 2019 [cited by examiner]
US 20200356365A1 · Pezaris · 2020 [cited by examiner]
Non-Final Office Action mailed on Jun. 17, 2024 in pending, related U.S. Appl. No. 17/645,832. [cited by applicant]
Cited By (1)
US 12,675,388