OMG System Modeling Language Avatar
  1. OMG Specification

OMG System Modeling Language — Open Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
SYSML2_-11 Missing explicit explanation of compartments as views SysML 2.0a1 open
SYSML2_-76 Transformation does not cover SysMLv1::FlowProperty SysML 2.0a1 open
SYSML2_-40 Port transfer semantics SysML 2.0a1 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_-18 No support for metadata definition in graphical notation SysML 2.0a1 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_-44 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 open
SYSML2-629 Guillemets are not used on keywords in textual notation snippets used in the graphical notation SysML 2.0a1 open
SYSML2-591 Transformation fails on Enumerations that are ValueTypes SysML 2.0a1 open
SYSML2-601 Proxy nodes are missing from states SysML 2.0a1 open
SYSML2_-172 Transformation fails on Enumerations that are ValueTypes SysML 2.0a1 open
SYSML2_-176 Proxy nodes are missing from states SysML 2.0a1 open
SYSML2-588 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable 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-590 Helper::getScalarValueType operation is not robust enough SysML 2.0a1 open
SYSML2_-171 Helper::getScalarValueType operation is not robust enough SysML 2.0a1 open
SYSML2_-168 Literal factories are missing operation for their value SysML 2.0a1 open
SYSML2_-170 SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong SysML 2.0a1 open
SYSML2_-169 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable SysML 2.0a1 open
SYSML2-584 Default multiplicities are not managed correctly SysML 2.0a1 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_-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_-166 Default multiplicities are not managed correctly SysML 2.0a1 open
SYSML2-532 OpaqueBehavior shall be transformed even if they are not 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-534 Most SysML::Blocks are owned by a package SysML 2.0a1 open
SYSML2_-158 timeslice/snapshot featuring types required to specialize or be same as types SysML 2.0a1 open
SYSML2_-161 Properties typed by Actors SysML 2.0a1 open
SYSML2_-160 OpaqueBehavior shall be transformed even if they are not owned by a Package SysML 2.0a1 open
SYSML2_-162 Most SysML::Blocks are owned by a package 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_-153 GenericToStateUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-156 Relationship_Mapping::ownedRelatedElement() is wrong SysML 2.0a1 open
SYSML2_-157 Namespace_Mapping shall redefine ownedRelationship() SysML 2.0a1 open
SYSML2_-154 GenericToElement_Mapping is missing default rules SysML 2.0a1 open
SYSML2_-155 Comment_Mapping is missing a default rule 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-502 Control nodes missing from concrete syntax for states SysML 2.0a1 open
SYSML2-505 GenericToRequirementUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-147 Graphical notation unclear on optionality of keywords on edges 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_-148 Graphical notation unclear about user-defined keywords for library extensions SysML 2.0a1 open
SYSML2_-152 GenericToRequirementUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-485 Clarify bolding of keywords in concrete graphical syntax SysML 2.0a1 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_-143 Missalignment between interface graphical production and notation table SysML 2.0a1 open
SYSML2_-146 Clarify bolding of keywords in concrete graphical syntax SysML 2.0a1 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_-139 missing graphical bnf for events and event occurrences SysML 2.0a1 open
SYSML2-462 element-node not defined SysML 2.0a1 open
SYSML2_-135 element-node not defined SysML 2.0a1 open
SYSML2-456 Missing production for n-ary connection definition graphical SysML 2.0a1 open
SYSML2_-134 Missing production for n-ary connection definition graphical SysML 2.0a1 open
SYSML2-385 CommentAnnotation_Mapping shall be a "unique" mapping SysML 2.0a1 open
SYSML2-390 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2_-127 CommentAnnotation_Mapping shall be a "unique" mapping SysML 2.0a1 open
SYSML2_-128 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2-297 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2-286 the getMapped operation cannot be called on ElementOwnership_Mapping SysML 2.0a1 open
SYSML2_-107 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2_-106 the getMapped operation cannot be called on ElementOwnership_Mapping SysML 2.0a1 open
SYSML2-272 Transformation does not cover UML4SysML::ReadLinkAction SysML 2.0a1 open
SYSML2-274 Transformation does not cover UML4SysML::DestroyLinkAction 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-273 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 open
SYSML2_-101 Transformation does not cover UML4SysML::ReadLinkAction SysML 2.0a1 open
SYSML2_-104 Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet SysML 2.0a1 open
SYSML2_-102 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 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_-105 Transformation does not cover UML4SysML::FunctionBehavior 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-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-199 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_-98 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2_-96 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2_-97 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2-183 Some package-level features are mandatory 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-177 Assignment action usages do not specify when their expressions are evaluated 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_-92 XMI and JSON for example model SysML 2.0a1 open
SYSML2_-94 Some package-level features are mandatory SysML 2.0a1 open
SYSML2-151 Transformation does not cover SysMLv1::NoBuffer SysML 2.0a1 open
SYSML2-152 Accepters on transition usages from entry actions 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_-87 Transformation does not cover SysMLv1::Overwrite SysML 2.0a1 open
SYSML2_-90 Subject of an include use case usage SysML 2.0a1 open
SYSML2_-89 Accepters on transition usages from entry actions SysML 2.0a1 open
SYSML2_-88 Transformation does not cover SysMLv1::NoBuffer SysML 2.0a1 open
SYSML2-145 Transformation does not cover SysMLv1::BoundReference SysML 2.0a1 open
SYSML2-147 Transformation does not cover SysMLv1::EndPathMultiplicity 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_-86 Transformation does not cover SysMLv1::AllocateActivitiyPartition SysML 2.0a1 open
SYSML2_-83 Transformation does not cover SysMLv1::ParticipantProperty SysML 2.0a1 open
SYSML2_-82 Transformation does not cover SysMLv1::BoundReference 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-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_-79 Transformation does not cover SysMLv1::Conform SysML 2.0a1 open
SYSML2_-78 Transformation does not cover SysMLv1::View SysML 2.0a1 open
SYSML2_-77 Transformation does not cover SysMLv1::InvocationOnNestedPortAction SysML 2.0a1 open
SYSML2_-81 Transformation does not cover SysMLv1::DistributedProperty SysML 2.0a1 open
SYSML2_-80 Transformation does not cover SysMLv1::Expose SysML 2.0a1 open
SYSML2-135 Transformation does not cover SysMLv1::TriggerOnNestedPort SysML 2.0a1 open
SYSML2-134 Transformation does not cover UML4SysML::UnmarshallAction 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_-74 Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent SysML 2.0a1 open
SYSML2_-75 Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction 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-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_-70 Transformation does not cover UML4SysML::LinkEndDestructionData 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_-69 Transformation does not cover UML4SysML::LinkEndCreationData SysML 2.0a1 open
SYSML2_-68 Transformation does not cover UML4SysML::ConditionalNode SysML 2.0a1 open
SYSML2_-71 Transformation does not cover UML4SysML::LinkEndData 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-126 Transformation does not cover UML4SysML::OccurrenceSpecification SysML 2.0a1 open
SYSML2-127 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2_-63 Transformation does not cover UML4SysML::Gate SysML 2.0a1 open
SYSML2_-65 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2_-62 Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification SysML 2.0a1 open
SYSML2_-64 Transformation does not cover UML4SysML::OccurrenceSpecification 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_-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_-60 Transformation does not cover UML4SysML::PartDecomposition 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_-53 Transformation does not cover UML4SysML::DurationInterval SysML 2.0a1 open
SYSML2_-55 Transformation does not cover UML4SysML::Interval SysML 2.0a1 open
SYSML2_-56 Transformation does not cover UML4SysML::Image SysML 2.0a1 open
SYSML2_-57 Transformation does not cover UML4SysML::DestructionOccurrenceSpecification SysML 2.0a1 open
SYSML2_-54 Transformation does not cover UML4SysML::TimeConstraint SysML 2.0a1 open
SYSML2-112 Transformation does not cover UML4SysML::IntervalConstraint SysML 2.0a1 open
SYSML2-113 Transformation does not cover UML4SysML::DurationObservation 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-110 Transformation does not cover UML4SysML::Duration SysML 2.0a1 open
SYSML2_-50 Transformation does not cover UML4SysML::IntervalConstraint SysML 2.0a1 open
SYSML2_-49 Transformation does not cover UML4SysML::TimeObservation SysML 2.0a1 open
SYSML2_-52 Transformation does not cover UML4SysML::StringExpression SysML 2.0a1 open
SYSML2_-48 Transformation does not cover UML4SysML::Duration SysML 2.0a1 open
SYSML2_-51 Transformation does not cover UML4SysML::DurationObservation SysML 2.0a1 open
SYSML2-107 Transformation does not cover UML4SysML::Extend SysML 2.0a1 open
SYSML2-106 Transformation of UML4SysML::ActivityFinalNode is not specified yet 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-108 Transformation does not cover UML4SysML::TimeInterval 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-97 Semantics of transfers across interfaces SysML 2.0a1 open
SYSML2-104 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_-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_-42 Transformation does not cover UML4SysML::GeneralizationSet SysML 2.0a1 open
SYSML2-87 Add standard domain libraries for mathematical and physical constants 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-96 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_-37 XMI and JSON for model libraries SysML 2.0a1 open
SYSML2_-38 Incorrect action name in graphical notation example SysML 2.0a1 open
SYSML2_-35 Add standard domain libraries for mathematical and physical constants SysML 2.0a1 open
SYSML2_-34 Add capability to specify accuracy, uncertainty or tolerance for numerical values 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_-31 Graphical BNF for grid rendering is missing SysML 2.0a1 open
SYSML2_-32 Resolve "TODO" in domain library model Time 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-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_-26 Special graphical notation for distinguished parameters in name compartment 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_-29 Graphical BNF mapping to abstract syntax is missing SysML 2.0a1 open
SYSML2_-27 Missing graphical notation for Flows Compartment 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-55 Quantity and unit for ratio and fraction 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_-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-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_-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_-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_-20 Examples requirement derivation, cause effect, and refinement missing 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_-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_-12 Regularization of textual notation for loops 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-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-31 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2_-9 Identify impact views on model organization 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-17 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 open
SYSML2-25 Standard view filters incomplete SysML 2.0a1 open
SYSML2-18 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered 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-5 UntypedPin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-7 Pin_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-153 Error in assert constraint example SysML 2.0a1 open
SYSML2-92 Packages can also have compartments SysML 2.0a1 open
SYSML2-156 Errors in textual BNF for RequirementDefinition and ConcernDefinition 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-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-4 Transformation of UML4SysML::AddVariableValueAction is not correct 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-178 ClassifierBehaviorFeatureMembership_Mapping does not exist 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-215 ControlFlow transformation target ends are not defined correctly 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-202 Filter for mapping class Behavior_Mapping is useless SysML 2.0a1 open
SYSML2-43 Graphical BNF sq-message reference 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-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-155 Limitation on specifying view renderings 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-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-224 Number missing from table listing Standard View Definitions 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-261 Error in textual BNF for TargetSuccession 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-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-232 TIAOperatorExpression_Mapping uses non-existing mapping class EqualOperatorExpressionOperand_Mapping 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-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-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-248 CreateLinkObjectAction_Mapping should specialize CreateLinkAction_Mapping 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-281 Map OpqueBehavior always to ActionDefinition SysML 2.0a1 open
SYSML2-250 Typo in AEAReceiverFeatureValue_Mapping::value() SysML 2.0a1 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-47 Graphical BNF productions missing for connections SysML 2.0a1 open
SYSML2-287 sq-port-label and sq-ev-occurrence-label productions use Usage SysML 2.0a1 open
SYSML2-321 Nesting port symbols should use rounded rectangles SysML 2.0a1 open
SYSML2-93 Keyword for documentation is "doc" SysML 2.0a1 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-218 Errors in TransitionUsage semantic constraints SysML 2.0a1 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-398 TransitionUsage effectAction attribute text and constraint are different SysML 2.0a1 open
SYSML2-66 Graphical BNF for n-ary connections missing SysML 2.0a1 open
SYSML2-252 Graphical BNF opaque "text block" productions SysML 2.0a1 open
SYSML2-63 Various incorrect Graphical BNF productions SysML 2.0a1 open
SYSML2-139 Transformation does not cover SysMLv1::~InterfaceBlock SysML 2.0a1 open
SYSML2-58 Representative notation table uses deprecated «equal» 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-280 ElementMain_Mapping::ownedRelationship is wrong SysML 2.0a1 open
SYSML2-79 View::viewpointSatisfactions should subset viewpointChecks and checkedConstraints SysML 2.0a1 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-253 Additional cases when usages are required to be referential SysML 2.0a1 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-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-536 TestCaseVerifyRequirementUsage_Mapping.ownedRelationship() SysML 2.0a1 open
SYSML2-226 Incorrect reference to SysML v1 to SysML v2 Transformation SysML 2.0a1 open
SYSML2-219 Action::decisionTransitions should subset Action::transitions SysML 2.0a1 open
SYSML2-599 Wrong production for adding state-def as a definition node SysML 2.0a1 open
SYSML2-182 Universal features can have many values SysML 2.0a1 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-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-587 The mapping name "~InterfaceBlock_Mapping" is not convenient SysML 2.0a1 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-59 Inconsistent graphical notation for succession, message and flow edges SysML 2.0a1 open

