OMG System Modeling Language Avatar
  1. OMG Specification

OMG System Modeling Language — Open Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
SYSML2_-173 Flow connections are incorrectly both structure and behavior SysML 2.0b1 open
SYSML2_-311 Fix errors in resolution of issue SYSML2_-203 (InitialState mapping) SysML 2.0b2 open
SYSML2_-304 Diagram frame production not properly integrated into graphical BNF SysML 2.0b2 open
SYSML2_-382 Subclause 7.7.5.3.7 Trigger_Mapping is empty SysML 2.0b2 open
SYSML2_-366 No else branch for a decision node SysML 2.0b2 open
SYSML2_-224 State machine graphical notation for entry/exit/do actions inconsistent 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_-385 The operation RICOAOutputPin_Mapping::filter() should redefine Pin_Mapping::filter() SysML 2.0b2 open
SYSML2_-323 There is no production for general-view SysML 2.0b2 open
SYSML2_-372 ValuePin_Mapping is not correctly specified SysML 2.0b2 open
SYSML2_-378 Entry, do and exit actions compartment should be named "state actions" SysML 2.0b2 open
SYSML2_-362 Alignment of selected graphical symbols in states and actions. SysML 2.0b2 open
SYSML2_-370 Mapping class description AEAChangeParameterFeatureMembership_Mapping is missing SysML 2.0b2 open
SYSML2_-351 Incorrect graphical notation for parameters with nested items in example "Flow as Node" SysML 2.0b2 open
SYSML2_-15 Graphical BNF production proxy should be contextualized SysML 2.0a1 open
SYSML2_-389 Incorrect graphical BNF production item-name-compartment SysML 2.0b2 open
SYSML2_-14 Graphical BNF production sq-ev-occurrence has inconsistent proxy notation SysML 2.0a1 open
SYSML2_-367 Mistakes in various occurrence examples SysML 2.0b2 open
SYSML2_-405 Messages cannot have explicit flow connection definitions SysML 2.0b2 open
SYSML2_-379 Incorrect graphical notation of nested items in item parameter SysML 2.0b2 open
SYSML2_-392 TestCaseVerifyObjectiveRequirementUsage_Mapping has no general mapping SysML 2.0b2 open
SYSML2_-294 Send action examples in representative notation tables wrong SysML 2.0b2 open
SYSML2_-27 Missing graphical notation for Flows Compartment SysML 2.0a1 open
SYSML2_-260 Accept action in representative notation tables is confusing and needs cleanup SysML 2.0b2 open
SYSML2_-268 Incorrect declaration of parameters on actions SysML 2.0b2 open
SYSML2_-394 deriveItemUsageItemDefinition is incorrect SysML 2.0b2 open
SYSML2_-159 Textual notation for send actions is too limited SysML 2.0b1 open
SYSML2_-368 Graphical notation examples violate GBNF and contain typo SysML 2.0b2 open
SYSML2_-354 Not possible to show inherited symbol in name compartment SysML 2.0b2 open
SYSML2_-407 Language description of messages is incorrect SysML 2.0b2 open
SYSML2_-414 flow-label definition cut short SysML 2.0b2 open
SYSML2_-413 ownedParameterMember should be ownedMemberParameter 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_-411 Accept after guard causes errors in IDE SysML 2.0b2 open
SYSML2_-410 Definitions of View Usage are Too Restricted SysML 2.0b2 open
SYSML2_-409 Notation should be more formally tied with Abstract Syntax SysML 2.0b2 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_-359 SysMLv2 Metadata Annotation Capabilities do Not Hide enough Implementation Details in Textual Representation 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_-364 Syntactic Sugar Notation to Define Payload for Flow Def 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_-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_-44 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 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_-4 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 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_-286 Misspelling in Table 16 / graphical and textual notation do not match 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_-245 Multiple vs Single Trigger/Guard/Effect for State Transitions Contradiction SysML 2.0b2 open
SYSML17-650 Directed Composition SysML 1.6 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_-349 Inconsistent compartment labels SysML 2.0b2 open
SYSML2_-232 two haves SysML 2.0b1 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_-320 Specification lacks precision in multiple sentences that begin with the word 'however' SysML 2.0b2 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_-150 OccurrenceUsage missing portioningFeature SysML 2.0b1 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_-111 Mapping of ObjectFlows with ForkNodes SysML 2.0b1 open
SYSML2_-23 Missing graphical notation for n-ary connection def and usage SysML 2.0a1 open
SYSML2_-302 Chapter Trigger_Mapping is empty SysML 2.0b2 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_-263 There is no checkSatisfyRequirementUsageSpecialization constraint SysML 2.0b2 open
SYSML2_-265 Missing semantic constraints related to features of Part SysML 2.0b2 open
SYSML2_-264 Interface usage cannot redefine inherited attributes in textual syntax SysML 2.0b2 open
SYSML2_-126 Decision/MergeNode SuccessionSpecialization checks missing some constraints SysML 2.0b1 open
SYSML2_-254 No way to expose non-membership and non-namespace elements SysML 2.0b2 open
SYSML2_-256 Inconsistent compartment labels 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_-158 timeslice/snapshot featuring types required to specialize or be same as types SysML 2.0a1 open
SYSML2_-39 Semantics of transfers across interfaces SysML 2.0a1 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_-246 Ordering of guards and accepts in transitions is inconsistent SysML 2.0b2 open
SYSML2_-248 Evaluation problem with TradeStudyObjectives 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_-233 Table 6 Duplicate Row Titles SysML 2.0b1 open
SYSML2_-234 Table 16 has misspelling issue SysML 2.0b1 open
SYSML2_-235 Table 16 Graphical Notation does not match Textual Notation SysML 2.0b1 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_-239 Missing Element Import Alias SysML 2.0b2 open
SYSML2_-240 ShapeItems have radius feature bound SysML 2.0b2 open
SYSML2_-76 Transformation does not cover SysMLv1::FlowProperty SysML 2.0a1 open
SYSML2_-229 Invalid values can be assigned to an enum SysML 2.0b2 open
SYSML2_-40 Port transfer semantics SysML 2.0a1 open
SYSML2_-226 Description and examples for message notation are wrong 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_-179 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-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_-174 Enumerations not specializable SysML 2.0b1 open
SYSML2_-175 PortUsage direction SysML 2.0b1 open
SYSML2_-172 Transformation fails on Enumerations that are ValueTypes SysML 2.0a1 open
SYSML2_-176 Proxy nodes are missing from states SysML 2.0a1 open
SYSML2-588 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship is not reliable SysML 2.0a1 open
SYSML2-589 SatisfyReferenceUsageFeatureTyping_Mapping::type() is wrong SysML 2.0a1 open
SYSML2-586 Literal factories are missing operation for their value SysML 2.0a1 open
SYSML2-590 Helper::getScalarValueType operation is not robust enough SysML 2.0a1 open
SYSML2_-168 Literal factories are missing operation for their value 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-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_-166 Default multiplicities are not managed correctly SysML 2.0a1 open
SYSML2_-167 Factories specified for Literal specification shall be optimized SysML 2.0a1 open
SYSML2_-163 ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationship() is wrong SysML 2.0a1 open
SYSML2_-164 Add a distinguished attribute to capture the textual body of a requirement SysML 2.0b1 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_-160 OpaqueBehavior shall be transformed even if they are not owned by a Package SysML 2.0a1 open
SYSML2_-161 Properties typed by Actors SysML 2.0a1 open
SYSML2-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_-157 Namespace_Mapping shall redefine ownedRelationship() SysML 2.0a1 open
SYSML2_-156 Relationship_Mapping::ownedRelatedElement() is wrong SysML 2.0a1 open
SYSML2_-154 GenericToElement_Mapping is missing default rules SysML 2.0a1 open
SYSML2_-153 GenericToStateUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2-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_-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_-152 GenericToRequirementUsage_Mapping is missing a default rule SysML 2.0a1 open
SYSML2_-149 Control nodes missing from concrete syntax for states 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_-143 Missalignment between interface graphical production and notation table SysML 2.0a1 open
SYSML2_-145 Incorrect definition elements in interconnection-element SysML 2.0b1 open
SYSML2_-146 Clarify bolding of keywords in concrete graphical syntax SysML 2.0a1 open
SYSML2-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_-141 AssociationClass_Mapping is uncomplete SysML 2.0b1 open
SYSML2_-140 Initializer classes have to be rationalized 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_-137 Optional language for documentation SysML 2.0b1 open
SYSML2_-138 ConcernOwningMemberships_Mapping and ConcernDocumentation_Mapping are useless SysML 2.0b1 open
SYSML2_-135 element-node not defined SysML 2.0a1 open
SYSML2-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_-133 Fork/JoinNode succession "other" end multiplicity validations missing SysML 2.0b1 open
SYSML2_-131 ChangeEvent 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_-132 TimeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2_-134 Missing production for n-ary connection definition graphical SysML 2.0a1 open
SYSML2_-130 ConstraintProperty should be mapped to a AssertConstraintUsage 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_-128 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2_-124 Feature modifiers missing in Portion Membership examples SysML 2.0b1 open
SYSML2_-125 Representative example "Package with members" to be improved SysML 2.0b1 open
SYSML2_-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_-122 Incomplete example "Individual Occurrence" SysML 2.0b1 open
SYSML2_-120 Package import wildcard is missing SysML 2.0b1 open
SYSML2_-121 Representative notation for filtered package import missing SysML 2.0b1 open
SYSML2_-119 Wrong imported package notation SysML 2.0b1 open
SYSML2_-123 Feature modefiers missing in Feature Membership examples 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_-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-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_-108 Various constraints need to take feature chaining into account SysML 2.0b1 open
SYSML2_-109 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_-110 Transformation does not cover the mapping of Unit and QuantityKind SysML 2.0b1 open
SYSML2_-107 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2-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_-104 Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet SysML 2.0a1 open
SYSML2_-102 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 open
SYSML2_-100 Transformation does not cover UML4SysML::SignalEvent 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_-97 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2_-98 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2_-96 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2_-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_-95 ConstraintBlock mapping parameters to input attributes SysML 2.0a1 open
SYSML2_-93 Assignment action usages do not specify when their expressions are evaluated SysML 2.0a1 open
SYSML2_-91 Machine readable project interchange file(s) for language description examples SysML 2.0a1 open
SYSML2_-94 Some package-level features are mandatory SysML 2.0a1 open
SYSML2_-92 XMI and JSON for example model 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_-89 Accepters on transition usages from entry actions SysML 2.0a1 open
SYSML2_-87 Transformation does not cover SysMLv1::Overwrite SysML 2.0a1 open
SYSML2_-90 Subject of an include use case usage SysML 2.0a1 open
SYSML2_-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_-84 Transformation does not cover SysMLv1::EndPathMultiplicity SysML 2.0a1 open
SYSML2_-82 Transformation does not cover SysMLv1::BoundReference 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_-85 Transformation does not cover SysMLv1::PropertySpecificType 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_-78 Transformation does not cover SysMLv1::View SysML 2.0a1 open
SYSML2_-79 Transformation does not cover SysMLv1::Conform 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_-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_-72 Transformation does not cover UML4SysML::UnmarshallAction 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-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_-71 Transformation does not cover UML4SysML::LinkEndData 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_-68 Transformation does not cover UML4SysML::ConditionalNode SysML 2.0a1 open
SYSML2_-69 Transformation does not cover UML4SysML::LinkEndCreationData SysML 2.0a1 open
SYSML2_-66 Transformation does not cover UML4SysML::ActivityPartition 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_-64 Transformation does not cover UML4SysML::OccurrenceSpecification SysML 2.0a1 open
SYSML2_-65 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2_-63 Transformation does not cover UML4SysML::Gate 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_-61 Transformation does not cover UML4SysML::ConsiderIgnoreFragment SysML 2.0a1 open
SYSML2_-58 Transformation does not cover UML4SysML::Continuation 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-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_-56 Transformation does not cover UML4SysML::Image SysML 2.0a1 open
SYSML2_-55 Transformation does not cover UML4SysML::Interval SysML 2.0a1 open
SYSML2_-53 Transformation does not cover UML4SysML::DurationInterval SysML 2.0a1 open
SYSML2_-57 Transformation does not cover UML4SysML::DestructionOccurrenceSpecification 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_-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_-50 Transformation does not cover UML4SysML::IntervalConstraint 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_-45 Transformation does not cover UML4SysML::Extend SysML 2.0a1 open
SYSML2_-43 Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete SysML 2.0a1 open
SYSML2_-47 Transformation does not cover UML4SysML::DurationConstraint 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_-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_-35 Add standard domain libraries for mathematical and physical constants 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-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_-30 Graphical notation for variant inheritance from variation requires improvement SysML 2.0a1 open
SYSML2_-33 Extend ISQ with missing quantity and unit types for US Customary Units SysML 2.0a1 open
SYSML2_-32 Resolve "TODO" in domain library model Time 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_-28 Graphical BNF defines lifeline elements incorrectly 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_-24 Port symbol notation (arrows) needs improvement SysML 2.0a1 open
SYSML2_-22 Quantity and unit for ratio and fraction SysML 2.0a1 open
SYSML2_-21 Parameter symbol notation needs improvement SysML 2.0a1 open
SYSML2-51 Loop examples incomplete in representative notation table SysML 2.0a1 open
SYSML2-49 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2-48 Consider production for standard case view vs filtered general view SysML 2.0a1 open
SYSML2-50 No support for metadata in graphical notation SysML 2.0a1 open
SYSML2-41 Graphical BNF production proxy refers to wrong label SysML 2.0a1 open
SYSML2-52 Examples requirement derivation, cause effect, and refinement missing SysML 2.0a1 open
SYSML2_-17 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2_-20 Examples requirement derivation, cause effect, and refinement missing SysML 2.0a1 open
SYSML2_-19 Loop examples incomplete in representative notation table SysML 2.0a1 open
SYSML2_-16 Consider production for standard case view vs filtered general view 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_-12 Regularization of textual notation for loops SysML 2.0a1 open
SYSML2_-13 Identify the owning context in a graphical view SysML 2.0a1 open
SYSML2-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_-8 Clarify query using view SysML 2.0a1 open
SYSML2_-9 Identify impact views on model organization SysML 2.0a1 open
SYSML2_-7 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2_-10 Missing graphical notation allocating flow to connection SysML 2.0a1 open
SYSML2-17 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 open
SYSML2-25 Standard view filters incomplete SysML 2.0a1 open
SYSML2-18 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered SysML 2.0a1 open
SYSML2_-5 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered SysML 2.0a1 open
SYSML2_-6 Standard view filters incomplete SysML 2.0a1 open
KERML-245 KerML should have syntax for enumerations SysML 2.0b1 open
KERML_-53 KerML should have syntax for enumerations SysML 2.0b1 open
SYSML2-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
SYSML17-649 Metadata - category refers to DCMI abstract (not a category) / dublinCoreTag. Dublin Core Should Only Apply to Artefacts (Documents, Sound, Video, Text) Not any AD Element SysML 1.5 open
SYSML17-648 Metadata, ArchitectureMetadata Incorrect - Metadata Applies to Architecture Description Not Architecture. ArchitectureMetadata duplicates Metadata in application to an AD SysML 1.5 open
SYSML17-647 View Specifications::Summary & Overview::Summary & Overview - Missing Relationships and Triples, Concerns Not Defined SysML 1.5 open
SYSML17-646 UAFElement - Attributes Missing. URI incorrectly defined SysML 1.5 open
SYSML17-645 Figure 9:134 / 8:86 Undefined DMM Elements - Refine, Trace, Refine, Verifiy, Requirement. Requirement not a UAF Element? SysML 1.5 open
SYSML17-644 Figure 9:129 ArchitecturalDescription - Multiplicities Incorrect SysML 1.5 open
SYSML17-643 Figure 8:2 Architecture Views Does Not Conform to ISO/IEC/IEEE 42010 - Multiplicities, Naming, Direction [repeat - Tracker Now Using Correct OMG Identifiers] SysML 1.5 open
SYSML17-642 Figure 8:2 Architecture Views Does Not Conform to ISO/IEC/IEEE 42010 - Multiplicities, Naming, Direction SysML 1.5 open
SYSML17-641 1.1 Introduction - Normative + Informative Identifies Wrong OMG Specifications SysML 1.5 open
SYSML17-640 Typo in brief description about Activity Diagram SysML 1.6 open
SYSML17-639 Element Name Incorrectly Shown as InternalBlockDiagram - Should be Dependency SysML 1.6 open
SYSML17-636 Conform as a Generalization is Incorrect - A View is Not a Viewpoint / 'is a' Does Not Equate to Conform SysML 1.5 open
SYSML17-637 View is not a Viewpoint SysML 1.5 open
SYSML17-500 Artifacts and «document» SysML 1.6 open
SYSML17-638 UML::Artifact is Excluded But Specification Doesn't State With What Documents/Artifacts Are to Be Represented with Instead SysML 1.7b1 open
SYSML17-635 Risk, Source and Verification Method Are Attributes of Any / All Requirements Not Just an Extended Requirement SysML 1.5 open
SYSML17-634 Issues with SysML 1.7 XMI SysML 1.6 open
SYSML17-536 Typo: Constraint name 8 of Adjunct Property (again) SysML 1.6 open
SYSML17-515 Statement about UML semantics of ActivityPartitions is wrong SysML 1.6 open
SYSML17-494 wrong statement about UML semantics of partitions SysML 1.6 open
SYSML17-463 QUDV: Specification of PrefixedUnit should have a QuantityKind SysML 1.6 open
SYSML17-512 Added BehavioralFeatures to AdjuctProperty SysML 1.6 open
SYSML17-365 Meta-ticket: SysML-1.6: Specification body (only) figure inconsistencies and errors and related text inconsistencies SysML 1.6 open
SYSML17-252 ConstraintBlock: abstract syntax consistency SysML 1.6 open
SYSML17-507 wrong name on Figure 9-6 SysML 1.6 open
SYSML17-504 Why are FlowProperties not included in FlowDirectionKind SysML 1.6 open
SYSML17-505 The FeatureDirectionKind to which the constraint belongs is wrong SysML 1.6 open
SYSML17-502 FlowProperties as aggregations SysML 1.6 open
SYSML17-498 NoBuffer: Clarify when a token is considered "refused" SysML 1.6 open
SYSML17-233 Comments in the XMI have no annotated elements SysML 1.6b1 open
SYSML17-265 Stereotype Rate extends ObjectNode in the XMI, but not in the abstract syntax in the specification SysML 1.6 open
SYSML17-490 no longer existing "primaryQuantityKind" shown in diagram E.8 SysML 1.6 open
SYSML17-489 Removes references to UML4SYSML from the SysML diagrams SysML 1.6 open
SYSML17-485 Mentioned stereotype «distributedDefinition» does not exist SysML 1.6 open
SYSML17-488 FinalState should be an exitPoint Pseudostate SysML 1.6 open
SYSML17-487 connector properties should be in compartment SysML 1.6 open
SYSML17-486 Behavioral Ports and Nesting SysML 1.6 open
SYSML17-483 DistributedProperty definition has to be reveiwed SysML 1.6 open
SYSML17-482 The circle plus notation is for members, not ownedElements SysML 1.6 open
SYSML17-481 Consistency with Effects and Ports SysML 1.6 open
SYSML17-479 Association Rules SysML 1.6 open
SYSML17-227 About Block constraint "3" removed by SysML v1.6 SysML 1.6 open
SYSML17-480 Problems with Flows SysML 1.6 open
SYSML17-478 AcceptChangeStructuralFeatureEventAction SysML 1.6 open
SYSML17-467 Implementation of non-normative extensions cannot be used in other OMG specifications SysML 1.6 open
SYSML17-475 move to SystemOfQuantities SysML 1.6 open
SYSML17-474 rename getKindOfQuantitiesForMeasurementUnit SysML 1.6 open
SYSML17-473 OCL is not syntatically correct see ->allUnits() SysML 1.6 open
SYSML17-472 wrongfully copied SysML 1.6 open
SYSML17-471 OCL with SpecializedQuantityKind needs to be changed SysML 1.6 open
SYSML17-469 ControlValue to ControlValueKind SysML 1.6 open
SYSML17-468 Changes to Annex D sample problem figures may impact on some specification body figures SysML 1.6 open
SYSML17-366 Need constraint for inverted provided/required Interfaces (InterfaceRealization and Usage) on ~InterfaceBlock SysML 1.6 open
SYSML17-464 Constraint Typos SysML 1.6 open
SYSML17-454 QUDV: Unknown property primaryQuantityKind SysML 1.6 open
SYSML17-462 SysML model URI in the specification document SysML 1.6 open
SYSML17-455 Suggest capability to list :features on Pin symbols and on elided Pin "ObjectNode" rectangle symbol SysML 1.6 open
SYSML17-456 Suggest capability to list :features on ItemFlows in a rectangle symbol over a Connector or Association line SysML 1.6 open
SYSML17-357 Suggest introduce strict diagram policy: avoid "elided Pin" ObjectNode notation in Activity Diagrams in all revised and future specification figures SysML 1.6 open
SYSML17-438 Body conditions of operation in QUDV model should be Boolean expressions SysML 1.6 open
SYSML17-437 QUDV::PrefixedUnit: Redefinition of quantityKind SysML 1.6 open
SYSML17-430 Issues in figure E-7 SysML 1.6 open
SYSML17-414 7_composition_acyclic wrong SysML 1.6 open
SYSML17-351 If there is no «port» keyword in UML-2.5.1 or SysML-1.6 it should be removed from Figure 9-8 SysML 1.6 open
SYSML17-408 orderedMember in ElementGroup should be {ordered} SysML 1.6 open
SYSML17-406 AbstractRequirement needs to be consistent SysML 1.6 open
SYSML17-405 Description for getSatisfies SysML 1.6 open
SYSML17-404 Parameter names mismatch in ~InterfaceBlock::areConjugated(Property, Property) SysML 1.6 open
SYSML17-401 Suggest introduce an operation to obtain the magnitude of a value property in a given compatible Unit (to afford equality comparison) SysML 1.6 open
SYSML17-399 Taken literally the text and OCL of constraint '6_valueproperties_composite' imply that every FlowProperty typed by a ValueType should have AggregationKind 'composite' SysML 1.6 open
SYSML17-400 Property types 'Four general categories of properties of blocks are recognized in SysML ...' does not cover FlowProperty SysML 1.6 open
SYSML17-367 InterfaceBlock: OCL constraint 2_no_part is missing FlowProperty check for cases where a FlowProperty is not typed by a ValueType SysML 1.6 open
SYSML17-395 Compartments for Connectors and Participants SysML 1.6 open
SYSML17-394 Suggest not allow an AssociationBlock to type a BindingConnector used for pure proxying SysML 1.6 open
SYSML17-386 All kinds of errors in Fig. 8-17 SysML 1.6 open
SYSML17-348 Figure 8-17: Vehicle specialization: multiple inconsistencies SysML 1.6 open
SYSML17-388 constraint needed SysML 1.6 open
SYSML17-393 Relationship should be specified for Stakeholder to a View SysML 1.6 open
SYSML17-392 Adjunct allows for additional notation on CallBehaviorActions SysML 1.6 open
SYSML17-391 What are redefined BoundReferences SysML 1.6 open
SYSML17-390 EndPathMultiplicity and BoundReference Ordered and Unique SysML 1.6 open
SYSML17-389 Lower and Upper Explained SysML 1.6 open
SYSML17-387 Lower and Upper are constrained SysML 1.6 open
SYSML17-385 Statement about EndPathMultiplicity SysML 1.6 open
SYSML17-384 BoundReference Specificity SysML 1.6 open
SYSML17-383 BoundReference Diagram is wrong SysML 1.6 open
SYSML17-382 Unclear English Statement SysML 1.6 open
SYSML17-377 Make Annex E Optional but Normative SysML 1.6 open
SYSML17-372 Figure E.6 QUDV Units Diagram display exactly the same content as Figure E.5 QUDV Concepts Diagram SysML 1.6 open
SYSML17-347 The 'initialValues' compartment needs to be renamed 'contextValues' and they need to be referred to as 'context-specific values' SysML 1.6 open
SYSML17-371 Suggest primary/replica as alternative to master/slave terminology for Copy relationship SysML 1.6 open
SYSML17-370 SysML-1.6: Refers to both 'composite requirement' and 'compound requirement' SysML 1.6 open
SYSML17-369 BindingConnector constraint 1_compatible_types: Use of OCL conformsTo contradicts definition of compatibility of connected ProxyPort, does not admit per Feature compatibility or compatibility via a union of connected features SysML 1.6 open
SYSML17-368 9.3.2.13 ProxyPort 'When a proxy port is connected to a single internal part ...' extend to include ' or port on an internal part' SysML 1.6 open
SYSML17-361 SysML-1.6: text on Requirement 'Test and procedure conditions' is mangled in 'Figure 16-2: Requirements Derivation' (was OK in SysML-1.5) [also affects Figure 16-6] SysML 1.6 open
SYSML17-362 'Figure 16-2: Requirements Derivation' indeed shows DeriveReqt but spec text refers to it as 'an example of a compound requirement' SysML 1.6 open
SYSML17-349 'Figure 9-6: Usage example of ports with provided and required features' does not expose any directed features SysML 1.6 open
SYSML17-350 SysML-1.6 does not leverage redefinition of 'sp:Surface' on 'Figure 9-7: Usage example of proxy and full ports'. And does not show direction of flows on Ports symbols SysML 1.6 open
SYSML17-352 Figure 9-16 and Figure 9-17 'Usage example of item flow decomposition': multiple inconsistencies SysML 1.6 open
SYSML17-353 The ControlValue input to Monitor Traction without a Pin is invalid in 'Figure 11-10: Continuous system example 1' and multiple issues with ControlOperator SysML 1.6 open
SYSML17-354 Edge for [else] in 'Figure 11-11: Continuous system example 2' should be an ObjectFlow not a ControlFlow SysML 1.6 open
SYSML17-364 Suggest additional main body figure illustrating context-specific values (initialValues) compartment used for deep system configuration SysML 1.6 open
SYSML17-329 Inconsistent incoming ObjectFlow and outgoing ControlFlows on the DecisionNode in Figure 11.12 - Continuous system example 3 'Enable on Brake Pressure > 0' SysML 1.6 open
SYSML17-356 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not allocate to a FlowProperty and multiple other minor issues SysML 1.6 open
SYSML17-360 Fig D.41 should be bdd with instance specs & slot values, not ibd with default values SysML 1.6 open
SYSML17-363 SysML-1.6: DeriveReqt: OCL constraint directions client vs supplier SysML 1.6 open
SYSML17-358 Trivial: consistency: Either show the [metaclass] on all Stereotype symbols or none in 'Figure 16-1: Abstract Syntax for Requirements Stereotypes' SysML 1.6 open
SYSML17-339 Figure D.24 Parametric Diagram does not explicitly show «equal» keyword or '=' on BindingConnectors SysML 1.6 open
SYSML17-344 Typo: 'not' should be 'nor' in '... not is this always even desirable' SysML 1.6 open
SYSML17-343 Typo: references to FuelTankAssy should be FuelTankAssembly for consistency with Figure D.25 SysML 1.6 open
SYSML17-334 Typo: 'Various other model elements may be necessary to help develop a derived requirement, and these model element' plural missing SysML 1.6 open
SYSML17-336 Typo: Missing end parentheses bracket: '(described in D.4.3 Elaborating Behavior (Sequence and State Machine Diagrams)' SysML 1.6 open
SYSML17-330 Typo: 'with is owned by the AutomotiveDomain block.' SysML 1.6 open
SYSML17-342 Need Connector from fuel:Fuel to :FuelPump in 'Figure D.25 Detailed Internal Structure of Fuel Delivery Subsystem (Internal Block Diagram)' SysML 1.6 open
SYSML17-341 Naming inconsistencies 'Figure D.24 is a parametric diagram showing how fuel flowrate is related to FuelDemand and FuelPressure value properties.' SysML 1.6 open
SYSML17-338 Figure D.23 has FuelFlow stereotyped by the DEPRECATED «flowSpecification» SysML 1.6 open
SYSML17-332 'Figure D.7 - Elaborating Black Box Behavior' some OCL missing, State names in oclInState() should be capital first letter, and display of name of alt fragment SysML 1.6 open
SYSML17-345 SysML-1.6: Figure D.25 has the type Fuel for both an in Port and an out Port on FuelTankAssembly (and it is not ideal to have same name as the Classifier that flows) SysML 1.6 open
SYSML17-346 7.3.2.3 Expose refers to 'The method' without referencing Viewpoint SysML 1.6 open
SYSML17-340 Typo: 'Binding connectors, as defined in Clause 8 are used ...' missing comma SysML 1.6 open
SYSML17-333 Typo: 'Deleting the container requirement deleted the nested requirements, a functionality inherited from UML.' should be 'deletes' SysML 1.6 open
SYSML17-337 Typo: 9.3.2.8 FlowProperty 'A flow propertys values' SysML 1.6 open
SYSML17-335 For Connectors in IBD Figure D.4 to be typed by implied anonymous Associations need define them in BDD Figure D.15 between 'HybridSUV' and: 'Driver', 'Maintainer', 'Passenger', 'Baggage', 'Environment' SysML 1.6 open
SYSML17-331 In Figure D.2 Real appears to be owned by the Automotive Value Types ModelLibrary (with no explicit ElementImport) SysML 1.6 open
SYSML17-307 Lots of ControlValues that should be ControlValueKinds SysML 1.6 open
SYSML17-319 It should not be allowed to modify an AdjunctProperty SysML 1.6 open
SYSML17-316 Duplicated sentence SysML 1.6 open
SYSML17-315 Unexpected word 'Figure' in Figure 4-2 name SysML 1.6 open
SYSML17-314 Unexpected section number SysML 1.6 open
SYSML17-313 Clarify that contraint parameters are value properties SysML 1.6 open
SYSML17-308 7_cannot_redefine_boundreference is too constrained SysML 1.6 open
SYSML17-306 Aggregation multiplicities not correct SysML 1.6 open
SYSML17-300 SysML 1.6 statement is too strong SysML 1.6 open
SYSML17-299 Caveat is not specific for UseCases SysML 1.6 open
SYSML17-293 Introduction to 9.1.3 Proxy Ports and Full Ports might be interpreted as SysML only permitting Full and Proxy Ports (not standard ports) SysML 1.6 open
SYSML17-298 Continuous and Discrete need to be on FlowProperties as well SysML 1.6 open
SYSML17-296 No Creation and Destruction Event in Current UML SysML 1.6 open
SYSML17-295 Figure 9.5 missing, duplicates 9.4 SysML 1.6 open
SYSML17-290 Remove reference to non-existing properties allocatedFrom and allocatedTo SysML 1.6 open
SYSML17-286 Remove notation form ActorPart SysML 1.6 open
SYSML17-284 Conjugation Stereotype SysML 1.6 open
SYSML17-285 is the stereotype <<~InterfaceBlock>> SysML 1.6 open
SYSML17-283 Need Bound References Compartment SysML 1.6 open
SYSML17-274 Parameters and Variables don't make sense SysML 1.6 open
SYSML17-248 The definition of AdjunctProperty SysML 1.6 open
SYSML17-234 QUDV library inconsistently uses SysML::Libraries::PrimitiveValueTypes SysML 1.6b1 open
SYSML17-278 AbstractRequirement: direction of /tracedTo wrong in Attributes description SysML 1.6 open
SYSML17-277 Description of getRefines() has typo and inconsistent singular vs plural SysML 1.6 open
SYSML17-276 Description of getRefines() restricts returned elements to AbstractRequirement [0..*] but the OCL static query does not (effectively NamedElement [0..*]) SysML 1.6 open
SYSML17-275 Parts is too restrictive SysML 1.6 open
SYSML17-273 Missing guard brackets in example activity diagram 11-12 SysML 1.6 open
SYSML17-261 How to interpret non-Navigation SysML 1.6b1 open
SYSML17-258 No changebars in SysML 1.6b1 open
SYSML17-257 Proposal: patent-friendly part/element numbering system with compliant solid line SysML 1.6b1 open
SYSML17-250 Should <> have a capital V? SysML 1.6b1 open
SYSML17-249 Duplicate Elements in Table SysML 1.6b1 open
SYSML17-243 Refine / Trace relationship operations are too restrictive SysML 1.6b1 open
SYSML17-242 VerdictKind should also have the literal none SysML 1.6b1 open
SYSML17-231 ProxyPort property "matching" SysML 1.6 open
SYSML17-229 cannot model and validate physical connections SysML 1.4 open
UMLR-104 Section: Chapter: 7.3.2.4 View SysML 1.0 open
UMLR-140 Section: Activities SysML 1.0 open
UMLR-141 Callout notation for many clients/suppliers SysML 1.0 open

