Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After reading Applying UML and Patterns (Larman) and looking around on the Internet it still seems ambiguous to me if a UML communication diagram should depict implementation details (such as GUI related function calls) or be more bound to the analysis. What is the correct answer? Does UML even specify it?

share|improve this question
up vote 4 down vote accepted

Well, it depends on the view the diagram belongs too.

If the diagram is part of the Logical View or the Use Case View, it should not dive into the very details of the implementation because this view is concerned with the functionality provided to end users and may be used communicate the architecture to end users, domain experts and others who do not care much about the internal functions.

On the other hand if the diagram is part of the Development View, it's your call. The development view is used to communicate the architecture to the developers. So if you believe the details of GUI function calls and so on will help the developer understand what you want then it's Ok.

share|improve this answer
+1 for a pragmatic and common sense answer. – maple_shaft Apr 30 '13 at 1:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.