Not really. I believe it is intended to mean "data driven programming" as Jeremy mentioned earlier. To me, data driven programming means "use lotsa lookup tables, the contents of which are user tweakable". As simple as it sounds, it can be an effective technique to let you quickly adapt a system as requirements "evolve" - without code changes.
Having found this hammer early in my programming career, I find a great many nails. Early days in any new design are spent setting up a "lookup table" table, along with utility routines for reporting, validation, UI picking values (one or several), etc. It may be a use case, but I don't think this is quite the same thing as the subject of this thread which, as Uri says, is a general approach to analysis. At 09:00 AM 4/4/2006 -0400, [EMAIL PROTECTED] wrote: >hi > >( 06.04.04 08:46 -0400 ) Tolkin, Steve: > > The difference is that I am trying to find a quote that focuses on the > > benefits of using data in a special way, as "control data", to determine > > the specific execution path taken by the code. > >um, isn't this the scientific method? > >-- >\js oblique strategy: how would you have done it? > >_______________________________________________ >Boston-pm mailing list >[email protected] >http://mail.pm.org/mailman/listinfo/boston-pm _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
