Good RUP Resources when it comes to UI Documentation, etc.?

8 Feb 2010 - 1:53pm
4 years ago
3 replies
1815 reads
aronoff
2010

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? It's
going to have system information and business information. At first
glance, I'm thinking actors, preconditions, flows, the actual
screens, and then on the business side, business rules. Anything
else?

Also, do you guys know of any good RUP resources or documentation
help with UI and UXD?

Thanks!
~Josh

Comments

8 Feb 2010 - 4:49pm
jrrogan
2005

Usually you don't want to repeat the business requirements in the UI Specs,
it's often better just to refer to the individual requirements/ requirement
sets/ use cases/ features, (whatever your bus documentation method is).

As well you probably don't want to mix up Functional Spec/Architecture in
the UI Specs, (I've found being completely agnositic to implementation,
usually is the way to go, especially for the bigger projects).

Note State, Flow & Transition should be detailed out in some form via UI
Specs, and this can reference both requirements & architecture, (note this
does not mean repeating requirements or architecture).

Does this make sense?

PS I've never seen anything really useful from official "RUP" documentation,
although some sequence/activity diagrams can do double duty for UI and
logic. If you find anything definitely send it my way,

Rich

On Mon, Feb 8, 2010 at 5:53 AM, Josh Aronoff <josh.aronoff at highmark.com>wrote:

> 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? It's
> going to have system information and business information. At first
> glance, I'm thinking actors, preconditions, flows, the actual
> screens, and then on the business side, business rules. Anything
> else?
>
> Also, do you guys know of any good RUP resources or documentation
> help with UI and UXD?
>
> Thanks!
> ~Josh
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> 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

8 Feb 2010 - 6:40pm
Aaron Wester
2010

Think of your UI Specs as your design contract. It would hold your
style guide and UI parameters/attributes that would be used by
development during implementation - including specific hex values,
specific pixel counts on element spacing and alignment, etc...
Include your UI screenshots, but add a layer on top in PS with notes
that devs should be aware of (e.g., if a header navbar has hover
state, or if background gradient should be seamless transition rather
than banded, etc...)

AaronW.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=49138

15 Feb 2010 - 3:54pm
aronoff
2010

Hi everyone. Great advice... thank you! The more I think about these
docs, the more I realize that they need to stand on there own outside
of the use cases.

I have included the business rules, mainly to hold the business
stakeholders feet to the fire, and show them what it is that they are
getting. I originally had system requirements in there as well.

When finished, I may write a little blog entry about the whole
process, with the finished document.

Thank you all for your help.
~Josh

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=49138

Syndicate content Get the feed