our software is parted into logical components, such as
i.e. 'message management', which covers a lot of
packages, all prefixable with
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
It would be most valuable to show the dependency
graph between these 'logical packages' or 'components'
one could identify a 'component' by a lot of prefixes (like
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
Log in to post a comment.