Issues Descriptions

Flow connections are incorrectly both structure and behavior

  • Key: SYSML2_-173
  • 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: Mon, 2 Dec 2024 21:46 GMT

Fix errors in resolution of issue SYSML2_-203 (InitialState mapping)

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

    Unfortunately, a small error has crept into the resolution of SYSML2_-203.

    The mapping class InitialStateMembership_Mapping should be named InitialStateSubactionMembership_Mapping and the general mapping of the mapping class should be GenericToSubactionMembership_Mapping.

    Accordingly, change InitialStateMembership_Mapping in Helper::stateOwnedRelationship() to InitialStateSubactionMembership_Mapping.
  • Reported: SysML 2.0b2 — Sat, 24 Aug 2024 11:29 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

Diagram frame production not properly integrated into graphical BNF

  • Key: SYSML2_-304
  • 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: Mon, 2 Dec 2024 20:17 GMT

Subclause 7.7.5.3.7 Trigger_Mapping is empty

  • Key: SYSML2_-382
  • 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: Mon, 2 Dec 2024 20:17 GMT

No else branch for a decision node

  • Key: SYSML2_-366
  • 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: Mon, 2 Dec 2024 20:17 GMT

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

  • Key: SYSML2_-224
  • 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: Mon, 2 Dec 2024 20:17 GMT

