Conference Buddies

Writing Good Use Case – SD West 2009

March 11, 2009

Speaker: Terry Quatrani (UML Evangelist, IBM)

Conference Notes:

Keep a use case high level and don’t have it bogged down with features and details. The main function of a use case is to clearly communicate:

• the main justification for the software
• who will be using it
• the end goal for the actor/ user
• a  happy day scenario
• other main listed alternatives
• high risk identifiers

Use case should be in plan language giving the reader enough information to understand the justification and main purpose of the software without being lost in the details.

More information should follow in a technical UI document that flushes out the detail requirements. A good use case is high level and provides enough information.  Do not list out all details, alternative scenarios, risk factors, or “what if statements” – just focus on the major key areas.

Personas, Profiles, Actors, & Roles: Modeling Users To Target Successful Product Design – SD West 2009

March 11, 2009

Speaker: Jeff Patton (Architect, Interaction Designers, AgileProductDesign)

Conference Notes:
Building personas, profiles, actors & roles are key to understanding:

1. Who will be using the software
2. What is the profile of the target user – skills, user experience, levels of interaction
3. What is the function of the software
4. What is the responsibility of the user in relation to the software

This often starts by brain storming. More data is often available from market data, marketing departments, and UI studies.

Use of images of what your target personas is often helpful for people to connect with the attributes.  Keep attributes short and easy to remember.