[Issue 6437] New - concurrency: unspecified

http://argouml.tigris.org/issues/show_bug.cgi?id=6437
                 Issue #|6437
                 Summary|concurrency: unspecified
               Component|argouml
                 Version|0.34
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P3
            Subcomponent|Model
             Assigned to|bobtarling
             Reported by|yurikhan






------- Additional comments from [email protected] Mon Jul 16 23:24:38 -0700 2012 -------
Currently, ArgoUML insists that each and every class operation state its
concurrency — sequential, guarded or concurrent, and displays it as a property
string (e.g. foo() {sequential}). This unnecessarily clutters the diagram if
property strings are displayed; if I hide them, I lose important information in
other properties (e.g. {query}).

I suggest that it should be possible to suppress the display of concurrency
independently of the master property switch.

OMG UML 1.5 says:

> In the absence of a specification, the concurrency semantics are unspecified
and must therefore be assumed to be sequential in the worst case.

i.e. they explicitly allow the case of unspecified concurrency.

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=2990914

To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.