I'm interested how do you guys capture the more complex business rules within the prototype phase? I think Hal said that he only prototypes the front-end pages, not back-end. And Steve (?) said he also creates the back-end pages that say something like "I add blah-blah-blah to the database, if all's OK I go HERE, if not I go HERE".
Now how do you capture something that clients says about that back-end process? Like if the insertion process is made of multiple queries and if one fails all should be rolled back etc. Or if the client describes how the logic should work depending on different form selections etc. Do you just capture it in DevNotes attached to those back-end pages? Or do you create more elaborate docs that use UML or whatever to nail down the exact logic? .erki ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