Issues Descriptions

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: Mon, 8 Jul 2024 19:31 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: Fri, 28 Jun 2024 13:16 GMT

Port transfer semantics

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

    In 7.12.1 Ports Overview, at the end of the third paragraph, it states

    A transfer can occur from the out features of one port usage to the matching in features of connected port usages. Transfers can occur in both directions between matching inout features.

    It is unclear whether this is intended to mean that such transfers happen automatically in some way, or if it just means that it is possible to have such transfers by adding explicit flows to the model. If the former is intended, then this does not seem to be currently supported by port semantics (8.4.8). If the latter is intended, this should be made more clear.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:28 GMT
  • Updated: Tue, 25 Jun 2024 20:28 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

No support for metadata definition in graphical notation


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

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

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

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

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

  • 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 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

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

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

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

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

Missing production for n-ary connection definition graphical

  • Key: SYSML2-456
  • 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

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

CommentAnnotation_Mapping shall be a "unique" mapping

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

    Any execution of the CommentAnnotation_Mapping transformation rule shall result in the same instance of SysMLv2 Annotation for a given (Comment, annotatedElement) pair provided. I.e. it should specialize the Foundations::UniqueMapping class.

  • Reported: SysML 2.0a1 — Sun, 20 Aug 2023 15:12 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Actor and subject parameter notation not effective

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

    Actor and subject are parameters of a use case (and also requirement in case of subject). The current notation suggests symbols completely outside the contour of the use case/requirements linked by a line segment. This is different from V1 where actors and subjects were not parameters. Ultimately the modeler is interested to see the binding of those parameters being the concrete occurrences standing for them. The parameter bindings can be graphically represented by binding connections to those external symbols. Would be more effective to treat those predefined parameters using on contour symbols like ports and parameters and bind to those.

  • Reported: SysML 2.0a1 — Thu, 24 Aug 2023 12:11 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

CommentAnnotation_Mapping shall be a "unique" mapping

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

    Any execution of the CommentAnnotation_Mapping transformation rule shall result in the same instance of SysMLv2 Annotation for a given (Comment, annotatedElement) pair provided. I.e. it should specialize the Foundations::UniqueMapping class.

  • Reported: SysML 2.0a1 — Sun, 20 Aug 2023 15:12 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Actor and subject parameter notation not effective

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

    Actor and subject are parameters of a use case (and also requirement in case of subject). The current notation suggests symbols completely outside the contour of the use case/requirements linked by a line segment. This is different from V1 where actors and subjects were not parameters. Ultimately the modeler is interested to see the binding of those parameters being the concrete occurrences standing for them. The parameter bindings can be graphically represented by binding connections to those external symbols. Would be more effective to treat those predefined parameters using on contour symbols like ports and parameters and bind to those.

  • Reported: SysML 2.0a1 — Thu, 24 Aug 2023 12:11 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

SysML Libraries' elements shall have an elementId defined

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

    The way SysML libraries are provided relies on textual notation files on which element declarations do not include the specification of their elementId property.

    As consequence, if the elementId is actually generated by the tool, as written in the KerML specification (p226), it is very likely to have a different value from one computer to another and even from one loading to another on the same computer.

    Hence, it is impossible to make sure it will "not change during the lifetime of the Element", as required by in the same paragraph of that specification.

    Linked to a similar issue raised on KerML

  • Reported: SysML 2.0a1 — Thu, 13 Jul 2023 06:51 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

the getMapped operation cannot be called on ElementOwnership_Mapping

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

    Since Relationship is now an abstract class, ElementOwnership_Mapping has been made abstract as well. A consequence of this, because it is not a "MainMapping", is that it is not possible to invoke the getMapped operation directly on this mapping class.
    However there are many body conditions that still that. They have to be fixed.

  • Reported: SysML 2.0a1 — Tue, 4 Jul 2023 20:16 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

SysML Libraries' elements shall have an elementId defined

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

    The way SysML libraries are provided relies on textual notation files on which element declarations do not include the specification of their elementId property.

    As consequence, if the elementId is actually generated by the tool, as written in the KerML specification (p226), it is very likely to have a different value from one computer to another and even from one loading to another on the same computer.

    Hence, it is impossible to make sure it will "not change during the lifetime of the Element", as required by in the same paragraph of that specification.

    Linked to a similar issue raised on KerML

  • Reported: SysML 2.0a1 — Thu, 13 Jul 2023 06:51 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

