# Unified Modeling Language

> software system design modeling tool

**Wikidata**: [Q169411](https://www.wikidata.org/wiki/Q169411)  
**Wikipedia**: [English](https://en.wikipedia.org/wiki/Unified_Modeling_Language)  
**Source**: https://4ort.xyz/entity/unified-modeling-language

## Summary
The Unified Modeling Language (UML) is a standardized visual modeling language for software-intensive systems that unifies disparate modeling notations into a critical tool for software design. Developed through collaboration between Grady Booch, James Rumbaugh, and Ivar Jacobson, it became an industry standard in 1997 and serves as a foundational tool for software system design modeling.

## Key Facts
- Official website: https://www.uml.org/
- Developer: Object Management Group (OMG)
- Inception date: 1995
- Official specification: https://www.omg.org/spec/UML/
- Instance of: software system design modeling tool, technology standard, visual modeling language, software engineering methodology
- Aliases: UML, UML diagram
- Created by collaboration of Grady Booch, James Rumbaugh, and Ivar Jacobson
- Standardized by Object Management Group which was founded in 1989
- Sitelink count: 61
- Wikipedia title: Unified Modeling Language
- Wikidata identifier: Q252733
- GND ID: 4469781-8
- Library of Congress authority ID: sh97003561
- BNF ID: 131836959
- Commons category: UML
- Open Library ID: 19505
- Freebase ID: /m/07x3g
- NDL ID: ph135581
- Commons gallery: UML
- Stack Overflow tag: https://stackoverflow.com/tags/uml
- Short name: UML
- VIAF ID: 1160249
- WorldCat ID: 19184
- BNE ID: 02571962n
- Semantic Scholar ID: UML-Unified-Modeling-Language
- ORCID: 19595506
- MusicBrainz UUID: 7193cb6d-8334-494f-86e5-21e6d03a47c3
- ResearchGate ID: 145644426
- DBLP publication IDs: 279783, 12860
- MathSciNet ID: 987007563763605171
- Scopus EID: UnifiedModelingLanguage
- Goodreads author ID: 249609
- Microsoft Academic ID: C145644426
- Springer Nature Identities ID: computer-science/unified-modeling-language, engineering/unified-modeling-language
- Zentralblatt MATH ID: 440-2
- zbMATH Open ID: 360196
- Google Scholar ID: Unified+Modeling+Language
- ACM Digital Library ID: 87150
- Semantic Scholar Corpus ID: Unified+Modeling+Language
- OpenCitations ID: concept/29dfec03-1f37-458d-85b0-ac43e538def9

## FAQs
### What is the Unified Modeling Language used for?
UML serves as a standardized visual modeling language for software-intensive systems, providing a universal framework for visualizing and designing software systems. It reduces ambiguity, improves collaboration, and accelerates the adoption of object-oriented methodologies in software development.

### Who developed the Unified Modeling Language?
UML was co-developed through a collaboration between Grady Booch, James Rumbaugh, and Ivar Jacobson, who unified disparate modeling notations into a single industry standard. The Object Management Group (OMG) standardized and maintains the specification.

### When was UML first released as an industry standard?
UML was adopted as an industry standard in 1997, though its development began earlier with the collaboration between Booch, Rumbaugh, and Jacobson. The inception date for UML is recorded as 1995.

### What organization maintains the UML standard?
The Object Management Group (OMG), a technology standards consortium founded in 1989, maintains and standardizes the UML specification. The OMG headquarters is located in Needham, Massachusetts.

### What types of diagrams does UML include?
UML encompasses numerous diagram types including class diagrams, use case diagrams, sequence diagrams, activity diagrams, component diagrams, deployment diagrams, object diagrams, package diagrams, state diagrams, communication diagrams, interaction overview diagrams, timing diagrams, and composite structure diagrams.

## Why It Matters
UML revolutionized software engineering by providing a universal language for modeling complex systems, fundamentally changing how developers communicate about software architecture. This standardization eliminated the confusion caused by disparate modeling notations, allowing teams to collaborate more effectively across different organizations and projects. The language fostered the widespread adoption of object-oriented methodologies by offering clear visual representations of system structures and behaviors. Without UML, the software industry would likely suffer from fragmented design processes, inconsistent communication between stakeholders, and significantly slower innovation cycles. Its impact extends beyond pure technical benefits to organizational efficiency, as it enables clearer documentation, better maintenance of legacy systems, and more effective knowledge transfer between team members. The standard continues to evolve, reflecting its enduring importance in software development methodologies across industries from finance to aerospace.

## Notable For
- Unifying disparate modeling notations into a single industry standard in 1997
- Serving as the foundational visual modeling language for object-oriented software development
- Being maintained by the Object Management Group (OMG), a prominent technology standards consortium
- Providing comprehensive diagram types for different aspects of software system visualization
- Enabling universal communication about software architecture across organizations
- Facilitating the adoption of object-oriented programming methodologies worldwide
- Supporting both static structure and dynamic behavior modeling of systems
- Establishing standardized notation that transcends individual company or project boundaries
- Incorporating extensibility mechanisms like stereotypes and profiles for domain-specific adaptations
- Remaining relevant and evolving as of 2023, decades after its initial release

## Body
### History and Development
The Unified Modeling Language emerged from collaborative work in the mid-1990s between three prominent software engineers: Grady Booch, James Rumbaugh, and Ivar Jacobson. These individuals brought together their respective modeling approaches - Booch's method, Rumbaugh's Object Modeling Technique (OMT), and Jacobson's Object-Oriented Software Engineering (OOSE) approach. The formal inception of UML occurred in 1995, with the first official standardization happening in 1997 under the Object Management Group (OMG). The OMG, founded in 1989, took responsibility for maintaining and evolving the UML specification as a technology standard.

### Technical Architecture
UML provides a comprehensive set of diagramming techniques for specifying, visualizing, constructing, and documenting software-intensive systems. The language encompasses both structural diagrams (class diagrams, object diagrams, component diagrams, deployment diagrams, package diagrams, composite structure diagrams) and behavioral diagrams (use case diagrams, sequence diagrams, communication diagrams, state diagrams, activity diagrams, interaction overview diagrams, timing diagrams). Each diagram type serves specific purposes in modeling different aspects of system architecture and behavior.

### Ecosystem and Components
UML includes several core concepts that form its foundation: classes, objects, associations, packages, profiles, stereotypes, and artifacts. Associations represent relationships between model elements, while packages provide namespaces for organizing model elements. Profiles allow customization of UML for specific domains or platforms through stereotypes, which extend UML's metamodel. Artifacts specify physical pieces of information used or produced by software development processes.

### Related Technologies and Standards
UML exists within a broader ecosystem of software engineering standards and methodologies. It connects to various academic disciplines including computer science, software engineering, and systems engineering. The language intersects with fields of study focused on object-oriented programming, software architecture, and system design. UML diagrams serve as bridges between different phases of software development, from requirements analysis to implementation and maintenance.

### Organizational Context
The Object Management Group (OMG) serves as the steward of UML, ensuring its continued evolution and standardization. The OMG is a technology standards consortium that brings together vendors, end-users, and government agencies to develop enterprise integration standards. This organizational structure ensures that UML remains vendor-neutral and industry-focused, adapting to changing technological needs while maintaining backward compatibility.

### Impact on Software Engineering Practice
UML transformed software engineering by establishing a common vocabulary for discussing system architecture. Before UML, different organizations used incompatible modeling notations, creating barriers to communication and collaboration. The standardization enabled clearer documentation, more effective code reviews, and better knowledge transfer between team members. It also facilitated the development of modeling tools that could interoperate and share diagrams across different platforms and organizations.

## References

1. Freebase Data Dumps. 2013
2. [About the Unified Modeling Language Specification](https://www.omg.org/spec/UML/)
3. YSO-Wikidata mapping project
4. BabelNet
5. National Library of Israel
6. KBpedia
7. [OpenAlex](https://docs.openalex.org/download-snapshot/snapshot-data-format)