UML 2.0 - Overview

UML Tutorial

UML (Unified Modeling Language) is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems. UML was created by the Object Management Group (OMG) and UML 1.0 specification draft was proposed to the OMG in January 1997. It was initially started to capture the behavior of complex software and non-software system and now it has become an OMG standard. This tutorial gives a complete understanding on UML.

Purpose of UML

"An image speaks louder than words," and this is perfectly applicable when discussing UML. Object-oriented concepts were introduced before UML, and at that time, there were no standardized methods for organizing and consolidating object-oriented development. This is when UML was introduced. While there are many goals for creating UML, the key objective is:

To establish a general-purpose modeling language that all modelers can use, and it should also be simple to understand and apply. It is designed for developers, but also for business users, common people, and anyone wanting to understand the system. The system could be either software or non-software. It is important to note that UML is not a development method, but it supports processes to ensure the success of a system. In conclusion, the purpose of UML can be defined as providing a simple modeling tool for modeling any practical systems in todays complex environment.

Audience

This tutorial has been prepared for beginners to help them understand the fundamentals of UML. After completing this tutorial you will find yourself at a moderate level of expertise from where you can take yourself to the next levels.

Prerequisites

No specific skill is required as a prerequisite to understand the learning material in this tutorial. The reader must be enthusiastic to acquire knowledge on UML.

FAQs on UML

There are some very Frequently Asked Questions (FAQs) on UML, this section tries to answer them briefly.

UML diagrams are commonly used in software engineering. The main reasons for integrating UML diagramming into the development process when creating new products or systems are twofold.

The primary goal of UML is to define a simple, general-purpose modeling language that can be easily understood and used by all modelers.

Yes, UML is not limited to software systems and can also be used to model non-software systems, such as process flows in manufacturing.

No, UML is not a programming language, but it can be used to generate code in various languages through its diagrams.

UML is closely related to object-oriented analysis and design, helping to visualize and document the relationships between objects, classes, and their behaviors in a system.

A use case diagram captures the functional requirements of a system by representing use cases, actors, and their relationships, helping in high-level design and planning.

The major elements of UML include UML building blocks, rules for connecting these blocks, and common mechanisms of UML.

The main types of UML diagrams include Class diagrams, Object diagrams, Use case diagrams, Sequence diagrams, Collaboration diagrams, Activity diagrams, Statechart diagrams, Deployment diagrams, and Component diagrams.

The types of relationships in UML include Dependency, Association, Generalization, and Extensibility, each representing different ways elements are connected or related in a system.

Start by learning the basic building blocks, then practice with diagrams and modeling techniques.

Print Page