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?
I've been tasked at helping our BAs sift through some documentation,
to work within the confines of the RUP methodology. The documents
that I'm working on are the Storyboard artifact, the UI concepts,
and the UI Document or UI Specs. document.
The first two are pretty self explanatory, but I'm struggling with
what's usually in the last one.
The way I see it is this document will be a bridge for people in
systems and people on the business side to rally around the screens
and "be on the same page", literally.
So, my question is, what usually goes in this UI document?
I am in the process of creating a document that a UI designer/information
architect would ideally extract from and record in his first few meetings
with the clients/development team. It should also serve as a document that
the team can go back to and refer in case of doubts emerging in course of
development. At the least, the document should act as a base for the UI
designer to design the information flow and user interaction.
Can anybody help me with that? Is there such a document ready? Or some such
material in place? Any kind of help is appreciated.