1

I’m modelling a simple SysML structure in Enterprise Architect (EA) and I’ve hit a problem with part instances and value propagation.

I have a BDD1 and IBD2, illustrated in the images.

IBD

BDD

I have these blocks:

  • Smartphone
  • Camera
  • Sensor

Relationships:

Smartphone has two parts:

  • frontCamera : Camera
  • backCamera : Camera

Camera has one part:

  • sensor : Sensor

Sensor has a value property power

When I change the power value of one sensor (e.g. set frontCamera.sensor.power = 76), the value automatically changes in the other sensor (backCamera.sensor.power also becomes 76).

It seems both cameras are sharing the same sensor instance, even though I expected each camera to have its own sensor.

But i want to make use of the "context specific values".

I know that SysML has this concept and I dont know why this should not be possible in EA. How can I correctly model this so that frontCamera.sensor and backCamera.sensor are independent instances (each with its own Sensor.power value) in EA’s SysML IBD?

1
  • Context specific values is a complicated matter in SysML 1. It might well be, that Enterprise Architect is one of the many tools that never implemented it. Or if it is implemented, the tool doesn't help with creating the correct structure. I only know of one tool, that supports it. Now when you change the value in the definition of the sensor, then of course, it will be changed for all usages of this definition. Commented Oct 17 at 12:56

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.