Two weeks to go until exam day and in the nitty gritty of my BAMentor prep course (with my super-amazing instructor, Kym Byron). Last night we went over some of the key techniques in Requirements Analysis – data modeling, data flow diagrams, sequence diagrams, use cases, user stories, and the like.
Some of this seemed so readily apparent, the BABOK terms falling nicely into place. Other aspects seemed so completely foreign.
And that’s when it hit me over the head.
The BABOK makes so much sense when…you’ve done it before!
Never having done decision analysis, the description to “calculate expected value of outcomes” seemed foreign until Kym went over it a second time. (Then it was relatively simple.)
Never having done a sequence diagram, I had to break apart the elements and try to piece them together. Essentially, using the BABOK descriptions to teach myself how to do a quick and dirty sequence diagram.
But having written user stories, the knowledge fell right into place (or validated what I already knew). And though I’ve never done anything I called Functional Decomposition, I could definitely relate the material to examples from my own work.
Obviously, this opinion isn’t the result of any fancy rocket science. But the realization hit me with so much force, I thought it would be worth sharing.
>>Learn More About Becoming a CBAP or CCBA
Interested in becoming a CBAP or CCBA? We cover 8 steps to the CBAP certification, that will take you to just learning about the certification to successfully sitting for the exam.