${taskforce.name} Avatar
  1. OMG Task Force

Systems Modeling Language (SysML) 2.0 FTF — Open Issues

  • Key: SYSML2
  • Issues Count: 416
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
SYSML2-783 Parsing KerML Feature elements from SysML textual notation SysML 2.0b1 open
SYSML2-637 User-defined keywords are not allowed on enumeration definitions SysML 2.0b1 open
SYSML2-553 checkRequirementUsageObjectiveRedefinition is incorrect SysML 2.0b1 open
SYSML2-643 Comment locale not in textual notation SysML 2.0b1 open
SYSML2-635 Issues with SysML grammar SysML 2.0b1 open
SYSML2-631 User-defined keywords are not allowed on metadata SysML 2.0b1 open
SYSML2-185 ISQ in specification and libraries not aligned SysML 2.0a1 open
SYSML2-848 Issues with SysML/KerML grammar SysML 2.0b1 open
SYSML2-847 incorrect naming of * character SysML 2.0b1 open
SYSML2-85 Effective name is not correct for a redefined perform action usage SysML 2.0a1 open
SYSML2-846 incorrect naming of * character SysML 2.0b1 open
SYSML2-844 Annotation diagram needs to be updated SysML 2.0b1 open
SYSML2-686 Reuse of KerML textual notation productions in the SysML grammar SysML 2.0b1 open
SYSML2-642 Make orthogonal and rounded corners the default connector style for architectural drawings SysML 2.0b1 open
SYSML2-641 Do not use abbreviations for key word in SysML v2/KerML textual concrete syntax SysML 2.0b1 open
SYSML2-640 Find a better way to differ between definition and instance elements in graphical notation SysML 2.0b1 open
SYSML2-639 Change graphical notation for use cases to elliptic elements SysML 2.0b1 open
SYSML2-636 package View and Viewpoint TBD should not be included in the xmi file SysML 2.0b1 open
SYSML2-634 VerificationCase::subVerificationCases is typed incorrectly SysML 2.0b1 open
SYSML2-632 Long-form notation for bindings and successions SysML 2.0b1 open
SYSML2-629 Guillemets are not used on keywords in textual notation snippets used in the graphical notation SysML 2.0a1 open
SYSML2-615 Constraint on Usage variation memberships is too restrictive SysML 2.0b1 open
SYSML2-613 Constraint on Definition variation memberships is too restrictive SysML 2.0b1 open
SYSML2-601 Proxy nodes are missing from states SysML 2.0a1 open
SYSML2-594 PortUsage direction SysML 2.0b1 open
SYSML2-593 Enumerations not specializable SysML 2.0b1 open
SYSML2-592 Flow connections are incorrectly both structure and behavior SysML 2.0b1 open
SYSML2-591 Transformation fails on Enumerations that are ValueTypes SysML 2.0a1 open
SYSML2-590 Helper::getScalarValueType operation is not robust enough SysML 2.0a1 open
SYSML2-589 SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong SysML 2.0a1 open
SYSML2-588 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable SysML 2.0a1 open
SYSML2-587 The mapping name "~InterfaceBlock_Mapping" is not convenient SysML 2.0a1 open
SYSML2-569 Rename ~InterfaceBlock_Mapping SysML 2.0b1 open
SYSML2-586 Literal factories are missing operation for their value SysML 2.0a1 open
SYSML2-585 Factories specified for Literal specification shall be optimized SysML 2.0a1 open
SYSML2-584 Default multiplicities are not managed correctly SysML 2.0a1 open
SYSML2-576 Semantic constraints missing for shorthand succession notation SysML 2.0b1 open
SYSML2-562 Tables in overview sections have empty cells SysML v2 column SysML 2.0b1 open
SYSML2-564 Mapping tables in the overview sections show duplicates in the SysML v2 column SysML 2.0b1 open
SYSML2-561 Intersection missing for some multiple specializations SysML 2.0b1 open
SYSML2-546 Add a distinguished attribute to capture the textual body of a requirement SysML 2.0b1 open
SYSML2-535 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong SysML 2.0a1 open
SYSML2-534 Most SysML::Blocks are owned by a package SysML 2.0a1 open
SYSML2-533 Properties typed by Actors SysML 2.0a1 open
SYSML2-532 OpaqueBehavior shall be transformed even if they are not owned by a Package SysML 2.0a1 open
SYSML2-527 The XMI versions of standard libraries should be delivered SysML 2.0a1 open
SYSML2-91 XMI and JSON for model libraries SysML 2.0a1 open
SYSML2-526 Textual notation for send actions is too limited SysML 2.0b1 open
SYSML2-524 timeslice/snapshot featuring types required to specialize or be same as types SysML 2.0a1 open
SYSML2-516 Namespace_Mapping shall redefine ownedRelationship() SysML 2.0a1 open
SYSML2-515 Relationship_Mapping::ownedRelatedElement() is wrong SysML 2.0a1 open
SYSML2-508 Comment_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-507 GenericToElement_Mapping is missing default rules SysML 2.0a1 open
SYSML2-506 GenericToStateUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-505 GenericToRequirementUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-504 GenericToRelationship_Mapping is missing default rules SysML 2.0a1 open
SYSML2-503 OccurrenceUsage missing portioningFeature SysML 2.0b1 open
SYSML2-502 Control nodes missing from concrete syntax for states SysML 2.0a1 open
SYSML2-487 Graphical notation unclear about user-defined keywords for library extensions SysML 2.0a1 open
SYSML2-486 Graphical notation unclear on optionality of keywords on edges SysML 2.0a1 open
SYSML2-485 Clarify bolding of keywords in concrete graphical syntax SysML 2.0a1 open
SYSML2-484 Incorrect textual notation for rep annotation SysML 2.0a1 open
SYSML2-626 Incorrect textual notation for TextualRepresentation SysML 2.0b1 open
SYSML2-483 Incorrect definition elements in interconnection-element SysML 2.0b1 open
SYSML2-482 Missing production for use case actors and subject SysML 2.0a1 open
SYSML2-479 Missalignment between interface graphical production and notation table SysML 2.0a1 open
SYSML2-478 GBNF for flow connection not mapped to semantics SysML 2.0a1 open
SYSML2-477 AssociationClass_Mapping is uncomplete SysML 2.0b1 open
SYSML2-476 Initializer classes have to be rationalized SysML 2.0b1 open
SYSML2-475 missing graphical bnf for events and event occurrences SysML 2.0a1 open
SYSML2-473 ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless SysML 2.0b1 open
SYSML2-472 Optional language for documentation SysML 2.0b1 open
SYSML2-463 Transformation of UML4SysML::State does not consider entry, do, and exit behavior SysML 2.0b1 open
SYSML2-462 element-node not defined SysML 2.0a1 open
SYSML2-456 Missing production for n-ary connection definition graphical SysML 2.0a1 open
SYSML2-450 Fork/JoinNode succession "other" end multiplicity validations missing SysML 2.0b1 open
SYSML2-449 TimeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2-448 ChangeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2-445 ConstraintProperty should be mapped to a AssertConstraintUsage SysML 2.0b1 open
SYSML2-426 specializesFromLibrary arguments use inconsistent notation for strings SysML 2.0b1 open
SYSML2-397 TransitionUsage requires binding to succession with mandatory end multiplicities SysML 2.0b1 open
SYSML2-390 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2-385 CommentAnnotation_Mapping shall be a "unique" mapping SysML 2.0a1 open
SYSML2-383 Decision/MergeNode SuccessionSpecialization checks missing some constraints SysML 2.0b1 open
SYSML2-357 Representative example "Package with members" to be improved SysML 2.0b1 open
SYSML2-353 Feature modifiers missing in Portion Membership examples SysML 2.0b1 open
SYSML2-352 Feature modefiers missing in Feature Membership examples SysML 2.0b1 open
SYSML2-337 Incomplete example "Individual Occurrence" SysML 2.0b1 open
SYSML2-329 Representative notation for filtered package import missing SysML 2.0b1 open
SYSML2-327 Package import wildcard is missing SysML 2.0b1 open
SYSML2-326 Wrong imported package notation SysML 2.0b1 open
SYSML2-324 Missing representative notation for causation and requirements derivation SysML 2.0b1 open
SYSML2-323 Nesting parameter symbol is missing optional nested parameter SysML 2.0b1 open
SYSML2-320 Binding between action parameters and directed features on ports missing SysML 2.0b1 open
SYSML2-317 Metadata declaration needs clarification SysML 2.0b1 open
SYSML2-316 Symbol for metadata def is missing SysML 2.0b1 open
SYSML2-315 Mapping of ObjectFlows with DecisionNodes SysML 2.0b1 open
SYSML2-314 Mapping of ObjectFlows with JoinNodes SysML 2.0b1 open
SYSML2-313 Mapping of ObjectFlows with ForkNodes SysML 2.0b1 open
SYSML2-311 Transformation does not cover the mapping of Unit and QuantityKind SysML 2.0b1 open
SYSML2-309 Transformation does not cover mapping of Parameter::isStreaming=true SysML 2.0b1 open
SYSML2-307 Various constraints need to take feature chaining into account SysML 2.0b1 open
SYSML2-297 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2-286 the getMapped operation cannot be called on ElementOwnership_Mapping SysML 2.0a1 open
SYSML2-284 Transformation does not cover UML4SysML::FunctionBehavior SysML 2.0a1 open
SYSML2-283 Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet SysML 2.0a1 open
SYSML2-274 Transformation does not cover UML4SysML::DestroyLinkAction SysML 2.0a1 open
SYSML2-273 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 open
SYSML2-272 Transformation does not cover UML4SysML::ReadLinkAction SysML 2.0a1 open
SYSML2-271 Transformation does not cover UML4SysML::SignalEvent SysML 2.0a1 open
SYSML2-225 Some Standard View Definitions should be filtered specializations of General View SysML 2.0a1 open
SYSML2-199 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2-188 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2-187 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2-186 ConstraintBlock mapping parameters to input attributes SysML 2.0a1 open
SYSML2-183 Some package-level features are mandatory SysML 2.0a1 open
SYSML2-177 Assignment action usages do not specify when their expressions are evaluated SysML 2.0a1 open
SYSML2-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-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-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-106 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 open
SYSML2-105 Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete SysML 2.0a1 open
SYSML2-104 Transformation does not cover UML4SysML::GeneralizationSet SysML 2.0a1 open
SYSML2-100 Semantics of a conditional succession using "else" are missing SysML 2.0a1 open
SYSML2-98 Port transfer semantics SysML 2.0a1 open
SYSML2-97 Semantics of transfers across interfaces SysML 2.0a1 open
SYSML2-96 Incorrect action name in graphical notation 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-82 Extend ISQ with missing quantity and unit types for US Customary Units SysML 2.0a1 open
SYSML2-77 Resolve "TODO" in domain library model Time 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-67 Graphical BNF mapping to abstract syntax is missing SysML 2.0a1 open
SYSML2-65 Graphical BNF defines lifeline elements incorrectly SysML 2.0a1 open
SYSML2-64 Missing graphical notation for Flows Compartment 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-57 Port symbol notation (arrows) needs improvement SysML 2.0a1 open
SYSML2-56 Missing graphical notation for n-ary connection def and usage SysML 2.0a1 open
SYSML2-55 Quantity and unit for ratio and fraction SysML 2.0a1 open
SYSML2-53 Parameter symbol notation needs improvement 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-50 No support for metadata in graphical notation SysML 2.0a1 open
SYSML2-49 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2-48 Consider production for standard case view vs filtered general view SysML 2.0a1 open
SYSML2-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-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-33 Identify impact views on model organization SysML 2.0a1 open
SYSML2-32 Clarify query using view SysML 2.0a1 open
SYSML2-31 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2-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-25 Standard view filters incomplete 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
SYSML2-59 Inconsistent graphical notation for succession, message and flow edges SysML 2.0a1 open
SYSML2-430 Subsetting of subjectParameter properties is wrong SysML 2.0b1 open
SYSML2-554 Enumeration definitions VerdictKind and VerificationMethodKind are missing from specification document SysML 2.0b1 open
SYSML2-552 Errors in the TradeStudy domain model SysML 2.0b1 open
SYSML2-182 Universal features can have many values SysML 2.0a1 open
SYSML2-318 Adornments on ends missing in graphical syntax SysML 2.0b1 open
SYSML2-597 checkFlowConnectionUsageSpecialization is too restrictive about FlowConnections SysML 2.0b1 open
SYSML2-558 checkStateUsageSpecialization constraint is incorrect SysML 2.0b1 open
SYSML2-529 OCL for deriveViewDefinitionViewCondition and deriveViewUsageViewCondition are wrong SysML 2.0b1 open
SYSML2-599 Wrong production for adding state-def as a definition node SysML 2.0a1 open
SYSML2-480 Missing production for use case actors and subject SysML 2.0a1 open
SYSML2-620 Textual notation production for Comment is wrong SysML 2.0b1 open
SYSML2-226 Incorrect reference to SysML v1 to SysML v2 Transformation SysML 2.0a1 open
SYSML2-219 Action::decisionTransitions should subset Action::transitions SysML 2.0a1 open
SYSML2-616 User-defined keywords are not allowed on control nodes SysML 2.0b1 open
SYSML2-612 OCL rule deriveUsageNestedFlow references non-existent class called FlowUsage SysML 2.0b1 open
SYSML2-611 OCL rule deriveDefinitionOwnedFlow references non-existent class called FlowUsage SysML 2.0b1 open
SYSML2-583 Incorrect graphical notation for successions examples with actions SysML 2.0b1 open
SYSML2-557 Need to complete and align flow and message notations in GBNF SysML 2.0a1 open
SYSML2-582 Incorrect graphical notation for flow between actions SysML 2.0b1 open
SYSML2-581 Mistakes in example Interface as Node (with flow) SysML 2.0b1 open
SYSML2-580 Incorrect and incomplete sequence view with message SysML 2.0b1 open
SYSML2-579 Incorrect graphical notation for flow connections in Flow as Node SysML 2.0b1 open
SYSML2-578 Incorrect graphical notation for message between ports SysML 2.0b1 open
SYSML2-577 Incorrect graphical notation for flow connection SysML 2.0b1 open
SYSML2-572 Need to remove action control nodes from Statemachines GBNF productions SystemsModelingAPI 1.0b1 open
SYSML2-566 Section containing tables about elements not mapped should get an introductory text SysML 2.0b1 open
SYSML2-560 Add note on FlowFeature direction to textual notation grammar SysML 2.0b1 open
SYSML2-556 Typos in Quantities and Units Domain Library SysML 2.0b1 open
SYSML2-536 TestCaseVerifyRequirementUsage_Mapping.ownedRelationship() SysML 2.0a1 open
SYSML2-459 Resolution of approved issue SYSML2-241 is not considered by merged issue SYSML2-240 SysML 2.0b1 open
SYSML2-499 Assignments parsed without a target will fail validateAssignmentActionUsageArguments SysML 2.0b1 open
SYSML2-481 Use of the term 'Feature' SysML 2.0b1 open
SYSML2-351 Unnecessary event declaration in example "Message" SysML 2.0b1 open
SYSML2-227 Subsections of section 7.7.2.3.7 should be ordered alphabetically SysML 2.0a1 open
SYSML2-94 Confusing naming in Individual Occurrence example SysML 2.0a1 open
SYSML2-336 Incorrect notation in example "Individual Occurrence" SysML 2.0b1 open
SYSML2-80 Reflective SysML abstract syntax model has inconsistencies SysML 2.0a1 open
SYSML2-38 Textual and graphical notations for flow on connection unclear SysML 2.0a1 open
SYSML2-102 Semantic constraint for target of AssignmentActionUsage is missing SysML 2.0a1 open
SYSML2-495 Textual notation BNF for TriggerExpression is wrong SysML 2.0b1 open
SYSML2-68 Graphical notation for nested reference usage needs resolution SysML 2.0a1 open
SYSML2-457 Missing graphical BNF production for keyword extension using #key word in guillemet in compartments SysML 2.0a1 open
SYSML2-458 Missing production for connections with an edge on one or both ends SysML 2.0a1 open
SYSML2-492 KerML constraint requires updates to Domain Library models SysML 2.0a1 open
SYSML2-498 validateTriggerInvocationExpressionWhenArgument constraint is wrong SysML 2.0b1 open
SYSML2-468 binding connector production overly constraining SysML 2.0a1 open
SYSML2-497 validateTriggerInvocationExpressionAfterArgument constraint is too strong SysML 2.0b1 open
SYSML2-491 KerML constraint requires updates to Systems Library models SysML 2.0b1 open
SYSML2-305 Message and flow connection ends should be occurrence usages SysML 2.0b1 open
SYSML2-253 Additional cases when usages are required to be referential SysML 2.0a1 open
SYSML2-28 Validation constraints are missing in the SysML abstract syntax SysML 2.0a1 open
SYSML2-500 The derivation of AssignmentActionUsage::referent is wrong SysML 2.0b1 open
SYSML2-490 Actions::acceptSubactions and sendSubactions should subset acceptActions and sendActions SysML 2.0b1 open
SYSML2-488 Constraints missing to enforce variations being abstract SysML 2.0b1 open
SYSML2-393 Documentation of Time::defaultClock is missing SysML 2.0b1 open
SYSML2-378 Sample::calculation has an incorrect type SysML 2.0b1 open
SYSML2-295 Causation end features need to redefine source and target SysML 2.0a1 open
SYSML2-83 Narrow down return types of SpatialItem::PositionOf and ::CurrentPositionOf SysML 2.0a1 open
SYSML2-79 View::viewpointSatisfactions should subset viewpointChecks and checkedConstraints SysML 2.0a1 open
SYSML2-241 TestCaseVerifyRequirementUsage_Mapping uses non-existing mapping classes SysML 2.0a1 open
SYSML2-513 Missing text in some main mapping sections SysML 2.0b1 open
SYSML2-511 Remove sentence in StateMachines overview section SysML 2.0b1 open
SYSML2-509 Remove sentence in Classification overview section SysML 2.0b1 open
SYSML2-467 RequirementConstraintUsage should not have a RequirementBody SysML 2.0b1 open
SYSML2-453 Text error in List property construction SysML 2.0b1 open
SYSML2-454 PrefixComment should not be a production for AnnotatingElement SysML 2.0b1 open
SYSML2-452 misspelled ConjugatePortTyping should be ConjugatedPortTyping SysML 2.0b1 open
SYSML2-451 Missing production for ConjugatePortTyping SysML 2.0b1 open
SYSML2-431 Incorrect EBNF specification SysML 2.0b1 open
SYSML2-412 SYSML2-180 uses non-existing general mapping class GenericToItemUsage_Mapping SysML 2.0b1 open
SYSML2-422 GenericToItemDefinition_Mapping should specialize GenericToOccurrenceDefinition_Mapping SysML 2.0b1 open
SYSML2-349 Incorrect item flow notation in example "Interface as Node" SysML 2.0b1 open
SYSML2-350 Incomplete flow notation in example "Flow as Node" SysML 2.0b1 open
SYSML2-346 Incorrect notation in example "Binding Connection" SysML 2.0b1 open
SYSML2-333 Incomplete textual notation in example "Variants Compartment" SysML 2.0b1 open
SYSML2-331 Incomplete textual notation in example "Subsetting" SysML 2.0b1 open
SYSML2-280 ElementMain_Mapping::ownedRelationship is wrong SysML 2.0a1 open
SYSML2-139 Transformation does not cover SysMLv1::~InterfaceBlock SysML 2.0a1 open
SYSML2-95 Flows Compartment example graphical notation missing SysML 2.0a1 open
SYSML2-58 Representative notation table uses deprecated «equal» SysML 2.0a1 open
SYSML2-21 RSAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-343 Mistake in example "Part performs a reference action (action1) that references ..." SysML 2.0b1 open
SYSML2-252 Graphical BNF opaque "text block" productions SysML 2.0a1 open
SYSML2-63 Various incorrect Graphical BNF productions SysML 2.0a1 open
SYSML2-425 LoopActionUsage descriptions refer to property not in metamodel SysML 2.0b1 open
SYSML2-299 validateDefinitionVariationSpecialization and validateUsageVariationSpecialization OCL is wrong SysML 2.0b1 open
SYSML2-446 Document how SysML v1 properties are mapped to SysML v2 SysML 2.0b1 open
SYSML2-443 Property_Mapping should map to ItemUsage and the class name is misleading SysML 2.0b1 open
SYSML2-441 Change the table header of the overview tables in the mapping class specification chapters SysML 2.0b1 open
SYSML2-439 UML4SysML::Class should be mapped to ItemDefinition SysML 2.0b1 open
SYSML2-432 Part properties with AggregationKind::none or shared are not mapped to PartUsage with isComposite=false SysML 2.0b1 open
SYSML2-437 The transformation specification does not explicitly specify how to map a ValueType SysML 2.0b1 open
SYSML2-420 InformationFlow mapping classes should use GenericTo mapping classes SysML 2.0b1 open
SYSML2-418 Description of TimeEvent_Mapping is a note SysML 2.0b1 open
SYSML2-416 Description of ChangeEvent_Mapping is a note SysML 2.0b1 open
SYSML2-66 Graphical BNF for n-ary connections missing SysML 2.0a1 open
SYSML2-424 WhileLoopsActionusage title typos SysML 2.0b1 open
SYSML2-210 OCL errors in specialization constraints SystemsModelingAPI 1.0b1 open
SYSML2-423 checkIfActionUsageSpecialization OCL specifiesFromLibrary typo SysML 2.0b1 open
SYSML2-398 TransitionUsage effectAction attribute text and constraint are different SysML 2.0a1 open
SYSML2-414 checkTransitionUsageSourceBindingConnector text and OCL are different SysML 2.0b1 open
SYSML2-356 The OCL for the body of ConstraintUsage::namingFeature is incorrect SysML 2.0b1 open
SYSML2-303 validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization OCL is wrong SysML 2.0b1 open
SYSML2-306 validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization constraints are too restrictive SysML 2.0b1 open
SYSML2-302 validateOccurrenceUsageIndividualDefinition OCL is wrong SysML 2.0b1 open
SYSML2-301 validateUsageOwningType constraint is too restrictive SysML 2.0b1 open
SYSML2-300 validateDefinitionNonVariationMembership and validateUsageNonVariationMembership are redundant with validateVariantMembershipOwningNamespace SysML 2.0b1 open
SYSML2-298 validateDefinitionVariationMembership and validateUsageVariationMembership are too strict SysML 2.0b1 open
SYSML2-254 Redundant numbered list in language description of usage SysML 2.0a1 open
SYSML2-296 validateFramedConcernUsageConstraintKind constraint is misnamed SysML 2.0b1 open
SYSML2-218 Errors in TransitionUsage semantic constraints SysML 2.0a1 open
SYSML2-191 deriveForLoopActionUsageBodyAction is misnamed SysML 2.0a1 open
SYSML2-101 Time triggers are relative to "localClock", not "defaultClock" SysML 2.0a1 open
SYSML2-190 The description and derivation of ForLoopActionUsage::seqArgument is wrong SysML 2.0a1 open
SYSML2-99 Incorrect notation in action examples SysML 2.0a1 open
SYSML2-325 Wrong compartment name: documentation SysML 2.0b1 open
SYSML2-93 Keyword for documentation is "doc" SysML 2.0a1 open
SYSML2-348 Incorrect item flow notation in example "Message" SysML 2.0b1 open
SYSML2-345 Incorrect inherited notation in example "Connection" SysML 2.0b1 open
SYSML2-347 Wrong reference usage notation SysML 2.0b1 open
SYSML2-344 Missing «perform action» in example "Part with Graphical Compartment with perform actions ..." SysML 2.0b1 open
SYSML2-342 Misleading port name in example "Part with Ports" SysML 2.0b1 open
SYSML2-340 Examples "Timeslices Compartment" and "Snapshots Compartment" incorrectly declare state feature SysML 2.0b1 open
SYSML2-341 Compartments still show nested feature notation SysML 2.0b1 open
SYSML2-339 Unnecessarily complicated examples "Timeslices Compartment" and "Snapshots Compartment" SysML 2.0b1 open
SYSML2-338 Incomplete example "Occurrences Compartment" SysML 2.0b1 open
SYSML2-335 Incorrect keyword in example "Attributes Compartment" SysML 2.0b1 open
SYSML2-334 Incorrect example "Relationships Compartment" SysML 2.0b1 open
SYSML2-332 Incorrect example "Variant Membership" SysML 2.0b1 open
SYSML2-328 Incorrect private keyword notation SysML 2.0b1 open
SYSML2-330 Incorrect entry name representative notation SysML 2.0b1 open
SYSML2-322 Nesting parameter symbols should use rounded rectangles SysML 2.0b1 open
SYSML2-321 Nesting port symbols should use rounded rectangles SysML 2.0a1 open
SYSML2-319 Wrong line style on action flow succession SysML 2.0b1 open
SYSML2-287 sq-port-label and sq-ev-occurrence-label productions use Usage SysML 2.0a1 open
SYSML2-312 Typo: Table 19 - requirres SysML 2.0b1 open
SYSML2-47 Graphical BNF productions missing for connections SysML 2.0a1 open
SYSML2-157 Incorrect font in descriptions of AttributeUsage and TransitionUsage SysML 2.0a1 open
SYSML2-304 Mapping of ActivityEdge does not consider ActivityParameterNodes SysML 2.0b1 open
SYSML2-278 UntypedPin_Mapping redefines operation without any changes SysML 2.0a1 open
SYSML2-221 UML4SysML::Activities and StateMachines owned by blocks should be mapped to definition elements SysML 2.0a1 open
SYSML2-281 Map OpqueBehavior always to ActionDefinition SysML 2.0a1 open
SYSML2-258 Mapping of allcation between usage and definition or definition and usage elements does not work SysML 2.0a1 open
SYSML2-250 Typo in AEAReceiverFeatureValue_Mapping::value() SysML 2.0a1 open
SYSML2-248 CreateLinkObjectAction_Mapping should specialize CreateLinkAction_Mapping SysML 2.0a1 open
SYSML2-246 AEAParameterMembership_Mapping::ownedMemberParameter cannot return OclUndefined SysML 2.0a1 open
SYSML2-244 RVVAVariable_Mapping uses CommonAssignmentActionOwningMembership_Mapping, but should be a factory class SysML 2.0a1 open
SYSML2-240 TestCaseActivity_Mapping uses non-existing mapping classes SysML 2.0a1 open
SYSML2-238 ObjectFlows targeting a final node or a activity parameter node cannot be mapped SysML 2.0a1 open
SYSML2-236 Resolution of approved issue SYSML2-23 uses outdated mapping classes SysML 2.0a1 open
SYSML2-234 RSFAReferenceUsageFeatureMembership_Mapping uses non-existing mapping class SysML 2.0a1 open
SYSML2-229 ControlFlowSuccessionAsUsage_Mapping uses non-existing mapping class SysML 2.0a1 open
SYSML2-232 TIAOperatorExpression_Mapping uses non-existing mapping class EqualOperatorExpressionOperand_Mapping SysML 2.0a1 open
SYSML2-228 Helpers::activityOwnedRelationships mixes up FinalNodes and FlowFinalNodes SysML 2.0a1 open
SYSML2-206 Mapping of UML4SysML::InformationFlow with a realizing connector is not supported SysML 2.0a1 open
SYSML2-180 Mapping of UML4SysML::InformationFlow between definition elements is not supported SysML 2.0a1 open
SYSML2-181 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-291 Case View is not a standard view SysML 2.0a1 open
SYSML2-255 Error in textual BNF for MessageDeclaration SysML 2.0a1 open
SYSML2-261 Error in textual BNF for TargetSuccession SysML 2.0a1 open
SYSML2-224 Number missing from table listing Standard View Definitions SysML 2.0a1 open
SYSML2-223 Table 38 "Standard View Definitions" redundant SysML 2.0a1 open
SYSML2-155 Limitation on specifying view renderings SysML 2.0a1 open
SYSML2-84 Connection declaration does not allow a feature value SysML 2.0a1 open
SYSML2-62 Incorrect production for attributes-compartment-element SysML 2.0a1 open
SYSML2-46 Graphical BNF flow-label and interface-label productions missing SysML 2.0a1 open
SYSML2-44 Graphical BNF sq-message-label usage incorrect SysML 2.0a1 open
SYSML2-45 Graphical BNF interconnection view production incorrect SysML 2.0a1 open
SYSML2-43 Graphical BNF sq-message reference incorrect SysML 2.0a1 open
SYSML2-42 Textual production for sq-proxy-label incorrect SysML 2.0a1 open
SYSML2-39 Graphical BNF production sq-part refers to wrong port SysML 2.0a1 open
SYSML2-213 Typo in section 7.6.3 and section 7.6.4: mappingsto 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-208 A ConnectionUsage should be owned by a FeatureMembership relationship SysML 2.0a1 open
SYSML2-202 Filter for mapping class Behavior_Mapping is useless SysML 2.0a1 open
SYSML2-204 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-211 Introduce GenericToTransitionUsage_Mapping class SysML 2.0a1 open
SYSML2-195 GenericToEndFeatureMembership_Mapping::to property redefines itself SysML 2.0a1 open
SYSML2-200 Description of Subsetting mapping classes is not correct 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-189 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class ActivityEdgeInitialNodeSourceEndFeatureMembership_Mapping SysML 2.0a1 open
SYSML2-193 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class SysML 2.0a1 open
SYSML2-88 Mapping of allocation between usage elements is not specified yet SysML 2.0a1 open
SYSML2-171 Optimize Pin mapping class generalization hierarchy SysML 2.0a1 open
SYSML2-173 Mapping of ValueSpecificationActions does not work for untyped pins 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-19 REAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-14 UML4SysML::ClearVariableAction transformation does not include a ReturnParameter SysML 2.0a1 open
SYSML2-23 Transformation of UML4SysML::AddStructuralFeatureValueAction is not correct SysML 2.0a1 open
SYSML2-4 Transformation of UML4SysML::AddVariableValueAction is not correct SysML 2.0a1 open
SYSML2-2 ItemFlowEnds of ObjectFlow transformation target are not defined correctly SysML 2.0a1 open
SYSML2-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-5 UntypedPin_Mapping::filter: property src should be from SysML 2.0a1 open

