OMG System Modeling Language Avatar
  1. OMG Specification

OMG System Modeling Language — Open Issues

  • Acronym: SysML
  • Issues Count: 776
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
SYSML2_-224 State machine graphical notation for entry/exit/do actions incosistent SysML 2.0b2 open
SYSML2_-212 Inconsistencies in the graphical notation for "expose" SysML 2.0b2 open
SYSML2_-209 isOrdered and isUnique are missing from the reflective abstract mapping SysML 2.0b2 open
SYSML2_-207 Update language description and concrete syntax related to imports SysML 2.0b2 open
SYSML2_-202 Missing guidance on highlighting keywords SysML 2.0b2 open
SYSML2_-191 Error in the specification of "connections" SysML 2.0b2 open
SYSML2_-189 Incorrect enumeration example SysML 2.0b2 open
SYSML2_-187 There is no need for AnalysisAction SysML 2.0b2 open
SYSML2_-184 StateAction::substates has an implied subsetting of exclusiveStates SysML 2.0b2 open
SYSML2_-183 checkStateUsageExclusiveStateSpecialization and checkStateUsageSubstateSpecialization have problems SysML 2.0b2 open
SYSML2_-177 Guillemets should not be used on keywords in textual notation snippets used in the graphical notation SysML 2.0a1 open
SYSML2_-144 Missing production for use case actors and subject SysML 2.0a1 open
SYSML2_-142 GBNF for flow connection not mapped to semantics SysML 2.0a1 open
SYSML2_-114 Symbol for metadata def is missing SysML 2.0b1 open
SYSML2_-18 No support for metadata definition in graphical notation SysML 2.0a1 open
SYSML2_-11 Missing explicit explanation of compartments as views SysML 2.0a1 open
SYSML2_-3 incorrect naming of * character SysML 2.0b1 open
SYSML2_-2 incorrect naming of * character SysML 2.0b1 open
SYSML2_-1 Issues with SysML/KerML grammar SysML 2.0b1 open
SYSML2_-222 TransitionUsage source and target properties do not support feature chains SysML 2.0b2 open
SYSML2_-221 Default multiplicities are not formally specified SysML 2.0b2 open
SYSML2_-220 Replace Generic mapping classes by Initializers SysML 2.0b2 open
SYSML2_-173 Flow connections are incorrectly both structure and behavior SysML 2.0b1 open
SYSML2_-199 InterfaceBlock mapped to PortDefinition, but ConjugatedPortDefinition is not generated SysML 2.0b2 open
SYSML2_-214 Mapping of State does not consider orthogonal states SysML 2.0b2 open
SYSML2-480 Missing production for use case actors and subject SysML 2.0a1 open
SYSML2-557 Need to complete and align flow and message notations in GBNF SysML 2.0a1 open
SYSML2_-206 Editorial errors in constraints SysML 2.0b2 open
SYSML2_-200 Structured actions not properly covered by GBNF and notation tables SysML 2.0b2 open
SYSML2_-201 Confusing send/accept examples in notation tables SysML 2.0b2 open
SYSML2_-203 InitialState is mapped to StateUsage, but should be an empty ActionUsage SysML 2.0b2 open
SYSML2_-136 Transformation of UML4SysML::State does not consider entry, do, and exit behavior SysML 2.0b1 open
SYSML2_-111 Mapping of ObjectFlows with ForkNodes SysML 2.0b1 open
SYSML2_-197 Inconsistent use of guillemets in graphical notation for metamodel aspects SysML 2.0b2 open
SYSML2_-76 Transformation does not cover SysMLv1::FlowProperty SysML 2.0a1 open
SYSML2_-44 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 open
SYSML2_-165 Semantic constraints missing for shorthand succession notation SysML 2.0b1 open
SYSML2_-180 Reuse of KerML textual notation productions in the SysML grammar SysML 2.0b1 open
SYSML2_-178 Long-form notation for bindings and successions SysML 2.0b1 open
SYSML2_-179 Change graphical notation for use cases to elliptic elements SysML 2.0b1 open
SYSML2-629 Guillemets are not used on keywords in textual notation snippets used in the graphical notation SysML 2.0a1 open
SYSML2-686 Reuse of KerML textual notation productions in the SysML grammar SysML 2.0b1 open
SYSML2-632 Long-form notation for bindings and successions SysML 2.0b1 open
SYSML2-639 Change graphical notation for use cases to elliptic elements SysML 2.0b1 open
SYSML2_-175 PortUsage direction SysML 2.0b1 open
SYSML2_-172 Transformation fails on Enumerations that are ValueTypes SysML 2.0a1 open
SYSML2_-174 Enumerations not specializable SysML 2.0b1 open
SYSML2_-176 Proxy nodes are missing from states SysML 2.0a1 open
SYSML2-593 Enumerations not specializable SysML 2.0b1 open
SYSML2-592 Flow connections are incorrectly both structure and behavior SysML 2.0b1 open
SYSML2-601 Proxy nodes are missing from states SysML 2.0a1 open
SYSML2-591 Transformation fails on Enumerations that are ValueTypes SysML 2.0a1 open
SYSML2-594 PortUsage direction SysML 2.0b1 open
SYSML2_-170 SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong SysML 2.0a1 open
SYSML2_-171 Helper::getScalarValueType operation is not robust enough SysML 2.0a1 open
SYSML2_-169 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable SysML 2.0a1 open
SYSML2_-168 Literal factories are missing operation for their value SysML 2.0a1 open
SYSML2-588 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable SysML 2.0a1 open
SYSML2-590 Helper::getScalarValueType operation is not robust enough SysML 2.0a1 open
SYSML2-589 SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong SysML 2.0a1 open
SYSML2-586 Literal factories are missing operation for their value SysML 2.0a1 open
SYSML2_-166 Default multiplicities are not managed correctly SysML 2.0a1 open
SYSML2_-164 Add a distinguished attribute to capture the textual body of a requirement SysML 2.0b1 open
SYSML2_-163 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong SysML 2.0a1 open
SYSML2_-167 Factories specified for Literal specification shall be optimized SysML 2.0a1 open
SYSML2-546 Add a distinguished attribute to capture the textual body of a requirement SysML 2.0b1 open
SYSML2-584 Default multiplicities are not managed correctly SysML 2.0a1 open
SYSML2-576 Semantic constraints missing for shorthand succession notation SysML 2.0b1 open
SYSML2-535 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong SysML 2.0a1 open
SYSML2-585 Factories specified for Literal specification shall be optimized SysML 2.0a1 open
SYSML2_-162 Most SysML::Blocks are owned by a package SysML 2.0a1 open
SYSML2_-160 OpaqueBehavior shall be transformed even if they are not owned by a Package SysML 2.0a1 open
SYSML2_-161 Properties typed by Actors SysML 2.0a1 open
SYSML2_-159 Textual notation for send actions is too limited SysML 2.0b1 open
SYSML2_-158 timeslice/snapshot featuring types required to specialize or be same as types SysML 2.0a1 open
SYSML2-532 OpaqueBehavior shall be transformed even if they are not owned by a Package SysML 2.0a1 open
SYSML2-534 Most SysML::Blocks are owned by a package SysML 2.0a1 open
SYSML2-533 Properties typed by Actors SysML 2.0a1 open
SYSML2-524 timeslice/snapshot featuring types required to specialize or be same as types SysML 2.0a1 open
SYSML2-526 Textual notation for send actions is too limited SysML 2.0b1 open
SYSML2_-156 Relationship_Mapping::ownedRelatedElement() is wrong SysML 2.0a1 open
SYSML2_-154 GenericToElement_Mapping is missing default rules SysML 2.0a1 open
SYSML2_-153 GenericToStateUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-155 Comment_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-157 Namespace_Mapping shall redefine ownedRelationship() SysML 2.0a1 open
SYSML2-506 GenericToStateUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-507 GenericToElement_Mapping is missing default rules SysML 2.0a1 open
SYSML2-516 Namespace_Mapping shall redefine ownedRelationship() SysML 2.0a1 open
SYSML2-508 Comment_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-515 Relationship_Mapping::ownedRelatedElement() is wrong SysML 2.0a1 open
SYSML2_-148 Graphical notation unclear about user-defined keywords for library extensions SysML 2.0a1 open
SYSML2_-150 OccurrenceUsage missing portioningFeature SysML 2.0b1 open
SYSML2_-147 Graphical notation unclear on optionality of keywords on edges SysML 2.0a1 open
SYSML2_-152 GenericToRequirementUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-151 GenericToRelationship_Mapping is missing default rules SysML 2.0a1 open
SYSML2_-149 Control nodes missing from concrete syntax for states SysML 2.0a1 open
SYSML2-504 GenericToRelationship_Mapping is missing default rules SysML 2.0a1 open
SYSML2-486 Graphical notation unclear on optionality of keywords on edges SysML 2.0a1 open
SYSML2-487 Graphical notation unclear about user-defined keywords for library extensions SysML 2.0a1 open
SYSML2-505 GenericToRequirementUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-503 OccurrenceUsage missing portioningFeature SysML 2.0b1 open
SYSML2-502 Control nodes missing from concrete syntax for states SysML 2.0a1 open
SYSML2_-145 Incorrect definition elements in interconnection-element SysML 2.0b1 open
SYSML2_-146 Clarify bolding of keywords in concrete graphical syntax SysML 2.0a1 open
SYSML2_-143 Missalignment between interface graphical production and notation table SysML 2.0a1 open
SYSML2-485 Clarify bolding of keywords in concrete graphical syntax SysML 2.0a1 open
SYSML2-483 Incorrect definition elements in interconnection-element SysML 2.0b1 open
SYSML2-479 Missalignment between interface graphical production and notation table SysML 2.0a1 open
SYSML2-482 Missing production for use case actors and subject SysML 2.0a1 open
SYSML2_-139 missing graphical bnf for events and event occurrences SysML 2.0a1 open
SYSML2_-141 AssociationClass_Mapping is uncomplete SysML 2.0b1 open
SYSML2_-140 Initializer classes have to be rationalized SysML 2.0b1 open
SYSML2-476 Initializer classes have to be rationalized SysML 2.0b1 open
SYSML2-475 missing graphical bnf for events and event occurrences SysML 2.0a1 open
SYSML2-478 GBNF for flow connection not mapped to semantics SysML 2.0a1 open
SYSML2-477 AssociationClass_Mapping is uncomplete SysML 2.0b1 open
SYSML2_-138 ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless SysML 2.0b1 open
SYSML2_-135 element-node not defined SysML 2.0a1 open
SYSML2_-137 Optional language for documentation SysML 2.0b1 open
SYSML2-472 Optional language for documentation SysML 2.0b1 open
SYSML2-463 Transformation of UML4SysML::State does not consider entry, do, and exit behavior SysML 2.0b1 open
SYSML2-462 element-node not defined SysML 2.0a1 open
SYSML2-473 ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless SysML 2.0b1 open
SYSML2_-132 TimeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2_-131 ChangeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2_-134 Missing production for n-ary connection definition graphical SysML 2.0a1 open
SYSML2_-133 Fork/JoinNode succession "other" end multiplicity validations missing SysML 2.0b1 open
SYSML2_-130 ConstraintProperty should be mapped to a AssertConstraintUsage SysML 2.0b1 open
SYSML2_-129 TransitionUsage requires binding to succession with mandatory end multiplicities SysML 2.0b1 open
SYSML2-445 ConstraintProperty should be mapped to a AssertConstraintUsage SysML 2.0b1 open
SYSML2-397 TransitionUsage requires binding to succession with mandatory end multiplicities SysML 2.0b1 open
SYSML2-456 Missing production for n-ary connection definition graphical SysML 2.0a1 open
SYSML2-450 Fork/JoinNode succession "other" end multiplicity validations missing SysML 2.0b1 open
SYSML2-449 TimeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2-448 ChangeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2_-127 CommentAnnotation_Mapping shall be a "unique" mapping SysML 2.0a1 open
SYSML2_-124 Feature modifiers missing in Portion Membership examples SysML 2.0b1 open
SYSML2_-125 Representative example "Package with members" to be improved SysML 2.0b1 open
SYSML2_-126 Decision/MergeNode SuccessionSpecialization checks missing some constraints SysML 2.0b1 open
SYSML2_-128 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2-385 CommentAnnotation_Mapping shall be a "unique" mapping SysML 2.0a1 open
SYSML2-353 Feature modifiers missing in Portion Membership examples SysML 2.0b1 open
SYSML2-357 Representative example "Package with members" to be improved SysML 2.0b1 open
SYSML2-383 Decision/MergeNode SuccessionSpecialization checks missing some constraints SysML 2.0b1 open
SYSML2-390 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2_-120 Package import wildcard is missing SysML 2.0b1 open
SYSML2_-119 Wrong imported package notation SysML 2.0b1 open
SYSML2_-122 Incomplete example "Individual Occurrence" SysML 2.0b1 open
SYSML2_-123 Feature modefiers missing in Feature Membership examples SysML 2.0b1 open
SYSML2_-121 Representative notation for filtered package import missing SysML 2.0b1 open
SYSML2-327 Package import wildcard is missing SysML 2.0b1 open
SYSML2-326 Wrong imported package notation SysML 2.0b1 open
SYSML2-329 Representative notation for filtered package import missing SysML 2.0b1 open
SYSML2-337 Incomplete example "Individual Occurrence" SysML 2.0b1 open
SYSML2-352 Feature modefiers missing in Feature Membership examples SysML 2.0b1 open
SYSML2_-117 Nesting parameter symbol is missing optional nested parameter SysML 2.0b1 open
SYSML2_-115 Metadata declaration needs clarification SysML 2.0b1 open
SYSML2_-118 Missing representative notation for causation and requirements derivation SysML 2.0b1 open
SYSML2_-116 Binding between action parameters and directed features on ports missing SysML 2.0b1 open
SYSML2-320 Binding between action parameters and directed features on ports missing SysML 2.0b1 open
SYSML2-317 Metadata declaration needs clarification SysML 2.0b1 open
SYSML2-323 Nesting parameter symbol is missing optional nested parameter SysML 2.0b1 open
SYSML2-324 Missing representative notation for causation and requirements derivation SysML 2.0b1 open
SYSML2_-112 Mapping of ObjectFlows with JoinNodes SysML 2.0b1 open
SYSML2_-113 Mapping of ObjectFlows with DecisionNodes SysML 2.0b1 open
SYSML2-315 Mapping of ObjectFlows with DecisionNodes SysML 2.0b1 open
SYSML2-316 Symbol for metadata def is missing SysML 2.0b1 open
SYSML2-313 Mapping of ObjectFlows with ForkNodes SysML 2.0b1 open
SYSML2-314 Mapping of ObjectFlows with JoinNodes SysML 2.0b1 open
SYSML2_-106 the getMapped operation cannot be called on ElementOwnership_Mapping SysML 2.0a1 open
SYSML2_-108 Various constraints need to take feature chaining into account SysML 2.0b1 open
SYSML2_-110 Transformation does not cover the mapping of Unit and QuantityKind SysML 2.0b1 open
SYSML2_-107 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2_-109 Transformation does not cover mapping of Parameter::isStreaming=true SysML 2.0b1 open
SYSML2-311 Transformation does not cover the mapping of Unit and QuantityKind SysML 2.0b1 open
SYSML2-297 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2-309 Transformation does not cover mapping of Parameter::isStreaming=true SysML 2.0b1 open
SYSML2-286 the getMapped operation cannot be called on ElementOwnership_Mapping SysML 2.0a1 open
SYSML2-307 Various constraints need to take feature chaining into account SysML 2.0b1 open
SYSML2_-103 Transformation does not cover UML4SysML::DestroyLinkAction SysML 2.0a1 open
SYSML2_-100 Transformation does not cover UML4SysML::SignalEvent SysML 2.0a1 open
SYSML2_-104 Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet SysML 2.0a1 open
SYSML2_-101 Transformation does not cover UML4SysML::ReadLinkAction SysML 2.0a1 open
SYSML2_-102 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 open
SYSML2_-105 Transformation does not cover UML4SysML::FunctionBehavior SysML 2.0a1 open
SYSML2-272 Transformation does not cover UML4SysML::ReadLinkAction SysML 2.0a1 open
SYSML2-273 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 open
SYSML2-283 Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet SysML 2.0a1 open
SYSML2-284 Transformation does not cover UML4SysML::FunctionBehavior SysML 2.0a1 open
SYSML2-274 Transformation does not cover UML4SysML::DestroyLinkAction SysML 2.0a1 open
SYSML2_-96 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2_-98 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2_-99 Some Standard View Definitions should be filtered specializations of General View SysML 2.0a1 open
SYSML2_-97 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2-271 Transformation does not cover UML4SysML::SignalEvent SysML 2.0a1 open
SYSML2-187 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2-199 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2-225 Some Standard View Definitions should be filtered specializations of General View SysML 2.0a1 open
SYSML2-188 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2_-94 Some package-level features are mandatory SysML 2.0a1 open
SYSML2_-92 XMI and JSON for example model SysML 2.0a1 open
SYSML2_-91 Machine readable project interchange file(s) for language description examples SysML 2.0a1 open
SYSML2_-93 Assignment action usages do not specify when their expressions are evaluated SysML 2.0a1 open
SYSML2_-95 ConstraintBlock mapping parameters to input attributes SysML 2.0a1 open
SYSML2-183 Some package-level features are mandatory SysML 2.0a1 open
SYSML2-177 Assignment action usages do not specify when their expressions are evaluated SysML 2.0a1 open
SYSML2-186 ConstraintBlock mapping parameters to input attributes SysML 2.0a1 open
SYSML2-160 Machine readable project interchange file(s) for language description examples SysML 2.0a1 open
SYSML2-161 XMI and JSON for example model SysML 2.0a1 open
SYSML2_-90 Subject of an include use case usage SysML 2.0a1 open
SYSML2_-88 Transformation does not cover SysMLv1::NoBuffer SysML 2.0a1 open
SYSML2_-87 Transformation does not cover SysMLv1::Overwrite SysML 2.0a1 open
SYSML2_-89 Accepters on transition usages from entry actions SysML 2.0a1 open
SYSML2-151 Transformation does not cover SysMLv1::NoBuffer SysML 2.0a1 open
SYSML2-154 Subject of an include use case usage SysML 2.0a1 open
SYSML2-150 Transformation does not cover SysMLv1::Overwrite SysML 2.0a1 open
SYSML2-152 Accepters on transition usages from entry actions SysML 2.0a1 open
SYSML2_-86 Transformation does not cover SysMLv1::AllocateActivitiyPartition SysML 2.0a1 open
SYSML2_-85 Transformation does not cover SysMLv1::PropertySpecificType SysML 2.0a1 open
SYSML2_-84 Transformation does not cover SysMLv1::EndPathMultiplicity SysML 2.0a1 open
SYSML2_-82 Transformation does not cover SysMLv1::BoundReference SysML 2.0a1 open
SYSML2_-83 Transformation does not cover SysMLv1::ParticipantProperty SysML 2.0a1 open
SYSML2-145 Transformation does not cover SysMLv1::BoundReference SysML 2.0a1 open
SYSML2-146 Transformation does not cover SysMLv1::ParticipantProperty SysML 2.0a1 open
SYSML2-148 Transformation does not cover SysMLv1::PropertySpecificType SysML 2.0a1 open
SYSML2-149 Transformation does not cover SysMLv1::AllocateActivitiyPartition SysML 2.0a1 open
SYSML2-147 Transformation does not cover SysMLv1::EndPathMultiplicity SysML 2.0a1 open
SYSML2_-80 Transformation does not cover SysMLv1::Expose SysML 2.0a1 open
SYSML2_-78 Transformation does not cover SysMLv1::View SysML 2.0a1 open
SYSML2_-81 Transformation does not cover SysMLv1::DistributedProperty SysML 2.0a1 open
SYSML2_-79 Transformation does not cover SysMLv1::Conform SysML 2.0a1 open
SYSML2_-77 Transformation does not cover SysMLv1::InvocationOnNestedPortAction SysML 2.0a1 open
SYSML2-140 Transformation does not cover SysMLv1::InvocationOnNestedPortAction SysML 2.0a1 open
SYSML2-142 Transformation does not cover SysMLv1::Conform SysML 2.0a1 open
SYSML2-144 Transformation does not cover SysMLv1::DistributedProperty SysML 2.0a1 open
SYSML2-143 Transformation does not cover SysMLv1::Expose SysML 2.0a1 open
SYSML2-141 Transformation does not cover SysMLv1::View SysML 2.0a1 open
SYSML2_-72 Transformation does not cover UML4SysML::UnmarshallAction SysML 2.0a1 open
SYSML2_-73 Transformation does not cover SysMLv1::TriggerOnNestedPort SysML 2.0a1 open
SYSML2_-74 Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent SysML 2.0a1 open
SYSML2_-75 Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction SysML 2.0a1 open
SYSML2-135 Transformation does not cover SysMLv1::TriggerOnNestedPort SysML 2.0a1 open
SYSML2-136 Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent SysML 2.0a1 open
SYSML2-137 Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction SysML 2.0a1 open
SYSML2-138 Transformation does not cover SysMLv1::FlowProperty SysML 2.0a1 open
SYSML2-134 Transformation does not cover UML4SysML::UnmarshallAction SysML 2.0a1 open
SYSML2_-70 Transformation does not cover UML4SysML::LinkEndDestructionData SysML 2.0a1 open
SYSML2_-68 Transformation does not cover UML4SysML::ConditionalNode SysML 2.0a1 open
SYSML2_-69 Transformation does not cover UML4SysML::LinkEndCreationData SysML 2.0a1 open
SYSML2_-71 Transformation does not cover UML4SysML::LinkEndData SysML 2.0a1 open
SYSML2_-67 Transformation does not cover UML4SysML::Clause SysML 2.0a1 open
SYSML2_-66 Transformation does not cover UML4SysML::ActivityPartition SysML 2.0a1 open
SYSML2-129 Transformation does not cover UML4SysML::Clause SysML 2.0a1 open
SYSML2-133 Transformation does not cover UML4SysML::LinkEndData SysML 2.0a1 open
SYSML2-131 Transformation does not cover UML4SysML::LinkEndCreationData SysML 2.0a1 open
SYSML2-132 Transformation does not cover UML4SysML::LinkEndDestructionData SysML 2.0a1 open
SYSML2-128 Transformation does not cover UML4SysML::ActivityPartition SysML 2.0a1 open
SYSML2-130 Transformation does not cover UML4SysML::ConditionalNode SysML 2.0a1 open
SYSML2_-62 Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification SysML 2.0a1 open
SYSML2_-65 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2_-64 Transformation does not cover UML4SysML::OccurrenceSpecification SysML 2.0a1 open
SYSML2_-63 Transformation does not cover UML4SysML::Gate SysML 2.0a1 open
SYSML2-124 Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification SysML 2.0a1 open
SYSML2-125 Transformation does not cover UML4SysML::Gate SysML 2.0a1 open
SYSML2-127 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2-126 Transformation does not cover UML4SysML::OccurrenceSpecification SysML 2.0a1 open
SYSML2_-60 Transformation does not cover UML4SysML::PartDecomposition SysML 2.0a1 open
SYSML2_-61 Transformation does not cover UML4SysML::ConsiderIgnoreFragment SysML 2.0a1 open
SYSML2_-59 Transformation does not cover UML4SysML::GeneralOrdering SysML 2.0a1 open
SYSML2_-58 Transformation does not cover UML4SysML::Continuation SysML 2.0a1 open
SYSML2-120 Transformation does not cover UML4SysML::Continuation SysML 2.0a1 open
SYSML2-121 Transformation does not cover UML4SysML::GeneralOrdering SysML 2.0a1 open
SYSML2-122 Transformation does not cover UML4SysML::PartDecomposition SysML 2.0a1 open
SYSML2-123 Transformation does not cover UML4SysML::ConsiderIgnoreFragment SysML 2.0a1 open
SYSML2_-54 Transformation does not cover UML4SysML::TimeConstraint SysML 2.0a1 open
SYSML2_-55 Transformation does not cover UML4SysML::Interval SysML 2.0a1 open
SYSML2_-57 Transformation does not cover UML4SysML::DestructionOccurrenceSpecification SysML 2.0a1 open
SYSML2_-53 Transformation does not cover UML4SysML::DurationInterval SysML 2.0a1 open
SYSML2_-56 Transformation does not cover UML4SysML::Image SysML 2.0a1 open
SYSML2-116 Transformation does not cover UML4SysML::TimeConstraint SysML 2.0a1 open
SYSML2-119 Transformation does not cover UML4SysML::DestructionOccurrenceSpecification SysML 2.0a1 open
SYSML2-117 Transformation does not cover UML4SysML::Interval SysML 2.0a1 open
SYSML2-115 Transformation does not cover UML4SysML::DurationInterval SysML 2.0a1 open
SYSML2-118 Transformation does not cover UML4SysML::Image SysML 2.0a1 open
SYSML2_-49 Transformation does not cover UML4SysML::TimeObservation SysML 2.0a1 open
SYSML2_-50 Transformation does not cover UML4SysML::IntervalConstraint SysML 2.0a1 open
SYSML2_-52 Transformation does not cover UML4SysML::StringExpression SysML 2.0a1 open
SYSML2_-51 Transformation does not cover UML4SysML::DurationObservation SysML 2.0a1 open
SYSML2_-48 Transformation does not cover UML4SysML::Duration SysML 2.0a1 open
SYSML2-112 Transformation does not cover UML4SysML::IntervalConstraint SysML 2.0a1 open
SYSML2-110 Transformation does not cover UML4SysML::Duration SysML 2.0a1 open
SYSML2-111 Transformation does not cover UML4SysML::TimeObservation SysML 2.0a1 open
SYSML2-114 Transformation does not cover UML4SysML::StringExpression SysML 2.0a1 open
SYSML2-113 Transformation does not cover UML4SysML::DurationObservation SysML 2.0a1 open
SYSML2_-47 Transformation does not cover UML4SysML::DurationConstraint SysML 2.0a1 open
SYSML2_-46 Transformation does not cover UML4SysML::TimeInterval SysML 2.0a1 open
SYSML2_-43 Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete SysML 2.0a1 open
SYSML2_-45 Transformation does not cover UML4SysML::Extend SysML 2.0a1 open
SYSML2-107 Transformation does not cover UML4SysML::Extend SysML 2.0a1 open
SYSML2-108 Transformation does not cover UML4SysML::TimeInterval SysML 2.0a1 open
SYSML2-105 Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete SysML 2.0a1 open
SYSML2-109 Transformation does not cover UML4SysML::DurationConstraint SysML 2.0a1 open
SYSML2-106 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 open
SYSML2_-41 Semantics of a conditional succession using "else" are missing SysML 2.0a1 open
SYSML2_-39 Semantics of transfers across interfaces SysML 2.0a1 open
SYSML2_-40 Port transfer semantics SysML 2.0a1 open
SYSML2_-42 Transformation does not cover UML4SysML::GeneralizationSet SysML 2.0a1 open
SYSML2-100 Semantics of a conditional succession using "else" are missing SysML 2.0a1 open
SYSML2-98 Port transfer semantics SysML 2.0a1 open
SYSML2-97 Semantics of transfers across interfaces SysML 2.0a1 open
SYSML2-104 Transformation does not cover UML4SysML::GeneralizationSet SysML 2.0a1 open
SYSML2_-37 XMI and JSON for model libraries SysML 2.0a1 open
SYSML2_-35 Add standard domain libraries for mathematical and physical constants SysML 2.0a1 open
SYSML2_-38 Incorrect action name in graphical notation example SysML 2.0a1 open
SYSML2_-36 Redefining feature information missing from specification document SysML 2.0a1 open
SYSML2_-34 Add capability to specify accuracy, uncertainty or tolerance for numerical values SysML 2.0a1 open
SYSML2-96 Incorrect action name in graphical notation example SysML 2.0a1 open
SYSML2-86 Add capability to specify accuracy, uncertainty or tolerance for numerical values SysML 2.0a1 open
SYSML2-90 Redefining feature information missing from specification document SysML 2.0a1 open
SYSML2-91 XMI and JSON for model libraries SysML 2.0a1 open
SYSML2-87 Add standard domain libraries for mathematical and physical constants SysML 2.0a1 open
SYSML2_-31 Graphical BNF for grid rendering is missing SysML 2.0a1 open
SYSML2_-33 Extend ISQ with missing quantity and unit types for US Customary Units SysML 2.0a1 open
SYSML2_-30 Graphical notation for variant inheritance from variation requires improvement SysML 2.0a1 open
SYSML2_-32 Resolve "TODO" in domain library model Time SysML 2.0a1 open
SYSML2-77 Resolve "TODO" in domain library model Time SysML 2.0a1 open
SYSML2-82 Extend ISQ with missing quantity and unit types for US Customary Units SysML 2.0a1 open
SYSML2-71 Graphical BNF for grid rendering is missing SysML 2.0a1 open
SYSML2-70 Graphical notation for variant inheritance from variation requires improvement SysML 2.0a1 open
SYSML2_-27 Missing graphical notation for Flows Compartment SysML 2.0a1 open
SYSML2_-29 Graphical BNF mapping to abstract syntax is missing SysML 2.0a1 open
SYSML2_-25 Source and target on binary ConnectionDefinition symbol missing SysML 2.0a1 open
SYSML2_-28 Graphical BNF defines lifeline elements incorrectly SysML 2.0a1 open
SYSML2_-26 Special graphical notation for distinguished parameters in name compartment SysML 2.0a1 open
SYSML2-61 Special graphical notation for distinguished parameters in name compartment SysML 2.0a1 open
SYSML2-64 Missing graphical notation for Flows Compartment SysML 2.0a1 open
SYSML2-60 Source and target on binary ConnectionDefinition symbol missing SysML 2.0a1 open
SYSML2-67 Graphical BNF mapping to abstract syntax is missing SysML 2.0a1 open
SYSML2-65 Graphical BNF defines lifeline elements incorrectly SysML 2.0a1 open
SYSML2_-24 Port symbol notation (arrows) needs improvement SysML 2.0a1 open
SYSML2_-23 Missing graphical notation for n-ary connection def and usage SysML 2.0a1 open
SYSML2_-21 Parameter symbol notation needs improvement SysML 2.0a1 open
SYSML2_-22 Quantity and unit for ratio and fraction SysML 2.0a1 open
SYSML2-55 Quantity and unit for ratio and fraction SysML 2.0a1 open
SYSML2-57 Port symbol notation (arrows) needs improvement SysML 2.0a1 open
SYSML2-53 Parameter symbol notation needs improvement SysML 2.0a1 open
SYSML2-56 Missing graphical notation for n-ary connection def and usage SysML 2.0a1 open
SYSML2_-20 Examples requirement derivation, cause effect, and refinement missing SysML 2.0a1 open
SYSML2_-15 Graphical BNF production proxy refers to wrong label SysML 2.0a1 open
SYSML2_-16 Consider production for standard case view vs filtered general view SysML 2.0a1 open
SYSML2_-17 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2_-19 Loop examples incomplete in representative notation table SysML 2.0a1 open
SYSML2-51 Loop examples incomplete in representative notation table SysML 2.0a1 open
SYSML2-49 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2-48 Consider production for standard case view vs filtered general view SysML 2.0a1 open
SYSML2-50 No support for metadata in graphical notation SysML 2.0a1 open
SYSML2-41 Graphical BNF production proxy refers to wrong label SysML 2.0a1 open
SYSML2-52 Examples requirement derivation, cause effect, and refinement missing SysML 2.0a1 open
SYSML2_-12 Regularization of textual notation for loops SysML 2.0a1 open
SYSML2_-13 Identify the owning context in a graphical view SysML 2.0a1 open
SYSML2_-14 Graphical BNF production sq-ev-occurrence has inconsistent proxy notation SysML 2.0a1 open
SYSML2-37 Identify the owning context in a graphical view SysML 2.0a1 open
SYSML2-40 Graphical BNF production sq-ev-occurrence has inconsistent proxy notation SysML 2.0a1 open
SYSML2-36 Regularization of textual notation for loops SysML 2.0a1 open
SYSML2_-8 Clarify query using view SysML 2.0a1 open
SYSML2_-7 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2_-10 Missing graphical notation allocating flow to connection SysML 2.0a1 open
SYSML2_-9 Identify impact views on model organization SysML 2.0a1 open
SYSML2-33 Identify impact views on model organization SysML 2.0a1 open
SYSML2-32 Clarify query using view SysML 2.0a1 open
SYSML2-31 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2-34 Missing graphical notation allocating flow to connection SysML 2.0a1 open
SYSML2-35 Missing explicit explanation of compartments as views SysML 2.0a1 open
SYSML2_-5 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered SysML 2.0a1 open
SYSML2_-4 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 open
SYSML2_-6 Standard view filters incomplete SysML 2.0a1 open
SYSML2-17 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 open
SYSML2-18 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered SysML 2.0a1 open
SYSML2-25 Standard view filters incomplete SysML 2.0a1 open
KERML-245 KerML should have syntax for enumerations SysML 2.0b1 open
KERML_-53 KerML should have syntax for enumerations SysML 2.0b1 open
SYSML2-7 Pin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-5 UntypedPin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-1 "Elements not mapped" table sections are empty SysML 2.0a1 open
SYSML2-75 Spatial links can be occurrences SysML 2.0a1 open
SYSML2-69 Inefficient graphical notation specification tooling SysML 2.0a1 open
SYSML2-54 Error in InterfaceUsage semantics subclause SysML 2.0a1 open
SYSML2-78 The .project.json file for the Cause and Effect Domain Library is misnamed SysML 2.0a1 open
SYSML2-26 Standard view filters incomplete SysML 2.0a1 open
SYSML2-81 Association end name " /usageWithDirectedUsage" has a typo SysML 2.0a1 open
SYSML2-156 Errors in textual BNF for RequirementDefinition and ConcernDefinition SysML 2.0a1 open
SYSML2-153 Error in assert constraint example SysML 2.0a1 open
SYSML2-92 Packages can also have compartments SysML 2.0a1 open
SYSML2-23 Transformation of UML4SysML::AddStructuralFeatureValueAction is not correct SysML 2.0a1 open
SYSML2-103 Editoral corrections in 7.16.11 SysML 2.0a1 open
SYSML2-4 Transformation of UML4SysML::AddVariableValueAction is not correct SysML 2.0a1 open
SYSML2-2 ItemFlowEnds of ObjectFlow transformation target are not defined correctly SysML 2.0a1 open
SYSML2-14 UML4SysML::ClearVariableAction transformation does not include a ReturnParameter SysML 2.0a1 open
SYSML2-16 Subsections for mapping classes in section 7.7.2.3.9 should be ordered alphabetically SysML 2.0a1 open
SYSML2-173 Mapping of ValueSpecificationActions does not work for untyped pins SysML 2.0a1 open
SYSML2-19 REAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-88 Mapping of allocation between usage elements is not specified yet SysML 2.0a1 open
SYSML2-171 Optimize Pin mapping class generalization hierarchy SysML 2.0a1 open
SYSML2-200 Description of Subsetting mapping classes is not correct SysML 2.0a1 open
SYSML2-189 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class ActivityEdgeInitialNodeSourceEndFeatureMembership_Mapping SysML 2.0a1 open
SYSML2-174 EmptyReturnParameterFeatureMembership_Mapping does not exist SysML 2.0a1 open
SYSML2-195 GenericToEndFeatureMembership_Mapping::to property redefines itself SysML 2.0a1 open
SYSML2-193 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class SysML 2.0a1 open
SYSML2-178 ClassifierBehaviorFeatureMembership_Mapping does not exist SysML 2.0a1 open
SYSML2-215 ControlFlow transformation target ends are not defined correctly SysML 2.0a1 open
SYSML2-202 Filter for mapping class Behavior_Mapping is useless SysML 2.0a1 open
SYSML2-208 A ConnectionUsage should be owned by a FeatureMembership relationship SysML 2.0a1 open
SYSML2-197 ControlFlow target SuccessionAsUsage should have end feature with reference subsetting SysML 2.0a1 open
SYSML2-211 Introduce GenericToTransitionUsage_Mapping class SysML 2.0a1 open
SYSML2-204 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-43 Graphical BNF sq-message reference incorrect SysML 2.0a1 open
SYSML2-39 Graphical BNF production sq-part refers to wrong port SysML 2.0a1 open
SYSML2-45 Graphical BNF interconnection view production incorrect SysML 2.0a1 open
SYSML2-42 Textual production for sq-proxy-label incorrect SysML 2.0a1 open
SYSML2-213 Typo in section 7.6.3 and section 7.6.4: mappingsto SysML 2.0a1 open
SYSML2-84 Connection declaration does not allow a feature value SysML 2.0a1 open
SYSML2-46 Graphical BNF flow-label and interface-label productions missing SysML 2.0a1 open
SYSML2-62 Incorrect production for attributes-compartment-element SysML 2.0a1 open
SYSML2-44 Graphical BNF sq-message-label usage incorrect SysML 2.0a1 open
SYSML2-155 Limitation on specifying view renderings SysML 2.0a1 open
SYSML2-261 Error in textual BNF for TargetSuccession SysML 2.0a1 open
SYSML2-255 Error in textual BNF for MessageDeclaration SysML 2.0a1 open
SYSML2-223 Table 38 "Standard View Definitions" redundant SysML 2.0a1 open
SYSML2-291 Case View is not a standard view SysML 2.0a1 open
SYSML2-224 Number missing from table listing Standard View Definitions SysML 2.0a1 open
SYSML2-181 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-206 Mapping of UML4SysML::InformationFlow with a realizing connector is not supported SysML 2.0a1 open
SYSML2-232 TIAOperatorExpression_Mapping uses non-existing mapping class EqualOperatorExpressionOperand_Mapping SysML 2.0a1 open
SYSML2-180 Mapping of UML4SysML::InformationFlow between definition elements is not supported SysML 2.0a1 open
SYSML2-228 Helpers::activityOwnedRelationships mixes up FinalNodes and FlowFinalNodes SysML 2.0a1 open
SYSML2-234 RSFAReferenceUsageFeatureMembership_Mapping uses non-existing mapping class SysML 2.0a1 open
SYSML2-236 Resolution of approved issue SYSML2-23 uses outdated mapping classes SysML 2.0a1 open
SYSML2-240 TestCaseActivity_Mapping uses non-existing mapping classes SysML 2.0a1 open
SYSML2-229 ControlFlowSuccessionAsUsage_Mapping uses non-existing mapping class SysML 2.0a1 open
SYSML2-244 RVVAVariable_Mapping uses CommonAssignmentActionOwningMembership_Mapping, but should be a factory class SysML 2.0a1 open
SYSML2-238 ObjectFlows targeting a final node or a activity parameter node cannot be mapped SysML 2.0a1 open
SYSML2-248 CreateLinkObjectAction_Mapping should specialize CreateLinkAction_Mapping SysML 2.0a1 open
SYSML2-250 Typo in AEAReceiverFeatureValue_Mapping::value() SysML 2.0a1 open
SYSML2-281 Map OpqueBehavior always to ActionDefinition SysML 2.0a1 open
SYSML2-258 Mapping of allcation between usage and definition or definition and usage elements does not work SysML 2.0a1 open
SYSML2-246 AEAParameterMembership_Mapping::ownedMemberParameter cannot return OclUndefined SysML 2.0a1 open
SYSML2-304 Mapping of ActivityEdge does not consider ActivityParameterNodes SysML 2.0b1 open
SYSML2-278 UntypedPin_Mapping redefines operation without any changes SysML 2.0a1 open
SYSML2-157 Incorrect font in descriptions of AttributeUsage and TransitionUsage SysML 2.0a1 open
SYSML2-221 UML4SysML::Activities and StateMachines owned by blocks should be mapped to definition elements SysML 2.0a1 open
SYSML2-312 Typo: Table 19 - requirres SysML 2.0b1 open
SYSML2-47 Graphical BNF productions missing for connections SysML 2.0a1 open
SYSML2-328 Incorrect private keyword notation SysML 2.0b1 open
SYSML2-322 Nesting parameter symbols should use rounded rectangles SysML 2.0b1 open
SYSML2-330 Incorrect entry name representative notation SysML 2.0b1 open
SYSML2-321 Nesting port symbols should use rounded rectangles SysML 2.0a1 open
SYSML2-319 Wrong line style on action flow succession SysML 2.0b1 open
SYSML2-287 sq-port-label and sq-ev-occurrence-label productions use Usage SysML 2.0a1 open
SYSML2-335 Incorrect keyword in example "Attributes Compartment" SysML 2.0b1 open
SYSML2-334 Incorrect example "Relationships Compartment" SysML 2.0b1 open
SYSML2-338 Incomplete example "Occurrences Compartment" SysML 2.0b1 open
SYSML2-332 Incorrect example "Variant Membership" SysML 2.0b1 open
SYSML2-341 Compartments still show nested feature notation SysML 2.0b1 open
SYSML2-339 Unnecessarily complicated examples "Timeslices Compartment" and "Snapshots Compartment" SysML 2.0b1 open
SYSML2-344 Missing «perform action» in example "Part with Graphical Compartment with perform actions ..." SysML 2.0b1 open
SYSML2-340 Examples "Timeslices Compartment" and "Snapshots Compartment" incorrectly declare state feature SysML 2.0b1 open
SYSML2-345 Incorrect inherited notation in example "Connection" SysML 2.0b1 open
SYSML2-342 Misleading port name in example "Part with Ports" SysML 2.0b1 open
SYSML2-347 Wrong reference usage notation SysML 2.0b1 open
SYSML2-325 Wrong compartment name: documentation SysML 2.0b1 open
SYSML2-93 Keyword for documentation is "doc" SysML 2.0a1 open
SYSML2-348 Incorrect item flow notation in example "Message" SysML 2.0b1 open
SYSML2-190 The description and derivation of ForLoopActionUsage::seqArgument is wrong SysML 2.0a1 open
SYSML2-99 Incorrect notation in action examples SysML 2.0a1 open
SYSML2-101 Time triggers are relative to "localClock", not "defaultClock" SysML 2.0a1 open
SYSML2-300 validateDefinitionNonVariationMembership and validateUsageNonVariationMembership are redundant with validateVariantMembershipOwningNamespace SysML 2.0b1 open
SYSML2-254 Redundant numbered list in language description of usage SysML 2.0a1 open
SYSML2-191 deriveForLoopActionUsageBodyAction is misnamed SysML 2.0a1 open
SYSML2-296 validateFramedConcernUsageConstraintKind constraint is misnamed SysML 2.0b1 open
SYSML2-218 Errors in TransitionUsage semantic constraints SysML 2.0a1 open
SYSML2-298 validateDefinitionVariationMembership and validateUsageVariationMembership are too strict SysML 2.0b1 open
SYSML2-302 validateOccurrenceUsageIndividualDefinition OCL is wrong SysML 2.0b1 open
SYSML2-301 validateUsageOwningType constraint is too restrictive SysML 2.0b1 open
SYSML2-303 validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization OCL is wrong SysML 2.0b1 open
SYSML2-306 validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization constraints are too restrictive SysML 2.0b1 open
SYSML2-356 The OCL for the body of ConstraintUsage::namingFeature is incorrect SysML 2.0b1 open
SYSML2-414 checkTransitionUsageSourceBindingConnector text and OCL are different SysML 2.0b1 open
SYSML2-398 TransitionUsage effectAction attribute text and constraint are different SysML 2.0a1 open
SYSML2-424 WhileLoopsActionusage title typos SysML 2.0b1 open
SYSML2-423 checkIfActionUsageSpecialization OCL specifiesFromLibrary typo SysML 2.0b1 open
SYSML2-66 Graphical BNF for n-ary connections missing SysML 2.0a1 open
SYSML2-418 Description of TimeEvent_Mapping is a note SysML 2.0b1 open
SYSML2-437 The transformation specification does not explicitly specify how to map a ValueType SysML 2.0b1 open
SYSML2-420 InformationFlow mapping classes should use GenericTo mapping classes SysML 2.0b1 open
SYSML2-416 Description of ChangeEvent_Mapping is a note SysML 2.0b1 open
SYSML2-432 Part properties with AggregationKind::none or shared are not mapped to PartUsage with isComposite=false SysML 2.0b1 open
SYSML2-446 Document how SysML v1 properties are mapped to SysML v2 SysML 2.0b1 open
SYSML2-299 validateDefinitionVariationSpecialization and validateUsageVariationSpecialization OCL is wrong SysML 2.0b1 open
SYSML2-443 Property_Mapping should map to ItemUsage and the class name is misleading SysML 2.0b1 open
SYSML2-441 Change the table header of the overview tables in the mapping class specification chapters SysML 2.0b1 open
SYSML2-439 UML4SysML::Class should be mapped to ItemDefinition SysML 2.0b1 open
SYSML2-252 Graphical BNF opaque "text block" productions SysML 2.0a1 open
SYSML2-425 LoopActionUsage descriptions refer to property not in metamodel SysML 2.0b1 open
SYSML2-343 Mistake in example "Part performs a reference action (action1) that references ..." SysML 2.0b1 open
SYSML2-63 Various incorrect Graphical BNF productions SysML 2.0a1 open
SYSML2-331 Incomplete textual notation in example "Subsetting" SysML 2.0b1 open
SYSML2-139 Transformation does not cover SysMLv1::~InterfaceBlock SysML 2.0a1 open
SYSML2-280 ElementMain_Mapping::ownedRelationship is wrong SysML 2.0a1 open
SYSML2-21 RSAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-95 Flows Compartment example graphical notation missing SysML 2.0a1 open
SYSML2-58 Representative notation table uses deprecated «equal» SysML 2.0a1 open
SYSML2-422 GenericToItemDefinition_Mapping should specialize GenericToOccurrenceDefinition_Mapping SysML 2.0b1 open
SYSML2-412 SYSML2-180 uses non-existing general mapping class GenericToItemUsage_Mapping SysML 2.0b1 open
SYSML2-350 Incomplete flow notation in example "Flow as Node" SysML 2.0b1 open
SYSML2-346 Incorrect notation in example "Binding Connection" SysML 2.0b1 open
SYSML2-349 Incorrect item flow notation in example "Interface as Node" SysML 2.0b1 open
SYSML2-333 Incomplete textual notation in example "Variants Compartment" SysML 2.0b1 open
SYSML2-453 Text error in List property construction SysML 2.0b1 open
SYSML2-451 Missing production for ConjugatePortTyping SysML 2.0b1 open
SYSML2-452 misspelled ConjugatePortTyping should be ConjugatedPortTyping SysML 2.0b1 open
SYSML2-431 Incorrect EBNF specification SysML 2.0b1 open
SYSML2-454 PrefixComment should not be a production for AnnotatingElement SysML 2.0b1 open
SYSML2-79 View::viewpointSatisfactions should subset viewpointChecks and checkedConstraints SysML 2.0a1 open
SYSML2-467 RequirementConstraintUsage should not have a RequirementBody SysML 2.0b1 open
SYSML2-513 Missing text in some main mapping sections SysML 2.0b1 open
SYSML2-511 Remove sentence in StateMachines overview section SysML 2.0b1 open
SYSML2-509 Remove sentence in Classification overview section SysML 2.0b1 open
SYSML2-241 TestCaseVerifyRequirementUsage_Mapping uses non-existing mapping classes SysML 2.0a1 open
SYSML2-83 Narrow down return types of SpatialItem::PositionOf and ::CurrentPositionOf SysML 2.0a1 open
SYSML2-295 Causation end features need to redefine source and target SysML 2.0a1 open
SYSML2-378 Sample::calculation has an incorrect type SysML 2.0b1 open
SYSML2-488 Constraints missing to enforce variations being abstract SysML 2.0b1 open
SYSML2-393 Documentation of Time::defaultClock is missing SysML 2.0b1 open
SYSML2-253 Additional cases when usages are required to be referential SysML 2.0a1 open
SYSML2-500 The derivation of AssignmentActionUsage::referent is wrong SysML 2.0b1 open
SYSML2-490 Actions::acceptSubactions and sendSubactions should subset acceptActions and sendActions SysML 2.0b1 open
SYSML2-28 Validation constraints are missing in the SysML abstract syntax SysML 2.0a1 open
SYSML2-468 binding connector production overly constraining SysML 2.0a1 open
SYSML2-498 validateTriggerInvocationExpressionWhenArgument constraint is wrong SysML 2.0b1 open
SYSML2-305 Message and flow connection ends should be occurrence usages SysML 2.0b1 open
SYSML2-497 validateTriggerInvocationExpressionAfterArgument constraint is too strong SysML 2.0b1 open
SYSML2-491 KerML constraint requires updates to Systems Library models SysML 2.0b1 open
SYSML2-495 Textual notation BNF for TriggerExpression is wrong SysML 2.0b1 open
SYSML2-458 Missing production for connections with an edge on one or both ends SysML 2.0a1 open
SYSML2-492 KerML constraint requires updates to Domain Library models SysML 2.0a1 open
SYSML2-457 Missing graphical BNF production for keyword extension using #key word in guillemet in compartments SysML 2.0a1 open
SYSML2-68 Graphical notation for nested reference usage needs resolution SysML 2.0a1 open
SYSML2-94 Confusing naming in Individual Occurrence example SysML 2.0a1 open
SYSML2-102 Semantic constraint for target of AssignmentActionUsage is missing SysML 2.0a1 open
SYSML2-80 Reflective SysML abstract syntax model has inconsistencies SysML 2.0a1 open
SYSML2-227 Subsections of section 7.7.2.3.7 should be ordered alphabetically SysML 2.0a1 open
SYSML2-38 Textual and graphical notations for flow on connection unclear SysML 2.0a1 open
SYSML2-336 Incorrect notation in example "Individual Occurrence" SysML 2.0b1 open
SYSML2-499 Assignments parsed without a target will fail validateAssignmentActionUsageArguments SysML 2.0b1 open
SYSML2-459 Resolution of approved issue SYSML2-241 is not considered by merged issue SYSML2-240 SysML 2.0b1 open
SYSML2-556 Typos in Quantities and Units Domain Library SysML 2.0b1 open
SYSML2-481 Use of the term 'Feature' SysML 2.0b1 open
SYSML2-536 TestCaseVerifyRequirementUsage_Mapping.ownedRelationship() SysML 2.0a1 open
SYSML2-351 Unnecessary event declaration in example "Message" SysML 2.0b1 open
SYSML2-578 Incorrect graphical notation for message between ports SysML 2.0b1 open
SYSML2-560 Add note on FlowFeature direction to textual notation grammar SysML 2.0b1 open
SYSML2-566 Section containing tables about elements not mapped should get an introductory text SysML 2.0b1 open
SYSML2-577 Incorrect graphical notation for flow connection SysML 2.0b1 open
SYSML2-582 Incorrect graphical notation for flow between actions SysML 2.0b1 open
SYSML2-579 Incorrect graphical notation for flow connections in Flow as Node SysML 2.0b1 open
SYSML2-583 Incorrect graphical notation for successions examples with actions SysML 2.0b1 open
SYSML2-581 Mistakes in example Interface as Node (with flow) SysML 2.0b1 open
SYSML2-611 OCL rule deriveDefinitionOwnedFlow references non-existent class called FlowUsage SysML 2.0b1 open
SYSML2-580 Incorrect and incomplete sequence view with message SysML 2.0b1 open
SYSML2-612 OCL rule deriveUsageNestedFlow references non-existent class called FlowUsage SysML 2.0b1 open
SYSML2-620 Textual notation production for Comment is wrong SysML 2.0b1 open
SYSML2-219 Action::decisionTransitions should subset Action::transitions SysML 2.0a1 open
SYSML2-226 Incorrect reference to SysML v1 to SysML v2 Transformation SysML 2.0a1 open
SYSML2-616 User-defined keywords are not allowed on control nodes SysML 2.0b1 open
SYSML2-599 Wrong production for adding state-def as a definition node SysML 2.0a1 open
SYSML2-529 OCL for deriveViewDefinitionViewCondition and deriveViewUsageViewCondition are wrong SysML 2.0b1 open
SYSML2-597 checkFlowConnectionUsageSpecialization is too restrictive about FlowConnections SysML 2.0b1 open
SYSML2-558 checkStateUsageSpecialization constraint is incorrect SysML 2.0b1 open
SYSML2-552 Errors in the TradeStudy domain model SysML 2.0b1 open
SYSML2-554 Enumeration definitions VerdictKind and VerificationMethodKind are missing from specification document SysML 2.0b1 open
SYSML2-318 Adornments on ends missing in graphical syntax SysML 2.0b1 open
SYSML2-182 Universal features can have many values SysML 2.0a1 open
SYSML2-430 Subsetting of subjectParameter properties is wrong SysML 2.0b1 open
SYSML2-29 Name all associations in the SysML abstract syntax SysML 2.0a1 open
SYSML2-30 Follow typographical conventions in the SysML Metamodel clause SysML 2.0a1 open
SYSML2-158 Example FrontAxle definition SysML 2.0a1 open
SYSML2-159 Example analysis case fuelEconomyAnalysis SysML 2.0a1 open
SYSML2-426 specializesFromLibrary arguments use inconsistent notation for strings SysML 2.0b1 open
SYSML2-626 Incorrect textual notation for TextualRepresentation SysML 2.0b1 open
SYSML2-484 Incorrect textual notation for rep annotation SysML 2.0a1 open
SYSML2-527 The XMI versions of standard libraries should be delivered SysML 2.0a1 open
SYSML2-561 Intersection missing for some multiple specializations SysML 2.0b1 open
SYSML2-562 Tables in overview sections have empty cells SysML v2 column SysML 2.0b1 open
SYSML2-564 Mapping tables in the overview sections show duplicates in the SysML v2 column SysML 2.0b1 open
SYSML2-569 Rename ~InterfaceBlock_Mapping SysML 2.0b1 open
SYSML2-587 The mapping name "~InterfaceBlock_Mapping" is not convenient SysML 2.0a1 open
SYSML2-613 Constraint on Definition variation memberships is too restrictive SysML 2.0b1 open
SYSML2-615 Constraint on Usage variation memberships is too restrictive SysML 2.0b1 open
SYSML2-640 Find a better way to differ between definition and instance elements in graphical notation SysML 2.0b1 open
SYSML2-636 package View and Viewpoint TBD should not be included in the xmi file SysML 2.0b1 open
SYSML2-634 VerificationCase::subVerificationCases is typed incorrectly SysML 2.0b1 open
SYSML2-641 Do not use abbreviations for key word in SysML v2/KerML textual concrete syntax SysML 2.0b1 open
SYSML2-844 Annotation diagram needs to be updated SysML 2.0b1 open
SYSML2-631 User-defined keywords are not allowed on metadata SysML 2.0b1 open
SYSML2-185 ISQ in specification and libraries not aligned SysML 2.0a1 open
SYSML2-85 Effective name is not correct for a redefined perform action usage SysML 2.0a1 open
SYSML2-642 Make orthogonal and rounded corners the default connector style for architectural drawings SysML 2.0b1 open
SYSML2-635 Issues with SysML grammar SysML 2.0b1 open
SYSML2-637 User-defined keywords are not allowed on enumeration definitions SysML 2.0b1 open
SYSML2-643 Comment locale not in textual notation SysML 2.0b1 open
SYSML2-553 checkRequirementUsageObjectiveRedefinition is incorrect SysML 2.0b1 open
SYSML2-783 Parsing KerML Feature elements from SysML textual notation SysML 2.0b1 open
SYSML2-59 Inconsistent graphical notation for succession, message and flow edges SysML 2.0a1 open
SYSML17-649 Metadata - category refers to DCMI abstract (not a category) / dublinCoreTag. Dublin Core Should Only Apply to Artefacts (Documents, Sound, Video, Text) Not any AD Element SysML 1.5 open
SYSML17-648 Metadata, ArchitectureMetadata Incorrect - Metadata Applies to Architecture Description Not Architecture. ArchitectureMetadata duplicates Metadata in application to an AD SysML 1.5 open
SYSML17-647 View Specifications::Summary & Overview::Summary & Overview - Missing Relationships and Triples, Concerns Not Defined SysML 1.5 open
SYSML17-646 UAFElement - Attributes Missing. URI incorrectly defined SysML 1.5 open
SYSML17-645 Figure 9:134 / 8:86 Undefined DMM Elements - Refine, Trace, Refine, Verifiy, Requirement. Requirement not a UAF Element? SysML 1.5 open
SYSML17-644 Figure 9:129 ArchitecturalDescription - Multiplicities Incorrect SysML 1.5 open
SYSML17-643 Figure 8:2 Architecture Views Does Not Conform to ISO/IEC/IEEE 42010 - Multiplicities, Naming, Direction [repeat - Tracker Now Using Correct OMG Identifiers] SysML 1.5 open
SYSML17-642 Figure 8:2 Architecture Views Does Not Conform to ISO/IEC/IEEE 42010 - Multiplicities, Naming, Direction SysML 1.5 open
SYSML17-641 1.1 Introduction - Normative + Informative Identifies Wrong OMG Specifications SysML 1.5 open
SYSML17-640 Typo in brief description about Activity Diagram SysML 1.6 open
SYSML17-639 Element Name Incorrectly Shown as InternalBlockDiagram - Should be Dependency SysML 1.6 open
SYSML17-636 Conform as a Generalization is Incorrect - A View is Not a Viewpoint / 'is a' Does Not Equate to Conform SysML 1.5 open
SYSML17-637 View is not a Viewpoint SysML 1.5 open
SYSML17-500 Artifacts and «document» SysML 1.6 open
SYSML17-638 UML::Artifact is Excluded But Specification Doesn't State With What Documents/Artifacts Are to Be Represented with Instead SysML 1.7b1 open
SYSML17-635 Risk, Source and Verification Method Are Attributes of Any / All Requirements Not Just an Extended Requirement SysML 1.5 open
SYSML17-634 Issues with SysML 1.7 XMI SysML 1.6 open
SYSML17-536 Typo: Constraint name 8 of Adjunct Property (again) SysML 1.6 open
SYSML17-515 Statement about UML semantics of ActivityPartitions is wrong SysML 1.6 open
SYSML17-494 wrong statement about UML semantics of partitions SysML 1.6 open
SYSML17-463 QUDV: Specification of PrefixedUnit should have a QuantityKind SysML 1.6 open
SYSML17-512 Added BehavioralFeatures to AdjuctProperty SysML 1.6 open
SYSML17-365 Meta-ticket: SysML-1.6: Specification body (only) figure inconsistencies and errors and related text inconsistencies SysML 1.6 open
SYSML17-252 ConstraintBlock: abstract syntax consistency SysML 1.6 open
SYSML17-507 wrong name on Figure 9-6 SysML 1.6 open
SYSML17-504 Why are FlowProperties not included in FlowDirectionKind SysML 1.6 open
SYSML17-505 The FeatureDirectionKind to which the constraint belongs is wrong SysML 1.6 open
SYSML17-502 FlowProperties as aggregations SysML 1.6 open
SYSML17-498 NoBuffer: Clarify when a token is considered "refused" SysML 1.6 open
SYSML17-233 Comments in the XMI have no annotated elements SysML 1.6b1 open
SYSML17-265 Stereotype Rate extends ObjectNode in the XMI, but not in the abstract syntax in the specification SysML 1.6 open
SYSML17-490 no longer existing "primaryQuantityKind" shown in diagram E.8 SysML 1.6 open
SYSML17-489 Removes references to UML4SYSML from the SysML diagrams SysML 1.6 open
SYSML17-485 Mentioned stereotype «distributedDefinition» does not exist SysML 1.6 open
SYSML17-488 FinalState should be an exitPoint Pseudostate SysML 1.6 open
SYSML17-487 connector properties should be in compartment SysML 1.6 open
SYSML17-486 Behavioral Ports and Nesting SysML 1.6 open
SYSML17-483 DistributedProperty definition has to be reveiwed SysML 1.6 open
SYSML17-482 The circle plus notation is for members, not ownedElements SysML 1.6 open
SYSML17-481 Consistency with Effects and Ports SysML 1.6 open
SYSML17-479 Association Rules SysML 1.6 open
SYSML17-227 About Block constraint "3" removed by SysML v1.6 SysML 1.6 open
SYSML17-480 Problems with Flows SysML 1.6 open
SYSML17-478 AcceptChangeStructuralFeatureEventAction SysML 1.6 open
SYSML17-467 Implementation of non-normative extensions cannot be used in other OMG specifications SysML 1.6 open
SYSML17-475 move to SystemOfQuantities SysML 1.6 open
SYSML17-474 rename getKindOfQuantitiesForMeasurementUnit SysML 1.6 open
SYSML17-473 OCL is not syntatically correct see ->allUnits() SysML 1.6 open
SYSML17-472 wrongfully copied SysML 1.6 open
SYSML17-471 OCL with SpecializedQuantityKind needs to be changed SysML 1.6 open
SYSML17-469 ControlValue to ControlValueKind SysML 1.6 open
SYSML17-468 Changes to Annex D sample problem figures may impact on some specification body figures SysML 1.6 open
SYSML17-366 Need constraint for inverted provided/required Interfaces (InterfaceRealization and Usage) on ~InterfaceBlock SysML 1.6 open
SYSML17-464 Constraint Typos SysML 1.6 open
SYSML17-454 QUDV: Unknown property primaryQuantityKind SysML 1.6 open
SYSML17-462 SysML model URI in the specification document SysML 1.6 open
SYSML17-455 Suggest capability to list :features on Pin symbols and on elided Pin "ObjectNode" rectangle symbol SysML 1.6 open
SYSML17-456 Suggest capability to list :features on ItemFlows in a rectangle symbol over a Connector or Association line SysML 1.6 open
SYSML17-357 Suggest introduce strict diagram policy: avoid "elided Pin" ObjectNode notation in Activity Diagrams in all revised and future specification figures SysML 1.6 open
SYSML17-438 Body conditions of operation in QUDV model should be Boolean expressions SysML 1.6 open
SYSML17-437 QUDV::PrefixedUnit: Redefinition of quantityKind SysML 1.6 open
SYSML17-430 Issues in figure E-7 SysML 1.6 open
SYSML17-414 7_composition_acyclic wrong SysML 1.6 open
SYSML17-351 If there is no «port» keyword in UML-2.5.1 or SysML-1.6 it should be removed from Figure 9-8 SysML 1.6 open
SYSML17-408 orderedMember in ElementGroup should be {ordered} SysML 1.6 open
SYSML17-406 AbstractRequirement needs to be consistent SysML 1.6 open
SYSML17-405 Description for getSatisfies SysML 1.6 open
SYSML17-404 Parameter names mismatch in ~InterfaceBlock::areConjugated(Property, Property) SysML 1.6 open
SYSML17-401 Suggest introduce an operation to obtain the magnitude of a value property in a given compatible Unit (to afford equality comparison) SysML 1.6 open
SYSML17-399 Taken literally the text and OCL of constraint '6_valueproperties_composite' imply that every FlowProperty typed by a ValueType should have AggregationKind 'composite' SysML 1.6 open
SYSML17-400 Property types 'Four general categories of properties of blocks are recognized in SysML ...' does not cover FlowProperty SysML 1.6 open
SYSML17-367 InterfaceBlock: OCL constraint 2_no_part is missing FlowProperty check for cases where a FlowProperty is not typed by a ValueType SysML 1.6 open
SYSML17-395 Compartments for Connectors and Participants SysML 1.6 open
SYSML17-394 Suggest not allow an AssociationBlock to type a BindingConnector used for pure proxying SysML 1.6 open
SYSML17-386 All kinds of errors in Fig. 8-17 SysML 1.6 open
SYSML17-348 Figure 8-17: Vehicle specialization: multiple inconsistencies SysML 1.6 open
SYSML17-388 constraint needed SysML 1.6 open
SYSML17-393 Relationship should be specified for Stakeholder to a View SysML 1.6 open
SYSML17-392 Adjunct allows for additional notation on CallBehaviorActions SysML 1.6 open
SYSML17-391 What are redefined BoundReferences SysML 1.6 open
SYSML17-390 EndPathMultiplicity and BoundReference Ordered and Unique SysML 1.6 open
SYSML17-389 Lower and Upper Explained SysML 1.6 open
SYSML17-387 Lower and Upper are constrained SysML 1.6 open
SYSML17-385 Statement about EndPathMultiplicity SysML 1.6 open
SYSML17-384 BoundReference Specificity SysML 1.6 open
SYSML17-383 BoundReference Diagram is wrong SysML 1.6 open
SYSML17-382 Unclear English Statement SysML 1.6 open
SYSML17-377 Make Annex E Optional but Normative SysML 1.6 open
SYSML17-372 Figure E.6 QUDV Units Diagram display exactly the same content as Figure E.5 QUDV Concepts Diagram SysML 1.6 open
SYSML17-347 The 'initialValues' compartment needs to be renamed 'contextValues' and they need to be referred to as 'context-specific values' SysML 1.6 open
SYSML17-371 Suggest primary/replica as alternative to master/slave terminology for Copy relationship SysML 1.6 open
SYSML17-370 SysML-1.6: Refers to both 'composite requirement' and 'compound requirement' SysML 1.6 open
SYSML17-369 BindingConnector constraint 1_compatible_types: Use of OCL conformsTo contradicts definition of compatibility of connected ProxyPort, does not admit per Feature compatibility or compatibility via a union of connected features SysML 1.6 open
SYSML17-368 9.3.2.13 ProxyPort 'When a proxy port is connected to a single internal part ...' extend to include ' or port on an internal part' SysML 1.6 open
SYSML17-361 SysML-1.6: text on Requirement 'Test and procedure conditions' is mangled in 'Figure 16-2: Requirements Derivation' (was OK in SysML-1.5) [also affects Figure 16-6] SysML 1.6 open
SYSML17-362 'Figure 16-2: Requirements Derivation' indeed shows DeriveReqt but spec text refers to it as 'an example of a compound requirement' SysML 1.6 open
SYSML17-349 'Figure 9-6: Usage example of ports with provided and required features' does not expose any directed features SysML 1.6 open
SYSML17-350 SysML-1.6 does not leverage redefinition of 'sp:Surface' on 'Figure 9-7: Usage example of proxy and full ports'. And does not show direction of flows on Ports symbols SysML 1.6 open
SYSML17-352 Figure 9-16 and Figure 9-17 'Usage example of item flow decomposition': multiple inconsistencies SysML 1.6 open
SYSML17-353 The ControlValue input to Monitor Traction without a Pin is invalid in 'Figure 11-10: Continuous system example 1' and multiple issues with ControlOperator SysML 1.6 open
SYSML17-354 Edge for [else] in 'Figure 11-11: Continuous system example 2' should be an ObjectFlow not a ControlFlow SysML 1.6 open
SYSML17-364 Suggest additional main body figure illustrating context-specific values (initialValues) compartment used for deep system configuration SysML 1.6 open
SYSML17-329 Inconsistent incoming ObjectFlow and outgoing ControlFlows on the DecisionNode in Figure 11.12 - Continuous system example 3 'Enable on Brake Pressure > 0' SysML 1.6 open
SYSML17-356 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not allocate to a FlowProperty and multiple other minor issues SysML 1.6 open
SYSML17-360 Fig D.41 should be bdd with instance specs & slot values, not ibd with default values SysML 1.6 open
SYSML17-363 SysML-1.6: DeriveReqt: OCL constraint directions client vs supplier SysML 1.6 open
SYSML17-358 Trivial: consistency: Either show the [metaclass] on all Stereotype symbols or none in 'Figure 16-1: Abstract Syntax for Requirements Stereotypes' SysML 1.6 open
SYSML17-339 Figure D.24 Parametric Diagram does not explicitly show «equal» keyword or '=' on BindingConnectors SysML 1.6 open
SYSML17-344 Typo: 'not' should be 'nor' in '... not is this always even desirable' SysML 1.6 open
SYSML17-343 Typo: references to FuelTankAssy should be FuelTankAssembly for consistency with Figure D.25 SysML 1.6 open
SYSML17-334 Typo: 'Various other model elements may be necessary to help develop a derived requirement, and these model element' plural missing SysML 1.6 open
SYSML17-336 Typo: Missing end parentheses bracket: '(described in D.4.3 Elaborating Behavior (Sequence and State Machine Diagrams)' SysML 1.6 open
SYSML17-330 Typo: 'with is owned by the AutomotiveDomain block.' SysML 1.6 open
SYSML17-342 Need Connector from fuel:Fuel to :FuelPump in 'Figure D.25 Detailed Internal Structure of Fuel Delivery Subsystem (Internal Block Diagram)' SysML 1.6 open
SYSML17-341 Naming inconsistencies 'Figure D.24 is a parametric diagram showing how fuel flowrate is related to FuelDemand and FuelPressure value properties.' SysML 1.6 open
SYSML17-338 Figure D.23 has FuelFlow stereotyped by the DEPRECATED «flowSpecification» SysML 1.6 open
SYSML17-332 'Figure D.7 - Elaborating Black Box Behavior' some OCL missing, State names in oclInState() should be capital first letter, and display of name of alt fragment SysML 1.6 open
SYSML17-345 SysML-1.6: Figure D.25 has the type Fuel for both an in Port and an out Port on FuelTankAssembly (and it is not ideal to have same name as the Classifier that flows) SysML 1.6 open
SYSML17-346 7.3.2.3 Expose refers to 'The method' without referencing Viewpoint SysML 1.6 open
SYSML17-340 Typo: 'Binding connectors, as defined in Clause 8 are used ...' missing comma SysML 1.6 open
SYSML17-333 Typo: 'Deleting the container requirement deleted the nested requirements, a functionality inherited from UML.' should be 'deletes' SysML 1.6 open
SYSML17-337 Typo: 9.3.2.8 FlowProperty 'A flow propertys values' SysML 1.6 open
SYSML17-335 For Connectors in IBD Figure D.4 to be typed by implied anonymous Associations need define them in BDD Figure D.15 between 'HybridSUV' and: 'Driver', 'Maintainer', 'Passenger', 'Baggage', 'Environment' SysML 1.6 open
SYSML17-331 In Figure D.2 Real appears to be owned by the Automotive Value Types ModelLibrary (with no explicit ElementImport) SysML 1.6 open
SYSML17-307 Lots of ControlValues that should be ControlValueKinds SysML 1.6 open
SYSML17-319 It should not be allowed to modify an AdjunctProperty SysML 1.6 open
SYSML17-316 Duplicated sentence SysML 1.6 open
SYSML17-315 Unexpected word 'Figure' in Figure 4-2 name SysML 1.6 open
SYSML17-314 Unexpected section number SysML 1.6 open
SYSML17-313 Clarify that contraint parameters are value properties SysML 1.6 open
SYSML17-308 7_cannot_redefine_boundreference is too constrained SysML 1.6 open
SYSML17-306 Aggregation multiplicities not correct SysML 1.6 open
SYSML17-300 SysML 1.6 statement is too strong SysML 1.6 open
SYSML17-299 Caveat is not specific for UseCases SysML 1.6 open
SYSML17-293 Introduction to 9.1.3 Proxy Ports and Full Ports might be interpreted as SysML only permitting Full and Proxy Ports (not standard ports) SysML 1.6 open
SYSML17-298 Continuous and Discrete need to be on FlowProperties as well SysML 1.6 open
SYSML17-296 No Creation and Destruction Event in Current UML SysML 1.6 open
SYSML17-295 Figure 9.5 missing, duplicates 9.4 SysML 1.6 open
SYSML17-290 Remove reference to non-existing properties allocatedFrom and allocatedTo SysML 1.6 open
SYSML17-286 Remove notation form ActorPart SysML 1.6 open
SYSML17-284 Conjugation Stereotype SysML 1.6 open
SYSML17-285 is the stereotype <<~InterfaceBlock>> SysML 1.6 open
SYSML17-283 Need Bound References Compartment SysML 1.6 open
SYSML17-274 Parameters and Variables don't make sense SysML 1.6 open
SYSML17-248 The definition of AdjunctProperty SysML 1.6 open
SYSML17-234 QUDV library inconsistently uses SysML::Libraries::PrimitiveValueTypes SysML 1.6b1 open
SYSML17-278 AbstractRequirement: direction of /tracedTo wrong in Attributes description SysML 1.6 open
SYSML17-277 Description of getRefines() has typo and inconsistent singular vs plural SysML 1.6 open
SYSML17-276 Description of getRefines() restricts returned elements to AbstractRequirement [0..*] but the OCL static query does not (effectively NamedElement [0..*]) SysML 1.6 open
SYSML17-275 Parts is too restrictive SysML 1.6 open
SYSML17-273 Missing guard brackets in example activity diagram 11-12 SysML 1.6 open
SYSML17-261 How to interpret non-Navigation SysML 1.6b1 open
SYSML17-258 No changebars in SysML 1.6b1 open
SYSML17-257 Proposal: patent-friendly part/element numbering system with compliant solid line SysML 1.6b1 open
SYSML17-250 Should <> have a capital V? SysML 1.6b1 open
SYSML17-249 Duplicate Elements in Table SysML 1.6b1 open
SYSML17-243 Refine / Trace relationship operations are too restrictive SysML 1.6b1 open
SYSML17-242 VerdictKind should also have the literal none SysML 1.6b1 open
SYSML17-231 ProxyPort property "matching" SysML 1.6 open
SYSML17-229 cannot model and validate physical connections SysML 1.4 open
UMLR-104 Section: Chapter: 7.3.2.4 View SysML 1.0 open
UMLR-140 Section: Activities SysML 1.0 open
UMLR-141 Callout notation for many clients/suppliers SysML 1.0 open