Specification of Helper::getScalarValueType() uses unknown OCL function

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

    The specification of Helper::getScalarValueType() uses the unknown OCL String function includes:

    t.qualifiedName.includes('PrimitiveTypes::UnlimitedNatural')

    To check if a string is part of another string, the function indexOf() should be used instead.

    The issue was accidentally introduced by SYSML2_-300 in ballot #3.
  • Reported: SysML 2.0b2 — Wed, 13 Nov 2024 19:45 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

COAPin_Mapping is not correctly specified

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

    The COAPin_Mapping class should specialize directly or indirectly a mapping class from the mapping framework. Very likely, it should specialize Pin_Mapping.

  • Reported: SysML 2.0b2 — Wed, 13 Nov 2024 14:58 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

The operation RICOAOutputPin_Mapping::filter() should redefine Pin_Mapping::filter()

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

    Operation RICOAOutputPin_Mapping::filter() does not redefine Pin_Mapping::filter(). The issue is not visible in the specification document but in the model resp. XMI.
  • Reported: SysML 2.0b2 — Mon, 18 Nov 2024 17:53 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

There is no production for general-view

  • Key: SYSML2_-323
  • Status: open  
  • Source: sodiuswillert.com ( Mr. Eran Gery)
  • Summary:

    general-view is used but not specified. The definition should probably be 

    general-view = 
    definition-node*  definition-edge * usage-node* usage-edge*

    Also, need to add a production for definition-edge and account for namespace symbols (e.g., packages)
  • Reported: SysML 2.0b2 — Wed, 18 Sep 2024 13:49 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

