Considering the following class diagram:
The class System
is active and its behaviour is to continuously
- call
filter
onPressureSensorFilter
passingPressureSensor.Pressure
as argument - call
Display.show
passing the output param ofPressureSensorFilter.filter
as argument
I would like to model the behaviour of System
through an ActivityDiagram
.
The main challenge in doing this is accessing the property PressureSensor
of System
.
After reading the UML 2.5 specification, I believe that the only way to do this is to use ReadSelfAction
(pag 457 UML 2.5 spec) and ReadStructuralFeatureAction
(pag 466 UML 2.5 spec) as depicted by the following Activity diagram:
where
ReadSelfAction
gives as output a current Instance ofSystem
.ReadPressureSensorFe..
is aREadStructuralFeatureAction
that reads the propertyPressureSensor
of the object give at its input pin which in this case is the current Instance of System.CallBesselFilter.filter Action
andCallDisplay.show Action
are twoCallOperationAction
(s) that callPressureSensorFilter.filter
andDisplay.show
respectively.
The issue with this is that is very convoluted and unclear. Is there any less convoluted and more clear way to describe the behaviour of System through an Activity diagram?