Wednesday, May 22, 2013

   Quick Links:   Articles     MA Blog     Community Blog     Templates     Books     BA Humor     Events     Jobs     Interview Questions         RSS Feeds

Business Analyst Articles: Business Analysis & Systems Analysis

Resources




BA ARTICLE ARCHIVE
» May 2013 (6)
» April 2013 (8)
» March 2013 (4)
» February 2013 (6)
» January 2013 (6)
» December 2012 (5)
» November 2012 (7)
» October 2012 (6)
» September 2012 (6)
» August 2012 (5)
» July 2012 (9)
» June 2012 (5)
» May 2012 (9)
» April 2012 (7)
» March 2012 (7)
» February 2012 (5)
» January 2012 (7)
» December 2011 (6)
» November 2011 (6)
» October 2011 (8)
» September 2011 (6)
» August 2011 (8)
» July 2011 (7)
» June 2011 (7)
» May 2011 (6)
» April 2011 (8)
» March 2011 (6)
» February 2011 (5)
» January 2011 (6)
» December 2010 (5)
» November 2010 (9)
» October 2010 (5)
» September 2010 (6)
» August 2010 (8)
» July 2010 (6)
» June 2010 (6)
» May 2010 (10)
» April 2010 (5)
» March 2010 (8)
» February 2010 (7)
» January 2010 (7)
» December 2009 (7)
» November 2009 (7)
» October 2009 (6)
» September 2009 (8)
» August 2009 (10)
» July 2009 (9)
» June 2009 (5)
» May 2009 (10)
» April 2009 (5)
» March 2009 (12)
» February 2009 (8)
» January 2009 (6)
» December 2008 (9)
» November 2008 (8)
» October 2008 (9)
» September 2008 (4)
» August 2008 (6)
» July 2008 (8)
» June 2008 (17)
» May 2008 (12)
» April 2008 (7)
» March 2008 (21)
» February 2008 (16)
» January 2008 (13)
» December 2007 (9)
» November 2007 (25)
» October 2007 (2)
» September 2007 (23)
» August 2007 (12)
» July 2007 (11)
» June 2007 (7)
» May 2007 (6)
» April 2007 (9)
» March 2007 (5)
» February 2007 (3)
» January 2007 (2)
Articles and White Papers
Minimize


Current Articles | Search | Subscribe (RSS)

» What is a Business Analyst?

Statistics:Article Rating (7373 Views) (2 Comments) Print
Posted: Monday, March 15, 2010
Categories: Career as a Business Systems Analyst, Getting Started as a Business Systems Analyst, Business Analysis Planning (BABOK KA), General Business Analysis

When this paper was first published in 2003, business analysis was just starting to emerge as a distinct profession in its own right. Prior to this the role was often performed by the systems analyst who would carry out both the analysis and the design on a new system or enhancement. This often meant that a “problem” was made to fit the “solution”. The transition from telling the client what they would be getting - versus analysing their problems and recommending solutions – was still a new one for many organisations.

How things have changed – we now have an international organisation solely for business analysts (with over 11,000 members) plus a professional, experience-based qualification. We also have a reference guide - The Business Analysis Body of Knowledge (BABOK®) - now into its second edition.

And yet the underlying skills needed by business analyst have remained remarkably constant – analysts still need investigative, analytical and communications skills for dealing with clients and stakeholders. They also need specification and modelling skills when dealing with developers and solution providers.

In this latest version of the paper we’ve updated the methodologies, techniques and tools references to reflect current trends and usage – but the mix of soft and hard skills which was the basis of the first version of this paper remains consistently relevant today. The business analyst can be confident that their fundamental skills will not be outdated anytime soon.

Today the term Business Analyst is synonymous with a career in the IT industry but the most successful and valuable analysts are those who understand the 'business' rather than those who understand IT. So what exactly is a Business Analyst?  What is the Business Analyst’s role?  What is the best background for this job? What skill set is required?  What type of person is the best fit?  What training is required and available?

This article/whitepaper includes:

  • The modern business analyst – a definition
  • Evolution of the business analyst
  • Typical background requirements for business analysts
  • Today’s business analyst – the job role
  • Techniques and methodologies
  • Software tools
  • A skills roadmap for the professional business analyst

Authors: Derrick Brown and Jan Kusiak, IRM Training Pty Ltd

Read More ...

Rating
Comments
Hi:

Let me ask you a question: How would you position data flow diagrams, use cases, BPM techniques, and activity diagrams relative to each other?

Hints to the answer:

* The answer is not "use whatever you feel is the best"
* The BABOK 2.0 is wrong and incomplete in answering this question

The answer to this above question is the key to what the essence of business analysis really is.

Tony

posted @ Tuesday, March 16, 2010 9:24 AM by ajmarkos


It may be based on where is the process are you or to which level of detail are the requirements being gathered.

Example, if you are designing a high level process then a flow diagram may be best to illustrate it and find gaps or specific points where requirements need to be gathered.

Alternatively if you are a level deeper and need to get into some specifics, then a use case will be better as that will help drive primary and alternate scenarios based on user needs.

I am rather new to the "theory" of BA, hope i am on the right track.

Thanks for the question.

posted @ Tuesday, March 16, 2010 12:55 PM by vikdave


Only registered users may post comments.
  

Do you twitter?: If you want short updates on what's going on in the BA world and at ModernAnalyst.com, simply follow us on Twitter: http://twitter.com/ModernAnalyst



 

Privacy Statement  |  Terms Of Use
Copyright 2006-2013 by Modern Analyst Media LLC