If you're enterprise application uses a browser based platform, you've generally got the two big deliverables, (of course you could have these regardless of the platform):
1. Prototype 2. Annotated Diagrams To support the above, generally I like to audit the system before jumping into design. Various applications can dictate which audit to perform such as: 1. Screenshot audit of existing system, inventoried and linked to reqs/UC's/etc 2. Form and display list audit, (per screen/zone), listing values, valid inputs, required/not required, sorts, messaging, etc. 3. Screen flow audit, simple flow of forms thru UC's There's lots of ways to approach audits, depending on how the system functions. It's amazing how many times you can refer back to these audits in design, not to mention you'll fully understand the requirements process, and application by the time you're done. On 6/5/08, Catriona Lohan-Conway <[EMAIL PROTECTED]> wrote: > > I have just started a project where I will be doing the UX for enterprise > applications and wondering if any of you have any best practices to share on > documentation of the current systems and books... > > Catríona > > __________________________ > Catríona Lohan-Conway > User Experience Architect > 917 405 5127 > [EMAIL PROTECTED] > > > > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [EMAIL PROTECTED] > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > -- Joseph Rich Rogan President UX/UI Inc. http://www.jrrogan.com ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
