Well, I've looked at the diagrams and thought about their implications for the confluence of technical culture and interaction design culture. Perhaps this will help ...
Of the UML diagrams http://en.wikipedia.org/wiki/Unified_Modeling_Language#Diagrams_overview ... at a detail level, the sequence diagram aligns best with what interaction designers like to talk about. You can have several actors experiencing events and notifying one another with messages. The activity diagram is basically a flow chart, which can be at a high level or a low level. The really delicate one is the use case diagram. If you can come to agreement with your UML adoption team on how to express scenarios and how those relate to use case diagrams, you'll have a good time. This is your chance to advocate for a view that is strongly context-driven, in which the systems play a supporting role and recede from playing a determining role in the interactions. You may end up writing the scenarios separately, or using the use case notation to write scenarios that come from your understanding of typical uses, or cross-checking your scenarios against use cases that were primarily written with systems in mind. It's not that the systems aren't important, but they can easily dominate the discussion. So it's the manner of interpretation of the use case diagrams that you'll probably want to pay the most attention to. Best wishes, Bruce On Mon, Feb 15, 2010 at 5:10 PM, Anne Hjortshoj <a...@annehj.com> wrote: > I've found UML to be quite helpful in requirements definition -- the > process enables workflow to be described in a way that is entirely > separate from defining the UI. > > The end result is a set of requirements that doesn't rely on UI > elements (which can be defined later, and not baked in during > requirements generation). > > -Anne > > > On Mon, Feb 15, 2010 at 8:54 AM, gail swanson > <gail_swan...@sbcglobal.net> wrote: >> My organization is moving toward UML for all of its documentation, >> from requirements through development and maintenance. The UX >> practice here is in it's infancy and I am now a team of one. While >> I'm familiar with UML, I'm skeptical that it will be appropriate >> for user flows and any other UX documentation. >> >> Has anyone worked in a UML environment? How did you integrate your >> practice into RUP or similar methodologies? >> ________________________________________________________________ >> Welcome to the Interaction Design Association (IxDA)! >> To post to this list ....... disc...@ixda.org >> Unsubscribe ................ http://www.ixda.org/unsubscribe >> List Guidelines ............ http://www.ixda.org/guidelines >> List Help .................. http://www.ixda.org/help >> > > > > -- > Anne Hjortshoj | a...@annehj.com | www.annehj.com | Skype: anne-hj | > Hjortshoj is pronounced "YORT-soy." > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... disc...@ixda.org > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
