On Oct 21, 2007, at 5:50 AM, Bill Fernandez wrote: >> ... (for example, does the system use a session or a cookie to >> remember a user preference? which database does the data come >> from?)... > > BF: To me, these do not belong in a a functional spec. A > functional spec would say "we have to let users set [these] > preferences..." and "there must be a way to store and retrieve > [this] data...". *how* > the preferences and data are stored and retrieved is up to the > engineers to design.
Perhaps this is a difference in either experience or opinion (or both), but the functional spec is the part that elaborates more on the backend technology. So, this is exactly where I would see this type of information fitting in. Cheers! Todd Zaki Warfel President, Design Researcher Messagefirst | Designing Information. Beautifully. ---------------------------------- Contact Info Voice: (215) 825-7423 Email: [EMAIL PROTECTED] AIM: [EMAIL PROTECTED] Blog: http://toddwarfel.com ---------------------------------- In theory, theory and practice are the same. In practice, they are not. ________________________________________________________________ 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
