1. OMG Mailing List
  2. Systems Modeling Language (SysML) 2.0 FTF

Open Issues

  • Issues not resolved
  • Name: sysml-v2-ftf
  • Issues Count: 173

Issues Summary

Key Issue Reported Fixed Disposition Status
SYSML2-218 Errors in TransitionUsage semantic constraints SysML 2.0a1 open
SYSML2-204 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-181 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-215 ControlFlow transformation target ends are not defined correctly 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-213 Typo in section 7.6.3 and section 7.6.4: mappingsto SysML 2.0a1 open
SYSML2-208 A ConnectionUsage should be owned by a FeatureMembership relationship SysML 2.0a1 open
SYSML2-180 Mapping of UML4SysML::InformationFlow between definition elements is not supported SysML 2.0a1 open
SYSML2-206 Mapping of UML4SysML::InformationFlow with a realizing connector is not supported SysML 2.0a1 open
SYSML2-106 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 open
SYSML2-188 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2-202 Filter for mapping class Behavior_Mapping is useless SysML 2.0a1 open
SYSML2-157 Incorrect font in descriptions of AttributeUsage and TransitionUsage SysML 2.0a1 open
SYSML2-103 Editoral corrections in 7.16.11 SysML 2.0a1 open
SYSML2-156 Errors in textual BNF for RequirementDefinition and ConcernDefinition SysML 2.0a1 open
SYSML2-153 Error in assert constraint example SysML 2.0a1 open
SYSML2-92 Packages can also have compartments SysML 2.0a1 open
SYSML2-81 Association end name " /usageWithDirectedUsage" has a typo SysML 2.0a1 open
SYSML2-78 The .project.json file for the Cause and Effect Domain Library is misnamed SysML 2.0a1 open
SYSML2-69 Inefficient graphical notation specification tooling SysML 2.0a1 open
SYSML2-75 Spatial links can be occurrences SysML 2.0a1 open
SYSML2-26 Standard view filters incomplete SysML 2.0a1 open
SYSML2-54 Error in InterfaceUsage semantics subclause SysML 2.0a1 open
SYSML2-1 "Elements not mapped" table sections are empty SysML 2.0a1 open
SYSML2-7 Pin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-25 Standard view filters incomplete SysML 2.0a1 open
SYSML2-5 UntypedPin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-88 Mapping of allocation between usage elements is not specified yet SysML 2.0a1 open
SYSML2-200 Description of Subsetting mapping classes is not correct SysML 2.0a1 open
SYSML2-199 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2-23 Transformation of UML4SysML::AddStructuralFeatureValueAction is not correct 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-189 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class ActivityEdgeInitialNodeSourceEndFeatureMembership_Mapping SysML 2.0a1 open
SYSML2-171 Optimize Pin mapping class generalization hierarchy 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-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-16 Subsections for mapping classes in section 7.7.2.3.9 should be ordered alphabetically SysML 2.0a1 open
SYSML2-14 UML4SysML::ClearVariableAction transformation does not include a ReturnParameter SysML 2.0a1 open
SYSML2-2 ItemFlowEnds of ObjectFlow transformation target are not defined correctly SysML 2.0a1 open
SYSML2-4 Transformation of UML4SysML::AddVariableValueAction is not correct SysML 2.0a1 open
SYSML2-28 Validation constraints are missing in the SysML abstract syntax SysML 2.0a1 open
SYSML2-191 deriveForLoopActionUsageBodyAction is misnamed SysML 2.0a1 open
SYSML2-190 The description and derivation of ForLoopActionUsage::seqArgument is wrong SysML 2.0a1 open
SYSML2-187 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2-177 Assignment action usages do not specify when their expressions are evaluated SysML 2.0a1 open
SYSML2-186 ConstraintBlock mapping parameters to input attributes SysML 2.0a1 open
SYSMOAS-1 missing and superfluous properties SystemsModelingAPI 2.0a1 open
SYSML2-185 ISQ in specification and libraries not aligned SysML 2.0a1 open
SYSML2-183 Some package-level features are mandatory SysML 2.0a1 open
SYSML2-182 Universal features can have many values SysML 2.0a1 open
SYSML2-43 Graphical BNF sq-message reference incorrect SysML 2.0a1 open
SYSML2-91 XMI and JSON for model libraries SysML 2.0a1 open
SYSML2-161 XMI and JSON for example model SysML 2.0a1 open
SYSML2-160 Machine readable project interchange file(s) for language description examples SysML 2.0a1 open
SYSML2-159 Example analysis case fuelEconomyAnalysis SysML 2.0a1 open
SYSML2-158 Example FrontAxle definition SysML 2.0a1 open
SYSML2-155 Limitation on specifying view renderings SysML 2.0a1 open
SYSML2-154 Subject of an include use case usage SysML 2.0a1 open
SYSML2-152 Accepters on transition usages from entry actions SysML 2.0a1 open
SYSML2-151 Transformation does not cover SysMLv1::NoBuffer SysML 2.0a1 open
SYSML2-150 Transformation does not cover SysMLv1::Overwrite SysML 2.0a1 open
SYSML2-149 Transformation does not cover SysMLv1::AllocateActivitiyPartition SysML 2.0a1 open
SYSML2-148 Transformation does not cover SysMLv1::PropertySpecificType 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-145 Transformation does not cover SysMLv1::BoundReference 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-142 Transformation does not cover SysMLv1::Conform SysML 2.0a1 open
SYSML2-141 Transformation does not cover SysMLv1::View SysML 2.0a1 open
SYSML2-140 Transformation does not cover SysMLv1::InvocationOnNestedPortAction SysML 2.0a1 open
SYSML2-139 Transformation does not cover SysMLv1::~InterfaceBlock SysML 2.0a1 open
SYSML2-138 Transformation does not cover SysMLv1::FlowProperty SysML 2.0a1 open
SYSML2-137 Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction SysML 2.0a1 open
SYSML2-136 Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent 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-133 Transformation does not cover UML4SysML::LinkEndData SysML 2.0a1 open
SYSML2-132 Transformation does not cover UML4SysML::LinkEndDestructionData SysML 2.0a1 open
SYSML2-131 Transformation does not cover UML4SysML::LinkEndCreationData SysML 2.0a1 open
SYSML2-130 Transformation does not cover UML4SysML::ConditionalNode SysML 2.0a1 open
SYSML2-129 Transformation does not cover UML4SysML::Clause SysML 2.0a1 open
SYSML2-128 Transformation does not cover UML4SysML::ActivityPartition SysML 2.0a1 open
SYSML2-127 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2-126 Transformation does not cover UML4SysML::OccurrenceSpecification SysML 2.0a1 open
SYSML2-125 Transformation does not cover UML4SysML::Gate SysML 2.0a1 open
SYSML2-124 Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification SysML 2.0a1 open
SYSML2-123 Transformation does not cover UML4SysML::ConsiderIgnoreFragment SysML 2.0a1 open
SYSML2-122 Transformation does not cover UML4SysML::PartDecomposition SysML 2.0a1 open
SYSML2-121 Transformation does not cover UML4SysML::GeneralOrdering SysML 2.0a1 open
SYSML2-120 Transformation does not cover UML4SysML::Continuation SysML 2.0a1 open
SYSML2-119 Transformation does not cover UML4SysML::DestructionOccurrenceSpecification SysML 2.0a1 open
SYSML2-118 Transformation does not cover UML4SysML::Image SysML 2.0a1 open
SYSML2-117 Transformation does not cover UML4SysML::Interval SysML 2.0a1 open
SYSML2-116 Transformation does not cover UML4SysML::TimeConstraint SysML 2.0a1 open
SYSML2-115 Transformation does not cover UML4SysML::DurationInterval SysML 2.0a1 open
SYSML2-114 Transformation does not cover UML4SysML::StringExpression SysML 2.0a1 open
SYSML2-113 Transformation does not cover UML4SysML::DurationObservation SysML 2.0a1 open
SYSML2-112 Transformation does not cover UML4SysML::IntervalConstraint SysML 2.0a1 open
SYSML2-111 Transformation does not cover UML4SysML::TimeObservation SysML 2.0a1 open
SYSML2-110 Transformation does not cover UML4SysML::Duration 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-107 Transformation does not cover UML4SysML::Extend SysML 2.0a1 open
SYSML2-105 Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete SysML 2.0a1 open
SYSML2-104 Transformation does not cover UML4SysML::GeneralizationSet 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-102 Semantic constraint for target of AssignmentActionUsage is missing SysML 2.0a1 open
SYSML2-100 Semantics of a conditional succession using "else" are missing SysML 2.0a1 open
SYSML2-93 Keyword for documentation is "doc" SysML 2.0a1 open
SYSML2-98 Port transfer semantics SysML 2.0a1 open
SYSML2-97 Semantics of transfers across interfaces SysML 2.0a1 open
SYSML2-96 Incorrect action name in graphical notation example SysML 2.0a1 open
SYSML2-95 Flows Compartment example graphical notation missing SysML 2.0a1 open
SYSML2-94 Confusing naming in Individual Occurrence example SysML 2.0a1 open
SYSML2-90 Redefining feature information missing from specification document 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-85 Effective name is not correct for a redefined perform action usage SysML 2.0a1 open
SYSML2-84 Connection declaration does not allow a feature value SysML 2.0a1 open
SYSML2-83 Narrow down return types of SpatialItem::PositionOf and ::CurrentPositionOf SysML 2.0a1 open
SYSML2-82 Extend ISQ with missing quantity and unit types for US Customary Units SysML 2.0a1 open
SYSML2-80 Reflective SysML abstract syntax model has inconsistencies SysML 2.0a1 open
SYSML2-79 View::viewpointSatisfactions should subset viewpointChecks and checkedConstraints SysML 2.0a1 open
SYSML2-77 Resolve "TODO" in domain library model Time SysML 2.0a1 open
SYSML2-49 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2-47 Graphical BNF productions missing for connections SysML 2.0a1 open
SYSML2-46 Graphical BNF flow-label and interface-label productions missing SysML 2.0a1 open
SYSML2-45 Graphical BNF interconnection view production incorrect SysML 2.0a1 open
SYSML2-44 Graphical BNF sq-message-label usage incorrect SysML 2.0a1 open
SYSML2-42 Graphical BNF sq-proxy-label reference incorrect SysML 2.0a1 open
SYSML2-41 Graphical BNF production proxy refers to wrong label SysML 2.0a1 open
SYSML2-40 Graphical BNF production sq-ev-occurrence has inconsistent proxy notation SysML 2.0a1 open
SYSML2-39 Graphical BNF production sq-part refers to wrong port SysML 2.0a1 open
SYSML2-38 Textual and graphical notations for flow on connection unclear SysML 2.0a1 open
SYSML2-37 Identify the owning context in a graphical view SysML 2.0a1 open
SYSML2-36 Regularization of textual notation for loops SysML 2.0a1 open
SYSML2-35 Missing explicit explanation of compartments as views SysML 2.0a1 open
SYSML2-34 Missing graphical notation allocating flow to connection SysML 2.0a1 open
SYSML2-32 Clarify query using view SysML 2.0a1 open
SYSML2-31 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2-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-68 Graphical notation for reference usage needs resolution SysML 2.0a1 open
SYSML2-67 Graphical BNF mapping to abstract syntax is missing SysML 2.0a1 open
SYSML2-66 Graphical BNF for n-ary connections missing SysML 2.0a1 open
SYSML2-65 Graphical BNF defines lifeline elements incorrectly SysML 2.0a1 open
SYSML2-64 Flows compartment missing in Representative Notation Table SysML 2.0a1 open
SYSML2-63 Various incorrect Graphical BNF productions SysML 2.0a1 open
SYSML2-62 Incorrect production for attributes-compartment-element SysML 2.0a1 open
SYSML2-61 Special graphical notation for distinguished parameters in name compartment SysML 2.0a1 open
SYSML2-60 Source and target on binary ConnectionDefinition symbol missing SysML 2.0a1 open
SYSML2-59 Graphical notation for edges is not 100% consistent SysML 2.0a1 open
SYSML2-58 Representative notation table uses deprecated «equal» SysML 2.0a1 open
SYSML2-53 Parameter symbol notation needs improvement SysML 2.0a1 open
SYSML2-57 Port symbol notation (arrows) needs improvement SysML 2.0a1 open
SYSML2-56 Inconsistent graphical notation n-ary connection examples SysML 2.0a1 open
SYSML2-55 Quantity and unit for ratio and fraction SysML 2.0a1 open
SYSML2-50 No support for metadata in graphical notation SysML 2.0a1 open
SYSML2-30 Follow typographical conventions in the SysML Metamodel clause SysML 2.0a1 open
SYSML2-29 Name all associations in the SysML abstract syntax SysML 2.0a1 open
SYSML2-52 Examples requirement derivation, cause effect, and refinement missing SysML 2.0a1 open
SYSML2-51 Loop examples incomplete in representative notation table SysML 2.0a1 open
SYSML2-48 Consider production for standard case view vs filtered general view SysML 2.0a1 open
SYSML2-33 Identify impact views on model organization SysML 2.0a1 open
SYSML2-21 RSAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-18 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered SysML 2.0a1 open
SYSML2-17 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 open

