• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Automated dependency graph as starting point?

 
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
author
Posts: 5
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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. :-)
reply
    Bookmark Topic Watch Topic
  • New Topic