This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Agile and Other Processes and the fly likes Automated dependency graph as starting point? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Automated dependency graph as starting point?" Watch "Automated dependency graph as starting point?" New topic
Author

Automated dependency graph as starting point?

Ernest Friedman-Hill
author and iconoclast
Marshal

Joined: Jul 08, 2003
Posts: 24183
    
  34

Many tools can generate dependency graphs of classes or (sometimes) larger modules. Is there an advantage in starting your Mikado graph with an auto-generated graph like this, perhaps as an overlay or as a guide map?


[Jess in Action][AskingGoodQuestions]
Daniel Brolund
author
Greenhorn

Joined: May 21, 2013
Posts: 5
    
    5
Hi Ernest,

The purpose of the Mikado Graph is to represent the dependencies of just the things you need to change. This is usually not the same as the dependencies in the code base, although the dependencies in the code base will of course influence the order in which you need to do things.

So the answer is no, it's not a good starting point for a Mikado Graph, but it is a good source of information about your system. :-)
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Automated dependency graph as starting point?
 
Similar Threads
Refresh a folder
Scene Graphs
WA #2 ..... word association
Get vs post in servlets
cewolf XY Chart