Sammi,
Hal and jeff explain it better than I would.  They have podcasts that explain the entire process.  It is about 2 hours of content plus their normal pods.

http://www.helmsandpeters.com/

Teddy

On 11/8/06, Sammy Larbi <[EMAIL PROTECTED]> wrote:
Teddy Payne wrote, On 11/8/2006 8:37 AM:
> I would like to add that considerations for what phase you enter the
> project is important here.  When developing new applications for a
> client, your UI design and interaction for the client will be key to
> drive your database design.  The Flip process is a great process to
> ensure that clients know exactly what they are getting and when they
> can make changes.
Teddy,

Would you mind elaborating on the Flip process?

Thanks,

Sam

>
> If you are entering a currently existing applications and the client
> looking to revamp the current project, it may be good to understand
> why the UI is displeasing probably due to the database not allowing
> the UI to be representative of what the client wants.
>
> Teddy
>
> On 11/8/06, *Steve Gustafson* <[EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]> > wrote:
>
>     For me the application dictates whether I build from the front-end
>     or back-end.
>
>
>
>     As the complexity of the back-end increases, I am more likely to
>     begin there.  The reason for this is it is very easy to build a UI
>     that does not match the requirements of the back-end.  For a
>     simple application this is not the case, but if you are building
>     an online banking system, you better nail down the back-end before
>     you think about the UI.
>
>
>
>     That being said… for a very high percentage of applications
>     building around the UI is fine.
>
>
>
>     Gus
>
>
>
>     ------------------------------------------------------------------------
>
>     *From:* [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>     [mailto:[EMAIL PROTECTED]
>     <mailto: [EMAIL PROTECTED]>] *On Behalf Of *Brian Klaas
>     *Sent:* Wednesday, November 08, 2006 8:27 AM
>     *To:* [email protected] <mailto: [email protected]>
>     *Subject:* Re: [CFCDEV] Application design ideas
>
>
>
>     I always tell my staff that "The interface /is/ the application"
>     for the users. Building the interface first will save you
>     countless hours down the line by removing a large number (but not
>     all) of the "Oh, I thought the application would...[insert name of
>     feature here]" and "Couldn't you just change this to...[insert
>     description of new feature here]" conversations that you're likely
>     to have.
>
>     brian
>
>
>     on 11/8/06 7:14 AM, Hal Helms at [EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]> wrote:
>
>     Yes, I would, Stephen. Here's why: only users can tell us both
>     exactly what they want the system to do and, very importantly,
>     what the system should look and feel like. (I've seen many times
>     when a perfectly functional system is never used because the fit
>     between system and user is a poor match.) We would LIKE for users
>     to be able to tell us what they want, but experience shows us
>     they're much better doing this AFTER the fact (which is why so
>     many requirements come out at deployment in the guise of "You know
>     what would be nice…" comments). Doing the UI first allows all this
>     discovery to be done before the cost of code and database work is
>     paid.
>
>
>     *From:* [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>     [ mailto:[EMAIL PROTECTED]]
>     <mailto: [EMAIL PROTECTED]%5d> *On Behalf Of *Stephen Adams
>     *Sent:* Wednesday, November 08, 2006 7:07 AM
>     *To:* [email protected] <mailto:[email protected]>
>     *Subject:* Re: [CFCDEV] Application design ideas
>
>
>     Hi Hal,
>
>
>
>     Thanks for the reply, the application I'm building is a Flex
>     front-end based application, do you think it's a good idea to
>     build a demo front-end in Flex first?
>
>
>
>     On 08/11/06, *Hal Helms* < [EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>> wrote:
>
>     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]>
>     [ mailto:[EMAIL PROTECTED]]
>     <mailto: [EMAIL PROTECTED]%5d> *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 <http://www.katapultmedia.com/>
>     <http://www.katapultmedia.com/ >
>
>     An archive of the CFCDev list is available at
>     www.mail-archive.com/[email protected]
>     < http://www.mail-archive.com/[email protected]>
>     <http://www.mail-archive.com/[email protected]>
>
>
>     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 <http://www.katapultmedia.com/>
>     <http://www.katapultmedia.com/ >
>
>     An archive of the CFCDev list is available at
>     www.mail-archive.com/[email protected]
>     < http://www.mail-archive.com/[email protected]>
>     <http://www.mail-archive.com/[email protected]>
>
>
>     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 <http://www.katapultmedia.com/>
>     <http://www.katapultmedia.com > <http://www.katapultmedia.com/>
>
>     An archive of the CFCDev list is available at
>     www.mail-archive.com/[email protected]
>     <http://www.mail-archive.com/[email protected]>
>     < http://www.mail-archive.com/[email protected]>
>
>     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 <http://www.katapultmedia.com/>
>
>     An archive of the CFCDev list is available at
>     www.mail-archive.com/[email protected]
>     <http://www.mail-archive.com/[email protected]>
>
>
>
>
>     You are subscribed to cfcdev. To unsubscribe, please follow the
>     instructions at http://www.cfczone.org/listserv.cfm
>     <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 < http://www.katapultmedia.com/>
>
>     An archive of the CFCDev list is available at
>     www.mail-archive.com/[email protected]
>     <http://www.mail-archive.com/[email protected]>
>     You are subscribed to cfcdev. To unsubscribe, please follow the
>     instructions at http://www.cfczone.org/listserv.cfm
>     <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 < http://www.katapultmedia.com/>
>
>     An archive of the CFCDev list is available at
>     www.mail-archive.com/[email protected]
>     < http://www.mail-archive.com/[email protected]>
>
>
>
>
> --
> <cf_payne />
> Adobe Certified ColdFusion MX 7 Developer
>
> Blog: http://cfpayne.wordpress.com/
> Atlanta CFUG: http://www.acfug.org <http://www.acfug.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/[email protected]



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/[email protected]




--
<cf_payne />
Adobe Certified ColdFusion MX 7 Developer

Blog: http://cfpayne.wordpress.com/
Atlanta CFUG: http://www.acfug.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/[email protected]

Reply via email to