Issues Descriptions

Errors in TransitionUsage semantic constraints

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

    There are errors in the specification of the following constraints for TransitionUsage:

    checkTransitionUsageSpecialization

    • The feature Actions::transitions named in the description should be Actions::transitionActions
    • In the OCL, "Actions::actions::transitionActions" should be "Actions::transitionActions".

    checkTransitionActionUsageActionSpecialization

    • In the OCL, "Actions::Action::decisionTransitionActions" should be "Actions::Action::decisionTransitions".
  • Reported: SysML 2.0a1 — Sat, 27 May 2023 18:30 GMT
  • Updated: Sat, 27 May 2023 18:30 GMT

Mapping of SysMLv1::ItemFlow does not consider the itemProperty

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

    The mapping of ItemFlow does not consider the itemProperty. For the case that the itemProperty is not used, it could reuse the mapping of InformationFlow.

  • Reported: SysML 2.0a1 — Wed, 17 May 2023 14:34 GMT
  • Updated: Tue, 23 May 2023 13:06 GMT

Mapping of SysMLv1::ItemFlow does not consider the itemProperty

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

    The mapping of ItemFlow only covers the flow of classifiers, but not of items specified by ItemFlow::itemProperty.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 12:48 GMT
  • Updated: Tue, 23 May 2023 13:05 GMT

ControlFlow transformation target ends are not defined correctly

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

    The ends of a control flow mapping target have a subsetting relationship, but it should be a reference subsetting relationship.

  • Reported: SysML 2.0a1 — Tue, 23 May 2023 12:52 GMT
  • Updated: Tue, 23 May 2023 12:59 GMT

ControlFlow target SuccessionAsUsage should have end feature with reference subsetting

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

    The end features of the the UML4SysML::ControlFlow target element SuccessionAsUsage should have end feature with reference subsetting instead of a subsetting.

  • Reported: SysML 2.0a1 — Thu, 11 May 2023 06:48 GMT
  • Updated: Tue, 23 May 2023 12:59 GMT

Introduce GenericToTransitionUsage_Mapping class

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

    Several mapping classes map to a transition usage. A GenericToTransitionUsage_Mapping class could be introduced to simplify the mapping model and reduce redundancies.

  • Reported: SysML 2.0a1 — Mon, 22 May 2023 15:22 GMT
  • Updated: Mon, 22 May 2023 16:16 GMT

Typo in section 7.6.3 and section 7.6.4: mappingsto

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

    The descriptions of all mapping classes in sections 7.6.3 and 7.6.4 contain the text "mappingsto" which should be "mappings to".

  • Reported: SysML 2.0a1 — Mon, 22 May 2023 15:50 GMT
  • Updated: Mon, 22 May 2023 15:57 GMT

