On 22 Oct 2007, at 21:54, Christopher Fahey wrote: >> A few thoughts - first I often call "What a product should do" >> Business requirements - not functional requirements. > > Yes! > > My ideal process: > > 1) Business Requirements -- what the business wants to do > 2) UI Spec - what the user experiences to deliver #1 successfully > 3) Functional Spec - what the machines do to deliver #2 successfully
Personally I find doing 2 & 3 at the same time to be more effective than doing all the UI work up-front. So much of (2) needs to be communicated to (3) I find it saves an enormous amount of time producing artefacts when it would be much easier to have everybody in the same room. Adrian ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
