Ambient knowledge
Posted on November 4, 2008
Modern version control systems have a concept of “change-set†– an atomic group of files that were created or changed to solve a problem or implement a feature.  If we create a graph and mark the distance between files in change-set to 1, and then analyse all other change-sets and create nodes for files and edges for files in the same change-set, we can then compute the total weight of edges from node to node and perform the grouping of closely related files. To identify potentially relevant but not modified files (change request, specification documents) we can also use heuristics and father augment the graph with set of open files in the IDE and mark them as potentially relevant.
The visual representation of the resulting graph as a picture or a highlighting of related files in the IDE will probably be useful for software developers and maintainers to quickly identify potentially relevant files and subsystems.
Filed Under Uncategorized | 1 Comment
Leave a Comment
If you would like to make a comment, please fill out the form below.
Good idea!
But i think proper naming of files, with good categorisation with the use of classes and OOP, along with version control for tracking in time as well as space.. i think that is enough, but sure your idea would help the beginers.