Issues Descriptions

Parsing KerML Feature elements from SysML textual notation

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

    In some cases, parsing certain short-hand SysML notations results in the creation of KerML Feature elements. In particular, according to 8.2.2.13.1 Connection Definition and Usage, shorthand connection notation such as

    connection connect x to y;
    

    is parsed into a ConnectionUsage with two end features that are KerML Features. However, it is not possible to create ends that are KerML Features in "long hand" SysML notations. For example, in the notation

    connection {
        end references x;
        end references y;
    }
    

    the two ends are parsed as SysML ReferenceUsages, not KerML Features.

    This means that these two examples, while semantically equivalent, are not actually just different surface notations for the same underlying abstract syntax representation. it would be better to have the shorthand notations parse to fully SysML abstract syntax, as much as possible, so that the shorthand notation is just a different surface representation of a certain abstract syntax pattern that can also be equally represented in the full notation.

  • Reported: SysML 2.0b1 — Mon, 22 Jan 2024 04:35 GMT
  • Updated: Tue, 20 Feb 2024 22:17 GMT

User-defined keywords are not allowed on enumeration definitions

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

    The BNF in 8.2.2.8 Enumerations Textual Notation does not allow user-defined keywords on EnumerationDefinitions, even though nested metadata feature annotations are allowed in both cases. (Note that the syntax for EnumerationUsages does allow for user-defined keywords.)

  • Reported: SysML 2.0b1 — Mon, 15 Jan 2024 22:42 GMT
  • Updated: Mon, 19 Feb 2024 04:26 GMT

