The Unified Modeling Language

The Unified Modeling Languag (UML) is a standard visual modeling language intended to be used for

• modeling business and similar processes,
• analysis, design, and implementation of software-based systems

UML is a common language for business analysts, software architects and developers used to describe, specify, design, and document existing or new business processes, structure and behavior of artifacts of software system.

UML CLASS DIAGRAM

Class diagram is a static diagram. It represents the static view of an application. Class diagram is not only used for visualizing, describing, and documenting different aspects of a system but also for constructing executable code of the software application.

Class diagram describes the attributes and operations of a class and also the constraints .

USECASE DIAGRAM

Use case diagrams consists of actors, use cases and their relationships. The diagram is used to model the system/subsystem of an application. A single use case diagram captures a particular functionality of a system.The purpose of use case diagram is to capture the dynamic aspect of a system

DATA FLOW DIAGRAM:

What is a data flow diagram?

A data flow diagram (DFD) maps out the flow of information for any process or system. It uses defined symbols like rectangles, circles and arrows, plus short text labels, to show data inputs, outputs, storage points and the routes between each destination.

ACTIVITY DIAGRAM:

What is an activity diagram?

The unified modeling language includes several subsets of diagrams, including structure diagrams, interaction diagrams, and behavior diagrams. Activity diagrams, along with use case and state machine diagram, are considered behavior diagrams because they describe what must happen in the system being modeled.

SEQUENCE DIAGRAM:

A sequence diagram is a type of interaction diagram because it describes how—and in what order—a group of objects works together. These diagrams are used by software developers and business professionals to understand requirements for a new system or to document an existing process. Sequence diagrams are sometimes known as event diagrams or event scenarios.

COMPONENT DIAGRAM:

Component diagrams are different in terms of nature and behavior. Component diagrams are used to model the physical aspects of a system.  Physical aspects are the elements such as executables, libraries, files, documents, etc.

Component diagrams are used to visualize the organization and relationships among components in a system. These diagrams are also used to make executable systems.

DEPLOYMENT DIAGRAM:

Deployment diagrams are used to visualize the topology of the physical components of a system, where the software components are deployed.

Deployment diagrams are used to describe the static deployment view of a system. Deployment diagrams consist of nodes and their relationships.