Another factor that can degrade a tools ability to support optimization throughout development is the degree to which connectivity changes can be made without disturbing other definitions. Frequently, as the connectivity changes, other layers of information are essentially destroyed, causing additional re-engineering work that slows the turn-around time, or even prevents a response in the timeframe it is required altogether.

If turn-around time in a tool reaches the point where the turn-time exceeds the window of opportunity in which recommendations can be accepted, the tool fails to take part in the optimization process.

This design consideration was once again factored into how eXpress manages its information. Unlike any other approach, eXpress supports more than a simple layering of data. Instead, it uses a layering and abstraction approach so that, for example Test Definitions tolerate connectivity changes, so that they can automatically update in response to it. This is a leap beyond other approaches in that connectivity changes otherwise require Testing to be re-entered and re-analyzed. eXpress incorporates topological abstraction into its approach, thereby eliminating virtually all Test rework associated with connectivity changes.

Of course, approaches like this must extend throughout the tool, as they do in eXpress. Like the old addage, software tools as well, are only as good as their weakest link.