the getMapped operation cannot be called on ElementOwnership_Mapping

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

    Since Relationship is now an abstract class, ElementOwnership_Mapping has been made abstract as well. A consequence of this, because it is not a "MainMapping", is that it is not possible to invoke the getMapped operation directly on this mapping class.
    However there are many body conditions that still that. They have to be fixed.

  • Reported: SysML 2.0a1 — Tue, 4 Jul 2023 20:16 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ReadLinkAction

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

    The transformation does not specify mapping rules for UML4SysML::ReadLinkAction.

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:56 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DestroyLinkAction

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

    The transformation does not specify mapping rules for UML4SysML::DestroyLinkAction.

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:59 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet

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

    Currently, the transformation supports only AcceptEventActions with one trigger, but it could be many.

  • Reported: SysML 2.0a1 — Mon, 3 Jul 2023 16:34 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::FunctionBehavior

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

    The transformation does not specify mapping rules for UML4SysML::FunctionBehavior.

  • Reported: SysML 2.0a1 — Tue, 4 Jul 2023 10:30 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::CreateLinkAction

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

    The transformation does not specify mapping rules for UML4SysML::CreateLinkAction.

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:58 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ReadLinkAction

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

    The transformation does not specify mapping rules for UML4SysML::ReadLinkAction.

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:56 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet

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

    Currently, the transformation supports only AcceptEventActions with one trigger, but it could be many.

  • Reported: SysML 2.0a1 — Mon, 3 Jul 2023 16:34 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::CreateLinkAction

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

    The transformation does not specify mapping rules for UML4SysML::CreateLinkAction.

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:58 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DestroyLinkAction

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

    The transformation does not specify mapping rules for UML4SysML::DestroyLinkAction.

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:59 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::SignalEvent

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

    The transformation does not specify mapping rules for UML4SysML::SignalEvent.

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:53 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::FunctionBehavior

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

    The transformation does not specify mapping rules for UML4SysML::FunctionBehavior.

  • Reported: SysML 2.0a1 — Tue, 4 Jul 2023 10:30 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::SignalEvent

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

    The transformation does not specify mapping rules for UML4SysML::SignalEvent.

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:53 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover the different UML4SysML::PseudoStates

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

    The transformation generally maps a PseudoState, but does not distinguish between the different kinds of pseudostates.

  • Reported: SysML 2.0a1 — Sat, 6 May 2023 12:22 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Some Standard View Definitions should be filtered specializations of General View

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

    Some Standard View Definitions, like Case View, are not a self-standing view, but are effectively a General View with a specific filter applied.

    Add filtered views as specializations of General View into the first table "Standard View Definitions" of clause 9.2.19.1, in particular Case View, with an explicit filter declaration.

  • Reported: SysML 2.0a1 — Wed, 14 Jun 2023 10:44 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet


Graphical notation of State Definition not consistent with other submission documents

  • Key: SYSML2-199
  • Status: open  
  • Source: CARIAD SE ( Zahir Ismail)
  • Summary:

    There are different implementations of the SysML v2 graphical notation in the various release documents

    Documents checked:
    2-OMG_Systems_Modeling_Language.pdf Version 2.0 Release 2023-02
    Intro to the SysML v2 Language-Graphical Notation.pdf (2023 03 07)
    Intro to the SysML v2 Language-Textual Notation.pdf Release: 2023-02

    Example of difference, on page 218 of "2-OMG_Systems_Modeling_Language.pdf", the stereotype identifier (<<state>>) is not displayed for State1 and State2, in the "Intro to the SysML v2 Language-Graphical Notation.pdf", the "<<state>>" is displayed.

    If you then take a look at the "Intro to the SysML v2 Language-Textual Notation.pdf" document, there is again a different graphical notation.

    What is the correct standard notation? Does the "2-OMG_Systems_Modeling_Language.pdf" take precedence here?

  • Reported: SysML 2.0a1 — Fri, 12 May 2023 08:13 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Some Standard View Definitions should be filtered specializations of General View

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

    Some Standard View Definitions, like Case View, are not a self-standing view, but are effectively a General View with a specific filter applied.

    Add filtered views as specializations of General View into the first table "Standard View Definitions" of clause 9.2.19.1, in particular Case View, with an explicit filter declaration.

  • Reported: SysML 2.0a1 — Wed, 14 Jun 2023 10:44 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical notation of State Definition not consistent with other submission documents

  • Key: SYSML2_-98
  • Status: open  
  • Source: CARIAD SE ( Zahir Ismail)
  • Summary:

    There are different implementations of the SysML v2 graphical notation in the various release documents

    Documents checked:
    2-OMG_Systems_Modeling_Language.pdf Version 2.0 Release 2023-02
    Intro to the SysML v2 Language-Graphical Notation.pdf (2023 03 07)
    Intro to the SysML v2 Language-Textual Notation.pdf Release: 2023-02

    Example of difference, on page 218 of "2-OMG_Systems_Modeling_Language.pdf", the stereotype identifier (<<state>>) is not displayed for State1 and State2, in the "Intro to the SysML v2 Language-Graphical Notation.pdf", the "<<state>>" is displayed.

    If you then take a look at the "Intro to the SysML v2 Language-Textual Notation.pdf" document, there is again a different graphical notation.

    What is the correct standard notation? Does the "2-OMG_Systems_Modeling_Language.pdf" take precedence here?

  • Reported: SysML 2.0a1 — Fri, 12 May 2023 08:13 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover the different UML4SysML::PseudoStates

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

    The transformation generally maps a PseudoState, but does not distinguish between the different kinds of pseudostates.

  • Reported: SysML 2.0a1 — Sat, 6 May 2023 12:22 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet


Some package-level features are mandatory

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

    Package-level features do not give featuring types, and some have lower multiplicity greater than zero, meaning everything in the universe (instances of Anything), including every data value, is required to give at least that number of values to them (see KERML-56). For example, the libraries include:

    Time::universalClock[1] {...} 
    Observation::defaultMonitor[1] : ChangeMonitor[1] {...}
    SpatialFrames::defaultFrame : SpatialFrame[1] {...}
    

    Might be others.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:17 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

ConstraintBlock mapping parameters to input attributes

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

    In SysML 1.7, Clause 10.1 (Overview, Constraint Blocks) and 10.3.2.1 (ConstraintBlock) say:

    Constraint blocks define generic forms of constraints that can be used in multiple contexts. For example, a definition for Newton’s Laws may be used to specify these constraints in many different contexts. Constraint blocks can be used to specify a network of constraints that represent mathematical expressions such as {F=m*a} and {a=dv/dt}, which constrain the physical properties of a system.

    A constraint block is a block that packages the statement of a constraint so it may be applied in a reusable way to constrain properties of other blocks. A constraint block typically defines one or more constraint parameters, which are bound to properties of other blocks in a surrounding context where the constraint is used.

    enabling an equation to "calculate" any of its variables (constraint parameters), to the extent it's reversible, depending on its usage. For example a constraint block for F=m*a can calculate any on of its variables given the other two by where it's used. But in SysML v1 to SysML v2 Transformation, 7.8.5.2.1 (ConstraintBlock_Mapping) says

    A SysML::ConstraintBlocks::ConstraintBlock is mapped to a SysML v2 ConstraintDefinition. The following shows an example of what the textual SysML v2 syntax of the result of the transformation may look like.

    onstraint def SysMLv1ConstraintBlock {
    in attribute a : ScalarValues::Integer;
    in attribute b : ScalarValues::Integer;
    in attribute c : ScalarValues::Integer;
    constraint constraintExpression {
      language "OCL2.0"  /* c == a + b */ } }
    

    suggests constraint parameters are mapped to attributes with direction in, preventing them from being "calculated" from within the constraint (see KERML-10).

    Not sure if the above is encoded in the mapping rules, but perhaps related is 7.8.5.2.2 (ConstraintParameter_Mapping), under Mapping Rules, says

    The mapping class only has inherited rules. See the mapping classes in the general mapping section for details.

    which means nothing specific is required for mapping constraint parameters. I couldn't find a "general mapping section".

  • Reported: SysML 2.0a1 — Thu, 4 May 2023 15:26 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Machine readable project interchange file(s) for language description examples

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

    Clause 7 Language Description includes a large number of example models and snippets, in textual and graphical notation. However, no machine-readable interchange file was submitted for these models. Project interchange files should be provided for them, including textual notation, XMI and JSON versions.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:33 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

XMI and JSON for example model

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

    There is a machine-readable file containing the example model described in Annex A, but only in the textual notation. There should also be machine-readable versions of this model represented in XMI and JSON.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:37 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Assignment action usages do not specify when their expressions are evaluated

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

    Clause 8.3.16.5 (AssignmentActionUsage), Description, says:

    An AssignmentActionUsage is an ActionUsage that is defined, directly or indirectly, by the ActionDefinition AssignmentAction from the Systems Model Library. It specifies that the value of the referent Feature, relative to the target given by the result of the targetArgument Expression, should be set to the result of the valueExpression.

    but does not require the model to specify when the expression is evaluated (or its owner, AFAICT).

  • Reported: SysML 2.0a1 — Tue, 2 May 2023 20:38 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Machine readable project interchange file(s) for language description examples

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

    Clause 7 Language Description includes a large number of example models and snippets, in textual and graphical notation. However, no machine-readable interchange file was submitted for these models. Project interchange files should be provided for them, including textual notation, XMI and JSON versions.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:33 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Assignment action usages do not specify when their expressions are evaluated

  • Key: SYSML2_-93
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Clause 8.3.16.5 (AssignmentActionUsage), Description, says:

    An AssignmentActionUsage is an ActionUsage that is defined, directly or indirectly, by the ActionDefinition AssignmentAction from the Systems Model Library. It specifies that the value of the referent Feature, relative to the target given by the result of the targetArgument Expression, should be set to the result of the valueExpression.

    but does not require the model to specify when the expression is evaluated (or its owner, AFAICT).

  • Reported: SysML 2.0a1 — Tue, 2 May 2023 20:38 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

