Issue 17772: Definition of invariant condition (uml25-ftf)
Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org)
Nature: Revision
Severity: Critical
Summary: This is not the normal interpretation of invariant conditions, and I believe it has no support in UML 2.4.1. The typical definition for invariant condition is that it must be true (it must hold) whenever it is checked, pre, post, and during. However, it need not hold while the object is not at a stable point and not query-able (not inspectable), but it must be true when and if the condition can be checked (by normal means). In an environment with multi-threading, this is often done with locks of some sort.
Resolution: 
Revised Text: 
Actions taken:
September 25, 2012: received issue
Discussion: 

End of Annotations:=====
s is issue # 17772

Problem: 6.050

Severity: Major
Type: Error
Location: 6.3.3 definition of invariant conditions  p 20
Title: Definition of invariant condition
Description:
This is not the normal interpretation of invariant conditions, and I believe it has no support in UML 2.4.1. The typical definition for invariant condition is that it must be true (it must hold) whenever it is checked, pre, post, and during. However, it need not hold while the object is not at a stable point and not query-able (not inspectable), but it must be true when and if the condition can be checked (by normal means). In an environment with multi-threading, this is often done with locks of some sort.
Source: Michael Jesse Chonoles