Issue 18779: VirtualCall is missing an Addresses (kdm-rtf) Source: Benchmark Consulting (Dr. Stephane Vaucher, ) Nature: Clarification Severity: Significant Summary: Virtual calls should have an Addresses to indicate what is the object that is being passed a message. Currently, the only action relations that are required describe the parameters and the next control flow. IMO, a VirtualCall should match a PtrCall that requires a "Addresses relationship to the DataElement that represents the pointer". In the case of the Virtual call, it should probably read "Addresses relationship to the DataElement that represents the object", and perhaps specify that the DataElement should be of ClassUnit type. Resolution: Revised Text: Actions taken: June 14, 2013: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 14 Jun 2013 12:45:33 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Stephane Vaucher Employer: Benchmark Consulting mailFrom: svaucher@benchmarkcanada.com Terms_Agreement: I agree Specification: Architecture-Driven Modernization (ADM): Knowledge Discovery Meta-Model (KDM) Section: Annex A.4 FormalNumber: ptc/2010-12-12 Version: 1.3 Doc_Year: Year Doc_Month: Month Doc_Day: Day Page: 317 Title: VirtualCall is missing an Addresses Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Remote Name: modemcable.benchmarkcanada.com Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36 Time: 12:45 PM Description: Virtual calls should have an Addresses to indicate what is the object that is being passed a message. Currently, the only action relations that are required describe the parameters and the next control flow. IMO, a VirtualCall should match a PtrCall that requires a "Addresses relationship to the DataElement that represents the pointer". In the case of the Virtual call, it should probably read "Addresses relationship to the DataElement that represents the object", and perhaps specify that the DataElement should be of ClassUnit type.