> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sean > Corfield > > > I'd love to know how to avoid this. I'm constantly going > between "what am I > > trying to do here" (logical) to "how do I implement that" > (physical) and the > > I try to ignore the physical model for my first couple of iterations > over the logical model. That stops me getting distracted. Once I'm > convinced that my logical model reflects my use case scenarios and is > reasonably self-consistent and rich, I start mapping logical -> > physical.
OK, the lightbulb has gone on. I had assumed (wishful thinking?) that with the right OO constructs, the logical and physical models become so close that there is no strain flipping back and forth. In other words, I can use the physical implementation to prototype the logical model. Back to Software Engineering 101 for me! Jaime You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
