the thing that annoys me without going through the UI process first is (and it doesn't happen all the time but it's happened to me enough on complex systems) ... is the obscured micrologic contained in the workflow of the user using said UI.
while I agree it doesn't help _design_ the entities, the amount of times I've had to hack stupid flag fields like "isThis" or "hasThat" after defining the entities because they only start coming up when looking at how the app is going to be used... it certainly has been an "input" in deciding between one or more entities, inheritance, decorating, etc. just saying, that's all... On Sun, Jan 18, 2009 at 1:45 PM, Mark Mandel <[email protected]> wrote: > > Yeah, Balsamiq is just for single page mockups. > > As for step 3, it's just plain ol' HTML.. nothing fancy. The actual > HTML and images that I will use on the production project. Once we're > gone through the design process, I know how all the elements will > look, and then I build the actual pages. > > > Re: what Sean said: >> As he says, most OO novices use the obvious - and often correct - >> approach of picking nouns for objects and verbs for behaviors but over >> time you develop a sense of when underlying abstractions make more >> sense than basic nouns - or you develop a sense for "seeing" the right >> classes in a problem. Sometimes you start out on one approach and hit >> problems and realize you need to take a different tack. I've sometimes >> had to make three passes at a design before it "felt" right. > > I find this is very similar to my feelings on OOA/D, I've never done > the 'noun' approach, but instead have a mental picture of how I think > the system should work based on use cases and/or prototyping how the > application should function. I will quite often work with UML class, > sequence and/or state diagrams to see if my approach will be a good > fit, before I actually code anything, and this allows me to refine, or > even totally rethink my original design. > > Mark > > > > > On Sat, Jan 17, 2009 at 9:10 AM, Dan O'Keefe <[email protected]> wrote: >>> 1) Mockups (Balsamiq Powered) >>> 2) Branding / Graphic Design >>> 3) Actual HTML pages that can be clicked. >>> >> >> Mark, I was looking at Balsamiq, and that is for individual page mockups >> only, correct, not for creating a prototype. >> So you are doing that in step 3 then. What do you use for that and are you >> incorporating the Balsamiq mockups into the click thru? >> Thanks >> Dan >> > >> > > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
