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

Open Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
KERML_-161 Typo in description of namespace KerML 1.0b2 open
SYSML2_-32 Resolve "TODO" in domain library model Time SysML 2.0a1 open
SYSML2_-248 Evaluation problem with TradeStudyObjectives SysML 2.0b2 open
SYSML2_-503 Graphical notation for filter conditions not defined SysML 2.0b2 open
SYSML2_-235 Table 16 Graphical Notation does not match Textual Notation SysML 2.0b1 open
SYSML2_-111 Mapping of ObjectFlows with ForkNodes SysML 2.0b1 open
SYSML2_-131 ChangeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2_-234 Table 16 has misspelling issue SysML 2.0b1 open
SYSML2_-94 "Universal" package-level features can have many values. SysML 2.0a1 open
SYSML2_-135 element-node not defined SysML 2.0a1 open
SYSML2_-134 Missing production for n-ary connection definition graphical SysML 2.0a1 open
SYSML2_-471 Unredefinable shape attributes SysML 2.0b2 open
SYSML2_-256 Inconsistent and/or incomplete graphical notation for standard reference-subsetted usages SysML 2.0b2 open
SYSML2_-477 Explanation for extended-usage and extended-def concepts SysML 2.0b2 open
SYSML2_-498 The approved Issue KERML_-18 requires the transformation specification to be adjusted SysML 2.0b2 open
SYSML2_-490 Signal_Mapping maps to ItemDefinition but description says AttributeDefinition SysML 2.0b2 open
SYSML2_-496 Resolution SYSML2_-424 uses invalid operation call of base mapping class SysML 2.0b2 open
SYSML2_-494 not possible to include action (effect) on a decision branch transition SysML 2.0b2 open
SYSML2_-487 Action node is missing on stateflow SysML 2.0b2 open
SYSML2_-483 Incorrect VerificationMethodKind values in Table 21 SysML 2.0b2 open
SYSML2_-492 Wrong guard expression in Graphical BNF SysML 2.0b2 open
SYSML2_-4 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 open
KERML_-142 two haves SysML 2.0b1 open
KERML_-143 ownedParameterMember should be ownedMemberParameter SysML 2.0b2 open
KERML_-101 Global scope notation SysML 2.0b2 open
SYSML2_-502 Lack of documentation of purpose and semantics of single-line and multiline notes SysML 2.0b2 open
SYSML2_-499 subsets of scalarQuantities should be nonunique SysML 2.0b2 open
SYSML2_-424 Adopted resolution SYSML2_-403 has impact on the v1 to v2 Transformation SysML 2.0b2 open
SYSML2_-370 Mapping class description AEAChangeParameterFeatureMembership_Mapping is missing SysML 2.0b2 open
SYSML2_-108 Various constraints need to take feature chaining into account SysML 2.0b1 open
SYSML2_-39 Semantics of transfers across interfaces SysML 2.0a1 open
SYSML2_-362 Alignment of selected graphical symbols in states and actions. SysML 2.0b2 open
SYSML2_-351 Incorrect graphical notation for parameters with nested items in example "Flow as Node" SysML 2.0b2 open
SYSML2_-304 Diagram frame production not properly integrated into graphical BNF SysML 2.0b2 open
SYSML2_-294 Send action examples in representative notation tables wrong SysML 2.0b2 open
SYSML2_-173 Flow connections are incorrectly both structure and behavior SysML 2.0b1 open
SYSML2_-89 Accepters on transition usages from entry actions SysML 2.0a1 open
SYSML2_-378 Entry, do and exit actions compartment should be named "state actions" SysML 2.0b2 open
SYSML2_-366 No else branch for a decision node SysML 2.0b2 open
SYSML2_-354 Not possible to show inherited symbol in name compartment SysML 2.0b2 open
SYSML2_-159 Textual notation for send actions is too limited SysML 2.0b1 open
SYSML2_-15 Graphical BNF production proxy should be contextualized SysML 2.0a1 open
SYSML2_-268 Incorrect declaration of parameters on actions SysML 2.0b2 open
SYSML2_-224 State machine graphical notation for entry/exit/do actions inconsistent SysML 2.0b2 open
SYSML2_-260 Accept action in representative notation tables is confusing and needs cleanup SysML 2.0b2 open
SYSML2_-426 VerificationKind should be VerificationMethodKind SysML 2.0b2 open
SYSML2_-416 Cross features for connection definitions and connection usages SysML 2.0b2 open
SYSML2_-265 Missing semantic constraints related to features of Part SysML 2.0b2 open
SYSML2_-486 ShapeItems can't be SpatialItems KerML 1.0b2 open
SYSML2_-465 Ref Port Displayed with Dashed Lines SysML 2.0b2 open
SYSML2_-158 timeslice/snapshot featuring types required to specialize or be same as types SysML 2.0a1 open
SYSML2_-150 OccurrenceUsage missing portioningFeature SysML 2.0b1 open
SYSML2_-149 Control nodes missing from textual notation for states SysML 2.0a1 open
SYSML2_-148 Graphical notation unclear about user-defined keywords for library extensions SysML 2.0a1 open
SYSML2_-147 Graphical notation unclear on optionality of keywords on edges SysML 2.0a1 open
SYSML2_-146 Clarify bolding of keywords in concrete graphical syntax SysML 2.0a1 open
SYSML2_-145 Incorrect definition elements in interconnection-element SysML 2.0b1 open
SYSML2_-143 Missalignment between interface graphical production and notation table SysML 2.0a1 open
SYSML2_-107 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2_-133 Fork/JoinNode succession "other" end multiplicity validations missing SysML 2.0b1 open
SYSML2_-130 ConstraintProperty should be mapped to a AssertConstraintUsage SysML 2.0b1 open
SYSML2_-126 Decision/MergeNode SuccessionSpecialization checks missing some constraints SysML 2.0b1 open
SYSML2_-120 Package import wildcard is missing SysML 2.0b1 open
SYSML2_-119 Wrong imported package notation SysML 2.0b1 open
SYSML2_-117 Nesting parameter symbol is missing optional nested parameter SysML 2.0b1 open
SYSML2_-116 Binding between action parameters and directed features on ports missing SysML 2.0b1 open
SYSML2_-115 Metadata declaration needs clarification SysML 2.0b1 open
SYSML2_-33 Extend ISQ with missing quantity and unit types for US Customary Units SysML 2.0a1 open
SYSML2_-28 Graphical BNF defines lifeline elements incorrectly SysML 2.0a1 open
SYSML2_-24 Port symbol notation (arrows) needs improvement SysML 2.0a1 open
SYSML2_-21 Parameter symbol notation needs improvement SysML 2.0a1 open
SYSML2_-16 Consider production for standard case view vs filtered general view SysML 2.0a1 open
SYSML2_-12 Regularization of textual notation for loops SysML 2.0a1 open
SYSML2_-10 Missing graphical notation allocating flow to connection SysML 2.0a1 open
SYSML2_-110 Transformation does not cover the mapping of Unit and QuantityKind SysML 2.0b1 open
SYSML2_-97 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2_-96 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2_-66 Transformation does not cover UML4SysML::ActivityPartition SysML 2.0a1 open
SYSML2_-43 Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete SysML 2.0a1 open
SYSML2_-411 Accept after guard causes errors in IDE SysML 2.0b2 open
SYSML2_-246 Ordering of guards and accepts in transitions is inconsistent SysML 2.0b2 open
SYSML2_-302 Chapter Trigger_Mapping is empty SysML 2.0b2 open
SYSML2_-382 Subclause 7.7.5.3.7 Trigger_Mapping is empty SysML 2.0b2 open
SYSML2_-263 There is no checkSatisfyRequirementUsageSpecialization constraint SysML 2.0b2 open
SYSML2_-239 Missing Element Import Alias SysML 2.0b2 open
SYSML2_-226 Description and examples for message notation are wrong SysML 2.0b2 open
SYSML2_-132 TimeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2_-129 TransitionUsage requires binding to succession with mandatory end multiplicities SysML 2.0b1 open
SYSML2_-100 Transformation does not cover UML4SysML::SignalEvent SysML 2.0a1 open
SYSML2_-76 Transformation does not cover SysMLv1::FlowProperty SysML 2.0a1 open
SYSML2_-40 Port transfer semantics SysML 2.0a1 open
SYSML2_-417 Remove "Connection" from the names "FlowConnectionDefinition", "FlowConnectionUsage", and "SuccessionFlowConnectionUsage" SysML 2.0b2 open
SYSML2_-447 Specification of Satisfy Requirement is Unclear SysML 2.0b2 open
SYSML2_-349 Inconsistent compartment labels SysML 2.0b2 open
SYSML2_-286 Misspelling in Table 16 / graphical and textual notation do not match SysML 2.0b2 open
SYSML2_-233 Table 6 Duplicate Row Titles SysML 2.0b1 open
SYSML2_-320 Specification lacks precision in multiple sentences that begin with the word 'however' SysML 2.0b2 open
SYSML2_-414 flow-label definition cut short SysML 2.0b2 open
SYSML2_-412 Apparent use of an overly-generic notation entry in subsetting or redefinition notation specification for Connection end SysML 2.0b2 open
SYSML2_-409 Notation should be more formally tied with Abstract Syntax SysML 2.0b2 open
SYSML2_-444 No Inheritance Symbol for Parameters, Ports, Connectors, Transitions SysML 2.0b2 open
SYSML2_-445 Metadata Compartment is not Specified SysML 2.0b2 open
SYSML2_-446 Short Usage Name is not Specified (e.g. Perform action and Perform) SysML 2.0b2 open
SYSML2_-448 Issues with the 'Swimlane' Element Specification SysML 2.0b2 open
SYSML2_-449 Additional Properties are missing for few Usages SysML 2.0b2 open
SYSML2_-450 Compartment Name for Action in States is not Correct SysML 2.0b2 open
SYSML2_-451 Abstract Usage Name is not in Italic SysML 2.0b2 open
SYSML2_-452 Port/Parameter Labels Inside Context SysML 2.0b2 open
SYSML2_-453 View Node is not Specified as a 'subject-actors-stakeholders-node' SysML 2.0b2 open
SYSML2_-454 Documentation in Objective Compartment SysML 2.0b2 open
SYSML2_-455 Keyword Display in Constraints Compartment SysML 2.0b2 open
SYSML2_-456 Return Keyword in Parameters Compartment SysML 2.0b2 open
SYSML2_-457 Nested Shapes are Displayed for Interfaces SysML 2.0b2 open
SYSML2_-458 Dotted line for elaborated connectors SysML 2.0b2 open
SYSML2_-459 Documentation compartment name SysML 2.0b2 open
SYSML2_-460 Compartments are not specified in BNF SysML 2.0b2 open
SYSML2_-461 No Names specified for Control Nodes SysML 2.0b2 open
SYSML2_-462 Symbol Keyword is not Displayed in Shapes SysML 2.0b2 open
SYSML2_-463 Arrows for Parameters Not Displayed SysML 2.0b2 open
SYSML2_-464 Library package keyword not displayed SysML 2.0b2 open
SYSML2_-466 Missing Abstract Keyword SysML 2.0b2 open
SYSML2_-467 No Compartments for Send and Accepts Actions SysML 2.0b2 open
SYSML2_-468 Cosmetic Changes to Table Examples SysML 2.0b2 open
SYSML2_-469 Package With Visibility Indicator SysML 2.0b2 open
SYSML2_-470 Owned Member Display in Package SysML 2.0b2 open
SYSML2_-365 Flow Connection End modeling - Different models created for definition through sytactic sugar vs fully expanded definition SysML 2.0b2 open
SYSML2_-363 Flow Connection Payload modeling - Different models created for definition through sytactic sugar vs fully expanded definition SysML 2.0b2 open
SYSML2_-90 Subject of an include use case usage SysML 2.0a1 open
SYSML2_-422 Properties typed by a Signal are not mapped SysML 2.0b2 open
SYSML2_-407 Language description of messages is incorrect SysML 2.0b2 open
SYSML2_-405 Messages cannot have explicit flow connection definitions SysML 2.0b2 open
SYSML2_-394 deriveItemUsageItemDefinition is incorrect SysML 2.0b2 open
SYSML2_-392 TestCaseVerifyObjectiveRequirementUsage_Mapping has no general mapping SysML 2.0b2 open
SYSML2_-389 Incorrect graphical BNF production item-name-compartment SysML 2.0b2 open
SYSML2_-385 The operation RICOAOutputPin_Mapping::filter() should redefine Pin_Mapping::filter() SysML 2.0b2 open
SYSML2_-379 Incorrect graphical notation of nested items in item parameter SysML 2.0b2 open
SYSML2_-376 Specification of Helper::getScalarValueType() uses unknown OCL function SysML 2.0b2 open
SYSML2_-374 COAPin_Mapping is not correctly specified SysML 2.0b2 open
SYSML2_-372 ValuePin_Mapping is not correctly specified SysML 2.0b2 open
SYSML2_-368 Graphical notation examples violate GBNF and contain typo SysML 2.0b2 open
SYSML2_-367 Mistakes in various occurrence examples SysML 2.0b2 open
SYSML2_-323 There is no production for general-view SysML 2.0b2 open
SYSML2_-27 Missing graphical notation for Flows Compartment SysML 2.0a1 open
SYSML2_-14 Graphical BNF production sq-ev-occurrence has inconsistent proxy notation SysML 2.0a1 open
SYSML2_-359 SysMLv2 Metadata Annotation Capabilities do Not Hide enough Implementation Details in Textual Representation SysML 2.0b2 open
SYSML2_-311 Fix errors in resolution of issue SYSML2_-203 (InitialState mapping) SysML 2.0b2 open
SYSML2_-415 All redefinitions of mapping features should be visible in the generated document SysML 2.0b2 open
SYSML2_-410 Definitions of View Usage are Too Restricted SysML 2.0b2 open
SYSML2_-30 Graphical notation for variant inheritance from variation requires improvement SysML 2.0a1 open
SYSML2_-245 Multiple vs Single Trigger/Guard/Effect for State Transitions Contradiction SysML 2.0b2 open
SYSML2_-44 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 open
SYSML2_-360 Each FlowConnectionUsage owned by PartUsage subsets 3 features SysML 2.0b2 open
SYSML2_-401 proxy connection points are not contextualized in sequence diagrams SysML 2.0b2 open
SYSML2_-364 Syntactic Sugar Notation to Define Payload for Flow Def SysML 2.0b2 open
SYSML2_-369 Library description of Duration of is truncated SysML 2.0b2 open
SYSML2_-280 Header description of unowned elements does not align with textual notation SysML 2.0b2 open
SYSML2_-398 Stakeholder_Mapping should map from Classifier to PartDefinition SysML 2.0b2 open
SYSML2_-283 Table 5 Attributes Compartment Graphical Notation and Textual Notation does not match SysML 2.0b2 open
SYSML2_-282 P8 import textual notation may have errors SysML 2.0b2 open
SYSML2_-222 TransitionUsage source and target properties do not support feature chains SysML 2.0b2 open
SYSML2_-285 Multiple textual notation issues SysML 2.0b2 open
SYSML2_-352 Error in specification of library model UUIDs SysML 2.0b2 open
SYSML2_-346 Chapter 7.8.7.3.4 is empty SysML 2.0b2 open
SYSML2_-345 Chapter 7.8.7.3.3 FeatureDirectionKind is empty SysML 2.0b2 open
SYSML2_-330 Typo - "calculation" instead of "constraint" SysML 2.0b2 open
SYSML2_-314 Actor should be mapped to a PartDefinition SysML 2.0b2 open
SYSML2_-305 SysMLv1Tov2.xmi contains temporary mapping classes SysML 2.0b2 open
SYSML2_-300 Weak check of input parameter in Helper::getScalarValueType SysML 2.0b2 open
SYSML2_-291 Typo in definition of RenderingDefinition SysML 2.0b2 open
SYSML2_-288 Missing word in description of view usage SysML 2.0b2 open
SYSML2_-281 Error in textual notation on this page ("comment Comment 2") SysML 2.0b2 open
SYSML2_-279 Presuming missing word in sentence describing implicit annotation. SysML 2.0b2 open
SYSML2_-267 Invalid use of "loop" as merge action name SysML 2.0b2 open
SYSML2_-220 Replace Generic mapping classes by Initializers SysML 2.0b2 open
SYSML2_-206 Editorial errors in constraints SysML 2.0b2 open
SYSML2_-171 Helper::getScalarValueType operation is not robust enough SysML 2.0a1 open
SYSML2_-361 Support SysML stereotypes applied to specialized metaclasses SysML 2.0b2 open
SYSML2_-357 Incosistency between notation tables and BNF related to package nodes SysML 2.0b2 open
SYSML2_-356 Graphical Notation does not specify else-condition for decision nodes SysML 2.0b2 open
SYSML2_-259 Operation should not be mapped to perform action SysML 2.0b2 open
SYSML2_-350 Incorrect GBNF production relationship-name SysML 2.0b2 open
SYSML2_-278 Row headers not descriptive enough SysML 2.0b2 open
SYSML2_-284 Differentiate Row Headers that say "Interface" SysML 2.0b2 open
SYSML2_-287 Why does View Definition specialise Part Definition? SysML 2.0b2 open
SYSML2_-289 Filter condition or view condition? SysML 2.0b2 open
SYSML2_-290 Is view the same as view usage? SysML 2.0b2 open
SYSML2_-292 Examples of Nested View Usages SysML 2.0b2 open
SYSML2_-293 Definition of view artifact SysML 2.0b2 open
SYSML2_-297 Proxy connection points should be applicable more broadly then currently supported by the GBNF SysML 2.0b2 open
SYSML2_-326 Use Cases should have stakeholderParameters SysML 2.0b2 open
SYSML2_-155 Comment_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-329 Mapping overview tables are wrong SysML 2.0b2 open
SYSML2_-180 Reuse of KerML textual notation productions in the SysML grammar SysML 2.0b1 open
SYSML2_-327 Transformation does not cover the deprecated elements FlowSpecification SysML 2.0b2 open
SYSML2_-325 Transformation does not cover the deprecated elements FlowPort SysML 2.0b2 open
SYSML2_-324 Representative notation example for allocation confusing/wrong? SysML 2.0b2 open
SYSML2_-136 Transformation of UML4SysML::State does not consider entry, do, and exit behavior SysML 2.0b1 open
SYSML2_-197 Inconsistent use of guillemets in graphical notation for metamodel aspects SysML 2.0b2 open
SYSML2_-321 state-flow GBNF issues SysML 2.0b2 open
SYSML2_-227 Name expressions in GBNF are too constraining SysML 2.0b2 open
SYSML2_-25 Source and target on binary ConnectionDefinition symbol missing SysML 2.0a1 open
SYSML2_-165 Semantic constraints missing for shorthand succession notation SysML 2.0b1 open
SYSML2_-200 Structured actions not properly covered by GBNF and notation tables SysML 2.0b2 open
SYSML2_-113 Mapping of ObjectFlows with DecisionNodes SysML 2.0b1 open
SYSML2_-41 Semantics of a conditional succession using "else" are missing SysML 2.0a1 open
SYSML2_-274 Map UML4SysML::Constraint to ConstraintUsage only SysML 2.0b2 open
SYSML2_-318 Transformation does not cover UML4SysML::ProfileApplication SysML 2.0b2 open
SYSML2_-317 Transformation does not cover SysMLv1::ConnectorProperty SysML 2.0b2 open
SYSML2_-310 ObjectFlow with guards outgoing from DecisionNodes are not mapped correctly SysML 2.0b2 open
SYSML2_-309 CallBehaviorAction mapping does not consider the pins SysML 2.0b2 open
SYSML2_-308 Mapping of ObjectFlow should not consider the type of the objects that flow SysML 2.0b2 open
SYSML2_-307 ActivityParameterNodes should be mapped SysML 2.0b2 open
SYSML2_-303 ConnectionPointReference_Mapping should create a Redefinition SysML 2.0b2 open
SYSML2_-272 Typos in graphical metadata representative notation SysML 2.0b2 open
SYSML2_-249 RICOAOutputPin_Mapping should specialized Pin_Mapping SysML 2.0b2 open
SYSML2_-230 Inconsistent graphical notation for view frame SysML 2.0b2 open
SYSML2_-214 Mapping of State does not consider orthogonal states SysML 2.0b2 open
SYSML2_-203 InitialState is mapped to StateUsage, but should be an empty ActionUsage SysML 2.0b2 open
SYSML2_-199 InterfaceBlock mapped to PortDefinition, but ConjugatedPortDefinition is not generated SysML 2.0b2 open
SYSML2_-112 Mapping of ObjectFlows with JoinNodes SysML 2.0b1 open
SYSML2_-23 Missing graphical notation for n-ary connection def and usage SysML 2.0a1 open
SYSML2_-301 Mapping for UML4SysML::CallEvent and UML4SysML::AcceptCallAction are missing SysML 2.0b2 open
SYSML2_-296 Need to add terminate action node to action flow and state flow views SysML 2.0b2 open
SYSML2_-295 send and accept actions name compartment productions inconsistent SysML 2.0b2 open
SYSML2_-277 Mapping of UseCase does not consider more than one subject SysML 2.0b2 open
SYSML2_-276 Property typed by an Actor should be mapped to a PartUsage SysML 2.0b2 open
SYSML2_-275 Mapping of UML4SysML::Constraint: Bind the result parameter SysML 2.0b2 open
SYSML2_-262 Flows cannot connect ControlNodes SysML 2.0b2 open
SYSML2_-261 Graphical notation action names need to be aligned SysML 2.0b2 open
SYSML2_-207 Update language description and concrete syntax related to imports SysML 2.0b2 open
SYSML2_-187 There is no need for AnalysisAction SysML 2.0b2 open
SYSML2_-271 Mappings from the "Common" package SysML 2.0b2 open
SYSML2_-270 Type of the ReferenceUsage created for the client of a Satisfy relationship SysML 2.0b2 open
SYSML2_-269 ReferenceUsage creation in case of a Satisfy relationship transformation SysML 2.0b2 open
SYSML2_-29 Graphical BNF mapping to abstract syntax is missing SysML 2.0a1 open
SYSML2_-266 ObjectFlow mappings limited to non-streaming parameters SysML 2.0b2 open
SYSML2_-264 Interface usage cannot redefine inherited attributes in textual syntax SysML 2.0b2 open
SYSML2_-254 No way to expose non-membership and non-namespace elements SysML 2.0b2 open
SYSML2_-255 Name misplaced on action symbol parameter SysML 2.0b2 open
SYSML2_-221 Default multiplicities are not formally specified SysML 2.0b2 open
SYSML2_-253 Mapping of ClearStructuralFeatureAction is not defined yet SysML 2.0b2 open
SYSML2_-252 Mapping of RemoveStructuralFeatureValueAction is not defined yet SysML 2.0b2 open
SYSML2_-251 AddStructuralFeatureValueAction Mapping does not consider the names of the input and output pins SysML 2.0b2 open
SYSML2_-247 Graphical BNF for n-ary ConnectionDefinition is missing SysML 2.0b2 open
SYSML2_-11 Missing explicit explanation of compartments as views SysML 2.0a1 open
SYSML2_-184 StateAction::substates has an implied subsetting of exclusiveStates SysML 2.0b2 open
SYSML2_-236 Missing Complete concept SysML 2.0b2 open
SYSML2_-237 Missing Final concept SysML 2.0b2 open
SYSML2_-238 Missing isLeaf concept SysML 2.0b2 open
SYSML2_-240 ShapeItems have radius feature bound SysML 2.0b2 open
SYSML2_-229 Invalid values can be assigned to an enum SysML 2.0b2 open
SYSML2_-212 Inconsistencies in the graphical notation for "expose" SysML 2.0b2 open
SYSML2_-209 isOrdered and isUnique are missing from the reflective abstract mapping SysML 2.0b2 open
SYSML2_-202 Missing guidance on highlighting keywords SysML 2.0b2 open
SYSML2_-191 Error in the specification of "connections" SysML 2.0b2 open
SYSML2_-189 Incorrect enumeration example SysML 2.0b2 open
SYSML2_-183 checkStateUsageExclusiveStateSpecialization and checkStateUsageSubstateSpecialization have problems SysML 2.0b2 open
SYSML2_-177 Guillemets should not be used on keywords in textual notation snippets used in the graphical notation SysML 2.0a1 open
SYSML2_-144 Missing production for use case actors and subject SysML 2.0a1 open
SYSML2_-142 GBNF for flow connection not mapped to semantics SysML 2.0a1 open
SYSML2_-114 Symbol for metadata def is missing SysML 2.0b1 open
SYSML2_-18 No support for metadata definition in graphical notation SysML 2.0a1 open
SYSML2_-3 incorrect naming of * character SysML 2.0b1 open
SYSML2_-2 incorrect naming of * character SysML 2.0b1 open
SYSML2_-1 Issues with SysML/KerML grammar SysML 2.0b1 open
SYSML2-480 Missing production for use case actors and subject SysML 2.0a1 open
SYSML2-557 Need to complete and align flow and message notations in GBNF SysML 2.0a1 open
SYSML2_-201 Confusing send/accept examples in notation tables SysML 2.0b2 open
SYSML2-629 Guillemets are not used on keywords in textual notation snippets used in the graphical notation SysML 2.0a1 open
SYSML2-686 Reuse of KerML textual notation productions in the SysML grammar SysML 2.0b1 open
SYSML2-632 Long-form notation for bindings and successions SysML 2.0b1 open
SYSML2-639 Change graphical notation for use cases to elliptic elements SysML 2.0b1 open
SYSML2_-178 Long-form notation for bindings and successions SysML 2.0b1 open
SYSML2_-179 Change graphical notation for use cases to elliptic elements SysML 2.0b1 open
SYSML2-593 Enumerations not specializable SysML 2.0b1 open
SYSML2-591 Transformation fails on Enumerations that are ValueTypes SysML 2.0a1 open
SYSML2-594 PortUsage direction SysML 2.0b1 open
SYSML2-601 Proxy nodes are missing from states SysML 2.0a1 open
SYSML2-592 Flow connections are incorrectly both structure and behavior SysML 2.0b1 open
SYSML2_-175 PortUsage direction SysML 2.0b1 open
SYSML2_-176 Proxy nodes are missing from states SysML 2.0a1 open
SYSML2_-174 Enumerations not specializable SysML 2.0b1 open
SYSML2_-172 Transformation fails on Enumerations that are ValueTypes SysML 2.0a1 open
SYSML2-588 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable SysML 2.0a1 open
SYSML2-589 SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong SysML 2.0a1 open
SYSML2-586 Literal factories are missing operation for their value SysML 2.0a1 open
SYSML2-590 Helper::getScalarValueType operation is not robust enough SysML 2.0a1 open
SYSML2_-169 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable SysML 2.0a1 open
SYSML2_-170 SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong SysML 2.0a1 open
SYSML2_-168 Literal factories are missing operation for their value SysML 2.0a1 open
SYSML2-546 Add a distinguished attribute to capture the textual body of a requirement SysML 2.0b1 open
SYSML2-584 Default multiplicities are not managed correctly SysML 2.0a1 open
SYSML2-576 Semantic constraints missing for shorthand succession notation SysML 2.0b1 open
SYSML2-535 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong SysML 2.0a1 open
SYSML2-585 Factories specified for Literal specification shall be optimized SysML 2.0a1 open
SYSML2_-163 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong SysML 2.0a1 open
SYSML2_-166 Default multiplicities are not managed correctly SysML 2.0a1 open
SYSML2_-164 Add a distinguished attribute to capture the textual body of a requirement SysML 2.0b1 open
SYSML2_-167 Factories specified for Literal specification shall be optimized SysML 2.0a1 open
SYSML2-532 OpaqueBehavior shall be transformed even if they are not owned by a Package SysML 2.0a1 open
SYSML2-526 Textual notation for send actions is too limited SysML 2.0b1 open
SYSML2-533 Properties typed by Actors SysML 2.0a1 open
SYSML2-524 timeslice/snapshot featuring types required to specialize or be same as types SysML 2.0a1 open
SYSML2-534 Most SysML::Blocks are owned by a package SysML 2.0a1 open
SYSML2_-162 Most SysML::Blocks are owned by a package SysML 2.0a1 open
SYSML2_-161 Properties typed by Actors SysML 2.0a1 open
SYSML2_-160 OpaqueBehavior shall be transformed even if they are not owned by a Package SysML 2.0a1 open
SYSML2-506 GenericToStateUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-507 GenericToElement_Mapping is missing default rules SysML 2.0a1 open
SYSML2-516 Namespace_Mapping shall redefine ownedRelationship() SysML 2.0a1 open
SYSML2-508 Comment_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-515 Relationship_Mapping::ownedRelatedElement() is wrong SysML 2.0a1 open
SYSML2_-154 GenericToElement_Mapping is missing default rules SysML 2.0a1 open
SYSML2_-156 Relationship_Mapping::ownedRelatedElement() is wrong SysML 2.0a1 open
SYSML2_-153 GenericToStateUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-157 Namespace_Mapping shall redefine ownedRelationship() SysML 2.0a1 open
SYSML2-504 GenericToRelationship_Mapping is missing default rules SysML 2.0a1 open
SYSML2-486 Graphical notation unclear on optionality of keywords on edges SysML 2.0a1 open
SYSML2-487 Graphical notation unclear about user-defined keywords for library extensions SysML 2.0a1 open
SYSML2-503 OccurrenceUsage missing portioningFeature SysML 2.0b1 open
SYSML2-502 Control nodes missing from concrete syntax for states SysML 2.0a1 open
SYSML2-505 GenericToRequirementUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-151 GenericToRelationship_Mapping is missing default rules SysML 2.0a1 open
SYSML2_-152 GenericToRequirementUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-485 Clarify bolding of keywords in concrete graphical syntax SysML 2.0a1 open
SYSML2-483 Incorrect definition elements in interconnection-element SysML 2.0b1 open
SYSML2-479 Missalignment between interface graphical production and notation table SysML 2.0a1 open
SYSML2-482 Missing production for use case actors and subject SysML 2.0a1 open
SYSML2-476 Initializer classes have to be rationalized SysML 2.0b1 open
SYSML2-477 AssociationClass_Mapping is uncomplete SysML 2.0b1 open
SYSML2-475 missing graphical bnf for events and event occurrences SysML 2.0a1 open
SYSML2-478 GBNF for flow connection not mapped to semantics SysML 2.0a1 open
SYSML2_-139 missing graphical bnf for events and event occurrences SysML 2.0a1 open
SYSML2_-140 Initializer classes have to be rationalized SysML 2.0b1 open
SYSML2_-141 AssociationClass_Mapping is uncomplete SysML 2.0b1 open
SYSML2-472 Optional language for documentation SysML 2.0b1 open
SYSML2-463 Transformation of UML4SysML::State does not consider entry, do, and exit behavior SysML 2.0b1 open
SYSML2-462 element-node not defined SysML 2.0a1 open
SYSML2-473 ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless SysML 2.0b1 open
SYSML2_-138 ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless SysML 2.0b1 open
SYSML2_-137 Optional language for documentation SysML 2.0b1 open
SYSML2-445 ConstraintProperty should be mapped to a AssertConstraintUsage SysML 2.0b1 open
SYSML2-397 TransitionUsage requires binding to succession with mandatory end multiplicities SysML 2.0b1 open
SYSML2-456 Missing production for n-ary connection definition graphical SysML 2.0a1 open
SYSML2-448 ChangeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2-449 TimeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2-450 Fork/JoinNode succession "other" end multiplicity validations missing SysML 2.0b1 open
SYSML2-385 CommentAnnotation_Mapping shall be a "unique" mapping SysML 2.0a1 open
SYSML2-353 Feature modifiers missing in Portion Membership examples SysML 2.0b1 open
SYSML2-357 Representative example "Package with members" to be improved SysML 2.0b1 open
SYSML2-390 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2-383 Decision/MergeNode SuccessionSpecialization checks missing some constraints SysML 2.0b1 open
SYSML2_-124 Feature modifiers missing in Portion Membership examples SysML 2.0b1 open
SYSML2_-128 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2_-125 Representative example "Package with members" to be improved SysML 2.0b1 open
SYSML2_-127 CommentAnnotation_Mapping shall be a "unique" mapping SysML 2.0a1 open
SYSML2-352 Feature modefiers missing in Feature Membership examples SysML 2.0b1 open
SYSML2-326 Wrong imported package notation SysML 2.0b1 open
SYSML2-329 Representative notation for filtered package import missing SysML 2.0b1 open
SYSML2-337 Incomplete example "Individual Occurrence" SysML 2.0b1 open
SYSML2-327 Package import wildcard is missing SysML 2.0b1 open
SYSML2_-121 Representative notation for filtered package import missing SysML 2.0b1 open
SYSML2_-123 Feature modefiers missing in Feature Membership examples SysML 2.0b1 open
SYSML2_-122 Incomplete example "Individual Occurrence" 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-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_-118 Missing representative notation for causation and requirements derivation SysML 2.0b1 open
SYSML2-313 Mapping of ObjectFlows with ForkNodes 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-316 Symbol for metadata def is missing SysML 2.0b1 open
SYSML2-311 Transformation does not cover the mapping of Unit and QuantityKind SysML 2.0b1 open
SYSML2-297 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2-286 the getMapped operation cannot be called on ElementOwnership_Mapping SysML 2.0a1 open
SYSML2-307 Various constraints need to take feature chaining into account SysML 2.0b1 open
SYSML2-309 Transformation does not cover mapping of Parameter::isStreaming=true SysML 2.0b1 open
SYSML2_-106 the getMapped operation cannot be called on ElementOwnership_Mapping SysML 2.0a1 open
SYSML2_-109 Transformation does not cover mapping of Parameter::isStreaming=true SysML 2.0b1 open
SYSML2-272 Transformation does not cover UML4SysML::ReadLinkAction SysML 2.0a1 open
SYSML2-274 Transformation does not cover UML4SysML::DestroyLinkAction SysML 2.0a1 open
SYSML2-283 Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet SysML 2.0a1 open
SYSML2-284 Transformation does not cover UML4SysML::FunctionBehavior SysML 2.0a1 open
SYSML2-273 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 open
SYSML2_-105 Transformation does not cover UML4SysML::FunctionBehavior SysML 2.0a1 open
SYSML2_-101 Transformation does not cover UML4SysML::ReadLinkAction SysML 2.0a1 open
SYSML2_-102 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 open
SYSML2_-104 Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet SysML 2.0a1 open
SYSML2_-103 Transformation does not cover UML4SysML::DestroyLinkAction SysML 2.0a1 open
SYSML2-271 Transformation does not cover UML4SysML::SignalEvent SysML 2.0a1 open
SYSML2-187 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2-225 Some Standard View Definitions should be filtered specializations of General View SysML 2.0a1 open
SYSML2-188 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2-199 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2_-98 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2_-99 Some Standard View Definitions should be filtered specializations of General View SysML 2.0a1 open
SYSML2-183 Some package-level features are mandatory SysML 2.0a1 open
SYSML2-186 ConstraintBlock mapping parameters to input attributes SysML 2.0a1 open
SYSML2-160 Machine readable project interchange file(s) for language description examples SysML 2.0a1 open
SYSML2-161 XMI and JSON for example model SysML 2.0a1 open
SYSML2-177 Assignment action usages do not specify when their expressions are evaluated SysML 2.0a1 open
SYSML2_-93 Assignment action usages do not specify when their expressions are evaluated SysML 2.0a1 open
SYSML2_-95 ConstraintBlock mapping parameters to input attributes SysML 2.0a1 open
SYSML2_-92 XMI and JSON for example model SysML 2.0a1 open
SYSML2_-91 Machine readable project interchange file(s) for language description examples SysML 2.0a1 open
SYSML2-151 Transformation does not cover SysMLv1::NoBuffer SysML 2.0a1 open
SYSML2-152 Accepters on transition usages from entry actions SysML 2.0a1 open
SYSML2-154 Subject of an include use case usage SysML 2.0a1 open
SYSML2-150 Transformation does not cover SysMLv1::Overwrite SysML 2.0a1 open
SYSML2_-87 Transformation does not cover SysMLv1::Overwrite SysML 2.0a1 open
SYSML2_-88 Transformation does not cover SysMLv1::NoBuffer SysML 2.0a1 open
SYSML2-145 Transformation does not cover SysMLv1::BoundReference SysML 2.0a1 open
SYSML2-147 Transformation does not cover SysMLv1::EndPathMultiplicity SysML 2.0a1 open
SYSML2-146 Transformation does not cover SysMLv1::ParticipantProperty SysML 2.0a1 open
SYSML2-148 Transformation does not cover SysMLv1::PropertySpecificType SysML 2.0a1 open
SYSML2-149 Transformation does not cover SysMLv1::AllocateActivitiyPartition SysML 2.0a1 open
SYSML2_-85 Transformation does not cover SysMLv1::PropertySpecificType SysML 2.0a1 open
SYSML2_-84 Transformation does not cover SysMLv1::EndPathMultiplicity SysML 2.0a1 open
SYSML2_-86 Transformation does not cover SysMLv1::AllocateActivitiyPartition SysML 2.0a1 open
SYSML2_-83 Transformation does not cover SysMLv1::ParticipantProperty SysML 2.0a1 open
SYSML2_-82 Transformation does not cover SysMLv1::BoundReference SysML 2.0a1 open
SYSML2-140 Transformation does not cover SysMLv1::InvocationOnNestedPortAction SysML 2.0a1 open
SYSML2-142 Transformation does not cover SysMLv1::Conform SysML 2.0a1 open
SYSML2-144 Transformation does not cover SysMLv1::DistributedProperty SysML 2.0a1 open
SYSML2-143 Transformation does not cover SysMLv1::Expose SysML 2.0a1 open
SYSML2-141 Transformation does not cover SysMLv1::View SysML 2.0a1 open
SYSML2_-81 Transformation does not cover SysMLv1::DistributedProperty SysML 2.0a1 open
SYSML2_-77 Transformation does not cover SysMLv1::InvocationOnNestedPortAction SysML 2.0a1 open
SYSML2_-79 Transformation does not cover SysMLv1::Conform SysML 2.0a1 open
SYSML2_-78 Transformation does not cover SysMLv1::View SysML 2.0a1 open
SYSML2_-80 Transformation does not cover SysMLv1::Expose SysML 2.0a1 open
SYSML2-135 Transformation does not cover SysMLv1::TriggerOnNestedPort SysML 2.0a1 open
SYSML2-134 Transformation does not cover UML4SysML::UnmarshallAction SysML 2.0a1 open
SYSML2-136 Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent SysML 2.0a1 open
SYSML2-137 Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction SysML 2.0a1 open
SYSML2-138 Transformation does not cover SysMLv1::FlowProperty SysML 2.0a1 open
SYSML2_-73 Transformation does not cover SysMLv1::TriggerOnNestedPort SysML 2.0a1 open
SYSML2_-74 Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent SysML 2.0a1 open
SYSML2_-75 Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction SysML 2.0a1 open
SYSML2_-72 Transformation does not cover UML4SysML::UnmarshallAction SysML 2.0a1 open
SYSML2-129 Transformation does not cover UML4SysML::Clause SysML 2.0a1 open
SYSML2-133 Transformation does not cover UML4SysML::LinkEndData SysML 2.0a1 open
SYSML2-131 Transformation does not cover UML4SysML::LinkEndCreationData SysML 2.0a1 open
SYSML2-132 Transformation does not cover UML4SysML::LinkEndDestructionData SysML 2.0a1 open
SYSML2-128 Transformation does not cover UML4SysML::ActivityPartition SysML 2.0a1 open
SYSML2-130 Transformation does not cover UML4SysML::ConditionalNode SysML 2.0a1 open
SYSML2_-70 Transformation does not cover UML4SysML::LinkEndDestructionData SysML 2.0a1 open
SYSML2_-67 Transformation does not cover UML4SysML::Clause SysML 2.0a1 open
SYSML2_-71 Transformation does not cover UML4SysML::LinkEndData SysML 2.0a1 open
SYSML2_-68 Transformation does not cover UML4SysML::ConditionalNode SysML 2.0a1 open
SYSML2_-69 Transformation does not cover UML4SysML::LinkEndCreationData SysML 2.0a1 open
SYSML2-124 Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification SysML 2.0a1 open
SYSML2-125 Transformation does not cover UML4SysML::Gate SysML 2.0a1 open
SYSML2-126 Transformation does not cover UML4SysML::OccurrenceSpecification SysML 2.0a1 open
SYSML2-127 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2_-63 Transformation does not cover UML4SysML::Gate SysML 2.0a1 open
SYSML2_-65 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2_-64 Transformation does not cover UML4SysML::OccurrenceSpecification SysML 2.0a1 open
SYSML2_-62 Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification SysML 2.0a1 open
SYSML2-120 Transformation does not cover UML4SysML::Continuation SysML 2.0a1 open
SYSML2-121 Transformation does not cover UML4SysML::GeneralOrdering SysML 2.0a1 open
SYSML2-122 Transformation does not cover UML4SysML::PartDecomposition SysML 2.0a1 open
SYSML2-123 Transformation does not cover UML4SysML::ConsiderIgnoreFragment SysML 2.0a1 open
SYSML2_-59 Transformation does not cover UML4SysML::GeneralOrdering SysML 2.0a1 open
SYSML2_-60 Transformation does not cover UML4SysML::PartDecomposition SysML 2.0a1 open
SYSML2_-61 Transformation does not cover UML4SysML::ConsiderIgnoreFragment SysML 2.0a1 open
SYSML2_-58 Transformation does not cover UML4SysML::Continuation SysML 2.0a1 open
SYSML2-116 Transformation does not cover UML4SysML::TimeConstraint SysML 2.0a1 open
SYSML2-119 Transformation does not cover UML4SysML::DestructionOccurrenceSpecification SysML 2.0a1 open
SYSML2-117 Transformation does not cover UML4SysML::Interval SysML 2.0a1 open
SYSML2-115 Transformation does not cover UML4SysML::DurationInterval SysML 2.0a1 open
SYSML2-118 Transformation does not cover UML4SysML::Image SysML 2.0a1 open
SYSML2_-54 Transformation does not cover UML4SysML::TimeConstraint SysML 2.0a1 open
SYSML2_-55 Transformation does not cover UML4SysML::Interval SysML 2.0a1 open
SYSML2_-57 Transformation does not cover UML4SysML::DestructionOccurrenceSpecification SysML 2.0a1 open
SYSML2_-56 Transformation does not cover UML4SysML::Image SysML 2.0a1 open
SYSML2_-53 Transformation does not cover UML4SysML::DurationInterval SysML 2.0a1 open
SYSML2-112 Transformation does not cover UML4SysML::IntervalConstraint SysML 2.0a1 open
SYSML2-113 Transformation does not cover UML4SysML::DurationObservation SysML 2.0a1 open
SYSML2-111 Transformation does not cover UML4SysML::TimeObservation SysML 2.0a1 open
SYSML2-114 Transformation does not cover UML4SysML::StringExpression SysML 2.0a1 open
SYSML2-110 Transformation does not cover UML4SysML::Duration SysML 2.0a1 open
SYSML2_-50 Transformation does not cover UML4SysML::IntervalConstraint SysML 2.0a1 open
SYSML2_-48 Transformation does not cover UML4SysML::Duration SysML 2.0a1 open
SYSML2_-51 Transformation does not cover UML4SysML::DurationObservation SysML 2.0a1 open
SYSML2_-49 Transformation does not cover UML4SysML::TimeObservation SysML 2.0a1 open
SYSML2_-52 Transformation does not cover UML4SysML::StringExpression SysML 2.0a1 open
SYSML2-107 Transformation does not cover UML4SysML::Extend SysML 2.0a1 open
SYSML2-106 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 open
SYSML2-105 Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete SysML 2.0a1 open
SYSML2-109 Transformation does not cover UML4SysML::DurationConstraint SysML 2.0a1 open
SYSML2-108 Transformation does not cover UML4SysML::TimeInterval SysML 2.0a1 open
SYSML2_-46 Transformation does not cover UML4SysML::TimeInterval SysML 2.0a1 open
SYSML2_-47 Transformation does not cover UML4SysML::DurationConstraint SysML 2.0a1 open
SYSML2_-45 Transformation does not cover UML4SysML::Extend SysML 2.0a1 open
SYSML2-97 Semantics of transfers across interfaces SysML 2.0a1 open
SYSML2-104 Transformation does not cover UML4SysML::GeneralizationSet SysML 2.0a1 open
SYSML2-100 Semantics of a conditional succession using "else" are missing SysML 2.0a1 open
SYSML2-98 Port transfer semantics SysML 2.0a1 open
SYSML2_-42 Transformation does not cover UML4SysML::GeneralizationSet SysML 2.0a1 open
SYSML2-87 Add standard domain libraries for mathematical and physical constants SysML 2.0a1 open
SYSML2-86 Add capability to specify accuracy, uncertainty or tolerance for numerical values SysML 2.0a1 open
SYSML2-90 Redefining feature information missing from specification document SysML 2.0a1 open
SYSML2-91 XMI and JSON for model libraries SysML 2.0a1 open
SYSML2-96 Incorrect action name in graphical notation example SysML 2.0a1 open
SYSML2_-37 XMI and JSON for model libraries SysML 2.0a1 open
SYSML2_-34 Add capability to specify accuracy, uncertainty or tolerance for numerical values SysML 2.0a1 open
SYSML2_-35 Add standard domain libraries for mathematical and physical constants SysML 2.0a1 open
SYSML2_-38 Incorrect action name in graphical notation example SysML 2.0a1 open
SYSML2_-36 Redefining feature information missing from specification document SysML 2.0a1 open
SYSML2-77 Resolve "TODO" in domain library model Time SysML 2.0a1 open
SYSML2-82 Extend ISQ with missing quantity and unit types for US Customary Units SysML 2.0a1 open
SYSML2-71 Graphical BNF for grid rendering is missing SysML 2.0a1 open
SYSML2-70 Graphical notation for variant inheritance from variation requires improvement SysML 2.0a1 open
SYSML2_-31 Graphical BNF for grid rendering is missing SysML 2.0a1 open
SYSML2-61 Special graphical notation for distinguished parameters in name compartment SysML 2.0a1 open
SYSML2-64 Missing graphical notation for Flows Compartment SysML 2.0a1 open
SYSML2-60 Source and target on binary ConnectionDefinition symbol missing SysML 2.0a1 open
SYSML2-67 Graphical BNF mapping to abstract syntax is missing SysML 2.0a1 open
SYSML2-65 Graphical BNF defines lifeline elements incorrectly SysML 2.0a1 open
SYSML2_-26 Special graphical notation for distinguished parameters in name compartment SysML 2.0a1 open
SYSML2-57 Port symbol notation (arrows) needs improvement SysML 2.0a1 open
SYSML2-53 Parameter symbol notation needs improvement SysML 2.0a1 open
SYSML2-56 Missing graphical notation for n-ary connection def and usage SysML 2.0a1 open
SYSML2-55 Quantity and unit for ratio and fraction SysML 2.0a1 open
SYSML2_-22 Quantity and unit for ratio and fraction SysML 2.0a1 open
SYSML2-51 Loop examples incomplete in representative notation table SysML 2.0a1 open
SYSML2-49 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2-48 Consider production for standard case view vs filtered general view SysML 2.0a1 open
SYSML2-50 No support for metadata in graphical notation SysML 2.0a1 open
SYSML2-41 Graphical BNF production proxy refers to wrong label SysML 2.0a1 open
SYSML2-52 Examples requirement derivation, cause effect, and refinement missing SysML 2.0a1 open
SYSML2_-20 Examples requirement derivation, cause effect, and refinement missing SysML 2.0a1 open
SYSML2_-17 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2_-19 Loop examples incomplete in representative notation table SysML 2.0a1 open
SYSML2-37 Identify the owning context in a graphical view SysML 2.0a1 open
SYSML2-40 Graphical BNF production sq-ev-occurrence has inconsistent proxy notation SysML 2.0a1 open
SYSML2-36 Regularization of textual notation for loops SysML 2.0a1 open
SYSML2_-13 Identify the owning context in a graphical view SysML 2.0a1 open
SYSML2-33 Identify impact views on model organization SysML 2.0a1 open
SYSML2-32 Clarify query using view SysML 2.0a1 open
SYSML2-34 Missing graphical notation allocating flow to connection SysML 2.0a1 open
SYSML2-35 Missing explicit explanation of compartments as views SysML 2.0a1 open
SYSML2-31 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2_-7 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2_-9 Identify impact views on model organization SysML 2.0a1 open
SYSML2_-8 Clarify query using view SysML 2.0a1 open
SYSML2-17 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 open
SYSML2-25 Standard view filters incomplete SysML 2.0a1 open
SYSML2-18 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered SysML 2.0a1 open
SYSML2_-5 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered SysML 2.0a1 open
SYSML2_-6 Standard view filters incomplete SysML 2.0a1 open
SYSMOAS-39 Description of deletion in createCommit row seems wrong SystemsModelingAPI 1.0b1 open
KERML-122 validateClassSpecialization is too strict KerML 1.0b1 open
KERML-227 Documentation of features in Transfers library model is wrong KerML 1.0b1 open
KERML-120 FlowTransferBefore needs end feature declarations KerML 1.0b1 open
SYSMOAS-1 missing and superfluous properties SystemsModelingAPI 1.0b2 open
SYSML2-5 UntypedPin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-7 Pin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-1 "Elements not mapped" table sections are empty SysML 2.0a1 open
SYSML2-75 Spatial links can be occurrences SysML 2.0a1 open
SYSML2-69 Inefficient graphical notation specification tooling SysML 2.0a1 open
SYSML2-54 Error in InterfaceUsage semantics subclause SysML 2.0a1 open
SYSML2-78 The .project.json file for the Cause and Effect Domain Library is misnamed SysML 2.0a1 open
SYSML2-26 Standard view filters incomplete SysML 2.0a1 open
SYSML2-81 Association end name " /usageWithDirectedUsage" has a typo SysML 2.0a1 open
SYSML2-153 Error in assert constraint example SysML 2.0a1 open
SYSML2-92 Packages can also have compartments SysML 2.0a1 open
SYSML2-156 Errors in textual BNF for RequirementDefinition and ConcernDefinition SysML 2.0a1 open
SYSML2-23 Transformation of UML4SysML::AddStructuralFeatureValueAction is not correct SysML 2.0a1 open
SYSML2-103 Editoral corrections in 7.16.11 SysML 2.0a1 open
SYSML2-2 ItemFlowEnds of ObjectFlow transformation target are not defined correctly SysML 2.0a1 open
SYSML2-14 UML4SysML::ClearVariableAction transformation does not include a ReturnParameter SysML 2.0a1 open
SYSML2-4 Transformation of UML4SysML::AddVariableValueAction is not correct SysML 2.0a1 open
SYSML2-16 Subsections for mapping classes in section 7.7.2.3.9 should be ordered alphabetically SysML 2.0a1 open
SYSML2-173 Mapping of ValueSpecificationActions does not work for untyped pins SysML 2.0a1 open
SYSML2-19 REAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-88 Mapping of allocation between usage elements is not specified yet SysML 2.0a1 open
SYSML2-171 Optimize Pin mapping class generalization hierarchy SysML 2.0a1 open
SYSML2-200 Description of Subsetting mapping classes is not correct SysML 2.0a1 open
SYSML2-189 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class ActivityEdgeInitialNodeSourceEndFeatureMembership_Mapping SysML 2.0a1 open
SYSML2-178 ClassifierBehaviorFeatureMembership_Mapping does not exist SysML 2.0a1 open
SYSML2-174 EmptyReturnParameterFeatureMembership_Mapping does not exist SysML 2.0a1 open
SYSML2-195 GenericToEndFeatureMembership_Mapping::to property redefines itself SysML 2.0a1 open
SYSML2-193 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class SysML 2.0a1 open
SYSML2-215 ControlFlow transformation target ends are not defined correctly SysML 2.0a1 open
SYSML2-208 A ConnectionUsage should be owned by a FeatureMembership relationship SysML 2.0a1 open
SYSML2-197 ControlFlow target SuccessionAsUsage should have end feature with reference subsetting SysML 2.0a1 open
SYSML2-211 Introduce GenericToTransitionUsage_Mapping class SysML 2.0a1 open
SYSML2-204 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-202 Filter for mapping class Behavior_Mapping is useless SysML 2.0a1 open
SYSML2-43 Graphical BNF sq-message reference incorrect SysML 2.0a1 open
SYSML2-42 Textual production for sq-proxy-label incorrect SysML 2.0a1 open
SYSML2-213 Typo in section 7.6.3 and section 7.6.4: mappingsto SysML 2.0a1 open
SYSML2-39 Graphical BNF production sq-part refers to wrong port SysML 2.0a1 open
SYSML2-45 Graphical BNF interconnection view production incorrect SysML 2.0a1 open
SYSML2-155 Limitation on specifying view renderings SysML 2.0a1 open
SYSML2-62 Incorrect production for attributes-compartment-element SysML 2.0a1 open
SYSML2-44 Graphical BNF sq-message-label usage incorrect SysML 2.0a1 open
SYSML2-84 Connection declaration does not allow a feature value SysML 2.0a1 open
SYSML2-46 Graphical BNF flow-label and interface-label productions missing SysML 2.0a1 open
SYSML2-224 Number missing from table listing Standard View Definitions SysML 2.0a1 open
SYSML2-255 Error in textual BNF for MessageDeclaration SysML 2.0a1 open
SYSML2-223 Table 38 "Standard View Definitions" redundant SysML 2.0a1 open
SYSML2-291 Case View is not a standard view SysML 2.0a1 open
SYSML2-261 Error in textual BNF for TargetSuccession SysML 2.0a1 open
SYSML2-181 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-206 Mapping of UML4SysML::InformationFlow with a realizing connector is not supported SysML 2.0a1 open
SYSML2-180 Mapping of UML4SysML::InformationFlow between definition elements is not supported SysML 2.0a1 open
SYSML2-228 Helpers::activityOwnedRelationships mixes up FinalNodes and FlowFinalNodes SysML 2.0a1 open
SYSML2-232 TIAOperatorExpression_Mapping uses non-existing mapping class EqualOperatorExpressionOperand_Mapping SysML 2.0a1 open
SYSML2-234 RSFAReferenceUsageFeatureMembership_Mapping uses non-existing mapping class SysML 2.0a1 open
SYSML2-236 Resolution of approved issue SYSML2-23 uses outdated mapping classes SysML 2.0a1 open
SYSML2-244 RVVAVariable_Mapping uses CommonAssignmentActionOwningMembership_Mapping, but should be a factory class SysML 2.0a1 open
SYSML2-238 ObjectFlows targeting a final node or a activity parameter node cannot be mapped SysML 2.0a1 open
SYSML2-240 TestCaseActivity_Mapping uses non-existing mapping classes SysML 2.0a1 open
SYSML2-229 ControlFlowSuccessionAsUsage_Mapping uses non-existing mapping class SysML 2.0a1 open
SYSML2-248 CreateLinkObjectAction_Mapping should specialize CreateLinkAction_Mapping SysML 2.0a1 open
SYSML2-258 Mapping of allcation between usage and definition or definition and usage elements does not work SysML 2.0a1 open
SYSML2-246 AEAParameterMembership_Mapping::ownedMemberParameter cannot return OclUndefined SysML 2.0a1 open
SYSML2-281 Map OpqueBehavior always to ActionDefinition SysML 2.0a1 open
SYSML2-250 Typo in AEAReceiverFeatureValue_Mapping::value() SysML 2.0a1 open
SYSML2-304 Mapping of ActivityEdge does not consider ActivityParameterNodes SysML 2.0b1 open
SYSML2-278 UntypedPin_Mapping redefines operation without any changes SysML 2.0a1 open
SYSML2-157 Incorrect font in descriptions of AttributeUsage and TransitionUsage SysML 2.0a1 open
SYSML2-221 UML4SysML::Activities and StateMachines owned by blocks should be mapped to definition elements SysML 2.0a1 open
SYSML2-312 Typo: Table 19 - requirres SysML 2.0b1 open
SYSML2-47 Graphical BNF productions missing for connections SysML 2.0a1 open
SYSML2-328 Incorrect private keyword notation SysML 2.0b1 open
SYSML2-322 Nesting parameter symbols should use rounded rectangles SysML 2.0b1 open
SYSML2-330 Incorrect entry name representative notation SysML 2.0b1 open
SYSML2-287 sq-port-label and sq-ev-occurrence-label productions use Usage SysML 2.0a1 open
SYSML2-319 Wrong line style on action flow succession SysML 2.0b1 open
SYSML2-321 Nesting port symbols should use rounded rectangles SysML 2.0a1 open
SYSML2-335 Incorrect keyword in example "Attributes Compartment" SysML 2.0b1 open
SYSML2-334 Incorrect example "Relationships Compartment" SysML 2.0b1 open
SYSML2-339 Unnecessarily complicated examples "Timeslices Compartment" and "Snapshots Compartment" SysML 2.0b1 open
SYSML2-338 Incomplete example "Occurrences Compartment" SysML 2.0b1 open
SYSML2-332 Incorrect example "Variant Membership" SysML 2.0b1 open
SYSML2-341 Compartments still show nested feature notation SysML 2.0b1 open
SYSML2-344 Missing «perform action» in example "Part with Graphical Compartment with perform actions ..." SysML 2.0b1 open
SYSML2-340 Examples "Timeslices Compartment" and "Snapshots Compartment" incorrectly declare state feature SysML 2.0b1 open
SYSML2-342 Misleading port name in example "Part with Ports" SysML 2.0b1 open
SYSML2-347 Wrong reference usage notation SysML 2.0b1 open
SYSML2-345 Incorrect inherited notation in example "Connection" SysML 2.0b1 open
SYSML2-325 Wrong compartment name: documentation SysML 2.0b1 open
SYSML2-93 Keyword for documentation is "doc" SysML 2.0a1 open
SYSML2-348 Incorrect item flow notation in example "Message" SysML 2.0b1 open
SYSML2-190 The description and derivation of ForLoopActionUsage::seqArgument is wrong SysML 2.0a1 open
SYSML2-99 Incorrect notation in action examples SysML 2.0a1 open
SYSML2-101 Time triggers are relative to "localClock", not "defaultClock" SysML 2.0a1 open
SYSML2-300 validateDefinitionNonVariationMembership and validateUsageNonVariationMembership are redundant with validateVariantMembershipOwningNamespace SysML 2.0b1 open
SYSML2-218 Errors in TransitionUsage semantic constraints SysML 2.0a1 open
SYSML2-298 validateDefinitionVariationMembership and validateUsageVariationMembership are too strict SysML 2.0b1 open
SYSML2-296 validateFramedConcernUsageConstraintKind constraint is misnamed SysML 2.0b1 open
SYSML2-254 Redundant numbered list in language description of usage SysML 2.0a1 open
SYSML2-191 deriveForLoopActionUsageBodyAction is misnamed SysML 2.0a1 open
SYSML2-302 validateOccurrenceUsageIndividualDefinition OCL is wrong SysML 2.0b1 open
SYSML2-301 validateUsageOwningType constraint is too restrictive SysML 2.0b1 open
SYSML2-356 The OCL for the body of ConstraintUsage::namingFeature is incorrect SysML 2.0b1 open
SYSML2-306 validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization constraints are too restrictive SysML 2.0b1 open
SYSML2-303 validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization OCL is wrong SysML 2.0b1 open
SYSML2-414 checkTransitionUsageSourceBindingConnector text and OCL are different SysML 2.0b1 open
SYSML2-398 TransitionUsage effectAction attribute text and constraint are different SysML 2.0a1 open
SYSML2-424 WhileLoopsActionusage title typos SysML 2.0b1 open
SYSML2-423 checkIfActionUsageSpecialization OCL specifiesFromLibrary typo SysML 2.0b1 open
SYSML2-66 Graphical BNF for n-ary connections missing SysML 2.0a1 open
SYSML2-418 Description of TimeEvent_Mapping is a note SysML 2.0b1 open
SYSML2-437 The transformation specification does not explicitly specify how to map a ValueType SysML 2.0b1 open
SYSML2-416 Description of ChangeEvent_Mapping is a note SysML 2.0b1 open
SYSML2-420 InformationFlow mapping classes should use GenericTo mapping classes SysML 2.0b1 open
SYSML2-432 Part properties with AggregationKind::none or shared are not mapped to PartUsage with isComposite=false SysML 2.0b1 open
SYSML2-446 Document how SysML v1 properties are mapped to SysML v2 SysML 2.0b1 open
SYSML2-299 validateDefinitionVariationSpecialization and validateUsageVariationSpecialization OCL is wrong SysML 2.0b1 open
SYSML2-443 Property_Mapping should map to ItemUsage and the class name is misleading SysML 2.0b1 open
SYSML2-441 Change the table header of the overview tables in the mapping class specification chapters SysML 2.0b1 open
SYSML2-439 UML4SysML::Class should be mapped to ItemDefinition SysML 2.0b1 open
SYSML2-252 Graphical BNF opaque "text block" productions SysML 2.0a1 open
SYSML2-425 LoopActionUsage descriptions refer to property not in metamodel SysML 2.0b1 open
SYSML2-343 Mistake in example "Part performs a reference action (action1) that references ..." SysML 2.0b1 open
SYSML2-63 Various incorrect Graphical BNF productions SysML 2.0a1 open
SYSML2-331 Incomplete textual notation in example "Subsetting" SysML 2.0b1 open
SYSML2-139 Transformation does not cover SysMLv1::~InterfaceBlock SysML 2.0a1 open
SYSML2-58 Representative notation table uses deprecated «equal» SysML 2.0a1 open
SYSML2-21 RSAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-95 Flows Compartment example graphical notation missing SysML 2.0a1 open
SYSML2-280 ElementMain_Mapping::ownedRelationship is wrong SysML 2.0a1 open
SYSML2-422 GenericToItemDefinition_Mapping should specialize GenericToOccurrenceDefinition_Mapping SysML 2.0b1 open
SYSML2-346 Incorrect notation in example "Binding Connection" SysML 2.0b1 open
SYSML2-349 Incorrect item flow notation in example "Interface as Node" SysML 2.0b1 open
SYSML2-333 Incomplete textual notation in example "Variants Compartment" SysML 2.0b1 open
SYSML2-350 Incomplete flow notation in example "Flow as Node" SysML 2.0b1 open
SYSML2-412 SYSML2-180 uses non-existing general mapping class GenericToItemUsage_Mapping SysML 2.0b1 open
SYSML2-453 Text error in List property construction SysML 2.0b1 open
SYSML2-451 Missing production for ConjugatePortTyping SysML 2.0b1 open
SYSML2-452 misspelled ConjugatePortTyping should be ConjugatedPortTyping SysML 2.0b1 open
SYSML2-431 Incorrect EBNF specification SysML 2.0b1 open
SYSML2-454 PrefixComment should not be a production for AnnotatingElement SysML 2.0b1 open
SYSML2-79 View::viewpointSatisfactions should subset viewpointChecks and checkedConstraints SysML 2.0a1 open
SYSML2-467 RequirementConstraintUsage should not have a RequirementBody SysML 2.0b1 open
SYSML2-513 Missing text in some main mapping sections SysML 2.0b1 open
SYSML2-241 TestCaseVerifyRequirementUsage_Mapping uses non-existing mapping classes SysML 2.0a1 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-83 Narrow down return types of SpatialItem::PositionOf and ::CurrentPositionOf SysML 2.0a1 open
SYSML2-295 Causation end features need to redefine source and target SysML 2.0a1 open
SYSML2-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-253 Additional cases when usages are required to be referential SysML 2.0a1 open
SYSML2-490 Actions::acceptSubactions and sendSubactions should subset acceptActions and sendActions SysML 2.0b1 open
SYSML2-28 Validation constraints are missing in the SysML abstract syntax SysML 2.0a1 open
SYSML2-500 The derivation of AssignmentActionUsage::referent is wrong SysML 2.0b1 open
SYSML2-305 Message and flow connection ends should be occurrence usages SysML 2.0b1 open
SYSML2-497 validateTriggerInvocationExpressionAfterArgument constraint is too strong SysML 2.0b1 open
SYSML2-491 KerML constraint requires updates to Systems Library models SysML 2.0b1 open
SYSML2-468 binding connector production overly constraining SysML 2.0a1 open
SYSML2-498 validateTriggerInvocationExpressionWhenArgument constraint is wrong SysML 2.0b1 open
SYSML2-458 Missing production for connections with an edge on one or both ends SysML 2.0a1 open
SYSML2-492 KerML constraint requires updates to Domain Library models SysML 2.0a1 open
SYSML2-457 Missing graphical BNF production for keyword extension using #key word in guillemet in compartments SysML 2.0a1 open
SYSML2-68 Graphical notation for nested reference usage needs resolution SysML 2.0a1 open
SYSML2-495 Textual notation BNF for TriggerExpression is wrong SysML 2.0b1 open
SYSML2-94 Confusing naming in Individual Occurrence example SysML 2.0a1 open
SYSML2-102 Semantic constraint for target of AssignmentActionUsage is missing SysML 2.0a1 open
SYSML2-80 Reflective SysML abstract syntax model has inconsistencies SysML 2.0a1 open
SYSML2-227 Subsections of section 7.7.2.3.7 should be ordered alphabetically SysML 2.0a1 open
SYSML2-38 Textual and graphical notations for flow on connection unclear SysML 2.0a1 open
SYSML2-336 Incorrect notation in example "Individual Occurrence" SysML 2.0b1 open
SYSML2-499 Assignments parsed without a target will fail validateAssignmentActionUsageArguments SysML 2.0b1 open
SYSML2-351 Unnecessary event declaration in example "Message" SysML 2.0b1 open
SYSML2-459 Resolution of approved issue SYSML2-241 is not considered by merged issue SYSML2-240 SysML 2.0b1 open
SYSML2-556 Typos in Quantities and Units Domain Library SysML 2.0b1 open
SYSML2-481 Use of the term 'Feature' SysML 2.0b1 open
SYSML2-536 TestCaseVerifyRequirementUsage_Mapping.ownedRelationship() SysML 2.0a1 open
SYSML2-578 Incorrect graphical notation for message between ports SysML 2.0b1 open
SYSML2-560 Add note on FlowFeature direction to textual notation grammar SysML 2.0b1 open
SYSML2-566 Section containing tables about elements not mapped should get an introductory text SysML 2.0b1 open
SYSML2-577 Incorrect graphical notation for flow connection SysML 2.0b1 open
SYSML2-582 Incorrect graphical notation for flow between actions SysML 2.0b1 open
SYSML2-579 Incorrect graphical notation for flow connections in Flow as Node SysML 2.0b1 open
SYSML2-583 Incorrect graphical notation for successions examples with actions SysML 2.0b1 open
SYSML2-581 Mistakes in example Interface as Node (with flow) SysML 2.0b1 open
SYSML2-611 OCL rule deriveDefinitionOwnedFlow references non-existent class called FlowUsage SysML 2.0b1 open
SYSML2-580 Incorrect and incomplete sequence view with message SysML 2.0b1 open
SYSML2-612 OCL rule deriveUsageNestedFlow references non-existent class called FlowUsage SysML 2.0b1 open
SYSML2-620 Textual notation production for Comment is wrong SysML 2.0b1 open
SYSML2-226 Incorrect reference to SysML v1 to SysML v2 Transformation SysML 2.0a1 open
SYSML2-616 User-defined keywords are not allowed on control nodes SysML 2.0b1 open
SYSML2-219 Action::decisionTransitions should subset Action::transitions SysML 2.0a1 open
SYSML2-599 Wrong production for adding state-def as a definition node SysML 2.0a1 open
SYSML2-558 checkStateUsageSpecialization constraint is incorrect SysML 2.0b1 open
SYSML2-529 OCL for deriveViewDefinitionViewCondition and deriveViewUsageViewCondition are wrong SysML 2.0b1 open
SYSML2-597 checkFlowConnectionUsageSpecialization is too restrictive about FlowConnections SysML 2.0b1 open
SYSML2-552 Errors in the TradeStudy domain model SysML 2.0b1 open
SYSML2-182 Universal features can have many values SysML 2.0a1 open
SYSML2-430 Subsetting of subjectParameter properties is wrong SysML 2.0b1 open
SYSML2-318 Adornments on ends missing in graphical syntax SysML 2.0b1 open
SYSML2-554 Enumeration definitions VerdictKind and VerificationMethodKind are missing from specification document SysML 2.0b1 open
SYSML2-29 Name all associations in the SysML abstract syntax SysML 2.0a1 open
SYSML2-30 Follow typographical conventions in the SysML Metamodel clause SysML 2.0a1 open
SYSML2-158 Example FrontAxle definition SysML 2.0a1 open
SYSML2-159 Example analysis case fuelEconomyAnalysis SysML 2.0a1 open
SYSML2-426 specializesFromLibrary arguments use inconsistent notation for strings SysML 2.0b1 open
SYSML2-626 Incorrect textual notation for TextualRepresentation SysML 2.0b1 open
SYSML2-484 Incorrect textual notation for rep annotation SysML 2.0a1 open
SYSML2-527 The XMI versions of standard libraries should be delivered SysML 2.0a1 open
SYSML2-561 Intersection missing for some multiple specializations SysML 2.0b1 open
SYSML2-562 Tables in overview sections have empty cells SysML v2 column SysML 2.0b1 open
SYSML2-564 Mapping tables in the overview sections show duplicates in the SysML v2 column SysML 2.0b1 open
SYSML2-569 Rename ~InterfaceBlock_Mapping SysML 2.0b1 open
SYSML2-587 The mapping name "~InterfaceBlock_Mapping" is not convenient SysML 2.0a1 open
SYSML2-613 Constraint on Definition variation memberships is too restrictive SysML 2.0b1 open
SYSML2-615 Constraint on Usage variation memberships is too restrictive SysML 2.0b1 open
SYSML2-640 Find a better way to differ between definition and instance elements in graphical notation SysML 2.0b1 open
SYSML2-636 package View and Viewpoint TBD should not be included in the xmi file SysML 2.0b1 open
SYSML2-634 VerificationCase::subVerificationCases is typed incorrectly SysML 2.0b1 open
SYSML2-641 Do not use abbreviations for key word in SysML v2/KerML textual concrete syntax SysML 2.0b1 open
SYSML2-844 Annotation diagram needs to be updated SysML 2.0b1 open
SYSML2-631 User-defined keywords are not allowed on metadata SysML 2.0b1 open
SYSML2-642 Make orthogonal and rounded corners the default connector style for architectural drawings SysML 2.0b1 open
SYSML2-185 ISQ in specification and libraries not aligned SysML 2.0a1 open
SYSML2-85 Effective name is not correct for a redefined perform action usage SysML 2.0a1 open
SYSML2-635 Issues with SysML grammar SysML 2.0b1 open
SYSML2-553 checkRequirementUsageObjectiveRedefinition is incorrect SysML 2.0b1 open
SYSML2-783 Parsing KerML Feature elements from SysML textual notation SysML 2.0b1 open
SYSML2-637 User-defined keywords are not allowed on enumeration definitions SysML 2.0b1 open
SYSML2-643 Comment locale not in textual notation SysML 2.0b1 open
SYSML2-59 Inconsistent graphical notation for succession, message and flow edges SysML 2.0a1 open

