What approach has the examinees taken for sequence diagram?
1) Show names of the methods in a great detail. e.g., getItinerary() 2) Also show attributes in those methods. e.g. getItinerary(customer) 3) Only add notes, instead of showing method names. e.g., Get list of itineraries for a customer as a note.
Originally posted by Sam Gehouse: What approach has the examinees taken for sequence diagram?
1) Show names of the methods in a great detail. e.g., getItinerary() 2) Also show attributes in those methods. e.g. getItinerary(customer) 3) Only add notes, instead of showing method names. e.g., Get list of itineraries for a customer as a note.
Or, a combination there of?
I've chosen the first option, since I wanted to keep the sequence diagrams clean.
I am following a pattern where I am not even displaying the parameters. Its just getThis or setThat. I am displaying notes to connect to other sequence diagrams or to elaborate on what a class is doing at that point of time
The approach to be used depends of what kind of diagram you're about to define. In OOAD (Object Oriented Analysis and Design) there are two kinds of diagrams.
If you create a sequence diagram at the analysis level, you should take the option number three, which is, use a more detailed expression. If your diagram are in the design level, you should take take the option number two.
Regarding that architecture for the use case level, is related to design, so the answer is something clear at this point
I have a question on this thread. I am planning to use option three and I am using StarUML for the sequence diagram. When I attach a name to the call it by default attaches method symbol i.e. (). However I can change the type of the actionKind property for the call to value send instead of call and removes the method symbol. But at this stage it does not show the life span of the call.
My question is is the diagram valid without life spans being not indicated while methods are represented as descriptions and not actual method names.
If you change the value of call to "Send", it shows that it's an asynchronous call. And that's why it doesn't show you lifespan of call. It's valid representation of asynchronous call. You should decide if your design need an asynchronous call. Hope it helps,
Post by:autobot
It was the best of times. It was the worst of times. It was a tiny ad.
a bit of art, as a gift, the permaculture playing cards