Eclipse Community Forums: Tigerstripe » Class Diagram problems

Help

Home

Home » Archived » Tigerstripe » Class Diagram problems

Show: Today's Messages :: Show Polls :: Message Navigator

Class Diagram problems [message #6462]

Fri, 07 March 2008 12:30

Marc FLAUW

Messages: 151
Registered: July 2009

Senior Member

Hello,

Using TS 2.2.4, on a brand new model. I have created a few classes and I
want to display them in a class diagram, but the class diagram only
displays 1 attribute.

This was also the case in the past, using previous version of TS.

Any idea of what can I do to have all the attributes show up.

Thanks,

Marc

Report message to a moderator

Re: Class Diagram problems [message #6521 is a reply to message #6462]

Fri, 07 March 2008 22:41

Eric Dillon

Messages: 103
Registered: July 2009

Senior Member

Hi Marc,

no. We are using this version in production here at Cisco, and never ran
into this.
Is there anything weird the Error Log?

Eric
"Marc Flauw" <marc.flauw@hp.com> wrote in message
news:565848096841cbaaf8dbe96ed2fb6da3$1@www.eclipse.org...
> Hello,
> Using TS 2.2.4, on a brand new model. I have created a few classes and I
> want to display them in a class diagram, but the class diagram only
> displays 1 attribute.
> This was also the case in the past, using previous version of TS.
>
> Any idea of what can I do to have all the attributes show up.
>
> Thanks,
>
> Marc
>
>
>

Report message to a moderator

Re: Class Diagram problems [message #6538 is a reply to message #6521]

Mon, 10 March 2008 10:08

Marc FLAUW

Messages: 151
Registered: July 2009

Senior Member

Eric,

I will send you the logs.

Best regards,

Marc

Report message to a moderator

Re: Class Diagram problems [message #6575 is a reply to message #6538]

Tue, 11 March 2008 01:24

Eric Dillon

Messages: 103
Registered: July 2009

Senior Member

Ok, so here's what I think is going on...

Tigerstripe out of the box is configured to draw "references" on diagrams,
which means that any attribute of non primitive type is going to be drawn as
an "arrow towards that type on a Class Diagram". This is consistent with the
"legacy" conventions from OSSJ. However, what this means is that:
- it is different from proper UML behavior
- if the corresponding type is NOT on the diagram... the attribute will
simply not appear in the "box".

This behavior can be controled through a Tigerstripe profile, which will
allow you to fine-tune the behavior and turn it back to the usual UML Class
diagram behavior.

To do that:
- File->New->Other... Select Tigerstripe/Tigerstripe profile. You might want
to call this "tip.wbp" as I suspect a "TIP" TS profile will make sense in
the long run.
- On the second tab ("General") you will see some of the "tweaks" that are
available. Uncheck the very first one on the left column ("Artifact
attributes can be used as References").
- make sure you save the profile (CTRL-S)
- then go back to the "Overview" tab and click on the link "Save as Active
profile and reload".

This will active the "tip.wbp" profile as your local profile. At this stage
you should be able to re-open your diagrams and see a change.
For more details about Tigerstripe profiles, check out the Help->Help
Contents->Tigerstripe Workbench 2.0->Tasks->Creating and Using Profiles.

Hope this helps,
Eric

"Marc Flauw" <marc.flauw@hp.com> wrote in message
news:57d094aff9be136366d846ea08258b97$1@www.eclipse.org...
> Eric,
>
> I will send you the logs.
> Best regards,
>
> Marc
>

Report message to a moderator

Re: Class Diagram problems [message #6594 is a reply to message #6575]

Tue, 11 March 2008 08:04

Marc FLAUW

Messages: 151
Registered: July 2009

Senior Member

Eric,

OK, I did that, but the results are surprising.

After loading the profile, I saw no change on the diagram. I had to delete
and recreate the object (Tracking Record).

Then all the attributes were showing up, but Tracking Record had 2
relationships with Service Problem, as Service Problem contains 2
attributes of type Tracking Record and those 2 relationships were gone. So
changing the profile is not perfect and not really what I want.

Best regards,

Marc

Report message to a moderator

Re: Class Diagram problems [message #6612 is a reply to message #6594]

Tue, 11 March 2008 11:01

Eric Dillon

Messages: 103
Registered: July 2009

Senior Member

See my comments inline.

Eric
"Marc Flauw" <marc.flauw@hp.com> wrote in message
news:80bb8c6e1bd2b6dcb8f50bccdd53c821$1@www.eclipse.org...
> Eric,
>
> OK, I did that, but the results are surprising.
> After loading the profile, I saw no change on the diagram. I had to delete
> and recreate the object (Tracking Record).
Ok. It seems we have a bug open on this.
> Then all the attributes were showing up, but Tracking Record had 2
> relationships with Service Problem, as Service Problem contains 2
> attributes of type Tracking Record and those 2 relationships were gone. So
> changing the profile is not perfect and not really what I want.
Well... this is the dilemna we have now with all OSSJ APIs. The
"relationships" that you are refering to are really "References", where they
should really be represented using proper Associations. We've brought that
up to the attention of Vincent and I believe it is important that this
modeling "convention" is straightened up going forward (especially setting
the context for TIP). I suggest setting up a call with Richard, Vincent,
maybe Jerome and others. I'll send you an email offline.
>
> Best regards,
>
> Marc
>

Report message to a moderator

Re: Class Diagram problems [message #6631 is a reply to message #6612]

Tue, 11 March 2008 14:28

Marc FLAUW

Messages: 151
Registered: July 2009

Senior Member

Eric,

I am a bit confused.
Let's take an example:
today, in my service problem, I have an attribute affectedServices
pointing to the entity Service (0..*) by key.

So now, I create an Association artefact that I call AffectedServices (it
is no longer starting by a non cap letter) that points to service and to
service problem. How do I indicate that affectedServices should be
attached to Service Problem?

Thanks,

Marc

Report message to a moderator