Book a Demo

Author Topic: Redefined Property vs Inherited Features  (Read 9825 times)

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Redefined Property vs Inherited Features
« on: September 07, 2017, 01:26:28 am »
Hi all,


Let's say I create two classes, both with some attributes, and a Generalization between them. In the more specific class, I can specify that an attribute is a "redefined property", and select an attribute from the more general class that the more specific attribute redefines.

If I then open the Feature and Compartment Visibility dialog for the more specific class and select Inherited Features -- Show Attributes, I would expect the property I have redefined not to show up. It's been redefined, after all. But it does show up.

Am I misunderstanding the "redefine property" feature?


/Uffe
My theories are always correct, just apply them to the right reality.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Redefined Property vs Inherited Features
« Reply #1 on: September 07, 2017, 03:56:24 am »
I'd say no. The redefined attribute replaces the inherited one. The latter is only visible by indirecting to the super class. So you should report that as defect.

q.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Redefined Property vs Inherited Features
« Reply #2 on: September 07, 2017, 09:54:12 am »
I'd say no. The redefined attribute replaces the inherited one. The latter is only visible by indirecting to the super class. So you should report that as defect.

q.
If you've ever read Object Oriented Software Construction, you'll see there's a LOT of missing functionality in the inheritance mechanism.  Some of it can be from UML itself, and some due to the implementation mechanism used by Sparx.

Over the years, I've come to the conclusion that the inheritance mechanism should be attached to the relationship and not the end point.  But that isn't going to change before Armageddon.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Glassboy

  • EA Practitioner
  • ***
  • Posts: 1367
  • Karma: +112/-75
    • View Profile
Re: Redefined Property vs Inherited Features
« Reply #3 on: September 07, 2017, 11:04:25 am »
Over the years, I've come to the conclusion that the inheritance mechanism should be attached to the relationship and not the end point.  But that isn't going to change before Armageddon.

The next Armageddon in the 20-23th October in Auckland.  I suggest it will take longer than that.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Redefined Property vs Inherited Features
« Reply #4 on: September 07, 2017, 05:21:38 pm »
Over the years, I've come to the conclusion that the inheritance mechanism should be attached to the relationship and not the end point.  But that isn't going to change before Armageddon.

The next Armageddon in the 20-23th October in Auckland.  I suggest it will take longer than that.
I implied the semi-open interval:  [Not before Armageddon..After Armageddon)  My statement is, therefore, unaltered!  :P

Paolo (It may be Friday in Auckland, by now)
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Glassboy

  • EA Practitioner
  • ***
  • Posts: 1367
  • Karma: +112/-75
    • View Profile
Re: Redefined Property vs Inherited Features
« Reply #5 on: September 08, 2017, 11:43:52 am »
Paolo (It may be Friday in Auckland, by now)

I'm not even sure it's the same reality in Auckland :-)