ValuePin_Mapping is not correctly specified

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

    The ValuePin_Mapping class should specialize directly or indirectly a mapping class from the mapping framework. Very likely, it should specialize Pin_Mapping.

  • Reported: SysML 2.0b2 — Wed, 13 Nov 2024 13:11 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

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

  • Key: SYSML2_-378
  • 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: Mon, 2 Dec 2024 20:17 GMT

Alignment of selected graphical symbols in states and actions.

  • Key: SYSML2_-362
  • 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: Mon, 2 Dec 2024 20:17 GMT
  • Attachments:

Mapping class description AEAChangeParameterFeatureMembership_Mapping is missing

  • Key: SYSML2_-370
  • 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: Mon, 2 Dec 2024 20:17 GMT

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

  • Key: SYSML2_-351
  • 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: Mon, 2 Dec 2024 20:17 GMT
  • Attachments:

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: Mon, 2 Dec 2024 20:17 GMT

Incorrect graphical BNF production item-name-compartment

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

    In subclause 8.2.3.10 the production item-name-compartment is out-of-date. In line with other usage name-compartment productions it should read:

    item-name-compartment =
      '«' OccurrenceUsagePrefix 'item' '»'
      usage-name-with-alias
  • Reported: SysML 2.0b2 — Mon, 18 Nov 2024 23:01 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

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

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

    Currently sq-ev-occurrence is denoted as an "X", which is not used anywhere else. Should it be rather the proxy notation, i.e., a black dot?
  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:28 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

Mistakes in various occurrence examples

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

    In subclause 7.9.1, Table 7, example "Individual Occurrence Definition", in the graphical notation, the name 'OccurenceDef1-1' is an UNRESTRICTED_NAME and should be written between two single quotation marks as it contains a character (the hyphen) outside the valid character set for BASIC_NAME (see KerML clause 8.2.2.3).

    There are also many typos in the spelling of "occurrence":

    • Example "Occurrence Definition": in graphical notation OccurenceDef1 should read OccurrenceDef1.
    • Example "Occurrence": in graphical notation OccurenceDef1 should read OccurrenceDef1.
    • Example "Individual Occurrence Definition": In graphical notation: OccurenceDef should read OccurrenceDef (2x missing r), and in the textual notation: OcurrenceDef should read OccurrenceDef (1x missing c).
    • Example "Individual Occurrence": in graphical notation OccurenceDef1-1 should read OccurrenceDef1-1.
    • Example "Timeslice": in graphical notation OccurenceDef1 should read OccurrenceDef1.
    • Example "Snapshot": in graphical notation OccurenceDef1 should read OccurrenceDef1.
  • Reported: SysML 2.0b2 — Wed, 6 Nov 2024 22:00 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

Messages cannot have explicit flow connection definitions

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

    As for other flow connection usages, the syntax for a message declaration allows for explicit typing by flow connection definitions. However:

    • The constraint checkFlowConnectionDefinitionSpecialization requires that a flow connection definition specialize the base type MessageConnection. MessageConnection has source and target ends that redefines corresponding ends from BinaryConnection and Transfer. So, any flow connection definition must be binary, with exactly two ends, either inherited from or redefining the ends of MessageConnection.
    • The constraint checkFlowConnectionUsageSpecialization requires that a message (with no owned end features) specialize the base feature messageConnections, which also has source and target ends that redefine the corresponding ends from MessageConnection, binaryConnections and transfers.
    • This means that a message declaration with explicit typing by flow connection definitions inherits ends from both the flow connection definitions and its subsetting of messageConnections. Since a message declaration by definition has no owned end features, this cannot be resolve by redefining the inherited end features. The message declaration therefore results in a flow connection usage with more than two ends, which violates the (KerML) constraint validateConnectorBinarySpecialization.
  • Reported: SysML 2.0b2 — Mon, 2 Dec 2024 06:04 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

Incorrect graphical notation of nested items in item parameter

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

    In subclause 7.13.1, Table 11, example "Flow as node" in the «flow» elaboration symbol the subItems of source.item1 and target.item2 are depicted with parameter symbols. This is incorrect because the subItems are undirected features and therefore should be depicted as parameters, but rather as nested items inside the containing item1 and item2 rounded rectangles.
  • Reported: SysML 2.0b2 — Thu, 14 Nov 2024 15:47 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

TestCaseVerifyObjectiveRequirementUsage_Mapping has no general mapping

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

    Each mapping class needs at least one general mapping. There is none defined for TestCaseVerifyObjectiveRequirementUsage_Mapping.
  • Reported: SysML 2.0b2 — Tue, 19 Nov 2024 10:52 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

Send action examples in representative notation tables wrong

  • Key: SYSML2_-294
  • 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: Mon, 2 Dec 2024 20:17 GMT

Missing graphical notation for Flows Compartment

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

    In subclause 7.13.1, Table 15, in example "Flows Compartment" the graphical notation is missing. Graphical notation corresponding to the example expressed in textual notation should be added. Also, the corresponding graphical BNF production for flows-compartment is missing in subclause 8.2.3.13, so that should be added too.
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:55 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

Accept action in representative notation tables is confusing and needs cleanup

  • Key: SYSML2_-260
  • 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: Mon, 2 Dec 2024 20:17 GMT

Incorrect declaration of parameters on actions

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

    In subclause 7.16.1 Table 14 examples "Actions Compartment" and "Perform Actions Compartment" have outdated notation using parentheses for parameter notation in actions compartments.

    It is suggested to remove those parameter declarations.
  • Reported: SysML 2.0b2 — Wed, 31 Jul 2024 14:03 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

