UML Components

The UML certain number of graphical elements combined into diagrams. Because it is a language, the UML has rules for combining these elements.

The purpose of the diagrams is to present multiple views of a system, and this set of multiple views is caled a model.

  UML model describes what a system is supposed to do. It doesn't tell how to implement the system.

Let's take a brief look of all the UML diagrams. UML consists of nine basic diagrams, but bear in mind that hybrids of theese diagrams are possible.

Class Diagram
Things naturally fall into categories (computers, automobiles, trees...). We refer to these categories as classes.

  A class is a category or group of things that have similar attributes and common behaviors.

Class diagram provide the representations used by the developers.
For detailed informations about Class diagrams Click Here!

Object Diagram

An object is an instance of a class - a specific thing that has specific values of the attributes and behavior.

Use Case Diagram
A use case is a description of a system's behavior from a user's standpoint.
For system developers, this is a valuable tool: it's a tried-and-true technique for gathering system requirements from a user's point of view. That's important if the goal is to build a system that real people can use. In graphical representations of use cases a symbol for the actor is used .

The actor is the entity that initiates the use case. It can be a person or another system.

For detailed informations about Use Case diagrams Click Here!

State Diagram
At any given time, an object is in particular state. State diagrams represent these states, and their changes during time. Every state diagram starts with symbol that represents start state, and ends with symbol for the end state. For example every person can be a newborn, infant, child, adolescent, teenager or adult.
For detailed informations about State diagrams Click Here!

Sequence Diagram
Class diagrams and object diagrams represent static information. In a functioning system, however, objects interact with one another, and these interactions occur over time. The UML sequence diagram shows the time-based dynamics of the interaction.
For detailed informations about Sequence diagrams Click Here!

Activity Diagram
The activities that occur within a use case or within an object's behaviour typically occur in a sequence. This sequence is represented with activity diagrams.
For detailed informations about Activity diagrams Click Here!

Collaboration Diagram
The elements of a system work together to accomplish the system's objectives, and a modeling language must have a way of representing this. The UML collaboration diagram is designed for this purpose.
For detailed informations about Collaboration diagrams Click Here!

Componenet Diagram
Today in software engineering we have team-based development efforts, where everyone has to work on diferent component. That's important to have a component diagram in modeling process of the system.
For detailed informations about Component diagrams Click Here!

Deployment Diagram
The UML deployment diagram shows the physical architecture of a computer-based system. It can depict the computers and devices, show their connections with one another, and show the software that sits on each machine.
For detailed informations about Deployment diagrams Click Here!

System development is a human activity. Without an easy-to-understand notation system, the development process has great potential for error.
Consisting of a set of diagrams, the UML provides a standard that enebles the system analyst to build a multifaceted blueprint that's comprehensible to clients, programmers, and everyone involved in the development process. It's necessary to have all these diagrams because each one speaks to a different stakeholder in the system.
The UML model tells what a system is supposed to do. It doesn't tell how.