Issues for Mailing list of the IT Portfolio Management Finalization Task Force

To comment on any of these issues, send email to itpmf-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 7921: Linkage package should use MOF::Element instead of RefObject
Issue 7922: 2. 7.2.2, property 'origin'
Issue 7923: . In Section 8.3.2
Issue 8958: HardwareInstance Class

Issue 7921: Linkage package should use MOF::Element instead of RefObject (itpmf-ftf)

Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary:
Linkage package should use MOF::Element instead of RefObject

Resolution: see above
Revised Text:
Actions taken:
November 17, 2004: received issue
October 30, 2006: closed issue

Discussion:
Replace 'RefObject' by 'Reflective::Element' in the following places:
·	In the second paragraph of 7.2, in the clause "This package imports the class RefObject,"
·	In the diagram in Section 7.2, Linkage Package
·	Section 7.2.1.2 first line "RefObject origin [1]"
·	Section 7.2.5.1 first line referenceObject RefObject


Issue 7922: 2. 7.2.2, property 'origin' (itpmf-ftf)

Click
here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary:
2. 7.2.2, property 'origin': there is an extraneous line "The system
used to resolve the link." which should be deleted

Resolution: see above
Revised Text:
Actions taken:
November 17, 2004: received issue
October 30, 2006: closed issue

Discussion:
The section numbering has changed in the Final Adopted Spec after the issue was raised.
In section 7.2.1.2 remove the following line:
"The system used to resolve the link."


Issue 7923: . In Section 8.3.2 (itpmf-ftf)

Click
here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary:
3. In Section 8.3.2 has no type declared for the 'body' property of
Agreement: it should be String

Resolution:
Revised Text:
Actions taken:
November 17, 2004: received issue
October 30, 2006: closed issue

Discussion:
The section numbering has changed in the Final Adopted Spec after the issue was raised.
In Section 7.3.2 replace the line:
	body
With the line
	String body


Issue 8958: HardwareInstance Class (itpmf-ftf)

Click
here for this issue's archive.
Source: Deere & Company (Mr. David C. Smith, smithdavec(at)johndeere.com)
Nature: Uncategorized Issue
Severity:
Summary:
Please explain why there is a HardwareInstance Class.  I see it on the 'Essential' Diagram 8.3.1.4 and Deployment Diagram 8.3.1.3.  I expected to find PlatformElement at these points in the model.


Resolution: close, no change
Revised Text:
Actions taken:
August 9, 2005: received issue
October 30, 2006: closed issue

Discussion:
PlatformElement is at the 'type' level for example 'Departmental Server' or "Dell Model 242". HardwareInstance as its name suggests is a specific instance - for example "Dell Model 242 with serial number 123456". An actual deployment will therefore be related to a HardwareInstance. The relationship bwtween these is that of Deployment (i.e. the Dell Model 242 with serial number 123456 is a deployment of Dell Model 242. 
Section 7.3.12 explains this thus "HardwareInstance itself inherits from Deployment - indicating that each item of hardware is the deployment of the PlatformElement representing the Model of server."