[Sigia-l] Meaning of "unified development methodologies"

[Lisa Fitzgerald]

I work with TAs who do the use case diagrams and context diagrams that
capture *system* requirements.  An IA would only be doing that if, in
reality, they were doing the job of both IA and TA. 

Re front-end I do activity diagrams and sequence diagrams and then attach
those to wireframes/storyboards of the user interface. In my experience, TAs
and IAs work _together_ in the process -- it makes for interesting solutions
that neither would have conceived of in isolation.


Lisa Fitzgerald | Information Architect
henderson bas
lfitzgerald at theniceagency.com
 
416.977.6660  x227
TheNiceAgency.com
 
Digital Agency of the Year
 

-----Original Message-----
From: Johnson, Bryce [mailto:BryceJ at navantis.com] 
Sent: May 12, 2005 10:01 AM
To: SIGIA-L
Subject: RE: [Sigia-l] Meaning of "unified development methodologies"

Apart from when somebody is a developer disguised as an IA, does anyone
actually use UML in their IA work?

I'm not asking a rhetorical question here - just curious.

Jonathan
====================================================
 
I'd like to more then I do right now but I work in an software development
environment so lots of people use it here.
I think it is very important for an IA to understand how to read UML to
interact with software architects. I also think there is a real benefit to
having a diagram notation with a strict syntax to ensure that the
information is clear.

This guy uses UML in his IA
http://www.techquila.com/tmsinia_4.html
 
Bryce
------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

IA 06 Summit.  Mark your calendar.  March 23-27, Vancouver, BC


________________________________________
Sigia-l mailing list -- post to: Sigia-l at asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l