Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Unified Modeling Language
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== History == [[File:OO Modeling languages history.jpg|thumb|320px|History of object-oriented methods and notation]] === Before UML 1.0 === UML has evolved since the second half of the 1990s and has its roots in the [[object-oriented programming]] methods developed in the late 1980s and early 1990s. The timeline (see image) shows the highlights of the history of object-oriented modeling methods and notation. It is originally based on the notations of the [[Booch method]], the [[object-modeling technique]] (OMT), and [[object-oriented software engineering]] (OOSE), which it has integrated into a single language.<ref name=":0" /> [[Rational Software Corporation]] hired [[James Rumbaugh]] from [[General Electric]] in 1994 and after that, the company became the source for two of the most popular object-oriented modeling approaches of the day:<ref>Andreas Zendler (1997) ''Advanced Concepts, Life Cycle Models and Tools for Objeckt-Oriented Software Development''. p. 122</ref> Rumbaugh's [[object-modeling technique]] (OMT) and [[Grady Booch]]'s method. They were soon assisted in their efforts by [[Ivar Jacobson]], the creator of the [[object-oriented software engineering]] (OOSE) method, who joined them at Rational in 1995.<ref name=":1">{{cite book | title = Unified Modeling Language User Guide, The | publisher = Addison-Wesley | edition = 2 | year = 2005 | page = 496 | url = http://www.informit.com/store/unified-modeling-language-user-guide-9780321267979 | isbn = 0321267974 }} See the sample content: look for history</ref> === UML 1.x === Under the technical leadership of those three (Rumbaugh, Jacobson, and Booch), a consortium called the [[UML Partners]] was organized in 1996 to complete the ''Unified Modeling Language (UML)'' specification and propose it to the Object Management Group (OMG) for standardization. The partnership also contained additional interested parties (for example [[Hewlett-Packard|HP]], [[Digital Equipment Corporation|DEC]], [[IBM]], and [[Microsoft]]). The UML Partners' UML 1.0 draft was proposed to the OMG in January 1997 by the consortium. During the same month, the UML Partners formed a group, designed to define the exact meaning of language constructs, chaired by [[Cris Kobryn]] and administered by Ed Eykholt, to finalize the specification and integrate it with other standardization efforts. The result of this work, UML 1.1, was submitted to the OMG in August 1997 and adopted by the OMG in November 1997.<ref name=":1" /><ref>{{cite web|url=http://www.omg.org/cgi-bin/doc?ad/97-08-11 |title=UML Specification version 1.1 (OMG document ad/97-08-11) |publisher=Omg.org |access-date=2011-09-22}}</ref> After the first release, a task force was formed<ref name=":1" /> to improve the language, which released several minor revisions, 1.3, 1.4, and 1.5.<ref>{{cite web|url=http://www.omg.org/spec/UML/ |title=UML |publisher=Omg.org |access-date=2014-04-10}}</ref> The standards it produced (as well as the original standard) have been noted as being ambiguous and inconsistent.<ref>Génova et alia 2004 "Open Issues in Industrial Use Case Modeling"</ref> ==== Cardinality notation ==== As with database Chen, Bachman, and ISO [[ER diagram]]s, class models are specified to use "look-across" [[Cardinality (data modeling)|cardinalities]], even though several authors ([[Merise]],<ref>Hubert Tardieu, Arnold Rochfeld and René Colletti La methode MERISE: Principes et outils (Paperback - 1983)</ref> Elmasri & Navathe,<ref>Elmasri, Ramez, B. Shamkant, Navathe, Fundamentals of Database Systems, third ed., Addison-Wesley, Menlo Park, CA, USA, 2000.</ref> amongst others<ref>{{cite book |title=Conceptual Modeling – ER 2004: 23rd International Conference on Conceptual Modeling, Shanghai, China, November 8–12, 2004 |publisher=[[Springer Publishing|Springer]] |date=October 27, 2004 |series=[[Lecture Notes in Computer Science]] 3288 |edition=2004 |isbn=3540237232 |editor1=Paolo Atzeni |editor2=Wesley Chu |editor3=Hongjun Lu |editor4=Shuigeng Zhou |editor5=Tok Wang Ling }}</ref>) prefer same-side or "look-here" for roles and both minimum and maximum cardinalities. Recent researchers (Feinerer<ref>{{cite thesis |author=Ingo Feinerer |title=A Formal Treatment of UML Class Diagrams as an Efficient Method for Configuration Management |url=https://publik.tuwien.ac.at/files/pub-inf_4582.pdf |date=March 2007 |location=Vienna |degree=Doctor of Technical Sciences |publisher=Technical University of Vienna}}</ref> and Dullea et al.<ref>{{cite journal |journal=Data & Knowledge Engineering |volume=47 |issue=2 |title=An analysis of structural validity in entity-relationship modeling |author1=James Dullea |author2=Il-Yeol Song |author3=Ioanna Lamprou |date=November 1, 2003 |pages=167–205 |doi=10.1016/S0169-023X(03)00049-1}}</ref>) have shown that the "look-across" technique used by UML and ER diagrams is less effective and less coherent when applied to ''n''-ary relationships of order strictly greater than 2. Feinerer says: "Problems arise if we operate under the look-across semantics as used for UML associations. Hartmann<ref>{{cite conference |conference=ADC '03: Proceedings of the 14th Australasian database conference |author=Sven Hartmann |publisher=[[Australian Computer Society]] |url=https://dl.acm.org/doi/abs/10.5555/820085.820110 |title=Reasoning about participation constraints and Chen's constraints |date=January 17, 2003 |pages=105–113}} {{open access}}</ref> investigates this situation and shows how and why different transformations fail.", and: "As we will see on the next few pages, the look-across interpretation introduces several difficulties which prevent the extension of simple mechanisms from binary to ''n''-ary associations." === UML 2 === UML 2.0 major revision replaced version 1.5 in 2005, which was developed with an enlarged consortium to improve the language further to reflect new experiences on the usage of its features.<ref>{{cite web|url=http://www.omg.org/spec/UML/2.0/ |title=UML 2.0 |publisher=Omg.org |access-date=2011-09-22}}</ref> Although UML 2.1 was never released as a formal specification, versions 2.1.1 and 2.1.2 appeared in 2007, followed by UML 2.2 in February 2009. UML 2.3 was formally released in May 2010.<ref name="spec">{{cite web|url=http://www.omg.org/spec/UML/ |title=UML |publisher=Omg.org |access-date=2011-09-22}}</ref> UML 2.4.1 was formally released in August 2011.<ref name="spec" /> UML 2.5 was released in October 2012 as an "In progress" version and was officially released in June 2015.<ref name="spec" /> The formal version 2.5.1 was adopted in December 2017.<ref name="OMG" /> There are four parts to the UML 2.x specification: * The Superstructure that defines the notation and semantics for diagrams and their model elements * The Infrastructure that defines the core metamodel on which the Superstructure is based * The [[Object Constraint Language]] (OCL) for defining rules for model elements * The UML Diagram Interchange that defines how UML 2 diagram layouts are exchanged Until UML 2.4.1, the latest versions of these standards were:<ref name="Versions2.4.1">{{cite web|author=OMG|title=OMG Formal Specifications (Modeling and Metadata paragraph)|url=http://www.omg.org/spec/#M&M|access-date = 2016-02-12}}</ref> * UML Superstructure version 2.4.1 * UML Infrastructure version 2.4.1 * OCL version 2.3.1 * UML Diagram Interchange version 1.0. Since version 2.5, the UML Specification has been simplified (without Superstructure and Infrastructure), and the latest versions of these standards are now:<ref name="LatestVersions">{{cite web|author=OMG|title=about the unified modeling language specification|url=https://www.omg.org/spec/UML/About-UML/|access-date = 2020-02-22}}</ref> * UML Specification 2.5.1 * OCL version 2.4 It continues to be updated and improved by the revision task force, who resolve any issues with the language.<ref>{{cite web |title=Issues for UML 2.6 Revision task Force mailing list |url=https://issues.omg.org/issues/lists/uml2-rtf |access-date=2014-04-10 |publisher=Omg.org}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)