deriveItemUsageItemDefinition is incorrect

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

    In 8.3.10.3 ItemUsage, under "Attributes", the type of the attribute itemDefinition is Structure and the attribute description states

    The Structures that are the definitions of this ItemUsage. Nominally, these are ItemDefinitions, but other kinds of Kernel Structures are also allowed, to permit use of Structures from the Kernel Library.

    However, under "Constraints" the constraint deriveItemUsageItemDefinition has the following description and OCL:

    The itemDefinitions of an ItemUsage are those occurrenceDefinitions that are ItemDefinitions. 

    itemDefinition = occurrenceDefinition->selectByKind(ItemDefinition)

    This only allows itemDefinitions that are ItemDefinitions, filtering out all other kinds of Structures.
  • Reported: SysML 2.0b2 — Tue, 19 Nov 2024 23:11 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

Textual notation for send actions is too limited

  • Key: SYSML2_-159
  • 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: Mon, 2 Dec 2024 20:17 GMT

Graphical notation examples violate GBNF and contain typo

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

    In subclause 7.9.1., Table 7, examples "Individual Occurrence" and "Portion Membership" the graphical notations incorrectly show «individual» as a separate keyword in guillemets. In line with the Graphical BNF specification, they should be put together with the main element keyword, i.e. «individual occurrence» and «individual part» respectively.

    The first example also contains a typo: 'OccurenceDef1-1' should read 'OccurrenceDef1-1'. The second contains typo: indvidual1 should read individual1.
  • Reported: SysML 2.0b2 — Wed, 6 Nov 2024 22:11 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

Not possible to show inherited symbol in name compartment

  • Key: SYSML2_-354
  • 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: Mon, 2 Dec 2024 20:17 GMT

Language description of messages is incorrect

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

    In 7.13.6 Flow Connection Usages and Messages, a message declaration is described as identifying the "source and target related features", and the associated example shows a message declared as being between controller and engine parts. This is not correct. Messages are actually declared between source and target events that are within the source and target related features, with the actual ends of the transfer remaining implicit.
  • Reported: SysML 2.0b2 — Mon, 2 Dec 2024 06:55 GMT
  • Updated: Mon, 2 Dec 2024 20:17 GMT

flow-label definition cut short

  • Key: SYSML2_-414
  • 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: Mon, 2 Dec 2024 18:35 GMT

ownedParameterMember should be ownedMemberParameter

  • Key: SYSML2_-413
  • 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: Mon, 2 Dec 2024 18:34 GMT

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

  • Key: SYSML2_-412
  • 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: Mon, 2 Dec 2024 18:33 GMT

Accept after guard causes errors in IDE

  • Key: SYSML2_-411
  • 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: Mon, 2 Dec 2024 18:28 GMT

Definitions of View Usage are Too Restricted

  • Key: SYSML2_-410
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    View usage is restricted to have at most one definition which must be a view definition:
    /viewDefinition : ViewDefinition [0..1]

    {redefines partDefinition}

    With this passage viewDefinition field redefines partDefinition field - this makes constraints on what partDefinition field values can be - namely (at most) one definiition which must be a view definition.

    This is too restrictive and precludes some valid use cases; For example, additional "instrumentation" of the view with additional properties to implement diagram properties
    e.g.:
    part def VendorSpecificDiagramProperties

    { attribute showGrid:Boolean; //other diagram style attributes here }

    //.......
    view usage usersDiagram: InterconnectionView, VendorSpecificDiagramProperties {
    :>>showGrid = true;
    }

    This restriction could be relaxed to e.g. viewDefinition subsetting partDefinition instead of redefining, allowing more flexible use of views (just like partDefinition only subsets itemDefinition).
  • Reported: SysML 2.0b2 — Mon, 18 Nov 2024 08:20 GMT
  • Updated: Mon, 2 Dec 2024 18:28 GMT

Notation should be more formally tied with Abstract Syntax

  • Key: SYSML2_-409
  • 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: Mon, 2 Dec 2024 18:28 GMT

Each FlowConnectionUsage owned by PartUsage subsets 3 features

  • Key: SYSML2_-360
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    In current implementation each FlowConnectionUsage owned by PartUsage subsets (automatically) 3 features:

    1. FlowConnectionUsage::flowConnections
    2. PartUsage::subparts
    3. ActionUsage::ownedActions

    This could be optimized for the sake of model size. Maybe it would be better idea to introduce

        Part::Part::ownedFlows :> ownedActions, subparts, flowConections

    and define something like CheckFlowConnectionSubFlowSpecialization constraint?
  • Reported: SysML 2.0b2 — Mon, 28 Oct 2024 08:27 GMT
  • Updated: Mon, 2 Dec 2024 06:41 GMT

proxy connection points are not contextualized in sequence diagrams

  • Key: SYSML2_-401
  • Status: open  
  • Source: sodiuswillert.com ( Mr. Eran Gery)
  • Summary:

    proxy connection in sequence views should be contextualized on lifelines.
    Right now they just float as nodes.

  • Reported: SysML 2.0b2 — Wed, 27 Nov 2024 11:11 GMT
  • Updated: Wed, 27 Nov 2024 11:11 GMT

SysMLv2 Metadata Annotation Capabilities do Not Hide enough Implementation Details in Textual Representation

  • Key: SYSML2_-359
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    When metadata is defined with keyword textual notation allows short syntax of metadata application with #keyword. Example from the spec:

    occurrence def Situation;
occurrence situations : Situation[0..*] nonunique;
metadata def <situation> SituationMetadata :> SemanticMetadata {
:>> baseType = situations meta SysML::Usage;
}

// batteryLow is an OccurrenceUsage that implicitly subsets situations.
#situation occurrence batteryLow;

    Unfortunately, the end user still needs to know underlying model element flavor (occurrence in the example above). This knowledge is difficult to learn for the users of the particular specialized domain. It could be considered an "implementation detail" of the domain specific modeling provider.

    Ideally, when metadata is defined 1) with keyword 2) with annotatedElement fixed to a single variant, the end user should not need to specify the model element flavor ("metaclass") in the textual notation and just state the keyword; like this:

    #situation batteryLow;

    This would be very handy for UAF and other domains.
  • Reported: SysML 2.0b2 — Mon, 28 Oct 2024 07:58 GMT
  • Updated: Mon, 25 Nov 2024 09:09 GMT

Flow Connection Payload modeling - Different models created for definition through sytactic sugar vs fully expanded definition

  • Key: SYSML2_-363
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    It is possible to define flow connection usage in several ways.

    One - use the simple/nice notation where syntactic sugar hides the underlying complexity:

       flow of SomeItemDefinition from firstEndCon to secondEndCon;

    Second- use full available detailed notation allowing precise definition of the characteristics of the payload

       flow {
      :>>payload: SomeItemDef; //note more characteristics for payload can be modeled here - especially useful when flows are inherited
      end ::> firstEndCon;
      end ::> secondEndCon;
   }

    Sometimes the second, detailed way is the only way to define characteristics of the payload in the more complex cases (especially when the flows are inherited/specialized in the hierarcy).

    Now the problem is that two different models are created for these two cases. ItemFeature is created for the first/nice/short case while simple ReferenceUsage is created for the full/complete case.

    It seems that ItemFeature (meta)type is mostly a syntactic marker. So perhaps it would be possible to get rid of it entirely and make the two cases equivalent from the abstract syntax/model standpoint?

    This non-uniformity causes several technical problems down the line.

    • It does not allow to have other kind of features (for example ReferenceUsage in SysML) as item features on FlowConnections. ReferenceUsage is not inherited from ItemFeature
    • ItemFlow::itemFeature derived property returns only owned flow item feature, but in practice actual (owned or inherited) one should be returned.

    The second problem could perhaps be solved by e.g. changing the definition of the itemFeature property in the abstract syntax to be the feature that specializes `Transfer::item`, whether or not it is owned or inherited, and whether or not it is an ItemFeature. The derivation would not be as simple as the current one, but it would be a reasonable suggestion.
  • Reported: SysML 2.0b2 — Mon, 4 Nov 2024 07:26 GMT
  • Updated: Sun, 24 Nov 2024 04:44 GMT

