diagram

How can I represent a diagram in which several actors have access to the same function, or "use case" but some of them have additional functions or "extends" (if im right) inside it, if i just extend on the main "use case" that would mean its accessible by everyone right? When a use case extends the main use case, extension points at the main use case, can have conditions. As a condition you could specify a specific actor. If the actors can be generalized, I have seen this solution too. But I prefer the first one because I am not sure if it is technically correct (As you noted, extend use case

In sequence diagrams, how would you represent an event triggered listener? It is not just a regular method call, so displaying like that would not seem correct. I try to make a sequence diagram of a system including a JMS listener. I could start the lifeline with the send() call of the system to the JMS queue (displaying the system calling send() as a business actor), or I could start the lifeline at the onMessage() call. (displaying JMS Queue as a business actor) Or should I just ignore the whole JMS Queue in the diagram? For what it's worth: I'm using Astah Community to create the diagrams.

I am new to UML. I have studied more tutorials.I learned two broad categories like, UML Diagrams: 1. Structural Diagrams Class diagram Object diagram Component diagram Deployment diagram 2. Behavioral Diagrams Use case diagram Sequence diagram Collaboration diagram Statechart diagram Activity diagram But I dont know which one is high level design and low design. Anyone list out the UML diagram types based on priorities. (high-level diagrams to low level) There is not really a well-defined order of higher-level versus lower-level diagram languages in UML. The same diagram language (e.g. class