Issue 19322: Rename Specialization/Generalization between abstract classes (uml2-rtf) Source: (, ) Nature: Enhancement Severity: Critical Summary: Inheritance between an abstract and a solid class should not be named Inheritance (or specialization or generalization). Reason: If abstract classes do not have filled in methods, the concrete class just implements them, not extend. Therefore inheritance between concrete class and an abstract class is really an implementation. But implementation is used for interfaces. Therefore we need different name to describe the relationship between abstract class and concrete class. Resolution: Revised Text: Actions taken: March 31, 2014: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 31 Mar 2014 04:34:41 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Bernard Szlachta Employer: NobleProg Ltd mailFrom: bernard.szlachta@nobleprog.co.uk Terms_Agreement: I agree Specification: UML 2.5 Section: Inheritance FormalNumber: various Version: beta2 Doc_Year: 2013 Doc_Month: September Doc_Day: 05 Page: various Title: Rename Specialization/Generalization between abstract classes Nature: Enhancement Severity: Critical CODE: 3TMw8 B1: Report Issue Remote Name: host90-152-2-38.ipv4.regusnet.com Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.154 Safari/537.36 Time: 04:34 AM Description: Inheritance between an abstract and a solid class should not be named Inheritance (or specialization or generalization). Reason: If abstract classes do not have filled in methods, the concrete class just implements them, not extend. Therefore inheritance between concrete class and an abstract class is really an implementation. But implementation is used for interfaces. Therefore we need different name to describe the relationship between abstract class and concrete class.