Syntactic Sugar Notation to Define Payload for Flow Def

  • Key: SYSML2_-364
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    Currently, the only way to create payload for flow def is to redefine it explicitly:

    flow def SomeFD {
   :>>payload: SomeData;
   end :FirstEndType;
   end :SecondEndType;
}

    it would be nice for the same syntactic sugar "of TypeOfPayload" to be available for flow defs as is now available for flow usages:

    flow def SomeFD  of SomeData {
   end :FirstEndType;
   end :SecondEndType;
}
  • Reported: SysML 2.0b2 — Mon, 4 Nov 2024 08:13 GMT
  • Updated: Sun, 24 Nov 2024 04:41 GMT

Flow Connection End modeling - Different models created for definition through sytactic sugar vs fully expanded definition

  • Key: SYSML2_-365
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    It is possible to define flow connection usage in several ways.

    One - use the simple/nice notation where syntactic sugar hides the underlying complexity:

    flow of SomeItemDefinition from firstEndCon to secondEndCon;

    Second- use full available detailed notation allowing precise definition of the characteristics of the flow ends:

    flow of SomeItemDefinition {
    end ::> firstEndCon {
       //more end characteristics can be specified here:
       :>>sourceOutput, someFlowPropertyofEnd1;
    }
    end ::> secondEndCon {
       :>>targetInput, someFlowPropertyofEnd2;
    }
}

    Sometimes the second, detailed way is the only way to define characteristics of the ends in the more complex cases. Now the problem is that two different models are created for these two cases. ItemFlowEnd is created for the first/nice/short case while simple ReferenceUsage is created for the full/complete case

    It seems that ItemFlowEnd (meta)type is mostly a syntactic marker.So perhaps it would be possible to get rid of it entirely and make the two cases equivalent from the abstract syntax/model standpoint (by using just ReferenceUsage)?
  • Reported: SysML 2.0b2 — Mon, 4 Nov 2024 08:29 GMT
  • Updated: Sun, 24 Nov 2024 04:39 GMT

Library description of Duration of is truncated

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

    The description in clause 9.8.8.2.4 is missing the three words at the end of the sentence.
    'its start snapshot.'
    The above description in the SysML specification should align with corresponding clause 9.2.12.2.5 in the KerML specification to read as follows:
    DurationOf returns the duration of a given Occurrence relative to a given Clock, which is equal to the TimeOf the end snapshot of the Occurrence minus the TimeOf its start snapshot.
  • Reported: SysML 2.0b2 — Fri, 8 Nov 2024 01:01 GMT
  • Updated: Sun, 24 Nov 2024 04:36 GMT

Header description of unowned elements does not align with textual notation

  • Key: SYSML2_-280
  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    The following row headers describe unowned elements, but the textual notation illustrates that the elements are owned.

    Package with alias member (unowned)
    Package with alias member (unowned)
    Membership (unowned member with alias name)

    The simplest resolution, if the desire to emphasize "unowned" is maintained, may be to use textual notation for each which declare the packages to be aliased in the next higher namespaces.
  • Reported: SysML 2.0b2 — Sat, 10 Aug 2024 18:41 GMT
  • Updated: Fri, 22 Nov 2024 23:07 GMT

Transformation of UML4SysML::ActivityFinalNode is not specified yet

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

    The mapping of a UML4SysML::ActivityFinalNode is not covered by the transformation rules.
  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:04 GMT
  • Updated: Fri, 22 Nov 2024 22:48 GMT
  • Attachments:

Stakeholder_Mapping should map from Classifier to PartDefinition

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

    The SysML v1 stereotype Stakeholder is applied to Classifiers. Therefore, it could also be other model elements than Class which represent stakeholders. The usage of Actor is quite common.

    Actors are mapped to PartDefinition. Therefore, Stakeholders should also be mapped to PartDefinition which makes it more consistent. Stakeholders and Actors are different concepts, but there seems to be no reason to map them differently to parts and items.
  • Reported: SysML 2.0b2 — Fri, 22 Nov 2024 08:24 GMT
  • Updated: Fri, 22 Nov 2024 08:24 GMT

