|Re: Use-case doubts [message #1780664 is a reply to message #1780650]
||Thu, 25 January 2018 14:13
| Charles Rivet
Registered: May 2014
I agree with Richard Freggi's comments on this matter. "Applying Use Cases" is definitely a good read, and "Elements of UML2 style is useful - but, although not required, a knowledge of UML is definitely beneficial for the latter.|
If you absolutely want to use the boundary (and I have met people who "absolutely" need it...), you best bet is to use a class, hide all its compartment save for name, scale it properly for use case, and make sure it's in the background. Note that this is a WORKAROUND and is NOT the right approach and I would NOT recommend a generalized use of that approach! However, I have had to take that approach in the past where it was the only solution I could find to address the client's requirement to show, on a single diagram, use cases from multiple systems in a "system of software systems" where UML was required by the client when SysML would have been a much better choice...
I would also like to mention note that sequence diagrams is one way to show the "how", activity diagrams is another one to do that. The choice of diagram to use will depend on many aspects, such as application domain, industry, client familiarity with diagrams, etc.
Powered by FUDForum
. Page generated in 0.02195 seconds