A ConnectionUsage should be owned by a FeatureMembership relationship

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

    The BehavioredClassifier_Mapping::ownedRelationship() operation creates a OwningMembership relationship for ConnectionUsages, but should be a FeatureMembership relationship

  • Reported: SysML 2.0a1 — Thu, 18 May 2023 06:33 GMT
  • Updated: Thu, 18 May 2023 06:45 GMT

Mapping of UML4SysML::InformationFlow between definition elements is not supported

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

    The mapping of UML4SysML::InformationFlow and therefore also SysMLv1::ItemFlow between definition elements is not supported yet.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 05:35 GMT
  • Updated: Wed, 17 May 2023 17:55 GMT

Mapping of UML4SysML::InformationFlow with a realizing connector is not supported

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

    The SysMLv1::ItemFlow mapping supports the flow with a realizing connector. Move this capability to the mapping of UML4SysML::InformationFlow and reuse it to map an ItemFlow. The ItemFlow mapping must only add the special handling of an itemProperty.

  • Reported: SysML 2.0a1 — Wed, 17 May 2023 17:53 GMT
  • Updated: Wed, 17 May 2023 17:54 GMT

Transformation of UML4SysML::ActivityFinalNode is not specified yet

  • Key: SYSML2-106
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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, 17 May 2023 17:44 GMT

Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet


Filter for mapping class Behavior_Mapping is useless

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

    The filter condition of the mapping class Behavior_Mapping is just "true". The filter can be removed.

  • Reported: SysML 2.0a1 — Tue, 16 May 2023 08:52 GMT
  • Updated: Tue, 16 May 2023 13:12 GMT

