Thanks! Will read more carefully, but at a glance it sounds suspiciously similar to effect sketches and feature sketches from M. Feathers' book on working with

Thanks! Will read more carefully, but at a glance it sounds suspiciously similar to effect sketches and feature sketches from M. Feathers' book on working with legacy code, rather than a design methodology method per se. (is that the case?) EDIT: oh I see, it's basically the same concept as effect and feature sketches, but at the design stage rather than at the "dealing with existing code" stage. The intent is to figure upstream and downstream dependencies in your design in a structured manner. Cool.