Issues Descriptions

State machine graphical notation for entry/exit/do actions incosistent

  • Status: open  
  • Source: sodiuswillert.com ( Mr. Eran Gery)
  • Summary:

    Current GBNF uses the textual notation to represent state entry/do/exit actions within a "state actions" compartment.
    This does not allow to describe state actions in a graphical way and also requires the graphical modeler to use more extended textual syntax.

  • Reported: SysML 2.0b2 — Thu, 20 Jun 2024 12:44 GMT
  • Updated: Thu, 20 Jun 2024 12:44 GMT

Inconsistencies in the graphical notation for "expose"

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:
    1. In 7.25.1 Views and Viewpoints Overview, Table 23. Views and Viewpoints – Representative Notation, the example for "Expose" renders the expose relationship using a dashed arrow. However, in 8.2.3.25 Views and Viewpoints Graphical Notation, the graphical BNF production expose-relationship shows the arrow as being solid.
    2. An expose relationship is a kind of import and, as such, can expose a single membership or the content of a namespace, and can optionally be recursive. The textual BNF production Expose in 8.2.2.25.2 View Usages allows all these options, as does the graphical BNF production expose-compartment-element (for showing an expose declaration in a compartment) in 8.2.3.25 Views and Viewpoints Graphical Notation. However, the graphical graphical BNF production expose-relationship does not.
    3. The textual BNF production Expose allows a VisibilityIndicator on an expose declaration, as does the graphical BNF production expose-compartment-element. However, the graphical BNF production expose-relationship does not.
  • Reported: SysML 2.0b2 — Thu, 30 May 2024 14:46 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT
  • Attachments:

isOrdered and isUnique are missing from the reflective abstract mapping

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The mapping given in 9.2.21 from the MOF abstract syntax model to the reflective SysML abstract syntax model is missing instructions for what to do if a property is ordered or non-unique. Therefore, appropriate annotations for these are missing from the normative SysML.sysml file.

  • Reported: SysML 2.0b2 — Mon, 27 May 2024 19:34 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

Update language description and concrete syntax related to imports

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The resolutions by the KerML FTF to the following issues make restrictions to the functionality of imports in KerML and hence, by reference, in SysML, also:

    • KERML_-73 Disallow public imports at root level
    • KERML_-74 Make imports private by default
    • KERML_-75 Restrict the functionality of recursive import

    The discussion of imports in Clause 7 Language Description need to be updated to reflect these changes (particularly in 7.5.3 Imports). In addition, adopting the requirement to always show visibility of imports in the concrete syntax, consistent with KERML_-74, requires changes in

    • 8.2.2.5.1 Packages (textual notation)
    • 8.2.3.5 Namespaces and Packages Graphical Notation
    • 8.3.5 Namespaces and Packages Abstract Syntax, Figure 5 Namespaces
  • Reported: SysML 2.0b2 — Sun, 26 May 2024 21:27 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT
  • Attachments:

Missing guidance on highlighting keywords

  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    The KerML specification contains guidance for tooling to highlight keywords in concrete textual notation. KerML subclause 8.2.2.6 specifically says:

    Tooling for the KerML textual notation should generally highlight keywords relative to other text, for example by using boldface and/or distinctive coloring. However, while keywords are shown in boldface in this specification, the specification does not require any specific highlighting (or any highlighting at all), and KerML textual notation documents are expected to be interchanged as plain text (see also Clause 10 on Model Interchange).

    A similar statement, modified for SysML, should be added, probably as a last paragraph under subclause 8.2.2.1.2, including a cross-reference to KerML. For SysML the same guidance applies to textual snippets used in the Graphical Notation.

  • Reported: SysML 2.0b2 — Mon, 20 May 2024 09:37 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

