In continuing to cover all 49 BABOK® techniques, this entry is about scenarios/use cases.
UC Diagram-Training Example
Since most people refer to these as use cases, that’s the name I’ll use. They are a great way to elicit, analyze, and model interaction requirements. Plus, they help generate related requirements for interfaces, data, process, and business rules.
I gave a use case training class last week, so it’s fresh in my mind. It also influenced me to put this explanation in question and answer form.
Q. What is a use case?
of BAs, BI specialists, technical architects, and business SMEs (subject matter experts). What made it successful was not only the learning that took place, but also the students’ willingness and eagerness to apply this technique back on their jobs.
center for a large retailer. We provided an estimate for both the 
When I first read the BABOK® Guide, my initial reaction was, “What are they thinking?!” With my Project Manager (PM) hat perched squarely on my head, my reaction was “but… but this is 
Have you ever gazed at the stars and found it difficult to focus on a particular one? It’s initially a bit disconcerting. If you look away a small amount, the star seems to become visible. Look straight at it and the star begins to dim and even disappear. Scientists call this the “parallax effect.” I just call it frustrating (I’m an impatient star-gazer).
