Made with
ConceptDraw
DIAGRAM 15

About UML

Unified Modeling Language (UML) is a language of graphic description for object modeling in the field of software engineering. UML was created for definition, visualization, designing of software systems. It was developed in the 1990s by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software Corporation.

In 1997 was adopted the UML 1.1 version by the Object Management Group (OMG).

In 2000 the UML 1.4.2 version was accepted by the International Organization for Standardization (ISO) as an open standard ISO/IEC 19501:2005 that uses graphic notations for creating visual models of object-oriented software systems. UML took in the notations of the Object-modeling technique, Object-oriented software engineering and the Booch method. UML can be applied for all the processes of the development life cycle.

In 2005 by OMG was adopted the UML 2.0 version that was seriously reworked. The last published version in 2011 was UML 2.4.1.


Types of UML Diagrams

Two types of diagrams are used in UML: Structure Diagrams and Behavior Diagrams. Behavior Diagrams represent the processes proceeding in a modeled environment. Structure Diagrams represent the elements that compose the system.

There are seven types of Structure Diagrams that must be present in any modeled system:

The Behavior Diagrams group includes:

The subgroup of Interaction Diagrams controls the flow of control and data, and includes:

UML Building Blocks

The UML building blocks determine as things, relationships and diagrams.

There are four types of things in UML: Structural, Behavioral, Grouping and Annotational.

Sructural things (the static part of the model):

Class:

Class represents a set of objects that have the same structure, behavior, and relationships with objects of other classes. Classes are represented as boxes that consist of name, attributes, operations, and responsibilities.

UML Building Blocks - Class

Interface:

Interface is an abstract class that defines a set of operations that the object of the class associated with this interface provides to other objects.

UML Building Blocks - Interface

Collaboration:

Collaboration determines interactions between the elements.

UML Building Blocks - Collaboration

Use case:

Use case is a description of the system behavior on the request from the outside of this system.

UML Building Blocks - Use-Case

Component:

Component describes the physical part of the system.

UML Building Blocks - Component

Node:

Node is a resource available during the run time.

UML Building Blocks - Node

Behavioral things (dynamic part of the model):

Interaction:

Interaction is a set of messages that the elements exchange for execution the tasks.

UML Building Blocks - Message

State machine:

State machine defines the states of the object that go in response to the events.

UML Building Blocks - State

Grouping things (the mechanism for grouping the UML model elements):

Package:

Package groups the classes and other packages.

UML Building Blocks - Package

Annotational things (the mechanism for capturing the remarks, descriptions, and comments of the UML model elements):

Note:

Note is a textual explication.

UML Building Blocks - Note

Relationship :

Association:

Association is a relationship that connect two classes.

UML Building Blocks - Association

Dependency:

Dependency is a relationship when some changes of one element of the model can need the change of another dependent element.

UML Building Blocks - Dependency

Generalization:

Generalization is an association between the more general classifier and the more special classifier.

UML Building Blocks - Generalization

Realization:

Realization is a relationship between interfaces and classes or components that realize them.

UML Building Blocks - Realization

About UML *

Pic 1. UML component diagram example.

This diagram was redrawn from wikipedia.org

The documents of ConceptDraw DIAGRAM with UML Diagrams are vector graphic documents. They are available for reviewing, modifying or converting to a variety of formats: image, HTML, PDF file, MS PowerPoint Presentation, Adobe Flash or MS Visio.






TEN RELATED HOW TO's:

UML 2 4 Process Flow Diagram →

This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the UML Activity Diagram library of the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park.UML 2 4 Process Flow Diagram *
Picture: UML 2 4 Process Flow Diagram
Related Solution:

UML Composite Structure Diagram. Design Elements →

UML Composite Structure Diagram shows the internal structure of a class and the possible interactions at this structure. ConceptDraw has 393 vector stencils in the 13 libraries that helps you to start using software for designing your own UML Diagrams. You can use the appropriate stencils of UML notation from UML Composite Structure library.UML Composite Structure Diagram. Design Elements *
Picture: UML Composite Structure Diagram. Design Elements
Related Solution:

Create UML Diagram →

This sample is a UML Class Diagram that shows the banking system. The classes represented as boxes with attributes and are connected with dependency and synchronous message associations. The associations are indicated with the multiplicity 1..*. This sample can be used by the banks, by financial enterprises.Create UML Diagram *
Picture: Create UML Diagram
Related Solution:

BPMN 2.0 →

ConceptDraw DIAGRAM diagramming and vector drawing software offers the Business Process Diagram Solution from the Business Processes Area of ConceptDraw Solution Park with powerful tools to help you easy represent the business processes and create the business process diagrams based on BPMN 2.0 standard.BPMN 2.0 *
Picture: BPMN 2.0
Related Solution:

Sales Process Flowchart Symbols →

The most easier way of creating the visually engaging and informative Sales Process Flowchart is to create the new ConceptDraw document and to use the predesigned vector symbols offered in 6 libraries of the Sales Flowchart Solution. There are more than six types of sales process flow diagrams, ConceptDraw DIAGRAM software is flowchart maker which include six collections of extended flowchart symbols for effective diagramming. There are main collections of color coded flowchart symbols: Sales Department, Sales Steps, Sales Workflow, Sales Symbols and special set of Sales Arrows and Sales Flowchart.Sales Process Flowchart Symbols *
Picture: Sales Process Flowchart Symbols
Related Solution:

Entity Relationship Diagram Software Engineering →

While designing a conceptual data model, you should use appropriate software. For instance, ConceptDraw DIAGRAM is a user-friendly ER diagram tool that has a lot of samples and templates to facilitate your work. A clear entity-relationship diagram helps to define the relations between system’s components. Software engineering is the section of a computer science engaged to design, realization, and support of complex software products. An ERD is a data modeling method that is widely applied in the software engineering practice. Commonly it is used for developing a structure of a a relational database. An entity relationship diagram is helpful for structuring and organizing databases that can be modeled using a relational structure. An entity relationship diagram is designed to depicts the interrelationships within the sets of entities which are accumulated in the database. Each entity represents a particular component of a data. Thus, ER diagrams depicts the logical structure of databases. ConceptDraw ER Diagrams solution provides software engineers with the professional tool for making entity-relationship diagrams.Entity Relationship Diagram Software Engineering *
Picture: Entity Relationship Diagram Software Engineering
Related Solution:
ConceptDraw
DIAGRAM 15