The Unified Modelling Language

The Unified Modelling Language (UML) is a graphical language for visualizing, specifying, constructing and documenting the artifacts of software-intensive systems.

The UML was originally derived from the object modelling languages of three leading object-oriented methods: Booch, Object Modelling Technique (OMT) and Object-Oriented Software Engineering (OOSE). It was first added to the list of Object Management Group (OMG) adopted technologies in 1997, and has since become the industry standard for modelling software-intensive systems.

Software Modelling Services

Static Modelling

Design Modelling

Use-Case Modelling

State Machine Modelling

Activity Modelling

Interaction Modelling

Deployment Modelling

Model Management

Profile Models

Managing the UML Modelling Environment


Software Modelling:

The UML Resource Page



Software Modelling

Unified Modelling Language

The Unified Modelling Language (UML) is the standard notation for modelling software-intensive systems.

The Unified Modelling Language is used to support software development by modelling requirements, software architectures, implementations and existing systems. UML is used by developers, architects, project managers, system engineers, programmers, analysts, contracting officers, customers and anyone who needs to specify, design, build, or understand software systems.


Example of Static Modelling: Entity-Relationship-Diagram

Intellia Ltd - Stock and Debtors ERD.jpg

Diagram above: Entity-Relationship Diagram is an example of a "Static Model" for accounting software, in this case a prototype for a stock, debtors and shipment database.


Applications of Modelling Languages

Various kinds of modelling languages are applied in different disciplines, including computer science, information management, business process modelling, software engineering, and systems engineering.

Modelling languages can be used to specify system requirements, structures and behaviors. Modelling languages are intended to be used to precisely specify systems so that stakeholders (e.g., customers, operators, analysts, designers) can better understand the system being modeled.

The more mature modelling languages are precise, consistent and executable.

Informal diagramming techniques applied with drawing tools are expected to produce useful pictorial representations of system requirements, structures and behaviors, but not much else.

Executable modelling languages applied with proper tool support, however, are expected to automate system verification, validation, simulation and code generation from the same representations.