It's common to have the need to show that an evolved version of a component has a different kind of dependencies than the original version. Classic example from the original book is co-evolution of practices and activities, for example this:
component High MTTR [0.15, 0.47]
component Application Architecture [0.63, 0.60] label [-3, -39]
pipeline Application Architecture
{
component Capacity Planning [0.78] label [-14, 28]
component Fault-tolerance [0.52] label [-30, 25]
}
evolve High MTTR->Low MTTR 0.78
Capacity Planning->High MTTR
Fault-tolerance->Low MTTR
size [800,400]
Unfortunately the diagram does not show the Fault-tolerance->Low MTTR line. It appears that evolved state of a component, even if renamed, is not a component itself. Would be great to be able link to and from such components.
It's common to have the need to show that an evolved version of a component has a different kind of dependencies than the original version. Classic example from the original book is co-evolution of practices and activities, for example this:
Unfortunately the diagram does not show the
Fault-tolerance->Low MTTRline. It appears that evolved state of a component, even if renamed, is not a component itself. Would be great to be able link to and from such components.