We call them System Engineers.
SE's are responsible for defining system level requirements. This includes
detailed interaction requirments between the various actors in the systems,
what the rules are and how the interaction should occure given various
senarios. The System Engineers are currently using UML (Rose) linked with
SLATE to define requirements and describe the interactions. The Software
Engineers take the output of the SE's and use the modeling to develop the
software code.
You may want to attach a business name to the SE's, but its the same
function.
"McMurry, Knox"
<knox.mcmurry@bankofa To: [EMAIL PROTECTED]
merica.com> cc: [EMAIL PROTECTED],
[EMAIL PROTECTED]
Sent by: Subject: (ROSE) RE: (RUP) Business
Analysts be part of IT
owner-rose_forum@rati
onal.com
11/27/02 08:46 AM
Please respond to
"McMurry, Knox"
Hi Naidu,
I am a manager of a group of business analysts. In my organization, the
BAs take rough, high-level requirements from the business sponsor and write
the use cases, detailed software requirements, activity diagrams, and other
necessary artifacts that the development teams will actually develop the
application from. So, from what you are saying below, we are not actually
doing BA work, is that correct? If so, then what is our true role?
Systems analysts?
This has been an item for debate in my group for quite some time, and I
would appreciate the feedback from this group.
Cheers,
Knox
-----Original Message-----
From: Naidu, Om [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 27, 2002 8:55 AM
To: 'Charles Edwards'
Cc: [EMAIL PROTECTED]; '[EMAIL PROTECTED]';
'[EMAIL PROTECTED]'
Subject: RE: (RUP) Business Analysts be part of IT
Hi Charles,<?xml:namespace prefix = o ns
= "urn:schemas-microsoft-com:office:office" />
I have a doubt for long lingering in my mind. I think that this
concept of Business Analyst caught up to the limelight for the
past three years. However, there is no clear definition of what
qualifies one to be a business analyst. In most of the software
development houses, the BAs are erstwhile project coordinators
of excellent administrative skills and MS Office, mostly,
without much or no software development skills. Such BAs find
it hard to understand UML or any development methodology and
they hate to learn anything new also.
So, is there a clear definition of what qualifies (technically
speaking) one to be a BA in a software development house? For
that matter I would like you to give us some understanding on
the technical qualifications of various roles as defined by
RUP.
I remember that you came out with a much acclaimed white paper
"Technically implementing RUP with Rational Tools" for a
million $$ (as stated in your paper) question from me, about a
year back.
A white paper on this topic will definitely help all HR or
program managers to define the roles and responsibilities of
various human actors in project management. It would be nice if
we have a white paper followed by the old one on:
"The requirements of the human-actors in Roles and
Responsibilities as defined by RUP".
Thank you very much for your contributions,
Om Naidu,
Rational-RUP-Administrator,
Pfizer Inc., USA
-----Original Message-----
From: Charles Edwards [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 27, 2002 7:34 AM
To: 'Baynes, Steve'; [EMAIL PROTECTED]
Subject: (RUP) Business Analysts be part of IT
| This leads me to the question "Should business analysts be
| part of the IT organisation?" IMO no, no, no. The business
analyst needs
| to be seen as part of the business they are analysing!
I agree with you fully on this point. There should be a
separate entity in Business where a small group of Business
Analysts called "Business Architecture" or something, whose aim
is to formally document Strategy, and Business process. They
should make use of UML and define the business processes at a
level above the software implementations.
o Business Analysts on any one project tend not see the
Business as a whole.
o They tend to get sucked into Software and software
implementation issues, like we do it this way because Product X
forces us to...
This would allow individual projects to go to the Business
Architecture when they start and get the ready made Business
Use Cases, Business Object Models, Business Visions and
Strategy document, and align their particular projects to this
centrally available information.
Obviously the people who staffed this "Business Architecture"
team would be from a Technical IT background where they learned
about Modeling and Analysis, etc. but owned by, managed and
close to the Business directly.
Comments?
regards
Charles Edwards
Software Process Engineer
Concise Group Limited
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential and
may be privileged. It is intended for the addressee(s) only. Access
to this E-mail by anyone else is unauthorized. If you are not an
addressee, any disclosure or copying of the contents of this E-mail
or any action taken (or not taken) in reliance on it is unauthorized
and may be unlawful. If you are not an addressee, please inform the
sender immediately.
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Post or Reply to: [EMAIL PROTECTED]
* Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
* http://www.rational.com/support/usergroups/rose/rose_forum.jsp
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
* To: [EMAIL PROTECTED]
* Subject: <BLANK>
* Body: unsubscribe rose_forum
*************************************************************************
