RE: [CFCDEV] Application design ideas

[Hal Helms]

Stephen,   Here’s how I approach things. After I have a decent idea of what the system needs to do (the features of the system in your list), I begin creating the user interface. Designing the UI first is the best way I have found to fully capture all the nuances of the system. Because there is (almost) no code and no database involved, I remain very flexible as I iterate over many versions with the client. My goal is to capture all of the requirements within the context of a very usable system. If you’ve not done “UI First”, I can’t recommend it highly enough.   Once this is done, I’ll create the UML and, finally, the persistence/DB layer.   HTH, Hal   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Adams Sent: Wednesday, November 08, 2006 6:23 AM To: cfcdev Subject: [CFCDEV] Application design ideas   Hi, I'm thinking about how I go about designing an application from scratch. I've got a wireframe diagram of how the system should look, all the pages and what they will contain, but I trying to think what to do next. Do I: Create the database Create UML diagram List the features of the system I'm building this system with a Flex front end so its got to be very OO orientated, but where to start. Does anyone have any ideas, thoughts, what do other do? Stephen 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 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