Enterprise architect and Startuml Express UML common diagram

Transferred from: http://www.cnblogs.com/alexlee73/archive/2011/11/05/2237294.html

Attached: http://download.csdn.net/download/tiancen2001/1529391

1.UML is divided into:

1) Static Modeling: System Foundation and system fixed frame structure, these graphs are often "static".

• Class Diagram: Commonly used to analyze business concepts
• Use case Diagram: Common
• Object Diagram: Infrequently used
• Component Diagram (Component Diagram): Occasional use
• Deployment diagram (Deployment Diagram): Occasional use

• Package diagrams (Package Diagram): Infrequently used

2) Dynamic Modeling: Describes a behavior that is "dynamic".

• Activity Diagram: Occasional use
• Status machine diagram (state machines Diagram): Ibid.
• Timing Diagram (Sequence Diagram): Common
• Communication diagram (communication Diagram): Infrequently used
• Time graph (Timing Diagram): Infrequently used

2 Use case diagram:

Activity by: User

Use Case: Core functionality

Indicates what functionality a certain user can perform.

The use case Diagram EA's function is richer than the startuml, the relative restraint also will be much more, I still quite like the EA effect.

3. Timing Diagram

Captures the interaction information between multiple objects over a period of time, emphasizing the chronological order of information interactions.

STARTUML and EA are not able to represent the return values of the time series diagram, which they are similar.

4. Component diagram (component diagram) (Dashed line indicates dependency)

Represents a relationship between components

5. Deployment diagram

Deploying physical device information for software applications

6. Activity diagram (similar flowchart)

In contrast, I prefer the EA's presentation effect, compared to Offic's viso effect is more good.

Enterprise architect and Startuml Express UML common diagram