← Back to team overview

oship-dev team mailing list archive

Re: Inheritance of classes

 

Hi Eduardo,

First of this specification is not fully defined.

On Sat, 2009-12-12 at 14:17 -0200, Eduardo César wrote:
> Hi all,
> 
> Tim, in the specfication of the ehr extract information model, some
> classes do not have a super class discrimined. I had put those classes
> subclassing "object", but I don't know if it is the best approach. Any
> tips?

In your example that would be correct.  Since these classes are used to
construct attribute values for higher order classes.  They cannot exist
at the top of a tree.

> Also, on the Syncextract Package of the Ehr Extract IM wants a class
> of the Message Package that is not there.
> Perhaps should I change the message package? Or should I change the
> ehr extract package? Some more tips? :)

I assume you are referring to the UML saying that SyncExtract should
inherit from MESSAGE_CONTENT?  But there is no such class.  This is
probably a typo and should be change to the MESSAGE class.  IF you read
the description in the MESSAGE class then it clearly is the 'content'
carrier.  I usually err on the side of the UML but in this case I
believe the text (table) makes more sense.

Nice work.........


--Tim


-- 
***************************************************************
Timothy Cook, MSc

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == (upon request)
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or    
from this link http://timothywayne.cook.googlepages.com/home 

Attachment: signature.asc
Description: This is a digitally signed message part


References