Issue 8450: Default values for ValueSpecification are not specified properly (uml2-rtf)
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity: 
Summary: There are a few cases when the default is documented as a ValueExpression, as follows: 
-        JoinNode.joinSpec = {default value is" and"} 
-        ActivityEdge.guard= {default value is "true"} 

These defaults are currently just plain text in the Rose Model displayed under the ValueSpecification as shown in figure 185 in the superstructure specification. 

They should be included formally in the model. However it is not clear that the UML2 notation text allows defaults for association ends, and that those defaults can include expressions that construct instances of classes such as ValueSpecification. For example, the notation for ActivityEdge::guard in figure 185 could be: 

        +guard = LiteralBoolean(true) 

The default value for guard is set to a newly constructed LiteralBoolean (a ValueSpecification) with value true. 

Recommendation: 

Ensure the text notation for default values includes the ability to construct InstanceSpecifications, and that the notation supports defaults for properties on association ends. 


Resolution: 
Revised Text: 
Actions taken:
March 4, 2005: received issue
February 20, 2015: closed issue
Discussion: 
Discussion
This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
Disposition: Closed - No Change
End of Annotations:=====
ource: Pete Rivett, IBM Software 

Summary: 

There are a few cases when the default is documented as a ValueExpression, as follows: 
-        JoinNode.joinSpec = {default value is" and"} 
-        ActivityEdge.guard= {default value is "true"} 

These defaults are currently just plain text in the Rose Model displayed under the ValueSpecification as shown in figure 185 in the superstructure specification. 

They should be included formally in the model. However it is not clear that the UML2 notation text allows defaults for association ends, and that those defaults can include expressions that construct instances of classes such as ValueSpecification. For example, the notation for ActivityEdge::guard in figure 185 could be: 

        +guard = LiteralBoolean(true) 

The default value for guard is set to a newly constructed LiteralBoolean (a ValueSpecification) with value true. 

Recommendation: 

Ensure the text notation for default values includes the ability to construct InstanceSpecifications, and that the notation supports defaults for properties on association ends.