Articles Blogs Humor TemplatesInterview Questions
Question for all:
The way I learned it and have experienced it, analysis is largely about properly partitioning a system. Yet, I have reviewed the BABOk (v 1.6) and could not even find the word partitioning mentioned once. Am I missing something or is this a fundamental error?
Tony
Tony,
I recently arrange a talk for my local BA chapter. The principal speaker, who is also the principal trainer for one of the local software houses, opened his address with the following comment; “the BABOK is not for the novice. In fact it is very difficult for anyone who does not have an understanding of Business Analysis to appreciate the text”. He then went onto describe that it is a Meta-model, which constrains the methodologies that sit underneath it. The conception is similar to the PMBOK, which governs methodologies like PRINCE2 etc. Likewise, a methodology like SADM, RUP, Agile etc., is governed by the BABOK. Hence one does not expect to find any specifics about SADM (partitioning) in the tome. Having said this, I have not read the latest version. I’m a little IIBA/BABOK agnostic.
warm regards,
K
But K, partitioning is not a SADM (Structured Analysis and Design) thing. Irregardless of what analysis tool is choosen, the system functionality still needs to be partitioned (i.e., broken up).
Isn't it strange that analysis is largely about partitioning, and yet a handbook on how perform analysis does not even mention it?
I have done a fair amount of technical writing, and often a big part of that work is evaluating existing documentation for usability. I have read alot of documentation that goes on-and-on-and-on about all kinds of stuff, but that is largely unintelligable - by anybody - because the author skipped over key fundamentals necessary for a reader to comprehend all the other stuff. And if the author did not understand the fundamentals himself/herself - a very common occurance - the documentation is even more difficult to comprehend.
I think the BABOK v2 is a bunch more readable than v1.6 was. The before/after description includes a lot of consolidation of topics.
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: