Adding custom object as the subject of the State Chart Modeler

Prakash_Mavuduru

I have added a custom object that I need to be available as the subject of a state chart. i.e be able to select the custom object and be able to add a state chart as a "Component Model" . I tried to change the "Laws" related to the State Chart Modeler however I am not seeing the "Subject types" tab in the Legal definition. All I see is the"Member Types" tab.

 

See below..

 

 

 

I was able to do the same for the "Busines Class Modeler" successfully , just cannot seem to be able to do this for the state chart.

 

Any help to explain this behavior and help me acheive what I am trying to is very much appreciated.

 

Cheers,

Prakash

 

Blaine Bickar

Prakash,

 

Thanks for your inquiry.

 

Some of the model types in ProVision are more restrictive than others, and the Statechart model type is one of those.  Why it does not allow for a custom object to be it's subject is the fact that the Statechart model and the Class model are tightly coupled in ProVision - meaning that the objects used in the Statechart model are derived from the contents of a Class object (which is the subject of the model).  So, the States in the Statechart model are part of the definition of the Class object it describes...further, the State Transitions modeled in the Statechart model are usually the result of an Operation against the Class (also part of the Class definition).  Thus, the Statechart model only makes "sense" in the context of a Class object, therefore the Laws of the Statechart Model do not permit modification of the valid subject types.

 

I hope this explanation makes sense, but if it does not, please contact me and I will explain it in another way.

Prakash_Mavuduru

Thanks for your response Blaine.

 

It seems like an explanation of the behavior observed rather than any principles.

 

Seems like I should be allowed to define by own "things". Business Class is the default thing. As things can have a lifecycle I should be able to define a lifecycle (state chart) for my custom thing.

 

In any case it was important for me to know what is possible and what is not and your note certainly was helpful in that regards.

 

Thanks