Use Case Modeling
The alarm sounded too early, at least from my perspective. My adventures last night left me energized, which meant I didn't get to sleep until closer to midnight (sleep+24 hours).
I wandered downstairs about 45 minutes before the morning session. Since there was no conference session today, the line at the restaurant was quite long, so I hit the deli instead. Now, this is still inside the hotel, so don't think this is like the deli in Palm Springs with the wonderful breakfasts and desserts. No, this is your choice of day-old mixed fruit and stale bagels. I grabbed some yogurt and the 'breakfast sandwich'...a croissant with sliced ham and american cheese, expertly microwaved to order while in plastic wrap, creating a greasy mess. Ugh.
The Use Case session was only moderately interesting. It was a basic introduction to use case diagramming, setting you up for all the wonderful tools that Borland offers, though not in a sales-pitch sort of way (thankfully).
I think the things to take away are that people should be aware of the basic diagrammatic grammar (so we can communicate in a common language), and they should use the use case diagrams as a magic mirror. They are a transform that you can use to discover what plain text may not be able to express. Whether the end result stays as a diagram or goes back to text is up to you.
One interesting fact that dropped: remember all that talk about SDO tools from last year. You know, the future vision for their suite? Well, at least for now, it's all based around Java and Eclipse. If you're in Win32 or .NET, you're out of luck, at least for the forseeable future.
I wandered downstairs about 45 minutes before the morning session. Since there was no conference session today, the line at the restaurant was quite long, so I hit the deli instead. Now, this is still inside the hotel, so don't think this is like the deli in Palm Springs with the wonderful breakfasts and desserts. No, this is your choice of day-old mixed fruit and stale bagels. I grabbed some yogurt and the 'breakfast sandwich'...a croissant with sliced ham and american cheese, expertly microwaved to order while in plastic wrap, creating a greasy mess. Ugh.
The Use Case session was only moderately interesting. It was a basic introduction to use case diagramming, setting you up for all the wonderful tools that Borland offers, though not in a sales-pitch sort of way (thankfully).
I think the things to take away are that people should be aware of the basic diagrammatic grammar (so we can communicate in a common language), and they should use the use case diagrams as a magic mirror. They are a transform that you can use to discover what plain text may not be able to express. Whether the end result stays as a diagram or goes back to text is up to you.
One interesting fact that dropped: remember all that talk about SDO tools from last year. You know, the future vision for their suite? Well, at least for now, it's all based around Java and Eclipse. If you're in Win32 or .NET, you're out of luck, at least for the forseeable future.
0 Comments:
Post a Comment
<< Home