> One thing to know about these system analysis&design methodologies... It's crazy think about now, but the methodology strongly influences the design. Late 9

> One thing to know about these system analysis&design methodologies... It's crazy think about now, but the methodology strongly influences the design. Late 90s, I favored the Fusion Methodology for design. There was a researcher in the UK (Tony something?) that showed using the UML process led to overuse of Observable (Listener), which quickly becomes intractable. Tony (?) then reimplemented the same problems with Fusion, then diffing the resulting implementations. The notion is almost lost in the sands of time. I'm pretty sure this is the same Fusion. I couldn't quickly refind Tony's (?) original work. http://wiki.c2.com/?FusionMethodology http://wiki.c2.com/?FusionMethodology The diagrams and other artifacts were largely the same. > ... only a fraction of the benefit Emphatic agreement. Alas, I've never worked at orgs that would or could keep the modeling and the implementation in sync. Perhaps it's more feasible now. (I haven't looked for a long time.)