All notes


There are two major groupings of UML diagrams:

The most useful, standard UML diagrams are: use case diagram, class diagram, sequence diagram, statechart diagram, activity diagram, component diagram, and deployment diagram.


Use case

MSDN: diagrams needed for user requirements.
MSDN: use case diagram.
MSDN: Class diagram.
MSDN: Activity diagram.
MSDN: Sequence diagram.

A use case diagram summarizes who uses your application or system, and what they can do with it. It can discuss and communicate:

A use case diagram does not show the detail of the use cases: it only summarizes some of the relationships between use cases, actors, and systems. In particular, the diagram does not show the order in which steps are performed to achieve the goals of each use case. You can describe those details in other diagrams and documents, and link them to each use case.

A use case represents:

The descriptions you provide for use cases will use several terms related to the domain in which the system works, such as Sale, Menu, Customer, and so on. It is important to define these terms and their relationships clearly, and you can do that with the help of a UML Class Diagram.

Use cases deal only in the functional requirements for a system. Other requirements such as business rules, quality of service requirements, and implementation constraints must be represented separately. Architecture and internal details must also be described separately.

Roles include:

Class diagram

A UML class diagram describes data types and their relationships separately from their implementation. The diagram is used to focus on the logical aspects of the classes, instead of their implementation.

You can use a UML class diagram for a variety of purposes:

Generalization, Association

Generalization and association are the two main ways to reuse code.

is a term signifying the inheritance of a class or the implementation of an interface.
is has-a relationship.

Activity diagram

An activity diagram helps you explain a more complex process where there are loops, branches and parallel threads. It can also show the flow of data between parts of the process.

Sequence diagram

A sequence diagram helps you explain a complex series of interactions between different actors. You can also use it to show what happens inside the system in response to each use case.



java -jar argouml.jar -help

# Switch back to the English UI. Please beware: the language is in lowercase.
java -jar argouml.jar -locale en

# Run without UI
java -jar argouml.jar -batch -command "org.argouml.uml.ui.ActionOpenProject=c:\Documents and Settings\Michiel\My Documents\test.zargo" -command org.argouml.ui.cmd.ActionGotoDiagram=A -command "org.argouml.uml.ui.ActionSaveGraphics=c:\Documents and Settings\Michiel\My Documents\test.PNG"