ConstraintBlock mapping parameters to input attributes

  • Key: SYSML2_-95
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    In SysML 1.7, Clause 10.1 (Overview, Constraint Blocks) and 10.3.2.1 (ConstraintBlock) say:

    Constraint blocks define generic forms of constraints that can be used in multiple contexts. For example, a definition for Newton’s Laws may be used to specify these constraints in many different contexts. Constraint blocks can be used to specify a network of constraints that represent mathematical expressions such as {F=m*a} and {a=dv/dt}, which constrain the physical properties of a system.

    A constraint block is a block that packages the statement of a constraint so it may be applied in a reusable way to constrain properties of other blocks. A constraint block typically defines one or more constraint parameters, which are bound to properties of other blocks in a surrounding context where the constraint is used.

    enabling an equation to "calculate" any of its variables (constraint parameters), to the extent it's reversible, depending on its usage. For example a constraint block for F=m*a can calculate any on of its variables given the other two by where it's used. But in SysML v1 to SysML v2 Transformation, 7.8.5.2.1 (ConstraintBlock_Mapping) says

    A SysML::ConstraintBlocks::ConstraintBlock is mapped to a SysML v2 ConstraintDefinition. The following shows an example of what the textual SysML v2 syntax of the result of the transformation may look like.

    onstraint def SysMLv1ConstraintBlock {
    in attribute a : ScalarValues::Integer;
    in attribute b : ScalarValues::Integer;
    in attribute c : ScalarValues::Integer;
    constraint constraintExpression {
      language "OCL2.0"  /* c == a + b */ } }
    

    suggests constraint parameters are mapped to attributes with direction in, preventing them from being "calculated" from within the constraint (see KERML-10).

    Not sure if the above is encoded in the mapping rules, but perhaps related is 7.8.5.2.2 (ConstraintParameter_Mapping), under Mapping Rules, says

    The mapping class only has inherited rules. See the mapping classes in the general mapping section for details.

    which means nothing specific is required for mapping constraint parameters. I couldn't find a "general mapping section".

  • Reported: SysML 2.0a1 — Thu, 4 May 2023 15:26 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

XMI and JSON for example model

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

    There is a machine-readable file containing the example model described in Annex A, but only in the textual notation. There should also be machine-readable versions of this model represented in XMI and JSON.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:37 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Some package-level features are mandatory

  • Key: SYSML2_-94
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Package-level features do not give featuring types, and some have lower multiplicity greater than zero, meaning everything in the universe (instances of Anything), including every data value, is required to give at least that number of values to them (see KERML-56). For example, the libraries include:

    Time::universalClock[1] {...} 
    Observation::defaultMonitor[1] : ChangeMonitor[1] {...}
    SpatialFrames::defaultFrame : SpatialFrame[1] {...}
    

    Might be others.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:17 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::NoBuffer

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:03 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Accepters on transition usages from entry actions

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

    In 7.17.3 Transition Usages, in the fourth text paragraph, it states:

    Transition usages from the entry action are not allowed to have accepters.

    There is no validation constraint for this in the abstract syntax.

    Is this constraint necessary? If so, a validation constraint should be added. If not, the statement in 7.17.3 should be removed.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:29 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Subject of an include use case usage

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

    In 7.24.1 Use Cases Overview, in the third paragraph, it states:

    The subject of the included use case is the same as the subject of the containing use case...

    In 7.24.3 Include Use Case Usages, in the third paragraph, it also states:

    The subject of an included use case usage is bound by default to the subject of its containing use case definition or usage.

    However, there is no semantic constraint in the abstract syntax to enforce this.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:40 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::Overwrite

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:02 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::Overwrite

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:02 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Subject of an include use case usage

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

    In 7.24.1 Use Cases Overview, in the third paragraph, it states:

    The subject of the included use case is the same as the subject of the containing use case...

    In 7.24.3 Include Use Case Usages, in the third paragraph, it also states:

    The subject of an included use case usage is bound by default to the subject of its containing use case definition or usage.

    However, there is no semantic constraint in the abstract syntax to enforce this.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:40 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Accepters on transition usages from entry actions

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

    In 7.17.3 Transition Usages, in the fourth text paragraph, it states:

    Transition usages from the entry action are not allowed to have accepters.

    There is no validation constraint for this in the abstract syntax.

    Is this constraint necessary? If so, a validation constraint should be added. If not, the statement in 7.17.3 should be removed.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:29 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::NoBuffer

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:03 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::BoundReference

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:57 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::EndPathMultiplicity

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:00 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::ParticipantProperty

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:57 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::PropertySpecificType

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:01 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::AllocateActivitiyPartition

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:02 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::AllocateActivitiyPartition

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:02 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::ParticipantProperty

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:57 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::BoundReference

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:57 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::PropertySpecificType

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:01 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::EndPathMultiplicity

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:00 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::InvocationOnNestedPortAction

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:51 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::Conform

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:54 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::DistributedProperty

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:55 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::Expose

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:54 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::View

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:53 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::Conform

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:54 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::View

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:53 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::InvocationOnNestedPortAction

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:51 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::DistributedProperty

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:55 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::Expose

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:54 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::TriggerOnNestedPort

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:46 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::UnmarshallAction

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

    The transformation does not specify mapping rules for UML4SysML::UnmarshallAction.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:45 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:47 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:48 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::FlowProperty

  • Key: SYSML2-138
  • 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: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:47 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:48 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::UnmarshallAction

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

    The transformation does not specify mapping rules for UML4SysML::UnmarshallAction.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:45 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover SysMLv1::TriggerOnNestedPort

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:46 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Clause

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

    The transformation does not specify mapping rules for UML4SysML::Clause.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:42 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::LinkEndData

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

    The transformation does not specify mapping rules for UML4SysML::LinkEndData.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:45 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::LinkEndCreationData

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

    The transformation does not specify mapping rules for UML4SysML::LinkEndCreationData.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:43 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::LinkEndDestructionData

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

    The transformation does not specify mapping rules for UML4SysML::LinkEndDestructionData.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:44 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ActivityPartition

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

    The transformation does not specify mapping rules for UML4SysML::ActivityPartition.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:41 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ConditionalNode

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

    The transformation does not specify mapping rules for UML4SysML::ConditionalNode.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:42 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::LinkEndDestructionData

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

    The transformation does not specify mapping rules for UML4SysML::LinkEndDestructionData.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:44 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Clause

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

    The transformation does not specify mapping rules for UML4SysML::Clause.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:42 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ActivityPartition

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

    The transformation does not specify mapping rules for UML4SysML::ActivityPartition.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:41 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::LinkEndCreationData

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

    The transformation does not specify mapping rules for UML4SysML::LinkEndCreationData.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:43 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ConditionalNode

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

    The transformation does not specify mapping rules for UML4SysML::ConditionalNode.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:42 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::LinkEndData

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

    The transformation does not specify mapping rules for UML4SysML::LinkEndData.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:45 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification

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

    The transformation does not specify mapping rules for UML4SysML::ExecutionOccurrenceSpecification.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:22 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Gate

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

    The transformation does not specify mapping rules for UML4SysML::Gate.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:37 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::OccurrenceSpecification

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

    The transformation does not specify mapping rules for UML4SysML::OccurrenceSpecification.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:38 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::InteractionConstraint

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

    The transformation does not specify mapping rules for UML4SysML::InteractionConstraint.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:39 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Gate

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

    The transformation does not specify mapping rules for UML4SysML::Gate.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:37 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::InteractionConstraint

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

    The transformation does not specify mapping rules for UML4SysML::InteractionConstraint.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:39 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification

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

    The transformation does not specify mapping rules for UML4SysML::ExecutionOccurrenceSpecification.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:22 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::OccurrenceSpecification

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

    The transformation does not specify mapping rules for UML4SysML::OccurrenceSpecification.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:38 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Continuation

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

    The transformation does not specify mapping rules for UML4SysML::Continuation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:18 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::GeneralOrdering

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

    The transformation does not specify mapping rules for UML4SysML::GeneralOrdering.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:19 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::PartDecomposition

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

    The transformation does not specify mapping rules for UML4SysML::PartDecomposition.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:21 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ConsiderIgnoreFragment

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

    The transformation does not specify mapping rules for UML4SysML::ConsiderIgnoreFragment.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:21 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::ConsiderIgnoreFragment

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

    The transformation does not specify mapping rules for UML4SysML::ConsiderIgnoreFragment.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:21 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::GeneralOrdering

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

    The transformation does not specify mapping rules for UML4SysML::GeneralOrdering.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:19 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Continuation

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

    The transformation does not specify mapping rules for UML4SysML::Continuation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:18 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::PartDecomposition

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

    The transformation does not specify mapping rules for UML4SysML::PartDecomposition.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:21 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::TimeConstraint

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

    The transformation does not specify mapping rules for UML4SysML::TimeConstraint.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:15 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DestructionOccurrenceSpecification

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

    The transformation does not specify mapping rules for UML4SysML::DestructionOccurrenceSpecification.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:18 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Interval

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

    The transformation does not specify mapping rules for UML4SysML::Interval.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:16 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DurationInterval

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

    The transformation does not specify mapping rules for UML4SysML::DurationInterval.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:15 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Image

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

    The transformation does not specify mapping rules for UML4SysML::Image.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:17 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DurationInterval

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

    The transformation does not specify mapping rules for UML4SysML::DurationInterval.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:15 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Interval

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

    The transformation does not specify mapping rules for UML4SysML::Interval.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:16 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Image

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

    The transformation does not specify mapping rules for UML4SysML::Image.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:17 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DestructionOccurrenceSpecification

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

    The transformation does not specify mapping rules for UML4SysML::DestructionOccurrenceSpecification.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:18 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::TimeConstraint

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

    The transformation does not specify mapping rules for UML4SysML::TimeConstraint.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:15 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::IntervalConstraint

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

    The transformation does not specify mapping rules for UML4SysML::IntervalConstraint.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:12 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DurationObservation

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

    The transformation does not specify mapping rules for UML4SysML::DurationObservation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:13 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::TimeObservation

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

    The transformation does not specify mapping rules for UML4SysML::TimeObservation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:12 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::StringExpression

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

    The transformation does not specify mapping rules for UML4SysML::StringExpression.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:14 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Duration

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

    The transformation does not specify mapping rules for UML4SysML::Duration.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:11 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::IntervalConstraint

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

    The transformation does not specify mapping rules for UML4SysML::IntervalConstraint.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:12 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::TimeObservation

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

    The transformation does not specify mapping rules for UML4SysML::TimeObservation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:12 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::StringExpression

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

    The transformation does not specify mapping rules for UML4SysML::StringExpression.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:14 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Duration

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

    The transformation does not specify mapping rules for UML4SysML::Duration.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:11 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DurationObservation

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

    The transformation does not specify mapping rules for UML4SysML::DurationObservation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:13 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Extend

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

    The extend relationship between use cases is not covered by the transformation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:07 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation of UML4SysML::ActivityFinalNode is not specified yet

  • Key: SYSML2-106
  • 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: Wed, 10 Apr 2024 00:41 GMT

Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete

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

    The details of the mapping of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode are not specified.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:01 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DurationConstraint

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

    The transformation does not specify mapping rules for UML4SysML::DurationConstraint.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:10 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::TimeInterval

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

    The transformation does not specify mapping rules for UML4SysML::TimeInterval.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:09 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::DurationConstraint

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

    The transformation does not specify mapping rules for UML4SysML::DurationConstraint.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:10 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::TimeInterval

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

    The transformation does not specify mapping rules for UML4SysML::TimeInterval.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:09 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete

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

    The details of the mapping of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode are not specified.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:01 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::Extend

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

    The extend relationship between use cases is not covered by the transformation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:07 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Semantics of transfers across interfaces

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

    In 7.16.1 Actions Overview, in the "Bindings and Flows Between Actions" section, it states in the last paragraph (italics added):

    A send action usage includes an expression that is evaluated to provide the values to be transferred, and it specifies the destination to which those values are to be sent (possibly delegated through a port and across one or more interfaces – see also 7.12 and 7.14 on interfaces between ports).

    However, the semantics of "delagation across an interface", per the italicized part above, are not described in 7.12 or 7.14, nor are they specified in 8.4.10 Interfaces Semantics.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:23 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::GeneralizationSet

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

    The transformation does not include a mapping for UML4SysML::GeneralizationSet.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 06:56 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Semantics of a conditional succession using "else" are missing

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

    In 7.16.5 Conditional Successions, in the second paragraph, it states:

    Further, the keyword else may be used in place of a guard expression to indicate a succession to be taken if the guards evaluate to false on all of an immediately preceding set of conditional successions.

    In 8.2.2.16.7, a conditional succession with the else keyword is parsed as a TransitionUsage that simply does not have a guard condition:

    DefaultTargetSuccession : TransitionUsage =
        'else' ownedRelationship += TransitionSuccessionMember
    

    However, the semantics of such a TransitionUsage would seem to be that it can be taken unconditionally, not that it can only be taken if preceding conditional successions have guards that evaluate to false. The else case is not mentioned at all in 8.4.12.3 Decision Transition Usages, which covers the semantics of conditional successions.

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

