Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#44 dependency graph: logical package view

open
nobody
None
5
2004-12-10
2004-12-10
Aksel Schmidt
No

Hi

our software is parted into logical components, such as
i.e. 'message management', which covers a lot of
packages, all prefixable with
com.terma.xxx.messagemanagement,
com.terma.xxx.hmi.messagemanagement,
dk.terma.xxx.messagemanagement and so on.

This is also our release/compile level granularity. (i.e. we
release different components and they should very much
fit together)

It would be most valuable to show the dependency
graph between these 'logical packages' or 'components'

example:
one could identify a 'component' by a lot of prefixes (like
the above)
in 'component mode' the graph would then display
the 'component' dependencies and we would
immediately know what the impact would be to throw a
complete component away and reimplement it in another
namespace (package) or just the potential of releasing
this component (if assuming the developer has changed
all signatures in his component :)

this would also provide another benefit:
in case of using facade patterns, one could easily
define 'implementation components' and then check that
no 'implementation components' would depend on
eachother, but solely on the interfaces each component
define.

thanks!

/aksel

Discussion