Issues Descriptions

Typo in description of namespace

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

    The spec says "For an OwningMembership, the owningMemberName and owningMemberShortName are given by the Element name and shortName"

    I think this should be ownedMemberName and ownedMemberShortName

    <Note that this was found in Version 1.0, Beta 2.2>

  • Reported: KerML 1.0b2 — Sat, 8 Feb 2025 11:33 GMT
  • Updated: Wed, 12 Feb 2025 19:48 GMT

Resolve "TODO" in domain library model Time

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

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

     * TODO: Add constraint to verify ISO 8691 extended string encoding.
    
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 18:47 GMT
  • Updated: Wed, 12 Feb 2025 19:42 GMT

Evaluation problem with TradeStudyObjectives

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

    The Analysis Domain Library model TradeStudies includes the following definition:

    	requirement def MinimizeObjective :> TradeStudyObjective {
    		doc
    		/*
    		 * A MinimizeObjective is a TradeStudyObjective that requires that the 
    		 * selectedAlternative have the minimum ObjectiveFunction value of all the
    		 * given alternatives.
    		 */
    		 
    		subject :>> selectedAlternative;
    		in ref :>> alternatives;
    		in calc :>>fn;
    	
    		out attribute :>> best = alternatives->minimize {
    			doc
    			/*
    			 * For a MinimizeObjective, the best value is the minimum one.
    			 */
    		
    			in x; fn(x)
    		};
    	}
    

    (and there is a similar definition for MaximizeObjective that uses maximize instead of minimize). Unfortunately, in the definition minimize in the Kernel Function Library model ControlFunctions, the functional argument to minimized is named fn, and, in the expression fn(x), the name fn gets bound to this parameter, instead of to MinimizeObjective::fn. This means that an evaluation of the invocation of minimize as given will result in an infinite recursion (and similarly for the call to maximize in MaximizeObjective).

  • Reported: SysML 2.0b2 — Wed, 17 Jul 2024 23:06 GMT
  • Updated: Wed, 12 Feb 2025 19:29 GMT

Graphical notation for filter conditions not defined

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

    The specification does not define how to show filter conditions at an import relationship, and it also does not define a compartment for packages for owned filter conditions.

  • Reported: SysML 2.0b2 — Wed, 12 Feb 2025 16:33 GMT
  • Updated: Wed, 12 Feb 2025 16:33 GMT

Table 16 Graphical Notation does not match Textual Notation

  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    "State with entry, do and exit actions": image showns definition by StateDef1, textual notation does not show this.

  • Reported: SysML 2.0b1 — Tue, 11 Jun 2024 22:01 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Mapping of ObjectFlows with ForkNodes

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

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

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

  • Reported: SysML 2.0b1 — Mon, 24 Jul 2023 13:16 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT
  • Attachments:

ChangeEvent should be mapped to an accept action instead of TextualRepresentation

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

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

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 11:35 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Table 16 has misspelling issue

  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    "State with entry, do and exit actions." - code shows "entry actio1" instead of "entry action1"

  • Reported: SysML 2.0b1 — Tue, 11 Jun 2024 21:48 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

"Universal" package-level features can have many values.

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

    The feature below is intended to identity the same value on all instances, but each instance can identify its own (see KERML-56).

    ISQSpaceTime::universalCartesianSpatial3dCoordinateFrame [1] { ... }
    
  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:17 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