Port transfer semantics

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

    In 7.12.1 Ports Overview, at the end of the third paragraph, it states

    A transfer can occur from the out features of one port usage to the matching in features of connected port usages. Transfers can occur in both directions between matching inout features.

    It is unclear whether this is intended to mean that such transfers happen automatically in some way, or if it just means that it is possible to have such transfers by adding explicit flows to the model. If the former is intended, then this does not seem to be currently supported by port semantics (8.4.8). If the latter is intended, this should be made more clear.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:28 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Semantics of a conditional succession using "else" are missing

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

    In 7.16.5 Conditional Successions, in the second paragraph, it states:

    Further, the keyword else may be used in place of a guard expression to indicate a succession to be taken if the guards evaluate to false on all of an immediately preceding set of conditional successions.

    In 8.2.2.16.7, a conditional succession with the else keyword is parsed as a TransitionUsage that simply does not have a guard condition:

    DefaultTargetSuccession : TransitionUsage =
        'else' ownedRelationship += TransitionSuccessionMember
    

    However, the semantics of such a TransitionUsage would seem to be that it can be taken unconditionally, not that it can only be taken if preceding conditional successions have guards that evaluate to false. The else case is not mentioned at all in 8.4.12.3 Decision Transition Usages, which covers the semantics of conditional successions.

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

Semantics of transfers across interfaces

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

    In 7.16.1 Actions Overview, in the "Bindings and Flows Between Actions" section, it states in the last paragraph (italics added):

    A send action usage includes an expression that is evaluated to provide the values to be transferred, and it specifies the destination to which those values are to be sent (possibly delegated through a port and across one or more interfaces – see also 7.12 and 7.14 on interfaces between ports).

    However, the semantics of "delagation across an interface", per the italicized part above, are not described in 7.12 or 7.14, nor are they specified in 8.4.10 Interfaces Semantics.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:23 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Transformation does not cover UML4SysML::GeneralizationSet

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

    The transformation does not include a mapping for UML4SysML::GeneralizationSet.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 06:56 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Add standard domain libraries for mathematical and physical constants


Add capability to specify accuracy, uncertainty or tolerance for numerical values

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

    The SysML v2 RFP included Requirement PRP 1.15 “Probabilistic Value Distributions", which stated:

    Proposals for SysML v2 shall include a capability to represent the value of a quantity with a probabilistic value distribution, including an extensible mechanism to detail the kind of distribution, i.e. the probability density function for continuous random variables, or the probability mass function for discrete random variables.

    This requirement was not satisfied in the SysML specification as submitted. A capability should be added that covers this requirement. It should at least be possible to represent a numerical value as a symmetric or asymmetric accuracy, uncertainty or tolerance, with a uniform (i.e., rectangular) distribution.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:53 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Redefining feature information missing from specification document

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

    Multiplicities and bound values of redefining features don't seem to show up in the specification. For example, Clause 9.7.3.2.40 (Toroid) redefines edges, faces, and genus, but does not show the redefining multiplicities or bound values that appear in ShapeItems.kerml and the repository from which this part of the spec was generated. Might be other kinds of information missing on other redefining features.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 19:33 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

XMI and JSON for model libraries

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

    Project interchange files (.kpar) were submitted for all model libraries. However, in all cases, these archives only included textual notation model interchange files (.sysml). There should also be normative model library project interchange files in which the models are formatted in XMI and JSON.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 19:54 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Incorrect action name in graphical notation example

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

    In 7.15.1 Allocations Overview, Table 17, entry for "Allocation (with sub allocation)", the name acton1 in the graphical notation should be action1.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:07 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Redefining feature information missing from specification document

  • Key: SYSML2_-36
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Multiplicities and bound values of redefining features don't seem to show up in the specification. For example, Clause 9.7.3.2.40 (Toroid) redefines edges, faces, and genus, but does not show the redefining multiplicities or bound values that appear in ShapeItems.kerml and the repository from which this part of the spec was generated. Might be other kinds of information missing on other redefining features.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 19:33 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

XMI and JSON for model libraries

  • Key: SYSML2_-37
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Project interchange files (.kpar) were submitted for all model libraries. However, in all cases, these archives only included textual notation model interchange files (.sysml). There should also be normative model library project interchange files in which the models are formatted in XMI and JSON.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 19:54 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Incorrect action name in graphical notation example

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

    In 7.15.1 Allocations Overview, Table 17, entry for "Allocation (with sub allocation)", the name acton1 in the graphical notation should be action1.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:07 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Add standard domain libraries for mathematical and physical constants


