Topics - Bharathi K

I am trying to structure two levels of a functional model (with activity diagrams) so that the activity parameters used in the top level modelling can be decomposed into more detailed parameters that are used at the next level, i.e. an Activity like 'Make Bread' is decomposed down to 'Mix Flour', 'Knead Dough' and 'Pour in Baking Tray' so the 'Cake Ingredients' parameter to the 'Make Bread' activity decomposes down to 'Flour', 'Sugar', etc.

Can the Activity Parameter that is instantiated to a particular Class be manipulated so that it turns up as an Activity Parameter at the next level? Currently if you connect the high level activities to to pins on the subactivities (as suggested in the SysML standard) then you have to reuse these as pins at the next level activity diagram. Can they be turned into Activity Parameters at the next level of decomposition?

If the class instantiated with the Activity Parameter is decomposed, can the child classes be used to instantiate the Activity Parameters/Pins at the next level of functional modelling? :-?

Also object flows and activity flows on a SysML activity diagram are shown with solid lines - why doesnt EA draw the control flows in dotted lines?

Using the AllocateActivityPartition to allocate activites to blocks works in the SysML Allocation Report (SysML Tech -> View Allocations) the same relationship does not show up in the Relationship Matrix.

To generate the Relationship matrix, I am using the Link Type Allocate with Source pointing to Behaviour and Target pointing to the Structure packages.

Tested the same with the Allocate dependency and this seemed to work ok in the Relationship Matrix.

How do you create Allocations in a Behaviour Package that reflect part of the System Breakdown Structure - the notation for the AllocationActivityPartition in the SysML Example (<<allocateActivityPartition>>:InternalCombustionEngine, etc) indicates that the system must be somehow named when the partition is created? :-?