checkRequirementUsageObjectiveRedefinition is incorrect

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

    In 8.3.20.9 RequirementUsage, the checkRequirementUsageObjectiveRedefinition constraint requires that "A RequirementUsage whose owningFeatureMembership is a ObjectiveMembership must redefine the objectiveRequirement of each CaseDefinition or CaseUsage that is specialized by the owningType of the RequirementUsage." However, the objectiveRequirement property of a CaseDefinition (see 8.3.21.2) or a CaseUsage (see 8.3.21.3) is derived to be only the owned objective of the case. This means that, if a case declares an owned objective, but specializes a case with an inherited objective, then checkRequirementUsageObjectiveRedefinition will actually not be satisfiable.

  • Reported: SysML 2.0b1 — Wed, 22 Nov 2023 04:58 GMT
  • Updated: Mon, 19 Feb 2024 04:16 GMT

Comment locale not in textual notation

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

    In 8.3.4 Annotations Abstract Syntax, in Figure 4 Annotation (from KerML), Comment is shown as having a locale attribute. However, the is no provision for specifying this in the concrete syntax for Comments, neither the textual (8.2.2.4.2 Comments and Documentation) nor graphical (8.2.3.4 Annotations Graphical Notation).

  • Reported: SysML 2.0b1 — Thu, 18 Jan 2024 23:25 GMT
  • Updated: Sat, 17 Feb 2024 03:26 GMT
  • Attachments:

Issues with SysML grammar

  • Key: SYSML2-635
  • Status: open   Implementation work Blocked
  • Source: itemis AG ( David Akehurst)
  • Summary:

    Reuse of KerML rules in SysML grammar is not described sufficiently.
    Not clear which rules are reused and which not.
    Reused rules are simply missing from the SysML definitions.

    Additionally,
    1. AnnotatingElement defined twice: In 8.2.2.4.1 and in 8.2.2.5.2
    2. Extra ')' in 8.2.2.15 AllocationUsageDeclaration
    3. MetadataUsageDeclaration not defined, used in 8.2.2.26 in MetadataUsage
    4. PerformActionDeclaration not defined, used in 8.2.2.17.3 in TransitionPerformActionUsage - should this be PerformActionUsageDeclaration?
    5. StakeholderDefinition not defined, used in 8.2.2.5.2 in DefinitionElement
    6. BindingConnector not defined, used in 8.2.2.6.4 in VariantUsageElement and 8.2.2.14.1 in InterfaceNonOccurrenceUsageElement - should this be BindingConnectorAsUsage
    7. Succession not defined, used in 8.2.2.6.4 in VariantUsageElement and 8.2.2.14.1 in InterfaceNonOccurrenceUsageElement - should this be SuccessionAsUsage
    8. AnnotatingMember defined twice, in 8.2.2.8 and in 8.2.2.4.1
    9. MessageEvent not defined, used in 8.2.2.13.4 in MessageEventMember - should the definition of MessageEnd (after it) be named MessageEvent?
    10. ItemFeature not defined, used in 8.2.2.13.4 in FlowPayloadFeatureMember - should it be FlowPayloadFeature
    11. ItemFlowEnd not defined, used in 8.2.2.13.4 in FlowEndMember - should it be FlowEnd
    12. InterfaceNonOccurrenceUsageMember not defined, used in 8.2.2.14.1 in InterfaceBodyItem - should it be InterfaceNonOccurrenceMember
    13. FeatureChain not defined, used in 8.2.2.16.5 in OwnedFeatureChainMember - should this be OwnedFeatureChain

  • Reported: SysML 2.0b1 — Wed, 10 Jan 2024 18:48 GMT
  • Updated: Sat, 17 Feb 2024 00:25 GMT

User-defined keywords are not allowed on metadata

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

    The productions for MetadataDefinition and MetadataUsage in 8.2.2.26 Metadata Textual Notation do not provide for the use of user-defined keywords, even though it is allowable to have nested metadata usages in both cases.

  • Reported: SysML 2.0b1 — Tue, 2 Jan 2024 19:50 GMT
  • Updated: Sat, 17 Feb 2024 00:08 GMT

