Be Advised: Classified, FOUO, and PII Content is Not Permitted

  • Replies 6 replies
  • Subscribers 461 subscribers
  • Views 27222 views
  • Users 0 members are here
Related

How to show usage in an instance table?

Jeff Smallwood

Assumptions for this example:

Model has two classes: Car and Tire

Car has a property "Tires" of type Tire [1..*] (i.e. car has 1 or more instances of objects of type Tire)

Model has multiple instances of cars and tires.

 

I want to create an instance table (built in diagram type) that shows all the instances of type Tire and have one of the columns in that table be the instance of the car that uses each tire in its "Tires" property. Basically it would let me see all the tires and also see which cars use that tire (by "use" I don't mean the "usage" relationship, I mean use that tire instance as a value).

I have found how to add derived properties and can easily add columns for properties of objects that the tires own, but I can't find a way to go up the chain of composition.

The closest I have come to doing this is adding a new derived column under "simple navigation", select the "instance" criterion with "target to source" as the direction. The problem with doing that is the column returns the list of every class that the tire instance is used and doesn't let me filter by only objects of type Car. i.e. if a tire instance was also used as a property of another object, all the parent objects show up. I only want parent objects of a particular class (Car) that use that instance of the tire in the Instance table.

Seems like it should be easy but I'm obviously missing something...

Parents
  • Do you really mean instances or usages as type? I tend not to use instances since defining the classes/blocks and part properties has been enough for my work.

    The thing I think you want is a metachain of "typed element of type." You could also make a table of part properties with Name, Type, Owner, Multiplicity that may do what you want.
  • in reply to Michael Vinarcik
    I do mean instances. I appreciate what you mention, I've also built models where the class definitions were enough. In this case we are actually using instances (in object diagrams) to model how the execution manifests in the real world. Of course it isn't really cars & tires, that was just my analogous example, but it does capture what I'm trying to do. I played with the metachain and also thought that should work, but kept striking out finding a way to connect from the tire to the car. For example, picking "InstanceSpecification" on the metaclass and using the property of "Usage" or "_elementValueOfElement" or "_instanceValueOfInstance" doesn't produce any results. I'll admit I'm stabbing in the dark with how to use the metachain navigation though.
Reply
  • in reply to Michael Vinarcik
    I do mean instances. I appreciate what you mention, I've also built models where the class definitions were enough. In this case we are actually using instances (in object diagrams) to model how the execution manifests in the real world. Of course it isn't really cars & tires, that was just my analogous example, but it does capture what I'm trying to do. I played with the metachain and also thought that should work, but kept striking out finding a way to connect from the tire to the car. For example, picking "InstanceSpecification" on the metaclass and using the property of "Usage" or "_elementValueOfElement" or "_instanceValueOfInstance" doesn't produce any results. I'll admit I'm stabbing in the dark with how to use the metachain navigation though.
Children
No Data