element-node not defined

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

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

  • Reported: SysML 2.0a1 — Wed, 27 Sep 2023 10:09 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Missing production for n-ary connection definition graphical

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

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

  • Reported: SysML 2.0a1 — Fri, 22 Sep 2023 12:11 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Unredefinable shape attributes

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

    [From Dr. Charles Manion] Values for Shapes::RightCircularCylinder::radius cannot be specified by redefinition because it is given a value in CircularCylinder (= semiMajorAxis). Might be others like this in Shapes.

  • Reported: SysML 2.0b2 — Sat, 11 Jan 2025 15:13 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Inconsistent and/or incomplete graphical notation for standard reference-subsetted usages

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

    The specification contains inconsistent graphical notation for the standard textual shorthand constructs that declare reference-subsetted usages. The full list of shorthand reference-subsetted usage patterns to be made consistent is:

    • assert (constraint)
    • assume (constraint)
    • exhibit (state)
    • frame (concern)
    • include use case
    • perform (action)
    • require (constraint)
    • satisfy (requirement)
    • verify (requirement)

    In addition, a mix of verb forms are used: some use the infinitive (exhibit states, satisfy requirements), some use third person singular form (exhibits, satisfies). This is confusing and should be regularized following a single rule.

    This affects both the representative notation examples in clause 7 as well as the graphical BNF in subclause 8.2.3.

  • Reported: SysML 2.0b2 — Wed, 24 Jul 2024 14:06 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Explanation for extended-usage and extended-def concepts

  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    In the GBNF 8.2.3.6 Definition and Usage Graphical Notation (pages 192-195) of the SysML v2 Specification, the "extended-def" and "extended-usage" concepts are introduced without any explanation of what they represent—whether they refer to a usage/definition annotated with any metadata, semantic metadata, or something else. This is important because "extended-def" and "extended-usage" have dedicated symbolic representations, as shown below (simplified):
    extended-def-name-compartment ='«' DefinitionPrefix 'def' '»' definition-name-with-alias
    extended-usage-name-compartment ='«' UsagePrefix '»' usage-name-with-alias

    To sum up, this symbolic graphical representation allows only annotated metadata within guillemets to be displayed, while omitting the metaclass name. During the OMG Graphical Specification meeting, it was highlighted that extended usage and definition should only be interpreted when annotated with SemanticMetadata rather than any Metadata. However, this is not documented anywhere in the SysML v2 specification.

  • Reported: SysML 2.0b2 — Mon, 20 Jan 2025 08:07 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

The approved Issue KERML_-18 requires the transformation specification to be adjusted

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

    KERML_-18 introduces the concept of cross feature that shall be taken into account for the transformation of SysMLv1 associations and their ends

  • Reported: SysML 2.0b2 — Fri, 7 Feb 2025 21:35 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Signal_Mapping maps to ItemDefinition but description says AttributeDefinition

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

    A UML4SysML::Signal is mapped to an ItemDefinition but the description of the mapping class Signal_Mapping states that it is mapped to an AttributeDefinition.

  • Reported: SysML 2.0b2 — Tue, 28 Jan 2025 08:49 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Resolution SYSML2_-424 uses invalid operation call of base mapping class

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

    The resolution of issue SYSML2_-424 adds a call of ElementMain_Mapping::ownedRelationship() to the operation InformationFlow_Mapping::ownedRelationship(). However, InformationFlow_Mapping is not a main mapping and does not directly or indirectly specializes ElementMain_Mapping which makes the call invalid.

    self.oclAsType(ElementMain_Mapping).ownedRelationship()
    
  • Reported: SysML 2.0b2 — Fri, 31 Jan 2025 13:50 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

not possible to include action (effect) on a decision branch transition

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

    currently it is not possible to include a textual effect on a guarded transition (branch).

  • Reported: SysML 2.0b2 — Wed, 29 Jan 2025 09:41 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Action node is missing on stateflow

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

    stateflow allows entry, exit, and do action nodes, but not action nodes otherwise. This would be useful to show effects on stateflows.

  • Reported: SysML 2.0b2 — Mon, 27 Jan 2025 12:06 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Incorrect VerificationMethodKind values in Table 21

  • Status: open  
  • Source: Aerospace Corporation ( Mr. Ryan Noguchi)
  • Summary:

    In Table 21 on page 136 of the SysML v2 Specification (Beta 2.3, Release 2024-11), incorrect verification method kind names are shown in both the graphical and textual notation examples:

    "inspection" is incorrect; it should be "inspect"
    "analysis" is incorrect; it should be "analyze"
    "demonstration" is incorrect; it should be "demo"

  • Reported: SysML 2.0b2 — Fri, 24 Jan 2025 18:17 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Wrong guard expression in Graphical BNF

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

    Current expression '[' ExpressionParameterMember ActionBodyParameterMember ']' is wrong, should be '[' ownedExpression ']'

  • Reported: SysML 2.0b2 — Wed, 29 Jan 2025 08:10 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

Incomplete description of TestCaseVerifyObjectiveMembership_Mapping

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

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

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 17:16 GMT
  • Updated: Wed, 12 Feb 2025 06:36 GMT

two haves

  • Key: KERML_-142
  • Status: open  
  • Source: Elparazim ( Edward Roberts)
  • Summary:

    Certain primitive data types have have specified extents of values

    two "have"s remove one

  • Reported: SysML 2.0b1 — Sun, 9 Jun 2024 17:37 GMT
  • Updated: Wed, 12 Feb 2025 05:55 GMT