Add capability to specify accuracy, uncertainty or tolerance for numerical values

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

    The SysML v2 RFP included Requirement PRP 1.15 “Probabilistic Value Distributions", which stated:

    Proposals for SysML v2 shall include a capability to represent the value of a quantity with a probabilistic value distribution, including an extensible mechanism to detail the kind of distribution, i.e. the probability density function for continuous random variables, or the probability mass function for discrete random variables.

    This requirement was not satisfied in the SysML specification as submitted. A capability should be added that covers this requirement. It should at least be possible to represent a numerical value as a symmetric or asymmetric accuracy, uncertainty or tolerance, with a uniform (i.e., rectangular) distribution.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:53 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Resolve "TODO" in domain library model Time

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

    The declaration of attribute def Iso860DateTimeEncoding in the Quantities and Units Domain Library model Time.sysml still has a TODO comment (line 199):

     * TODO: Add constraint to verify ISO 8691 extended string encoding.
    
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 18:47 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Extend ISQ with missing quantity and unit types for US Customary Units

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

    The US Customary Units as specified in NIST SP811 Annex B include a number of units for which the corresponding quantity is not defined in ISO/IEC 80000, the International System of Quantities (ISQ). These units are currently commented out in Quantities and Units Domain Library USCustomaryUnits. Examples are:

    //attribute <'Btu_IT/ft³'> 'British thermal unit (IT) per cubic foot' : EnergyDensityUnit = Btu_IT/ft^3;
    //attribute <'gal/(hp⋅h)'> 'gallon (US) per horsepower hour' : EnergySpecificVolumeUnit = gal/(hp*h);
    //attribute <'mi/gal'> 'mile per gallon (US)' : FuelEconomyUnit = mi/gal;
    //attribute <'lb/(hp⋅h)'> 'pound per horsepower hour' : FuelConsumptionUnit = lb/(hp*h);
    

    An additional extension package for ISQ is needed that declares the attribute definitions for the missing quantity and measurement unit types, e.g.:

    • EnergyDensityValue and EnergyDensityUnit
    • EnergySpecificVolumeValue and EnergySpecificVolumeUnit
    • FuelEconomyValue and FuelEconomyUnit
    • FuelConsumptionValue and FuelConsumptionUnit

    It should be considered whether or not to include the new library package inside ISQ, as formally these quantity and unit types are not part of ISO/IEC 800000.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:14 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF for grid rendering is missing

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

    There is no Graphical BNF for grid rendering, required by the Grid View Standard View Definition.

    This should be added.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:36 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical notation for variant inheritance from variation requires improvement

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

    A variant is an owned member of its variation and is also a specialization of its variation. As a result, the variant inherits the owned member relationships from its variation.

    This appears in the diagram in the attached example (file name: variant_inheritance_from_variation_issue_sf_2023-04-12). The transmissionAutomatic has an inherited ownedMembership to the transmissionManual and to itself. This applies to the transmissionManual as well.

    Refer to the spec clauses as 8.2.3.5 Namespaces and Packages Graphical Notation and 8.2.3.6 for Definition and Usage Graphical Notation (where variation is introduced).

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:33 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF for grid rendering is missing

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

    There is no Graphical BNF for grid rendering, required by the Grid View Standard View Definition.

    This should be added.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:36 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Resolve "TODO" in domain library model Time

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

    The declaration of attribute def Iso860DateTimeEncoding in the Quantities and Units Domain Library model Time.sysml still has a TODO comment (line 199):

     * TODO: Add constraint to verify ISO 8691 extended string encoding.
    
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 18:47 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Extend ISQ with missing quantity and unit types for US Customary Units

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

    The US Customary Units as specified in NIST SP811 Annex B include a number of units for which the corresponding quantity is not defined in ISO/IEC 80000, the International System of Quantities (ISQ). These units are currently commented out in Quantities and Units Domain Library USCustomaryUnits. Examples are:

    //attribute <'Btu_IT/ft³'> 'British thermal unit (IT) per cubic foot' : EnergyDensityUnit = Btu_IT/ft^3;
    //attribute <'gal/(hp⋅h)'> 'gallon (US) per horsepower hour' : EnergySpecificVolumeUnit = gal/(hp*h);
    //attribute <'mi/gal'> 'mile per gallon (US)' : FuelEconomyUnit = mi/gal;
    //attribute <'lb/(hp⋅h)'> 'pound per horsepower hour' : FuelConsumptionUnit = lb/(hp*h);
    

    An additional extension package for ISQ is needed that declares the attribute definitions for the missing quantity and measurement unit types, e.g.:

    • EnergyDensityValue and EnergyDensityUnit
    • EnergySpecificVolumeValue and EnergySpecificVolumeUnit
    • FuelEconomyValue and FuelEconomyUnit
    • FuelConsumptionValue and FuelConsumptionUnit

    It should be considered whether or not to include the new library package inside ISQ, as formally these quantity and unit types are not part of ISO/IEC 800000.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:14 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical notation for variant inheritance from variation requires improvement

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

    A variant is an owned member of its variation and is also a specialization of its variation. As a result, the variant inherits the owned member relationships from its variation.

    This appears in the diagram in the attached example (file name: variant_inheritance_from_variation_issue_sf_2023-04-12). The transmissionAutomatic has an inherited ownedMembership to the transmissionManual and to itself. This applies to the transmissionManual as well.

    Refer to the spec clauses as 8.2.3.5 Namespaces and Packages Graphical Notation and 8.2.3.6 for Definition and Usage Graphical Notation (where variation is introduced).

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:33 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Special graphical notation for distinguished parameters in name compartment

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

    Currently, distinguished parameters like subject, actor, stakeholder, do not stand out in the graphical notation for symbols that use them.

    Consider allowing distinguished parameters in the name compartment of elements that use them, such as RequirementDefinition, RequirementUsage, UseCaseDefinition, UseCaseUsage, etc.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 13:01 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Missing graphical notation for Flows Compartment

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

    In subclause 7.13.1, Table 15, in example "Flows Compartment" the graphical notation is missing. Graphical notation corresponding to the example expressed in textual notation should be added. Also, the corresponding graphical BNF production for flows-compartment is missing in subclause 8.2.3.13, so that should be added too.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:55 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Source and target on binary ConnectionDefinition symbol missing

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

    The graphical BNF for binary ConnectionDefinition does not clearly indicate the source and target ends.
    The graphical BNF should provide the optional ability to include source and target notation, with arrow head or source and target keywords.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:57 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF mapping to abstract syntax is missing

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

    A mapping of the Graphical BNF productions to the abstract syntax has not been addressed.

    If no specific proposal is considered by the FTF, it may be worth including some discussion notes in the spec in place of any detailed mapping.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:09 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF defines lifeline elements incorrectly

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

    Lifeline elements need to be included within the lifeline itself, with connector segments above and below, and occurrences of * within the lifeline, similar to boundary elements.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:58 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Special graphical notation for distinguished parameters in name compartment

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

    Currently, distinguished parameters like subject, actor, stakeholder, do not stand out in the graphical notation for symbols that use them.

    Consider allowing distinguished parameters in the name compartment of elements that use them, such as RequirementDefinition, RequirementUsage, UseCaseDefinition, UseCaseUsage, etc.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 13:01 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Source and target on binary ConnectionDefinition symbol missing

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

    The graphical BNF for binary ConnectionDefinition does not clearly indicate the source and target ends.
    The graphical BNF should provide the optional ability to include source and target notation, with arrow head or source and target keywords.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:57 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF defines lifeline elements incorrectly

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

    Lifeline elements need to be included within the lifeline itself, with connector segments above and below, and occurrences of * within the lifeline, similar to boundary elements.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:58 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF mapping to abstract syntax is missing

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

    A mapping of the Graphical BNF productions to the abstract syntax has not been addressed.

    If no specific proposal is considered by the FTF, it may be worth including some discussion notes in the spec in place of any detailed mapping.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:09 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Missing graphical notation for Flows Compartment

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

    In subclause 7.13.1, Table 15, in example "Flows Compartment" the graphical notation is missing. Graphical notation corresponding to the example expressed in textual notation should be added. Also, the corresponding graphical BNF production for flows-compartment is missing in subclause 8.2.3.13, so that should be added too.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:55 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Port symbol notation (arrows) needs improvement

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

    The line-arrows in the current graphical notation for ports with directional features are badly readable in large, busy diagrams.

    The same solid triangular arrow symbols as for parameters should be used on ports with directional features.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:21 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Parameter symbol notation needs improvement

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

    The current graphical notation for parameters is similar to SysML v1, i.e. a (rounded) square attached to outside of the border of an action symbol. A directional parameter has a line arrow indicating in, out or inout direction. The notation is inconsistently depicted: both full squares outside the border and half squares outside the border (like in SysML v1) are used. See e.g., Representative Notation Table in section 7.16.1 page 194.

    There should be a single standard notation that is clearly differentiated from port symbols. Also, the direction arrows should be clearly readable in large and busy diagrams with many parameters (nested and non-nested).

    Alternative parameter symbol notation has been developed that uses a circular shape that straddles the border of the owning action (definition or usage), and has solid triangular arrow symbols.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:32 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Missing graphical notation for n-ary connection def and usage

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

    BNF production is missing for n-ary connection def and connection usage as in examples shown in the representative notation table in 7.13.1 Connections Overview. Must be fixed in 8.2.3.13.

    Check all examples of n-ary connections (including causation and requirements derivation) to replace arrowheads with bolded end names. Connections of 3 or more ends only have target ends, no source ends, see KerML spec clause 7.4.5.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:19 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Quantity and unit for ratio and fraction

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

    Explicit concepts for ratio, RatioValue and RatioUnit are missing from ISQ and SI, although they are highly relevant and often used.

    Similarly fraction, FractionValue and FractionUnit would be useful.

    Add these concepts as specializations of DimensionOneValue and DimensionOneUnit.

    Also add units <'%'> percent, <ppm> 'parts per million', <pbm> 'parts per billion'. For parts per billion it is important to explicitly chose the US or UK billion (10^9 vs 10^12).

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 23:17 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Parameter symbol notation needs improvement

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

    The current graphical notation for parameters is similar to SysML v1, i.e. a (rounded) square attached to outside of the border of an action symbol. A directional parameter has a line arrow indicating in, out or inout direction. The notation is inconsistently depicted: both full squares outside the border and half squares outside the border (like in SysML v1) are used. See e.g., Representative Notation Table in section 7.16.1 page 194.

    There should be a single standard notation that is clearly differentiated from port symbols. Also, the direction arrows should be clearly readable in large and busy diagrams with many parameters (nested and non-nested).

    Alternative parameter symbol notation has been developed that uses a circular shape that straddles the border of the owning action (definition or usage), and has solid triangular arrow symbols.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:32 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Quantity and unit for ratio and fraction

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

    Explicit concepts for ratio, RatioValue and RatioUnit are missing from ISQ and SI, although they are highly relevant and often used.

    Similarly fraction, FractionValue and FractionUnit would be useful.

    Add these concepts as specializations of DimensionOneValue and DimensionOneUnit.

    Also add units <'%'> percent, <ppm> 'parts per million', <pbm> 'parts per billion'. For parts per billion it is important to explicitly chose the US or UK billion (10^9 vs 10^12).

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 23:17 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Port symbol notation (arrows) needs improvement

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

    The line-arrows in the current graphical notation for ports with directional features are badly readable in large, busy diagrams.

    The same solid triangular arrow symbols as for parameters should be used on ports with directional features.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:21 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Missing graphical notation for n-ary connection def and usage

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

    BNF production is missing for n-ary connection def and connection usage as in examples shown in the representative notation table in 7.13.1 Connections Overview. Must be fixed in 8.2.3.13.

    Check all examples of n-ary connections (including causation and requirements derivation) to replace arrowheads with bolded end names. Connections of 3 or more ends only have target ends, no source ends, see KerML spec clause 7.4.5.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:19 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Loop examples incomplete in representative notation table

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

    The loop examples in representative notation table for section 7.16 are incomplete, only two until-loops are shown.

    Add while-loop and for-loop action examples in the representative notation table for Actions (after until-loops).

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:04 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Specification of standard geometric view missing

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

    Standard geometric view is identified, but contents are not specified yet. An initial description is given in the doc comment in 9.2.19 library element <gev> GeometricView.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 21:00 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Consider production for standard case view vs filtered general view

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

    No productions for case view. All case-related productions were included in general view, since no specific subset was finalized during discussions. Consider defining as a subset view, like other general view subsets. Incorrect reference to 9.2.19.1.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:54 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

