Skip to content

When creating a constraint inside a requirement, is should be owned through a RequirementConstraintMembership #2185

@pcdavid

Description

@pcdavid

When importing such a requirement definition:

requirement def MaximumMass {
  private import ScalarValues::*;
  attribute massActual : Real;
  attribute massRequired : Real;
  assume constraint { massRequired > 0 }
  require constraint { massActual <= massRequired }
}

The two constraints (assume & require) are correctly owned through a RequirementConstraintMembership, as per § 8.3.21.7 of the SysMLv2 spec:

A RequirementConstraintMembership is a FeatureMembership for an assumed or required
ConstraintUsage of a RequirementDefinition or RequirementUsage.

However, when creating a constraint "manually" from the SysON Explorer inside the same requirement, it is incorrectly owned through a "plain" FeatureMembership:

Image

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions