Home / UML Tutorial

UML Tutorial

Identifiable object-oriented modeling languages began to appear between mid-1970 and the late 1980s as various methodologists experimented with different approaches to object-oriented analysis and design. The number of identified modeling languages increased from less than 10 to more than 50 during the period between 1989-1994. Many users of OO methods had trouble finding complete satisfaction in any one modeling language, fueling the “method wars.” By the mid-1990s, new iterations of these methods began to appear and these methods began to incorporate each other’s techniques, and a few clearly prominent methods emerged.

The development of UML began in late 1994 when Grady Booch and Jim Rumbaugh of Rational Software Corporation began their work on unifying the Booch and OMT (Object Modeling Technique) methods. In the Fall of 1995, Ivar Jacobson and his Objectory company joined Rational and this unification effort, merging in the OOSE (Object-Oriented Software Engineering) method.

What is software Engineering?

Software engineering (SE) is concerned with developing and maintaining software systems that behave reliably and efficiently, are affordable to develop and maintain, and satisfy all the requirements that customers have …

Read More »

Definitions of Software Engineering

 Definitions of Software Engineering Over the years, numerous definitions of the discipline of Software Engineering have been presented. For the purpose of this document, we highlight the following definitions: “The …

Read More »

Software Engineering Approaches

Software Engineering Approaches Responsibility-driven versus data-driven approaches It is often said that data are more stable than functions and so data-centred approaches are to be preferred in most cases. However, …

Read More »

Evolution of UML

Evolution of UML Identifiable object-oriented modeling languages began to appear between mid-1970 and the late 1980s as various methodologists experimented with different approaches to object-oriented analysis and design. The number …

Read More »

Use of the Unified Modeling Language (UML)

Use of the Unified Modeling Language (UML) has quickly spread throughout the software development industry as a concrete foundation for designing and developing software applications. It has become the de …

Read More »

Pros and Cons of UML

  Pros and Cons of UML Pros: Wide Industry Acceptance in comparison to previous Modeling Language. Supports OOAD methodology Bridges the communication gap between different entities of system development(i.e . …

Read More »

Diagrams in UML

Diagrams in UML UML 2 defines many basic diagram types, divided into two general sets: 1. Structural Modeling Diagrams Structure diagrams define the static architecture of a model. They are …

Read More »

Structural Modeling Diagrams

Structural Modeling Diagrams Structure diagrams define the static architecture of a model. They are used to model the ‘things’ that make up a model – the classes, objects, interfaces and …

Read More »

Behavioral Modeling Diagrams

   Behavioral Modeling Diagrams Behavior diagrams capture the varieties of interaction and instantaneous states within a model as it ‘executes’ over time; tracking how the system will act in a …

Read More »

Package diagrams

Package diagrams In the Unified Modeling Language(UML), a package diagram depicts how a system is split up into logical groupings by showing the dependencies among these groupings. As a package is …

Read More »

Class Diagram

Class Diagram In the Unified Modeling Language (UML), a class diagram is a type of static structure diagram that describes the structure of a system by showing the system’s classes, their attributes, …

Read More »

Composite Structure diagrams

Composite Structure diagrams A Unified Modeling Language (UML) composite structure diagram shows the internal structure of a class and the collaborations that this structure makes possible. This can include internal parts, ports through which …

Read More »

Component diagrams

Component diagrams In the Unified Modeling Language, a component diagram depicts how a software system is split up into physical components and shows the dependencies among these components. Physical components could be, for …

Read More »

Implementation Diagram

Implementation Diagram In the Unified Modeling Language, a deployment diagram serves to model the hardware used in system implementations, the components deployed on the hardware, and the associations between those components. …

Read More »

Activity Diagrams

Activity Diagrams In the Unified Modeling Language, an activity diagram represents the business and operational step-by-step workflows of components in a system. An activity diagram shows the overall flow of control. In UML, an activity …

Read More »