Add a comment


Re: Grouping Components by Use Case

I use a similar approach. But it has been better for me to define logical component diagrams for the distributed systems that my designs are for. Then tie them together using a deployment diagram.

This reduces the mess that tends to come from trying to highlight components by multiple use cases. It also helps keep diagram maintenance minimal and speed up the design process.

Although it does lead a little to catalog management. Which is seemingly . inevitable and always irritates me. Of course I am ever hopeful of a better solution ...

Re: Grouping Components by Use Case

HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
E-mail address
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).