ownedParameterMember should be ownedMemberParameter

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

    typo in OCL, also on page 184

  • Reported: SysML 2.0b2 — Sat, 23 Nov 2024 10:48 GMT
  • Updated: Wed, 12 Feb 2025 05:55 GMT

Global scope notation

  • Key: KERML_-101
  • Status: open  
  • Source: Dassault Systemes ( Mr. Andrius Armonas)
  • Summary:

    Problem:
    Currently, there is no global scope operator specified. This makes it impossible to target an element in the global scope if an element with the same name exists in an intermediate scope.

    We should be able to target an element in the global scope, even if an intermediate element has the same name.

    Proposed Solution:
    Introduce a global scope operator: $::

    Example using the global scope notation:

    $::'Port Example'::FuelOutPort::temperature

  • Reported: SysML 2.0b2 — Fri, 26 Jul 2024 11:14 GMT
  • Updated: Wed, 12 Feb 2025 05:55 GMT

Lack of documentation of purpose and semantics of single-line and multiline notes

  • Status: open  
  • Source: Aerospace Corporation ( Mr. Ryan Noguchi)
  • Summary:

    The textual notation of single-line (//) and multiline (/** */) notes does not appear to be documented in either the SysML v2 or KerML specifications. These are described in the Intro to the SysML v2 Language - Textual Notation slide deck, are used extensively in example models throughout both specs, and appear in the BNF in 8.2.2.2 of the KerML Spec Beta 2.4. However, their intended use and semantics are not described anywhere in either spec. It should be important to state in the spec(s) that these notes are intended to not be part of the model, if this is still true.

  • Reported: SysML 2.0b2 — Tue, 11 Feb 2025 17:33 GMT
  • Updated: Tue, 11 Feb 2025 19:15 GMT

subsets of scalarQuantities should be nonunique

  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Axel Scheithauer)
  • Summary:

    scalarQuantities is defined as nonunique. However some of its subsets are not. They probably should be nonunique.

    Examples:
    width, height or gaugePressure

    Also many don't have multiplicity [*]. As far as I know, this would not be necessary, because it is the default for attributes defined at package level anyway. However, length and scalarQuantities itself do have an explicit multiplicity. I guess it should be consistent.

  • Reported: SysML 2.0b2 — Thu, 6 Feb 2025 17:03 GMT
  • Updated: Sun, 9 Feb 2025 18:51 GMT

Adopted resolution SYSML2_-403 has impact on the v1 to v2 Transformation

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

    SYSML2_-403 change semantics and the class hierarchy for FlowConnectionUsage and therefor impact the specification of the transformation that is related to that class

  • Reported: SysML 2.0b2 — Fri, 20 Dec 2024 17:43 GMT
  • Updated: Sat, 8 Feb 2025 05:27 GMT

Mapping class description AEAChangeParameterFeatureMembership_Mapping is missing

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

    The mapping class AEAChangeParameterFeatureMembership_Mapping is in the transformation model, i.e., the XMI and is referenced by the mapping class AEAChangeParameterTrigger_Mapping, but the description is missing in the document.

  • Reported: SysML 2.0b2 — Wed, 13 Nov 2024 11:14 GMT
  • Updated: Sat, 8 Feb 2025 05:20 GMT

Various constraints need to take feature chaining into account

  • 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: Fri, 7 Feb 2025 23:22 GMT

Semantics of transfers across interfaces

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

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

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:23 GMT
  • Updated: Fri, 7 Feb 2025 23:03 GMT

Alignment of selected graphical symbols in states and actions.

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

    Some graphical symbols used in state machine diagrams and activity diagrams in SysML v1 have been informally carried over to SysML v2. However, there are inconsistencies in how the symbols are used in SysML v2 actions and states. The intent is to align the symbols shown in the attachment that include the graphical SysML v2 symbols in action flow views that correspond to the initial node, flow final, and activity final with the SysML v2 graphical symbols in state transition views that correspond to the initial pseudo state, final state, and terminal node pseudo state. This will also require addressing the symbols for entry action which is currently informally depicted in SysML v2 with a solid filled circle like the initial pseudo state.

  • Reported: SysML 2.0b2 — Sat, 2 Nov 2024 15:22 GMT
  • Updated: Fri, 7 Feb 2025 19:53 GMT
  • Attachments:

Incorrect graphical notation for parameters with nested items in example "Flow as Node"

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

    In subclause 7.13.1, Table 11, example "Flow as Node" the subitems of parameters item1 and item2 of the flow between action1 and action2 are depicted in the elaborated flow node with parameter symbols subItem1, subItem2, subItem3. The current graphical notation is as follows:

    Currently parameter nodes can only show nested parameters and direction. They need to be able to show owned features such as item usages.

  • Reported: SysML 2.0b2 — Mon, 21 Oct 2024 13:09 GMT
  • Updated: Fri, 7 Feb 2025 19:50 GMT
  • Attachments:

Diagram frame production not properly integrated into graphical BNF

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

    While there is a production for a diagram frame, it is not used by the graphical BNF, other than by "usage-node".
    There is a need to specify how diagram frames are integrated into the various view productions, such as general-view, interconnection-view etc

  • Reported: SysML 2.0b2 — Tue, 20 Aug 2024 10:07 GMT
  • Updated: Fri, 7 Feb 2025 19:47 GMT
  • Attachments:

Send action examples in representative notation tables wrong

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

    In clause 7.16.1, the examples provided for send action are confusing and erratic. 5 alternative graphical examples for a single textual reference shown all of them have issues.

    • First example might be correct, if payload is indeed a parameter
    • Second example simply partial and lacks information such as picture
    • 3rd example use guiileimets in the textual expression and has redundant parameter symbols
    • 4th example Show(shoot.picture) misaligned with textual example
    • 5th example is partial and ot equivalent to the textual reference
  • Reported: SysML 2.0b2 — Wed, 14 Aug 2024 07:41 GMT
  • Updated: Fri, 7 Feb 2025 19:47 GMT
  • Attachments:

Flow connections are incorrectly both structure and behavior

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

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

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

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

  • Reported: SysML 2.0b1 — Fri, 8 Dec 2023 17:04 GMT
  • Updated: Fri, 7 Feb 2025 19:26 GMT
  • Attachments:

Accepters on transition usages from entry actions

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

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

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:29 GMT
  • Updated: Fri, 31 Jan 2025 23:45 GMT

Entry, do and exit actions compartment should be named "state actions"

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

    In subclause 7.17.1, Table 16, example row "State with entry, do and exit actions", the compartment label is "actions".

    In subclause 8.2.3.17 in production state-actions-compartment the compartment label is "states".

    To be explicit and unambiguous, in both places the label should be "state actions".

  • Reported: SysML 2.0b2 — Thu, 14 Nov 2024 15:35 GMT
  • Updated: Fri, 31 Jan 2025 23:31 GMT

No else branch for a decision node

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

    The graphical BNF and representative notation do not support an else branch originating from a decision node.

  • Reported: SysML 2.0b2 — Wed, 6 Nov 2024 15:25 GMT
  • Updated: Fri, 31 Jan 2025 23:24 GMT
  • Attachments:

Not possible to show inherited symbol in name compartment

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

    Graphical notation uses a caret symbol "^" to show inherited properties. This is currently only possible for textual compartments, it also needs to be enabled for name compartments.

  • Reported: SysML 2.0b2 — Wed, 23 Oct 2024 09:27 GMT
  • Updated: Fri, 31 Jan 2025 23:15 GMT

Textual notation for send actions is too limited

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

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

    send payloadExpression via senderExpression to receiverExpression

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

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

  • Reported: SysML 2.0b1 — Wed, 8 Nov 2023 17:26 GMT
  • Updated: Fri, 31 Jan 2025 10:48 GMT

Graphical BNF production proxy should be contextualized

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:40 GMT
  • Updated: Fri, 31 Jan 2025 10:43 GMT
  • Attachments:

Incorrect declaration of parameters on actions


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

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

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

  • Reported: SysML 2.0b2 — Thu, 20 Jun 2024 12:44 GMT
  • Updated: Wed, 29 Jan 2025 05:54 GMT
  • Attachments:

Accept action in representative notation tables is confusing and needs cleanup

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

    Clause 7.16.1 (rep. notation for actions) shows a graphical notation example of an accept action corresponding to the following textual notation:

    action trigger1 : Trigger 
    accept scene : Scene via viewPort;
    

    It shows 3 alternative graphical notations which are confusing and inconsistent.
    That graphical representative example needs to be corrected. Here are few issues:

    • it shows an unbound parameter "receiver" in 2nd and 3rd examples
    • first example uses the type Trigger instead of Trigger1
    • 3rd example uses guillemets in the wrong way
    • too many options instead of one "canonical" way to do this
    • it uses a parameter that in 2nd example called scene and in 3rd example called payload
  • Reported: SysML 2.0b2 — Mon, 29 Jul 2024 07:03 GMT
  • Updated: Wed, 29 Jan 2025 05:53 GMT
  • Attachments:

VerificationKind should be VerificationMethodKind

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

    In Clause 7.23.2, the first textual notation example includes

    metadata VerificationMethod {
      kind = VerificationKind::test;
    }
    

    But it should be

    metadata VerificationMethod {
      kind = VerificationMethodKind::test;
    }
    
  • Reported: SysML 2.0b2 — Thu, 26 Dec 2024 16:35 GMT
  • Updated: Wed, 29 Jan 2025 05:30 GMT

Cross features for connection definitions and connection usages

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

    Resolution KERML_-87 to issue KERML_-18, which has been approved by the KerML FTF, adds a new `CrossSubsetting` relationship and introduces the concept of cross features for end features of associations and connectors. These changes in KerML require corresponding updates to the concrete syntax, abstract syntax and semantics of connections and connection definitions in SysML, which are based on KerML associations and connectors.

  • Reported: SysML 2.0b2 — Tue, 10 Dec 2024 07:56 GMT
  • Updated: Wed, 29 Jan 2025 05:27 GMT

Missing semantic constraints related to features of Part

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

    In the Systems Library model Parts, the base part definition Part is declared to have the features ownedPorts, ownedActions and ownedStates. These features are described in 8.4.7 Parts Semantics, noting that the are covered further in 8.4.8 Ports Semantics, 8.4.12 Actions Semantics and 8.4.13 States Semantics, respectively. More specifically, 8.4.8.2 Port Usages, 8.4.12.2 Action Usages and 8.4.13.2 State Usages state that the semantic constraints checkPortUsageOwnedPortSpecialization, checkActionUsageOwnedActionSpecialization and checkStateUsageOwnedStateSpecialization determine the required specialization of the relevant Part features. However, of these, checkActionUsageOwnedActionSpecialization is defined in the abstract syntax, but the other two are not.

  • Reported: SysML 2.0b2 — Mon, 29 Jul 2024 18:59 GMT
  • Updated: Wed, 29 Jan 2025 04:37 GMT

ShapeItems can't be SpatialItems

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

    [From Dr. Charles Manion] SpatialItem (eventually) specializes KerML Body, which are required to be 3 dimensional (innerSpaceDimension=3), but the "shapes" in ShapeItems.sysml are all lower dimensional (Curves and Surfaces, innerSpaceDimension=1 and 2, respectively). Since SpatialItem defines coordinates, it would be contradictory to give shapes (and Points, innerSpaceDimension= 0) coordinates.

  • Reported: KerML 1.0b2 — Sat, 25 Jan 2025 16:54 GMT
  • Updated: Sun, 26 Jan 2025 16:16 GMT

Ref Port Displayed with Dashed Lines

  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    In section 8.2.3.12 of the Ports Graphical Notation, ports displayed as shapes have only a solid border, whereas ports on the border of another shape may also have a dashed border, as noted:
    "Dotted line port productions (references) are only possible for nested ports."
    This implies that a nested port can be displayed on another port with a dashed border. However, based on the BNF, the same nested port cannot be displayed with a dashed border when shown as a regular shape.

  • Reported: SysML 2.0b2 — Mon, 30 Dec 2024 14:18 GMT
  • Updated: Thu, 23 Jan 2025 06:37 GMT

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

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

    Clause 8.3.9.5 (OccurrenceUsage), Constraints, says

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

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

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

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

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

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

    which probably aren't intended in this exampie.

  • Reported: SysML 2.0a1 — Mon, 6 Nov 2023 14:05 GMT
  • Updated: Mon, 20 Jan 2025 17:15 GMT

OccurrenceUsage missing portioningFeature

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

    Clause 8.4.5.2 (Occurrence Usages) says

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

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

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

  • Reported: SysML 2.0b1 — Thu, 2 Nov 2023 14:26 GMT
  • Updated: Mon, 20 Jan 2025 17:14 GMT

Control nodes missing from textual notation for states

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

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

  • Reported: SysML 2.0a1 — Wed, 1 Nov 2023 13:19 GMT
  • Updated: Mon, 20 Jan 2025 17:13 GMT

Graphical notation unclear about user-defined keywords for library extensions

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:52 GMT
  • Updated: Mon, 20 Jan 2025 17:13 GMT

Graphical notation unclear on optionality of keywords on edges

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:51 GMT
  • Updated: Mon, 20 Jan 2025 17:12 GMT

Clarify bolding of keywords in concrete graphical syntax

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 13:50 GMT
  • Updated: Mon, 20 Jan 2025 17:12 GMT

Incorrect definition elements in interconnection-element

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

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

  • Reported: SysML 2.0b1 — Wed, 18 Oct 2023 13:46 GMT
  • Updated: Mon, 20 Jan 2025 17:12 GMT

Missalignment between interface graphical production and notation table

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

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

  • Reported: SysML 2.0a1 — Wed, 18 Oct 2023 11:24 GMT
  • Updated: Mon, 20 Jan 2025 17:11 GMT

SysML Libraries' elements shall have an elementId defined

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

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

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

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

    Linked to a similar issue raised on KerML

  • Reported: SysML 2.0a1 — Thu, 13 Jul 2023 06:51 GMT
  • Updated: Mon, 20 Jan 2025 17:10 GMT

Fork/JoinNode succession "other" end multiplicity validations missing

  • 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: Mon, 20 Jan 2025 17:03 GMT

ConstraintProperty should be mapped to a AssertConstraintUsage

  • 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: Mon, 20 Jan 2025 17:03 GMT

Decision/MergeNode SuccessionSpecialization checks missing some constraints

  • 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 7.16.1 (Actions Overview), under Sequencing of Actions, 7.16.3 (Control Nodes), and 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 binding 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: Mon, 20 Jan 2025 17:02 GMT

Package import wildcard is missing

  • 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: Mon, 20 Jan 2025 17:00 GMT

Wrong imported package notation

  • 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: Mon, 20 Jan 2025 17:00 GMT

Nesting parameter symbol is missing optional nested parameter

  • 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: Mon, 20 Jan 2025 17:00 GMT

Binding between action parameters and directed features on ports missing

  • 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: Mon, 20 Jan 2025 16:59 GMT

Metadata declaration needs clarification

  • 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: Mon, 20 Jan 2025 16:59 GMT

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

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

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

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

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:14 GMT
  • Updated: Mon, 20 Jan 2025 16:55 GMT

Graphical BNF defines lifeline elements incorrectly

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:58 GMT
  • Updated: Mon, 20 Jan 2025 16:52 GMT

Port symbol notation (arrows) needs improvement

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:21 GMT
  • Updated: Mon, 20 Jan 2025 16:52 GMT

Parameter symbol notation needs improvement

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

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:32 GMT
  • Updated: Mon, 20 Jan 2025 16:51 GMT

Consider production for standard case view vs filtered general view

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:54 GMT
  • Updated: Mon, 20 Jan 2025 16:51 GMT

Regularization of textual notation for loops

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:02 GMT
  • Updated: Mon, 20 Jan 2025 16:50 GMT

Missing graphical notation allocating flow to connection

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

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

    This should be added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:58 GMT
  • Updated: Mon, 20 Jan 2025 16:49 GMT

Transformation does not cover the mapping of Unit and QuantityKind

  • 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: Mon, 20 Jan 2025 16:16 GMT
  • Attachments:

Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet


Transformation does not cover the different UML4SysML::PseudoStates

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

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

  • Reported: SysML 2.0a1 — Sat, 6 May 2023 12:22 GMT
  • Updated: Mon, 20 Jan 2025 16:14 GMT

Transformation does not cover UML4SysML::ActivityPartition

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:41 GMT
  • Updated: Mon, 20 Jan 2025 16:13 GMT

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:01 GMT
  • Updated: Mon, 20 Jan 2025 16:13 GMT

Accept after guard causes errors in IDE

  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    The specification states in 7.17.3:

    "The accepter action for a transition usage is placed after the guard expression and notated using the accept keyword..."

    The examples in 7.17.3 also show "accept" after the "if' statement.

    However, the implementation (specifically, Eclipse) will not instantiate a transition that has the accept after the guard. It will recognize the accept before the guard.

    For example:

        item def TurnOn;
        state def OffOn {
        	state off;
        	state on;
        	in attribute enabled;
        	transition off_on3 first off accept TurnOn if enabled then on;//This declaration parses
        	transition off_on4 first off if enabled accept TurnOn then on;//This declaration does not parse.
        }
    
  • Reported: SysML 2.0b2 — Tue, 19 Nov 2024 17:20 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT

Ordering of guards and accepts in transitions is inconsistent

  • Status: open  
  • Source: Commonwealth Center for Advanced Manufacturing ( Nicholas Thompson)
  • Summary:

    The fourth and sixth rows of "Table 16. States – Representative Notation" each give an example of a transition statement that contains both an if statement and an accept statement, with the accept before the if.

    ...
    transition
       first state1
       accept trigger1
       if guard1
    ...
    

    However, page 110 and the subsequent examples seem to contradict this:

    A transition usage can also have an accepter, which is an accept action usage use to trigger the transition. The accepter action for a transition usage is placed after the guard expression and notated using the accept keyword, with its payload and receiver parameters specified exactly as discussed in 7.16.8 .

    If an accept before an if has a different meaning than an if before accept, the specification document does not make this obvious.
    The Jupyter Kernel in release 2024-05 of the SysML-v2-Release repository treats an if before an accept as a syntax error.

  • Reported: SysML 2.0b2 — Thu, 11 Jul 2024 14:42 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT

Chapter Trigger_Mapping is empty

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

    The chapter 7.7.5.3.7 Trigger_Mapping is empty.

  • Reported: SysML 2.0b2 — Mon, 19 Aug 2024 14:33 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT

Subclause 7.7.5.3.7 Trigger_Mapping is empty

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

    The subclause 7.7.5.3.7 Trigger_Mapping contains no text.

  • Reported: SysML 2.0b2 — Mon, 18 Nov 2024 08:37 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT

There is no checkSatisfyRequirementUsageSpecialization constraint

  • Status: open  
  • Source: Dassault Systemes ( Mr. Andrius Armonas)
  • Summary:

    SatisfyRequirementUsage subsets Requirements::notSatisfiedRequirementChecks or Requirements::satisfiedRequirementChecks in pilot implementation.

    checkSatisfyRequirementUsageSpecialization constraint should be defined in the specification.

  • Reported: SysML 2.0b2 — Mon, 29 Jul 2024 13:14 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT

Missing Element Import Alias

  • Status: open  
  • Source: Elparazim ( Edward Roberts)
  • Summary:

    in SysMLv1 for an ElementImport one can supply an Alias... That seems to be missing in SysMLv2

  • Reported: SysML 2.0b2 — Wed, 19 Jun 2024 16:31 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT

Description and examples for message notation are wrong

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

    The description of message declarations in 7.13.6 Flow Connection Usages and Messages is incorrect. It states that a message declaration "may or may not include identification of source and target related features. If they are included, then they follow the payload specification (if any), with the source related feature identified after the keyword from, followed by the target related feature after the keyword to." However, the from and to features of a message are not the related features of the message as a flow connection usage. Rather, they are the values of the sourceEvent and targetEvent parameters of the MessageConnection (see parsing in 8.2.2.13.4 Message and Flow Connections and semantics in 8.4.9.6 Flow Connection Usages).

    In light of this, the message declaration example in 7.13.6 is also incorrect, as is the textual notation for the first "Message" example in Table 11 Connections – Representative Notation (showing a message between ports). However, the graphical notation in this example seems to be acceptable, as are both the graphical and textual notations in the second "Message" example (showing a message on a sequence diagram).

  • Reported: SysML 2.0b2 — Mon, 24 Jun 2024 04:43 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT
  • Attachments:

TimeEvent should be mapped to an accept action instead of TextualRepresentation

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

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

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 11:42 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT

TransitionUsage requires binding to succession with mandatory end multiplicities

  • 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: Thu, 16 Jan 2025 00:26 GMT

Transformation does not cover UML4SysML::SignalEvent

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:53 GMT
  • Updated: Thu, 16 Jan 2025 00:26 GMT

Transformation does not cover SysMLv1::FlowProperty

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:49 GMT
  • Updated: Thu, 16 Jan 2025 00:25 GMT

Port transfer semantics

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

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

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:28 GMT
  • Updated: Thu, 16 Jan 2025 00:25 GMT

