SIGIA-L Mail Archives: Re: [Sigia-l] Meaning of "unified development methodologies"
Re: [Sigia-l] Meaning of "unified development methodologies"
> it is simply another way to describe the UI, in this case from the system's
> point of view,
Bingo. This begs the question: should IAs be in the business of
defining/designing "the system"? 
*When* they are required to, I'd put them in the developer/programmer
category. (Since I've been doing both sides for two decades I think I know
the demarcation line pretty well by now.) More often than not IAs are asked
to dabble in UML (and other programming related work) not necessarily
because there's *inherent* design/architectural reasons but simply because
it's cheaper to have one person do it all or, more likely, the project is
Then there are exceptions...
Nullius in Verba
 Beyond being fully aware of the technical ramifications of their own
design choices, of course.
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
This archive was generated by hypermail 2.1.6
: Thu May 12 2005 - 13:39:48 EDT