component-diagram | 易学教程

Is this okay to use UML component diagram for a 3-tier Architecture?

阅读更多关于 Is this okay to use UML component diagram for a 3-tier Architecture?

问题 There are so many types of diagrams in UML. I am little confused about which one to use for what. I designed a 3-tier architecture for my web application software using UML Component Diagram. Please see the attached image and tell me if I'm doing this right or wrong. Is this a good idea to use Component Diagram for this architecture? 回答1: Basically I agree with @KeizerHarm's answer. However, there's a flaw in your diagram. Rather than packages you should use components since you put ports on

How to correctly use port and interfaces in a UML2 component diagram

阅读更多关于 How to correctly use port and interfaces in a UML2 component diagram

问题 I haven't understood well how to use port, connector and interfaces in a UML2 component Diagram. I understand that a component can be a physical or a logical component, is the same with interfaces? For example a required import becomes a required interface in component diagram or a simple usage as in class diagram? And also I don't understand the concept of a port as an interaction point: is only a representation of enter and exit point in amicroservice? To understand I've made two very

Component diagram dependency vs assembly

阅读更多关于 Component diagram dependency vs assembly

问题 I'm having a hard time understanding the difference between dependency and assembly(ball and socket) in UML component diagram. I googled a lot and only found this relative question : uml component diagram difference between assembly and interfaces with dependency But I don't really understand the answer to that question, I specifically want to ask : What does he mean by "definition level" and "instance level" ? I understand that there is only one diagram, are there two ? Whether there are two

UML diagram for dependency between systems

阅读更多关于 UML diagram for dependency between systems

Which UML diagram is the best for showing dependency between our IT system and other external IT systems? For example I would like to show on diagram: system A gets data from system B system B can call some functionality from system A I'm wondering between component diagram and sequence diagram. What do you think? Components definitelly, and dependencies. Dependency does not go in direction of the data-flow, but from the component that "knows" other component (invokes something from it, creates an object, etc). The following diagram shows the idea. It is common (and highly recommendable)

UML diagram for dependency between systems

阅读更多关于 UML diagram for dependency between systems

问题 Which UML diagram is the best for showing dependency between our IT system and other external IT systems? For example I would like to show on diagram: system A gets data from system B system B can call some functionality from system A I\'m wondering between component diagram and sequence diagram. What do you think? 回答1: Components definitelly, and dependencies. Dependency does not go in direction of the data-flow, but from the component that "knows" other component (invokes something from it,