Incorrect font in descriptions of AttributeUsage and TransitionUsage

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

    Most of the text of the description of AttributeUsage (8.3.7.2) and TransitionUsage (8.3.17.9) is incorrectly in the "code" font, probably due to a missing HTML tag.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:01 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Editoral corrections in 7.16.11

  • Key: SYSML2-103
  • Status: open  
  • Source: Model Driven Solutions ( 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: Tue, 16 May 2023 00:33 GMT

Errors in textual BNF for RequirementDefinition and ConcernDefinition

  • Key: SYSML2-156
  • Status: open  
  • Source: Model Driven Solutions ( 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: Tue, 16 May 2023 00:33 GMT

Error in assert constraint example

  • Key: SYSML2-153
  • Status: open  
  • Source: Model Driven Solutions ( 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: Tue, 16 May 2023 00:33 GMT

Packages can also have compartments

  • Key: SYSML2-92
  • Status: open  
  • Source: Model Driven Solutions ( 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: Tue, 16 May 2023 00:33 GMT

Association end name " /usageWithDirectedUsage" has a typo

  • Key: SYSML2-81
  • Status: open  
  • Source: Model Driven Solutions ( 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: Tue, 16 May 2023 00:33 GMT

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

  • Key: SYSML2-78
  • Status: open  
  • Source: Model Driven Solutions ( 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: Tue, 16 May 2023 00:33 GMT

Inefficient graphical notation specification tooling

  • Key: SYSML2-69
  • Status: open  
  • Source: DEKonsult ( 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: Tue, 16 May 2023 00:33 GMT

Spatial links can be occurrences

  • Key: SYSML2-75
  • Status: open  
  • Source: NIST ( 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: Tue, 16 May 2023 00:33 GMT

Standard view filters incomplete

  • Key: SYSML2-26
  • Status: open  
  • Source: DEKonsult ( 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: Tue, 16 May 2023 00:33 GMT

Error in InterfaceUsage semantics subclause

  • Key: SYSML2-54
  • Status: open  
  • Source: Model Driven Solutions ( 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: Tue, 16 May 2023 00:33 GMT

"Elements not mapped" table sections are empty

  • Key: SYSML2-1
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Tue, 16 May 2023 00:33 GMT

Pin_Mapping::filter: property src should be from

  • Key: SYSML2-7
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Tue, 16 May 2023 00:33 GMT

Standard view filters incomplete

  • Key: SYSML2-25
  • Status: open  
  • Source: DEKonsult ( 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: Tue, 16 May 2023 00:33 GMT

UntypedPin_Mapping::filter: property src should be from

  • Key: SYSML2-5
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Tue, 16 May 2023 00:33 GMT

Mapping of allocation between usage elements is not specified yet

  • Key: SYSML2-88
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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, 15 May 2023 16:19 GMT

Description of Subsetting mapping classes is not correct

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

    The description of mapping classes creating a subsetting element states: "Creates a subsetting relationship for the subsettingFeature() and the subsettedFeature()."

    The operation subsettingFeature() is not defined in the mapping class. Sometimes also the subsettedFeature() operation is also not specified.

    The description should be simply:
    "Creates a subsetting relationship."

  • Reported: SysML 2.0a1 — Mon, 15 May 2023 15:53 GMT
  • Updated: Mon, 15 May 2023 15:59 GMT

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: Mon, 15 May 2023 13:58 GMT

Transformation of UML4SysML::AddStructuralFeatureValueAction is not correct

  • Key: SYSML2-23
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sun, 14 May 2023 15:03 GMT

GenericToEndFeatureMembership_Mapping::to property redefines itself

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

    The to property of GenericToEndFeatureMembership_Mapping redefines itself, but should redefine the inherited to property from GenericToFeatureMembership_Mapping.

  • Reported: SysML 2.0a1 — Thu, 11 May 2023 06:16 GMT
  • Updated: Sun, 14 May 2023 09:39 GMT

ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class

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

    The ownedRelationship() operation of ControlFlowSuccessionAsUsage_Mapping uses the mapping class ControlFlowTargetEndFeatureMembership_Mapping, which is not defined.

  • Reported: SysML 2.0a1 — Wed, 10 May 2023 15:45 GMT
  • Updated: Sun, 14 May 2023 09:39 GMT

ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class ActivityEdgeInitialNodeSourceEndFeatureMembership_Mapping

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

    The ownedRelationship() operation of ControlFlowSuccessionAsUsage_Mapping uses the mapping class ActivityEdgeInitialNodeSourceEndFeatureMembership_Mapping which is not defined.

  • Reported: SysML 2.0a1 — Mon, 8 May 2023 17:40 GMT
  • Updated: Sun, 14 May 2023 09:38 GMT

Optimize Pin mapping class generalization hierarchy

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

    The separation of typed and untyped pin mapping classes leads to the same separation for each specialized mapping class for InputPin and OutputPin and for further specializations. This leads to many mapping classes and thus redundancies in the operations.

    It can be simplified if the distinction of whether the pin has a type or not is not implemented via specialized mapping classes but within the rules.

  • Reported: SysML 2.0a1 — Mon, 1 May 2023 14:02 GMT
  • Updated: Sun, 14 May 2023 09:38 GMT

ClassifierBehaviorFeatureMembership_Mapping does not exist

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

    The mapping class ClassifierBehaviorFeatureMembership_Mapping is used in several operations, but it does not exist. It seems that the class was renamed to BehavioredClassifierFeatureMembership_Mapping.

    The wrong name is used in sections 7.3.1, 7.7.13.3.4, 7.8.4.3.4, 7.8.6.3.25, and 7.8.6.3.33

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 04:54 GMT
  • Updated: Sun, 14 May 2023 09:37 GMT

EmptyReturnParameterFeatureMembership_Mapping does not exist

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

    Section 7.7.2.3.9.22 RVVAVariableFeatureReferenceExpression_Mapping and section 7.7.14.3.23 OpaqueExpressionFeatureValueExpression_Mapping use the mapping class EmptyReturnParameterFeatureMembership_Mapping, but it does not exist.

    Instead, it should be ReturnParameterFeatureMembership_Factory.

  • Reported: SysML 2.0a1 — Tue, 2 May 2023 17:51 GMT
  • Updated: Sun, 14 May 2023 09:37 GMT

Mapping of ValueSpecificationActions does not work for untyped pins

  • Key: SYSML2-173
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sun, 14 May 2023 09:37 GMT

REAOutputPin_Mapping should specialize OutputPin_Mapping

  • Key: SYSML2-19
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sun, 14 May 2023 09:31 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 ( 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: Sun, 14 May 2023 07:11 GMT

UML4SysML::ClearVariableAction transformation does not include a ReturnParameter

  • Key: SYSML2-14
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 13 May 2023 11:37 GMT

ItemFlowEnds of ObjectFlow transformation target are not defined correctly

  • Key: SYSML2-2
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 13 May 2023 11:36 GMT

Transformation of UML4SysML::AddVariableValueAction is not correct

  • Key: SYSML2-4
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 13 May 2023 11:36 GMT

Validation constraints are missing in the SysML abstract syntax

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

    The following validation constraints are implied by textual descriptions in the specification, but are missing in the abstract syntax. They should be added, along with appropriate OCL.

    8.3.16.5 AssignmentActionUsage

    validateAssignmentActionUsageArguments – An AssignmentActionUsage must have two argument Expressions.

    validateAssignmentActionUsageReferent – An AssignmentActionUsage must have an ownedMembership that is not an OwningMembership whose memberElement is a Feature.

    8.3.16.9 ForLoopActionUsage

    validateForLoopActionUsageLoopVariable – The first ownedFeature of a ForLoopActionUsage must be a ReferenceUsage.

    validateForLoopActionUsageParameters – A ForLoopActionUsage must have two owned input parameters.

    8.3.16.10 IfActionUsage

    validateIfActionUsageParameters – An IfActionUsage must have at least two owned input parameters.

    8.3.16.16 TriggerInvocationExpression

    validateTriggerInvocationExpressionAfterArgument – If a TriggerInvocationExpression has kind = after, then it must have an argument Expression with a result that conforms to the type ISQ::DurationValue.

    validateTriggerInvocationExpressionAtArgument – If a TriggerInvocationExpression has kind = at, then it must have an argument Expression with a result that conforms to the type Time::TimeInstantValue.

    validateTriggerInvocationExpressionWhenArgument – If a TriggerInvocationExpression has kind = when, then it must have an argument Expression with a result that conforms to the type ScalarValues::Boolean.

    8.3.16.18 WhileLoopActionUsage

    validateWhileLoopActionUsageParameters – A WhileLoopActionUsage must have at least two owned input parameters.

    8.3.17.2 ExhibitStateUsage

    validateExhibitStateUsageReference – If an ExhibitStateUsage has an ownedReferenceSubsetting, then its referencedFeature must be a StateActionUsage.

    8.3.19.2 AssertConstraintUsage

    validateAssertConstraintUsageReference – If an AssertConstraintUsage has an ownedReferenceSubsetting, then its referencedFeature must be a ConstraintUsage.

    8.3.20.10 SatisfyRequirementUsage

    validateSatisfyRequirementUsageReference – If a SatisfyRequirementUsage has an ownedReferenceSubsetting, then its referencedFeature must be a RequirementUsage.

    8.3.24.2 IncludeUseCaseUsage

    validateIncludeUseCaseUsageReference – If an IncludeUseCaseUsage has an ownedReferenceSubsetting, then its referencedFeature must be a UseCaseUsage.

  • Reported: SysML 2.0a1 — Tue, 25 Apr 2023 20:50 GMT
  • Updated: Thu, 11 May 2023 04:08 GMT

deriveForLoopActionUsageBodyAction is misnamed

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

    The constraint deriveForLoopActionUsageBodyAction is owned by LoopAction, not ForLoopActionUsage, and, so, should be called deriveLoopActionUsageBodyAction.

  • Reported: SysML 2.0a1 — Mon, 8 May 2023 21:53 GMT
  • Updated: Mon, 8 May 2023 21:53 GMT

The description and derivation of ForLoopActionUsage::seqArgument is wrong

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

    The description of ForLoopActionUsage::seqArgument is (see 8.3.16.9 ForLoopActionUsage):

    The Expression whose result provides the sequence of values to which the loopVariable is set for each iterative performance of the bodyAction. It is the owned parameter that redefines ForLoopAction::body.

    The second sentence is clearly wrong. It should instead be

    It is the Expression whose result is bound to the seq input parameter of this ForLoopActionUsage.

    Similarly, the description of the constraint deriveForLoopActionUsageSeqArgument should be

    The seqArgument of a ForLoopActionUsage is its second argument Expression.

    and with the OCL

    seqArgument = argument(1)

  • Reported: SysML 2.0a1 — Mon, 8 May 2023 21:50 GMT
  • Updated: Mon, 8 May 2023 21:50 GMT

Transformation does not cover the different UML4SysML::PseudoStates

  • Key: SYSML2-187
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 6 May 2023 12:22 GMT

Assignment action usages do not specify when their expressions are evaluated

  • Key: SYSML2-177
  • Status: open  
  • Source: NIST ( 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: Fri, 5 May 2023 14:04 GMT

ConstraintBlock mapping parameters to input attributes

  • Key: SYSML2-186
  • Status: open  
  • Source: NIST ( 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: Thu, 4 May 2023 15:30 GMT

missing and superfluous properties

  • Key: SYSMOAS-1
  • Status: open  
  • Source: RHEA Group ( Sam Gerené)
  • Summary:

    While reading through Release 2023-02 of the Systems Modeling Application Programming Interface (API) and Services.pdf i think the following is incorrect:

    Project: missing property created:ISO8601DateTime
    Branch: owningProject is the Project that owns the given Branch -> this property should not be described here as Branch is a subclass of CommitReference which already has a property called owningProject
    Tag: owningProject is the Project that owns the given Tag-> this property should not be described here as Tag is a subclass of CommitReference which already has a property called owningProject

  • Reported: SystemsModelingAPI 2.0a1 — Sun, 30 Apr 2023 21:04 GMT
  • Updated: Wed, 3 May 2023 19:21 GMT

ISQ in specification and libraries not aligned

  • Key: SYSML2-185
  • Status: open  
  • Source: NIST ( Conrad Bock)
  • Summary:

    For example, comparing Clause 9.8.4 (ISQ) to ISQSpaceTime library,

    • universalCartesianSpatial3dCoordinateFrame is missing from the spec
    • In Clause (9.8.4.2.5),
      • Title is Cartesian3dSpatialCoordinateSystem, but the library and the rest of the spec has it as Cartesian3dSpatialCoordinateFrame.
      • General is VectorMeasurementReference, but the library specializes it from Spatial3dCoordinateFrame, which isn't in the spec.

    Might be others.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:29 GMT
  • Updated: Wed, 3 May 2023 15:29 GMT

Some package-level features are mandatory

  • Key: SYSML2-183
  • Status: open  
  • Source: NIST ( 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, 3 May 2023 15:18 GMT

Universal features can have many values

  • Key: SYSML2-182
  • Status: open  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Clause 9.8.8.2.13 (universalClock), Description, says

    universalClock is a single Clock that can be used as a default universal time reference.

    but the Time library shows it as a package-level feature, enabling everything in the universe (instances of Anything) to identify its own universal clock (see KERML-56).

    The phrase "universalClock is a single Clock" above is worded as if universalClock were a part def, rather than a part usage, giving the impression of exactly one value for universalClock across all things, but there is no constraint for this. Similarly, Clause 8.4.12.6 (Accept Action Usages) says

    In particular, the Occurrences::Occurrence::localClock itself defaults to the singleton universalClock (see 9.8.8.2.13 and [KerML, 9.2.12]).

    and 9.7.2.2.5 (SpatialItem) says its localClock is

    A local Clock to be used as the corresponding time reference within this SpatialItem. By default this is the singleton Time::universalClock.

    The term "singleton" usually refers to instances of a class, rather than values of a feature, giving the impression of exactly one value for universalClock across all things.

    Might be other features like this. For example, from the library:

        ISQSpaceTime::universalCartesianSpatial3dCoordinateFrame : CartesianSpatial3dCoordinateFrame[1] {
      /* A singleton CartesianSpatial3dCoordinateFrame that can be used as a default universal Cartesian 3D coordinate frame. */ }
    

    This is also a top-level feature that seems intended to be "universal" in the sense above.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:13 GMT
  • Updated: Wed, 3 May 2023 15:15 GMT

Graphical BNF sq-message reference incorrect

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

    sq-message refers to message-label instead of sq-message-label

    Resolution:
    Change the production rule

    sq-message = &sq-l-node message-label &sq-l-node
    ------------------->
    to:

    sq-message = &sq-l-node sq-message-label &sq-l-node
    ------------------->

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:49 GMT
  • Updated: Mon, 1 May 2023 12:27 GMT

XMI and JSON for model libraries

  • Key: SYSML2-91
  • Status: open  
  • Source: NIST ( 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: Sat, 29 Apr 2023 20:44 GMT

XMI and JSON for example model

  • Key: SYSML2-161
  • Status: open  
  • Source: Model Driven Solutions ( 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: Sat, 29 Apr 2023 20:37 GMT

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

  • Key: SYSML2-160
  • Status: open  
  • Source: Model Driven Solutions ( 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: Sat, 29 Apr 2023 20:33 GMT

Example analysis case fuelEconomyAnalysis

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

    In A.9 Analysis, in the diagram in Figure 70 Analysis Case fuelEconomyAnalysis, the following need to be addressed:

    1. The compartment title subjects should be subject.
    2. The compartment title documentations should be doc.
    3. The empty subject compartment under fuelEconomyAnalysisObjective should be removed.
    4. The notation for the objective using an edge labeled <<objective>> needs to be confirmed. This notation is not shown in Table 24 Analysis Cases – Representative Notation in 7.22, nor does it seem to be supported by the graphical BNF in 8.2.3.22.
  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:20 GMT
  • Updated: Sat, 29 Apr 2023 20:23 GMT

Example FrontAxle definition

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

    In A.3 Definitions, in the diagram in Figure 58, the feature FrontAxle::steeringAngle is shown subsetting ISQSpaceTime::angularMeasure. However, in the corresponding textual notation representation, steeringAngle is shown as subsetting ISQ::planeAngle. Now, ISQ::planeAngle is actually an alias for ISQSpaceTime::angularMeasure, so the representations as shown are technically correct. But the difference will be likely be confusing to the reader. Perhaps, at least, the ISQ::planeAngle should be changed to ISQ::angularMeasure in the textual representation.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:08 GMT
  • Updated: Sat, 29 Apr 2023 20:11 GMT

Limitation on specifying view renderings

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

    In 7.25.2 View Definitions and Usages, the third paragraph includes the parenthetical comment:

    (Note that, in the textual notation, it is only possible to specify a view rendering using reference subsetting.)

    This correctly reflects the following textual notation BNF in 8.2.2.25.1 View Definitions:

    ViewRenderingMember : ViewRenderingMembership =
        MemberPrefix 'render'
        ownedRelatedElement += ViewRenderingUsage
    
    ViewRenderingUsage : RenderingUsage =
        ownedRelationship += OwnedReferenceSubsetting
        FeatureSpecializationPart?
        UsageBody
    

    However, neither the abstract syntax (see 8.3.25) nor the semantics (see 8.4.21) of view rendering require this restriction. The textual notation should be updated to allow a more general declaration of a view rendering usage, consistent with what is representable in the abstract syntax.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:51 GMT
  • Updated: Sat, 29 Apr 2023 19:51 GMT

Subject of an include use case usage

  • Key: SYSML2-154
  • Status: open  
  • Source: Model Driven Solutions ( 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: Sat, 29 Apr 2023 19:40 GMT

Accepters on transition usages from entry actions

  • Key: SYSML2-152
  • Status: open  
  • Source: Model Driven Solutions ( 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: Sat, 29 Apr 2023 19:29 GMT

Transformation does not cover SysMLv1::NoBuffer

  • Key: SYSML2-151
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 08:03 GMT

Transformation does not cover SysMLv1::Overwrite

  • Key: SYSML2-150
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 08:02 GMT

Transformation does not cover SysMLv1::AllocateActivitiyPartition

  • Key: SYSML2-149
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 08:02 GMT

Transformation does not cover SysMLv1::PropertySpecificType

  • Key: SYSML2-148
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 08:01 GMT

Transformation does not cover SysMLv1::EndPathMultiplicity

  • Key: SYSML2-147
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 08:00 GMT

Transformation does not cover SysMLv1::ParticipantProperty

  • Key: SYSML2-146
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:57 GMT

Transformation does not cover SysMLv1::BoundReference

  • Key: SYSML2-145
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:57 GMT

Transformation does not cover SysMLv1::DistributedProperty

  • Key: SYSML2-144
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:55 GMT

Transformation does not cover SysMLv1::Expose

  • Key: SYSML2-143
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:54 GMT

Transformation does not cover SysMLv1::Conform

  • Key: SYSML2-142
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:54 GMT

Transformation does not cover SysMLv1::View

  • Key: SYSML2-141
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:53 GMT

Transformation does not cover SysMLv1::InvocationOnNestedPortAction

  • Key: SYSML2-140
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:51 GMT

Transformation does not cover SysMLv1::~InterfaceBlock

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

    The transformation does not specify mapping rules for SysMLv1::~InterfaceBlock.

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:50 GMT
  • Updated: Sat, 29 Apr 2023 07:50 GMT

Transformation does not cover SysMLv1::FlowProperty

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

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

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

Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction

  • Key: SYSML2-137
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:48 GMT

Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent

  • Key: SYSML2-136
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:47 GMT

Transformation does not cover SysMLv1::TriggerOnNestedPort

  • Key: SYSML2-135
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:46 GMT

Transformation does not cover UML4SysML::UnmarshallAction

  • Key: SYSML2-134
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:45 GMT

Transformation does not cover UML4SysML::LinkEndData

  • Key: SYSML2-133
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:45 GMT

Transformation does not cover UML4SysML::LinkEndDestructionData

  • Key: SYSML2-132
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:44 GMT

Transformation does not cover UML4SysML::LinkEndCreationData

  • Key: SYSML2-131
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:43 GMT

Transformation does not cover UML4SysML::ConditionalNode

  • Key: SYSML2-130
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:42 GMT

Transformation does not cover UML4SysML::Clause

  • Key: SYSML2-129
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:42 GMT

Transformation does not cover UML4SysML::ActivityPartition

  • Key: SYSML2-128
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:41 GMT

Transformation does not cover UML4SysML::InteractionConstraint

  • Key: SYSML2-127
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:39 GMT

Transformation does not cover UML4SysML::OccurrenceSpecification

  • Key: SYSML2-126
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:38 GMT

Transformation does not cover UML4SysML::Gate

  • Key: SYSML2-125
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:37 GMT

Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification

  • Key: SYSML2-124
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:22 GMT

Transformation does not cover UML4SysML::ConsiderIgnoreFragment

  • Key: SYSML2-123
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:21 GMT

Transformation does not cover UML4SysML::PartDecomposition

  • Key: SYSML2-122
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:21 GMT

Transformation does not cover UML4SysML::GeneralOrdering

  • Key: SYSML2-121
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:19 GMT

Transformation does not cover UML4SysML::Continuation

  • Key: SYSML2-120
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:18 GMT

Transformation does not cover UML4SysML::DestructionOccurrenceSpecification

  • Key: SYSML2-119
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:18 GMT

Transformation does not cover UML4SysML::Image

  • Key: SYSML2-118
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:17 GMT

Transformation does not cover UML4SysML::Interval

  • Key: SYSML2-117
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:16 GMT

Transformation does not cover UML4SysML::TimeConstraint

  • Key: SYSML2-116
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:15 GMT

Transformation does not cover UML4SysML::DurationInterval

  • Key: SYSML2-115
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:15 GMT

Transformation does not cover UML4SysML::StringExpression

  • Key: SYSML2-114
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:14 GMT

Transformation does not cover UML4SysML::DurationObservation

  • Key: SYSML2-113
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:13 GMT

Transformation does not cover UML4SysML::IntervalConstraint

  • Key: SYSML2-112
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:12 GMT

Transformation does not cover UML4SysML::TimeObservation

  • Key: SYSML2-111
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:12 GMT

Transformation does not cover UML4SysML::Duration

  • Key: SYSML2-110
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:11 GMT

Transformation does not cover UML4SysML::DurationConstraint

  • Key: SYSML2-109
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:10 GMT

Transformation does not cover UML4SysML::TimeInterval

  • Key: SYSML2-108
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:09 GMT

Transformation does not cover UML4SysML::Extend

  • Key: SYSML2-107
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:07 GMT

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

  • Key: SYSML2-105
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 07:01 GMT

Transformation does not cover UML4SysML::GeneralizationSet

  • Key: SYSML2-104
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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: Sat, 29 Apr 2023 06:56 GMT

Incorrect notation in action examples

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

    In 7.16.2 Action Definitions, the action definition example TakePicture contains two declarations with incorrect textual notation:

    action focus : Focus (in scene, out image);

    and

    action shoot : Shoot (in image, out picture);

    These should be

    action focus : Focus {in scene; out image;}

    and

    action shoot : Shoot {in image; out picture;}

    In 7.16.10 If Action Usages, the nested action declarations in the last example all have incorrect textual notation:

    if threat.level == high then {
        action soundAlarm(threat);
    } else if threat.level == medium then {
        action sendNotification(threat);
    } else {
        action beginMonitoring(threat);
    }

    This should instead be something like:

    if threat.level == high then {
        action soundAlarm {in cause=threat;}
    } else if threat.level == medium then {
        action sendNotification {in cause = threat;}
    } else {
        action beginMonitoring {in cause = threat;}
    }

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:33 GMT
  • Updated: Fri, 28 Apr 2023 22:57 GMT

Time triggers are relative to "localClock", not "defaultClock"

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

    In 7.16.8 Accept Action Usages, it states that the "current time" for time triggers is "relative to the defaultClock". This is incorrect, the time used for triggers is actually the localClock, which defaults to the defaultClock, but can be overridden locally.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 22:22 GMT
  • Updated: Fri, 28 Apr 2023 22:29 GMT

Semantic constraint for target of AssignmentActionUsage is missing

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

    In 7.16.9 Assignment Action Usages, at the beginning of the second text paragraph, it states

    If the target expression of an assignment action usage is omitted, then the target is implicitly the occurrence owning the assignment action usage.

    However, there is no semantic constraint enforce this (see 8.3.16.5).

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 22:28 GMT
  • Updated: Fri, 28 Apr 2023 22:28 GMT

Semantics of a conditional succession using "else" are missing

  • Key: SYSML2-100
  • Status: open  
  • Source: Model Driven Solutions ( 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: Fri, 28 Apr 2023 22:10 GMT

Keyword for documentation is "doc"

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

    In 7.4.1 Annotation Overview, Table 7, in the "Documentation Component" entry, the keyword in the graphical symbol should be doc, not documentation.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 20:59 GMT
  • Updated: Fri, 28 Apr 2023 21:48 GMT

Port transfer semantics

  • Key: SYSML2-98
  • Status: open  
  • Source: Model Driven Solutions ( 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: Fri, 28 Apr 2023 21:28 GMT

Semantics of transfers across interfaces

  • Key: SYSML2-97
  • Status: open  
  • Source: Model Driven Solutions ( 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: Fri, 28 Apr 2023 21:23 GMT

Incorrect action name in graphical notation example

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

    In 7.15.1 Allocations Overview, Table 17, entry for "Allocation (with sub allocation)", the name action 1 in the graphical notation seems to incorrectly have a space in it.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:07 GMT
  • Updated: Fri, 28 Apr 2023 21:07 GMT

Flows Compartment example graphical notation missing

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

    In 7.13.1 Connections Overview, Table 15, entry for "Flows Compartment", the graphical notation is missing.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:04 GMT
  • Updated: Fri, 28 Apr 2023 21:04 GMT

Confusing naming in Individual Occurrence example

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

    In 7.9.1 Occurrences Overview, Table 11, entry for Individual Occurrence, the subsetted occurrence and the subsetting individual are both named occurrence1. It would be better to give the individual occurrence a different name.

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:02 GMT
  • Updated: Fri, 28 Apr 2023 21:02 GMT

Redefining feature information missing from specification document

  • Key: SYSML2-90
  • Status: open  
  • Source: NIST ( 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 (Toriod) 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: Fri, 28 Apr 2023 19:33 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 ( 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: Thu, 27 Apr 2023 21:53 GMT

Effective name is not correct for a redefined perform action usage

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

    The PerformActionUsage::namingFeature operation documentation states that "The naming Feature of a PerformActionUsage is its performedAction." However the body of the operation is specified as exhibitedState. This should instead be performedAction.

    Further, this specification means that that, if a PerformActionUsage redefines another ActionUsage and doesn't have a reference usage, then it will not have any effective name. One would instead expect that its effective name in this case be the same as the name of the action it is redefining, as for a regular ActionUsage.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:49 GMT
  • Updated: Thu, 27 Apr 2023 21:49 GMT

Connection declaration does not allow a feature value

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

    The second line of the following does not parse:

    abstract connection c1;
    abstract connection c2 = c3; // Error: No viable alternative at input '='
    

    The reason for this is that the ConnectionUsage production uses UsageDeclaration (see subclause 8.2.2.13.1):

    ConnectionUsage =
        OccurrenceUsagePrefix
        ( 'connection' UsageDeclaration
          ( 'connect' ConnectorPart )?
        | 'connect' ConnectorPart )
        UsageBody
    

    However, UsageDeclaration does not include ValuePart, which provides the syntax for feature values (see 8.2.2.6.2):

    Usage =
        UsageDeclaration UsageCompletion
    UsageDeclaration : Usage =
        Identification FeatureSpecializationPart?
    UsageCompletion : Usage =
        ValuePart? UsageBody
    

    On the other hand, 7.13.2 states that “A connection definition or usage (that is not of a more specialized kind) is declared as a kind of occurrence definition or usage (see 7.9.2), using the kind keyword connection”, and an occurrence declaration (in the informal sense) can, in general, include a feature value, so it would be expected to be allowable for a connection, too.

    Note that this is also a problem for interactions, but not for messages or flow connections, which explicitly allow a ValuePart (see 8.2.2.13.4):

    MessageDeclaration : FlowConnectionUsage =
          UsageDeclaration ValuePart?
          ( 'of' ownedRelationship += ItemFeatureMember )?
          ( 'from' ownedRelationship += MessageEventMember
            'to' ownedRelationship += MessageEventMember
          )?
        | ownedRelationship += MessageEventMember 'to'
          ownedRelationship += MessageEventMember
    
    FlowConnectionDeclaration : FlowConnectionUsage =
          UsageDeclaration ValuePart?
          ( 'of'  ownedRelationship += FlowPayloadFeatureMember )?
          ( 'from' ownedRelationship += FlowEndMember
            'to'   ownedRelationship += FlowEndMember )?
        | ownedRelationship += FlowEndMember 'to'
          ownedRelationship += FlowEndMember
    
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:30 GMT
  • Updated: Thu, 27 Apr 2023 21:30 GMT

Narrow down return types of SpatialItem::PositionOf and ::CurrentPositionOf

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

    Currently, in the Geometry Domain Library model SpatialItems, the calculation definitions PositionOf and CurrentPositionOf return vectors defined by the generic definition VectorQuantityValue. These should be specialized more narrowly to ISQ::Position3dVector.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:19 GMT
  • Updated: Thu, 27 Apr 2023 21:19 GMT

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

  • Key: SYSML2-82
  • Status: open  
  • Source: Model Driven Solutions ( 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: Thu, 27 Apr 2023 21:14 GMT

Reflective SysML abstract syntax model has inconsistencies

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

    The reflective SysML model in the SysML Systems Library has the following inconsistencies with the normative SysML abstract syntax:

    1. The feature AnalysisCaseUsage::analysisAction should subset usage, not feature.

    2. The features of Definition, RequirementDefinition and Usage should have the same order as the properties of the corresponding metaclasses in the abstract syntax.

    3. The feature ViewDefinition::satisfiedViewpoint should subset ownedRequirement, not ownedUsage.

    4. The feature ViewDefinition::viewRendering should not subset ownedUsage.

    5. The feature ViewUsage::satisfiedViewpoint should subset ownedRequirement, not ownedUsage.

    6. The feature ViewUsage::viewRendering should not subset ownedUsage.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 20:59 GMT
  • Updated: Thu, 27 Apr 2023 20:59 GMT

View::viewpointSatisfactions should subset viewpointChecks and checkedConstraints

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

    In the Views::View model as submitted, viewpointSatisfactions was accidentally declared as redefining viewpointChecks. This should be changed to subsetting, so that there can be (non-composite) viewpoint references within a view that subset viewpointChecks but not viewpointSatisfactions.

    Further, because View is a kind of Part, viewpointSatisfactions also has an implied specialization of Item::checkConstraints. It would be better if this was explicit, to make it clear that any declaration in a View subsetting viewpointSatisfactions automatically satisfies the requirement to subset checkedConstraints, so that this does not require an additional implied specialization.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 20:48 GMT
  • Updated: Thu, 27 Apr 2023 20:48 GMT

Resolve "TODO" in domain library model Time

  • Key: SYSML2-77
  • Status: open  
  • Source: Model Driven Solutions ( 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: Thu, 27 Apr 2023 18:47 GMT

Specification of standard geometric view missing

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

    Standard geometric view is identified, but not 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: Thu, 27 Apr 2023 16:07 GMT

Graphical BNF productions missing for connections

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

    Connections is missing connection production with end names and multiplicities.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:53 GMT
  • Updated: Thu, 27 Apr 2023 16:06 GMT

Graphical BNF flow-label and interface-label productions missing

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

    The Graphical BNF flow-label and interface-label productions are missing and should be added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:52 GMT
  • Updated: Thu, 27 Apr 2023 16:05 GMT

Graphical BNF interconnection view production incorrect

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

    interconnection view production missing interfaces

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:51 GMT
  • Updated: Thu, 27 Apr 2023 16:04 GMT

Graphical BNF sq-message-label usage incorrect

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

    sq-message-label uses Usage from textual production, needs to be corrected

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:50 GMT
  • Updated: Thu, 27 Apr 2023 16:03 GMT

Graphical BNF sq-proxy-label reference incorrect

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

    sq-proxy-label refers to Usage from textual grammar - needs to be corrected

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:48 GMT
  • Updated: Thu, 27 Apr 2023 16:02 GMT

Graphical BNF production proxy refers to wrong label

  • Key: SYSML2-41
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 16:01 GMT

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

  • Key: SYSML2-40
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 16:00 GMT

Graphical BNF production sq-part refers to wrong port

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

    "sq-part refers to portNode* instead of sq-port
    Replace portNode by sq-port but also update sq-port graphics to show horizontal connector segments like other boundary elements"

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:25 GMT
  • Updated: Thu, 27 Apr 2023 15:59 GMT

Textual and graphical notations for flow on connection unclear

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

    Clarify the various textual notations and corresponding graphical notations for representing a flow on a connection.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:19 GMT
  • Updated: Thu, 27 Apr 2023 15:57 GMT

Identify the owning context in a graphical view

  • Key: SYSML2-37
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:56 GMT

Regularization of textual notation for loops

  • Key: SYSML2-36
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:56 GMT

Missing explicit explanation of compartments as views

  • Key: SYSML2-35
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:53 GMT

Missing graphical notation allocating flow to connection

  • Key: SYSML2-34
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:49 GMT

Clarify query using view

  • Key: SYSML2-32
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:46 GMT

Icons for standard view definitions missing

  • Key: SYSML2-31
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:44 GMT

Graphical BNF for grid rendering is missing

  • Key: SYSML2-71
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:36 GMT

Graphical notation for variant inheritance from variation requires improvement

  • Key: SYSML2-70
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:33 GMT

Graphical notation for reference usage needs resolution

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

    According to the Graphical BNF, the notation for a reference usage is now a white diamond in the upper-right hand corner of the usage shape (or optionally a black diamond for a non-reference usage, which is the default).

    This is a change from the previous dashed-outline shape as also used in SysML v1.

    There are arguments pro and con for which notation might be the more usable, including the affinity of the white diamond with a feature membership, but also continuity with SysML v1 and its visibility of the distinction around the whole shape.

    Note: The new notation was proposed primarily to avoid the practical difficulties providing dashed-outline versions of every usage shape in the BNF, but the notation should be properly decided on its own merits, not to make things easier for the BNF. An informal comment could be provided in the BNF simply stating that a dashed-outline version is available for each shape according to whether it is a reference usage. An additional alternative is to use dotted-outline, with the advantage that it more closely follows non-right-angled shapes, such as rounded rectangles used for usages.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:16 GMT
  • Updated: Thu, 27 Apr 2023 15:16 GMT

Graphical BNF mapping to abstract syntax is missing

  • Key: SYSML2-67
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 15:09 GMT

Graphical BNF for n-ary connections missing

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

    Section 8.2.3.13 Connections is missing productions for n-ary connections.

    They should be added.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:00 GMT
  • Updated: Thu, 27 Apr 2023 15:00 GMT

Graphical BNF defines lifeline elements incorrectly

  • Key: SYSML2-65
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 14:58 GMT

Flows compartment missing in Representative Notation Table

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

    A flows compartment is identified but an example is missing in Representative Notation Table 15 under 7.13 Connections.

    An example should be added.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:55 GMT
  • Updated: Thu, 27 Apr 2023 14:55 GMT

Various incorrect Graphical BNF productions

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

    The Graphical BNF productions in section 8.2.3 contain a number of minor mistakes

    In order to be efficient, the mistakes and corrections are recorded as an enumerated list hereafter.

    1. In 8.2.3.9, production occurrences-compartment-element incorrectly uses DefinitionBodyItem. DefinitionBodyItem should be removed.
    2. In 8.2.3.10, production items-compartment-element incorrectly uses DefinitionBodyItem. DefinitionBodyItem should be removed.
    3. In 8.2.3.11, production parts-compartment-element incorrectly uses OccurrenceUsagePrefix UsageDeclaration. It should be OccurrenceUsagePrefix Usage.
    4. In 8.2.3.12, production ports-compartment-element incorrectly uses OccurrenceUsagePrefix UsageDeclaration. It should be OccurrenceUsagePrefix Usage.
    5. In 8.2.3.13, production connections-compartment-element incorrectly uses OccurrenceUsagePrefix UsageDeclaration ConnectorPart+ DefinitionBodyItem*. It should be OccurrenceUsagePrefix UsageDeclaration ( 'connect' ConnectorPart )? | 'connect' ConnectorPart ) UsageBody.
    6. In 8.2.3.14, production interfaces-compartment-element incorrectly uses InterfaceUsageDeclaration InterfaceBodyDefinition*. It should be OccurrenceUsagePrefix InterfaceUsageDeclaration InterfaceBody.
    7. In 8.2.3.16, production actions-compartment-element incorrectly uses OccurrenceUsagePrefix ActionUsageDeclaration ActionBodyItem*. It should be OccurrenceUsagePrefix ActionUsageDeclaration.
    8. In 8.2.3.16, production perform-actions-compartment-element incorrectly uses PerformActionUsageDeclaration ActionBodyItem*. It should be OccurrenceUsagePrefix PerformActionUsageDeclaration.
    9. In 8.2.3.17, production states-compartment-element incorrectly uses UsageDeclaration. It should be OccurrenceUsagePrefix ActionUsageDeclaration.
    10. In 8.2.3.24, production use-cases-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: use-cases-compartment-contents = (use-cases-compartment-element)* '…'? and use-cases-compartment-element = el-prefix? OccurrenceUsagePrefix CalculationUsageDeclaration CaseBody '…'
    11. In 8.2.3.5, production packages-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: packages-compartment-contents = (packages-compartment-element)* '…'? and packages-compartment-element = el-prefix? TBD
    12. In 8.2.3.5, production members-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: members-compartment-contents = (members-compartment-element)* '…'? and members-compartment-element = el-prefix? TBD
    13. In 8.2.3.5, production relationships-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: relationships-compartment-contents = (relationships-compartment-element)* '…'? and relationships-compartment-element = el-prefix? TBD
    14. In 8.2.3.6, production variants-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: variants-compartment-contents = (variants-compartment-element)* '…'? and variants-compartment-element = el-prefix? TBD
    15. In 8.2.3.6, production variant-elementusages-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: variant-elementusages-compartment-contents = (variant-elementusages-compartment-element)* '…'? and variant-elementusages-compartment-element = el-prefix? TBD
    16. In 8.2.3.16, production performed-by-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: performed-by-compartment-contents = (performed-by-compartment-element)* '…'? and performed-by-compartment-element = el-prefix? TBD
    17. In 8.2.3.17, production succession-compartment-contents incorrectly equates to text-block placeholder. It should be renamed to successions-compartment-contents, and it should be replaced with two productions: successions-compartment-contents = (successions-compartment-element)* '…'? and successions-compartment-element = el-prefix? TBD
    18. In 8.2.3.18, production calcs-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: calcs-compartment-contents = (calcs-compartment-element)* '…'? and calcs-compartment-element = el-prefix? TBD
    19. In 8.2.3.18, production result-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: result-compartment-contents = result-compartment-element? and result-compartment-element = el-prefix? TBD
    20. In 8.2.3.20, production require-constraints-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: require-constraints-compartment-contents = (require-constraints-compartment-element)* '…'? and require-constraints-compartment-element = el-prefix? TBD
    21. In 8.2.3.20, production assume-constraints-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: assume-constraints-compartment-contents = (assume-constraints-compartment-element)* '…'? and assume-constraints-compartment-element = el-prefix? TBD
    22. In 8.2.3.20, production satisfies-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: satisfies-compartment-contents = (satisfies-compartment-element)* '…'? and satisfies-compartment-element = el-prefix? TBD
    23. In 8.2.3.25, production exposes-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: exposes-compartment-contents = (exposes-compartment-element)* '…'? and exposes-compartment-element = el-prefix? TBD
    24. In 8.2.3.25, production rendering-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: rendering-compartment-contents = (rendering-compartment-element)* '…'? and rendering-compartment-element = el-prefix? TBD
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 13:17 GMT
  • Updated: Thu, 27 Apr 2023 14:50 GMT

Incorrect production for attributes-compartment-element

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

    The production for attributes-compartment-element is incorrectly referencing "UsagePrefix UsageDeclaration".

    It should reference "UsagePrefix Usage".

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 13:15 GMT
  • Updated: Thu, 27 Apr 2023 13:15 GMT

Special graphical notation for distinguished parameters in name compartment

  • Key: SYSML2-61
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 13:08 GMT

Source and target on binary ConnectionDefinition symbol missing

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

    The graphical notation for binary ConnectionDefinition does not clearly indicate the source and target ends.

    The binary ConnectionDef examples and graphical BNF should be updated to clarify source and target notation (e.g., replacing black diamond edge with edge with arrow at target end or source and target key words).

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:57 GMT
  • Updated: Thu, 27 Apr 2023 12:57 GMT

Graphical notation for edges is not 100% consistent

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

    The line and arrow styles for edge symbols representing relationships in the representative notation tables in the Overview subsections 7.*.1 are not completely consistent.

    Ensure consistent styling of all edge symbols in terms of:

    • Line style (solid, long dash, short dash, dotted, ...)
    • Line color (black, gray, ...) if applicable
    • Start marker (black diamond, white diamond, ...)
    • Mid marker (arrow depicting item flow, ...)
    • End marker (arrow/end type, ...)
    • Start / Mid / End labels (multiplicity, role-name, item on item-flow, ...)
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:44 GMT
  • Updated: Thu, 27 Apr 2023 12:44 GMT

Representative notation table uses deprecated «equal»

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

    Representative notation table, in 7.13 Connections, uses the deprecated «equal» notation instead of the standard "=" notation for a binding connector.

    All «equal» notations should be replaced with = notation.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:33 GMT
  • Updated: Thu, 27 Apr 2023 12:33 GMT

Parameter symbol notation needs improvement

  • Key: SYSML2-53
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 12:28 GMT

Port symbol notation (arrows) needs improvement

  • Key: SYSML2-57
  • Status: open  
  • Source: DEKonsult ( 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: Thu, 27 Apr 2023 12:28 GMT

Inconsistent graphical notation n-ary connection examples

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

    The representative notation tables in 7.13.1 Connections Overview, and 7.20.1 Requirements Overview, contain inconsistent examples for n-ary connections.

    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: Thu, 27 Apr 2023 12:19 GMT

Quantity and unit for ratio and fraction

  • Key: SYSML2-55
  • Status: open  
  • Source: Model Driven Solutions ( 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, 26 Apr 2023 23:17 GMT

No support for metadata in graphical notation


Follow typographical conventions in the SysML Metamodel clause

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

    Subclause 8.1 defines typographical conventions to be used in the KerML metamodel. However, these are not being followed consistently throughout Clause 8 and Clause 9.

    Also, subclause 6.3 is inconsistent with 8.1 and should be removed.

  • Reported: SysML 2.0a1 — Tue, 25 Apr 2023 23:11 GMT
  • Updated: Wed, 26 Apr 2023 22:43 GMT

Name all associations in the SysML abstract syntax

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

    MOF constraints require that all associations be named. But none of the associations in the SysML abstract syntax model are currently named. They should all be given generated names.

  • Reported: SysML 2.0a1 — Tue, 25 Apr 2023 23:08 GMT
  • Updated: Wed, 26 Apr 2023 22:42 GMT

Examples requirement derivation, cause effect, and refinement missing

  • Key: SYSML2-52
  • Status: open  
  • Source: DEKonsult ( 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, 26 Apr 2023 22:36 GMT

Loop examples incomplete in representative notation table

  • Key: SYSML2-51
  • Status: open  
  • Source: DEKonsult ( 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, 26 Apr 2023 22:05 GMT

Consider production for standard case view vs filtered general view

  • Key: SYSML2-48
  • Status: open  
  • Source: DEKonsult ( 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, 26 Apr 2023 21:06 GMT

Identify impact views on model organization

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

    Identify the implications of views on the model organization and how to mitigate circular dependencies? Refer to SF nested view presentation and discussed at GSWG on March 8, 2023 as an input.

    (Derived from GSWG ID#09).

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:55 GMT
  • Updated: Wed, 26 Apr 2023 11:58 GMT

RSAOutputPin_Mapping should specialize OutputPin_Mapping

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

    The mapping class RSAOutputPin_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 07:07 GMT
  • Updated: Thu, 20 Apr 2023 07:07 GMT

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

  • Key: SYSML2-18
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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, 19 Apr 2023 21:09 GMT

Incomplete description of TestCaseVerifyObjectiveMembership_Mapping

  • Key: SYSML2-17
  • Status: open  
  • Source: oose Innovative Informatik eG ( 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, 19 Apr 2023 17:16 GMT