Error in the specification of "connections"

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    In the SysML Specification, 9.2.6.2.4 connections, the base connection usage connections is specified as being a ConcernUsage under "Elements". This should, instead, be ConnectionUsage. (Note that this error is only in the document, and connections is declared correctly in the Connections.sysml model file.

  • Reported: SysML 2.0b2 — Sat, 4 May 2024 20:16 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

Incorrect enumeration example

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The following example appears in 7.8.2 Enumeration Definitions and Usages:

    enum def ConditionColor { red; green; yellow; } 
    attribute def ConditionLevel {
        attribute color : ConditionColor; 
    }
    enum def RiskLevel :> ConditionLevel {
        enum low { color = ConditionColor::green; } 
        enum medium { color = ConditionColor::yellow; } 
        enum high { color = ConditionColor::red; }
    }
    

    This is example is not valid, because the color features defined in the enumerated values will have name conflicts with the color feature inherited from ConditionLevel. The intent was probably to have the color features in the enumerated values redefine ConditionLevel::color, but that is currently missing from the example.

  • Reported: SysML 2.0b2 — Thu, 2 May 2024 21:34 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

There is no need for AnalysisAction

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The Systems Library model AnalysisCases includes a declaration for AnalysisAction as a specialization of Actions::Action. In the abstract syntax, ActionDefinition::analysisSteps and ActionUsage::analysisSteps are derived to be the subactions that are AnalysisActions.

    However, no special semantics are specified for AnalysisActions and no special concrete syntax for defining analysisSteps. So they are never used in practice within user models of analysis caes, so they seem pointless.

  • Reported: SysML 2.0b2 — Wed, 1 May 2024 22:44 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

StateAction::substates has an implied subsetting of exclusiveStates

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    According to the constraint checkStateUsageExclusiveStateSpecialization (in 8.3.17.6), a substate of a non-parallel owning state definition or usage must specialize StateAction::exclusiveStates (at least according to the description of the constraint; the OCL is wrong, see SYSML2_-183). However, the feature StateAction::substates actually meets the requirements for the application of checkStateUsageExclusiveSpecialization, which means that it has an implied specialization of exclusiveStates. But exclusiveStates already subsets substates (at least according to the library model in States.sysml; the feature exclusiveStates seems to be missing from subclause 9.2.10.2.1 StateAction), so this would mean that all substates are exclusiveStates, which is, of course, incorrect for the semantics of parallel states.

  • Reported: SysML 2.0b2 — Wed, 1 May 2024 20:57 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

checkStateUsageExclusiveStateSpecialization and checkStateUsageSubstateSpecialization have problems

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    In 8.3.17.6 StateUsage:

    1. The constraint checkStateUsageExclusiveStateSpecialization has the description

      A StateUsage that is a substate usage with a non-parallel owning StateDefinition or StateUsage must directly or indirectly specialize the StateUsage States::State::exclusiveStates from the Systems Model Library.

      However, the OCL for the constraint actually checks for the owning state being parallel (rather than non-parallel) and requires specialization of substates rather than exclusiveStates.

    2. The constraint checkStateUsageSubstateSpecialization has the description

      A StateUsage that is a substate usage with a owning StateDefinition or StateUsage that is parallel must directly or indirectly specialize the StateUsage States::State::substates from the Systems Model Library.

      However, the OCL for the constraint actually checks for the owning state being non-parallel (rather than parallel).

    3. The operation isSubstateUsage used in the above constraints has the description

      Check if this StateUsage is composite and has an owningType that is an StateDefinition or StateUsage with the given value of isParallel, but is not an entryAction or exitAction. If so, then it represents a StateAction that is a substate or exclusiveState (for isParallel = false) of another StateAction.

      However, the OCL for the operation actually does not check if the state usage is composite and also excludes do actions (in addition to entry and exit actions).

  • Reported: SysML 2.0b2 — Wed, 1 May 2024 20:43 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

Guillemets should not be used on keywords in textual notation snippets used in the graphical notation

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Keywords introduced in the graphical notation BNF are surrounded by guillemets («...»). However, the graphical notation also uses snippets of textual notation in many places, often by referencing productions from the textual notation BNF, which does not put guillemets around keywords. In some cases, though, the graphical BNF will include productions for text that introduce keywords that parallel the textual notation, but don't directly use textual notation BNF productions. The resolution to SYSML2-59 includes such productions for message-label and flow-label that include the «of» keyword surrounded by guillemets, but other such productions in the graphical BNF do not put guillemets around keywords. There needs to be a consistent rule on how guillemets are to be used in the graphical notation.

  • Reported: SysML 2.0a1 — Fri, 22 Dec 2023 23:11 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

Missing production for use case actors and subject

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Right now use-case nodes cannot be associated with actors and subjects. They need to be made subject/actor stakeholders

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 12:20 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

GBNF for flow connection not mapped to semantics

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Graphical BNF specifies a flow connection. It is not clearly mapped to a semantic language concept. Should it be merged with a message specified as part of occurences?

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 11:15 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

Symbol for metadata def is missing

  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    Add support for defining a metadata definition using the normal definition symbol (e.g., key word metadata def with metadata def name in name compartment). Separate compartment for attribute declarations. Add compartment redefined the annotated elements so they are constrained to be of a certain metaclass. (Note that MetadataDefinition is a kind of ItemDefinition but MetadataFeature (and therefore MetadataUsage) is a kind of AnnotatingElement.)

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:09 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT
  • Attachments:

No support for metadata definition in graphical notation


Missing explicit explanation of compartments as views

  • Key: SYSML2_-11
  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    There should be explicit specification and explanation, that a diagram and a compartment are views, as well as clarification on how the filter notation can be applied to a view compartment and to a diagram. Consider an extension to the filter notation.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:01 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

incorrect naming of * character

  • Key: SYSML2_-3
  • Status: open  
  • Source: Dassault Systemes ( Mr. Daniel Brookshier)
  • Summary:

    Throughout the document, we need consistent and formal language; for the * character, use 'asterisk' instead of 'star' for the character *.

  • Reported: SysML 2.0b1 — Thu, 8 Feb 2024 18:14 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

incorrect naming of * character

  • Key: SYSML2_-2
  • Status: open  
  • Source: Dassault Systemes ( Mr. Daniel Brookshier)
  • Summary:

    Throughout the document, need consistent and formal language; for the * character, use 'asterisk' instead of 'star' for the character *.

  • Reported: SysML 2.0b1 — Thu, 8 Feb 2024 18:16 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

Issues with SysML/KerML grammar

  • Key: SYSML2_-1
  • Status: open  
  • Source: itemis AG ( David Akehurst)
  • Summary:

    I raised a number of issues previously with regards to detailed/specific problems with the KerML textual syntax grammar.
    A more general issue is that I find the grammar (as written) hard to digest.
    It is not modular, and the chapters don't seem to relate fully to the Abstract Syntax packages.

    I have created an alternative grammar, using a different grammar-syntax, that allows for modular definition of grammars.
    I would like to offer you this.
    However, I cannot attach files to this issue!
    feel free to contact me if you would like me to provide them.

    In summary, one can modularise the KerML grammar into a Kernel, Core, Root (groups/packages)
    with each group/package containing 3-5 grammar modules and extension relationships to combine them.

    I plan to do the same for the full SysML grammar (later).

  • Reported: SysML 2.0b1 — Wed, 14 Feb 2024 11:32 GMT
  • Updated: Tue, 18 Jun 2024 00:01 GMT

TransitionUsage source and target properties do not support feature chains

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    According to the SysML abstract syntax (8.3.17.9 TransitionUsage), the source and target of a TransitionUsage must be ActionUsages. However, the textual notation (8.2.2.17.3 Transition Usages) allows sources and targets to be feature chains, which are parsed as a KerML Feature with FeatureChaining relationships to the chained Features, which are not ActionUsages.

  • Reported: SysML 2.0b2 — Sun, 16 Jun 2024 22:17 GMT
  • Updated: Sun, 16 Jun 2024 22:17 GMT

Default multiplicities are not formally specified

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    In the SysML Specification, in non-normative Language Description subclause 7.6.3 Usages, it describes several conditions that, if meet, require a usage to have default multiplicity 1..1. However, there is no formal specification of this in the normative Clause 8 Metamodel.

  • Reported: SysML 2.0b2 — Sat, 15 Jun 2024 17:52 GMT
  • Updated: Sat, 15 Jun 2024 17:52 GMT

Replace Generic mapping classes by Initializers

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    The coexistence of both the "GenericTo*_Mapping" classes and the Initializer classes generates a significant number of redundancies in the model, and make it harder to understand and to maintain.

    More specifically it makes the management of redefinitions much more complex with a very negative impact on the clarity of the specification.

    In order to fix that, all the GenericTo*_Mapping classes shall be removed and replaced par their Initializer class equivalent in an appropriate way.

  • Reported: SysML 2.0b2 — Sat, 15 Jun 2024 10:33 GMT
  • Updated: Sat, 15 Jun 2024 10:34 GMT

Flow connections are incorrectly both structure and behavior

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    According to the KerML specification, "Structures and behaviors do not overlap". Consistent with this, the approved resolution to KERML-43 added validations to disallow a structure from specializing a behavior and vice versa.

    ConnectionDefinitions in SysML are kinds of PartDefinitions, which are (indirectly) kinds of KerML Structures. But FlowConnectionDefinitions are both ConnectionDefinitions and ActionDefinitions, and ActionDefinitions are kinds of KerML Behaviors. This means that FlowConnectionDefinitions are both Structures and Behaviors, violating the restrictions of KerML.

    As a result, the specializations in the declarations of MessageConnection and FlowConnection in the Systems Library model Connections now violate the new validateStructureSpecialization and validateBehaviorSpecialization constraints added by the resolution to KERML-43.

  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 17:04 GMT
  • Updated: Tue, 11 Jun 2024 19:04 GMT

InterfaceBlock mapped to PortDefinition, but ConjugatedPortDefinition is not generated

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    A SysMLv1::InterfaceBlock is mapped to a SysMLv2::PortDefinition, but the owned SysMLv2::ConjugatedPortDefinition is not generated.

  • Reported: SysML 2.0b2 — Fri, 10 May 2024 16:26 GMT
  • Updated: Sat, 1 Jun 2024 20:05 GMT

Mapping of State does not consider orthogonal states

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    A state with several regions should be mapped to a parallel state.

  • Reported: SysML 2.0b2 — Thu, 30 May 2024 16:07 GMT
  • Updated: Thu, 30 May 2024 16:08 GMT

Missing production for use case actors and subject


Need to complete and align flow and message notations in GBNF

  • Key: SYSML2-557
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    The graphical notation lacks clear differentiation between the various types of flows in the language: flow, succession flows, and message flow (see also SYSML2-59).
    In addition, the BNF was overly restrictive and did not allow flow connections on structural diagrams, except for flows on connections.
    Flows on connections also need to include messages and succession flows.
    It needs to be corrected in the BNF in the relevant clauses
    8.2.3.9 - Occurrences (SD notation)
    8.2.3.13 - Connections
    8.2.3.14 - Interfaces
    8.2.3.16 - Actions

  • Reported: SysML 2.0a1 — Wed, 29 Nov 2023 15:00 GMT
  • Updated: Sat, 25 May 2024 21:02 GMT

Editorial errors in constraints

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:
    1. In 8.3.6.4 Usage, the name of valideaUsageVariationIsAbstract should be validateUsageVariationIsAbstract.
  • Reported: SysML 2.0b2 — Wed, 22 May 2024 19:31 GMT
  • Updated: Wed, 22 May 2024 19:36 GMT

Structured actions not properly covered by GBNF and notation tables

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    GBNF and notation tables only cover a generic "loop action" which is not aligned with the textual syntax that has 3 specific structured actions:

    • while loop action
    • for loop action
    • if/else action

    Each one of the above has a specific textual syntax, that the graphical syntax should align with, to enable proper graphical modeling of actions.

  • Reported: SysML 2.0b2 — Sun, 12 May 2024 16:43 GMT
  • Updated: Wed, 22 May 2024 19:21 GMT

Confusing send/accept examples in notation tables

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    The notation tables show various permutations of send/receive actions with various parameter options. They are all shown against a single simple textual example. It is unclear what is the purpose of rationale each permutation.
    Graphical Examples need to align with corresponding text examples.

  • Reported: SysML 2.0b2 — Mon, 13 May 2024 13:29 GMT
  • Updated: Wed, 22 May 2024 19:20 GMT

InitialState is mapped to StateUsage, but should be an empty ActionUsage

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    The InitialState should be mapped to an empty ActionUsage owned by a StateSubactionMembership relationship.

  • Reported: SysML 2.0b2 — Tue, 21 May 2024 05:40 GMT
  • Updated: Tue, 21 May 2024 05:40 GMT

Transformation of UML4SysML::State does not consider entry, do, and exit behavior

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    The transformation ignores the entry, do, and exit behavior of a state.

  • Reported: SysML 2.0b1 — Wed, 27 Sep 2023 21:38 GMT
  • Updated: Sat, 11 May 2024 08:45 GMT

Mapping of ObjectFlows with ForkNodes

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    In SysML v1, an output value of an action that is an input value of more than one action, is often modeled by an object flow and fork node which create object tokens pointing to the value.

    The mapping of ObjectFlow in combination with ForkNodes is not covered yet by the transformation.

  • Reported: SysML 2.0b1 — Mon, 24 Jul 2023 13:16 GMT
  • Updated: Thu, 9 May 2024 15:12 GMT

Inconsistent use of guillemets in graphical notation for metamodel aspects

  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    The graphical notation makes use of enclosing guillemets to mark up presentation of the metaclass as well as possible metaproperties and metamodel extensions of a model element (i.e., their mapping to the SysML abstract syntax or metamodel). However, there are inconsistencies in their application. The following graphical BNF productions are affected:

    • -name-compartment productions,
    • -edge and -relationship productions,
    • productions including user-defined keywords that extend the metamodel.

    Currently, metaproperties of a metaclass are treated in different ways. E.g. in a -name-compartment the isAbstract metaproperty is presented as a leading '«abstract»' literal with its own guillemets, while the isReference metaproperty is included in the main metaclass presentation, e.g., '«ref part»'.

    A single, consistent rule should be established for all graphical BNF productions that concern presentation of metamodel information.

  • Reported: SysML 2.0b2 — Thu, 9 May 2024 10:42 GMT
  • Updated: Thu, 9 May 2024 14:11 GMT

Transformation does not cover SysMLv1::FlowProperty

  • Key: SYSML2_-76
  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    The transformation does not specify mapping rules for SysMLv1::FlowProperty.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:49 GMT
  • Updated: Sat, 27 Apr 2024 09:57 GMT

Transformation of UML4SysML::ActivityFinalNode is not specified yet

  • Key: SYSML2_-44
  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    The mapping of a UML4SysML::ActivityFinalNode is not covered by the transformation rules.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:04 GMT
  • Updated: Mon, 15 Apr 2024 18:45 GMT

Semantic constraints missing for shorthand succession notation

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The following cases in the textual notation allow "shorthand" then notations for SuccessionAsUsages:

    1. In 8.2.2.9.3 Occurrence Successions, the production SourceSuccession creates a SuccessionAsUsage that has a source end with no related feature and no target end.
    2. In 8.2.2.16.7 Action Successions, the production TargetSuccession creates a SuccessionAsUsage that has a source end as in SourceSuccession, but it has a full ConnectorEndMember for its target end, including an explicit related element.

    In both cases, the intent is that the implied related feature of the source end of the SuccessionAsUsage is a feature lexically previous to the declaration of the SuccessionAsUsage. In the first case, the implied related feature for the target end of the SuccessionAsUsage is a feature lexically following the SuccessionAsUsage. However, there are no semantic constraints given in 8.3.13.8 SuccessionAsUsage to enforce these implied relationships.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 17:12 GMT
  • Updated: Mon, 15 Apr 2024 18:45 GMT

Reuse of KerML textual notation productions in the SysML grammar

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The reuse of KerML BNF productions in the SysML textual notation grammar is not described sufficiently. It is not clear which productions are reused and which not. Reused productions are simply missing from the SysML definitions.

    (This issue was originally reported as part of SYSML2-635.)

  • Reported: SysML 2.0b1 — Fri, 19 Jan 2024 23:51 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Long-form notation for bindings and successions

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The genera textual notation for (binary) connections (see 8.2.2.13.1 Connection Definition and Usage) allows for both a "short form" (connect...to...;) and a "long form", in which the ends are explicitly declared within the connection body. The notations for binding connections (see 8.2.2.13.2 Binding Connectors) and successions (see 8.2.2.13.3 Successions) also have their own "short forms" (bind...=...; and first...then...;)). However, even though both notations allow for connection bodies, the short-form part is required, so it is not possible to declare the ends within the bodies. (Note that the corresponding KerML notations do allow fully "long form" declarations for bindings and successions; see 8.2.5.5.2 and 8.2.5.5.3 in the KerML specification.)

  • Reported: SysML 2.0b1 — Tue, 2 Jan 2024 20:04 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Change graphical notation for use cases to elliptic elements

  • Status: open  
  • Source: MDD4All ( Dr. Oliver Alt)
  • Summary:

    In the SysML v2 the graphical notation for use cases is a box with rounded corners containing the stereotype "use case" and the use case name.
    From the very beginning of UML and SysML v1.x use cases are visualized as elliptic elements. Nearly all people that have ever used or seen UML or SysML in the past are familiar with that notation. So why change it for SysML v2 here? It is not necessary from my perspective.
    A box with many textual things inside is not a good idea for a graphical language. Graphical languages should use as less text as possible. Instead they should use different graphical shapes, different stroke widths, stroke types and icons to express the semantics and what is modeled.
    A user should be able to recognize a diagram element on a first side, looking at a diagram drawing form far away. It should not be necessary to read all details to recognize that is a use case diagram and not any other diagram by reading the stereotype text elements first!

  • Reported: SysML 2.0b1 — Tue, 16 Jan 2024 11:46 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Guillemets are not used on keywords in textual notation snippets used in the graphical notation

  • Key: SYSML2-629
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Keywords introduced in the graphical notation BNF are surrounded by guillemets («...»). However, the graphical notation also uses snippets of textual notation in many places, often by referencing productions from the textual notation BNF, which does not put guillemets around keywords. In some cases, though, the graphical BNF will include productions for text that introduce keywords that parallel the textual notation, but don't directly use textual notation BNF productions. The resolution to SYSML2-59 includes such productions for message-label and flow-label that include the «of» keyword surrounded by guillemets, but other such productions in the graphical BNF do not put guillemets around keywords. There needs to be a consistent rule on how guillemets are to be used in the graphical notation.

  • Reported: SysML 2.0a1 — Fri, 22 Dec 2023 23:11 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Reuse of KerML textual notation productions in the SysML grammar

  • Key: SYSML2-686
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The reuse of KerML BNF productions in the SysML textual notation grammar is not described sufficiently. It is not clear which productions are reused and which not. Reused productions are simply missing from the SysML definitions.

    (This issue was originally reported as part of SYSML2-635.)

  • Reported: SysML 2.0b1 — Fri, 19 Jan 2024 23:51 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Long-form notation for bindings and successions

  • Key: SYSML2-632
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The genera textual notation for (binary) connections (see 8.2.2.13.1 Connection Definition and Usage) allows for both a "short form" (connect...to...;) and a "long form", in which the ends are explicitly declared within the connection body. The notations for binding connections (see 8.2.2.13.2 Binding Connectors) and successions (see 8.2.2.13.3 Successions) also have their own "short forms" (bind...=...; and first...then...;)). However, even though both notations allow for connection bodies, the short-form part is required, so it is not possible to declare the ends within the bodies. (Note that the corresponding KerML notations do allow fully "long form" declarations for bindings and successions; see 8.2.5.5.2 and 8.2.5.5.3 in the KerML specification.)

  • Reported: SysML 2.0b1 — Tue, 2 Jan 2024 20:04 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Change graphical notation for use cases to elliptic elements

  • Key: SYSML2-639
  • Status: open  
  • Source: MDD4All ( Dr. Oliver Alt)
  • Summary:

    In the SysML v2 the graphical notation for use cases is a box with rounded corners containing the stereotype "use case" and the use case name.
    From the very beginning of UML and SysML v1.x use cases are visualized as elliptic elements. Nearly all people that have ever used or seen UML or SysML in the past are familiar with that notation. So why change it for SysML v2 here? It is not necessary from my perspective.
    A box with many textual things inside is not a good idea for a graphical language. Graphical languages should use as less text as possible. Instead they should use different graphical shapes, different stroke widths, stroke types and icons to express the semantics and what is modeled.
    A user should be able to recognize a diagram element on a first side, looking at a diagram drawing form far away. It should not be necessary to read all details to recognize that is a use case diagram and not any other diagram by reading the stereotype text elements first!

  • Reported: SysML 2.0b1 — Tue, 16 Jan 2024 11:46 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

