- Use case diagram: Represents a functional module of the system and is simply a description of the system function. Use case diagrams include the relationships between use cases, roles, roles, and use cases, and between use cases within the system.
- Class Diagram: Indicates which entities are included in the system and how each entity is associated.
-
- In addition to representing the internal structure of an entity, a class diagram can represent the interrelationships between entities and three basic relationships between classes:
-
- Associations (including aggregations, combinations)
- Generalization (same concept as inheritance)
-
- Dependency: If a class's changes result in another class change, a dependency is called a two class.
-
- Component diagram: A large application is typically not a class or a set of classes that can be done, typically consisting of one or more deployable components. Reusable components are typically packaged into Jar,war packages. Component diagrams are used to represent dependencies between components.
-
- Deployment diagram
- Sequence diagram: Shows the detailed process of the specific use case, and shows the invocation relationship between the different objects in the process, and the sequence diagram describes the interaction between the objects (the sequence diagram and the communication diagram are called interaction diagrams).
-
- Activity diagram: A process used to describe an activity or method within a use case.
-
- State machine diagram: Describes the different states that need attention in an object's life cycle, and describes in detail the events that stimulate the state of the object and the actions taken when the state of the object changes.
-
Java Learning Note (ii) UML Basics
