I just started a project, where I've been doing a model very much like what Hal has recommended - interface driven.
Quote for the HTML UI to be built, which includes: 1) Mockups (Balsamiq Powered) 2) Branding / Graphic Design 3) Actual HTML pages that can be clicked. >From there I'll be going forward with writing up a quote based on the application we've iteratively worked out together. I have to say - it's been very liberating. We're still at the stage where we're fiddling with mockups, but at this point, I don't * mind * 17 rounds of tweaks, it only takes me 5 seconds with Balsamiq, and I'd rather those changes happened at this stage, than when we're building the thing. Mark On Fri, Jan 9, 2009 at 1:01 PM, Barry Beattie <[email protected]> wrote: > >> In a nutshell, goal directed design is particularly focused on the >> interface, particularly on the user of the interface. It focuses on the >> goals of the players involved in a system, and the interface/system is >> designed to fulfill those goals, prioritizing the most important. > > It's interesting to note that over the last couple of years, Hal Helms > has been increasingly preaching this mantra. > > so much so, that this process can come before coming up with the > entities. Besides, as Java guys are starting to learn, the thing > people notice is the UI and workflows, not the architecture. > > don't ppl do storyboards anymore? > > > > -- E: [email protected] W: www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
