Create the following source file example.cpp: class Animal { public: void die(); string name; int age; }; class Dog : public Animal { public: void bark(); }; class Cat : public Animal { public: void meow(); }; run doxygen -g and change the following options of the generated Doxyfile: EXTRACT_ALL = YES HAVE_DOT = YES … Read more
Robustness diagrams are written after use cases and before class diagrams. They help to identify the roles of use case steps. You can use them to ensure your use cases are sufficiently robust to represent usage requirements for the system you’re building. They involve: Actors Use Cases Entities Boundaries Controls Whereas the Model-View-Controller pattern is … Read more
Preliminary remark: First I’d like to than Bruno and Axel for their respective answers, that put me on the right track. Nevertheless digging further based on their indications, I stumble accross an even simpler solution and supporting references. As it’s useful and following Bruno’s suggestion I’ve finally decided to post it as ananswer. Can simple … Read more
You can use a qualified association: ┌──────────┐ 1 ┌───────┐ │ MyServer │Key│───────────│ Value │ └──────────┘ └───────┘ See: http://etutorials.org/Programming/UML/Chapter+6.+Class+Diagrams+Advanced+Concepts/Qualified+Associations/ (cause it is hard to draw using ASCII) Note also that a qualified association changes the multiplicity: ┌──────────┐ 0..* ┌───────┐ │ MyServer │───────────────│ Value │ └──────────┘ └───────┘ ┌──────────┐ 1 ┌───────┐ │ MyServer │Key│───────────│ Value │ └──────────┘ └───────┘ … Read more
A domain model is called conceptual model in database modeling, while a design model is called logical model. These distinctions are also used in model-driven development, where we have a succession of three types of models: (solution-independent) domain models resulting from domain/requirements engineering in the system analysis, or inception, phase of a development project; (platform-independent) … Read more
According to the current UML standard 2.4.1 and the next one 2.5 (it differs almost only in more simple documentation): Pointers/references should be shown as arrow with small black circle (dot) at the referenced end. If it is not pointer that the object has as an attribute, but it is counted in any way, there … Read more
In most cases, it will only clutter up your diagrams. Login is neither complex (*) nor does it give you much added value as a use case. In your textual document that includes the use cases with description, include as a prerequisite a list of features that require a successful login. Easier to track and … Read more
This shows navigability. A can see (means it has an attribute referencing) B. In contrast B has no idea about/reference to A. As @JimL commented, your arrow is wrong and only used for stereotype definition. I’m referring to the unfilled arrow which indicates navigability of associations from which I assume you actually meant that. UML … Read more
your question is not very specific as all UML diagrams display some kind of dependency or pathway how to get data or make a call, so I’m not sure if I got substance of your question right 1. there is no such thing as one best UML diagram to show it all There is usually … Read more
If else condition, also called alternatives in UML terms can indeed be represented in sequence diagrams. Here is a link where you can find some nice resources on the subject http://www.ibm.com/developerworks/rational/library/3101.html