PortUsage direction

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The direction of a PortUsage can be specified like that of any other feature. However, this does not really seem to make sense. The direction of a PortUsage should be determined by the direction of features within it, consistent with the visualization of directions on ports shown, e.g., in the Representative Notation table in 7.11.1 Parts Overview.

  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 18:15 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Transformation fails on Enumerations that are ValueTypes

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Both Enumeration and ValueType have main mappings and their specified filters do prevent a double match

  • Reported: SysML 2.0a1 — Wed, 6 Dec 2023 20:41 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Enumerations not specializable

  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    [From Mr. Ryan Noguchi] In the SysML v2 spec, section 7.8.1:

    An enumeration definition may not specialize another enumeration definition. This is because the semantics of specialization require that the set of instances classified by a definition be a subset of the instances of classified by any definition it specializes. The enumerated values defined in an enumeration definition, however, would add to the set of enumerated values allowed by any enumeration definition it specialized, which is inconsistent with the semantics of specialization.

    To comply with the Liskov Substitution Principle, a specialization of an enumeration definition should only remove literals, not add them. Why can’t the specialization’s definition either simply remove existing literals from the general definition or list the applicable literals—resulting in a syntax error if this list includes anything not present in the general definition? As a concrete example:

    enum def ClassificationLevel {
       enum unclassified;
       enum cui;
       enum secret;
       enum top_secret;
    }
    
    enum def ClassificationLevelClassified :> ClassificationLevel {
        enum secret;
        enum top_secret;
    }
    
  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 17:49 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Proxy nodes are missing from states

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    State shall be able to have proxy nodes on their boundaries. Currently not covered by the GBNF

  • Reported: SysML 2.0a1 — Sun, 17 Dec 2023 16:03 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Enumerations not specializable

  • Key: SYSML2-593
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    [From Mr. Ryan Noguchi] In the SysML v2 spec, section 7.8.1:

    An enumeration definition may not specialize another enumeration definition. This is because the semantics of specialization require that the set of instances classified by a definition be a subset of the instances of classified by any definition it specializes. The enumerated values defined in an enumeration definition, however, would add to the set of enumerated values allowed by any enumeration definition it specialized, which is inconsistent with the semantics of specialization.

    To comply with the Liskov Substitution Principle, a specialization of an enumeration definition should only remove literals, not add them. Why can’t the specialization’s definition either simply remove existing literals from the general definition or list the applicable literals—resulting in a syntax error if this list includes anything not present in the general definition? As a concrete example:

    enum def ClassificationLevel {
       enum unclassified;
       enum cui;
       enum secret;
       enum top_secret;
    }
    
    enum def ClassificationLevelClassified :> ClassificationLevel {
        enum secret;
        enum top_secret;
    }
    
  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 17:49 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Flow connections are incorrectly both structure and behavior

  • Key: SYSML2-592
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    According to the KerML specification, "Structures and behaviors do not overlap". Consistent with this, the approved resolution to KERML-43 added validations to disallow a structure from specializing a behavior and vice versa.

    ConnectionDefinitions in SysML are kinds of PartDefinitions, which are (indirectly) kinds of KerML Structures. But FlowConnectionDefinitions are both ConnectionDefinitions and ActionDefinitions, and ActionDefinitions are kinds of KerML Behaviors. This means that FlowConnectionDefinitions are both Structures and Behaviors, violating the restrictions of KerML.

    As a result, the specializations in the declarations of MessageConnection and FlowConnection in the Systems Library model Connections now violate the new validateStructureSpecialization and validateBehaviorSpecialization constraints added by the resolution to KERML-43.

  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 17:04 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Proxy nodes are missing from states

  • Key: SYSML2-601
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    State shall be able to have proxy nodes on their boundaries. Currently not covered by the GBNF

  • Reported: SysML 2.0a1 — Sun, 17 Dec 2023 16:03 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Transformation fails on Enumerations that are ValueTypes

  • Key: SYSML2-591
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Both Enumeration and ValueType have main mappings and their specified filters do prevent a double match

  • Reported: SysML 2.0a1 — Wed, 6 Dec 2023 20:41 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

