Site Sponsors:
Rhapsody Examples + UML Use Cases 

Off to a Shaky Start?

This first thing to be aware of when using Rhapsody is that *it matters* how you start it! If you are using Rhapsody in C, do not start a new project in Rhapsody for C++ or Java. (The rest of that truth table is also true!)

While that observation might sound moronically simple, when completing the sample exercise (yes, they do indeed work fine!) more than a few of us have been unable to get them completed for 'unknown reasons.' If you have / are having trouble completing the sample exercises in Rhapsody, check your unit type. (Right click on the main project name in Rhapsody, then select 'Edit Unit'')

Do This First

From the main Rhapsody menu, you can also select 'Help', then 'List of Books.' Notice that from User's Guides and oh-too-much information and reference materials, there are also tutorials for each and every language of choice.

After ensuring that your 'Edit Unit' language is what is appropriate for the tutorial that you intend to complete, complete one or more of them. They work great.


Did you do the exercises? Good! You now have a 'bottom's up' view of what Rhapsody can do for you.

But wait ' Before settling into your cubicle to radiate within your newfound superpower, re-visit that 'why are we doing this' -thread from the previous blog entry. Aside from documenting what we have done (in ways that even you and I will have to struggle to understand a few months from now), how has what we have just learned changed anything? While using pictures to generate code is cool, what was all that stuff about re-use, patterns, (bla, blaa ...) and managing expectations?

Codeless Diagrams

To truly appreciate what architecture can do for you, we need to start at the top. Specifically, we need to be able to create designs that even our mothers can relate to.

Impossible you say? Well, even if you mother is not exactly Grace Hopper, the Use Case Diagram (without a doubt the top-most diagram on the UML totem-pole), can help.

Use Cases

A relative late-comer to the OMG inventory of pulp-only artifacts, Use Cases allow us to begin to define our systems in a way that everyone can understand. Buy focusing on nouns and verbs, (aka Actors and Scenarios), Use Cases allow us to capture the essence of what others will want our system(s) to do.

(click above to view)

Simple, eh? (Yes 'My Mom gets it, too.)

While there can be a lot more to completely understanding use cases in all of their trivial glory (documentation formalisms, include 'v- extend relationships, actor inventories & inheritance, etc.) there are entire books dedicated to the subject. Feel free to pick one up... or not. What we have above is all we need to know for the moment.

The nice thing about Use Cases is that we can use them to discuss anything ' and at any time.

(click above to view)

When overlapping versions and other such messages, the use of colors can help a lot.

Next: Sequence Diagrams

-Stay tuned!


Add Comment
Comments are not available for this entry.