The unified modeling language reference manual

By J. Rumbaugh, I. Jacobson, G. Booch. 2010

5,460 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/18f910f755ac1ced2d8a644a50c7fdb200836b60

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

Giotto: a time-triggered language for embedded programming (2001, background): “This figure is a Unified Modeling Language (UML) deployment diagram [RJB99].”
CTTE: Support for Developing and Analyzing Task Models for Interactive System Design (2002, methodology): “Aimed at integrating the two approaches (task models represented in ConcurTaskTrees and UML), there can be various basic philosophies that are outlined below.”
Modeling software architectures in the Unified Modeling Language (2002, methodology): “For more extensive details, the reader is referred to standard texts on UML and OCL [Booch et al. 1998; Rumbaugh et al. 1998; Warmer and Kleppe 1998] and to the draft specification developed by the Object Management Group (OMG) [Object Management Group 2000].”
EDUTELLA: a P2P networking infrastructure based on RDF (2002, methodology): “The query interface that we propose includes a subset of UML [ 1 ].”
An overview of JML tools and applications (2003, background): “Despite the similarity in the acronyms, JML is very different in its aims fromUML [90].”
Multi-perspective enterprise modeling (MEMO) conceptual framework and modeling languages (2002, background): “In principle, general purpose modeling languages such as UML [21] or OML [3], allow for modeling a wide range of domains.”
Business Modelling Is Not Process Modelling (2000, methodology): “Sometimes, an e-business model is represented using a standard process modelling method such as the UML modelling language (activity diagrams) [11, 3], Petri Nets [13], IDEF0 [1], STRIM [9] or even (in many practitioner cases) ad-hoc diagrams with some notion of activity.”
The Embedded Systems Design Challenge (2006, methodology): “More recent modeling languages, such as UML [20] and AADL [10], attempt to be more generic in their choice of semantics and thus bring extensions in two directions: independence from a particular programming language; and emphasis on system architecture as a means to organize computation, communicat”
Design and development of multidevice user interfaces through multiple logical descriptions (2004, methodology): “The most common model-based approach in software engineering, UML [5], has paid very little attention to supporting the design of the interactive component of a software artefact.”
Matters of (Meta-) Modeling (2006, methodology): “Only a few non-UML elements are used for illustrative purposes.”
CoCoGUM: Contextual Code Summarization with Multi-Relational GNN on UMLs (2020, methodology): “The Unified Modeling Language (UML) [18, 19] has being widely accepted as a modeling notation for visualization during the design and development of software systems.”