Basic diagram of UML (i)



A class Diagram shows a set of classes, interfaces, and collaborations and their relationships. These diagrams is the most common diagram found in modeling object-oriented systems. Class diagrams address the static Design view of a system. Class diagrams that include active classes address the static process view of a system. Component diagrams is variants of class diagrams.

The class diagram shows the class. Interfaces and interaction sets and their relationships. These diagrams are the most common diagrams for building an object-oriented system model. A static design view of a class diagram processing system. The activity diagram included in the class diagram, which handles the static process view of the system. A component diagram is a form of change in a class diagram.

an Object Diagram shows a set of objects and their relationships. Object diagrams represent static snapshots of instances of the things found in class diagrams. These diagrams address the static Design view or static process view of a system as do class diagrams, and from the Perspe Ctive of real or prototypical cases.

The object graph shows the set of objects and the relationships between them. The object graph shows the static images of the instances, which are derived from the components established in the class diagram. The object graph deals with the static Design view or static process view of the system as if it were a class diagram. The difference is that it handles the view of a real or typical case.

AComponent Diagramis shows a encapsulated class and its interfaces, ports, and internal structure consisting of nested components and C Onnectors. Component diagrams address the static design implementation view of a system. They is important for building large systems from smaller parts. (UML distinguishes acomposite structure Diagram, applicable to any class, from a component diagram, but we combine the discussion because the distinction between a C Omponent and a structured class is unnecessarily subtle.)

The component diagram shows the encapsulated class and its interface, port. and its internal structure consisting of nested components and connectors. A static design implementation view of a Component diagram processing system. When a smaller component is built into a larger system. Component diagrams are important. (a composite structure diagram differs from a component diagram.) The combo chart is suitable for whatever class, but we discuss it here together. Because the components and structure classes are only slightly different, there is no need for a different discussion. )

A Use case diagram shows a set of use cases and actors (a special kind of class) and their relationships. Use case diagrams address the static use case view of a system. These diagrams is especially important in organizing and modeling the behaviors of a system.

A use case diagram shows a set of use cases and the participants (a special class) and their relationships. A static use case view of a use Case diagram processing system. These diagrams are especially important for the organization and modeling behavior of the system.

Basic diagram of UML (i)