[Sigia-l] IAs vs BAs

[Ray Sharma]

The BA's should not be designing the application but identifying problems
and approaches the business need fixed (similarly to usability testing)
-it's up to the IA, designer, development to design the applications.

The issue is the IA needs to have input into these requirements so should be
somebody the BA includes in defining these requirments.

I know what you are saying though, often the line gets crossed and can both
be frustrating and detrimental to the project.

Ray

-----Original Message-----
From: sigia-l-bounces at asis.org [mailto:sigia-l-bounces at asis.org] On Behalf
Of Ziya Oz
Sent: 19 June 2007 10:34
To: SIGIA-L
Subject: Re: [Sigia-l] IAs vs BAs

Ray Sharma:

>  BA's fill the gap of gathering business requirements.

Which brings up the particularly vexing question of how a BA knows what the
biz reqs are for an application that presumably hasn't been 'designed' yet.
If a BA owns the reqs, he pretty much frames the problem/solution space and
(thus what follows downstream) the design. Which is often a recipe for
disaster, but I digress.

----
Ziya

The constraint is the design.



------------
IA Summit 2008: "Experiencing Information" 
April 10-14, 2008, Miami, Florida

-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable Archive at http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l at asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.9.0/853 - Release Date: 18/06/2007
15:02
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.9.0/853 - Release Date: 18/06/2007
15:02