Issue 18725: The <<Property>> stereotype and its properties (updm-2-0-rtf)
Source: PTC (Mr. Simon Moore, simoore(at)ptc.com)
Nature: Revision
Severity: Significant
Summary: UPDM includes a <<Property>> stereotype with properties maxValue, minValue and defaultValue. <<CapabilityProperty>> specializes the Property stereotype and extends the Property metatype.


1. could you rename the Property stereotype to avoid confusion with the UML metatype of the same name?


2. since the UML metatype Property already has a defaultValue, could the UPDM one be removed?


3. the min/max/defaultValue properties have no multiplicity specified in the spec or XMI, so it defaults to 1. If these were intended to be optional they should be specified as [0..1]

These impact XMI (see MIWG TC22).
Resolution: 
Revised Text: 
Actions taken:
May 20, 2013: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 20 May 2013 11:19:19 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Simon Moore
Employer:        Atego
mailFrom:        simon.moore@atego.com
Terms_Agreement: I agree
Specification:   UPDM
Section:         8.2.1.1.2.5.7
FormalNumber:    2013-01-01
Version:         2.0.1
Doc_Year:        2013
Doc_Month:       January
Doc_Day:         01
Page:            52
Title:           The <<Property>> stereotype and its properties
Nature:          Revision
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue
Remote Name:     mail4.atego.com
Remote User:     
HTTP User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0)
Time:            11:19 AM


Description:


UPDM includes a <<Property>> stereotype with properties maxValue, minValue and defaultValue. <<CapabilityProperty>> specializes the Property stereotype and extends the Property metatype.


1. could you rename the Property stereotype to avoid confusion with the UML metatype of the same name?


2. since the UML metatype Property already has a defaultValue, could the UPDM one be removed?


3. the min/max/defaultValue properties have no multiplicity specified in the spec or XMI, so it defaults to 1. If these were intended to be optional they should be specified as [0..1]

These impact XMI (see MIWG TC22).