Unified Modeling Language
software system design modeling tool
The Unified Modeling Language (UML) is a general-purpose, object-oriented, visual modeling language that provides a way to visualize the architecture and design of a system, similar to the function of a blueprint. UML defines notation for 14 types of diagrams which focus on aspects such as behavior, interaction, and structure.
The UML has a metamodel defined by the OMG UML specification. The metamodel defines the elements in an object-oriented model such as classes and properties. It is essentially the same thing as the metamodel in object-oriented programming (OOP), however for OOP, the metamodel is primarily used at run time to dynamically inspect and modify an application object model. The UML metamodel provides a mathematical, formal foundation for the graphic views used in the modeling language to describe an emerging system.
UML was created in an attempt to define a standard language for object-oriented programming at the OOPSLA '95 Conference. Originally, Grady Booch and James Rumbaugh merged their models into a unified model. This was followed by Booch's company Rational Software purchasing Ivar Jacobson's Objectory company and merging their model into the UML. At the time Rational and Objectory were two of the dominant players in the small world of independent vendors of object-oriented tools and methods. The Object Management Group (OMG) then took ownership of UML.
The creation of UML was motivated by the desire to standardize the disparate nature of notational systems and approaches to software design at the time.
The public source identifies “Unified Modeling Language” as software system design modeling tool. This brief keeps that definition visible, then builds a research path around Unified, Modeling and Language.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Unified Modeling Language”, the useful work is to connect “software system design modeling tool” to the records capable of establishing context and consequence.
The date and method of observation matter as much as the stated conclusion, especially where classification or consensus has changed. The source revision retrieved here is dated Aug 20, 2026. The linked authority identifier is Q169411. The Library of Congress control number is sh97003561. 2 of 3 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank.
Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Unified Modeling Language”, its source revision and the description used here.
- Expand the search: follow Unified Modeling Language primary sources, Unified Modeling Language archive and Unified research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Unified Modeling Language”?
- Which observation, specimen, dataset or publication supports the account?
- Has classification or technical consensus changed since the cited source?
Search terms from this dossier
This entry incorporates text from “Unified Modeling Language” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.