Ashu works for TechnoSolutions which offers use case modeling software in its product line. So, he was well versed in the subject matter and did a good job of walking the line between presenting the topic while not hanging out his shingle for his product.
He walked the group through the basics of use cases, the situations that they serve best, and how to build a sample use case for an ATM machine. I remember working with use case modeling software back in college (mid 90's) and it stunk. Clunky and slow. It was interesting to see it fresh, running on the .Net platform in all of its glory.
The refresher was nice. Not too much in the OMG category, but good to see. During the presentation, Ashu made a point of how the traditional software requirements specification was long, boring and difficult to read. Use cases were better for everyone on the team, regardless of background. When we completed the exercise, I thought back over all of the documentation that we had created and how complex it became with all of the alternative paths and exception cases. I don't think there is a "simple" way to explain a complex problem. Software that costs a lot of money and consumes a lot of hours just can't be explained sufficiently on one sheet of paper, 12 point font. Its going to take stacks and stacks of paper and a keen eye to sift through the documents to make sure each party is getting what they want. No way around it.
dasBlog theme by Mads Kristensen
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.