76
General Board / Re: Constraints appear as parts instead of constraints
« on: December 19, 2023, 12:27:43 am »
Acording to the SysML spec (section 10.1) "Constraint blocks provide a mechanism for integrating engineering analysis such as performance and reliability models with other SysML models". The example given (10.2.1) suggests a constraint based on a mathematical operation, where the input parameters to that operation will be taken from elsewhere in the model. Another common example is something like Newton's laws. The idea is that you are defining a constraint to be reused/obeyed in various places throughout the model.
Constraints within the 'Properties' of an Element are typically conditions around the behaviours and existance of an instantiation of that Element. E.g. a certain precondition is expected/required prior to execution of an Activity.
There are better summaries of the differences online, as ever Google is your friend.
But coming back to your question. I'm not sure that it would logically make sense for a Block (a classifier) to have Parts that are defined as ConstraintBlocks. It may depend on what your constraints are trying to achieve, and what your Block is actually defining, but Part Association doesn't feel right to me. Although EA will let you do it
Constraints within the 'Properties' of an Element are typically conditions around the behaviours and existance of an instantiation of that Element. E.g. a certain precondition is expected/required prior to execution of an Activity.
There are better summaries of the differences online, as ever Google is your friend.
But coming back to your question. I'm not sure that it would logically make sense for a Block (a classifier) to have Parts that are defined as ConstraintBlocks. It may depend on what your constraints are trying to achieve, and what your Block is actually defining, but Part Association doesn't feel right to me. Although EA will let you do it
