-
Key: UML25-358
-
Legacy Issue Number: 17965
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
in the spec, emergent is a special term with its own definition (not exactly the term as used outside the specification)
The different format of the term should be made conforming.
1) emergent behavior as in 13.1
vs
2) emergent behavior as in 13.2.3 (2x), 13.4, or 18.1.1
vs
3) Emergent Behavior as in 17.1.4It should certainly be in the index.
-
Reported: UML 2.4.1 — Thu, 27 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
The uses of “emergent behavior” in 13.2.3, 13.4 and 18.1.1 are consistent with its definition in 13.1. And
there is no index as such in which the term could be concluded.
The only remaining issue is 17.1.4, which uses “Emergent Behavior”, as well as a number of other terms, in
a capitalized form. These seem to be left over references to the “Execution model” that is supposedly to be
found in Clause 13, but which is no longer there in the UML 2.5 specification. Subclause 17.1.4 is really no
longer applicable -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Location 13.1 Summary p 305 - Use of the word “emergent”
- Key: UML25-358
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF