35: Activity ActualisePhysicalAsset and «STUB» ManifestActualAssetFromPotentialAsset

This content has been marked as discussing an ADVANCED topic!
And finally, Activities representing the actual creation of a new «physical» ActualPhysicalAsset :
Click on the image to view it full size

The outer level ActualisePhysicalAsset is essentially a wrapper for managing the binding through a CallOperationAction for bind of the created (manifested) «physical» ActualPhysicalAsset to the «digital» @Entity , which transitions from state UnBound to state Bound. After this, the role of the «digital» @Entity as "template" ends, and it can take on a new role as part of the synchronisation loop.

The actual creation (building) of the «physical» ActualPhysicalAsset is represented by the «STUB» ManifestActualAssetFromPotentialAsset. In practice, information from the «digital» PotentialPhysicalAsset and the "template" or "prototype" «digital» @Entity it carries would be used to build or otherwise make the «physical» ActualPhysicalAsset as a «physical» PhysicalEntity in the real world, represented by the innermost StubMakePhysicalAsset. The CallOperationAction for manifest asserts that the «physical» ActualPhysicalAsset indeed now Exists (and has mass in the real world).

And now it's time to see it all running!

You may wish to visit one of these tutorials next:

Visit more Systems Modeling Language (SysML®) tutorial trails here.
Visit also these screencast tutorial videos

Please email or phone Webel IT Australia on +61 405 029 008 or +61 (2) 9386 0090 to arrange on-site, off-site, or live remote web training seminars and workshops
Watch full video
Up next
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)