Thursday, December 11, 2003 03:56 AM
You might want to create a sequence diagram directly from the Use Case when you are working on you applications API. This is what Craig Larman calls a System Sequence Diagram
and what UML calls High level Sequence Diagram
Basically, the idea is to represent on your diagram the different inputs from user to the System as a black box. If the System returns any specific result, you show it on the diagram as well.
Based on these System Sequence Diagrams you clearly identify your System APIs (menus if you prefer). For each entry point, you will have an Operation Contract and then a Collaboration Diagram (or sequence if you prefer, as they are equivalent). But these last diagrams are using the identified classes and describe the actual interaction between the objects. They are the usual sequence/collaboration diagrams.
Craig Larmans book I am referring to is presented and reviewed on our site:http://www.liemur.com/Resources/Readings/Bibliography-En.html
In the Practical Guides section. The title is: Applying UML and Patterns
I hope it helps.