No support for metadata in graphical notation


Graphical BNF production proxy refers to wrong label

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

    proxy refers to proxy-label should be sq-proxy-label
    The BNF attempted to reuse the proxy graphics and productions across all three contexts where a proxy may appear (lifeline, ports, and parameters), but all these need to be replaced by proxy graphics specific to each context, including connector line segments above and below, or left and right, in each specific graphic context where a proxy dot may appear.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:40 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Examples requirement derivation, cause effect, and refinement missing

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

    Requirement derivation, cause effect, and refinement are missing in the representative notation tables.

    Add examples in both graphical and textual notation for requirement derivation, cause effect, and refinement.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:13 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Specification of standard geometric view missing

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

    Standard geometric view is identified, but contents are not specified yet. An initial description is given in the doc comment in 9.2.19 library element <gev> GeometricView.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 21:00 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Loop examples incomplete in representative notation table

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

    The loop examples in representative notation table for section 7.16 are incomplete, only two until-loops are shown.

    Add while-loop and for-loop action examples in the representative notation table for Actions (after until-loops).

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:04 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF production proxy refers to wrong label

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

    proxy refers to proxy-label should be sq-proxy-label
    The BNF attempted to reuse the proxy graphics and productions across all three contexts where a proxy may appear (lifeline, ports, and parameters), but all these need to be replaced by proxy graphics specific to each context, including connector line segments above and below, or left and right, in each specific graphic context where a proxy dot may appear.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:40 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Consider production for standard case view vs filtered general view

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

    No productions for case view. All case-related productions were included in general view, since no specific subset was finalized during discussions. Consider defining as a subset view, like other general view subsets. Incorrect reference to 9.2.19.1.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:54 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Examples requirement derivation, cause effect, and refinement missing

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

    Requirement derivation, cause effect, and refinement are missing in the representative notation tables.

    Add examples in both graphical and textual notation for requirement derivation, cause effect, and refinement.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:13 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Identify the owning context in a graphical view

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

    Clarify how to show the owning context for a nested feature in a graphical view such as a state transition view (Proposed solution: consider 'exhibited by vehicle' for state transition view of vehicleStates).

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:08 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF production sq-ev-occurrence has inconsistent proxy notation

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

    Currently sq-ev-occurrence is denoted as an "X", which is not used anywhere else. Should it be rather the proxy notation, i.e., a black dot?

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:28 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Regularization of textual notation for loops

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

    The textual notation should be regularized between the until loop and while loop.

    The proposed update is loop while action actionName where action and actionName are optional.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:02 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Identify the owning context in a graphical view

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

    Clarify how to show the owning context for a nested feature in a graphical view such as a state transition view (Proposed solution: consider 'exhibited by vehicle' for state transition view of vehicleStates).

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:08 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Graphical BNF production sq-ev-occurrence has inconsistent proxy notation

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

    Currently sq-ev-occurrence is denoted as an "X", which is not used anywhere else. Should it be rather the proxy notation, i.e., a black dot?

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:28 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Regularization of textual notation for loops

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

    The textual notation should be regularized between the until loop and while loop.

    The proposed update is loop while action actionName where action and actionName are optional.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:02 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Identify impact views on model organization

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

    Identify the implications of views on the model organization and how to mitigate circular dependencies.

    Approaches to representing nested views

    • Case 1: Specify view rendering for each element in the view (e.g., show nested parts as a tree view for some parts and interconnection view for others)
    • Case 2: View exposes packages with views
    • Case 3: View contains nested views

    Example (representing nested parts tree). The default case is to apply the same rendering method to each element. In effect, the rendering method and filter is inherited by all elements in the view.

    Case 1. Specify view rendering for each element in the view (e.g., show nested parts as a tree view for some parts and interconnection view for others)

    Case 2. View exposes packages with views

    Case 3. View contains nested views

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:55 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT
  • Attachments:

Clarify query using view

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

    How a view/query is performed when using a view as an input mode is unspecified.

    This should be clarified and added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:53 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Missing graphical notation allocating flow to connection

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

    The graphical notation for allocating a flow to a connection, that is consistent with textual notation, is missing.

    This should be added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:58 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Missing explicit explanation of compartments as views

  • Key: SYSML2-35
  • 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: Wed, 10 Apr 2024 00:41 GMT

Icons for standard view definitions missing

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

    Add standardized element icons and standard view definition icons as they should appear in a browser or on diagrams.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:50 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Identify impact views on model organization

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

    Identify the implications of views on the model organization and how to mitigate circular dependencies.

    Approaches to representing nested views

    • Case 1: Specify view rendering for each element in the view (e.g., show nested parts as a tree view for some parts and interconnection view for others)
    • Case 2: View exposes packages with views
    • Case 3: View contains nested views

    Example (representing nested parts tree). The default case is to apply the same rendering method to each element. In effect, the rendering method and filter is inherited by all elements in the view.

    Case 1. Specify view rendering for each element in the view (e.g., show nested parts as a tree view for some parts and interconnection view for others)

    Case 2. View exposes packages with views

    Case 3. View contains nested views

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:55 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT
  • Attachments:

Clarify query using view

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

    How a view/query is performed when using a view as an input mode is unspecified.

    This should be clarified and added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:53 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Icons for standard view definitions missing

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

    Add standardized element icons and standard view definition icons as they should appear in a browser or on diagrams.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:50 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Missing graphical notation allocating flow to connection

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

    The graphical notation for allocating a flow to a connection, that is consistent with textual notation, is missing.

    This should be added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:58 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Incomplete description of TestCaseVerifyObjectiveMembership_Mapping

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

    The section describing the mapping class TestCaseVerifyObjectiveMembership_Mapping is incomplete. The subsections Description, General Mappings, Mapping Source, Mapping Target, and Owned Mappings are missing.

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 17:16 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Standard view filters incomplete

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

    Specifications of the standard views in library StandardViewDefinitions.sysml are incomplete, i.e. they are not all formally specified with a filter expression.

    Specify valid Definitions as a filter expression for each ViewDefinition. Initial specifications are in textual descriptions in clauses 9.2.19.2.x.

  • Reported: SysML 2.0a1 — Sun, 23 Apr 2023 18:07 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered

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

    The transformation does not consider the property UML4SysML::RemoveVariableValueAction::isRemoveDuplicates.

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 17:29 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered

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

    The transformation does not consider the property UML4SysML::RemoveVariableValueAction::isRemoveDuplicates.

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 17:29 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Incomplete description of TestCaseVerifyObjectiveMembership_Mapping

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

    The section describing the mapping class TestCaseVerifyObjectiveMembership_Mapping is incomplete. The subsections Description, General Mappings, Mapping Source, Mapping Target, and Owned Mappings are missing.

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 17:16 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

Standard view filters incomplete

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

    Specifications of the standard views in library StandardViewDefinitions.sysml are incomplete, i.e. they are not all formally specified with a filter expression.

    Specify valid Definitions as a filter expression for each ViewDefinition. Initial specifications are in textual descriptions in clauses 9.2.19.2.x.

  • Reported: SysML 2.0a1 — Sun, 23 Apr 2023 18:07 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT

UntypedPin_Mapping::filter: property src should be from

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

    The src property in the filter condition should be from.

  • Reported: SysML 2.0a1 — Sat, 15 Apr 2023 17:58 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Pin_Mapping::filter: property src should be from

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

    The src property in the filter condition should be from.

  • Reported: SysML 2.0a1 — Sat, 15 Apr 2023 18:03 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

