Browse Prior Art Database

Method and system for change notification based on dependency analysis

IP.com Disclosure Number: IPCOM000246294D
Publication Date: 2016-May-25
Document File: 4 page(s) / 84K

Publishing Venue

The IP.com Prior Art Database

Abstract

This disclosure introduces the method and system for change notification based on dependency analysis, which makes that stakeholders who are impacted by code change can be identfified & receive notification in time.

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

Page 01 of 4

Method and system for change notification based on dependency analysis

In current software development cycle, development team are delivering product by continuously updating code, to reflect with the latest collected feedback from customers.

If any code change happened, the development team expects the code change can be communicated to related contacts such as developers whose code has dependency with the changed part or corresponding or interested parties in effective way.

The current development team often feel crazy that functions is broken due to the surprise from 3rd party dependency. They're not aware of the change from depended components/products until very late of development phase. This may cause project delay and decrease customer satisfactory.

This disclosure introduces the method and system for change notification based on dependency analysis. The disclosure implements the bi-way relationship settlement of interesting parties within & across projects, improve the code change notification mechanism, provide the notification resolution with proper scope and granularity. And resolves the problem & pains which the existed products/publication/patents haven't resolved:

Our invention will deliver the change notification based on dependency analysis to the identified interested parties within& across project(s). Below Diagram 1 shows the overall architecture.

1



Page 02 of 4

Diagram 1: Architecture Diagram

2



Page 03 of 4

Within one code project: (see Diagram 2 below)

1. Analyze functi...