PortUsage direction

  • Key: SYSML2-594
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The direction of a PortUsage can be specified like that of any other feature. However, this does not really seem to make sense. The direction of a PortUsage should be determined by the direction of features within it, consistent with the visualization of directions on ports shown, e.g., in the Representative Notation table in 7.11.1 Parts Overview.

  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 18:15 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    In some cases (e.g. MIWG test case #11) it is unable to compute the requested type.

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:24 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Helper::getScalarValueType operation is not robust enough

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The current algorithm crashes if the data type provided has no name defined or if the type is not defined

  • Reported: SysML 2.0a1 — Wed, 6 Dec 2023 16:53 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The current specification is not computable in some cases (where the "any" OCL iterator find no value). E.g. : MIWG Test Case#27

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:21 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Literal factories are missing operation for their value

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    As a consequence SysMLv literals generated by the transformation have no value defined

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:14 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable

  • Key: SYSML2-588
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The current specification is not computable in some cases (where the "any" OCL iterator find no value). E.g. : MIWG Test Case#27

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:21 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Helper::getScalarValueType operation is not robust enough

  • Key: SYSML2-590
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The current algorithm crashes if the data type provided has no name defined or if the type is not defined

  • Reported: SysML 2.0a1 — Wed, 6 Dec 2023 16:53 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong

  • Key: SYSML2-589
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    In some cases (e.g. MIWG test case #11) it is unable to compute the requested type.

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:24 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Literal factories are missing operation for their value

  • Key: SYSML2-586
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    As a consequence SysMLv literals generated by the transformation have no value defined

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:14 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Default multiplicities are not managed correctly

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The multiplicities that the transformation specifies are wrong when the source element has the default multiplicity in the source model.
    Shall be fixed: MultiplicityUpperBoundOwningMembership_Mapping and MultiplicityLowerBoundOwningMembership_Mapping
    Shall be removed : DefaultLowerBound_Mapping and DefaultUpperBound_Mapping

    Factories for LiteralInteger, LiteralInfinity are required

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:09 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Add a distinguished attribute to capture the textual body of a requirement

  • Status: open  
  • Source: INCOSE ( Mr. Sanford A. Friedenthal)
  • Summary:

    A requirement should include a text body to capture the shall statement or other human readable requirement statement. The doc annotating element is one way to accomplish this. However, a doc element on a requirement definition is inherited by its requirement usages, but it cannot be redefined on its usage. (Note: The texts of a RequirementUsage are the bodies of the documentation of the RequirementUsage.)

    The proposal is to add a distinguished attribute to capture the text body of a requirement that would replace the derived text attribute/documentation. This distinguished attribute can be redefined. This avoids a requirement usage from having both the original text in the requirement definition and the modified text in the usage.

    The concrete syntax should be updated accordingly.

  • Reported: SysML 2.0b1 — Wed, 15 Nov 2023 17:41 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    ownedRelationship() operation. There is the following code:

       else if from.oclIsTypeOf(UML::FlowFinalNode) then
           ObjectFlowItemFlowEndRedefinition_Factory.create(ElementMain_Mapping.getMapped(SysMLv2::ActionUsage.allInstances()->any(e | e.qualifiedName =  'Actions::Action::done')))
    

    The point is that the parameter of a getMapped operation shall be an element form the source model, while the code above povide a SysMLv2 element from a library. This makes the MIWIG test case #27 failing

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 21:02 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Factories specified for Literal specification shall be optimized

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Duplicated operations can be removed by adding a common abstract root class. This will simplify the model and ease the maintenance

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:12 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Add a distinguished attribute to capture the textual body of a requirement

  • Key: SYSML2-546
  • Status: open  
  • Source: INCOSE ( Mr. Sanford A. Friedenthal)
  • Summary:

    A requirement should include a text body to capture the shall statement or other human readable requirement statement. The doc annotating element is one way to accomplish this. However, a doc element on a requirement definition is inherited by its requirement usages, but it cannot be redefined on its usage. (Note: The texts of a RequirementUsage are the bodies of the documentation of the RequirementUsage.)

    The proposal is to add a distinguished attribute to capture the text body of a requirement that would replace the derived text attribute/documentation. This distinguished attribute can be redefined. This avoids a requirement usage from having both the original text in the requirement definition and the modified text in the usage.

    The concrete syntax should be updated accordingly.

  • Reported: SysML 2.0b1 — Wed, 15 Nov 2023 17:41 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Default multiplicities are not managed correctly

  • Key: SYSML2-584
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The multiplicities that the transformation specifies are wrong when the source element has the default multiplicity in the source model.
    Shall be fixed: MultiplicityUpperBoundOwningMembership_Mapping and MultiplicityLowerBoundOwningMembership_Mapping
    Shall be removed : DefaultLowerBound_Mapping and DefaultUpperBound_Mapping

    Factories for LiteralInteger, LiteralInfinity are required

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:09 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Semantic constraints missing for shorthand succession notation

  • Key: SYSML2-576
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The following cases in the textual notation allow "shorthand" then notations for SuccessionAsUsages:

    1. In 8.2.2.9.3 Occurrence Successions, the production SourceSuccession creates a SuccessionAsUsage that has a source end with no related feature and no target end.
    2. In 8.2.2.16.7 Action Successions, the production TargetSuccession creates a SuccessionAsUsage that has a source end as in SourceSuccession, but it has a full ConnectorEndMember for its target end, including an explicit related element.

    In both cases, the intent is that the implied related feature of the source end of the SuccessionAsUsage is a feature lexically previous to the declaration of the SuccessionAsUsage. In the first case, the implied related feature for the target end of the SuccessionAsUsage is a feature lexically following the SuccessionAsUsage. However, there are no semantic constraints given in 8.3.13.8 SuccessionAsUsage to enforce these implied relationships.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 17:12 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong

  • Key: SYSML2-535
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    ownedRelationship() operation. There is the following code:

       else if from.oclIsTypeOf(UML::FlowFinalNode) then
           ObjectFlowItemFlowEndRedefinition_Factory.create(ElementMain_Mapping.getMapped(SysMLv2::ActionUsage.allInstances()->any(e | e.qualifiedName =  'Actions::Action::done')))
    

    The point is that the parameter of a getMapped operation shall be an element form the source model, while the code above povide a SysMLv2 element from a library. This makes the MIWIG test case #27 failing

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 21:02 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Factories specified for Literal specification shall be optimized

  • Key: SYSML2-585
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Duplicated operations can be removed by adding a common abstract root class. This will simplify the model and ease the maintenance

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:12 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Most SysML::Blocks are owned by a package

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The MIWIG test case #11 fails because it assumes that the client of a SysML::Satisfy relationship, that is a Block, is owned by something that is mapped to a SysMLv2 Type.

    This is unlikely to happen since in most cases (like in this test case) Blocks are owned by Packages

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:58 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

OpaqueBehavior shall be transformed even if they are not owned by a Package

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The filter operations defined for the mapping specified from an OpaqueBehavior prevent those owned by another kind of element to be transformed, like in MWIG test cases 7 and 35

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:38 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Properties typed by Actors

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The MWIG test case #8 fails because it contains a property that is typed by an Actor while the transformatiosn currently defined do not support it

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:53 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Textual notation for send actions is too limited

  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    According to the SysML Specification, 8.2.2.16.4 Send and Accept Actions, the general textual notation for a send action has the form

    send payloadExpression via senderExpression to receiverExpression

    In this syntax, the via and to parts are optional, but the payloadExpression is not. Since the result of the required payloadExpression is bound to the payload parameter of the send action, this makes it difficult to model a case in which, e.g., it is desired use a flow to provide the value of the payload, rather than the result of an expression. It also makes it difficult to model a general send action with the payload not specified (or defaulted), with the actual payload bound in a specialization of the general action.

    While it is possible to get around these limitations by modeling the send action using a regular action usage typed by Actions::SendAction, this is no longer syntactically a send action usage and so, e.g., would not be rendered as such in the graphical notation. It would be better if the textual notation allowed the payloadExpression to be optional, while still declaring syntactic send action usage.

  • Reported: SysML 2.0b1 — Wed, 8 Nov 2023 17:26 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

timeslice/snapshot featuring types required to specialize or be same as types

  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Clause 8.3.9.5 (OccurrenceUsage), Constraints, says

    checkOccurrenceUsageTypeFeaturing
    If the portionKind of an OccurrenceUsage is not empty, then, for each occurrenceDefinition of the OccurrenceUsage, there must be a featuringType of the OccurrenceUsage which either is the occurrenceDefinition or directly or indirectly specializes it.

    portionKind <> null implies
      occurrenceDefinition->forAll(occ |
        featuringType->exists(specializes(occ)))
    

    For example, adapted from 7.13.5 (Successions as Usages):

    occurrence def Flight {
      timeslice preflight : Preflight [1];
      then timeslice inflight : Inflight [1];
      then timeslice postflight : Postflight[1];
    

    checkOccurrenceUsageTypeFeaturing requires Flight to specialize each of Pre/In/Postflight, even though these would typically be disjoint with Flight, leading to:

    • all features defined in Pre/In/Postflight "inheriting" to Flight, eg, PreFlight::refuel, would inherit to Flight, with a separate value potentially unconstrained in time from the one happening in preflight.
    • valid traces where all the pre/in/postflight values are instances of Flight, which are all required to have pre/in/postflight timeslices.

    which probably aren't intended in this exampe.

  • Reported: SysML 2.0a1 — Mon, 6 Nov 2023 14:05 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

OpaqueBehavior shall be transformed even if they are not owned by a Package

  • Key: SYSML2-532
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The filter operations defined for the mapping specified from an OpaqueBehavior prevent those owned by another kind of element to be transformed, like in MWIG test cases 7 and 35

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:38 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Most SysML::Blocks are owned by a package

  • Key: SYSML2-534
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The MIWIG test case #11 fails because it assumes that the client of a SysML::Satisfy relationship, that is a Block, is owned by something that is mapped to a SysMLv2 Type.

    This is unlikely to happen since in most cases (like in this test case) Blocks are owned by Packages

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:58 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Properties typed by Actors

  • Key: SYSML2-533
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The MWIG test case #8 fails because it contains a property that is typed by an Actor while the transformatiosn currently defined do not support it

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:53 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

timeslice/snapshot featuring types required to specialize or be same as types

  • Key: SYSML2-524
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Clause 8.3.9.5 (OccurrenceUsage), Constraints, says

    checkOccurrenceUsageTypeFeaturing
    If the portionKind of an OccurrenceUsage is not empty, then, for each occurrenceDefinition of the OccurrenceUsage, there must be a featuringType of the OccurrenceUsage which either is the occurrenceDefinition or directly or indirectly specializes it.

    portionKind <> null implies
      occurrenceDefinition->forAll(occ |
        featuringType->exists(specializes(occ)))
    

    For example, adapted from 7.13.5 (Successions as Usages):

    occurrence def Flight {
      timeslice preflight : Preflight [1];
      then timeslice inflight : Inflight [1];
      then timeslice postflight : Postflight[1];
    

    checkOccurrenceUsageTypeFeaturing requires Flight to specialize each of Pre/In/Postflight, even though these would typically be disjoint with Flight, leading to:

    • all features defined in Pre/In/Postflight "inheriting" to Flight, eg, PreFlight::refuel, would inherit to Flight, with a separate value potentially unconstrained in time from the one happening in preflight.
    • valid traces where all the pre/in/postflight values are instances of Flight, which are all required to have pre/in/postflight timeslices.

    which probably aren't intended in this exampe.

  • Reported: SysML 2.0a1 — Mon, 6 Nov 2023 14:05 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Textual notation for send actions is too limited

  • Key: SYSML2-526
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    According to the SysML Specification, 8.2.2.16.4 Send and Accept Actions, the general textual notation for a send action has the form

    send payloadExpression via senderExpression to receiverExpression

    In this syntax, the via and to parts are optional, but the payloadExpression is not. Since the result of the required payloadExpression is bound to the payload parameter of the send action, this makes it difficult to model a case in which, e.g., it is desired use a flow to provide the value of the payload, rather than the result of an expression. It also makes it difficult to model a general send action with the payload not specified (or defaulted), with the actual payload bound in a specialization of the general action.

    While it is possible to get around these limitations by modeling the send action using a regular action usage typed by Actions::SendAction, this is no longer syntactically a send action usage and so, e.g., would not be rendered as such in the graphical notation. It would be better if the textual notation allowed the payloadExpression to be optional, while still declaring syntactic send action usage.

  • Reported: SysML 2.0b1 — Wed, 8 Nov 2023 17:26 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Relationship_Mapping::ownedRelatedElement() is wrong

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The body condition specified for this operation is wrong. It should be an empty set.

  • Reported: SysML 2.0a1 — Fri, 3 Nov 2023 17:58 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GenericToElement_Mapping is missing default rules

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    GenericToElement_Mapping is missing default rules for:

    • owningRelationship
    • aliasIds
    • declaredShortName
    • isImpliedIncluded
  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 18:07 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GenericToStateUsage_Mapping is missing a default rule

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    GenericToStateUsage_Mapping is missing a default rule for isParallel

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:42 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Comment_Mapping is missing a default rule

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Comment_Mapping is missing a default rule locale

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 18:23 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Namespace_Mapping shall redefine ownedRelationship()

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    A Namespace shall own the relationships that defined its members (either owned or not) and its import relationships.
    Instead the ownedImport() operation is useless since Namespace::ownedImport is a derived property

  • Reported: SysML 2.0a1 — Fri, 3 Nov 2023 18:21 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GenericToStateUsage_Mapping is missing a default rule

  • Key: SYSML2-506
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    GenericToStateUsage_Mapping is missing a default rule for isParallel

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:42 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GenericToElement_Mapping is missing default rules

  • Key: SYSML2-507
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    GenericToElement_Mapping is missing default rules for:

    • owningRelationship
    • aliasIds
    • declaredShortName
    • isImpliedIncluded
  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 18:07 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Namespace_Mapping shall redefine ownedRelationship()

  • Key: SYSML2-516
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    A Namespace shall own the relationships that defined its members (either owned or not) and its import relationships.
    Instead the ownedImport() operation is useless since Namespace::ownedImport is a derived property

  • Reported: SysML 2.0a1 — Fri, 3 Nov 2023 18:21 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Comment_Mapping is missing a default rule

  • Key: SYSML2-508
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Comment_Mapping is missing a default rule locale

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 18:23 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Relationship_Mapping::ownedRelatedElement() is wrong

  • Key: SYSML2-515
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The body condition specified for this operation is wrong. It should be an empty set.

  • Reported: SysML 2.0a1 — Fri, 3 Nov 2023 17:58 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Graphical notation unclear about user-defined keywords for library extensions

  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    A graphical BNF production should be added that specifies that it is mandatory to include the applicable user-defined keyword in the notation for a library extension element.

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:52 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

OccurrenceUsage missing portioningFeature

  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Clause 8.4.5.2 (Occurrence Usages) says

    If an OccurrenceUsage has a non-null portionKind, then it is also required to have a portioningFeature with the same portionKind. The following semantic constraints apply to a PortioningFeature:
    ...

    and the code example at the end of 8.4.5.2 has comments identifying some features as "Portioning", with text below it referring to portioningFeature

    However, portioningFeature doesn't appear in Figure 12 (Occurrence Definition and Usage) or anywhere else in the document.

  • Reported: SysML 2.0b1 — Thu, 2 Nov 2023 14:26 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Graphical notation unclear on optionality of keywords on edges

  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    A graphical BNF production should be added that specifies that keywords may optionally be included on edges.

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:51 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GenericToRequirementUsage_Mapping is missing a default rule

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    GenericToRequirementUsage_Mapping is missing a default rule for reqId

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:39 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GenericToRelationship_Mapping is missing default rules

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    GenericToRelationship_Mapping should provide default rules for

    • owningRelatedElement
    • isImplied
  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:34 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Control nodes missing from concrete syntax for states

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Currently it is not possible to use action control nodes (Fork/Join/Decision/Merge) as sources/targets of a transition in a state definition or usage.

  • Reported: SysML 2.0a1 — Wed, 1 Nov 2023 13:19 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GenericToRelationship_Mapping is missing default rules

  • Key: SYSML2-504
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    GenericToRelationship_Mapping should provide default rules for

    • owningRelatedElement
    • isImplied
  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:34 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Graphical notation unclear on optionality of keywords on edges

  • Key: SYSML2-486
  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    A graphical BNF production should be added that specifies that keywords may optionally be included on edges.

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:51 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Graphical notation unclear about user-defined keywords for library extensions

  • Key: SYSML2-487
  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    A graphical BNF production should be added that specifies that it is mandatory to include the applicable user-defined keyword in the notation for a library extension element.

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:52 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GenericToRequirementUsage_Mapping is missing a default rule

  • Key: SYSML2-505
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    GenericToRequirementUsage_Mapping is missing a default rule for reqId

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:39 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

OccurrenceUsage missing portioningFeature

  • Key: SYSML2-503
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Clause 8.4.5.2 (Occurrence Usages) says

    If an OccurrenceUsage has a non-null portionKind, then it is also required to have a portioningFeature with the same portionKind. The following semantic constraints apply to a PortioningFeature:
    ...

    and the code example at the end of 8.4.5.2 has comments identifying some features as "Portioning", with text below it referring to portioningFeature

    However, portioningFeature doesn't appear in Figure 12 (Occurrence Definition and Usage) or anywhere else in the document.

  • Reported: SysML 2.0b1 — Thu, 2 Nov 2023 14:26 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Control nodes missing from concrete syntax for states

  • Key: SYSML2-502
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Currently it is not possible to use action control nodes (Fork/Join/Decision/Merge) as sources/targets of a transition in a state definition or usage.

  • Reported: SysML 2.0a1 — Wed, 1 Nov 2023 13:19 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Incorrect definition elements in interconnection-element

  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    Definition elements incorrectly appear in graphical BNF productions for interconnection-element. Remove the following from interconnection-element productions: part-def in 8.2.3.11, port-def in 8.2.3.12, connection-def in 8.2.3.13, constraint-def in 8.2.3.19, requirement-def and concern-def in 8.2.3.20, viewpoint-def and view-def in 8.2.3.25.

  • Reported: SysML 2.0b1 — Wed, 18 Oct 2023 13:46 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Clarify bolding of keywords in concrete graphical syntax

  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    Documentation should be added that bolding of keywords in the graphical notation is optional, and may be used for visual prominence. For example, in representative notation table 16 in subclause 7.17.1 in the actions compartment of a state the keywords entry, do and exit are bolded.

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:50 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Missalignment between interface graphical production and notation table

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Notation table shows item flows on interface connections. This is not enabled by the graphical BNF

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 11:24 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Clarify bolding of keywords in concrete graphical syntax

  • Key: SYSML2-485
  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    Documentation should be added that bolding of keywords in the graphical notation is optional, and may be used for visual prominence. For example, in representative notation table 16 in subclause 7.17.1 in the actions compartment of a state the keywords entry, do and exit are bolded.

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:50 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Incorrect definition elements in interconnection-element

  • Key: SYSML2-483
  • Status: open  
  • Source: DEKonsult ( Mr. Hans Peter de Koning)
  • Summary:

    Definition elements incorrectly appear in graphical BNF productions for interconnection-element. Remove the following from interconnection-element productions: part-def in 8.2.3.11, port-def in 8.2.3.12, connection-def in 8.2.3.13, constraint-def in 8.2.3.19, requirement-def and concern-def in 8.2.3.20, viewpoint-def and view-def in 8.2.3.25.

  • Reported: SysML 2.0b1 — Wed, 18 Oct 2023 13:46 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Missalignment between interface graphical production and notation table

  • Key: SYSML2-479
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Notation table shows item flows on interface connections. This is not enabled by the graphical BNF

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 11:24 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Missing production for use case actors and subject

  • Key: SYSML2-482
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Right now use-case nodes cannot be associated with actors and subjects. They need to be made subject/actor stakeholders

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 12:20 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

missing graphical bnf for events and event occurrences

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Events and event occurrences are supported by the textual syntax, but not by the graphical syntax.
    It is also not mentioned in the representative notation tables

  • Reported: SysML 2.0a1 — Mon, 16 Oct 2023 12:57 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

AssociationClass_Mapping is uncomplete

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The redefinition of ownedRelationship() is missing the "class" part, i.e. what is defined in its Class aspect

  • Reported: SysML 2.0b1 — Mon, 25 Sep 2023 19:16 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Initializer classes have to be rationalized

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The intent of "initializer" classes is to factorize the opeations that provide default values for the properties of a target class so that it can be used for both mapping and factory classes. Initializers that do not generalize both a mapping and a factory class are useless and should be remove for clarity

  • Reported: SysML 2.0b1 — Mon, 25 Sep 2023 18:28 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Initializer classes have to be rationalized

  • Key: SYSML2-476
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The intent of "initializer" classes is to factorize the opeations that provide default values for the properties of a target class so that it can be used for both mapping and factory classes. Initializers that do not generalize both a mapping and a factory class are useless and should be remove for clarity

  • Reported: SysML 2.0b1 — Mon, 25 Sep 2023 18:28 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

missing graphical bnf for events and event occurrences

  • Key: SYSML2-475
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Events and event occurrences are supported by the textual syntax, but not by the graphical syntax.
    It is also not mentioned in the representative notation tables

  • Reported: SysML 2.0a1 — Mon, 16 Oct 2023 12:57 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

GBNF for flow connection not mapped to semantics

  • Key: SYSML2-478
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Graphical BNF specifies a flow connection. It is not clearly mapped to a semantic language concept. Should it be merged with a message specified as part of occurences?

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 11:15 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

AssociationClass_Mapping is uncomplete

  • Key: SYSML2-477
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    The redefinition of ownedRelationship() is missing the "class" part, i.e. what is defined in its Class aspect

  • Reported: SysML 2.0b1 — Mon, 25 Sep 2023 19:16 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless

  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Concern_Mapping is a main mapping that calls ConcernOwningMemberships_Mapping in its ownedRelationship() operation, which itself calls ConcernDocumentation_Mapping. However, the one defined in its ancestor Comment_Mapping should do the job without them.
    The redefinition should then be removed and both ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless and should be replace by a simpler version of the ownedRelationship() operation.

  • Reported: SysML 2.0b1 — Thu, 14 Sep 2023 16:56 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

element-node not defined

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Sub-clause 8.2.3.3 (dependencies) uses element-node as the source and target of a dependency.
    element-node is not defined anywhere

  • Reported: SysML 2.0a1 — Wed, 27 Sep 2023 10:09 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Optional language for documentation

  • Status: open  
  • Source: Robert Bosch GmbH ( Florian Beer)
  • Summary:

    Informal specification of requirements is realized as body of the documentation.
    Informal requirement specification often contains text formatting and images as illustrations. To facilitate exchange of requirements between different organizations and proper rendering, the used formatting language, the relative root path for included images and their allowed formats have to be aligned.

    • add optional 'language' keyword to doc
    • define the folder containing the sysml file as root for references made from documentation elements within this file

    To provide guidance for users on common formatting

    • reference jpg and png as suggested image formats
    • reference markdown "md" or other low-complex language as suggested formatting language

    example:
    requirement def SomeRequirement

    { doc language="md" /* The imprint of the serial number shall be positioned as shown in the illustration ![PositionOfSerialNumber](/images/PositionOfSerialNumber.png) */ }
  • Reported: SysML 2.0b1 — Mon, 2 Oct 2023 10:36 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Optional language for documentation

  • Key: SYSML2-472
  • Status: open  
  • Source: Robert Bosch GmbH ( Florian Beer)
  • Summary:

    Informal specification of requirements is realized as body of the documentation.
    Informal requirement specification often contains text formatting and images as illustrations. To facilitate exchange of requirements between different organizations and proper rendering, the used formatting language, the relative root path for included images and their allowed formats have to be aligned.

    • add optional 'language' keyword to doc
    • define the folder containing the sysml file as root for references made from documentation elements within this file

    To provide guidance for users on common formatting

    • reference jpg and png as suggested image formats
    • reference markdown "md" or other low-complex language as suggested formatting language

    example:
    requirement def SomeRequirement

    { doc language="md" /* The imprint of the serial number shall be positioned as shown in the illustration ![PositionOfSerialNumber](/images/PositionOfSerialNumber.png) */ }
  • Reported: SysML 2.0b1 — Mon, 2 Oct 2023 10:36 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

Transformation of UML4SysML::State does not consider entry, do, and exit behavior

  • Key: SYSML2-463
  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    The transformation ignores the entry, do, and exit behavior of a state.

  • Reported: SysML 2.0b1 — Wed, 27 Sep 2023 21:38 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

element-node not defined

  • Key: SYSML2-462
  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Sub-clause 8.2.3.3 (dependencies) uses element-node as the source and target of a dependency.
    element-node is not defined anywhere

  • Reported: SysML 2.0a1 — Wed, 27 Sep 2023 10:09 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless

  • Key: SYSML2-473
  • Status: open  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Concern_Mapping is a main mapping that calls ConcernOwningMemberships_Mapping in its ownedRelationship() operation, which itself calls ConcernDocumentation_Mapping. However, the one defined in its ancestor Comment_Mapping should do the job without them.
    The redefinition should then be removed and both ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless and should be replace by a simpler version of the ownedRelationship() operation.

  • Reported: SysML 2.0b1 — Thu, 14 Sep 2023 16:56 GMT
  • Updated: Wed, 10 Apr 2024 00:42 GMT

TimeEvent should be mapped to an accept action instead of TextualRepresentation

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    In the textual notation, a time event can be represented by an accept action with an at or after condition. The example below is from the vehicle model.
    transition normal_To_maintenance
    first normal
    accept at maintenanceTime
    then maintenance;

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 11:42 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

ChangeEvent should be mapped to an accept action instead of TextualRepresentation

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    In the textual notation, a change event can be represented by an accept action with a when condition. The example below is from the vehicle model.
    transition normal_To_degraded
    first normal
    accept when senseTemperature.temp > Tmax
    do send OverTemp() via targetPort
    then degraded;

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 11:35 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Missing production for n-ary connection definition graphical

  • Status: open  
  • Source: International Business Machines ( Mr. Eran Gery)
  • Summary:

    Subclause 8.2.3.13, specifies the productions for connections. Ballot 3 added a production for n-ary connection usage, but n-ary connection definition (graphical) is still missing

  • Reported: SysML 2.0a1 — Fri, 22 Sep 2023 12:11 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Fork/JoinNode succession "other" end multiplicity validations missing