Table 5 Attributes Compartment Graphical Notation and Textual Notation does not match

  • Key: SYSML2_-283
  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    Readers should expect that the textual notation and graphical notation should match as much as possible, including element names.
    The attributes compartment row should at least align on the attribute1 declaration (the definition is different between the graphical and textual notations. I would like to make the case that all of the graphical notation examples should be shown in textual notation, too. If it is worth it to show the graphical notation expectation in the table, it is worth it to show the corresponding textual notation.

    Example of minimum correction in textual notation:
    change:
    attribute attribute1 : Attribute1Def
    to:
    attribute attribute1 : AttributeDef1
  • Reported: SysML 2.0b2 — Sat, 10 Aug 2024 19:31 GMT
  • Updated: Thu, 21 Nov 2024 18:26 GMT

P8 import textual notation may have errors

  • Key: SYSML2_-282
  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    I suspect that there are two errors near the top of page 30 in the P8 namespace textual notation:
    1. Import Annotations::*; should be import ApprovalMetadata::*;
    import Annotations::* does not seem to serve a purpose here, and ApprovalMetadata elements would be needed to support the following code (when corrected).
    2. import NA::*[@Approved]; should be import NA::*[@Approval and approved]; or import NA::*[@approved]; or another version of this depending on interpretation of preceding commentary.
  • Reported: SysML 2.0b2 — Sat, 10 Aug 2024 19:21 GMT
  • Updated: Thu, 21 Nov 2024 18:24 GMT

TransitionUsage source and target properties do not support feature chains

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

    According to the SysML abstract syntax (8.3.17.9 TransitionUsage), the source and target of a TransitionUsage must be ActionUsages. However, the textual notation (8.2.2.17.3 Transition Usages) allows sources and targets to be feature chains, which are parsed as a KerML Feature with FeatureChaining relationships to the chained Features, which are not ActionUsages.
  • Reported: SysML 2.0b2 — Sun, 16 Jun 2024 22:17 GMT
  • Updated: Thu, 21 Nov 2024 16:57 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: Tue, 19 Nov 2024 10:53 GMT

Multiple textual notation issues

  • Key: SYSML2_-285
  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    Issue 1: the following notation found in the middle of the page has a comma instead of a semicolon for the declaration of an "in".

    action def B { in b1, out b2; }
    should be
    action def B { in b1; out b2; }

    Issue 2: The following notation found in the middle of the page has the wrong kind of closing bracket, followed by a semi-colon, following the declaration of an action definition. I.e., a closed parenthesis and semi-colon should be replaced by a closed curly bracket.

    action def B1 :> B { in b1; out b2; inout b3); // Redefinitions are implicit.
    should be
    action def B1 :> B { in b1; out b2; inout b3} // Redefinitions are implicit.
  • Reported: SysML 2.0b2 — Sat, 10 Aug 2024 19:43 GMT
  • Updated: Tue, 5 Nov 2024 16:34 GMT

Error in specification of library model UUIDs

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

    In 9.1 Model Libraries Overview, in the last paragraph, it states that "the prefix https://www.omg.org/SysML/" should be used "when constructing the URL for a standard library package" as part of the generation of model library element UUIDs. The URL used here should instead be the standard OMG base URI https://www.omg.org/spec/SysML/ (which was what was actually used when generating the UUIDs in the normative XMI for the library models).
  • Reported: SysML 2.0b2 — Mon, 21 Oct 2024 18:56 GMT
  • Updated: Tue, 5 Nov 2024 00:03 GMT

Chapter 7.8.7.3.4 is empty

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

    The chapter 7.8.7.3.4 has no content.
  • Reported: SysML 2.0b2 — Wed, 16 Oct 2024 08:56 GMT
  • Updated: Tue, 5 Nov 2024 00:03 GMT

Chapter 7.8.7.3.3 FeatureDirectionKind is empty

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

    The chapter 7.8.7.3.3 has no content.
  • Reported: SysML 2.0b2 — Wed, 16 Oct 2024 08:56 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

Typo - "calculation" instead of "constraint"

  • Key: SYSML2_-330
  • Status: open  
  • Source: Arcfield ( Mr. Alex Whittier)
  • Summary:

    The phrase "As such, any directed usages declared in the body of a calculation definition or usage are considered to be owned parameters of the calculation."
    Should be corrected to say "As such, any directed usages declared in the body of a constraint definition or usage are considered to be owned parameters of the constraint."
  • Reported: SysML 2.0b2 — Mon, 7 Oct 2024 15:55 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

Actor should be mapped to a PartDefinition

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

    An Actor is mapped to an ItemDefinition, but it should be a PartDefinition.

  • Reported: SysML 2.0b2 — Tue, 27 Aug 2024 07:00 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

SysMLv1Tov2.xmi contains temporary mapping classes

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

    The temporary mapping classes

    _InitialState_Mapping and _InitialStateMembership_Mapping

    should be removed from the SysMLv1Tov2.xmi.

    They are not part of the specification document.
  • Reported: SysML 2.0b2 — Wed, 21 Aug 2024 09:57 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

Weak check of input parameter in Helper::getScalarValueType

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

    Helper::getScalarValueType checks only the name of the input parameter and does not consider the fully qualified name to check if it is part of the SysML v1 library. Any DataType of name "UnlimitedNatural" is mapped to ScalarValues::Natural.
  • Reported: SysML 2.0b2 — Sat, 17 Aug 2024 11:54 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

Typo in definition of RenderingDefinition

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

    "A RenderingDefinition is a kind of PartDefinition. As such, all the general semantic constraints for a PartDefinition (see 8.4.7.1) also apply to a ViewDefinition."

    Should be "RenderingDefinition" not "ViewDefinition"
  • Reported: SysML 2.0b2 — Tue, 13 Aug 2024 08:14 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

Missing word in description of view usage

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

    spec: "A view definition or usage is declared as a kind of part definition or usage (see 7.11.2 ), using the kind keyword view. A view usage must be defined by a single view."

    Should this be "single view definition"?
  • Reported: SysML 2.0b2 — Tue, 13 Aug 2024 08:07 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

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

  • Key: SYSML2_-286
  • 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: Tue, 5 Nov 2024 00:02 GMT

Error in textual notation on this page ("comment Comment 2")

  • Key: SYSML2_-281
  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    There is an error in the last example on this page and in this section. One line calls out "comment Comment 2", which is likely intended to be "comment Comment2".
    Suggest change from original: comment Comment 2
    to: comment Comment2
  • Reported: SysML 2.0b2 — Sat, 10 Aug 2024 18:48 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

Presuming missing word in sentence describing implicit annotation.

  • Key: SYSML2_-279
  • Status: open  
  • Source: outlook.com ( Mr. Matthew Johnson)
  • Summary:

    A sentence is missing a word indicating that an owned comment is implicitly about the element owning the namespace, if it is about nothing else:

    Original: "If the comment is an owned member of a namespace (see 7.5 ), then the explicit identification of annotated elements can be omitted, in which case the annotated element is implicitly the containing namespace."
    Should be:"...the annotated element is implicitly about the containing namespace."
  • Reported: SysML 2.0b2 — Sat, 10 Aug 2024 18:31 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

Invalid use of "loop" as merge action name

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

    In two SysML textual notation example snippets, (1) clause 7.16.4 third snippet, (2) clause 7.16.5 last snippet, a merge node is named loop. This is not allowed as loop is a keyword.

    Suggest to rename the merge node to something like loopBegin, beginLoop or loopEntry.
  • Reported: SysML 2.0b2 — Wed, 31 Jul 2024 08:48 GMT
  • Updated: Tue, 5 Nov 2024 00:02 GMT

Replace Generic mapping classes by Initializers

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

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

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

    In order to fix that, all the GenericTo*_Mapping classes shall be removed and replaced par their Initializer class equivalent in an appropriate way.
  • Reported: SysML 2.0b2 — Sat, 15 Jun 2024 10:33 GMT
  • Updated: Tue, 5 Nov 2024 00:01 GMT

Editorial errors in constraints

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

Helper::getScalarValueType operation is not robust enough

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

    The current algorithm crashes if the data type provided has no name defined or if the type is not defined
  • Reported: SysML 2.0a1 — Wed, 6 Dec 2023 16:53 GMT
  • Updated: Tue, 5 Nov 2024 00:01 GMT

Support SysML stereotypes applied to specialized metaclasses

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

    If permitted, the transformation must also enable the mapping of SysML stereotypes that extend specialized metaclasses. For example, Satisfy based on Realization or Block based on Activity.
  • Reported: SysML 2.0b2 — Sat, 2 Nov 2024 10:03 GMT
  • Updated: Sat, 2 Nov 2024 10:03 GMT

Multiple vs Single Trigger/Guard/Effect for State Transitions Contradiction

  • Key: SYSML2_-245
  • Status: open   Implementation work Blocked
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    On one hand abstract syntax chapters for the transitions between states stipulate (Figure 32 in 8.3.17.1@page316, text in 8.3.17.9@page325)
    that transition can have multiple triggers, multiple guards and multiple effects
    by specifying multiplicities [0..*] for TransitionUsage::triggerAction, TransitionUsage::guardExpression, TransitionUsage::effectAction

    On the other hand, semantics and textual syntax chapters for the transitions between states stipulate (8.4.13.3@page424, 8.2.2.17.3@page178)
    that transition can have at most one of each trigger, guard and effect
    by stating:
    "A TransitionUsage is parsed as having the following ownedMemberships
    ....
    Zero to three TransitionFeatureMemberships for up to one each of a triggerAction, guardExpression, and effectAction."

    and by using "?" marks (which has a meaning of [0..1] multiplicity) in the BNF
    "TransitionUsage =
    ...
    ownedRelationship += TriggerActionMember )?
    ( ownedRelationship += GuardExpressionMember )?
    ( ownedRelationship += EffectBehaviorMember )?"

    -----------------------
    This contradiction should be resolved in one direction or another - by stipulating either [0..1] or [0..*] everywhere.

    We suggest that the variant with singular multiplicity be adopted as this seems to be closer to the original intent of standard builders.
    This was also the convention of previous standards (UML)

    Therefore the abstract syntax chapters - Figure 32 in chapter 8.3.17.1@page316, and specification in chapter 8.3.17.9@page325 -
    should be updated with multiplicity [0..1] for the aforementioned 3 fields.
  • Reported: SysML 2.0b2 — Wed, 10 Jul 2024 11:46 GMT
  • Updated: Tue, 29 Oct 2024 19:46 GMT

Directed Composition

  • Key: SYSML17-650
  • Status: open  
  • Source: GE Aerospace ( Chandramouli Jambunathan)
  • Summary:

    Please clarify what is the significance of Directed on the composition line. In the section 8.4.5, the directed line is used, whereas in other sections the direction is not used e.g. in section 11.3.1.1.1.
    Also I referenced in SysML 2.0 beta and I could see directed composition in one of the example. If there is no significance, will it be removed in SysML 2.0?
  • Reported: SysML 1.6 — Fri, 18 Oct 2024 12:31 GMT
  • Updated: Mon, 28 Oct 2024 16:54 GMT

Incosistency between notation tables and BNF related to package nodes

  • Key: SYSML2_-357
  • Status: open  
  • Source: sodiuswillert.com ( Mr. Eran Gery)
  • Summary:

    These issues reported by Dovile.ZIAUKIENE from Dassault.
    See 2 attachments.
    1. Name compartment of a package does not support guilements modifiers

    • a GBNF issue

    2. Unowned member alias notation

    • looks like a notation tables issue
  • Reported: SysML 2.0b2 — Fri, 25 Oct 2024 09:34 GMT
  • Updated: Fri, 25 Oct 2024 10:07 GMT
  • Attachments:

Graphical Notation does not specify else-condition for decision nodes

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

    The specification does not describe the else-condition for an outgoing succession of a decision node.
  • Reported: SysML 2.0b2 — Thu, 24 Oct 2024 18:35 GMT
  • Updated: Thu, 24 Oct 2024 18:35 GMT

Operation should not be mapped to perform action

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

    An Operation should not be mapped to perform action, but an owned action.
  • Reported: SysML 2.0b2 — Fri, 26 Jul 2024 18:02 GMT
  • Updated: Fri, 18 Oct 2024 15:04 GMT
  • Attachments:

Incorrect GBNF production relationship-name

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

    In clause 8.2.3.5 graphical BNF production relationship-name has an incorrect body of comma-separated terminals.

    It should use the pipe symbol as a separator instead of comma, i.e.:

    relationship-name = 'defines' | 'defined by' | 'specializes' | 'specialized by' | 'connect to'
    | 'subsets' | 'subsetted by' | 'performs' | 'performed by' | 'allocated' | 'allocated to'
    | 'satisfy' | 'satisfied by'
  • Reported: SysML 2.0b2 — Wed, 16 Oct 2024 15:06 GMT
  • Updated: Wed, 16 Oct 2024 15:07 GMT

Inconsistent compartment labels

  • Key: