Posts Tagged ‘diagram’

h1

Perfect Questions?

November 29, 2010

During a recent discussion I was having with a colleague who is an Agile Coach and Business Analyst, I asked her what the BA community was interested in regarding the practice of business analysis. Her answer surprised me. She said what many BAs want is the perfect list of questions to ask their clients. The perfect list of questions? Really? Who has that? For all situations?

Instead of the perfect list, how about a relevant list? How could that be created? What if you had a guide that could help you see what to ask? You do. Read More…

Advertisements
h1

The UML’s Double-Edged Sword

July 9, 2010

The sword is one of the most ubiquitous crafted weapons across civilizations worldwide. They come in many different shapes, sizes, and materials. An attribute that they all have in common is a sharp edge. Some multiply their offensive capability by being sharpened on both edges, i.e., the double-edged sword. These are more deadly because they can “cut both ways”. Who would have expected that the innocent use case would introduce a double-edged sword into the UML? Read more at DevX.com…

h1

The UML Survey Results Are In

June 15, 2010

In April, I invited one and all to participate in a simple survey to see how they are actually using the UML on projects. Is it really mainstreamed? Is it still in the adoption phase? Or is it in decline? The survey is now closed. Thanks to those who participated. Here are the results. Read more…

h1

The Goldilocks Conundrum

May 13, 2010

Use cases are by far the most commonly used element of the UML. This is also the area where modelers have the most difficulties. Use cases appear to be so simple and easy to use. Remember, as Jim Horning said “Nothing is as simple as we hope it will be.” … Just as Goldilocks could not find suitable sleeping arrangements, modelers often have problems with the abstraction level of a use case. In other words, is it too big? Too small? Read more on the DevX feature series Useful UML Modeling.