"Elements not mapped" table sections are empty

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

    All sections in the specification that end with "elements not mapped" should list tables of elements that are not considered by the transformation including a rationale. The tables are listed in the List of Tables of the document.

    As a table or in an alternative presentation form, the information about unmapped elements should be described in the appropriate sections of the specification.

  • Reported: SysML 2.0a1 — Tue, 11 Apr 2023 06:02 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Spatial links can be occurrences

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

    Clause 9.2.4.1 (Occurrences Overview), under Temporal and Spatial Associations, describes temporal/spatial relations between occurrences, such as HappensBefore/Outside and HappensDuring/InsideOf, then says:

    The Links above to do not take up time or space, they are temporal and spatial relations between things that do (they are disjoint with LinkObject, see 9.2.5.1).

    but

    • Some links can be occurrences without being link objects (LinkObject specializes of Link and Object, but does not intersect them).
    • Spatial links are not disjoint with LinkObject or Occurrence in the libraries.
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 18:31 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Inefficient graphical notation specification tooling

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

    Note: this is not an issue with the SysML v2 specification itself, but rather with the tooling to produce it.

    Currently, the graphical notation in the representative notation tables (and for Graphical BNF) is created using an adapted version of the open source tool diagrams.net (https:// www.diagrams.net) in .drawio format. The production workflow is very labor-intensive, cumbersome and therefore error-prone.

    A new, efficient and maintainable workflow using improved tooling should be considered. Preferably, the produced graphical artifacts should in SVG format. The workflow shall also be compatible with the KerML and SysML v2 specification authoring environment.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:28 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Error in InterfaceUsage semantics subclause

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

    In subclause 8.4.10.2, at the beginning of the second bullet, checkInterfaceDefinitionBinarySpecialization should be checkInterfaceUsageBinarySpecialization ("...Usage..." instead of "...Definition...").

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:47 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

The .project.json file for the Cause and Effect Domain Library is misnamed

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

    The Model Interchange Project file in the Cause and Effect Domain Library Project Interchange File is named .proj.json. It should be .project.json.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 19:36 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Standard view filters incomplete

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

    Specifications of the standard views in library `StandardViewDefinitions.sysml` are incomplete, i.e. they are not all formally specified with a filter expression.

    Identify valid element kinds as filter expression for each ViewDefinition. Initial set is specified in clause 9.2.19. Elaborate remaining filter expressions from initial description in comments.

    (Derived from GSWG ID#01).

  • Reported: SysML 2.0a1 — Sun, 23 Apr 2023 17:52 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Association end name " /usageWithDirectedUsage" has a typo

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

    In Figure 8. Definition and Usage (subclause 8.3.6.1), the opposite association end to Usage::directedUsage appears on the diagram as /usageWithDirectedUsage, where the slash indicates it is derived, and the property name is usageWithDirectedUsage. However, in the normative XMI for the abstract syntax, the property is not derived an it has the name  /usageWithDirectedUsage (it starts with a space and a slash).

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:08 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Error in assert constraint example

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

    In 7.19.3 Assert Constraint Usages, in the last example, the assert constraint usage nested in the part usage alienObject is incorrect (and inconsistent with the preceding comment). The name of the constraint should be negativeMass, not nonNegativeMass, and the value bound to mass should be antiMass, not computeMass.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:34 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Packages can also have compartments

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

    In 7.2.2 Elements, at the end of the last paragraph, in the sentence "In the graphical notation, owned elements may be shown in compartments within the symbol representing the owning element, particularly when the owning element is a definition or usage (see 7.6.1).", it should say "...when the owing element is a package, definition or usage (see 7.5 and 7.6.1)."

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 20:57 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Errors in textual BNF for RequirementDefinition and ConcernDefinition

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

    In the BNF production for RequirementDefinition in 8.2.2.20.1:

    RequirementDefinition =
        OccurrenceDefinitionPrefix 'requirement' 'def'
        DefinitionDeclaration RequirementBody?
    

    and the BNF production for ConcernDefinition in 8.2.2.20.3:

    ConcernDefinition =
        OccurrenceDefinitionPrefix 'concern' 'def'
        DefinitionDeclaration RequirementBody?
    

    the final ? after RequirementBody is incorrect and should be removed.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:55 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Transformation of UML4SysML::AddStructuralFeatureValueAction is not correct

  • Key: SYSML2-23
  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:
    • The example of a target SysML v2 textual syntax is not correct. The parameters target and object should be redefined. The others are defined in the library and directly connected by target elements of an object flow mapping.
      Update description: action thisIsAAddStructuralFeatureValueAction : SysMLv1Library::AddStructuralFeatureValueAction {
      :>> target := object.thisIsAnAttribute;
      :>> object : ThisIsABlock;
      }
    • The pins of the action should not be transformed, because their target elements are already defined in the SysMLv1Library.
    • The mapping of an object flow to pins of the action does not work. The target element is defined in the SysMLv1lLbrary.
    • Remove ASFVATargetReferenceUsage_Mapping::declaredName(), because the name must not be set. It is already defined in the SysMLv1Library
    • Redefinition of parameter SysMLv1Library::AddActionValue::target is missing
    • Redefinition of parameter SysMLv1Library::AddStructuralFeatureValueActionValue::object is missing
    • Usage of ASFVATargetFeatureValueExpressionMembership_Mapping in ASFVATargetFeatureChainExpression_Mapping should be ASFVATargetParameterExpressionMembership_Mapping
    • Use the AssignmentAction factory classes from SYSML2-4 instead of ASFVATargetAsignmentActionUsage_Mapping
    • Transformation links the object to the target but should be the structural feature
    • ASFVATargetParameterExpressionFeature_Mapping has no ownedRelationships, therefore remove the operation ownedRelationship()
    • Update ObjectFlowItemFlowEndReferenceUsage_Mapping to properly set the targets of object flows to pins of the AddStructuralFeatureValueAction
    • ASFVAObjectReferenceUsage_Mapping should specialize UniqueMapping, because the mapping class is used twice, but should generate only one element.
  • Reported: SysML 2.0a1 — Sat, 22 Apr 2023 14:34 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Editoral corrections in 7.16.11

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

    In 7.16.11 Loop Action Usages, in the section on "While Loops", in the last paragraph, in the first sentence, "true" should be bold.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 23:04 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

ItemFlowEnds of ObjectFlow transformation target are not defined correctly

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

    The subsetting of the ItemFlowEnd should be a ReferenceSubsetting instead of a Subsetting.

    The value of the isEnd property of the ItemFlowEnd is false, but should be true.

    It is misleading that the names of the mapping classes for the ItemFlowEnd mapping contain the string ItemFlow. It should be ItemFlowEnd.

  • Reported: SysML 2.0a1 — Sat, 15 Apr 2023 09:08 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

UML4SysML::ClearVariableAction transformation does not include a ReturnParameter

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

    The assignment of LiteralNull should include a ReturnParameterMembership element with a feature that is not there. It should be part of the mapping class CVAReferenceUsageFeatureValue_Mapping.

  • Reported: SysML 2.0a1 — Tue, 18 Apr 2023 20:46 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Transformation of UML4SysML::AddVariableValueAction is not correct

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

    The transformation of UML4SysML::AddVariableValueAction contains several issues:

    • AVVAFeatureValue_Mapping uses unknown mapping class AddValueActionValueFeatureReferenceExpression_Mapping; should be AVVAValueFeatureReferenceExpression_Mapping
    • The CommonAssignmentActionUsageReferenceFeatureMembership_Mapping and dependent mapping classes are independent of the mapping source and should be defined as factories
    • The mapping does not consider the isReplaceAll property
    • In SysMLv1Library::AddValueAction, the "if isReplaceAll" statement should be "if not isReplaceAll"
    • The mapping class AVVAValueExpressionMembership_Mapping defines the action as the memberElement. It should be the variable.
    • The source of the mapping classes for AddVariableValueAction should be "AddVariableValueAction" instead of "Action".
    • Remove the mapping of the pins "value" and "insertAt", because they are part of the SysMLv1Library::AddValueAction action definition
    • The mapping of an ObjectFlow to the pins "value" and "insertAt" does not work
  • Reported: SysML 2.0a1 — Sat, 15 Apr 2023 17:04 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Subsections for mapping classes in section 7.7.2.3.9 should be ordered alphabetically

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

    The subsections for mapping specification in the document are ordered alphabetically. The alphabetically order is not fully followed in section 7.7.2.3.9.

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 12:39 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Mapping of ValueSpecificationActions does not work for untyped pins

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

    The mapping class ValueSpecificationAction_Mapping uses a mapping class for the output pin that only considers typed pins.

  • Reported: SysML 2.0a1 — Mon, 1 May 2023 14:10 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

REAOutputPin_Mapping should specialize OutputPin_Mapping

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

    The mapping class REAOutputPin_Mapping should specialize OutputPin_Mapping instead of Pin_Mapping. The result pin of a ReadExtentAction is always an output pin with a defined type.

  • Reported: SysML 2.0a1 — Thu, 20 Apr 2023 06:39 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Mapping of allocation between usage elements is not specified yet

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

    The mapping of an allocation relationship between usage elements is not specified yet (see section 7.8.3.3.8).

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 11:23 GMT
  • Updated: Mon, 8 Apr 2024 18:21 GMT

Optimize Pin mapping class generalization hierarchy