Remove "Connection" from the names "FlowConnectionDefinition", "FlowConnectionUsage", and "SuccessionFlowConnectionUsage"

  • Status: open  
  • Source: Ansys Government Initiatives ( Mr. Richard Page)
  • Summary:

    After resolution SYSML2_-403 to issue SYSML2_-173, FlowConnectionDefinition no longer specializes ConnectionDefinition (now specializing only ActionDefinition and KerML Interaction), and FlowConnectionUsage no longer specializes ConnectionUsage (now only specializing ActionUsage, ConnectorAsUsage and KerML ItemFlow. As a result of SYSML2_-403, having "Connection" in the name of the "Flow" classes causesconfusion among users that don't see the distinction between structure and behavior.

    Renaming FlowConnectionDefinition to FlowDefinition and FlowConnectionUsage to FlowUsage would avoid confusion going forward. Not making this change prior to finalization of SysML v2 runs the risk of having confusion that would require complex deprecation steps to correct later.

    Similarly for SuccessionFlowConnectionUsage, which specializes FlowConnectionUsage.

  • Reported: SysML 2.0b2 — Wed, 11 Dec 2024 21:29 GMT
  • Updated: Tue, 14 Jan 2025 23:07 GMT

Specification of Satisfy Requirement is Unclear

  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    In the Table 19. Requirements - Representative Notation table in the Satisfy Requirements Compartment element a lot of information is displayed:

    • requirement that is satisfied.
    • nested requirement with their nested features with values.
      However in the 8.2.3.20 Requirements Graphical Notation section, it is not clear what information should be displayed in the satisfy requirement compartment.
      it looks that just text should be added:
      satisfy-requirements-compartment-contents = text-block
      
  • Reported: SysML 2.0b2 — Wed, 18 Dec 2024 09:54 GMT
  • Updated: Mon, 13 Jan 2025 11:42 GMT

Inconsistent compartment labels

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

    In subclause 7.20.1, Table 19, example "Requirement" the compartment labels "require constraints" and "assume constraints" and their content are misleading and inconsistent.

    • Besides pure "require ConstraintUsage" statements a "require constraints" compartment may also contain "require RequirementUsage" statements. Furthermore, a "require RequirementUsage" has the same semantics as a composite RequirementUsage owned by a containing RequirementUsage (see explanation in subclause 7.20.2). Therefore a better compartment name is possibly "requires".
    • Similarly besides pure "assume ConstraintUsage" statement an "assume constraints" compartment may also contain "assume RequirementUsage" statements. Therefore a better compartment name is possibly "assumes".
  • Reported: SysML 2.0b2 — Wed, 16 Oct 2024 14:07 GMT
  • Updated: Sat, 11 Jan 2025 22:26 GMT

Misspelling in Table 16 / graphical and textual notation do not match

  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    Issue 1: textual notation does not include a state definition, but the graphical notation does. Change to match.
    Issue 2: textual notation has an assumed spelling error, also causing a mismatch to graphical notation. In the following notation, "actio1" should likely be "action1".

    state state1

    { entry actio1; do action2; exit action3; }
  • Reported: SysML 2.0b2 — Sat, 10 Aug 2024 19:47 GMT
  • Updated: Sat, 11 Jan 2025 20:03 GMT

Table 6 Duplicate Row Titles

  • Status: open  
  • Source: Arcfield ( Matthew Johnson)
  • Summary:

    This table has two rows where the Element Column states Enums Compartment. Recommend adding information to the row titles to indicate what aspect of the compartment is important. E.g., Enums Compartment (enumeration usage names) and Enums Compartment (enumeration values). Alternatively, combine these into one row.

  • Reported: SysML 2.0b1 — Tue, 11 Jun 2024 19:41 GMT
  • Updated: Sat, 11 Jan 2025 19:57 GMT

Specification lacks precision in multiple sentences that begin with the word 'however'

  • Status: open  
  • Source: Dassault Systemes ( Mr. Daniel Brookshier)
  • Summary:

    There are 94 uses of the word 'however' in the specification, usually starting a sentence. In many cases, the word injects unnecessary text that further confuses and obfuscates the intent. In most cases, what follows is not an exception, rather just another option of the language. In many cases the word can be replaced with ‘if’ or ‘when’ but I also found many cases where a rewrite is necessary.

    Here are the first 45ish specific examples and rewrites. I stopped at page 119 as there is enough evidence to show simple rewriting of the offending test can greatly improved the text. I have also added comments to point to the issue and any further wordsmithing that seems to be required.
    This seems like a minor or even a style issue, ‘however’ the point of this issue is that the use of the word muddles the descriptive intent of the text when it should be precise as possible.

    2. conformance:
    Original:
    However, a tool demonstrating Concrete Syntax Conformance need not represent a model internally in exactly the form modeled for the abstract syntax in this specification.
    Replacement:
    A tool demonstrating Concrete Syntax Conformance need not represent a model internally in exactly the form modeled for the abstract syntax in this specification.

    6.2 Document Organization
    Original:
    However, this clause does not cover details of the Kernel metamodel, which are included by normative reference to the KerML specification [KerML].
    Replacement:
    This clause does not cover details of the Kernel metamodel, which are included by normative reference to the KerML specification [KerML].
    Comment:
    Optionally delete the sentence as it is already assumed that KerML is where the reader finds the details of the details.

    6.3 Acknowlegements
    Original:
    However, work on the specification was also supported by over 200 people in over 80 organizations that participated in the SysML v2 Submission Team (SST), by contributing use cases, providing critical review and comment, and validating the language design.
    Replacement:
    Over 200 people from over 80 organizations participated in the SysML v2 Submission Team (SST), contributing to the specifics and providing reviews and comments.

    7.2.1 Elements and Relationships Overview
    Original:
    However, in some cases, additional shapes may be attached to relationship lines in order to present additional information.
    Replacement:
    Additional shapes may be attached to relationship lines in order to present additional information.

    7.2.2 Elements
    Original:
    Various specific kinds of model elements in SysML are described in subsequent subclauses. However, there are certain concepts that apply to all model elements.
    eplacement:
    Key model elements in SysML are described in subsequent subclauses. Some of the concepts apply to all model elements.
    comments: The opening statement like this are without value to the spec.

    Original:
    The SysML notation does not have any provision for specifying element or alias IDs, since these are expected to be managed by the underlying modeling tooling. Instead, an element can be given a name and/or a short name, and it can also have any number of alias names relative to one or more namespaces (see 7.5).
    Replacement:
    The SysML notation does not have any provision for specifying element or alias IDs because these are expected to be managed by the underlying modeling tooling. Instead of using an ID, an element has a given name and/or a short name that can also have any number of alias names relative to one or more namespaces (see 7.5).

    Original:
    However, unless at least one of these is given, it is not possible to reference the element using the textual notation (though it is still possible to show it in relationships on graphical diagrams).
    Replacement:
    It is not possible to reference the element using the textual notation unless a name or short name is given, though it is still possible to show it in relationships on graphical diagrams.

    Original:
    However, a reserved word may not be used as a name, even though it has the form of a basic name (see 8.2.2.1.2 for the list of the reserved words in SysML).
    Replacement:
    A reserved word may not be used as a name (see 8.2.2.1.2 for the list of the reserved words in SysML).

    Original:
    However, these characters may be included as part of the name itself through use of an escape sequence.
    Replacement:
    Non-printable characters may be included as part of the name itself through use of an escape sequence.

    7.4.2 Comments and Documentation
    Original:
    However, marked up "rich text" for a comment is stored in the comment body in plain text including all mark up text, with all line terminators and white space included as entered, other than what is removed according to the rules referenced above.
    Replacement:
    Marked up "rich text" for a comment is stored in the comment body in plain text including all mark up text, with all line terminators and white space included as entered, other than what is removed according to the rules referenced above.
    Original:
    However, for any other language than "sysml", the SysML specification does not define how the body text is to be semantically interpreted as part of the model being represented
    Replacement:
    For any other language than "sysml", the SysML specification does not define how the body text is to be semantically interpreted as part of the model being represented

    7.5.4 Import Filtering
    Original:
    comments. Namespaces other than packages cannot have filter conditions (except for their special use in view definitions and usages – see 7.25). However, any kind of namespaces may have filtered imports.
    Replacement:
    Namespaces other than packages cannot have filter conditions, except for their special use in view definitions and usages – see 7.25. All kinds of namespaces may have filtered imports.
    comments: It is strange that this is a note as these are very specific semantics rather than an aside as would be described in a note.

    7.6.1 Definition and Usage Overview
    Original:
    However, truck can instead redefine fuel to restrict its definition to DieselFuel, a subclassification of Fuel.
    Replacement:
    Alternatively the Truck could redefine fuel to restrict its definition to DieselFuel, a subclassification of Fuel.
    comments: The paragraphs are rather confusing without a textual language or graphical examples. At least you could refer to an example in the annex. It is also odd to get into alternatives without an example of the alternative.
    Original:
    However, it is expected that if Vehicle is baselined in a configuration management tool, then a change to Vehicle is a new revision, and it is up to the modelers to determine whether to retain the previous version of Vehicle or move to the next revision.
    Replacement:
    If Vehicle is baselined in a configuration management tool, then a change to Vehicle is a new revision, and it is up to the modelers to determine whether to retain the previous version of Vehicle or move to the next revision.

    7.6.3 Usages
    Original:
    However, a tighter default of [1..1] is implicitly declared for the usage if all of the following conditions hold
    Replacement:
    A tighter default of [1..1] is implicitly declared for the usage if all of the following conditions are true:
    Comment: Is there a reference to where this is described in the standard?

    7.6.4 Reference Usages
    Original:
    However, a reference usage is always, by definition, referential. A reference usage is otherwise declared like any other usage, as given above.
    Replacement:
    Reference usages are always referential. A reference usage is declared like any other usage, as given above.
    Comment:
    Once the ‘however’ was removed, the changes to the following sentence is also required to improve the explanation of the concept.

    7.6.5 Effective Names
    Original:
    However, if neither a name or a short name are given in the declaration of a usage with an owned redefinition, then its effective name and short name are implicitly determined by the name and short name of the redefining usage of its first owned redefinition (which may itself be an implicit name, if the redefined usage is itself a redefining usage).
    Replacement:
    When neither a name or a short name are given in the declaration of a usage with an owned redefinition, then its effective name and short name are implicitly determined by the name and short name of the redefining usage of its first owned redefinition (which may itself be an implicit name, if the redefined usage is itself a redefining usage).
    Comment:
    The use of ‘however’ muddled the original explanation. Imagine Java or some other computer language with ‘however’ as a key word.

    7.6.6 Feature Chains
    Original:
    However, their use is particularly important when specifying the related features of a connection usage that are more deeply nested than the connection usage itself (see 7.13). (See also [KerML, 7.3.4.6].)
    Replacement:
    Feature chains are particularly important when specifying the related features of a connection usage that are more deeply nested than the connection usage itself (see 7.13). (See also [KerML, 7.3.4.6].)

    7.6.8 Implicit Specialization
    Comment:
    This may be a good use of however, but look at it anyway and see if it can be avoided,

    7.7.1 Attributes Overview
    Original:
    However, the owner of an attribute usage may be an occurrence definition or usage (or a specialized kind of occurrence, such as an item, part or action). In this case, the value of the attribute usage may vary over the lifetime of its owning occurrence, in the sense that it can have different values at different points in time, reflecting the changing condition of the occurrence over time.
    Replacement:
    The owner of an attribute usage may be an occurrence definition or usage (or a specialized kind of occurrence, such as an item, part or action). When the attribute owner is a usage is an occurrence definition or usage, the value of the attribute usage may vary over the lifetime of its owning occurrence, in the sense that it can have different values at different points in time, reflecting the changing condition of the occurrence over time.
    Comment:
    This is still confusing. It again screams out for a textual/graphical language example.

    7.8.1 Enumerations Overview
    Original:
    However, if the enumeration definition specializes an attribute definition with nested usages, then those nested usages will be inherited by the enumeration definition, and they may be bound to specific values within each enumerated value of the enumeration definition.
    Replacement:
    If the enumeration definition specializes an attribute definition with nested usages, then those nested usages will be inherited by the enumeration definition, and they may be bound to specific values within each enumerated value of the enumeration definition.
    Original:
    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.
    Replacement:
    The reason for this constraint is that enumerated values defined in an enumeration definition would add to the set of enumerated values, which is inconsistent with the semantics of specialization.
    Comment:
    This is a definite improvement over the original text, which is very confusing. It is very strange that given you are creating a new language to get around issues with UML you have not fixed this glaring issue of the inability to specialize enumerations.

    7.8.2 Enumeration Definitions and Usages
    Original:
    However, an enumeration definition must not subclassify another enumeration definition. An enumeration usage is declared as described in 7.6.3, using the kind keyword enum.
    Replacement:
    An enumeration definition must not subclassify another enumeration definition. An enumeration usage is declared as described in 7.6.3, using the kind keyword enum.
    Comment:
    This paragraph seems like a repeat of the previous change request. Suggest choosing one and deleting the other to reduce confusion and need to maintain both statements.

    7.9.1 Occurrences Overview
    Original:
    However, if a composite suboccurrence is removed from its containing occurrence before the end of the lifetime of the containing occurrence, then the former suboccurrence can continue to exist.
    Replacement:
    If a composite suboccurrence is removed from its containing occurrence before the end of the lifetime of the containing occurrence, then the former suboccurrence can continue to exist.
    Original:
    However, if the wheel is removed before the car is destroyed, then the wheel can continue to exist even after the car is destroyed. (See also 7.6 on referential and composite usages.)
    Replacement:
    If the wheel is removed before the car is destroyed, then the wheel can continue to exist even after the car is destroyed. (See also 7.6 on referential and composite usages.)

    Original:
    However, it could also be realized as the start and end of an explicitly modeled flow connection (see 7.13 on flow connections and messages).
    Replacement:
    These events can also be realized as a modeled flow connection (see 7.13 on flow connections and messages).
    Comment:
    This is another statement that becomes more muddled when treating it as an exception when in fact this is not an exeption, but just realkized by another possible construct.

    7.9.3 Time Slices and Snapshots
    Original:
    However, if such an occurrence usage has no explicitly declared definition, but is declared in the body of an occurrence definition, then it is considered to implicitly represent a portion of instances of the containing occurrence definition.
    Replacement:
    If an occurrence usage has no explicitly declared definition, but is declared in the body of an occurrence definition, then it is considered to implicitly represent a portion of instances of the containing occurrence definition.

    7.10.1 Items Overview
    Original:
    However, once the engine assembly is completed, the engine can be considered to be a part that may be installed into a car, where it is expected to perform the action providing power to propel the car. But later it may be removed from the car and again be considered only an inactive item in a junkyard.
    Replacement:
    Once the engine assembly is completed (e.g. the engine has completed manufacturing and exists as a whole), the engine can be considered to be a part that may be installed into a car, where it is expected to perform the action providing power to propel the car. Later in time, the engine may be removed from the car and again be considered only an inactive item in a junkyard.
    Comment:
    This is a weird example. There are many parts to an engine that are added and removed. For example, spark plugs. A spark plug could be a better example as these are assembled of pieces that are not individually replaceable and junked as a whole.

    7.13.1 Connections Overview
    Original:
    However, the values of connection ends (i.e., the things that are actually connected) do not change over time (though they can potentially be occurrences that themselves have features whose values change over time).
    Replacement:
    The values of connection ends (i.e., the things that are actually connected) do not change over time (though they can potentially be occurrences that themselves have features whose values change over time).
    Original:
    However, a message does not specify how the payload is to be obtained from the source or delivered to the target.
    Replacement:
    A message does not specify how the payload is to be obtained from the source or delivered to the target.
    Comment:
    So how do we specify how it obtained? This needs further clarification.

    7.13.2 Connection Definitions and Usages
    Original:
    However, if it declares any owned end features, then each of these must redefine an end feature of the general connection definition, in order, up to the number of end features of the general connection definition.
    Replacement:
    If a connection definition declares any owned end features, then each of these must redefine an end feature of the general connection definition, in order, up to the number of end features of the general connection definition.

    7.13.4 Feature Values
    Original:
    However, for a default, bound feature value, the symbol = may be elided.
    Replacement:
    Optionally. a default, bound feature value, the symbol = may be elided (as shown in the default ‘mass’ in the following example).
    Comment:
    This a capricious and confusing option. Please choose one and delete the other. This adds a complication to the reading of the language that is unnecessary.

    7.13.6 Flow Connection Usages and Messages
    Original:
    A streaming flow is declared similarly to a message, but with the kind keyword flow. However, instead of identifying the source and target features of the flow, such a flow declaration must identify (after the keyword from) the output feature of the source from which the flow receives its payload and (after the keyword to) the input feature of the target to which the flow delivers the payload.
    Replacement:
    A streaming flow has the kind keyword flow and must identify, after the keyword from, the output feature of the source from which the flow receives its payload and, after the keyword to, the input feature of the target to which the flow delivers the payload.
    Comment:
    The use of ‘however’ has created language of no value. The streaming flow is totally different than a message in its form. The rewrite hopefully fixes the first mistake, however the sentence is still rather obtuse and still needs some wordsmithing.

    7.14.2 Interface Definitions and Usages
    Original:
    However, if the declaration part of an interface usage is empty, then the interface keyword is still included, but the connect keyword may be omitted.
    Replacement:
    If the declaration part of an interface usage is empty, then the connect keyword may be omitted.

    7.16.1 Actions Overview
    Original:
    However, if the owner of the perform action usage is an occurrence, then the referenced action performance must be carried out entirely within the lifetime of the performing occurrence.
    Replacement:
    If the owner of the perform action usage is an occurrence, then the referenced action performance must be carried out entirely within the lifetime of the performing occurrence.

    Original:
    However, a succession between action usages may, additionally, have a guard condition, represented as a Boolean expression (see 7.18).
    Replacement:
    A succession between action usages may have an additional guard condition, represented as a Boolean expression (see 7.18).

    7.16.5 Conditional Successions
    Original:
    However, the target of a conditional succession must be specified as a qualified name or feature chain and cannot be a full action usage declaration, even when the shorthand notation is used.
    Replacement:
    The target of a conditional succession must be specified as a qualified name or feature chain and cannot be a full action usage declaration, even when the shorthand notation is used.

    7.17.1 States Overview
    Original:
    However, if the owner of the exhibit state usage is an occurrence, then the referenced state performance must be carried out entirely within the lifetime of the performing occurrence.
    Replacement:
    If the owner of the exhibit state usage is an occurrence, then the referenced state performance must be carried out entirely within the lifetime of the performing occurrence.

    7.17.2 State Definitions and Usages
    Original:
    However, if the keyword parallel is added to a state definition or usage, just before the body part, then the containing state definition or usage becomes a parallel state, and its contained state usages can be performed in parallel. (However, no transitions are allowed between concurrent states; see 7.17.3.)
    Replacement:
    If the keyword parallel is added to a state definition or usage, just before the body part, then the containing state definition or usage becomes a parallel state, and its contained state usages can be performed in parallel. In this case, no transitions are allowed between concurrent states; see 7.17.3.

    Original:
    (However, no transitions are allowed between concurrent states; see 7.17.3.)
    Replacement:
    No transitions are allowed between concurrent states; see 7.17.3.

    7.19.1 Constraints Overview
    Original:
    In general, a constraint may be satisfied sometimes and violated other times. However, an assert constraint usage asserts that the result of a given constraint must be always true at all times.
    Replacement:
    When an assert constraint usage asserts exists, the result of that constraint must be always true at all times. This is compared to a simple constraint may be satisfied sometimes and violated other times.
    Comment:
    This another example of the ‘however’ causing a confusion in the semantics. The spec should say what is true before saying what is true is an exception. In this case, there is no exception, just a differing kind of constraint than one already discussed.

  • Reported: SysML 2.0b2 — Thu, 15 Aug 2024 23:57 GMT
  • Updated: Sat, 11 Jan 2025 19:55 GMT

flow-label definition cut short

  • Status: open  
  • Source: UNICOM Systems ( Mark Gregory)
  • Summary:

    Definition is given as

    flow-label =
    UsageDeclaration? ('«of»' FlowPayloadFeatureMember)? | FlowPayloadF
    
  • Reported: SysML 2.0b2 — Tue, 26 Nov 2024 10:34 GMT
  • Updated: Sat, 11 Jan 2025 19:53 GMT

Apparent use of an overly-generic notation entry in subsetting or redefinition notation specification for Connection end

  • Status: open  
  • Source: UNICOM Systems ( Mark Gregory)
  • Summary:

    I think these specifications in section 8 are too generic.

    a-subsetting =
    '«subsets»' ownedRelationship (',' ownedRelationship)*
    a-redefinition =
    '«redefines»' ownedRelationship (',' ownedRelationship)*
    

    There is no single ownedRelationship = or ownedRelationship : but several ownedRelationship += which I interpret to mean that this is the property that would be added to when parsing.
    The first of these would surely be OwnedSubsetting which has a OwnedSubsetting : specification.

  • Reported: SysML 2.0b2 — Fri, 22 Nov 2024 17:25 GMT
  • Updated: Sat, 11 Jan 2025 19:53 GMT

Notation should be more formally tied with Abstract Syntax

  • Status: open  
  • Source: UNICOM Systems ( Mark Gregory)
  • Summary:

    Each section describing a particular thing e.g. Usage needs a notation subsection which should show all new possible notation relevant to that section where not described elsewhere and how it ties in with abstract syntax in terms of which properties, item types and values are involved.

    Graphical lines which connect items should be described in terms what attributes of what item should refer to which other items.

    Such information should not be buried in a sea of descriptive text, it should be clear and concise.

    An example: 7.10 deals with Items and only lists a couple of symbols and one compartment (displayable property) called 'items'.
    There is no specification of what this compartment is presenting in terms of a) the property or properties to be checked or b) what is referenced.
    Point a can sometimes be answered where they have property name = ... but not in this case.
    Point b can sometimes be answered by following the chain of notation specifications because they sometimes have notationname : type of element = ... - this does point to Usage types.
    I guessed that the nestedItem attribute should be the source of this information.

    The Graphical syntax section identifies another symbol, an item reference, which I guess is the presentation to be used when the Usage is a ReferenceUsage. I say guess because again there is no specification.

    Trying to understand 18: Connections with respect to abstract syntax when each pictured symbol's abstract type is not named is very difficult.

  • Reported: SysML 2.0b2 — Fri, 15 Nov 2024 16:21 GMT
  • Updated: Sat, 11 Jan 2025 19:52 GMT

No Inheritance Symbol for Parameters, Ports, Connectors, Transitions

  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    For ports and parameters on border, connectors and transitions name label there is no indication to display an inheritance symbol.
    The el-prefix is not indicated in none of these element specifications.

    • Ports and parameters on border labels are specified as QualifiedName (‘:’ QualifiedName)*;
    • Connectors labels are specified as UsageDeclaration? / UsageDeclaration? ('of' FlowPayloadFeatureMember)? | FlowPayloadFeatureMember / UsageDeclaration? ('of' ItemFeatureMember)? | ItemFeatureMember;
    • Transitions label is specified as trigger-expression/ActionUsage;
  • Reported: SysML 2.0b2 — Wed, 18 Dec 2024 08:23 GMT
  • Updated: Sat, 11 Jan 2025 19:50 GMT

Metadata Compartment is not Specified

  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    In the Table 25. Metadata - Representative Notation (Chapter 7.26.1 , page 151) table there is an element that specifies the metadata compartment, however, this compartment is not specified in the Graphical BNF.

  • Reported: SysML 2.0b2 — Wed, 18 Dec 2024 08:37 GMT
  • Updated: Sat, 11 Jan 2025 19:48 GMT

Short Usage Name is not Specified (e.g. Perform action and Perform)

  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    In the graphical BNF the short usage name notations are not specified as well duplicated usage keywords are possible. For these usages, the issues occurs:

    • perform action -> perform;
      • the usage with 'perform' keyword is displayed in Table 9. Parts.
    • exhibit state -> exhibit;
      • exhibit-state-name-compartment = '«exhibit-state»' state-name-compartment - as well based on the specification the keywords could be «exhibit-state» «state», as the state-name-compartment is used.
    • assert constraint -> constraint
      • assert-constraint-name-compartment = '«assert constraint»' constraint-name-compartment - as well based on the specification the keywords could be «assert constraint» «constraint», as the constraint-name-compartment is used.
      • the same issue could be for require constraint and assume constraint but they are not specified as a node shape in the 8.2.3.19 Constraints Graphical Notation section.
    • satisfy requirement -> satisfy
      • the usage with satisfy keyword is displayed in Table 19. Requirements
      • satisfy-requirement-name-compartment = '«satisfy requirement»' requirement-name-compartment - as well based on the specification the keywords could be «satisfy requirement» «requirement», as the requirement-name-compartment is used.
    • the same issue could be for frame concern but it is not specified as a node shape in the 8.2.3.20 Requirements Graphical Notation section.
    • include use case -> include
      • include-use-case-name-compartment = '«include use case»' requirement-name-compartment - as well based on the specification the keywords could be «include use case» «requirement», as the requirement-name-compartment is used.
  • Reported: SysML 2.0b2 — Wed, 18 Dec 2024 09:30 GMT
  • Updated: Sat, 11 Jan 2025 19:47 GMT

Issues with the 'Swimlane' Element Specification

  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    The Swimlane element is described in the specification as containing two elements: Usage-name-compartment and action-flow-node. However, several issues arise with this definition:
    The issues regarding the Swimlane:

    1. The Usage-name-compartment is not specified.
      • The specification does not provide any details or clarification for the Usage-name-compartment element, leaving its definition ambiguous.
    2. Incomplete action-flow-node Definition
      • The definition of action-flow-node excludes relationships and action usages.
      • It currently includes only the following:
        action-flow-node =
         start-node
         | done-node
         | fork-node
         | join-node
         | decision-node
         | merge-node
         | send-action-node
         | accept-action-node
         | while-loop-action-node
         | for-loop-action-node
         | if-else-action-node
         | assign-action-node
        
    3. Missing Compartment Declaration in Swimlane Specification
      • Examples in Table 14. Actions - Representative Notation display a compartment named perform actions within the Swimlane.
      • The specification, however, does not declare that such a compartment can be displayed, leading to inconsistency
  • Reported: SysML 2.0b2 — Wed, 18 Dec 2024 11:29 GMT
  • Updated: Sat, 11 Jan 2025 19:43 GMT

Additional Properties are missing for few Usages

  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    Additional properties that are specified under UsagePrefix/OccurrencePrefix element are missing for these usages inside the «» :

    • timeslices.
    • snapshot.
    • calculation usage - changes that were described in SYSML2_-197 ticket were not done - the old occurence-name-prefix and ref are not removed.
    • item usage - changes that were described in SYSML2_-197 ticket were not done - the old basic-name-prefix and ref are not removed.
  • Reported: SysML 2.0b2 — Wed, 18 Dec 2024 11:58 GMT
  • Updated: Sat, 11 Jan 2025 19:40 GMT

Compartment Name for Action in States is not Correct