ISQ in specification and libraries not aligned

  • Key: SYSML2-185
  • Status: open  
  • Source: NIST ( Mr. 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: Fri, 16 Feb 2024 05:15 GMT

Issues with SysML/KerML grammar

  • Key: SYSML2-848
  • Status: open  
  • Source: itemis AG ( David Akehurst)
  • Summary:

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

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

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

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

  • Reported: SysML 2.0b1 — Wed, 14 Feb 2024 11:32 GMT
  • Updated: Thu, 15 Feb 2024 19:39 GMT

incorrect naming of * character

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

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

  • Reported: SysML 2.0b1 — Thu, 8 Feb 2024 18:16 GMT
  • Updated: Thu, 15 Feb 2024 19:37 GMT

Effective name is not correct for a redefined perform action usage

  • Key: SYSML2-85
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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: Tue, 13 Feb 2024 23:27 GMT

incorrect naming of * character

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

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

  • Reported: SysML 2.0b1 — Thu, 8 Feb 2024 18:14 GMT
  • Updated: Thu, 8 Feb 2024 18:29 GMT

Annotation diagram needs to be updated

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

    The kernel abstract syntax diagram in Figure 4. Annotations (in 8.3.4 Annotations Abstract Syntax) needs to be updated consistent with the resolution to KERML-21 approved by the KerML FTF.

  • Reported: SysML 2.0b1 — Tue, 23 Jan 2024 23:09 GMT
  • Updated: Tue, 6 Feb 2024 01:43 GMT
  • Attachments:

Reuse of KerML textual notation productions in the SysML grammar

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

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

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

  • Reported: SysML 2.0b1 — Fri, 19 Jan 2024 23:51 GMT
  • Updated: Tue, 6 Feb 2024 01:43 GMT

Make orthogonal and rounded corners the default connector style for architectural drawings

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

    In UML and SysML v1 a connector that is used to connect two ports can be a direct connection what is drawn vertically between one port and another.
    The semantics does not differ if it is a direct connection or an orthogonal bented line. SysML user are often electrical or mechanical engineers and they are trained to draw connections between inputs and outputs in an orthogonal way. So why not make this the default connector shape in SysML for all connectors use to connect two ports together?
    Another advice would be to round the corner where the connector is bented. This would avoid misunderstandings when you zoom into a diagram. You can directly recognize that this a connector and not a corner of a component for example. Such a connector style is used as default in the BPMN 2.0 notation and it produces very readable diagrams.

  • Reported: SysML 2.0b1 — Tue, 16 Jan 2024 12:22 GMT
  • Updated: Tue, 6 Feb 2024 01:42 GMT

Do not use abbreviations for key word in SysML v2/KerML textual concrete syntax

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

    I would like to recommend, that abbreviations are not used in key words for the SysML v2 textual notation (resp. KerML). A good example is the key word "def" instead of "definition".
    Why it is here an abbreviation and other (longer) key words are not?
    To make the textual notation more consistent for users, eliminate all abbreviations and write it out.

  • Reported: SysML 2.0b1 — Tue, 16 Jan 2024 12:09 GMT
  • Updated: Tue, 6 Feb 2024 01:42 GMT

Find a better way to differ between definition and instance elements in graphical notation

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

    In SysML v2 parts are drawn in the graphical notation with rounded corners. In UML and and also in SysML v1.x there is a clear graphical language paradigm to use rounded corners only for behavioral elements like activities, states and use cases and all elements showing static aspects of a system like data structures, architectural things etc. are defining elements that have no rounded corners (e.g. classes, objects, blocks, parts, nodes etc.).
    Would it not be possible to find a better graphical notation to differ between definition elements and their instances? What about using different shapes or different stroke widths? Also icons could be used in graphical elements to express a what kind of element it is - like it is done in BPMN for example.
    I think following the rule, that behavioral aspects are modeled with rounded elements and static aspects with not-rounded elements would provide a better compatibility to still existing and well known standards like UML, SysML v1.x, BPMN etc.
    Many people are still trained with high effort in using this notations in their daily work and I think they will be very confused when the should use SysML v2 in the future with that big paradigm shift in the graphical notation.

  • Reported: SysML 2.0b1 — Tue, 16 Jan 2024 12:01 GMT
  • Updated: Tue, 6 Feb 2024 01:42 GMT

Change graphical notation for use cases to elliptic elements

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

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

  • Reported: SysML 2.0b1 — Tue, 16 Jan 2024 11:46 GMT
  • Updated: Tue, 6 Feb 2024 01:42 GMT

package View and Viewpoint TBD should not be included in the xmi file

  • Key: SYSML2-636
  • Status: open  
  • Source: The MathWorks ( Mr. Alan Moore)
  • Summary:

    package x View and Viewpoint TBD should not be included in the SysML.xmi file.

  • Reported: SysML 2.0b1 — Fri, 12 Jan 2024 17:59 GMT
  • Updated: Tue, 6 Feb 2024 01:41 GMT

VerificationCase::subVerificationCases is typed incorrectly

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

    In the Systems Model Library file VerificationCases.sysml, the feature VerificationCase::subVerificationCases is declared as having the type Case. It should instead be VerificationCase. (Note that this is actually specified correctly in the SysML Specification document, 9.2.16.2.2 VerificationCase.)

  • Reported: SysML 2.0b1 — Tue, 9 Jan 2024 00:04 GMT
  • Updated: Tue, 6 Feb 2024 01:41 GMT

Long-form notation for bindings and successions

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

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

  • Reported: SysML 2.0b1 — Tue, 2 Jan 2024 20:04 GMT
  • Updated: Tue, 6 Feb 2024 01:40 GMT

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

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

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

  • Reported: SysML 2.0a1 — Fri, 22 Dec 2023 23:11 GMT
  • Updated: Tue, 6 Feb 2024 01:40 GMT

Constraint on Usage variation memberships is too restrictive

  • Key: SYSML2-615
  • Status: open  
  • Source: The MathWorks ( Mr. Alan Moore)
  • Summary:

    with these two part defs:

    part def Source {
      part B;
    }
    
    part def Target{
      part C;
    }
    

    I want to define a variation of an allocation definition thus:

    variation allocation def theSet {
        end s:Source;
        end t:Target;
        variant allocation Scenario1:theSet {
            allocate s.B to t.C;
        }
    }
    

    and then use it thus:

    part Top {
        part b:Source;
        part a:Target;
    }
    
    allocation alloc1:theSet allocate Top.b to Top.a {
        assert constraint {alloc1 == Scenario1}
    }
    

    However, it seems that variations can only contain variants as members and hence I need to create another allocation definition to hold the ends, thus:

    allocation def theOtherSet {
        end s:Source;
        end t:Target;
    }
    

    and have the variation specialise this new definition thus:

    variation allocation def theSet:>theOtherSet {
        end s:Source;
        end t:Target;
        variant allocation Scenario1:theSet allocate s to t{
            allocate s.B to t.C;
        }
    }
    

    This seems unnecessarily restrictive and I can find no rationale in the spec for this.

  • Reported: SysML 2.0b1 — Wed, 20 Dec 2023 09:50 GMT
  • Updated: Tue, 6 Feb 2024 01:40 GMT

Constraint on Definition variation memberships is too restrictive

  • Key: SYSML2-613
  • Status: open  
  • Source: The MathWorks ( Mr. Alan Moore)
  • Summary:

    with these two part defs:

    part def Source {
      part B;
    }
    
    part def Target{
      part C;
    }
    

    I want to define a variation of an allocation definition thus:

    variation allocation def theSet {
        end s:Source;
        end t:Target;
        variant allocation Scenario1:theSet {
            allocate s.B to t.C;
        }
    }
    

    and then use it thus:

    part Top {
        part b:Source;
        part a:Target;
    }
    
    allocation alloc1:theSet allocate Top.b to Top.a {
        assert constraint {alloc1 == Scenario1}
    }
    

    However, it seems that variations can only contain variants as members and hence I need to create another allocation definition to hold the ends, thus:

    allocation def theOtherSet {
        end s:Source;
        end t:Target;
    }
    

    and have the variation specialise this new definition thus:

    variation allocation def theSet:>theOtherSet {
        end s:Source;
        end t:Target;
        variant allocation Scenario1:theSet allocate s to t{
            allocate s.B to t.C;
        }
    }
    

    This seems unnecessarily restrictive and I can find no rationale in the spec for this.

  • Reported: SysML 2.0b1 — Wed, 20 Dec 2023 09:31 GMT
  • Updated: Tue, 6 Feb 2024 01:40 GMT

Proxy nodes are missing from states

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

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

  • Reported: SysML 2.0a1 — Sun, 17 Dec 2023 16:03 GMT
  • Updated: Tue, 6 Feb 2024 01:39 GMT

PortUsage direction

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

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

  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 18:15 GMT
  • Updated: Tue, 6 Feb 2024 01:39 GMT

Enumerations not specializable

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

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

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

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

    enum def ClassificationLevel {
       enum unclassified;
       enum cui;
       enum secret;
       enum top_secret;
    }
    
    enum def ClassificationLevelClassified :> ClassificationLevel {
        enum secret;
        enum top_secret;
    }
    
  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 17:49 GMT
  • Updated: Tue, 6 Feb 2024 01:39 GMT

Flow connections are incorrectly both structure and behavior

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

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

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

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

  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 17:04 GMT
  • Updated: Tue, 6 Feb 2024 01:39 GMT

Transformation fails on Enumerations that are ValueTypes

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

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

  • Reported: SysML 2.0a1 — Wed, 6 Dec 2023 20:41 GMT
  • Updated: Tue, 6 Feb 2024 01:38 GMT

Helper::getScalarValueType operation is not robust enough

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

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

  • Reported: SysML 2.0a1 — Wed, 6 Dec 2023 16:53 GMT
  • Updated: Tue, 6 Feb 2024 01:38 GMT

SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong

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

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

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:24 GMT
  • Updated: Tue, 6 Feb 2024 01:38 GMT

ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable

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

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

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:21 GMT
  • Updated: Tue, 6 Feb 2024 01:38 GMT

The mapping name "~InterfaceBlock_Mapping" is not convenient

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

    The tilde character is not accepted in a name by most of the progarmming languages. So, it's not convenient to use it in a mapping name that is intended for software implementation

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:18 GMT
  • Updated: Tue, 6 Feb 2024 01:38 GMT

Rename ~InterfaceBlock_Mapping

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

    The special symbol ~ at the beginning is allowed, but it could lead to issues in mapping implementations because most script and programming languages do not allow it.

    The mapping class was introduced by SYSML2-139.

  • Reported: SysML 2.0b1 — Mon, 4 Dec 2023 21:14 GMT
  • Updated: Tue, 6 Feb 2024 01:37 GMT

Literal factories are missing operation for their value

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

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

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:14 GMT
  • Updated: Tue, 6 Feb 2024 01:37 GMT

Factories specified for Literal specification shall be optimized

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

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

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:12 GMT
  • Updated: Tue, 6 Feb 2024 01:37 GMT

Default multiplicities are not managed correctly

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

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

    Factories for LiteralInteger, LiteralInfinity are required

  • Reported: SysML 2.0a1 — Tue, 5 Dec 2023 22:09 GMT
  • Updated: Tue, 6 Feb 2024 01:37 GMT

Semantic constraints missing for shorthand succession notation

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

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

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

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

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 17:12 GMT
  • Updated: Tue, 6 Feb 2024 01:37 GMT

Tables in overview sections have empty cells SysML v2 column

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

    The table in the mapping chapters' overview sections sometimes has no information about the SysML v2 target element. There should be a target element or a note that the rationale for not having a target element can be found in the following section that lists the elements that are not mapped with a justification.

  • Reported: SysML 2.0b1 — Mon, 4 Dec 2023 15:11 GMT
  • Updated: Tue, 6 Feb 2024 01:36 GMT

Mapping tables in the overview sections show duplicates in the SysML v2 column

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

    Some entries in the mapping overview tables show duplicate entries in the SysML v2 column.

  • Reported: SysML 2.0b1 — Mon, 4 Dec 2023 16:47 GMT
  • Updated: Tue, 6 Feb 2024 01:36 GMT

Intersection missing for some multiple specializations

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

    Some multiple specializations in the libraries might be intended to be intersections, including feature specializations. For example, from SYSML2-490, under Actions::Actions

    action sendSubactions: SendAction[0..*] :> subactions, sendActions {
      doc /* 
          * The subactions of this Action that are SendActions. 
          */ 
    }
    
    action acceptSubactions: AcceptAction[0..*] :> subactions, acceptActions {
      doc /* 
          * The subactions of this Action that are AcceptActions. 
          */ 
    }
    
  • Reported: SysML 2.0b1 — Fri, 1 Dec 2023 15:34 GMT
  • Updated: Tue, 6 Feb 2024 01:36 GMT

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

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

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

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

    The concrete syntax should be updated accordingly.

  • Reported: SysML 2.0b1 — Wed, 15 Nov 2023 17:41 GMT
  • Updated: Tue, 6 Feb 2024 01:36 GMT

ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong

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

    ownedRelationship() operation. There is the following code:

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

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

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 21:02 GMT
  • Updated: Tue, 6 Feb 2024 01:36 GMT

Most SysML::Blocks are owned by a package

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

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

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

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:58 GMT
  • Updated: Tue, 6 Feb 2024 01:35 GMT

Properties typed by Actors

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

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

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:53 GMT
  • Updated: Tue, 6 Feb 2024 01:35 GMT

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

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

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

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 20:38 GMT
  • Updated: Tue, 6 Feb 2024 01:35 GMT

The XMI versions of standard libraries should be delivered

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

    The 2023-10 version of SysML2 still not include the XMI version of the standard libraries but only the textual syntax version.

    Because of this, model elements from those libraries have no stable identifiers

  • Reported: SysML 2.0a1 — Thu, 9 Nov 2023 15:45 GMT
  • Updated: Tue, 6 Feb 2024 01:35 GMT

XMI and JSON for model libraries

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 19:54 GMT
  • Updated: Tue, 6 Feb 2024 01:34 GMT

Textual notation for send actions is too limited

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

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

    send payloadExpression via senderExpression to receiverExpression

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

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

  • Reported: SysML 2.0b1 — Wed, 8 Nov 2023 17:26 GMT
  • Updated: Tue, 6 Feb 2024 01:34 GMT

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

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

    Clause 8.3.9.5 (OccurrenceUsage), Constraints, says

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

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

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

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

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

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

    which probably aren't intended in this exampe.

  • Reported: SysML 2.0a1 — Mon, 6 Nov 2023 14:05 GMT
  • Updated: Tue, 6 Feb 2024 01:34 GMT

Namespace_Mapping shall redefine ownedRelationship()

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

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

  • Reported: SysML 2.0a1 — Fri, 3 Nov 2023 18:21 GMT
  • Updated: Tue, 6 Feb 2024 01:34 GMT

Relationship_Mapping::ownedRelatedElement() is wrong

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

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

  • Reported: SysML 2.0a1 — Fri, 3 Nov 2023 17:58 GMT
  • Updated: Tue, 6 Feb 2024 01:34 GMT

Comment_Mapping is missing a default rule

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

    Comment_Mapping is missing a default rule locale

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 18:23 GMT
  • Updated: Tue, 6 Feb 2024 01:33 GMT

GenericToElement_Mapping is missing default rules

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

    GenericToElement_Mapping is missing default rules for:

    • owningRelationship
    • aliasIds
    • declaredShortName
    • isImpliedIncluded
  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 18:07 GMT
  • Updated: Tue, 6 Feb 2024 01:33 GMT

GenericToStateUsage_Mapping is missing a default rule

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

    GenericToStateUsage_Mapping is missing a default rule for isParallel

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:42 GMT
  • Updated: Tue, 6 Feb 2024 01:33 GMT

GenericToRequirementUsage_Mapping is missing a default rule

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

    GenericToRequirementUsage_Mapping is missing a default rule for reqId

  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:39 GMT
  • Updated: Tue, 6 Feb 2024 01:33 GMT

GenericToRelationship_Mapping is missing default rules

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

    GenericToRelationship_Mapping should provide default rules for

    • owningRelatedElement
    • isImplied
  • Reported: SysML 2.0a1 — Thu, 2 Nov 2023 17:34 GMT
  • Updated: Tue, 6 Feb 2024 01:33 GMT

OccurrenceUsage missing portioningFeature

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

    Clause 8.4.5.2 (Occurrence Usages) says

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

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

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

  • Reported: SysML 2.0b1 — Thu, 2 Nov 2023 14:26 GMT
  • Updated: Tue, 6 Feb 2024 01:32 GMT

Control nodes missing from concrete syntax for states

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

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

  • Reported: SysML 2.0a1 — Wed, 1 Nov 2023 13:19 GMT
  • Updated: Tue, 6 Feb 2024 01:32 GMT

Graphical notation unclear about user-defined keywords for library extensions

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:52 GMT
  • Updated: Tue, 6 Feb 2024 01:32 GMT

Graphical notation unclear on optionality of keywords on edges

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:51 GMT
  • Updated: Tue, 6 Feb 2024 01:32 GMT

Clarify bolding of keywords in concrete graphical syntax

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:50 GMT
  • Updated: Tue, 6 Feb 2024 01:31 GMT

Incorrect textual notation for rep annotation

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

    In Table 2, example "Annotation-Textual Representation", the textual notation incorrectly uses "rep about" syntax, while any textual representation element should be owned by, and therefore inside the body of, the element being represented. The upper textual notation fragment must be removed, and the lower fragment kept as is.

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:49 GMT
  • Updated: Tue, 6 Feb 2024 01:31 GMT

Incorrect textual notation for TextualRepresentation

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

    The textual notation for example "Annotation-Textual Representation" in clause 7.4.1 Table 2 is incorrect. A TextualRepresentation is always owned by its represented element, so the keyword about should not be used.

  • Reported: SysML 2.0b1 — Fri, 22 Dec 2023 16:04 GMT
  • Updated: Tue, 6 Feb 2024 01:31 GMT

Incorrect definition elements in interconnection-element

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

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

  • Reported: SysML 2.0b1 — Wed, 18 Oct 2023 13:46 GMT
  • Updated: Tue, 6 Feb 2024 01:31 GMT

Missing production for use case actors and subject

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 12:20 GMT
  • Updated: Tue, 6 Feb 2024 01:31 GMT

Missalignment between interface graphical production and notation table

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 11:24 GMT
  • Updated: Tue, 6 Feb 2024 01:30 GMT

GBNF for flow connection not mapped to semantics

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 11:15 GMT
  • Updated: Tue, 6 Feb 2024 01:30 GMT

AssociationClass_Mapping is uncomplete

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

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

  • Reported: SysML 2.0b1 — Mon, 25 Sep 2023 19:16 GMT
  • Updated: Tue, 6 Feb 2024 01:30 GMT

Initializer classes have to be rationalized

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

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

  • Reported: SysML 2.0b1 — Mon, 25 Sep 2023 18:28 GMT
  • Updated: Tue, 6 Feb 2024 01:30 GMT

missing graphical bnf for events and event occurrences

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

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

  • Reported: SysML 2.0a1 — Mon, 16 Oct 2023 12:57 GMT
  • Updated: Tue, 6 Feb 2024 01:29 GMT

ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless

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

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

  • Reported: SysML 2.0b1 — Thu, 14 Sep 2023 16:56 GMT
  • Updated: Tue, 6 Feb 2024 01:29 GMT

Optional language for documentation

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

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

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

    To provide guidance for users on common formatting

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

    example:
    requirement def SomeRequirement

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

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

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

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

  • Reported: SysML 2.0b1 — Wed, 27 Sep 2023 21:38 GMT
  • Updated: Tue, 6 Feb 2024 01:29 GMT

element-node not defined

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

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

  • Reported: SysML 2.0a1 — Wed, 27 Sep 2023 10:09 GMT
  • Updated: Tue, 6 Feb 2024 01:28 GMT

Missing production for n-ary connection definition graphical

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

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

  • Reported: SysML 2.0a1 — Fri, 22 Sep 2023 12:11 GMT
  • Updated: Tue, 6 Feb 2024 01:28 GMT

Fork/JoinNode succession "other" end multiplicity validations missing

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

    Clause 8.4.12.4 (Control Nodes), under the Join and Fork headings says:

    validateJoinNodeIncomingSuccessions constraint requires that all incoming Successions to a JoinNode have source multiplicity 1..1.

    validateForkNodeOutgoingSuccessions requires that all outgoing Successions from a ForkNode have target multiplicity 1..1.

    but the validation rules are missing from 8.3.16.11 (JoinNode) and 8.3.16.8 (ForkNode), respectively.

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 15:26 GMT
  • Updated: Tue, 6 Feb 2024 01:28 GMT

TimeEvent should be mapped to an accept action instead of TextualRepresentation

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

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

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 11:42 GMT
  • Updated: Tue, 6 Feb 2024 01:28 GMT

ChangeEvent should be mapped to an accept action instead of TextualRepresentation

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

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

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 11:35 GMT
  • Updated: Tue, 6 Feb 2024 01:28 GMT

ConstraintProperty should be mapped to a AssertConstraintUsage

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

    A UML4SysML::ConstraintProperty is currently mapped to a ItemUsage, but should be an AssertConstraintUsage.

  • Reported: SysML 2.0b1 — Sun, 10 Sep 2023 16:27 GMT
  • Updated: Tue, 6 Feb 2024 01:27 GMT

specializesFromLibrary arguments use inconsistent notation for strings

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

    The arguments for specializesFromLibrary are sometimes single quoted and sometimes double quoted. Search on specializesFromLibrary(' and specializesFromLibrary(" to find them.

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 15:35 GMT
  • Updated: Tue, 6 Feb 2024 01:27 GMT

TransitionUsage requires binding to succession with mandatory end multiplicities

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

    Clause 7.13.3 (Bindings as Usages) says

    The end features of a binding always have multiplicity [1..1].

    and Clause 8.3.17.9 (TransitionUsage) includes a constraint requiring a (1 to 1) binding between its succession and transitionLink:

    checkTransitionUsageSuccessionBindingConnector
    A TransitionUsage must have an ownedMember that is a BindingConnector between its succession and the
    inherited Feature TransitionPerformances::TransitionPerformance::transitionLink.
    ownedMember->selectByKind(BindingConnector)->exists(b |
    b.relatedFeatures->includes(succession) and
    b.relatedFeatures->includes(resolveGlobal(
    'TransitionPerformances::TransitionPerformance::transitionLink')))

    with similar text in 8.4.13.3 (Transition Usages). A succession will typically have fewer values than its transition usage, because the succession won't be traversed for every value (occurrence) of its source feature, while its transition usage will have the same number of values as the source feature, conflicting with the 1-1 end multiplicities. Compare to the modeling pattern in KerML Clause 9.2.10.1 (Transition Performances Overview), excerpted in KERML-157.

  • Reported: SysML 2.0b1 — Fri, 25 Aug 2023 19:22 GMT
  • Updated: Tue, 6 Feb 2024 01:27 GMT

Actor and subject parameter notation not effective

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

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

  • Reported: SysML 2.0a1 — Thu, 24 Aug 2023 12:11 GMT
  • Updated: Tue, 6 Feb 2024 01:27 GMT

CommentAnnotation_Mapping shall be a "unique" mapping

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

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

  • Reported: SysML 2.0a1 — Sun, 20 Aug 2023 15:12 GMT
  • Updated: Tue, 6 Feb 2024 01:26 GMT

Decision/MergeNode SuccessionSpecialization checks missing some constraints

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

    Decision/MergeNodes are (indirectly) typed by KerML:Decision/MergePerformance (via specialization of Actions::Action::decisions/merges), which KerML Clause 9.2.9.1 (Control Performances Overview) requires:

    Successions going out of Steps typed by DecisionPerformance or its specializations must:
    • ...
    • be included in a Feature of its featuringBehavior that unions (see 7.3.2.7) all the outgoing Successions, and is bound to the outgoingHBLink of the Step (see 7.3.4.6 on feature chaining).

    Successions coming into Steps typed by MergePerformance or its specializations must:
    • ...
    • subset a Feature of its featuringBehavior that unions all the incoming Successions, and is bound to the incomingHBLink of the Step.

    while constraints in 8.3.16.7 (DecisionNode) and 8.3.16.13 (MergeNode) say

    checkDecisionNodeOutgoingSuccessionSpecialization
    All outgoing Successions from a DecisionNode must subset the inherited outgoingHBLink feature of the DecisionNode.
    sourceConnector->selectByKind(Succession)-> forAll(subsetsChain(this,
    resolveGlobal("ControlPerformances::MergePerformance::outgoingHBLink")))

    checkMergeNodeIncomingSuccessionSpecialization
    All incoming Successions to a MergeNode must subset the inherited incomingHBLink feature of the MergeNode.
    targetConnector->selectByKind(Succession)-> forAll(subsetsChain(this,
    resolveGlobal("ControlPerformances::MergePerformance::incomingHBLink")))

    with similar text in 8.4.12.4 (Control Nodes) under Decision / Merge Nodes. These constraints allow outgoing/incomingHBLink to have values that are not identified by outgoing/incoming successions when none of the successions is traversed. The KerML pattern above introduces a feature unioning the successions and binds it to a chain through decision/merge to outgoing/incomingHBLink, ensuring the HB links are identified by the successions. See Annex A.3.7 (Timing for behaviors, Decisions and merges) for an example, at the end of the model to be executed (first code listing), under "Decision and merge timing constraints".

  • Reported: SysML 2.0b1 — Wed, 16 Aug 2023 17:21 GMT
  • Updated: Tue, 6 Feb 2024 01:26 GMT

Representative example "Package with members" to be improved

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

    The representative notation example "Package with members compartment" shows the members compartment which is the default compartment and does not require a compartment label. Change members compartment label to the requirements compartment label and adjust the package content and textual notation accordingly, i.e. with requirement elements.

  • Reported: SysML 2.0b1 — Thu, 3 Aug 2023 20:39 GMT
  • Updated: Tue, 6 Feb 2024 01:26 GMT

Feature modifiers missing in Portion Membership examples

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

    Add feature modifiers (e.g. ordered for [1..*] timestamps) to "Portion Membership" examples in representative notation tables for Occurrences.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 15:37 GMT
  • Updated: Tue, 6 Feb 2024 01:26 GMT

Feature modefiers missing in Feature Membership examples

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

    Add feature modifiers (e.g. ordered, nonunique) to "Feature Membership" examples in representative notation tables for Definitions and Usage.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 15:35 GMT
  • Updated: Tue, 6 Feb 2024 01:25 GMT

Incomplete example "Individual Occurrence"

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

    In examples "Individual Occurrence", "Timeslice", "Snapshot", add attribute to «individual» «occurrence» and redefine the attribute with value in «timeslice» and «snapshot».

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:17 GMT
  • Updated: Tue, 6 Feb 2024 01:25 GMT

Representative notation for filtered package import missing

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

    Add example package with filter in 7.5.1. The filter should be one of the filters defined in 9.2.19.2.4. Good choice is filter for Requirement.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:10 GMT
  • Updated: Tue, 6 Feb 2024 01:25 GMT

Package import wildcard is missing

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

    Add import qualifier text (* or **) to upper right corner of imported Package

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:58 GMT
  • Updated: Tue, 6 Feb 2024 01:25 GMT

Wrong imported package notation

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

    Example "Package with imported packages (nested packages)" should use dotted instead of dashed outline

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:57 GMT
  • Updated: Tue, 6 Feb 2024 01:25 GMT

Missing representative notation for causation and requirements derivation

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

    Add representative notation for causation (9.5.2.1) and requirements derivation (9.6.2.1) including n-arys. This (and other representative notation examples for domain library models) should probably go into the respective 9.x Overview subclauses, rather than in Clause 7.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:33 GMT
  • Updated: Tue, 6 Feb 2024 01:24 GMT

Nesting parameter symbol is missing optional nested parameter

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

    In the param-t production the nesting parameter pdv is missing an optional nested param-t* element.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:30 GMT
  • Updated: Tue, 6 Feb 2024 01:24 GMT

Binding between action parameters and directed features on ports missing

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

    Add graphical notation to represent binding between action inputs and outputs and directed features on ports.

    The request is to add a representative notation example to Table 11 that shows how directed features of performed actions in parts can be connected to directed features of ports.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:14 GMT
  • Updated: Tue, 6 Feb 2024 01:24 GMT

Metadata declaration needs clarification

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

    Clarify that the identifier for the metadata declaration is the metadata definition name.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:11 GMT
  • Updated: Tue, 6 Feb 2024 01:24 GMT

Symbol for metadata def is missing

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:09 GMT
  • Updated: Tue, 6 Feb 2024 01:23 GMT

Mapping of ObjectFlows with DecisionNodes

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

    The mapping of ObjectFlow in combination with DecisionNodes including the decisionInput is not covered yet by the transformation.

  • Reported: SysML 2.0b1 — Mon, 24 Jul 2023 14:47 GMT
  • Updated: Tue, 6 Feb 2024 01:23 GMT

Mapping of ObjectFlows with JoinNodes

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

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

  • Reported: SysML 2.0b1 — Mon, 24 Jul 2023 14:30 GMT
  • Updated: Tue, 6 Feb 2024 01:23 GMT

Mapping of ObjectFlows with ForkNodes

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

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

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

  • Reported: SysML 2.0b1 — Mon, 24 Jul 2023 13:16 GMT
  • Updated: Tue, 6 Feb 2024 01:23 GMT

Transformation does not cover the mapping of Unit and QuantityKind

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

    The mapping of a Unit and a QuantityKind is not covered by the transformation yet.

  • Reported: SysML 2.0b1 — Thu, 20 Jul 2023 15:04 GMT
  • Updated: Tue, 6 Feb 2024 01:22 GMT
  • Attachments:

Transformation does not cover mapping of Parameter::isStreaming=true

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

    The transformation does not map the Parameter::isStreaming.

  • Reported: SysML 2.0b1 — Tue, 18 Jul 2023 17:12 GMT
  • Updated: Tue, 6 Feb 2024 01:22 GMT

Various constraints need to take feature chaining into account

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

    There are a number of cases in which derived properties require that a referenced feature by of a certain metaclass. For example, the EventOccurrenceUsage::eventOccurrence property is derived as the referencedFeature of the ownedReferenceSubsetting EventOccurrenceUsage (if it has one), but the property is typed as an OccurrenceUsage, so the referencedFeature must be an OccurrenceUsage. This is enforced by the validateEventOccurrenceUsageReference constraint.

    Unfortunately, this does not take feature chaining into account. If the referencedFeature has a feature chain, it will be parsed as a plain Feature, not an OccurrenceUsage. However, the last Feature in the chain should be an OccurrenceUsage, and this OccurrenceUsage is what should be the eventOccurrence of the EventOccurrenceUsage, and what is check by validateEventOccurrenceUsageReference.

    There are similar problems with at least the "reference" derivation and validation constraints for all the subtypes of EventOccurrenceUsage, and perhaps in other cases, too.

  • Reported: SysML 2.0b1 — Sun, 16 Jul 2023 21:30 GMT
  • Updated: Tue, 6 Feb 2024 01:22 GMT

SysML Libraries' elements shall have an elementId defined

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

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

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

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

    Linked to a similar issue raised on KerML

  • Reported: SysML 2.0a1 — Thu, 13 Jul 2023 06:51 GMT
  • Updated: Tue, 6 Feb 2024 01:22 GMT

the getMapped operation cannot be called on ElementOwnership_Mapping

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

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

  • Reported: SysML 2.0a1 — Tue, 4 Jul 2023 20:16 GMT
  • Updated: Tue, 6 Feb 2024 01:21 GMT

Transformation does not cover UML4SysML::FunctionBehavior

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

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

  • Reported: SysML 2.0a1 — Tue, 4 Jul 2023 10:30 GMT
  • Updated: Tue, 6 Feb 2024 01:21 GMT

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

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

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

  • Reported: SysML 2.0a1 — Mon, 3 Jul 2023 16:34 GMT
  • Updated: Tue, 6 Feb 2024 01:21 GMT

Transformation does not cover UML4SysML::DestroyLinkAction

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:59 GMT
  • Updated: Tue, 6 Feb 2024 01:21 GMT

Transformation does not cover UML4SysML::CreateLinkAction

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:58 GMT
  • Updated: Tue, 6 Feb 2024 01:21 GMT

Transformation does not cover UML4SysML::ReadLinkAction

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:56 GMT
  • Updated: Tue, 6 Feb 2024 01:20 GMT

Transformation does not cover UML4SysML::SignalEvent

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:53 GMT
  • Updated: Tue, 6 Feb 2024 01:20 GMT

Some Standard View Definitions should be filtered specializations of General View

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

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

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

  • Reported: SysML 2.0a1 — Wed, 14 Jun 2023 10:44 GMT
  • Updated: Tue, 6 Feb 2024 01:20 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: Tue, 6 Feb 2024 01:20 GMT

Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet


Transformation does not cover the different UML4SysML::PseudoStates

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

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

  • Reported: SysML 2.0a1 — Sat, 6 May 2023 12:22 GMT
  • Updated: Tue, 6 Feb 2024 01:19 GMT

ConstraintBlock mapping parameters to input attributes

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

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

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

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

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

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

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

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

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

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

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

  • Reported: SysML 2.0a1 — Thu, 4 May 2023 15:26 GMT
  • Updated: Tue, 6 Feb 2024 01:19 GMT

Some package-level features are mandatory

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

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

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

    Might be others.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:17 GMT
  • Updated: Tue, 6 Feb 2024 01:18 GMT

Assignment action usages do not specify when their expressions are evaluated

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

    Clause 8.3.16.5 (AssignmentActionUsage), Description, says:

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

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

  • Reported: SysML 2.0a1 — Tue, 2 May 2023 20:38 GMT
  • Updated: Tue, 6 Feb 2024 01:18 GMT

XMI and JSON for example model

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:37 GMT
  • Updated: Tue, 6 Feb 2024 01:18 GMT

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:33 GMT
  • Updated: Tue, 6 Feb 2024 01:18 GMT

Example analysis case fuelEconomyAnalysis

  • Key: SYSML2-159
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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: Tue, 6 Feb 2024 01:17 GMT

Example FrontAxle definition

  • Key: SYSML2-158
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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: Tue, 6 Feb 2024 01:17 GMT

Subject of an include use case usage

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

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

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

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:40 GMT
  • Updated: Tue, 6 Feb 2024 01:17 GMT

Accepters on transition usages from entry actions

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

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

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:29 GMT
  • Updated: Tue, 6 Feb 2024 01:17 GMT

Transformation does not cover SysMLv1::NoBuffer

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:03 GMT
  • Updated: Tue, 6 Feb 2024 01:17 GMT

Transformation does not cover SysMLv1::Overwrite

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:02 GMT
  • Updated: Tue, 6 Feb 2024 01:16 GMT

Transformation does not cover SysMLv1::AllocateActivitiyPartition

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:02 GMT
  • Updated: Tue, 6 Feb 2024 01:16 GMT

Transformation does not cover SysMLv1::PropertySpecificType

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:01 GMT
  • Updated: Tue, 6 Feb 2024 01:16 GMT

Transformation does not cover SysMLv1::EndPathMultiplicity

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:00 GMT
  • Updated: Tue, 6 Feb 2024 01:16 GMT

Transformation does not cover SysMLv1::ParticipantProperty

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:57 GMT
  • Updated: Tue, 6 Feb 2024 01:15 GMT

Transformation does not cover SysMLv1::BoundReference

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:57 GMT
  • Updated: Tue, 6 Feb 2024 01:15 GMT

Transformation does not cover SysMLv1::DistributedProperty

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:55 GMT
  • Updated: Tue, 6 Feb 2024 01:15 GMT

Transformation does not cover SysMLv1::Expose

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:54 GMT
  • Updated: Tue, 6 Feb 2024 01:15 GMT

Transformation does not cover SysMLv1::Conform

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:54 GMT
  • Updated: Tue, 6 Feb 2024 01:14 GMT

Transformation does not cover SysMLv1::View

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:53 GMT
  • Updated: Tue, 6 Feb 2024 01:14 GMT

Transformation does not cover SysMLv1::InvocationOnNestedPortAction

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:51 GMT
  • Updated: Tue, 6 Feb 2024 01:14 GMT

Transformation does not cover SysMLv1::FlowProperty

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:49 GMT
  • Updated: Tue, 6 Feb 2024 01:14 GMT

Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:48 GMT
  • Updated: Tue, 6 Feb 2024 01:14 GMT

Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:47 GMT
  • Updated: Tue, 6 Feb 2024 01:13 GMT

Transformation does not cover SysMLv1::TriggerOnNestedPort

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:46 GMT
  • Updated: Tue, 6 Feb 2024 01:13 GMT

Transformation does not cover UML4SysML::UnmarshallAction

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:45 GMT
  • Updated: Tue, 6 Feb 2024 01:13 GMT

Transformation does not cover UML4SysML::LinkEndData

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:45 GMT
  • Updated: Tue, 6 Feb 2024 01:13 GMT

Transformation does not cover UML4SysML::LinkEndDestructionData

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:44 GMT
  • Updated: Tue, 6 Feb 2024 01:12 GMT

Transformation does not cover UML4SysML::LinkEndCreationData

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:43 GMT
  • Updated: Tue, 6 Feb 2024 01:12 GMT

Transformation does not cover UML4SysML::ConditionalNode

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:42 GMT
  • Updated: Tue, 6 Feb 2024 01:12 GMT

Transformation does not cover UML4SysML::Clause

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:42 GMT
  • Updated: Tue, 6 Feb 2024 01:12 GMT

Transformation does not cover UML4SysML::ActivityPartition

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:41 GMT
  • Updated: Tue, 6 Feb 2024 01:11 GMT

Transformation does not cover UML4SysML::InteractionConstraint

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:39 GMT
  • Updated: Tue, 6 Feb 2024 01:11 GMT

Transformation does not cover UML4SysML::OccurrenceSpecification

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:38 GMT
  • Updated: Tue, 6 Feb 2024 01:11 GMT

Transformation does not cover UML4SysML::Gate

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:37 GMT
  • Updated: Tue, 6 Feb 2024 01:11 GMT

Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:22 GMT
  • Updated: Tue, 6 Feb 2024 01:10 GMT

Transformation does not cover UML4SysML::ConsiderIgnoreFragment

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:21 GMT
  • Updated: Tue, 6 Feb 2024 01:10 GMT

Transformation does not cover UML4SysML::PartDecomposition

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:21 GMT
  • Updated: Tue, 6 Feb 2024 01:10 GMT

Transformation does not cover UML4SysML::GeneralOrdering

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:19 GMT
  • Updated: Tue, 6 Feb 2024 01:10 GMT

Transformation does not cover UML4SysML::Continuation

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:18 GMT
  • Updated: Tue, 6 Feb 2024 01:10 GMT

Transformation does not cover UML4SysML::DestructionOccurrenceSpecification

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:18 GMT
  • Updated: Tue, 6 Feb 2024 01:09 GMT

Transformation does not cover UML4SysML::Image

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:17 GMT
  • Updated: Tue, 6 Feb 2024 01:09 GMT

Transformation does not cover UML4SysML::Interval

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:16 GMT
  • Updated: Tue, 6 Feb 2024 01:09 GMT

Transformation does not cover UML4SysML::TimeConstraint

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:15 GMT
  • Updated: Tue, 6 Feb 2024 01:09 GMT

Transformation does not cover UML4SysML::DurationInterval

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:15 GMT
  • Updated: Tue, 6 Feb 2024 01:08 GMT

Transformation does not cover UML4SysML::StringExpression

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:14 GMT
  • Updated: Tue, 6 Feb 2024 01:08 GMT

Transformation does not cover UML4SysML::DurationObservation

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:13 GMT
  • Updated: Tue, 6 Feb 2024 01:08 GMT

Transformation does not cover UML4SysML::IntervalConstraint

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:12 GMT
  • Updated: Tue, 6 Feb 2024 01:08 GMT

Transformation does not cover UML4SysML::TimeObservation

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:12 GMT
  • Updated: Tue, 6 Feb 2024 01:07 GMT

Transformation does not cover UML4SysML::Duration

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:11 GMT
  • Updated: Tue, 6 Feb 2024 01:07 GMT

Transformation does not cover UML4SysML::DurationConstraint

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:10 GMT
  • Updated: Tue, 6 Feb 2024 01:07 GMT

Transformation does not cover UML4SysML::TimeInterval

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:09 GMT
  • Updated: Tue, 6 Feb 2024 01:07 GMT

Transformation does not cover UML4SysML::Extend

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:07 GMT
  • Updated: Tue, 6 Feb 2024 01:06 GMT

Transformation of UML4SysML::ActivityFinalNode is not specified yet

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:04 GMT
  • Updated: Tue, 6 Feb 2024 01:06 GMT

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:01 GMT
  • Updated: Tue, 6 Feb 2024 01:06 GMT

Transformation does not cover UML4SysML::GeneralizationSet

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 06:56 GMT
  • Updated: Tue, 6 Feb 2024 01:06 GMT

Semantics of a conditional succession using "else" are missing

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

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

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

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

    DefaultTargetSuccession : TransitionUsage =
        'else' ownedRelationship += TransitionSuccessionMember
    

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 22:10 GMT
  • Updated: Tue, 6 Feb 2024 01:06 GMT

Port transfer semantics

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

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

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:28 GMT
  • Updated: Tue, 6 Feb 2024 01:05 GMT

Semantics of transfers across interfaces

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

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

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:23 GMT
  • Updated: Tue, 6 Feb 2024 01:05 GMT

Incorrect action name in graphical notation example

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:07 GMT
  • Updated: Tue, 6 Feb 2024 01:05 GMT

Redefining feature information missing from specification document

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 19:33 GMT
  • Updated: Tue, 6 Feb 2024 01:04 GMT

Add standard domain libraries for mathematical and physical constants


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

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

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:53 GMT
  • Updated: Tue, 6 Feb 2024 01:04 GMT

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

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

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

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

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:14 GMT
  • Updated: Tue, 6 Feb 2024 01:03 GMT

Resolve "TODO" in domain library model Time

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

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

     * TODO: Add constraint to verify ISO 8691 extended string encoding.
    
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 18:47 GMT
  • Updated: Tue, 6 Feb 2024 01:03 GMT

Graphical BNF for grid rendering is missing

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

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

    This should be added.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:36 GMT
  • Updated: Tue, 6 Feb 2024 01:03 GMT

Graphical notation for variant inheritance from variation requires improvement

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

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:33 GMT
  • Updated: Tue, 6 Feb 2024 01:03 GMT

Graphical BNF mapping to abstract syntax is missing

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:09 GMT
  • Updated: Tue, 6 Feb 2024 01:03 GMT

Graphical BNF defines lifeline elements incorrectly

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:58 GMT
  • Updated: Tue, 6 Feb 2024 01:02 GMT

Missing graphical notation for Flows Compartment

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:55 GMT
  • Updated: Tue, 6 Feb 2024 01:02 GMT

Special graphical notation for distinguished parameters in name compartment

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 13:01 GMT
  • Updated: Tue, 6 Feb 2024 01:02 GMT

Source and target on binary ConnectionDefinition symbol missing

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:57 GMT
  • Updated: Tue, 6 Feb 2024 01:02 GMT

Port symbol notation (arrows) needs improvement

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:21 GMT
  • Updated: Tue, 6 Feb 2024 01:01 GMT

Missing graphical notation for n-ary connection def and usage

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:19 GMT
  • Updated: Tue, 6 Feb 2024 01:01 GMT

Quantity and unit for ratio and fraction

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

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

    Similarly fraction, FractionValue and FractionUnit would be useful.

    Add these concepts as specializations of DimensionOneValue and DimensionOneUnit.

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 23:17 GMT
  • Updated: Tue, 6 Feb 2024 01:01 GMT

Parameter symbol notation needs improvement

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

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:32 GMT
  • Updated: Tue, 6 Feb 2024 01:01 GMT

Examples requirement derivation, cause effect, and refinement missing

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:13 GMT
  • Updated: Tue, 6 Feb 2024 01:00 GMT

Loop examples incomplete in representative notation table

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:04 GMT
  • Updated: Tue, 6 Feb 2024 01:00 GMT

No support for metadata in graphical notation


Specification of standard geometric view missing

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 21:00 GMT
  • Updated: Tue, 6 Feb 2024 01:00 GMT

Consider production for standard case view vs filtered general view

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:54 GMT
  • Updated: Tue, 6 Feb 2024 00:59 GMT

Graphical BNF production proxy refers to wrong label

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:40 GMT
  • Updated: Tue, 6 Feb 2024 00:59 GMT

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:28 GMT
  • Updated: Tue, 6 Feb 2024 00:59 GMT

Identify the owning context in a graphical view

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:08 GMT
  • Updated: Tue, 6 Feb 2024 00:59 GMT

Regularization of textual notation for loops

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:02 GMT
  • Updated: Tue, 6 Feb 2024 00:59 GMT

Missing explicit explanation of compartments as views

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:01 GMT
  • Updated: Tue, 6 Feb 2024 00:58 GMT

Missing graphical notation allocating flow to connection

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

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

    This should be added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:58 GMT
  • Updated: Tue, 6 Feb 2024 00:58 GMT

Identify impact views on model organization

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

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

    Approaches to representing nested views

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

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

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

    Case 2. View exposes packages with views

    Case 3. View contains nested views

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:55 GMT
  • Updated: Tue, 6 Feb 2024 00:58 GMT
  • Attachments:

Clarify query using view

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

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

    This should be clarified and added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:53 GMT
  • Updated: Tue, 6 Feb 2024 00:58 GMT

Icons for standard view definitions missing

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:50 GMT
  • Updated: Tue, 6 Feb 2024 00:57 GMT

Follow typographical conventions in the SysML Metamodel clause

  • Key: SYSML2-30
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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: Tue, 6 Feb 2024 00:57 GMT

Name all associations in the SysML abstract syntax

  • Key: SYSML2-29
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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: Tue, 6 Feb 2024 00:57 GMT

Standard view filters incomplete

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

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

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

  • Reported: SysML 2.0a1 — Sun, 23 Apr 2023 18:07 GMT
  • Updated: Tue, 6 Feb 2024 00:57 GMT

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

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

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

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 17:29 GMT
  • Updated: Tue, 6 Feb 2024 00:56 GMT

Incomplete description of TestCaseVerifyObjectiveMembership_Mapping

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

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

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 17:16 GMT
  • Updated: Tue, 6 Feb 2024 00:56 GMT

Inconsistent graphical notation for succession, message and flow edges


Subsetting of subjectParameter properties is wrong

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

    The properties RequirementUsage::subjectParameter and CaseUsage::subjectParameter in the abstract syntax SysML.xmi currently subset Behavior::parameter. However, neither RequirementUsage nor CaseUsage specialize Behavior. Rather they (indirectly) specialize Step, so the subjectParameter properties should be subsetting Step::parameter rather than Behavior::parameter.

    (Note that this error is not apparent in the specification document, because, in the annotation for subsetting, the subsetted parameter is shown without qualification – e.g., just parameter, not Behavior::parameter.)

  • Reported: SysML 2.0b1 — Mon, 4 Sep 2023 18:27 GMT
  • Updated: Thu, 25 Jan 2024 19:29 GMT

Enumeration definitions VerdictKind and VerificationMethodKind are missing from specification document

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

    The enumeration definitions VerdictKind and VerificationMethodKind, which are in the normative Systems Model Library package VerificationCases, are missing from Systems Model Library subclause 9.2.16 Verification Cases in the SysML Specification.

  • Reported: SysML 2.0b1 — Wed, 22 Nov 2023 18:58 GMT
  • Updated: Thu, 25 Jan 2024 00:03 GMT

Errors in the TradeStudy domain model

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

    In the Analysis Domain Library model TradeStudies::TradeStudy, the requirement definitions MinimizeObjective and MaximizeObjective explicitly redefine the parameter best from the TradeStudyObjective definition they specialize, but do not declare any other parameters. However, this violates the checkFeatureParameterRedefinition constraint, which requires that parameters be redefined in order. And, if the implied redefinition is added to the actual first parameter selectedAlternative, then this also violates the validateRedefinitionDirectionConformance constraint (add by the approved resolution to KERML-20), because best is an out parameter, while selectedAlternative is an in parameter.

  • Reported: SysML 2.0b1 — Tue, 21 Nov 2023 22:35 GMT
  • Updated: Wed, 24 Jan 2024 23:54 GMT

Universal features can have many values

  • Key: SYSML2-182
  • Status: open  
  • Source: NIST ( Mr. 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, 24 Jan 2024 23:23 GMT

Adornments on ends missing in graphical syntax

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

    Graphical notation is missing support for adornments on ends of ConnectionDefinitions, such as ordered, nonunique, readonly, subsets, and redefines. This is needed for information modeling and compatibility with UML and SysML v1. In UML (and SysML v1) these adornments are called 'property modifiers'. Analogously, in KerML and SysML v2 the term 'feature modifiers' would seem appropriate.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:12 GMT
  • Updated: Wed, 24 Jan 2024 21:50 GMT
  • Attachments:

checkFlowConnectionUsageSpecialization is too restrictive about FlowConnections

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

    In 8.3.13.7 FlowConnectionUsage, the constraint checkFlowConnectionUsageSpecialization states that

    If a FlowConnectionUsage has no itemFlowEnds, then it must directly or indirectly specialize the base FlowConnectionUsage Connections::messageConnections from the Systems Library model. Otherwise, it must directly or indirectly specialize the FlowConnectionUsage Connections::flowConnections.

    The property itemFlowEnds is derived as all connectorEnds that are ItemFlowEnds. The (Kernel) metaclass ItemFlowEnd is used when a FlowConnectionUsage is parsed from the special flow notation. However, a FlowConnectionUsage can also be written using regular connection notation, which will not have ItemFlowEnds, e.g.,

    flow {
        end ::>> operator {
            out cmd : Command :>> sourceOutput;
        }
        end ::>> device {
            in cmd  : Command :>> targetInput;
        }
    }
    

    But, currently, this will implicitly specialize messageConnections, not flowConnections, which seems unexpected, since this is structurally a complete flow declaration.

  • Reported: SysML 2.0b1 — Thu, 14 Dec 2023 21:46 GMT
  • Updated: Mon, 22 Jan 2024 23:15 GMT

checkStateUsageSpecialization constraint is incorrect

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

    In 8.3.17.6 StateUsage, the description of checkStateUsageSpecialization is

    A StateUsage must directly or indirectly specialize the StateUsage States::stateActions from the Systems Model Library.

    but the OCL is

    specializesFromLibrary('States::StateAction')
    

    which requires specialization of StateAction, not stateActions.

  • Reported: SysML 2.0b1 — Wed, 29 Nov 2023 21:10 GMT
  • Updated: Mon, 22 Jan 2024 23:10 GMT

OCL for deriveViewDefinitionViewCondition and deriveViewUsageViewCondition are wrong

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

    The OCL for the constraints deriveViewDefinitionViewCondition and deriveViewUsageViewCondition are both

    viewCondition = featureMembership->
        selectByKind(ElementFilterMembership).
        condition
    

    This is clearly wrong, since ElementFilterMemberships are not featureMemberships.

    In addition, the description of the deriveViewUsageViewCondition constraint refers to ViewDefinition instead of ViewUsage, as do the descriptions of deriveViewUsageSatsifiedViewpoint, deriveViewUsageViewRendering and validateViewUsageOnlyOneViewRendering. (And the description of deriveViewUsageExposedElement is missing.)

  • Reported: SysML 2.0b1 — Sat, 11 Nov 2023 22:19 GMT
  • Updated: Mon, 22 Jan 2024 23:08 GMT

Wrong production for adding state-def as a definition node

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

    In subclause 8.2.3.17 - states gbnf definition-node is being augmented with action-def instead of state-def

  • Reported: SysML 2.0a1 — Sun, 17 Dec 2023 15:25 GMT
  • Updated: Tue, 16 Jan 2024 14:06 GMT

Missing production for use case actors and subject


Textual notation production for Comment is wrong

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

    In the textual notation grammar, the BNF production for Comment requires that a Comment always include the keyword comment. This is inconsistent with the description in 7.4.2 Comments and Documentation, which allows comments of the form /* ... */, without the keyword.

  • Reported: SysML 2.0b1 — Thu, 21 Dec 2023 04:44 GMT
  • Updated: Fri, 12 Jan 2024 17:44 GMT

Incorrect reference to SysML v1 to SysML v2 Transformation

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

    Clause 6.1 Document Overview contains an incorrect reference to the SysML v1 to SysML v2 Transformation Specification. The last line of the second paragraph refers to Annex C, which is no longer a correct reference.

  • Reported: SysML 2.0a1 — Wed, 14 Jun 2023 22:00 GMT
  • Updated: Fri, 12 Jan 2024 16:57 GMT

Action::decisionTransitions should subset Action::transitions

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

    In the SysML specification document, in 9.2.9.2.4 Action, the feature decisionActions is stated as subsetting transitions. However, in the normative Actions.sysml library model, Action::decisionTransitions currently subsets transitionActions. It should instead subset Action::transitions, as given in the specification.

  • Reported: SysML 2.0a1 — Sun, 28 May 2023 19:32 GMT
  • Updated: Fri, 12 Jan 2024 16:44 GMT

User-defined keywords are not allowed on control nodes

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

    In the textual notation grammar, in 8.2.2.16.3 Control Nodes, the ControlNodePrefix production does not allow the use of user-defined keywords in the prefix of control-node declarations in the body of an action. There is no real reason why this should not be allowed. It seems to be simply an oversight in the BNF.

  • Reported: SysML 2.0b1 — Wed, 20 Dec 2023 22:05 GMT
  • Updated: Tue, 9 Jan 2024 00:15 GMT

OCL rule deriveUsageNestedFlow references non-existent class called FlowUsage

  • Key: SYSML2-612
  • Status: open  
  • Source: The MathWorks ( Mr. Alan Moore)
  • Summary:

    The description indicates that it should be FlowConnectionUsage

  • Reported: SysML 2.0b1 — Wed, 20 Dec 2023 09:04 GMT
  • Updated: Tue, 9 Jan 2024 00:15 GMT

OCL rule deriveDefinitionOwnedFlow references non-existent class called FlowUsage

  • Key: SYSML2-611
  • Status: open  
  • Source: The MathWorks ( Mr. Alan Moore)
  • Summary:

    The description indicates that this should be FlowConnectionUsage.

  • Reported: SysML 2.0b1 — Wed, 20 Dec 2023 09:02 GMT
  • Updated: Tue, 9 Jan 2024 00:15 GMT

Incorrect graphical notation for successions examples with actions

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

    In subclause 7.16.1, Table 14, in the 7 examples "Perform Actions Swimlanes", "Actions with and without Conditional Succession", "Actions with and without Conditional Succession", "Actions with Control Nodes", "Action with Loop (body in textual notation)", "Action with Loop (body in graphical notation)", "Accept and Send Action Flow", the successions should be represented as dashed lines. The arrow heads are correct.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 21:59 GMT
  • Updated: Tue, 9 Jan 2024 00:15 GMT

Need to complete and align flow and message notations in GBNF

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

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

  • Reported: SysML 2.0a1 — Wed, 29 Nov 2023 15:00 GMT
  • Updated: Tue, 9 Jan 2024 00:15 GMT

Incorrect graphical notation for flow between actions

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

    In subclause 7.16.1, Table 14, in example "Action with Graphical Compartment showing standard action flow view" the flow between the actions should use a black filled arrow head.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 21:59 GMT
  • Updated: Tue, 9 Jan 2024 00:15 GMT

Mistakes in example Interface as Node (with flow)

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

    Subclause 7.14.1, Table 12, example "Interface as Node (with flow)" has the following mistakes: (1) label item1 : Item1 near the flow arrow head on interface2 should be prepended with «flow» «of». (2) the message flows in the interface2 node should use the open message arrow heads. (3) . (4) The textual and graphical notation should use reference-subsetting in the specification of interface2, i.e. replace :> with ::> (two times in graphical notation, and two times in textual notation). It is also recommended to use shorter names in the example to make it more compact.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 21:58 GMT
  • Updated: Tue, 9 Jan 2024 00:15 GMT

Incorrect and incomplete sequence view with message

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

    In subclause 7.13.1, Table 11, in example "Message" the message transfer between the life lines should use the open arrow head for message.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 21:57 GMT
  • Updated: Tue, 9 Jan 2024 00:14 GMT

Incorrect graphical notation for flow connections in Flow as Node

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

    In subclause 7.13.1, Table 11, in example "Flow as Node" the 3 flow connections in the «flow» node should use the black filled arrow head for flow connection.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 21:53 GMT
  • Updated: Tue, 9 Jan 2024 00:14 GMT

Incorrect graphical notation for message between ports

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

    In subclause 7.13.1, Table 11, in example "Message" the message symbol between two ports of parts should use the message open arrow head. Also the text above the message edge should read «message» «of» item1 : Item1.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 21:52 GMT
  • Updated: Tue, 9 Jan 2024 00:14 GMT

Incorrect graphical notation for flow connection

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

    In subclause 7.13.1, Table 11, in example "Flow" the flow connection between directed features of two actions should use the filled black arrow head. Also, the rounded square symbols for the parameters (directed features) should be placed adjacent to the action box outlines.

  • Reported: SysML 2.0b1 — Tue, 5 Dec 2023 21:48 GMT
  • Updated: Tue, 9 Jan 2024 00:14 GMT

Need to remove action control nodes from Statemachines GBNF productions

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

    Currently state machines GBNF allows for inclusion of control nodes:
    fork, join, merge, final
    They are not currently supported by SysML v2 state semantics and concrete syntax and need to be removed

  • Reported: SystemsModelingAPI 1.0b1 — Mon, 4 Dec 2023 18:30 GMT
  • Updated: Tue, 9 Jan 2024 00:14 GMT

Section containing tables about elements not mapped should get an introductory text

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

    The section containing the tables about the elements that have no mapping defined should start with a text that briefly describes the purpose of the section.

  • Reported: SysML 2.0b1 — Mon, 4 Dec 2023 17:15 GMT
  • Updated: Tue, 9 Jan 2024 00:14 GMT

Add note on FlowFeature direction to textual notation grammar

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

    The approved resolution to KERML-195 adds a note to the ItemFlowFeature production in the KerML concrete syntax grammar on properly setting the direction of the synthesized feature. A similar note should be added to the FlowFeature production in subclause 8.2.2.13.4 of the SysML textual notation grammar.

  • Reported: SysML 2.0b1 — Fri, 1 Dec 2023 04:14 GMT
  • Updated: Tue, 9 Jan 2024 00:13 GMT

Typos in Quantities and Units Domain Library

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

    1. Subclause 9.8.1 paragraph 2 sentence 2, contains a typo: "The library also provides enables the specification ..." should read "The library also enables the specification ...", i.e. delete "provides".
    2. Subclause 9.8.2.1 example 1 under Free versus Bound Quantities and Vector Spaces, contains a typo: "Displacement vector (free) and the position vector (bound), ..." should read "Displacement vector (free) and position vector (bound), ...", i.e. delete "the".

  • Reported: SysML 2.0b1 — Sun, 26 Nov 2023 13:32 GMT
  • Updated: Tue, 9 Jan 2024 00:13 GMT

TestCaseVerifyRequirementUsage_Mapping.ownedRelationship()

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

    TestCaseVerifyRequirementUsage_Mapping.ownedRelationship() contains the following code:

    CaseSubjectMembership_Mapping.getMapped(from.client),
    

    Since from.client is a collection the code specified cannot work. This makes MIWIG test case #37 failing

  • Reported: SysML 2.0a1 — Mon, 13 Nov 2023 21:06 GMT
  • Updated: Tue, 9 Jan 2024 00:13 GMT

Resolution of approved issue SYSML2-241 is not considered by merged issue SYSML2-240


Assignments parsed without a target will fail validateAssignmentActionUsageArguments

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

    The approved resolution to SYSML2-28 included the adding of the constraint validateAssignmentActionUsageArguments, which requires that an AssignmentActionUsage have two arguments. However, in the SysML Specification, 8.2.2.16.5 Assignment Action Usages, the AssignmentTargetParameter is optional for an AssignmentNodeDeclaration. An AssignmentActionUsage parsed without a target parameter argument will then fail the validateAssignmentActionUsageArguments.

    In 7.16.9 Assignment Action Usages it states that "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 enforcing this, so it is not clear how the informal statement is supposed to be realized.

  • Reported: SysML 2.0b1 — Fri, 27 Oct 2023 16:30 GMT
  • Updated: Tue, 9 Jan 2024 00:12 GMT

Use of the term 'Feature'

  • Key: SYSML2-481
  • Status: open  
  • Source: itemis AG ( Dr. David Akehurst)
  • Summary:

    The use of the term feature in the document is inconsistent with the ISO standard definition

    Feature - ISO/IEC/IEEE 29148:2018
    A feature is an externally desired service by the system that may require a sequence of inputs to effect the desired result.

    • For example, in a telephone system, features include
      • local call,
      • call forwarding and
      • conference call.
    • Each feature is generally described in a sequence of stimulus response pairs.

    I.e. a feature of a system is about externally visible system behaviour

    Feature is a generic term and has many different meanings in different fields/contexts.
    However in System Engineering, the word is usually used as defined by the ISO standard (above).

    The use of the term 'feature' in the SysML 2 document is definitely NOT consistent with the ISO definition.
    Suggestion for a better term in the SysML 2 would be something like Member, Attribute, Aspect, Detail.

  • Reported: SysML 2.0b1 — Wed, 18 Oct 2023 07:26 GMT
  • Updated: Tue, 9 Jan 2024 00:12 GMT

Unnecessary event declaration in example "Message"

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

    In (the second) example "Message" the event details should be removed from textual notation. The message becomes message msg1 from a1 to a2 in textual notation.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:44 GMT
  • Updated: Tue, 9 Jan 2024 00:12 GMT

Subsections of section 7.7.2.3.7 should be ordered alphabetically

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

    The subsections of section 7.7.2.3.7 should be ordered alphabetically.

  • Reported: SysML 2.0a1 — Tue, 20 Jun 2023 18:30 GMT
  • Updated: Tue, 9 Jan 2024 00:12 GMT

Confusing naming in Individual Occurrence example

  • Key: SYSML2-94
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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: Tue, 9 Jan 2024 00:11 GMT

Incorrect notation in example "Individual Occurrence"

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

    Example "Individual Occurrence" should include individual def from preceding example, and rename occurrence1 to occurrence1-1.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:16 GMT
  • Updated: Tue, 9 Jan 2024 00:11 GMT
  • Attachments:

Reflective SysML abstract syntax model has inconsistencies

  • Key: SYSML2-80
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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: Tue, 9 Jan 2024 00:11 GMT

Textual and graphical notations for flow on connection unclear

  • Key: SYSML2-38
  • Status: open  
  • Source: DEKonsult ( Mr. 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: Tue, 9 Jan 2024 00:11 GMT

Semantic constraint for target of AssignmentActionUsage is missing

  • Key: SYSML2-102
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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 to enforce this (see 8.3.16.5).

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 22:28 GMT
  • Updated: Sat, 30 Dec 2023 23:27 GMT

Textual notation BNF for TriggerExpression is wrong

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

    Time and change triggers for an accept action are supposed to be parsed as a TriggerInvocationExpression with a single argument: for a time trigger, the argument is a duration or time instant, while for a change trigger it is a boolean expression. However, the textual notation BNF for TriggerExpression in 8.2.2.16.4 is not properly parsing the textual notation as an invocation with arguments. As a result, the intended argument expression for the TriggerInocationExpression will not actually be recognized as an argument of the invocation.

  • Reported: SysML 2.0b1 — Thu, 26 Oct 2023 13:33 GMT
  • Updated: Mon, 11 Dec 2023 07:38 GMT

Graphical notation for nested reference usage needs resolution

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

    According to the Graphical BNF, the notation for a nested 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). In the Graphical BNF productions this is represented by rd = (reference-diamond)? as defined in clause 8.2.3.6. 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.

    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.

    After discussion the Graphical Specification WG recommends to replace the upper-right-hand corner reference-diamond notation with a dotted-outline for reference usage, and stay with a solid-outline for composite usage.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:16 GMT
  • Updated: Mon, 11 Dec 2023 07:30 GMT
  • Attachments:

Missing graphical BNF production for keyword extension using #key word in guillemet in compartments

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

    Current Graphical BNF needs to have a production for a keyword notation with and without the base class enabled for all name compartments.

  • Reported: SysML 2.0a1 — Fri, 22 Sep 2023 16:46 GMT
  • Updated: Mon, 11 Dec 2023 07:29 GMT
  • Attachments:

Missing production for connections with an edge on one or both ends

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

    Graphical BNF should allow for graphical relationships such as causation connection from a state (i.e. cause) to a transition (i.e. effect) or from one transition (i.e., cause) to another transition (i.e., effect). These should be supported in the general view.

  • Reported: SysML 2.0a1 — Fri, 22 Sep 2023 16:57 GMT
  • Updated: Mon, 11 Dec 2023 06:44 GMT
  • Attachments:

KerML constraint requires updates to Domain Library models

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

    The approved resolution to KERML-20 adds the validation constraint validateFeatureValueOverriding that "All Features directly or indirectly redefined by the featureWithValue of a FeatureValue must have only default FeatureValues." There are a number of cases of models in the Domain Libraries that violate this constraint.

    1. Analysis Domain Library – TradeStudy.sysml, argument in the invocation of tradeStudyObjective (see also SYSML2-491).
    2. Geometry Domain Library
      • SpatialIttems::SpatialItem::componentItems::coordinateFrame::transformation::target is given a default, but is already bound
      • ShapeItems::Circle::radius is bound, but needs to be overridable
    3. Quantities and Units Domain Library
      • Quantities::TensorQuantityValue::order redefines rank and is bound to mRef.order, but rank is already bound for an Array.
      • ISQSpaceTime::CartesianSpatial3dCoordinateFrame::mRef is bound, but needs to be overridable.
      • Several cases in ISQ models of dimensions = 3 even though, for a quantity value, dimensions is already bound to mRef.dimensions.
      • Time::Iso8601DateTimeStructure::mRef is bound to UTC, but it is already bound to UTC for a UTCInstanceValue.
      • VectorCalculations::transform::targetVector::dimensions is bound, but it is already bound for a VectorQuantityValue.
  • Reported: SysML 2.0a1 — Tue, 24 Oct 2023 16:50 GMT
  • Updated: Sun, 10 Dec 2023 22:44 GMT

validateTriggerInvocationExpressionWhenArgument constraint is wrong

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

    The approved resolution to SYSML2-28 included adding the constraint validateTriggerInvocationExpressionWhenArgument, which requires:

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

    However, the argument to a when trigger is not supposed to be an Expression with a Boolean result. Rather, it is an Expression whose result is the Evaluation of an Expression whose result is Boolean. That is, a trigger like when x > 0 is parsed as TriggerWhen({x > 0}), not as TriggerWhen(x > 0). So all properly parsed when triggers will violate validateTriggerInvocationExpressionWhenArgument as specified in the resolution to SYSML2-28.

  • Reported: SysML 2.0b1 — Fri, 27 Oct 2023 09:39 GMT
  • Updated: Sat, 9 Dec 2023 18:33 GMT

binding connector production overly constraining

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

    Currently binding connector graphical production overly constraining the possible permutations to two specific cases. it needs to be generalized to bind usage-nodes in general where they have to be of consistent types.

  • Reported: SysML 2.0a1 — Wed, 4 Oct 2023 15:26 GMT
  • Updated: Fri, 1 Dec 2023 17:56 GMT
  • Attachments:

validateTriggerInvocationExpressionAfterArgument constraint is too strong

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

    The approved resolution to SYSML2-28 includes adding the constraint validateTriggerInvocationExpressionAfterArgument, which requires:

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

    However, in a typical relative time trigger such as, e.g., after 10[SI::s], the result of the expression 10[SI::s] is not a DurationValue. Rather it is a ScalarQuantityValue whose mRef is the DurationUnit SI::s. Therefore, this example time trigger violates validateTriggerInvocationExpressionAfterArgument as specified in the resolution to SYSML2-28.

  • Reported: SysML 2.0b1 — Fri, 27 Oct 2023 09:31 GMT
  • Updated: Thu, 30 Nov 2023 20:46 GMT

KerML constraint requires updates to Systems Library models

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

    The approved resolution to KERML-20 adds the validation constraint validateFeatureValueOverriding that "All Features directly or indirectly redefined by the featureWithValue of a FeatureValue must have only default FeatureValues." This constraint causes problems for two models in the Systems Model Library. These library models do not actually violate the constraint, but using the models as intended my violate the constraint.

    1. In the action definition Actions::AcceptAction, the inout paramater payload is redefined with a feature value binding it to aState.aTransition.aPayload. However, when an accept action is parsed with a change or time trigger, the payload is implicitly bound to the generated change or time signal, and this violates the validateFeatureValueOverriding constraint.
    2. In the analysis case definition AnalysisCases::AnalysisCase:
      • The subject of the objective of AnalysisCase is bound to the result parameter of the AnalysisCase. However, when specifying an analysis case, it is sometimes convenient to compute a check of the case objective by evaluating it on a given subject value. However, the binding of such an subject argument then violates the validateFeatureValueOverring constraint.
      • The result parameter is bound to the result of the AnalysisCase::resultEvaluation calculation feature. However, when defining an analysis case in a user model, it is natural to bind the computation of the result of the case to the result parameter as a feature value. But this then violates the validateFeatureValueOverriding constraint.
  • Reported: SysML 2.0b1 — Tue, 24 Oct 2023 14:00 GMT
  • Updated: Thu, 30 Nov 2023 19:47 GMT

Message and flow connection ends should be occurrence usages

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

    The end features of MessageConnection, FlowConnection and SuccessionFlowConnection in the standard library package Connections are typed as Occurrences, but they are currently syntactically reference usages, not occurrence usages. However, the abstract syntax for EventOccurrenceUsage requires that its referenced eventOccurrence must actually be an OccurrenceUsage. This means that the source and target ends of, e.g., a message, if inherited from MessageConnection and not redefined, cannot be referenced by EventOccurrenceUsages, which prevents an intended use in "sequence diagram" modeling.

  • Reported: SysML 2.0b1 — Sun, 16 Jul 2023 20:35 GMT
  • Updated: Thu, 30 Nov 2023 19:38 GMT

Additional cases when usages are required to be referential

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

    The following statements are made in Clause 7 (Language Description) of the SysML v2 specification:

    • Subclause 7.6.3 (Usages): "Note also that a directed usage is always referential, whether or not the keyword ref is also given explicitly in its declaration."
    • Subclause 7.13.2 (Connection Definitions and Usages): "The end features of a connection definition or usage are always considered referential (non-composite), whether or not their declaration explicitly includes the ref keyword."

    However, there are currently no constraints on the Usage class in the abstract syntax to enforce these rules (see 8.3.6.4).

    In addition, a usage that is not explicitly declared as a feature of a type is, by default, considered to be a feature of the base type Anything. However, since Anything is not a kind of Occurrence, its features cannot be composite. Therefore, such usages should be always referential.

  • Reported: SysML 2.0a1 — Mon, 26 Jun 2023 17:15 GMT
  • Updated: Wed, 29 Nov 2023 21:04 GMT

Validation constraints are missing in the SysML abstract syntax

  • Key: SYSML2-28
  • Status: open  
  • Source: Model Driven Solutions ( Mr. 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 StateUsage.

    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: Wed, 29 Nov 2023 21:01 GMT

The derivation of AssignmentActionUsage::referent is wrong

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

    In the SysML Specification, 8.3.16.5 AssignmentActionUsage, the constraint deriveAssignmentActionUsageReferent states that "The referent of an AssignmentActionUsage is the first Feature that is the memberElement of a ownedMembership that is not an OwningMembership." However, according to the BNF in 8.2.2.16.5 Assignment Action Usages, the intended referent of an assignment is parsed as a FeatureChainMember, and, for an actual chain of more than one Feature, the chaining Feature is owned by the AssignmentActionUsage via OwningMembership. Therefore, it will not be identified as the referent of the assignment according to the current derivation.

  • Reported: SysML 2.0b1 — Sat, 28 Oct 2023 10:57 GMT
  • Updated: Wed, 29 Nov 2023 01:06 GMT

Actions::acceptSubactions and sendSubactions should subset acceptActions and sendActions

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

    In the Systems Model Library, the features Actions::Action::acceptSubactions and Actions::Action::sendSubactions should subset Actions::acceptActions and Actions::sendActions, respectively.

  • Reported: SysML 2.0b1 — Fri, 20 Oct 2023 14:07 GMT
  • Updated: Wed, 29 Nov 2023 01:06 GMT

Constraints missing to enforce variations being abstract