-
Key: UMLR-560
-
Legacy Issue Number: 17939
-
Status: open
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
Why
An interface should be allowed to have not public proprieties/attributes. These are necessary to have them referred to in the protocol state machine, but they need not be public attributes, i.e., no direct or query-based access to their values from he outside. They need to be there to allow for a consistent description of the state-based behavior. -
Reported: UML 2.4.1 — Thu, 27 Sep 2012 04:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
UMLR — Location: Constraints p 193 - All feturs must be public?
- Key: UMLR-560
- OMG Task Force: UML 2.6 RTF