Issue 9167: "set" operation for derived attributes                                                                                                                                                                  (mof2idl-ftf)
Source: Fraunhofer FOKUS (Mr. Michael Soden, soden@ikv.de soden@fokus.fraunhofer.de)
Nature: Uncategorized Issue
Severity: 
Summary: This issue is a follow up of issue 7591. For UML2 compliance, a "set" operation is needed for derived attributes.
Resolution: 
Revised Text: Resolution:
For derived attributes, add the "set" operation to Rule(11) .
Changes in the document:
Rule (15) was changed from
For an attribute with multiplicity upper>1, two operations to set and get the attribute value are declared - taking into account Rule (2), Rule (3) and Rule (11).
to
For an attribute with multiplicity [1..1], two operations to set and get the attributes value are declared - taking into account Rule (11). For optional attributes with a multiplicity of [0..1], an additional operation to unset the attribute is declared..

Actions taken:
November 15, 2005: received issue
March 8, 2006: closed issue
Discussion: 

End of Annotations:=====
MG Issue No: [Temp20]
Title:	.set. operation for derived attributes
Source:
Michael Soden, soden@ikv.de	
Summary:
This issue is a follow up of issue 7591. For UML2 compliance, a .set. operation is needed for derived attributes.
 
Discussion:

Resolution:
For derived attributes, add the .set. operation to Rule(11) .
Changes in the document:
Rule (15) was changed from
For an attribute with multiplicity upper>1, two operations to set and get the attribute value are declared - taking into account Rule (2), Rule (3) and Rule (11).
to
For an attribute with multiplicity [1..1], two operations to set and get the attributes value are declared - taking into account Rule (11). For optional attributes with a multiplicity of [0..1], an additional operation to unset the attribute is declared..

Disposition:	open