uml

I heard composition is preferable over inheritance. So when I design my simple game engine I tend to do the following: http://yuml.me/1252399d instead of: http://yuml.me/51cacb4f Is this a good approach, or should I reconsider? Edit: To clarify the notation. The arrows means inheritance, the arrows with a diamond means composition and the <<>> means interface. More info on the notation is available at the yUML webpage . OK, there are a few things to cover here. First: why do you need to express commonality between PointLight and Spotlight ? Is it Because there are clients who simply want to

I have imported a PHP source folder into Enterprise Architect. Now, I'd like to see the inheritance chain of any specific class. In other words, I'd like to see one big diagram displaying all relations of a class. Most classes are in folders separate from the parent/child class. How can I do that..? This was my reason for installing Enterprise Architect: I get confused within a lengthy and branched inheritance chain. It would be very disappointing if such a powerful tool that recognizes all relationships could not give an overview of these relationships. For example, I can see a class diagram

Does anyone know of any kind of UML variation which can map events in a GUI system? I have a quite complex event driven GUI system and I would like to create a diagram so new developers can easily get an overview of events fired by various views and what models/controllers or view are instantiated/effected by these events. I was looking for something that would look more like a mind map which branches all over the place rather than linear scenarios. Does anyone have any ideas? Regards, Chris State diagrams. Old and pricey, but here is a great text on modeling user interfaces with state charts.

Closed . This question needs to be more focused . It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post . Closed 2 years ago . What is the difference between sequence diagrams and communication (collaboration) diagrams in UML? Quoting Wikipedia : Communication diagrams show a lot of the same information as sequence diagrams, but because of how the information is presented, some of it is easier to find in one diagram than the other . Communication diagrams show which elements each one interacts with